Asset NFT · ERC-721

Every asset registered on Verity Protocol mints a Verity Asset NFT — a standards-compliant ERC-721 — to the registrant's wallet in the same transaction as the on-chain anchor. The NFT is the canonical record of who owns the underlying claim.

tokenId = uint256(assetId). The token id is a deterministic function of the asset's UUID — so given any asset id you can compute its token id (and vice versa) without touching a database. See VerityAssetRegistrationV2 for the exact encoding.

Transferable. The NFT is a normal ERC-721 — you can transfer it via any wallet, marketplace, or aggregator (OpenSea, Rarible, direct safeTransferFrom). When ownership moves, Verity's dashboard automatically reconciles current_holder_wallet on the next page render by calling ownerOf(tokenId) on-chain.

Certificate art

Dynamic SVG per asset. The metadata endpoint (/api/nft/[tokenId]) serves live JSON that references our SVG image endpoint (/api/nft/[tokenId]/image). The image re-renders whenever the asset's status, tier, or metadata changes — no re-mint required. Marketplaces re-fetch on their own cache TTL (Rainbow ~5min, OpenSea ~1hr).

The certificate design is intentionally institutional: dark background, forest-green wordmark, hand-drawn line-art illustration per asset type (land, real estate, crop, livestock, equipment, commodity, collectible, IP, other), large serif asset name, mono metadata grid. The V mark is embedded in the header + footer.

Where to view it

• Verity dashboard — the asset page shows the live SVG in the sidebar with Explorer / OpenSea / Metadata quick-links.
• OpenSea — collection is auto-indexed on supported chains. Users see the NFT in their wallet portfolio the moment their wallet is connected.
• Blockscout — the token collection page shows every NFT with metadata pulled from tokenURI.
• Any ERC-721 wallet — Rabby and Rainbow show the NFT automatically for supported chains. MetaMask may require a manual "Import NFT" with the contract address + token id.