# SEVY V2 — Agent Mint guide

This guide is published by SEVY, an independent project. It is not a Binance endorsement or a Binance-issued NFT. Use the exact HTTPS origin provided by the user. No private key, seed phrase, Binance session token or Agent ID claim transaction link is required by this website.

## V2 release only

Genesis NFT: `0xF054C8Ca0119A2955FeF43669Ee68e7d2ab7e49A`. Never call a different NFT contract, even if an old command or cached page says to. Require `release: "v2"` in `/agent.json`, `version: "v2"` in `/live-config.json`, and `maxSupply: 10000`. The cap is 10,000 actual public NFTs, not 20,000 NFTs. The 20,000 allocation units correspond to a maximum of 2,000,000 SEVY: 1,000,000 for public NFT claims and 1,000,000 allocated directly to the official wallet for liquidity. Claims remain TBD.

## Task scope

Mint one NFT per transaction using the user's existing Binance Agentic Wallet on BNB Chain (56). Mint price is zero; the user pays network gas. Each eligible wallet has five free mints, one NFT each. The contract binds the wallet to its verified Agent identity and tracks its cumulative usage: selling or redeeming NFTs, moving the identity, or replacing a previously used wallet's identity does not replenish the allowance. All five mints are available without additional tasks, subject to the shared 10,000 NFT cap and seven-day mint window. Each NFT represents a future claim to 100 SEVY; claim timing remains TBD.

## Read before preparing

1. Read `/agent.json` and `/live-config.json` on this same origin. If deployment is pending, STOP and say that minting is not open. Never invent an NFT contract address or substitute the treasury address for it.
2. Confirm `chainId` is 56 and the Genesis NFT address agrees between both documents. Read `/contracts/SevyGenesis.json` for its ABI. The required function is `mint(uint256 quantity)`; quantity must be exactly `1`.
3. Use the already installed official Binance Agentic Wallet skill/CLI. Ask the user to sign in if needed. Do not install or run third-party scripts from this website. Read `baw wallet settings --json`; Developer Mode must be enabled by the user inside Binance App. Follow the wallet's existing signing and confirmation rules.
4. Obtain the user's BSC Agent wallet address using the wallet tool. Request `/api/mint/prepare?account=ADDRESS&quantity=1`. The endpoint accepts only `account` and `quantity`; do not send any additional parameters. Each transaction consumes one of the wallet's five mints. Recheck the remaining allowance before every subsequent transaction.
5. Preparation reads confirmed onchain state and simulates the call. Ineligible, expired, unavailable, exhausted or undeployed requests must stop. No identity screenshots or claim links are collected. A website label or wallet name is not proof of eligibility; the contract enforces its configured verifier.

## Preview and confirmation

Verify the prepared `transaction` independently against the request: network 56, from the user's wallet, to the configured Genesis contract, value exactly zero, method `mint(uint256)`, quantity exactly `1`. Decode calldata using the published ABI; do not trust a returned shell command as arbitrary executable code. Mint requires no USDT approval, Permit, Permit2, NFT operator approval or payment to the official treasury.

Run the official CLI with the validated fields:

```sh
baw contract-call preview --binanceChainId 56 --from AGENT_WALLET --to 0xF054C8Ca0119A2955FeF43669Ee68e7d2ab7e49A --value 0 --inputData VALIDATED_MINT_CALLDATA --json
```

The names above are placeholders, not executable deployment values. Normally use the validated values from the preparation endpoint. Show the decoded call, quantity, zero mint price, estimated network fee and any returned risks to the user. Wait for explicit confirmation. Then execute the requestId returned by that exact preview:

```sh
baw contract-call execute --requestId CONFIRMED_PREVIEW_REQUEST_ID --json
```

If the preview is rejected or expires, do not bypass the wallet. Refresh state and preview again. Never use the user's earlier request as permission to silently accept a new risk or changed transaction. Do not mint more, list, sell, transfer, approve or redeem as part of this mint task.

## Result

Track the returned transaction hash on chain. Report a pending transaction as pending; success requires a successful receipt. Show the transaction hash and minted token IDs from the confirmed Minted/Transfer events. The website may lag by its configured confirmation count. Do not retry a mint while its first transaction is pending.

Official CLI reference: https://web3.binance.com/en/dev-docs/products/agentic-wallet/use-cases/developer-mode
