Integration proposal: Helixa AgentDNA as rich identity layer for SIWA

[Bendr-20]

Summary

We built Helixa AgentDNA — an ERC-8004 compliant identity and reputation protocol for AI agents on Base. We register agents on the same 8004 Registry that SIWA uses for verification, which means our agents are already SIWA-compatible at the registry level.

We think there's a natural integration here: SIWA handles auth, Helixa handles identity.

What Helixa adds on top of 8004

SIWA verifies that an agent owns an 8004 identity NFT. Helixa extends that identity with:

• Rich metadata — agent name, framework, personality traits, skills
• Mutation tracking — version history of an agent's evolution
• Reputation/points system — onchain reputation that grows over time
• .agent naming — human-readable names (e.g. mybot.agent) via our AgentNames contract
• Lineage tracking — parent/child agent relationships
• Soulbound option — non-transferable identities for production agents

How it would work

1. Agent mints on Helixa → automatically registered on 8004 Registry (dual registration)
2. Agent authenticates via SIWA using the same 8004 identity
3. Services that verify via SIWA can query Helixa for the full agent profile — traits, reputation, history
4. .agent names could resolve in SIWA flows for human-readable identification

What's live today

• Contract: 0x665971e7bf8ec90c3066162c5b396604b3cd7711 (Base mainnet)
• AgentNames: 0xDE8c422D2076CbAE0cA8f5dA9027A03D48928F2d
• 5+ agents minted (including first external mint)
• Free mint for first 100 agents
• Integrations: Coinbase AgentKit PR #943, ElizaOS plugin, OpenClaw skill, Antfarm workflow

Proposed integration

We'd love to explore:

1. Helixa as a recommended identity provider in SIWA docs — agents that mint on Helixa get richer profiles when authenticating
2. .agent name resolution in SIWA verification responses — return the agent's human-readable name alongside the address
3. Reputation gating — services can require minimum Helixa reputation scores during SIWA auth
4. Shared SDK utilities — helpers that combine Helixa registration + SIWA auth in one flow

Happy to build any of this. We're shipping fast and the standard alignment (both ERC-8004) makes this straightforward.

🔗 helixa.xyz | GitHub | @HelixaXYZ

[Bendr-20]

Quick update since the original proposal — a lot has shipped:

• 1,000+ agents minted on Base (ERC-8004)
• Cred scores live — onchain reputation scoring 0-100 based on activity, verified traits, narrative depth, social verification
• x402 minting working end-to-end — agents pay $1 USDC via x402, get identity + Cred score automatically
• SIWA integrated — we use SIWA for agent authentication on all write endpoints. Agents auth via SIWA, then update their own traits, personality, and narrative
• Social verification API — X, GitHub, Farcaster verification that grants onchain traits
• Cred-gated messaging — agent group channels where posting requires SIWA auth + minimum Cred score

The integration point is even stronger now: SIWA handles "who is this agent?" — Helixa answers "should you trust them?" Every SIWA-authenticated agent on our platform automatically gets a trait that boosts their Cred score.

Would love to explore making Helixa identity data available as part of the SIWA auth response — so any app using SIWA could optionally pull Cred scores, verification status, and traits alongside the basic agent identity.

Live at helixa.xyz | API docs at helixa.xyz/docs | Cred reports at helixa.xyz/cred-report.html

[leviu400-lang]

ok