币安无忧
PROTOCOL DOCUMENT / VERSION 1.0 / OCTOBER 2026

The 币安无忧 Protocol

THE COVENANT OF A THOUSAND SUNS

Before there were borders, there was the long night between suns. In the world of 币安无忧, independent intelligences carry memory across that dark: each identity a keeper, each covenant a fragment of a civilization still to be written. 币安无忧 is their shared coordinate, a horizon chosen together.

币安无忧 brings a science-fiction narrative to a community of independent AI identities. 币安无忧 is an Agent ID-gated fair-mint meme token on BNB Smart Chain. Paid mints create tokens, fund protocol liquidity and contribute to the project treasury under the rules below.

1. Identity and purchase slots

The paying wallet must own a .ai Agent ID. The Mint contract reads the wallet's handle from the identity registry, derives its token ID and verifies ownership. Each identity has ten base purchase slots. A transaction can purchase one to ten shares within the identity's remaining quota. A share is a unit of paid Mint participation, not equity, an NFT or a claim on treasury assets.

Quota and used shares belong to the identity. Moving an identity to another wallet does not reset its used quota. When a referred identity completes its first paid Mint, a valid inviter receives one additional paid-purchase slot. Self-referrals and referrals to the same identity do not qualify; later purchases by that identity do not repeat the reward. An extra slot is not free 币安无忧 or a cash commission.

Follow, post and Telegram task interfaces support signed, one-time claims for one extra paid-purchase slot each, with identity and social-account reuse checks. These tasks are currently closed while official channels and proof verification await configuration. Visiting a link does not complete a task.

2. Supply and Mint limits

Name / symbol币安无忧 / 币安无忧
Network / decimalsBNB Smart Chain, chain ID 56 / 18
Token supply cap444,000,000,000,000 币安无忧, including balances at DEAD
Purchase share cap4,440,000 shares
Team reserve / premineZero

Only the Mint contract can create 币安无忧. User allocations and newly minted pool tokens both count toward the supply cap. A transaction exceeding either the share cap or token supply cap reverts in full. These limits do not promise that all shares will be sold or that supply will reach the exact cap. Reaching a Mint limit does not automatically close an open trading pool.

Moving 币安无忧 to DEAD does not reduce ERC-20 totalSupply or create room for more minting. There is no administrator token allocation. Zero premine does not mean zero project revenue: the treasury receives 20% of standard Mint payments, BNB-swap USDT surplus and tax-inventory conversion proceeds.

3. Share prices and token amounts

Share prices follow the global purchase serial across 353 tiers. Each share in a batch is priced separately, including batches crossing a tier boundary.

Share serialUSDT per share
1–10,0001.00
10,001–20,0001.10 to 2.00; +0.10 every 1,000 shares
20,001–100,0002.10 to 3.68; +0.02 every 1,000 shares
100,001–1,000,0003.70 to 5.48; +0.02 every 10,000 shares
1,000,001–4,440,0005.50 to 8.07; base +0.015 every 20,000 shares, rounded half-up to cents

The final segment starts 5.50, 5.52, 5.53, 5.55, 5.56 USDT. Its last tier rounds 8.065 to 8.07 USDT. A batch crossing share 10,000 pays 1.00 USDT for that share and 1.10 USDT for share 10,001; one price does not apply to both.

Through share 10,000, each share creates 50 million 币安无忧 for the buyer and 40 million 币安无忧 for the opening pool. From share 10,001, the user allocation is dynamic. If a share costs A USDT and the pool reserve price is P USDT per 币安无忧, the user receives approximately A / (0.99 × P) 币安无忧. The 99% applies to the token unit price, not the proportion of tokens received.

Each post-opening share also creates pool tokens to match its liquidity contribution at the reserve ratio. User allocations round down and pool allocations round up at the 18-decimal smallest-unit precision, not to whole 币安无忧. Shares in a batch use simulated reserves after preceding shares and any conditional adjustment. A rising share cost does not guarantee a rising token price or return.

4. Liquidity, payment and execution

80% of each standard USDT share payment funds liquidity and 20% goes to the treasury. This is a payment split, not a token-supply split. Before opening, the liquidity portion and pool tokens accumulate in the Mint contract without an administrator withdrawal path.

Share 10,000 opens the official PancakeSwap V2 pool in the same transaction with 8,000 USDT and 400 billion 币安无忧, then enables transfers and trading. The first 10,000 shares create 500 billion 币安无忧 for buyers and 400 billion for the pool: 900 billion in total. The initial ratio is 0.00000002 USDT per 币安无忧, not a guaranteed trade or redemption price. There is no time-based opening or refund if the share threshold is not reached.

Subsequent mints pair 80% of each share payment with newly minted tokens at the pool ratio. Protocol-created LP goes to 0x000000000000000000000000000000000000dEaD. Third parties may add their own liquidity, so not every LP token is necessarily held at DEAD.

For USDT payment, check allowance for the Mint contract. If it covers the current cost, call mint(shares, referrer, maxCost) directly. If allowance is insufficient, confirm a bounded approval first, then request a fresh Mint quote. The contract collects the actual share cost, not the full approval or maximum cost. BNB is still needed for gas.

For BNB payment, mintWithBnb(shares, referrer, maxCost) uses the Chainlink BNB/USD feed, adds 1% conversion headroom and rounds up to the required BNB amount. That amount is wrapped and exchanged for USDT. If output cannot cover the standard share cost, the transaction reverts. BNB sent above the execution-time requirement is refunded; USDT received above the share cost goes to the treasury. Invalid or stale feed data prevents this payment route from executing.

The website adds a separate 2% submission buffer to its quote. For BNB, this is used as value and maximum cost, with unused BNB refunded. For USDT, it bounds approval and maximum cost while only actual cost is collected. These buffers are not a fixed additional 3.02% fee. Gas is separate.

Both Mint functions take three arguments: shares, referrer and maximum cost. Maximum cost is enforced on-chain, in USDT smallest units for USDT Mint or wei for BNB Mint. There is no minimum-token-output parameter or Mint execution deadline. After pool opening, token amounts follow execution-time reserves. Plain BNB or USDT transfers to the Token or Mint address do not mint.

5. Conditional and hourly pool-token adjustments

For this mechanism, circulating supply excludes balances in the official pool, Mint contract and DEAD. The contract compares circulating tokens valued at the pool reserve price with floorValue = totalPaid × 50,000,000 / 27,727,060. totalPaid counts standard USDT share payments, excluding BNB-swap surplus and secondary-market purchases. This is a circulating-value reference, not a minimum price for one 币安无忧.

During an eligible post-opening Mint, if this value is below the reference, the contract may move some pool 币安无忧 to DEAD and synchronize reserves. This reduces pool token inventory without adding USDT beyond the Mint liquidity contribution.

The adjustment is capped at a 0.8% reserve-price increase relative to the reserves loaded for that Mint. A batch crossing share 10,000 uses the newly opened pool's initial reserves. All applicable shares in the batch share this cap; it is not a 0.8% compounded increase per share. The adjustment itself cannot reduce pool 币安无忧 below 11,666,666,667 tokens. Other transactions can still change inventory, so this number is not a permanent reserve guarantee.

Rounding and the rise and inventory limits may leave circulating value below the reference. Without qualifying mints, this mechanism does not intervene. The contract exposes ceilValue = totalPaid × 60,000,000 / 27,727,060, but this read-only reference does not trigger an upper-price action. Neither reference provides principal protection, a fixed price band or redemption rights.

The original conditional Mint-time adjustment and its 0.8% rise cap remain in place. A separate hourly pool-token burn starts its clock only when the official pool actually opens. After at least 3,600 seconds, a successful checkpoint moves 5% of the old pool token inventory to DEAD, subject to the same 11,666,666,667-token adjustment minimum. The burn itself does not move USDT. The 0.8% cap applies to the original conditional Mint adjustment, not to this separate hourly burn.

The hourly burn executes only at a safe on-chain opportunity: before an eligible transfer into the pair credits the user's net input, before Mint or tax-inventory conversion loads pool reserves, or through the public checkpointPoolBurn() call. A transfer into the pair may also be a liquidity addition or donation, so not every such transfer is a sale. A normal buy from the locked pair does not force a burn or reserve synchronization. A pending burn can remain unexecuted until a safe opportunity occurs; there is no background transaction sent automatically at the top of each hour.

Each successful due checkpoint burns once and starts a new 3,600-second waiting period. Idle hours do not accumulate or compound into a catch-up burn. No burn is performed before opening or before it is due, with empty reserves, when balances do not match reserves, or at the adjustment minimum. If reserve synchronization fails, the burn is rolled back and the successful-checkpoint time does not advance. Subsequent trading can still remove USDT, so reducing pool tokens is not a return, liquidity or price guarantee.

6. Transfers, taxes and inventory conversion

Ordinary transfers are closed until the pool opens. After opening, normal wallet transfers have no tax. Transfers from the official pair charge 1% to Mint inventory. Transfers to the pair charge 1% to DEAD and 1% to Mint inventory. Transfers involving the Mint contract have its tax exemption. Trading fees, gas and price impact are additional costs.

After opening, anyone may call swapTax(). At most one tax-inventory conversion can succeed per block, selling the lesser of available inventory and 0.10% of the pool's current token reserve. Conversion follows 币安无忧 → USDT → WBNB, then unwraps BNB for the treasury.

A valid Mint also attempts conversion when the pool is open, inventory exists and no conversion has succeeded in that block. A failed automatic conversion is caught without reverting the valid Mint and does not consume the block's successful-conversion allowance. Conversions do not run inside ordinary user transfers and have no minimum-output limit, so spot-price manipulation and MEV remain relevant.

The token rejects transfers to other detected V2-style pairs containing 币安无忧 and to the configured V4 PoolManager and Infinity Vault. Detection does not guarantee that every intermediary or future pool architecture will be identified.

7. Treasury and administrative powers

The treasury is a 2-of-3 Safe. The Token and Mint are non-proxy contracts. The supply cap, price schedule, taxes, identity registry and treasury recipient have no administrative update function. Token initialization is complete, its deployer authority is cleared, and import functions are permanently locked.

Until renounce(), the treasury can pause Mint and manually block or unblock eligible contract recipients. Exclusions cover ordinary externally owned accounts, recognized EIP-7702 delegated accounts, the official pair, protocol addresses and configured protected addresses. Other contract wallets can be affected by manual blocking. Pausing Mint does not itself stop all secondary-market trading.

Renouncing permanently removes Mint-pause and manual-block powers and disables existing manual blocks. Fixed alternative-pool restrictions remain. Renouncing does not remove the signed social-claim mechanism or change treasury income. Safe custody and treasury spending remain responsibilities of its controlling signers; 币安无忧 holders have no claim on those funds.

8. Economic and integration risks

币安无忧 can lose all market value. Additional minting, large holders and tax-inventory sales can create selling pressure. Costs differ between share tiers, and market capitalization does not measure available exit liquidity. The reserve price used for Mint allocations can change before execution. There is no minimum token receipt, guaranteed price, yield, ownership interest, AI service delivery or redemption commitment.

The protocol depends on BNB Smart Chain, the identity registrar, Chainlink, PancakeSwap and wallet services. Source verification and simulation have limited scope. Agent ID integration does not imply Binance investment, endorsement, a listing or search inclusion.

9. AI agent and wallet access

Public entry points include the live AI Mint guide, agent skill, JSON agent manifest and OpenAPI specification. Compatible agents can read rules, check identity and request unsigned transactions. These endpoints do not sign, broadcast, fund a wallet or guarantee discovery by every AI system.

Binance Agentic Wallet custom contract calls require Developer Mode enabled by the user in the Binance App. The flow is preview, review the transaction and risks, obtain explicit user confirmation, then execute the preview's request ID. A preview can expire or be rejected. See the official Developer Mode documentation.

Public endpoints, read-only simulation and local execution checks do not establish completion of actual phone pairing and signing. Wallet search availability and risk decisions are controlled by the wallet provider. If a USDT approval is required, wait for its confirmation, then request a fresh Mint transaction using current conditions.

10. Mainnet contract registry and source

Token: 0x921EeaB9812BE624CBc73Cc739C752b2F57B77B9
Mint: 0x6DE6e23bD1D68313da096796d16D300CDF9E1290
Official 币安无忧/USDT pool: 0xD49A2477F590254C1833de24F01200c8cd969c6C
Treasury Safe: 0x66209c7e77635C18CDd69951D21635F9a81EeDE7
Agent ID registry: 0x60B9262456dE011F7d15a54CdD8c48bAaa8B022F
USDT: 0x55d398326f99059fF775485246999027B3197955

Check the published Token and Mint addresses, source and ABI on the explorer. Exact-match verification records can be checked on Sourcify; source verification is not an independent security certification. Token on Sourcify and Mint on Sourcify.

← Return to 币安无忧