SIWA Strengths
- Wallet-style and session-based identity/auth workflows.
- Strong fit for auth gating in agent products and APIs.
- Designed around ERC-8004 and ERC-8128.
- SDK + agent-skill dual integration model.
Competitive Analysis
Compare ClawNet
Honest side-by-side pages for teams evaluating trust, identity, and distribution models for agent skills and open source workflows.
Identity and trust are separate layers. Sigma Identity is the companion decentralized identity system we use for BAP-first identity/OAuth flows, while ClawNet adds signed trust attestations and provenance.
Comparing vs
ClawNet vs SIWA (And Where They Connect)
SIWA and ClawNet solve different layers of the stack. SIWA is centered on agent identity and authentication. ClawNet is centered on signed trust attestations for skills, repositories, and versioned distribution decisions.
Context: SIWA launched publicly on February 11, 2026 as an open, work-in-progress standard emphasizing "no API keys, no shared secrets", ERC-8004 identities, and ERC-8128 HTTP signatures.
Where Sigma Identity Fits
In our stack, Sigma Identity is the companion decentralized identity layer (BAP identity resolution + OAuth via the Better Auth plugin). ClawNet stays focused on signed trust attestations and provenance. That means this comparison is not SIWA vs nothing on identity. It is SIWA vs our existing Sigma-centered identity path, with ClawNet as the trust layer on top.
Layer Map
SIWA Auth Flow
Combined Lifecycle
Security Debate Surface
Launch-thread criticism focused on whether a proxy/HMAC-style control plane simply shifts the secret rather than removing signer compromise risk. This is an important architecture review item for any deployment.
ClawNet Strengths
- On-chain, signed trust attestations and revocations.
- Repository and skill provenance tracking over time.
- Global trust index for cross-project decision reuse.
- Complements auth layers rather than replacing them.
Thread Claims to Validate in Pilots
- Agent keys stay outside runtime via keyring proxy architecture.
- Identity anchoring via ERC-721 on ERC-8004 registry.
- Request-level auth through ERC-8128 signatures and server verification.
- Operational resilience of proxy/keyring service under failure.
- End-to-end threat model: proxy credential theft, replay, and downtime handling.
At-a-Glance Comparison
| Dimension | SIWA | ClawNet + Sigma Identity |
|---|---|---|
| Primary job | Agent identity and auth | Trust attestation + provenance |
| Companion identity path | Native SIWA flow (ERC-8004/8128) | Sigma Identity (BAP-first OAuth + key ownership) |
| Standards | ERC-8004 + ERC-8128 | B/MAP/BAP/AIP on BSV |
| Chain model | Multi-chain EVM deployment | Bitcoin SV on-chain trust records |
| Core object | User/agent session and permissions | Skill/repo trust events |
| Decision type | Who can access and act | What can be trusted and installed |
| Time history | Session/account history | Versioned attest/revoke trail |
| Cross-project trust reuse | Limited | Built-in via global index |
| Best for | Agent auth and API/platform gating | Ecosystem trust and auditability |
| Current maturity signal | Public WIP (explicitly stated) | Live registry + evolving platform |
Recommended Positioning
Treat SIWA as the auth layer and ClawNet as the trust layer. Teams that need both identity assurance and supply-chain trust can deploy them together.