1. Overview
QTARDS is a token and NFT project on BNB Chain. Minting is open to Binance Agentic Wallets holding an official .ai Agent ID.
The launch has one 48-hour window and 10,000 combined units: 8,750 units minted with USDT and 1,250 free claims. Both allocations must fill before the deadline. There is no separate fundraising target in USDT.
Tokens arrive in the successful mint transaction. Completing 10 paid units also delivers an NFT immediately. If the launch does not fill, original paying wallets can claim their recorded USDT back.
There is no presale, private round, or separate team token allocation. The treasury receives 20% of mint proceeds after a successful launch, plus its share of trading and marketplace fees.
2. Supply & allocation
The token has 18 decimals and an initial supply of 1,000,000,000 QTARDS. This supply is created at deployment and allocated once to the mint, free-mint, and staking contracts. The token has no function for creating additional supply after deployment.
| Allocation | Share | QTARDS |
|---|---|---|
| Mint with USDT | 45% | 450,000,000 |
| Liquidity | 45% | 450,000,000 |
| Free mint | 5% | 50,000,000 |
| NFT staking | 5% | 50,000,000 |
Trading-tax burns permanently reduce the token’s total supply. Transfers to staking, the converter, or liquidity move existing tokens; they do not create new ones.
The paid and free token amounts differ. Paid units divide 450M QTARDS across 8,750 units, or approximately 51,428.571428 QTARDS each. Every free claim receives exactly 40,000 QTARDS. Together they account for 500M participant tokens.
3. Minting with USDT
Minting requires current ownership of the submitted Agent ID in the pinned .ai registry. A wallet can register one paid Agent ID, and each participating ID can receive at most 10 paid units cumulatively. A transaction may purchase 1–10 units, subject to the remaining launch capacity and that ID’s allowance.
Price steps & your locked rate
The starting price is 1 USDT for each unit. After every 1,000 paid units sold, the rate available to a new paid participant increases by 0.10 USDT for each unit. That is a 1 USDT increase for a complete 10-unit entry. Free claims do not advance the paid-price counter.
| Paid units already sold | One unit | 10-unit equivalent |
|---|---|---|
| 0–999 | 1.00 USDT | 10 USDT |
| 1,000–1,999 | 1.10 USDT | 11 USDT |
| 2,000–2,999 | 1.20 USDT | 12 USDT |
| 3,000–3,999 | 1.30 USDT | 13 USDT |
| 4,000–4,999 | 1.40 USDT | 14 USDT |
| 5,000–5,999 | 1.50 USDT | 15 USDT |
| 6,000–6,999 | 1.60 USDT | 16 USDT |
| 7,000–7,999 | 1.70 USDT | 17 USDT |
| 8,000–8,749 | 1.80 USDT | 18 USDT |
Your first paid transaction locks your rate for later top-ups. A returning participant uses that locked rate, even if the rate for new participants has risen. There are no referral-based increases to the 10-unit allowance.
The transaction uses the rate read before its execution for all units in that transaction. For example, a new ID buying two units when 999 paid units have been sold pays the current 1 USDT rate for both. The next new ID then sees the higher tier. Exact final proceeds therefore depend on entry sizes and locked-rate top-ups; the pricing table is not a guaranteed fundraising total.
Payment & delivery
Approve the required USDT amount, then execute the mint registration with its expected unit price and quote deadline. Payment and asset delivery happen atomically in the successful registration transaction. If that transaction reverts, its payment and delivery revert together; a separately confirmed approval remains a separate transaction.
The contract distributes exactly 450M QTARDS across the full paid allocation using cumulative integer rounding. Individual deliveries can differ by one token wei, which is 10−18 QTARDS. Ten paid units deliver approximately 514,285.714285 QTARDS and one NFT.
Use the mint flow rather than transferring USDT directly. BNB is needed for network gas, not as the mint payment currency.
4. Free mint
Status: fully claimed. All 1,250 claims have been completed. New post submissions and vouchers are closed. The following describes the completed allocation.
The free allocation contains 1,250 claims of 40,000 QTARDS. Each wallet and each Agent ID may claim once. Confirmed on-chain claims determine first come, first served availability; a submitted post or issued voucher does not reserve a slot.
The participant shares QTARDS on X and provides the post URL to their agent. The agent requests an EIP-712 submission challenge, obtains the user’s signature, and submits the signed entry. The service verifies wallet control and current ownership in the pinned official Agent ID registry before issuing a project-signed claim voucher.
Binance documents its Agent ID as non-transferable and claimed from the associated Agentic Wallet. QTARDS uses that credential and the owner’s signature, rather than trusting a typed .ai name or pasted wallet-status text. The voucher is signed by the QTARDS project service; it is not an endorsement or attestation issued by Binance.
X usernames, post IDs, wallets, and Agent IDs must each be unique. The service normalizes X/Twitter links and rejects duplicates. It does not use the X API, so it does not verify post content, continued public availability, or ownership of the X account.
The free-claim contract verifies the voucher, expiry, current Agent ID ownership, capacity, and prior claim status. A successful claim immediately delivers tokens and adds one combined launch unit. It does not increase paid units sold, change paid pricing, or count toward an NFT bonus. Free claims stop when their allocation fills or registration closes. Check the mint page for current availability.
One wallet may participate in both mint routes if it independently meets their rules. Free mint requires BNB gas but no USDT payment.
5. Tokens & NFTs
Paid tokens are delivered during registration. The NFT is delivered when the same paid Agent ID reaches 10 cumulative units, including top-ups across multiple transactions. No later token or NFT claim is required for the current launch.
The NFT collection is capped at 1,000. Artwork IDs are issued sequentially from 1 to 1,000. Metadata is fixed at deployment, and there are no trait-based reward multipliers or rarity classes. Free claims alone do not receive an NFT.
At most 875 paid participants can complete a 10-unit entry within 8,750 paid units. At least 125 NFTs therefore remain for treasury if the collection is eventually fully issued. More can remain if participants choose partial entries. After a successful launch, anyone can trigger issuance of remaining NFTs to the fixed treasury in batches of up to 50. This collectible allocation is separate from the absence of a team token allocation.
Before trading opens
Receiving an asset does not mean trading has opened. QTARDS token transfers are restricted before successful settlement. NFT transfers are also restricted, except for the designated staking custody path between an NFT’s original wallet and the staking contract. An NFT may be staked immediately after receipt, and the depositor may withdraw it; staking reward claims require a successful launch.
6. Launch & liquidity
The deployer opens registration once. The opening transaction fixes a deadline exactly 48 hours later. The current mint has no admin function for pausing registration, extending that deadline, or withdrawing participant payments.
Success requires all 8,750 paid units and all 1,250 free claims. Reaching 10,000 combined units puts the mint into its sold-out state and stops further entries. A separate, permissionless finalize() transaction settles the launch. Anyone can call it; no owner-only approval is needed.
- Liquidity: 80% of recorded USDT payments and 450M QTARDS are transferred into the official QTARDS/USDT pair.
- Treasury: the remaining 20% of recorded USDT payments is sent to the fixed treasury vault.
- LP: the pair mints the launch LP tokens directly to
0x000000000000000000000000000000000000dEaD. - Trading: token transfers and trading are enabled in the same successful settlement transaction.
Those launch LP tokens are permanently inaccessible; there is no scheduled unlock or owner withdrawal path for them. This locks the liquidity represented by those LP tokens. Pool reserves and market price still change as trades take place; locked LP is not a price floor or a guarantee against loss.
Trading is enabled in the same successful settlement transaction. If settlement reverts, its transfers and activation revert together. A sold-out mint remains eligible for settlement after the deadline; it does not become refundable just because settlement is still pending.
The initial pool ratio is the actual liquidity USDT divided by 450M QTARDS. It is not promised to equal every participant’s entry price. Minting does not continue after the successful launch.
7. Refund protection
If the combined launch allocation does not fill within 48 hours, the original paying wallet can claim 100% of its recorded USDT payment back.
The mint enters its refund state after the deadline when it is not sold out. The payer calls refund(agentId) from the original beneficiary wallet. The contract returns the actual amount recorded for that ID, once, directly to that wallet.
- No token return or token-balance requirement.
- No NFT ownership or return requirement.
- No unstaking requirement.
- No current .ai ownership check for this refund.
- No refund claim expiry.
A refund transaction is required; funds are not automatically pushed to every wallet. Network gas is excluded. Keep access to the original paying wallet, as another address cannot receive its refund.
Free mint has no USDT payment to refund. Participants retain their issued assets after a failed launch, but token transfers and NFT trading remain restricted and staking rewards cannot be claimed. Retaining an asset is not a guarantee of utility or market value.
This protection covers failure to fill the launch allocation. It does not cover losses after a successful launch, USDT depegging, or a smart-contract failure. QTARDS is not a zero-risk investment or a promise of returns.
8. Trading fees & automatic burn
After trading opens, transfers involving the official QTARDS/USDT pair are taxed at 1% for buys and 2% for sells. Regular wallet-to-wallet token transfers are not taxed by this mechanism.
| Destination | Share of tax | Treatment |
|---|---|---|
| Treasury | 40% | QTARDS sent to the converter |
| NFT staking | 30% | QTARDS sent to the staking contract |
| Burn | 30% | Removed from token supply |
These percentages divide the tax collected, not the entire trade. For a 100-QTARDS buy transfer, the 1-QTARDS tax divides into 0.40 for treasury, 0.30 for staking, and 0.30 burned. The recipient receives 99 QTARDS. Tiny amounts are subject to integer rounding; the treasury receives any split remainder.
The burn and token routing execute inside the taxed token transfer. Burns reduce totalSupply() on-chain, and the distribution is recorded in events. Treasury conversion to USDT happens in a separate converter transaction with a positive minimum output and a short deadline. The converter’s own sale into the official pair is exempt from this tax to avoid taxing the conversion again.
Buy and sell rates, the split, and the destination contracts are fixed in this token implementation. This tax applies to the designated pair; it is not a claim that every possible external trading venue is taxed or prevented.
9. NFT staking
The staking contract is directly funded with 50M QTARDS. Every staked NFT has equal weight. A participant must own an eligible QTARD and hold an Agent ID to start staking; NFT approval and the stake transaction are separate actions.
The first valid stake starts the initial 30-day reward period. Its emission rate is the funded budget divided by 30 days, subject to integer rounding. A wallet’s share follows its number of staked NFTs divided by the total actively staked, over time. Rewards are not a fixed APY.
Staking may begin before settlement, but prelaunch accrual is conditional. Rewards become claimable only if the launch succeeds; a failed launch voids them. Withdrawing the NFT remains available to its depositor and does not require a successful launch.
The staking contract receives 30% of taxed trading tokens. After a successful launch and the end of a funded period, anyone can call fundNextPeriod() to start another 30-day period using available funding after existing reward liabilities are reserved. No rewards accrue in gaps between periods. Periods with no NFTs staked do not allocate rewards to a wallet.
An NFT in staking custody must be withdrawn before it can be listed or transferred. The staking contract has no owner withdrawal function for participant deposits or its reward pool.
10. The USDT marketplace
The QTARDS marketplace supports fixed-price listings and purchases in USDT, with BNB used only for gas. Listing and buying require an Agent ID. NFT transfer restrictions mean trades can complete only after successful launch.
A seller approves the marketplace and chooses an NFT and price. Buyers review the current price and listing nonce, approve USDT, and confirm the purchase. Ownership and transfer-version checks reject stale listings, including NFTs moved into and out of staking. A sweep transaction can purchase up to 20 listings atomically.
The marketplace fee is 3% of the sale price. The seller’s remaining 97% is credited as claimable USDT proceeds; the seller calls claimProceeds() to receive it. Marketplace fees are separate from token trading tax and are claimable to the fixed treasury vault through claimFees().
11. Treasury & operations
The treasury receives 20% of recorded USDT payments only after successful settlement. It also receives USDT from treasury-tax conversions, marketplace fees when claimed, and remaining NFTs when issued after a successful launch.
The vault is an operating treasury, not the participant refund escrow or staking pool. Its owner can spend treasury assets and transfer treasury NFTs. Ownership uses a two-step transfer process. Treasury spending is owner-controlled and visible on-chain; it should not be described as ownerless or automatically renounced.
Core launch rules are enforced by the contracts. Registration verifies payment, allowance, price and identity; asset delivery is atomic. The 80/20 settlement split and LP destination are fixed, and taxed transfers execute their split and burn directly.
Settlement, reward-period rollover, marketplace-fee collection, and user claims are executed through transactions. The treasury converter accepts transactions only from its owner or designated keeper; the owner can change that keeper. Software can submit eligible maintenance transactions, while the contracts enforce their conditions. User payments and signatures are always confirmed through the user’s own agent.
The free-mint signer was configured before opening and cannot be changed through its setup function after registration opens. The project’s voucher service remains part of the free-mint process. Its signature cannot bypass the contract’s ownership checks, claim caps or deadline.
12. Contract addresses
BNB Smart Chain, chain ID 56. Use the current deployment for new minting, staking and marketplace actions. The public manifest supplies the current addresses, runtime hashes and ABIs for independent checks.
- QTARDS token
- 0x60e6337CEFacef8DaFe95e7330ec9dF923c14b53 ↗
- Mint & USDT escrow
- 0x3348FF70Ffe2f6C73667718C111824Ec01630c51 ↗
- NFT collection
- 0x7D18C3FA49Bd28fe794bE8d98ED2FdB252555076 ↗
- Free-mint claims
- 0x5072Ac02bAF59BC7C64117317e92a68dE73a680c ↗
- NFT staking
- 0xcd920E8B5051AE569E3FB54680739132226F06D6 ↗
- USDT marketplace
- 0xa2a41E9D23C6F287Fb3D294bA5e527085e95c5C3 ↗
- Treasury vault
- 0x02107015bA2ba41E6Ed95aE9Fe11077FbD24730a ↗
- Treasury tax converter
- 0x1F370857591F604AecE39a8353e6e03EAf731b54 ↗
- QTARDS / USDT pair
- 0xa1732219B706d7Ddb6d5519d6E5D335a985c2B86 ↗
- Payment token · USDT
- 0x55d398326f99059fF775485246999027B3197955 ↗
- Agent ID registry
- 0x60B9262456dE011F7d15a54CdD8c48bAaa8B022F ↗
Contract directory ↗Current deployment manifest ↗On-chain distribution view ↗
Runtime and binding checks are not an independent security audit. The system depends on BNB Chain, USDT, the Agent ID registry, DEX contracts, wallet software, RPC providers, and the voucher service. Failures or compromised keys can interrupt participation or cause losses. Locked LP and refundable escrow address specific mechanics; they do not eliminate these risks.
13. How to participate
- Open the mint page to prepare a mint with USDT. Free mint is fully claimed.
- Copy the prompt into your own agent, using the official Binance Agentic Wallet skill.
- Have the agent verify the current manifest, contract code, Agent ID, phase, price, allowance and availability.
- Review every signature and transaction preview. Confirm each action separately before execution.
- Verify the transaction receipt and asset balances after minting.
The website does not take over the wallet session. Never provide recovery phrases, private keys, or server credentials. Copying a prompt does not authorize a payment, approval, stake, or swap. Wallet balances and personal details should be checked inside your own agent.
The launch UI shows verified on-chain snapshots. A short cache or RPC interruption can delay a displayed number; the contract’s current state determines whether a transaction succeeds. All documented deadlines are UTC.
QTARDS is an independent community project and is not affiliated with or endorsed by Binance. Use of Binance Agentic Wallet or the .ai registry does not imply approval of this project.
Identity reference: Binance Agentic Wallet & Agent ID documentation ↗
14. Earlier registrations
The previous mint uses separate contracts. Earlier payments have not been automatically moved into this launch, and old registrations do not count toward the current launch units.
The old mint address is 0x614f28E367d36c649F20Ee8C80435D4776aeaf34 ↗. If its own launch does not sell out by its deadline, refunds follow that contract’s recorded beneficiary and payment data. Use the dedicated guide and old manifest to check eligibility rather than substituting current-contract addresses.