Syncing interface
Skip to main content

Documentation Hub

Understanding Seed Metadata

Genesis Seed metadata is the canonical JSON object Wardenseed publishes for each ERC-721 capsule on Base. Wallets, OpenSea, and indexers read the same attribute keys—Rarity, Mythic Identity, Biome, boost percentages, rank fields—that appear in static files, API routes, and encyclopedia profiles. This guide documents the exact schema, storage paths, IPFS resolution, and verification workflow—not abstract NFT concepts.

Understanding Seed Metadata

ERC-721 Metadata Schema

Wardenseed follows the OpenSea metadata standard. Each token exposes name (string), description (string), image (HTTPS or IPFS-resolved URL), optional external_url (encyclopedia profile), and attributes (array of trait objects).

Each attribute object uses trait_type (string), value (string or number), and optional display_type ("number" | "boost_percentage") with max_value for UI formatting. Genesis Seeds ship twenty-one attributes covering rarity, mythic identity, biome palette, economy modifiers, awakening state, genome signals, and collection rank.

Technical Schema

The example below is generated from Wardenseed's buildSeedTokenMetadata function for Mythical Relic Seed #329—identical structure to /generated/seeds/metadata/329.json and the /api/nft/seed/metadata/329 API response.

Production tokenURI on Base resolves to IPFS content identifiers for image and JSON. The static paths on wardenseed.com serve as crawlable fallbacks and developer references; always verify the live contract tokenURI on /ecosystem/contracts before signing.

Metadata JSON — Genesis Seed #329
{
  "name": "Wardenseed Genesis Seed #329",
  "description": "Wardenseed Genesis Seed #329 is a capped Wardenseed SeedNFT: a living-digital seed identity for lineage evolution, recombination affinity, and mythic provenance. It preserves the seed as the primary asset and never mints SEEDOS rewards directly.",
  "image": "https://wardenseed.com/generated/seeds/images-pro/v3/329.webp",
  "external_url": "https://wardenseed.com/seeds/329",
  "attributes": [
    {
      "trait_type": "Rarity",
      "value": "Mythical"
    },
    {
      "trait_type": "Mythic Identity",
      "value": "Relic"
    },
    {
      "trait_type": "Biome",
      "value": "twilight_vine"
    },
    {
      "trait_type": "Accent Color",
      "value": "#516931"
    },
    {
      "trait_type": "Evolution Modifier",
      "value": 10.27,
      "display_type": "boost_percentage",
      "max_value": 12
    },
    {
      "trait_type": "Rarity Rank",
      "value": 14,
      "display_type": "number",
      "max_value": 1000
    },
    {
      "trait_type": "Genesis Index",
      "value": 329,
      "display_type": "number",
      "max_value": 1000
    }
  ]
}

Truncated attribute list for readability. Full JSON includes Visual Aura, Awakening Stage, genome signals, and economy pressure fields.

TokenURI resolution on Base
{
  "chain": "Base (chainId 8453)",
  "tokenId": 329,
  "tokenURI_patterns": {
    "static_metadata": "https://wardenseed.com/generated/seeds/metadata/329.json",
    "api_metadata": "https://wardenseed.com/api/nft/seed/metadata/329",
    "encyclopedia_profile": "https://wardenseed.com/seeds/329"
  },
  "ipfs_note": "Production tokenURI on Base resolves to IPFS CIDs. Verify contract addresses and owner roles on /ecosystem/contracts before marketplace actions."
}

Attribute Reference

Rarity and Rarity Rank are related but distinct: Rarity is the band label (Mythical, Epic, Rare, Common) derived from rank thresholds; Rarity Rank is the numeric collection standing (1 = best). Genesis Index equals tokenId.

Boost attributes (Evolution Modifier, Mutation Affinity, Sink Efficiency) use display_type boost_percentage with documented max_value caps (12, 10, and 9 respectively). Awakening fields (Stage, Progress, Lineage Stability, Hidden Potential) use display_type number with max_value 100.

Genome signals (Symbolic Form Signal, Lineage Flow, Recombination Harmony, Economy Link) are categorical strings (Strong, Moderate, etc.) derived from deterministic DNA—not manually assigned lore tags.

Storage Paths and IPFS

Static JSON: /generated/seeds/metadata/{tokenId}.json — pre-generated at build time, suitable for crawlers and offline verification.

Live API: /api/nft/seed/metadata/{tokenId} — returns current metadata including dynamic image URLs when applicable.

Images: unique pro-art at /generated/seeds/images-pro/v3/{tokenId}.webp when available; otherwise dynamic SVG via /api/nft/seed/image/{tokenId}.

Onchain tokenURI on Base points to IPFS-hosted JSON and image CIDs. Wardenseed does not read chain state back into gameplay; metadata is write-once at mint with deterministic generation rules.

Verification Workflow

Step 1: Open /ecosystem/contracts and confirm the Seed NFT contract address on Base.

Step 2: Call tokenURI(tokenId) onchain or read the static JSON at /generated/seeds/metadata/{tokenId}.json.

Step 3: Compare attributes to the encyclopedia profile at /seeds/{tokenId} and to marketplace displays.

Step 4: If any trait_type or value differs, treat the source as untrusted until resolved—do not sign transfers or approvals.

Frequently asked questions

What metadata standard does Wardenseed use?
OpenSea-compatible ERC-721 metadata with trait_type, value, and optional display_type fields for numbers and boost percentages.
Where can I download JSON for a specific seed?
Use https://wardenseed.com/generated/seeds/metadata/{tokenId}.json or the /api/nft/seed/metadata/{tokenId} API route.
Does encyclopedia narrative text appear in onchain metadata?
No. Origin stories, personality analysis, and AI destiny reports are editorial encyclopedia layers. Canonical JSON attributes are the provenance source.
Can metadata change after mint?
Genesis Collection metadata is deterministically generated at mint. Encyclopedia editorial content may expand over time but does not mutate tokenURI JSON fields.
How do I verify IPFS resolution?
Read tokenURI from the Base contract, resolve the IPFS gateway URL, and compare the JSON hash to static files on wardenseed.com and the encyclopedia profile.

Explore the encyclopedia

Continue exploring

Conclusion

Seed metadata is Wardenseed's verifiable identity layer on Base. Use the Technical Schema examples, static JSON paths, and /ecosystem/contracts verification workflow before any marketplace or wallet action. Browse featured seeds below for side-by-side encyclopedia and JSON comparison.