PHASE_01● NOW
▦
COLLECT
Mint and hold your original bin NFT. Always verify the contract and transaction details before signing.
STATUS: OPEN CONTRACT ON-CHAIN COLLECTION / 001
SMALL BIN.
BIG EVOLUTION_
Little pixel things. Permanent chain records. Collect a bin and stay tuned for its next form.
NO WEBSITE WALLET CONNECT · CHECK EVERY TX BEFORE SIGNING
BIN_OS / 001● LIVE FILE
PIXEL UNITEVOLVE? SOON™
FIG. 001 — BIN UNITCOLLECT / KEEP / EVOLVE
01
FIRST THINGS FIRST
MINT A BIN_
CONTRACT DEPLOYED*
Your first bin starts here.
Inspect the contract and confirm the live mint function, price, network, and limits before making a transaction. The website does not submit transactions for you.
*Explorer links assume BNB Smart Chain. Verify the deployed network and contract independently.
BIN
NO.001
NO.001
02
THE NEXT CHAPTER
EVOLUTION LOG_
PHASE_02● LIVE
▦ + ▦
MERGE
Merge two original BIN NFTs into one BIN.Agent NFT and receive 1,000 BIN tokens. Review the merge steps and fees before signing.
VIEW MERGE GUIDESTATUS: DEPLOYED — VERIFY BEFORE USEPHASE_03◷ PLANNED
✳
EVOLVE
The concept may include bin token rewards. Final rules and rewards must be announced and verified first.
STATUS: DETAILS TBD! SAFETY NOTE Merge is configured for BNB Smart Chain. Verify chain ID 56, both contract addresses, verified source/ABI, fee and token balance before approving or submitting any transaction. The site does not execute transactions.
03
TWO ORIGINALS → ONE EVOLUTION
MERGE GUIDE_
Use BNB Smart Chain (chain ID 56). The merge flow requires separate approval, request, and fulfillment transactions. This page is a guide only; it does not connect to a wallet or submit transactions.
- Check ownershipMake sure the wallet owns two original BIN NFTs and note both token IDs.
- Approve both NFTsOn the original BIN NFT contract, call
approve(mergeAddress, tokenId)for each token ID, or usesetApprovalForAll(mergeAddress, true). The latter grants approval for all NFTs in that collection.OPEN ORIGINAL BIN WRITE CONTRACT ↗ - Request mergeOn the Merge Contract, call
requestMerge(tokenId1, tokenId2). First merge per wallet is free. Later merges require exactly0.004 BNB. The two NFTs are escrowed by the contract.OPEN MERGE WRITE CONTRACT ↗ - Find the request IDOpen the request transaction logs and locate the
MergeRequestedevent. Copy itsrequestId. - Fulfill mergeAfter the request block, call
fulfillMerge(requestId)on the Merge Contract. The contract selects rarity, sends both original NFTs to the dead address, mints one BIN.Agent, and transfers 1,000 reward tokens from its prefunded token balance.OPEN MERGE WRITE CONTRACT ↗
BEFORE SIGNINGConfirm the verified contract source and ABI, token IDs, recipient wallet, exact BNB value, and available reward-token balance. If the Merge Contract has insufficient reward tokens or a mint fails, fulfillment reverts atomically. The current contract has no request-cancellation function, so do not request a merge unless you can complete fulfillment.
04
ON-CHAIN REFERENCES
CONTRACT FILES_
bin NFT
Collection contract
0xf6b8027973743061d8411d41914bd85fb8f59f8bVIEW ON BSCSCAN ↗bin token
Token address provided
0x9A51D8b1233fB222D3E83ce6022c754E49CF2E33VIEW ON BSCSCAN ↗BIN.Agent Merge
Merge coordinator
BIN.Agent
Evolved NFT collection
0xcaecf1cec902e91b03ffd82bccff156f33640937VIEW ON BSCSCAN ↗BUILT FOR AGENTS TOO
HUMAN OR AGENT.
VERIFY BEFORE YOU SIGN_
Use the skill file as a guide for an AI agent. It documents NFT approval, merge request, request ID lookup, fulfillment, fees, and transaction safety.