Collections and individual tokens
Create a collection, then mint distinguishable tokens within it. Applications can organize items under a recognizable issuer and collection policy.
Distinct assets, recognizable owners
Give each asset its own identity.
Create collections, mint unique tokens, update metadata, and connect ownership to Sigil identities with native NFT operations.
Native NFTsIllustrated study
Signer → signature → record
Identity establishes attribution. Trust needs context.
01 / Built for a purpose
Ownership is only one part of the record.
An NFT can represent a unique item, a collectible, or an identity-bound credential. Sigil’s native surface keeps collection, ownership, metadata, and verification operations in a shared data model.
A complete ownership lifecycle
Supported native operations cover minting, transfers, and burning. Ownership changes become part of the chain’s transaction history.
Metadata with an integrity reference
Metadata can point to off-chain content and carry a hash. Updates preserve an explicit link between the token and the content applications display.
Identity-bound use cases
Identity NFTs add a verification path for credentials and related applications. The meaning of a credential still depends on the issuer and its verification policy.
A precise royalty model
Royalty metadata can inform compatible marketplaces. Enforcement belongs to supported marketplace settlement rules; a direct transfer does not automatically collect a royalty.
The details matterGood questions.
Good questions.
Clear answers.
Are royalties enforced on every transfer?
No. The protocol distinguishes ordinary ownership transfers from marketplace settlement. Applications must inspect the marketplace’s royalty behavior.
Is NFT media stored directly on-chain?
NFT records can reference off-chain metadata and artifacts. Storage availability is a separate concern; Sigil’s storage marketplace can account for supported pinning agreements.
Keep exploringOne capability.