Baby AI / BBAI Whitepaper

Download whitepaper (PDF). This page is the web version.

Ethereum Mainnet · Active presale; purchase availability follows current contract state

Revised October 28, 2026. Allocation targets approved October 23, 2026; existing commitments, reserve release terms and operational signing controls remain under review. Historical evidence retains its stated dates. Technical evidence in the body records the October 1, 2026 verification snapshot, with a dated October 17 treasury disclosure. Contract availability and balances can change. The October 17 read-only snapshot confirmed the presale was paused; no scheduled date automatically opens purchases.

Token: 0x0cEC9423A7Ea56c920191D33a6511a141BC5ba93
Presale: 0x9d16af7a8c7fd522e904038ce37b5447c91bd900

Project phase: BBAI is in its active presale phase. Public exchange trading has not launched, and the project has not authorized the creation of a Uniswap liquidity pool. Trading and liquidity information will be published when available. Presale purchases are not exchange trading volume.

1. Executive summary

BBAI is the native token of the Baby AI ecosystem. Additional utility for Baby AI World, including eligible in-game features and digital items, is planned for future release. Its deployed Web3 foundation consists of:

• the fixed-supply BBAI ERC-20 token on Ethereum Mainnet;
• a deployed, inventory-backed Mainnet Presale contract that accepts ETH or canonical Ethereum USDC;
• a non-custodial web application in which users connect an external wallet and approve their own transactions; and
• planned token utilities, including staking and Baby AI World token-based features, which are separate from the deployed presale and existing browser activities.

The Mainnet Presale uses fifteen fixed-price stages and can distribute at most 1,000,000,000 BBAI, including a capped Stage 1 bonus. Successful purchases deliver BBAI directly to the buyer in the same transaction. There is no presale claim balance or later claim step in the authoritative Mainnet contract.

The Presale contract is deployed and fully source-verified on Blockscout. The exact evidence and repository reconciliation are recorded in BBAI-MAINNET-DEPLOYMENT-VERIFICATION-REPORT.md.

NO INDEPENDENT AUDIT REPORT FOUND. Internal reviews, automated tests, Mainnet-fork tests, regression tests, and application QA are described in this document, but none is represented as an independent third-party audit.

2. Purpose and principles

The Baby AI product direction is to make emerging AI and Web3 tools more understandable, useful, and human-centered. Current project materials identify four guiding themes:

1. Children and learning: encourage curiosity, education, and safe exploration.

2. Families and support: favor clear interfaces and approachable information.

3. Community: connect progress to transparent milestones and responsible participation.

4. Long-term impact: develop deliberately rather than promising utility that is not yet available.

These themes are product goals, not guarantees of investment value, adoption, revenue, or future functionality.

3. Current system architecture

The current Mainnet system separates user custody, application coordination, and settlement:

1. A user connects a compatible external wallet through an injected provider or WalletConnect-compatible session.

2. The application checks the selected account, Ethereum Mainnet chain, contract state, and purchase readiness.

3. The application obtains a contract quote and presents a confirmation step.

4. The user reviews and signs the transaction in the user's wallet.

5. Ethereum executes the Presale contract.

6. A successful purchase transfers BBAI directly from Presale inventory to the buyer and emits an indexed Purchase event.

7. The application waits for an on-chain receipt before presenting a confirmed allocation.

The website does not need the user's private key or seed phrase. Signing authority remains with the connected wallet. Baby AI support should never request a seed phrase, recovery phrase, private key, or wallet password.

The application and its backend helpers are not a substitute for Ethereum consensus. On-chain contract state and transaction receipts are authoritative for purchases and allocations.

4. BBAI token

4.1 Verified Mainnet identity

Read-only Ethereum calls and Blockscout verification establish the following token facts:

Blockscout reports the token contract as fully source-verified. Its verified source is named BabyAi.sol. Repository token examples with different names or source layouts are not the authority for the already-deployed token; the deployed address and its verified on-chain behavior are authoritative.

5. Mainnet Presale

5.1 Deployment identity

Blockscout reports the contract as fully verified. On October 1, 2026, an independent Ethereum RPC read returned 12,007 bytes of runtime code with Keccak-256 hash 0x489665cdb6bd27d0cc98e6f8ea404e184a7b027a66ab1afb8f652cf8b855fae6; Blockscout returned the exact same deployed bytecode and hash.

5.2 Immutable dependencies

The contract is restricted to chain ID 1 and pins these dependencies:

Circle lists the USDC address as canonical Ethereum Mainnet USDC. Chainlink lists the ETH/USD feed address for Ethereum Mainnet.

5.3 Fixed stage economics

The Presale uses token-inventory boundaries rather than dates to advance through fifteen stages. One purchase may cross multiple stage boundaries. Prices and base allocations are immutable in the deployed contract.

Stage 1 awards a cumulative 10% bonus on its base fills, bounded by the 5,000,000 BBAI bonus cap. No bonus exists in Stages 2–15.

The minimum purchase is $10.00 in the contract's six-decimal USD accounting units. The contract does not implement a per-wallet maximum, allowlist, vesting schedule, or price-changing administrator function.

5.4 ETH purchase flow

buyWithETH() is the only supported ETH purchase entry point. Plain ETH sent to receive() or fallback() is rejected.

For an ETH purchase, the contract:

1. requires the sale to be active and not paused;

2. validates a positive, complete, nonfuture Chainlink ETH/USD round no older than the immutable maximum age;

3. converts the offered wei to six-decimal USD units;

4. allocates available inventory across one or more stages;

5. calculates the ETH actually required;

6. updates accounting before external transfers;

7. transfers BBAI directly to the buyer;

8. refunds unused ETH when the offered value exceeds the fill; and

9. emits a Purchase event.

The deployed oracle maximum age is 7,200 seconds. A stale or invalid oracle response causes the purchase to revert.

5.5 USDC approval and purchase flow

USDC purchases use the standard ERC-20 allowance model and normally require two user-authorized transactions:

1. Approval: the user authorizes the Presale contract to spend a selected amount of USDC. Approval alone does not purchase BBAI.

2. Purchase: the user calls buyWithUSDC(maximumUsdcAmount) through the application and confirms the final transaction.

The contract calculates the actual USDC needed for the available fill and calls SafeERC20.safeTransferFrom. It compares the contract's USDC balance before and after the transfer and reverts if the exact expected amount was not received. It then transfers BBAI directly to the buyer and emits a Purchase event.

USDC is accounted as one USDC equal to one USD; the Presale does not use a USDC/USD oracle. If USDC materially depegs under project policy, the documented response is to pause both purchase rails and independently verify the paused state before considering a resume.

6. Custody and wallet behavior

BabyAiWallet.com operates as a connection and transaction interface, not as a custodian of user wallet keys.

• Users connect an external wallet.
• Transaction signing occurs in that wallet.
• The application must not request or store seed phrases or private keys.
• Wallet connection does not transfer assets by itself.
• A USDC approval authorizes the Presale contract as spender up to the approved allowance; it is distinct from the final purchase.
• Ethereum gas fees are separate from the ETH or USDC purchase amount.
• Users should verify the network, contract address, method, asset, amount, and allowance in their wallet before signing.

The current application contains routes for injected providers and WalletConnect-compatible mobile/QR sessions. It validates provider identity, connected account, Mainnet chain, contract pause/finalization/sold-out state, quotes, and receipts. Compatibility and availability can vary by wallet, browser, device, and wallet-provider service.

7. Contract security design

The Presale source uses OpenZeppelin Ownable2Step, Pausable, ReentrancyGuard, SafeERC20, and Math components. The custom contract adds the following controls and invariants:

• deployment is rejected outside Ethereum Mainnet;
• BBAI, USDC, and ETH/USD feed addresses are fixed;
• dependency decimals are checked in the constructor;
• stage prices, allocations, total caps, and payment assets cannot be changed by the owner;
• the contract deploys paused;
• purchase and withdrawal entry points use reentrancy protection;
• accounting is updated before token delivery and ETH refund interactions;
• inventory is checked before allocation;
• received and delivered token amounts are measured;
• direct ETH transfers are rejected;
• ownership transfer requires acceptance by the proposed owner;
• ownership renunciation is disabled;
• treasury rotation requires proposal and acceptance;
• finalization is irreversible and blocks later purchases; and
• BBAI recovery is unavailable until finalization or sellout and can only send remaining inventory to the treasury.

7.1 Administrative authority

The owner can pause, resume, permanently finalize, initiate two-step ownership transfer, propose a treasury change, recover unrelated tokens, and recover eligible unsold BBAI. The treasury can withdraw collected ETH and USDC. Withdrawals remain available while paused and after finalization.

At the October 1, 2026 verification snapshot, the owner and treasury resolved to the same externally owned account. The deployed contract does not itself enforce a multisignature wallet or timelock. This is a material operational and key-management risk even though contract-level transfer and recovery destinations are constrained.

7.2 Emergency controls

Pausing blocks both ETH and USDC purchases. The application reads paused(), finalized(), and sold-out state and is designed to fail closed when authoritative contract status cannot be established. Operational documentation requires an on-chain confirmation of paused() == true during a USDC depeg response.

8. Testing and assurance

Repository records describe the following internal work on the authoritative Mainnet Presale candidate:

• 51 passing dedicated candidate tests;
• 1 passing wrong-chain test;
• 64 passing local regression tests, with one opt-in fork test skipped in that profile;
• 1 passing Mainnet-fork profile; and
• 65 unique automated contract test cases passing in their applicable profiles.

Recorded coverage includes stage and cap arithmetic, ETH and USDC purchases, allowance behavior, complete stage traversal, mixed buyers and payment rails, minimum purchases, final-unit exhaustion, refunds, token-delivery rollback, oracle failures and staleness, pause/resume/finalize interactions, two-step ownership and treasury behavior, recovery restrictions, reentrancy attempts, and gas bounds.

The local Mainnet-fork test checked the deployed BBAI, USDC, and Chainlink dependencies and deployed the Presale candidate only inside the local fork. It did not broadcast a Mainnet transaction or move real funds.

Application QA covers wallet routing, two-step confirmation behavior, pause authority, stage/bonus presentation, holder-status presentation, storage isolation, mobile routing, and receipt-driven allocation display. Some QA artifacts are local records rather than tracked, immutable release evidence, and an older local UI report recorded blocked third-party stylesheets under its Content Security Policy.

NO INDEPENDENT AUDIT REPORT FOUND. These internal activities do not constitute an independent third-party security audit, certification, guarantee, or proof that the contracts or application are free of vulnerabilities.

9. Deployment and source verification

Repository documentation created before deployment still says “prepared, not deployed,” while later configuration and the deployment manifest include the live address. That historical conflict has been reconciled against independent evidence:

• Blockscout records a successful contract-creation transaction at block 26,018,778.
• Independent Ethereum RPC reads return deployed runtime code and callable Presale state at the address.
• Blockscout reports is_verified: true and is_fully_verified: true.
• Blockscout's published BBAIMainnetPresale.sol is an exact byte-for-byte match to onchain/contracts/BBAIMainnetPresale.sol in this repository.
• Blockscout's deployed bytecode is an exact byte-for-byte match to independent Ethereum RPC bytecode.
• The verified compiler, optimizer, and EVM settings match the release configuration.

Accordingly, it is accurate to state that the deployed Mainnet Presale source is fully verified on Blockscout. A read-only check on October 5, 2026 also confirmed source-verification markers on both Mainnet Etherscan contract pages.

The repository's recorded runtime hash 0x2cecf7…7036 is the compiler runtime template before constructor-set immutable values are patched. The deployed runtime hash is 0x489665…fae6. The repository creation artifact also differs from the explorer creation init code in its metadata suffix, although the authoritative top-level source matches exactly and Blockscout fully verifies the complete deployment. These distinctions are documented rather than concealed.

10. Product status and roadmap

Current project materials describe:

• Home and ecosystem presentation: active;
• Mainnet Presale: deployed, with purchase availability governed by on-chain state;
• community and support surfaces: active or under continuing development;
• governance voting: planned and not live; no current eligibility, quorum or proposal-execution rights are established;
• staking: planned and not currently available;
• Baby AI World: browser activities are available separately; additional BBAI token utility is planned and is not currently live; and
• previously scheduled ecosystem milestone: October 25, 2026; this date does not establish exchange trading or completion of planned features.

Roadmap dates and planned features may change. Future staking, rewards, educational experiences, integrations, merchandise, games, or other utilities require separate implementation, testing, authorization, and public documentation. Holding BBAI does not by itself guarantee access to a future feature or any particular economic return.

11. Risks and limitations

Participation involves substantial risk, including:

• smart-contract defects or unanticipated interactions;
• absence of an independent third-party audit;
• owner and treasury key compromise or misuse;
• reliance on a single externally owned administrative account at the verification snapshot;
• ETH/USD oracle failure, delay, or staleness;
• USDC depeg, issuer, blacklist, or smart-contract risk;
• wallet, provider, browser, WalletConnect, RPC, or frontend failure;
• phishing, malicious approvals, address substitution, or user signing error;
• Ethereum congestion, transaction failure, reorganization, or high gas fees;
• token-price volatility and lack of liquidity;
• regulatory, tax, sanctions, or jurisdictional changes;
• roadmap delay, modification, or cancellation; and
• unreconciled private commitments and undecided reserve release terms for the 90% of BBAI supply outside the Presale cap.

The Presale contract is not upgradeable. A defect in immutable logic or configuration cannot be patched in place; the available immediate response is to pause or finalize according to authorized procedures.

12. No financial, legal, or tax advice

BBAI is a digital token with market, technology, operational, and regulatory risk. Nothing in this document promises profit, appreciation, liquidity, income, rewards, or completion of future products. This document is technical and informational only and is not financial, investment, legal, accounting, or tax advice. Prospective participants should conduct independent research, review the verified contracts, evaluate their jurisdiction, and consult qualified advisers where appropriate.

Founder

Christopher Munoz — Founder & CEO, Baby AI

Baby AI was founded independently by Christopher Munoz as its sole founder. The project was inspired by his daughter and his younger brother, Ish.

Read Our Story — Built With Purpose.

Christopher Munoz on LinkedIn.

Official project contact

Support and legal enquiries: legal@babyaiwallet.com.

Official project channels

BabyAiWallet.com · X @babyaiweb3 · Baby AI Discord · Instagram · Support

No independent third-party audit is claimed. The shared tokenomics section records approved targets, dated custody observations and unresolved commitments and release conditions. Approval does not establish token transfers, vesting, staking or a certified circulating supply.