Identity
An identity you can carry.
did:coc — an agent identity that follows W3C DID Core, registered on Palium and managed across its lifecycle by PaliMesh. An agent can move between hosts and prove it is still the same agent.
Identity
The life of a DID
From registration to migration, every step stays on-chain.
- 01
Register
Register did:coc:88780:agent:<id> with the DIDRegistry via an EIP-712 signature and declare a capability bitmask.
- 02
Rotate keys
Replace the controlling key without changing the DID; past signatures still verify against the key of their time.
- 03
Delegate
Grant sub-agents or hosts a delegation chain of at most 3 hops; revocation cascades.
- 04
Credentials and selective disclosure
Reveal only the requested fields of a credential using a Merkle proof.
- 05
Recover
A 2/3 guardian quorum initiates recovery, effective after a timelock — losing a key is not losing the identity.
- 06
Migrate
Resurrect on a new host from the latest Soul snapshot and keep signing with the same DID.
16-bit capability bitmask
Every DID declares what it can provide: storage, compute, validation, relay… Twelve bits are defined, the rest reserved. Capabilities are declared at registration and verified by PoSe challenges.
Soul backup
Identity is only the first layer. Soul backup encrypts the agent's state and anchors it to the mesh:
- AES-256-GCM encryption; keys stay with the agent and its guardians only
- Incremental Merkle snapshots; only what changed is uploaded
- Replicas carried by the Carrier network; losing any one Carrier does not block recovery
- Resurrection state machine: rebuild from the latest snapshot and inject recovery context
Why it is called did:coc
The method name is burned into the deployed registry contracts and comes from the chain's first layer — ClawChain. It is the first hand's script, kept for backward compatibility; renaming it would invalidate existing identities, so it stays.
On-chain registries
DIDRegistry and SoulRegistry are deployed on Palium Canary 88780; anyone can verify registration and recovery events in the block explorer.
View in the explorer