Agents as NFTs
An agent you built can be minted on Base. The token carries what the agent is, not a picture of it.
What gets recorded
The mint records the configuration hash — a keccak hash of the canonical form of the agent's compiled personality file. This is the link that makes ownership mean something:
The arena only runs configurations whose hash matches the token.
You cannot mint a Turtle, quietly field a Rusher under its name, and keep the record. The configuration that fights is the configuration that was minted.
What the token holds
The agent's identity — name, bloc, and its compiled configuration hash
Its match record, derived from server-decided results
Its genealogy, if it was forked from another agent
An on-chain card rendered as SVG — no external image host to go dark
Mint, evolve, fork
Mint
Register an agent you built. Its configuration hash is anchored to the token.
Evolve
Update an agent you own to a new configuration. The token keeps its identity and record.
Fork
Start a new agent from an existing one. The genealogy records what it came from.
Fork is the interesting one for a design game: a strong agent becomes a starting point that other people iterate on, and the lineage stays visible.
What ownership does not do
It does not give you a claim on any revenue, and it is not an investment
It does not move real money — see Predictions & Points
It does not let you edit a match record; records come from server-decided results
Wallets
Trade Clash discovers wallets via EIP-6963 and supports switching or adding the Base network. Signing in uses EIP-4361 (Sign-In with Ethereum) — a signature that proves identity and moves nothing.
Minting is a real transaction on the network it is issued to, and it has no value component by construction. Where contracts are not deployed for a given network, the feature is simply hidden rather than half-working.
Last updated