Air Battle terms of use · Base, BNB Smart Chain and World Chain

1. Operator, scope and acceptance

CMM SMART AI SOLUTIONS LLC, 30 N Gould St Ste N, Sheridan, Wyoming 82801, United States, operates Air Battle. Game support: support@air-battle.com. Corporate contact: support@cmmsmartaisolutions.com.

Launch version 2026-11-20-mainnet-v1. Scheduled effective date: 11/20/2026 at 12:00 PM UTC. Covers separate markets on Base Mainnet, BNB Smart Chain and World Chain. Feature availability is indicated in the application.

2. Age, location and eligibility

You must be at least 18 and meet any higher applicable minimum age. Your age declaration is a user statement and does not replace verification that may be mandatory.

Before accessing the service or committing funds, the user is responsible for checking whether using applications such as Air Battle, paid-entry participation and receiving prizes are lawful in their country, state or territory and satisfy applicable personal restrictions. Users must refrain where they cannot lawfully participate and must not misrepresent their location or bypass controls.

The operator's availability criterion covers countries where the enabled networks and specific products may lawfully be used and where Air Battle may lawfully be offered and played. Users must check country, state or territory restrictions on paid-entry prize play, tokens and their chosen wallet, and abstain where participation is prohibited. Blockchain or RPC access, a wallet account or a VPN does not establish eligibility or universal territorial availability.

Having a wallet, USDC or the BNB token, verifying World ID or living in a provider-served country does not establish permission for paid-entry prize play. User duties do not remove CMM’s applicable obligations, licences or controls. The operator must restrict paid play where prohibited or required permissions are missing.

3. Wallet, network and fund authorization

The account is identified by a wallet. Protect its access methods and check network, token, amount, recipients and calls before approving an operation. A wallet does not establish a unique person.

Each battle uses one network, token, escrow version and entry. Both players must match that market; players on different networks are not matched and their funds are not automatically converted or moved. Planned whole entries are 1, 5 or 10 USDC on Base and World Chain and 1, 5 or 10 units of the token displayed as USDT on BNB. The prize is 90% of the pool and the fee 10%, in that battle's token and network. Calculation precision is 6 decimals for both USDC tokens and 18 for the BNB token.

Signing in and verifying World ID do not authorize deposits. Each fund operation requires separate wallet authorization. Ordinary gas is paid in ETH on Base and World Chain and BNB on BNB Smart Chain. Coinbase sponsorship is limited to a compatible native connection on Base and World App sponsorship to its native World Chain flow; both depend on activation, eligibility, limits and verified availability. Their HTTPS tests are currently pending. The app must show the effective mode before confirmation; it never silently switches to self-paid gas or promises free gas merely for selecting a network or verifying World ID.

4. Rules and authoritative game state

Each player deploys three non-overlapping ten-cell planes on a 10 × 10 board. Body hits grant another shot; an Empty cell passes the turn; nose hits destroy a plane. Destroying all three wins, unless deadlines resolve the battle.

The current configuration allows 30 seconds for readiness, 180 for funding, 30 for rock-paper-scissors initiative, 60 for deployment and 20 per turn. Three missed turns accumulated across the entire battle cause defeat, even if they are not consecutive. If only one player deploys in time, that player wins; if neither does, there is no winner.

In rock-paper-scissors, a tie gives initiative to the first commitment recorded by the server. If only one player reveals before the deadline, they get initiative; if neither reveals, the battle ends without a winner. The secret choice is stored in the originating tab and must remain available for timely reveal.

The server and database record valid moves and the result; the contract executes supported authorized operations. Closing a browser, losing connection or changing devices does not pause deadlines. Presence alone does not determine the winner.

Up to three simultaneous gameplay slots are allowed per wallet across tabs and markets. A pending prize does not occupy a slot. Collusion to simulate activity, result manipulation, unauthorized data access, exploit use and false invitations to obtain rewards are prohibited. Reviews must be based on records and respect applicable rights; an incident alone does not authorize fund confiscation.

5. Fee, result and payments

The agreed fee is 10% of the total pool and the winner receives 90%. With 5 USDC per player, the pool is 10 USDC, the total prize is 9 USDC including the winner’s entry, and the fee is 1 USDC. The winner’s net gain in that example is 4 USDC before gas and any applicable taxes. Entry recovery or profitability is not promised.

After a winner is durably recorded, the winner must select Claim prize and confirm in their wallet. The backend signs result authorization but does not submit the transaction. The contract transfers prize and fee in the same operation. Submission is distinct from confirmed payment, and the interface distinguishes them.

Game fees and gas are distinct. The effective available gas mode is shown before each deposit, claim or refund operation. In self-paid mode, the sender pays in that network's native currency. A rejected sponsorship does not trigger an automatic player-paid submission: any alternative requires a new choice and authorization. A failed transaction may consume gas; returning an entry does not automatically return gas or third-party costs.

The loser's browser closure does not condition payment. A pending prize does not occupy either player's game slots. The winner may return to claim later without accepting newer terms.

6. Cancellation, refunds and failures

Before funding, rooms may be cancelled according to their state. With one deposit, its owner may request a refund after the battle's funding window. The window is 180 seconds from the start of the server funding phase. Its absolute end is signed as fundingDeadline and stored by the contract with the first deposit: that deposit does not restart the window. A single-deposit refund is available from fundingDeadline + 1 second according to block time. Confirmation and the screen update may be delayed. The effective state is shown before preparing the operation. No opponent signature or refund game fee is required.

A joint refund requires valid no-winner cancellation and escrow authorization. Either participant may submit it, returning both entries without a game fee or another opponent signature. The displayed gas mode applies. Elapsed hours or absence of a visible onchain result do not erase a server-recorded victory.

Network, provider, server or recovery failures can delay operations. Total loss of authoritative data may require operational intervention and has no universal recovery guarantee. The operator cannot erase public blockchain records. Production backups on the same VPS are not an isolated offsite copy against total loss of that VPS.

Battle funds are held by the specified contract, subject to its rules and the administrative powers published in its code. The operator authorizes results and may apply supported pauses; escrow does not remove server dependence or risks from contract bugs, lost wallet access or provider outages. No return or deposit insurance is offered. Tokens may lose value or liquidity even when described as stable. Verify network and token address; a confirmed operation cannot be undone from the web.

You must meet any applicable tax duties; the operator retains its own legal obligations. Test networks are identified on screen: their tokens have no economic value and must not be confused with mainnet funds.

Any legal cancellation or termination rights and mandatory protections are handled under applicable rules. Acceptance does not require a blanket consumer-rights waiver.

7. Earn, profiles and standings

Earn requires acceptance of each campaign's rules version. Requirements, budget, deadlines and review apply; a claim does not establish a transfer. Campaigns do not turn battles into an investment or guarantee income. Campaign funds are managed separately from escrow. Invitations must clearly disclose any potential reward for the inviter; accepting a code does not by itself grant a reward to the invitee.

The leaderboard is informational, grants no automatic rewards and uses wins from eligible battles with confirmed payouts. Publication is optional and can be hidden in My profile.

Existing participation retains its accepted terms reference. A general update does not by itself condition a refund or a reward already generated under earlier rules.

8. Reports, changes and mandatory rules

Report an issue from battle history or write to support@air-battle.com. The form associates a verified wallet and battle and requests name, email, phone, category, subject and a 250–5000 character description. Provide only necessary information and never send keys, recovery phrases, access codes, photos or unnecessary sensitive information. Support commits to replying to the supplied email within 48 business hours; that reply does not mean the issue or payment will be resolved in that same period and does not limit mandatory rights or statutory time limits.

Material changes receive a new version and require acceptance before new participation. They do not retroactively change amounts, winners or existing rights.

No provision excludes liabilities or rights that cannot lawfully be excluded. Mandatory rules, applicable law and competent forums depend on the circumstances; no general waiver of local consumer protection is imposed.

9. Service risks and warranties

Battles carry a real possibility of losing the entry through a valid result. Accepting that risk does not mean accepting settlement contrary to the rules or loss caused by an operator breach.

To the extent permitted by law, the service is offered according to its published features and availability, without promising uninterrupted access, absolute freedom from faults, profit, dollar parity of a token, direct redemption or suitability for a particular economic objective. Legally required warranties and duties of care, security and remediation remain applicable.

Risks include internet outages, blockchain delays or reorganizations, fee changes, RPC, wallet or authentication failures, vulnerabilities and token issuer actions affecting transfers or value. Listing these risks does not release the operator from its own breaches or duties it retains regarding providers.

Keep devices, passkeys, wallets and recovery methods secure. Check the domain and instructions before signing and report suspicious access. Responsibility for an operation is not automatically assigned to the user merely because a wallet signed it; established causes and applicable law will be considered.

10. Scope of liability

CMM SMART AI SOLUTIONS LLC does not assume losses caused exclusively by a valid gameplay choice, instructions or access under the user's control, token fluctuations or third-party events outside its reasonable control, provided there is no breach or legally attributable responsibility of the operator. Where multiple causes contribute, responsibility is allocated under applicable rules; backend, contract and provider failures are not all shifted to the player.

Only where such an agreement is legally valid, compensation for indirect or consequential losses and unguaranteed profit expectations or opportunities is excluded. Naming a category of loss does not restrict a consumer remedy provided by law. Loss, causation and any duty to mitigate are assessed under applicable law; there is no blanket waiver of claims or automatic monetary liability cap for consumers.

These exclusions do not affect payment, delivery or return of entries, prizes and rewards due under the contract and accepted rules. They do not authorize fund confiscation or erasure of a victory, and do not turn collected fees into a cap on funds that must be delivered or restored.

Liability is not excluded or limited for fraud, intentional wrongdoing, deliberate misconduct, gross negligence, death or personal injury, or for data protection, security, consumer or other duties to the extent they cannot lawfully be excluded or limited. Nothing prevents access to competent authorities or courts, human review or exercise of other non-waivable rights and remedies. An invalid term will not be applied or unilaterally replaced by another waiver.

11. Maintenance, treasury and historical contracts

The production escrow treasury address is fixed at deployment and cannot be changed afterward. To use a different treasury, the operator must schedule maintenance, close new entries, handle active battles and deploy another escrow with its corresponding configuration.

The previous contract remains bound to battles funded in it. The change does not automatically migrate funds, change their recipients or extinguish pending prize or refund rights. Records and the support and claim or refund route applicable to the original contract will be retained; new terms will not be required merely to exercise existing rights.

Notice of maintenance and its effects will be given where possible. An urgent incident may require contract-supported pauses and proportionate security measures. Maintenance, an investigation, account suspension or service closure does not itself authorize appropriation of funds. Claims and any legally required restitution or compensation will be addressed under the rules and applicable law.

The 13 November 2026 reading of all three escrows identifies owner 0x2b702c57B3DC51b0de2b27b1D7F4ac4FEF8491e4, guardian 0x0B26E4Bc50412B4b868d5C9F98ccCd390a5c63A1, authorized signer 0x32Fc5aa5746A1e55a8f09DBcd53100a9EA596D4c and treasury 0x362aB82506A1fC66D3cc648fc40E037ea0688102. The owner manages the contract pauses and the guardian can trigger an emergency pause; the guardian cannot reopen alone. Expired single-deposit refunds remain available during these pauses. Results depend on the server arbiter: escrow does not mean decentralized arbitration or removal of trust in the operator. Check current roles on each network; changeable roles may change under the code.

12. Providers and applicable terms

In addition to these Air Battle terms, you must comply with applicable terms and restrictions of services you actually use. For Coinbase Wallet or its passkey account: https://wallet.coinbase.com/terms-of-service. Holding an account or using the Coinbase exchange is a separate service; this document does not make a MetaMask or other wallet user accept an exchange contract for a service they do not use.

CMM must comply with the Coinbase products it actually integrates: https://www.coinbase.com/legal/developer-platform/terms-of-service and https://www.coinbase.com/legal/prohibited_use. That policy requires prior written consent for certain paid-entry prize skill games; Air Battle does not claim to have it. Applicability to each product and trial must be resolved before offering that flow. Self-paid gas or an HTTPS URL does not replace that approval.

USDC use is subject to the Circle terms applicable to your location and type of use: outside the EEA, https://www.circle.com/legal/usdc-terms; for the EEA, see https://www.circle.com/legal/mica-usdc-whitepaper and, for relevant services, https://www.circle.com/legal/eea-terms. Restrictions at https://www.circle.com/legal/acceptable-use-policy are also relevant. Holding USDC does not mean having a Circle Mint account or guarantee direct redemption with Circle without meeting its requirements.

Reown connection is subject to its terms at https://reown.com/terms-of-service, as well as the chosen wallet's terms. A wallet connection is not automatically identified with WalletConnect Pay; if that product is introduced, its applicable terms at https://walletconnect.com/terms will be disclosed before use. Business SDK licensing, subscription or authorization obligations belong to CMM where applicable.

The acceptance recorded by Air Battle establishes only the version of our own packet. It does not establish separate acceptance on behalf of Coinbase, Circle, Reown, WalletConnect or your wallet; each provider manages its own applicable contracting. Review the provider's current terms when using its service. Changes to third-party terms do not themselves change rights already generated against CMM or automatically incorporate every future term into our relationship.

Technical integration, a link, a license or acceptance does not imply affiliation, representation, guarantee or regulatory approval of Air Battle by those providers. CMM's own responsibilities and mandatory rights remain. A provider restriction may affect new functionality but does not itself authorize erasure of pending rights or appropriation of funds.

World ID and World App have distinct terms and roles. See https://world.org/legal/user-terms-and-conditions and the notices shown by World App; distribution review follows https://docs.world.org/mini-apps/guidelines/policy. The operator must check the developer agreement accepted in the portal and Tools for Humanity terms applicable to the specific wallet. A private HTTPS trial is not an approved public Mini App.

13. Training modes

Target practice runs locally in the browser: select and confirm shots without connecting a wallet. The bot simulator lets you deploy your fleet and play a complete battle with no entry, prize, gas or turn clock. It requires connecting and signing in with a wallet; that signature authenticates the session and does not authorize fund movements.

The simulator may be disabled for new starts, have a daily limit per wallet address or allow unlimited starts. The available allowance and its reset at 00:00 UTC are shown before starting. The same allowance applies across networks, tabs and devices. A person with several addresses may have several allowances; a wallet does not establish a unique person.

Starting consumes one battle from that day’s allowance, even if you end it early. Resuming the same battle does not consume another. Only one active battle is retained per wallet. Disabling new starts allows existing battles to continue, subject to expiry or an incident preventing service.

These battles do not enter competitive history, profile statistics, the leaderboard or Earn campaigns, and generate no payments or rewards. The bot uses information its shots have discovered and the public rules; it does not inspect your hidden formation to choose a target. Difficulty is selected before starting.

You may close the simulator and resume with the same wallet. Your formation is saved on the server only when confirmed; a deployment draft in one tab does not transfer to another device. The saved board is deleted on completion; a battle with no moves for 7 days expires as described in the privacy policy. Technical start records enforce the allowance and prevent repeated starts, rather than recording results.

14. Base Mainnet appendix · USDC

Base Mainnet, chain ID 8453. Native Circle USDC: 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913, 6 decimals. Escrow: 0xa14D3273553E836e47f1d9E73873e524ab30729f. Ordinary gas in ETH. Explorer: https://basescan.org/address/0xa14D3273553E836e47f1d9E73873e524ab30729f.

Do not send another network’s USDC to this battle. Coinbase sponsorship requires a compatible flow and verified per-operation availability; the Paymaster callback must be HTTPS and reachable by the wallet service. An HTTP localhost callback is unsuitable. Coinbase terms and permissions are assessed by product, not merely the selected network.

15. BNB Smart Chain appendix · Binance-Peg token

BNB Smart Chain, chain ID 56. Token: 0x55d398326f99059fF775485246999027B3197955, 18 decimals, displayed as USDT in the game and identified as Binance-Peg BSC-USD on BscScan. Escrow: 0xa14D3273553E836e47f1d9E73873e524ab30729f. The user pays gas in BNB. Explorer: https://bscscan.com/token/0x55d398326f99059fF775485246999027B3197955.

This Binance-Peg token has backing, custody and counterparty risks in addition to reference-asset risks. It is not USDC and is not represented as native Tether issuance on BNB with universal direct redemption rights. The USDT symbol alone does not establish issuer, reserves or user rights. Check terms for the acquisition/redemption route, https://tether.to/en/legal/, supported protocols https://tether.to/en/supported-protocols/ and collateral information https://www.binance.com/en/proof-of-collateral. A reserves link does not establish an audit or backing verification for this version.

16. World Chain appendix · USDC and World App

World Chain, chain ID 480. Native Circle USDC: 0x79A02482A880bCE3F13e09Da970dC34db4CD24d1, 6 decimals. Escrow: 0xa14D3273553E836e47f1d9E73873e524ab30729f. Ordinary gas in ETH. Explorer: https://worldscan.org/address/0xa14D3273553E836e47f1d9E73873e524ab30729f. Official USDC addresses: https://developers.circle.com/stablecoins/usdc-contract-addresses.

World ID is an optional human proof, not access to funds, age verification or residency. WalletAuth access and native transaction submission are separate World App features. World App gas coverage depends on eligibility, limits, allowed contracts/tokens and native flow availability. A local World ID test does not establish native transaction integration or sponsorship. Where sponsorship is not enabled, self-paid gas is available only through a compatible wallet and submission flow expressly chosen by the user.

17. Network and funds separation

Although all three networks use the same escrow address, contracts and balances are independent for each chain ID. A wallet may use the same address on different networks without shared balances. There is no cross-network matching, bridge or automatic conversion. An incorrect token or direct transfer outside the deposit flow may be unrecoverable; contact support without sharing secrets.