---
name: bin-nft-agent
description: Read-only guidance for interacting with the bin NFT collection and token. Merge is not live and must never be attempted until a verified merge contract and official launch instructions are published.
---

# bin NFT Agent Skill

## Project
- Project name: `bin`
- NFT contract: `0xf6b8027973743061d8411d41914bd85fb8f59f8b`
- Token contract: `0x9A51D8b1233fB222D3E83ce6022c754E49CF2E33`
- Merge contract: **NOT DEPLOYED**
- Merge status: **DISABLED / COMING SOON**
- Explorer links currently configured for BNB Smart Chain:
  - NFT: https://bscscan.com/address/0xf6b8027973743061d8411d41914bd85fb8f59f8b
  - Token: https://bscscan.com/token/0x9A51D8b1233fB222D3E83ce6022c754E49CF2E33

## Safety rules
1. Treat all contract addresses and network settings as configuration, not proof that a contract is safe.
2. Before any transaction, verify the chain ID and compare the address against the project's official website or deployment announcement.
3. Never invent ABI functions, mint prices, wallet limits, token IDs, or transaction calldata.
4. Never approve, transfer, burn, or lock an NFT for merge. The merge contract is not deployed.
5. Do not describe merge as active. The planned concept is 2 original bin NFTs → 1 new NFT + bin tokens, but final terms may change.
6. Do not request or expose a seed phrase or private key. Use the user's wallet signer and ask for confirmation before each transaction.
7. If the contract is not verified or the mint ABI cannot be confirmed, stop and direct the user to inspect the contract on the explorer.

## Mint workflow — target quantity: 2 NFTs
1. The user's default requested quantity is **2 bin NFTs**, not 1.
2. Open the NFT contract explorer and verify the network and contract address.
3. Inspect the verified contract's Read Contract and Write Contract tabs.
4. Identify the actual public mint function and its parameters from the verified ABI/source. Do not assume the function is named `mint`.
5. Verify that the sale is active, at least 2 NFTs remain, and the wallet is allowed to mint 2. Never bypass wallet limits or sale rules.
6. If the verified mint function supports a quantity parameter, prepare one mint call for quantity `2`. If it only mints one NFT per call, explain that two calls may be required and obtain confirmation for that exact plan before submitting either transaction.
7. Read the live price and calculate the total cost for 2 NFTs plus estimated gas using the verified contract rules. Do not guess a price.
8. Show the user the function, quantity (**2**), total amount, network, and estimated gas before asking them to confirm.
9. Submit only after explicit user confirmation. Never silently reduce the requested quantity to 1. If 2 cannot be minted under the contract rules, stop and explain why instead of submitting a different quantity.
10. Return the transaction hash(es) and explorer link(s). If any check fails, stop safely.

## Merge workflow
- Current status: blocked because no merge contract address has been published.
- Do not call a guessed address or create an approval transaction.
- After the team deploys and verifies the merge contract, update this skill with:
  - official chain ID
  - verified merge contract address
  - verified ABI and source link
  - exact eligibility rules
  - NFT approval/transfer behavior
  - token reward amount and payout source
  - maximum supply and sold-out/activation condition
- Require a fresh user confirmation for each NFT approval and each merge transaction.

## Output style
Use concise language. Clearly separate verified on-chain facts from planned features. If the network or ABI is uncertain, say so.