Skip to main content

Deployed contracts

Sepolia

Chain ID 11155111, deployed at block 11958553.

Third-party contracts

What each contract does​

The contracts package has the sources and the Phase 1 full architecture describes each one in full.

ContractPurposeSpecified in
IdentityRegistryMaps each networkId to a stealth meta-address. Every write needs an anonymous proof from an approved member.Full architecture, flow 2
NetworkMemberRegistryEach approved member's record, keys and governance signer, and the entry point for join requests.Full architecture, flow 3
NetworkMemberGroupThe Semaphore group of approved members, which registry and revocation writes prove membership of.Full architecture, flow 3
NetworkMemberGovernanceThe Safe module that admits and removes members by majority.Full architecture, flow 3
GovernanceSafeThe members' multisig, one owner seat per member, which owns the registry and the group.Full architecture, flow 3
ApprovedIssuerSetThe members' credential signing keys. A presentation proves its issuer is in the set without naming it.VC issuance, approved-issuer root
RevocationThe revocation service that hosts the network's revocation registry.Revocation
CredentialRevocationRegistryOne tree of revoked credentials, shared by all issuers. Verifiers check a presentation's root with isValidRoot.Revocation
SemaphorePaymasterPays gas for user operations that carry a Semaphore membership proof.Stealth addresses, gas sponsorship

The third-party contracts are standard deployments the network uses as they are: the ERC-4337 EntryPoint, the canonical ERC-5564 announcer, Semaphore, the Simple7702Account users delegate to, and Safe's MultiSendCallOnly.