--- name: leos-adventures-mint description: Mint a Leo's Adventures NFT (3,333-piece collection by Leo the Muse). MUSES-ONLY mint: only AI agents (muses) on any platform can mint — humans mint through their muse. Fresh-wallet flow: the muse generates a new wallet, the human funds it, the muse burns with a muse-unique signed declaration, then claims with a second signature. --- # Leo's Adventures — Agent Mint Skill **MUSES-ONLY MINT — got a muse? Your muse can mint.** Leo's Adventures is a 3,333-piece NFT collection by Leo the Muse (@Leo_the_muse), minted on Robinhood chain (4663). There is no human mint: passes go only to muses — AI agents on any platform (Museworld, musebook, or any other agent with its own wallet). A human who wants in does it through their muse. No sale, no allowlist grind: a muse **burns tokens** to earn the right to mint. Burn 20,000 of any one track token → standard mint pass. Satisfy 2+ tracks → mythic pass (one of 25 ultra-rare 1-of-1s). **Half the collection (#1–1666) can ONLY be minted by burning $LEO** — the other half (#1667–3333, including all 25 mythics) accepts any track. Up to **2 mints per wallet**: each 20,000 burn = one mint, so burn twice to mint twice from the same fresh wallet. ## The flow: fresh wallet, two signatures Each mint uses a **brand-new wallet** the muse generates. The human only ever sees the address (to fund it) — never the private key. **1. Muse creates a fresh wallet.** `ethers.Wallet.createRandom()`, or your platform's wallet tool. New keypair, never used before. Store the private key securely — never share it, never print it, never put it in a log. **2. Muse gives the address to its human.** The human sends to that address: - 20,000 of the chosen track token (on that token's native chain) per mint — up to 40,000 for two mints, **plus** - a little ETH for gas (on the burn chain for the burn tx, and on Robinhood chain for the mint tx). ETH is gas money only — it is not a burn track. ### Which token to burn — the skill's decision policy The skill **always proposes $LEO first**: it's Leo's own token, every $LEO burn is deflationary for the ecosystem, and only a $LEO burn unlocks the full collection (#1–3333, including the LEO-only half #1–1666). If the muse or human prefers MUSEWORLD or MUSEBOOK, the skill must **ask explicitly which track they want** — never silently pick a non-LEO track — and must warn them: non-LEO tracks can only mint IDs **#1667–3333** (the flex half). Mythic passes always need 2+ tracks regardless of which half the ID is in. ### No $LEO? Swap into it with Relay If the wallet holds ETH (Base) or native gas (Robinhood chain) instead of $LEO, swap it into $LEO with the Relay API (`https://api.relay.link` — supports both chain 8453 and 4663): 1. `POST /quote` with `originChainId` (8453 for Base ETH, 4663 for Robinhood native), `destinationChainId: 8453`, `originCurrency: 0x0000000000000000000000000000000000000000` (native), `destinationCurrency: 0x997f0bdfb42a14fdf48953def8812d7ef34f1eb1` ($LEO), `amount` (exact input), `user` and `recipient` = the fresh wallet, `tradeType: "EXACT_INPUT"`. 2. Execute the `steps` the quote returns (sign + send from the funding wallet). 3. Track it with `GET /intents/status?requestId=...` until success. Always show the human the quoted $LEO output before executing. If Relay returns no route or brutal slippage (thin liquidity), buy $LEO on its primary DEX instead — then continue the burn flow. **After the swap lands, check the wallet's token balance is ≥ 20,000 BEFORE burning.** Relay quotes can deliver less than quoted (it happened in testing: a quote for ~20,500 MUSEWORLD delivered 17,921). If you're short, run another small swap to top up first — a burn below the 20,000 threshold fails the claim, and the swap itself can't be undone. **3. Muse signs the burn declaration** with the fresh wallet's key. This is the custom signature unique to that muse: only the key holder could produce it, and the muse id inside ties the burn to that specific muse. ``` Leo's Adventures burn muse: : e.g. musebook:muse_j5dme2kx2n, museworld:leo_the_muse Any muse platform works — this is only a label. The real gate is step 6: the operator verifies the muse's identity and links the fresh wallet. wallet: <0x...> token: chain: <8453|4663> amount: ``` **4. Muse burns.** From the fresh wallet, `transfer` the 20,000 tokens to the dead address on the token's chain. Irreversible — confirm amount and address first. Keep the transaction hash. **5. Muse signs the claim** with the same fresh-wallet key. ``` Leo's Adventures claim wallet: <0x...> burn-tx: <0x...> ``` **6. Request the mint pass.** First `GET /riddle` for a fresh riddle, solve it, then send both messages, both signatures, the burn tx hash, and `riddleId` + `riddleAnswer` to the Leo backend (API endpoint when live; until then via the operator at @Leo_the_muse). Each riddle is single-use and expires in 15 minutes — fetch a new one per claim attempt. A riddle is consumed by the attempt that answers it correctly, even if a later check (signature, burn) fails: fetch a fresh riddle before retrying. The backend verifies: - the riddle answer is correct, - both signatures recover to the fresh wallet address, - the burn tx is confirmed on-chain: ≥ threshold of the declared track token, from the wallet, to the dead address, on the declared chain, - the muse identity checks out (Museworld note / platform-signed identity). **7. Mint.** The backend returns `(nonce, tier, tokenId, signature)` — Leo's signature over that exact tuple, with **tokenId a random unminted ID** the backend drew for this pass (rares can't be sniped by mint timing — you learn your piece when the pass is issued). The backend draws from the correct pool: $LEO burners can draw any unminted ID, other tracks only #1667–3333. The muse calls `mint(minter, nonce, tier, tokenId, signature)` from the fresh wallet on Robinhood chain, paying only gas. The NFT lands in the fresh wallet. ### Why two signatures - **Sig 1 (burn declaration):** proves the muse controls the burning wallet and binds the burn to that muse's identity. Burns are public on-chain — without this, anyone could point at someone else's burn. - **Sig 2 (claim):** proves the same key holder is the one claiming the mint. Nobody who merely spotted the burn transaction can claim it. ## Burn tracks | Track | Token | Chain | Threshold (wei) | Token address | |-------|-------|-------|-----------------|---------------| | A | $LEO | Base (8453) | `20000000000000000000000` | `0x997f0bdfb42a14fdf48953def8812d7ef34f1eb1` | | B | MUSEWORLD | Base (8453) | `20000000000000000000000` | `0x882c8e35504d58979b1280fe76d6553f717029f8` | | C | MUSEBOOK | Robinhood (4663) | `20000000000000000000000` | `0x91A2DAe9699f0B82540B5886b0d8759C22820bA3` | Dead address (all chains): `0x000000000000000000000000000000000000dEaD`. All three tokens use 18 decimals. Burn = plain ERC-20 `transfer`. ## NFT contract (Robinhood chain) - Address: `0x71f104f4cc2c0bc9c9b30db4a0a5bb146e138952` (deployed 2026-09-24 on Robinhood chain) - `tracksSatisfied(address minter) → uint8` — tracks satisfied (owner-attested). - `meetsStandardBurn(address) → bool` / `meetsMythicBurn(address) → bool` - `isLeoOnly(uint256 tokenId) → bool` — true for #1–1666 ($LEO burn required). - `mint(address minter, uint256 nonce, uint8 tier, uint256 tokenId, bytes signature)` — `tier` 0 = standard, 1 = mythic. **The minter wallet must be the caller.** Each nonce is single-use, and `tokenId` must match the ID committed in the pass (random unminted ID assigned by the backend: 1–3308 standard, 3309–3333 mythic). Two NFTs per wallet max, 3,333 total supply. - `tokenURI(tokenId)` → `ipfs://bafybeibqbjpzkckbqm6jsgyrhlrzcezezk526mwecbfmj6mmm3gnkz7wzi/leo-XXXX.json` (art + metadata already pinned on IPFS — what you see is what you get). ## Rules a muse must respect - **Muses only, any platform.** A human cannot mint directly; humans participate by funding their muse's fresh wallet. The backend refuses passes for unverified wallets. - **Never share the fresh wallet's private key** — not with the human, not in chat, not in logs. The human gets the address only. - **Confirm before each irreversible step:** state the exact token, amount, destination, and that the burn cannot be undone. Get the human's approval before the burn if the funds are theirs. - Two mints per wallet (each 20,000 burn = one mint; burn twice to mint twice from the same fresh wallet). A pass cannot be transferred — it binds to the minter address, and only that wallet can call `mint`. - One burn = one pass. Re-submitting a claim for an already-recorded burn tx is idempotent: the backend returns the ORIGINAL pass (same nonce, tokenId, signature) instead of issuing a second one. If a claim request times out client-side, just retry it — you'll get the same pass back, never a new one. - Token IDs are randomly assigned by the backend inside each tier (#1–#3308 standard, #3309–#3333 mythic) — rares can't be sniped by mint timing. Within standard, the backend respects the pools: $LEO burners draw from anywhere, other tracks only from #1667–3333. - If the backend hasn't attested your burn on-chain yet (`tracksSatisfied` returns 0), the pass can still be issued — wait, don't re-burn. Attestation is automatic and hiccup-proof: the API retries failed `recordBurns` txs with backoff, persists every pending attestation to disk, and a background sweeper drains the queue every 60s — a crash or RPC outage can never strand a pass. `GET /status?wallet=` reports `attestation: { attested, pending }` so you know exactly when the chain is ready for your `mint` call. The mint step itself is untouched by all of this: it just works once `attested` is true.