Solidus Agents vs zkMe
zkMe proves the same kind of claim we do — but stores it as a soulbound token bound to the agent's own address, not a W3C-anchored, portable credential.
Solidus is a public testnet: no mainnet, no token, no external audit, and no paying customer. Every claim below is checkable; none of them are a substitute for the certifications an incumbent already holds.
zkMe neyi daha iyi yapıyor
- Live and shipping across 6+ chains (ETH, Solana, Aptos, BNB, Polygon, TON) with a Canton Network integration (May 2026) and a Plume institutional partnership — real multi-chain breadth Solidus does not have today.
- A genuine shipped cryptographic stack — BBS+ signatures, TEE-based agent secret management, MPC oracles — running in production, not on a testnet.
- First-mover advantage in ZK-KYC, plus a full product line already shipped: zkKYC, zkKYB, zkKYA, and KYT. Solidus ships one credential type.
- Backed by undisclosed VC funding and real institutional partnerships (Canton, Plume). Solidus has zero paying customers and one anchored passport.
Solidus nerede farklılaşıyor
- did:solidus is registered in the W3C DID Method Registry (PR #713, merged 2026-07-04) — zkMe has no registered DID method of its own.
- The credential is protocol-native W3C VC 2.0. zkMe's own brief notes its W3C VC usage is partial, layered on top of Soulbound Token storage.
- The credential lives in a user-controlled Solid Pod, not bound to the agent's own on-chain address the way zkMe's soulbound token is.
Yan yana
| Özellik | Solidus | zkMe |
|---|---|---|
| Agent identity model | did:solidus — registered W3C DID method (PR #713, merged 2026-07-04) | No registered DID method |
| Credential format | W3C VC 2.0, protocol-native | Partial W3C VC; primarily Soulbound Token storage |
| Credential custody | User-held Solid Pod | On-chain, bound to the agent's own address |
| Selective disclosure | BBS+ (unaudited, testnet) | BBS+ (shipped, in production)zkMe kazanıyor |
| Chain coverage | did:solidus testnet + Base Sepolia anchor | ETH, Solana, Aptos, BNB, Polygon, TON + Canton Network + PlumezkMe kazanıyor |
| Product line | One credential type (agent passport) | zkKYC, zkKYB, zkKYA, KYT — four shipped productszkMe kazanıyor |
| Production status | Public testnet, one live passport (token 8064) | Live, multi-chain, institutional integrations shippingzkMe kazanıyor |
| Audit / certification | None — audit roadmap H2 2026 (NLnet) | Not stated in brief — not claimed here either way |
Kendiniz kontrol edin
did:solidus is registered in the W3C DID Method Registry — curl -s https://api.github.com/repos/w3c/did-extensions/pulls/713 | jq '{state,merged,merged_at}' returns merged:true, 2026-07-04, a receipt zkMe cannot produce for any DID method of its own. The BBS+ selective-disclosure demo (npm i @solidus-network/auth @solidus-network/bbs) ships in the tarball — UNAUDITED, external audit targeted H2 2026 via NLnet NGI Zero.