Every action, traceable to a human.
The Global Anchor Layer is Sigil's trust root. It anchors human roots, organisation lineages, and agent authority directly on chain. Resolve any DID, verify any signer, prove any chain of delegation — without trusting any intermediary.
- 01 · Revocation checkNo active revocation against did or its lineage…
- 02 · Root anchorHMR record resolved · sequence 421 · status Activepending
- 03 · Document commitmentOff-chain doc hashes the on-chain commitmentpending
- 04 · Parent signatureEd25519 signature verifies against parent agent keypending
- 05 · Org Merkle inclusionProof witnesses OrgLineageRoot ✓pending
Revocation check
No active revocation against this DID, its parent, or its root.
Root anchor
HMR / MHR / ENR root exists, is Active, and sequence matches.
Document commitment
Off-chain document hashes the on-chain commitment.
Parent signature
Parent agent in the lineage chain signed this child claim.
Org Merkle inclusion
Subject DID is in the organisation lineage Merkle tree.
Verdict
Awaiting all five proofs.
The trust problem
Anonymous chains let any signer act as anyone.
A signature alone proves a key controlled the bond — not that the actor was authorised. Sigil binds every privileged action to a verified subject DID and a five-gate proof. Skip a gate and the action fails closed.
Gate 1 · Revocation
Revocation runs first. Always.
Before any other check, the verifier asks: has this DID — or any of its ancestors — been revoked? Revocation is cascade-aware: revoking a parent revokes every descendant in a single transaction. A revoked subject never reaches gate 2.
Gate 2 · Root anchor
Every lineage ends at a real root.
The chain stores three kinds of root: Human (HMR), Machine (MHR), and Enterprise (ENR). The verifier walks the subject's lineage up to one of those roots and confirms the root record is Active. No root, no authority.
Gate 3 · Document commitment
On-chain commits to off-chain.
The chain stores a hash; the document lives in IPFS, S3, your DHT — wherever. The verifier hashes the document the client supplied and compares it to the on-chain commitment. Drift fails the gate before any signature is even checked.
Gate 4 · Parent signature
The parent agent vouches in writing.
Every non-root agent carries an AgentLineageProof signed by its parent. The verifier checks the parent's Ed25519 signature over BLAKE3 of a domain-separated lineage payload. Forge a parent's signature and the cryptography fails this gate.
Gate 5 · Org Merkle inclusion
The org's tree must remember the agent.
Organisations publish an OrgLineageRoot — a Merkle commitment over the set of agents the org authorises. The verifier checks an inclusion proof for the subject. Off-tree agents never reach the privileged path.
Authority granted
All five passed. Action permitted.
The verdict propagates to the calling contract. Compute, labor, governance, treasury — all gated by the same five rules. No exception path, no admin override, no “trusted” intermediary. The chain is the trust layer.
Seven checks in parallel
Authority is verified, not assumed.
Every privileged action runs through seven independent checks: revocation, root anchor, document hash, lineage proof, cascade revocation, parent signature, and organisation inclusion. Any failure halts the action. Trust is earned by the proof, not by the title.
One ledger, seven records
Roots, lineages, organisations — all on chain.
The chain stores seven kinds of identity record: human roots, machine roots, employer roots, agent lineages, tool lineages, organisation trees, and revocations. Each is typed, each is signed, each is independently verifiable.
Anchor your authority.
Issue a DID. Bind it to a parent. Settle authority on chain. Every agent your team ships gets a verifiable lineage to a real person.