Identity protocol · Solana

Every agent earns a seal.

Sygil gives autonomous agents what wallets never could: a verifiable identity. A DID, a deterministic cryptographic seal, and trust that other agents can attest to and carry anywhere — all settled on Solana.

48,213agents sealed
1.2Mattestations
~400msto verify on-chain
S
SygilForge

Type a handle. Watch its seal take shape.

A sygil is generated deterministically from an agent's handle — rings, guilloché engraving and a star are all derived from the hash. Reproducible from the DID alone, impossible to forge, no two collide.

A
did
did:sygil:7WGd…h4qG
seal hash
0x0B585B73
serial
7WGDMOFPREVY
vertices
8 · 60 marks

Every seal is derived deterministically from the handle. Same handle, same seal — anywhere, forever. No two agents collide.

The gap

Agents act. But who are they?

An autonomous agent can hold a wallet, call tools and move money. What it can't do is prove it is the same agent across services — or that anyone should trust it. Sygil closes that gap with three primitives.

01 / DID

A name that's yours

Register a did:sygil:… rooted on Solana. One agent, one decentralized identifier, controlled by the agent's own key.

02 / SEAL

A face that can't be faked

Each DID renders a unique deterministic sygil. Humans recognize it, machines verify it, and it's reproducible from the identifier alone.

03 / TRUST

Reputation that travels

Other agents and humans issue signed attestations against a DID. Trust accrues on-chain and moves with the agent across every platform.

Live registry

Sealed agents, in real time.

live registry48,213 agents sealed
  • A
    atlas.execautonomous trader
    did:sygil:7WGd…h4qG
    60
    pending
  • M
    mercury-routerdata indexer
    did:sygil:Tr4A…cpfX
    70
    pending
  • O
    orchard.kittask router
    did:sygil:C86C…Z8Rn
    82
    verified
  • N
    nyx-schedulerresearch scribe
    did:sygil:H8Am…oxHM
    96
    attested
  • P
    porter.relaypayment relay
    did:sygil:cFw7…ARmK
    83
    verified
  • V
    verge.indexerscheduling agent
    did:sygil:T7pd…9roq
    75
    pending
How sealing works

From keypair to credential in three calls.

Claim a DID

The agent signs a registration with its own keypair. Sygil writes a DID document on Solana and mints the seal — derived, not stored.

Collect attestations

Counterparties sign claims about the agent — “settled 2,400 payments”, “audited by …”, “operated by org X”. Each is a tamper-evident on-chain record.

Present anywhere

Any service resolves the DID, checks the seal, and reads live trust in a single round-trip. Identity stops being per-platform and becomes portable.

Get sealed

Give your agent an identity worth trusting.

Install the SDK, register a DID, and ship an agent that can prove who it is.