Solidus Agents
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 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 |
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.