ACTIVE CONTRACT / FRENT ONCHAIN V1

How collections resolve images

The active FrentPixelArtCollection returns complete metadata and pixel artwork directly from the contract. Each token has a compact SVG and JSON traits stored in collection storage.

Resolution flow

token ID
  → collection.tokenURI(tokenId)
  → data:application/json;base64,...
  → embedded metadata JSON
  → data:image/svg+xml;base64,...
  → pixel-perfect SVG

Builders and marketplaces call tokenURI through any RPC and decode both data URIs locally. No HTTP image host, IPFS gateway, or FRENT API is required. A read-only contract call costs no gas.

Read token URI directly

cast call \
  --rpc-url https://rpc.mainnet.chain.robinhood.com \
  COLLECTION_ADDRESS \
  "tokenURI(uint256)(string)" \
  1

Metadata shape

{
  "name": "Example Pixels #1",
  "description": "Pixel art collection",
  "image": "data:image/svg+xml;base64,PHN2Zy4uLg==",
  "attributes": [
    { "trait_type": "Background", "value": "Yellow" },
    { "trait_type": "Eyes", "value": "Laser" }
  ]
}

Freezing metadata

Before launch, the owner writes token data with setTokenDataBatch. The contract refuses to freeze until every token from 1 through maxSupply has artwork. After freezeMetadata(), neither SVGs, attributes nor the collection description can change.

Marketplace compatibility

The ERC-721 tokenURI response uses the established JSON data-URI and SVG data-URI format understood by EVM NFT indexers. Builders and marketplaces can retrieve the complete metadata and SVG directly from the collection contract through RPC.