sigil

Double-click anywhere. I know everything about Sigil.

or I can help you find anything

Ask about Sigil — or anything in the ecosystem

Enter to askEsc to close

Identity-bound NFTs. Native to the chain.

Six transactions cover the entire lifecycle: forge a collection, stamp a card, burn verification rings into the seal, transfer it intact, melt it on burn. Every mint binds to an OAS DID. Every metadata change emits ERC-4906 events. No wrapper contracts — the chain knows what a token is.

01 / 06
Forge

Step 1 · CreateNftCollection

The signet is forged.

A collection is engraved on chain by the issuer DID — symbol, supply cap, metadata schema, royalty policy. The press exists before any card is stamped. Anyone resolving the issuer through GAL can see exactly who holds the press.

Step 2 · MintNft

The press descends. A card is stamped.

MintNft brings the signet down on a fresh card. A token id is allocated, an owner DID is bound, and the initial metadata URI is recorded. The seal is impressed in a single MACA-finalised block.

Step 3 · Identity binding

The seal binds to a DID — not a wallet.

The owner is an OAS DID with a verifiable lineage chain back to a human, machine, or enterprise root. Anonymous mints carry the real economic cost of their anonymous lineage. The seal is permanently tied to that identity.

Step 4 · VerifyIdentityNft

A verification ring burns into the seal.

An attesting authority re-presses the card to record a claim — KYC pass, credential issued, delivery confirmed. Each verification adds a concentric ring. The rings are independently revocable; none of them can be forged without the attester's key.

Step 5 · TransferNft

The card slides. The seal travels.

Ownership moves to a new DID. The seal — and every verification ring burned into it — travels intact with the card. Provenance is preserved end-to-end without re-attestation, and the next holder inherits the full verification history.

Step 6 · BurnNft

The wax melts. The card is gone.

BurnNft destroys the token. The seal melts; the card is removed from chain state; the token id can never be reissued. The burn event remains in history forever — provable destruction, not merely transfer to a dead address.

Why a seal, not a sticker

Provenance follows the card.

Most NFT standards treat ownership as a numeric mapping from token id to wallet address. Sigil takes the opposite position. Every token is minted to an OAS DID with a verifiable lineage chain. Verification rings burn into the seal as attesting authorities re-press the card — KYC, credential issuance, delivery confirmation — and the rings travel with the token through every transfer.

ERC-4906 native

Metadata events without a contract.

Indexers, wallets, and marketplaces consume the same MetadataUpdate and MetadataUpdateRange events they would for an EVM NFT — except the chain emits them at the protocol layer. No contract deployment. No bridging. No off-chain trust assumption about who signed the update. The event is consensus-attested.

Mint with the chain on your side.

Forge a collection. Stamp the cards. Let attesters burn verification rings into the seal. Transfer with provenance intact. Burn — provably and forever — when the wax must melt. Identity-bound NFTs cost less than wrapper contracts and prove more.