--- name: bnbcore-mint description: Read BNBCore deployment details, verify .ai identity and prepare an unsigned Seed mint for explicit wallet-owner confirmation. --- # BNBCore AI Mint Release: 2026-10-25-rpc-failover-1. ## RPC recovery (required) Use the bundled `scripts/agent.mjs` for status, unsigned mint preparation and receipt checks. It includes automatic bounded failover; do not stop after the first manual RPC read fails. Download the current `toolkit.zip` beside this Skill and run its locked Node dependencies if your environment supports command execution. The tool never signs or broadcasts. For manual execution environments, apply the same policy: try different RPC operators (BNB Chain, PublicNode, dRPC, Blast); at most two complete verification attempts per endpoint, with a 10-second timeout per request. Select a recent block 12 blocks behind the endpoint head; pin all verification reads to that block. If a block/state read fails, discard the partial attempt, select a new block, and rerun the entire operation on a fresh connection. Do not combine successful checks from different attempts or skip Bloom. Code/binding/quote mismatch, missing eligibility and contract reverts must stop immediately and must not be treated as connectivity errors. After all providers fail, return the exact diagnostics. No signing or sending is authorized by a retry. Revalidate the preview before signing; the pinned block is a verification snapshot, not a guarantee of future transaction success. This skill is a preparation workflow, not permission to sign, pay, register identities or perform administration. ## Deployment status Read `deployment.json` beside this file and `abis/BNBCoreSeed.json`. The mainnet addresses and runtime hashes are published in the manifest, restored from prior successful mainnet verification. Read its review field for verification scope and incomplete historical receipt coverage. Sale fields are a historical snapshot, not current availability. Independently recheck all hashes, bindings and current sale state before simulation. This is not an independent audit. Stop before simulation or execution when status is not `verified-deployment`, any address/hash is absent, or network is unconfirmed. Never borrow BNBS or other project addresses. A downloaded manifest is not automatically authentic: validate its project origin and deployment provenance. ## User intent Confirm Seed quantity (integer 1–5), network and the actual authorized signing wallet. No website wallet connection is required. Never ask for or accept seed phrases/private keys. Public-address lookup is not signing authorization. Do not register/buy a .ai identity automatically. ## Checks 1. Match BSC mainnet chain ID 56 and deployed runtime hashes for Seed, Bloom, identity adapter and Agent ID NFT. Check their binding addresses, the immutable treasury, source verification status, administrator and published permissions. A proxy Agent ID NFT additionally needs implementation and upgrade-policy verification. 2. Verify that the actual signing wallet holds a valid Binance Agent ID `.ai` NFT. Missing, expired, mismatched or unavailable identity must stop the workflow. A positive `balanceOf` alone is insufficient if the official token has an additional expiry/revocation rule. 3. Read mint open/paused state, sale deadline, remaining supply and cumulative wallet mints. Original mint allowance is five per wallet; never infer eligibility from a website label. 4. Obtain `quote(quantity)` on-chain. Expected price is 0.005 BNB per Seed; verify it on-chain. Read balance, simulate the exact call and estimate gas. Stop on any failure. Revalidate immediately before signing. 5. Show chain, signing wallet, Seed contract address, `mint(uint256)` calldata, exact BNB value, estimated gas and fixed treasury address. Successful Mint forwards payment to the treasury; there is no sellout refund. Never substitute a direct native transfer. 6. Wait for explicit confirmation of this exact transaction through the user's wallet. The supplied CLI never signs or broadcasts. Do not perform fusion, purchases, approvals or administration as a side effect. 7. After submission, verify chain, transaction from/to/value/calldata, successful receipt, SeedsMinted event, minted NFT ownership and cumulative allowance at the receipt block. Return hash and confirmation count. A hash alone is not success. For pending/unknown outcomes, inspect the same hash rather than resending. ## Tools Source repository: `protocol/scripts/agent.mjs` (Node.js, dependency ethers). Install the repository's locked dependencies with `npm ci` inside `protocol/`. The default RPC pool works without configuration. Optionally set `BNBCORE_RPC_URLS` to comma-separated HTTPS endpoints (preferred first), or `BNBCORE_RPC_URL` for a preferred single endpoint. You may also set `BNBCORE_MANIFEST` to the reviewed deployment JSON path. No signing credentials are accepted. - `node scripts/agent.mjs status PUBLIC_ADDRESS` - `node scripts/agent.mjs mint PUBLIC_ADDRESS QUANTITY` - `node scripts/agent.mjs receipt PUBLIC_ADDRESS QUANTITY TRANSACTION_HASH` `status` inspects. `mint` produces an unsigned preview only after checks and simulation. `receipt` verifies the matching operation. There is no execute option. ## Implementation limits The NFT Mint/fusion module has not undergone an independent audit. The production Agent ID address and runtime hash are published in deployment.json; verify them and the adapter binding against mainnet on each run. Runtime comparison is distinct from explorer source verification. The manifest documents the scope of prior verification and incomplete deployment receipt coverage. Website market orders are not implemented. Test fixtures are never production substitutes. Holding a .ai name does not prove a unique person; contracts cannot reliably determine whether a caller used an AI interface. The tools prepare unsigned transactions only.