Skip to main content
is Sumvin’s portable, verifiable digital identity, anchored to -verified users. It lets users — and their AI agents — prove who they are across third-party services without repeatedly sharing personal data. Sigil is not a record you look up. It’s a credential the user carries, cryptographically.

​
The three pillars of Sigil

  1. Non-custodial smart account wallets — each user gets a Safe multisig wallet that serves as their on-chain identity anchor.
  2. — EIP-712 signed messages that authorise specific actions and scopes. A Stamped Mandate is delivered over the API as a PINT (header x-sumvin-pint-token).
  3. The Sumvin Identity Service (SIS) — exchanges signed Stamped Mandates for verifiable JWTs that third parties can independently validate.

​
How it works

A typical Sigil flow looks like this:
  1. The user (or their agent) signs a Stamped Mandate — a structured EIP-712 message declaring what they want to do, which scopes they authorise, and how long the authorisation is valid. On the wire this is a PINT.
  2. Your app exchanges the signed mandate with the SIS token service, which validates the signature, checks KYC status, and returns a SIS-signed JWT.
  3. The JWT travels with requests to third-party services, which verify it against the SIS public keys (JWKS) and optionally check revocation status.

​
Key concepts

ConceptDescription
SigilSumvin’s portable, KYC-verified identity — “Proof of Personhood” a user carries across services
SRISumvin Resource Identifier — a URI-style identifier for users and resources (sr:us:person:safe:0x...)
Stamped Mandate (PINT)A signed authorisation a user grants for specific scoped actions — an EIP-712 signed message, delivered over the API as a PINT
SISSumvin Identity Service — the API that validates Stamped Mandates and issues JWTs
Safe WalletThe user’s on-chain identity anchor (Gnosis Safe multisig)
ScopesPermission grants included in a Stamped Mandate (e.g., sr:us:pint:identity:proof_of_personhood)
Verification TierStandard (JWT only) or Enhanced (JWT + PINT signature) — determined by scopes requested

​
Who uses what

You are…You need…
An app developer building on SumvinThe Platform API to create users and wallets, then this Sigil tab to create Stamped Mandates and exchange them for JWTs
A merchant or service provider receiving Sumvin credentialsThe Verifier Guide to validate incoming JWTs and PINT signatures

​
Next steps

  1. SRI format — the URI family that identifies users, resources, and scopes.
  2. EIP-712 and PINTs — the signed message spec your Stamped Mandates are built on.
  3. Token exchange — trade a signed Stamped Mandate for a SIS-issued JWT.
  4. Scopes reference — the capability envelope each Stamped Mandate carries.