# Agentic 404 Network — public project facts Independent project. Prelaunch. No official token/NFT contract, mint, reward claim, pool or LP lock is live. Official website: https://agentic404.xyz Official X: https://x.com/agentic404 Registration: https://agentic404.xyz/whitelist Topics: Agentic 404 Network, 404 Strays, DN404, BNB Chain, NFT, .ai Agent ID, genesis whitelist. Agentic scope: Agent ID-based access design. Ownership integration is pending. No live autonomous trading agent is claimed. No participant records, developer wallet, account credentials or personal contact details are published in this resource. These project-authored statements describe a proposed design, not a third-party audit, listing endorsement or investment guarantee. ## Genesis whitelist First valid registrations. Clear lanes. No referral shortcuts. ### How the queue works The queue follows the order of successful server-side registration saves. New entries receive a unique queue number atomically in the database. Opening the page, starting a browser check, posting an X reply or sending a request does not reserve a position. Device clocks and network request start times do not determine rank. Your receipt shows a provisional registration number and range. Final valid rank is determined by reviewing entries in that original order and excluding invalid or duplicate applicants. Verification processing speed does not give priority. Earlier valid entries remain ahead of later valid entries; a number is not a transferable mint allocation. Existing website registrations retain their saved order and original rules version; they are not retroactively invalidated solely for missing newly added task confirmations. Older entries without an atomic number use their original saved timestamp order, with the existing database order resolving equal timestamps. They are not reset by this update. Original X replies have not been imported; complete the website form to join the queue. ### The access lanes Final valid positions 1–1,000: GTD access to two free mints per verified Agent ID, reserved only during the published GTD window. This lane represents 2,000 planned NFT units. Gas applies. Final valid positions 1,001–3,333: FCFS eligibility for one free mint per verified Agent ID, subject to the published mint window, successful transaction inclusion and available inventory. This lane represents 2,333 planned NFT units. One identity cannot use both free lanes. Gas applies. New intake stops at 3,333 registrations. There is no new 10,000-entry reserve campaign. Existing records are not deleted by a policy update. If verification excludes entries, any reopening or replacement process must be announced, preserving earlier valid priority. Unclaimed mint slots are not automatically rolled over. The intake accepts up to 3,333 registrations, matching the planned Agent ID count rather than the entire 7,777-NFT unit capacity. The live Open/Full counter measures saved applications, not verified owners or minted NFTs. There are 3,333 planned Agent ID allocations and 4,333 planned free mints in total. Registration does not mint an NFT. Free claims are conditional on a successfully funded launch. The proposed paid-reservation period is seven days with a one-day activation grace period; GTD has 24 hours after activation and FCFS the following 24 hours. No exact registration, snapshot, verification or mint dates have been announced; dates will be published in UTC before the relevant window. ### What makes an entry valid Use an existing .ai Agent ID you control and your own X username. Submit one entry per person, using one Agent ID and one X account. Format checks and duplicate-name checks run now; ownership, X-account control and person-level eligibility are still pending review. Ownership evidence, the verification window and a correction/dispute process must be published before final ranking. An unverified name submission does not reserve that name or establish ownership. False ownership claims, related duplicate accounts, self-referrals, fabricated proof and automation used to evade entry limits can be excluded, with a reason and an opportunity to raise a dispute before final allocation. Referrals are optional and do not affect validity. For new submissions, required social-task confirmations and the public post link are reviewed under the rules recorded at submission; completing them does not prove ownership. A confirmed mint allocation requires the ownership and eligibility checks. Mint, token trading, rewards and the game are not live. ### No pay-to-skip or referral priority New registrations require opening all four X task links, confirming follow, like, repost and share, supplying a public project-share post URL from the submitted X username, and accepting the registration terms. The form stays disabled until every required step is completed. X actions and account control are self-reported and pending review, not automatically verified by a link click. Referrals record introductions only. Referral counts, follower counts, paid promotion, DMs and collaboration requests do not move an entry forward or buy a spot. The GTD, FCFS and public lanes have no different per-NFT rarity treatment. Registration needs no wallet connection, payment or seed phrase. Keep the private receipt token private; use the separate referral link if you want to share the project. ## Official token status No official AN404 token contract has been deployed. Registration is the only live project flow. ### Current status Agentic 404 Network has not deployed or launched an official AN404 token or 404 Strays NFT contract. No official mainnet or testnet contract address is being published here. A trading token with the same name, symbol or artwork is not proof of project affiliation. Local contract drafts are under development and owner review. They are excluded from the website deployment. A verified explorer source page or a listing badge alone is not an audit or proof that a token belongs to this project. ### How official addresses will be identified After review and an explicitly approved deployment, the project will publish the network, full ERC-20 contract address, linked ERC-721 mirror, explorer links and authority/fee details on this website and the official @agentic404 account. Addresses must match across these official sources. The proposed mainnet is BNB Smart Chain, chain ID 56. Tickers are copyable metadata; AN404 cannot be exclusively reserved through an ERC-20 deployment. Do not identify this project by a ticker search, a DM or an unconfirmed trading pair. ### Fees and launch prerequisites The current proposed service fees are 5% in USDT on settled project NFT marketplace sales and 2.5% on the project token swap route. Ordinary AN404 transfers have no project transfer tax. External DEX transactions do not automatically pay the project routing fee. Public mint is being designed for a reviewed standard stablecoin on BNB; the exact asset/address has not been finalized. LP custody, sale/refund terms, identity/history verification, rarity reveal and independent security review remain required before a funded launch. No token sale, reward claim or LP lock is live. ## Funding, refunds & LP lock Proposed launch rules for review. No paid reservation, mint, pool or LP lock is live. ### Why a funding minimum? The launch needs the paired USDT side of its liquidity pool. The proposed all-or-refund target is the full 1,890-unit public allocation: 10,350 nominal USDT, with prices increasing from 1.00 by 0.50 every 100 paid reservations. This is a funding condition, not a sales forecast or guaranteed token price. Public payments stay in sale escrow for a seven-day funding window. Reservations record units and paid USDT but deliver no AN404 or NFT before successful activation. Exact UTC dates, addresses and final reviewed terms must be published before funding opens. ### Success: permanent LP plus a public-mint rebate After all 1,890 public units are reserved, anyone may trigger activation within the published deadline. 70% of receipts, 7,245 nominal USDT, pairs with the separate 78.741M-AN404 LP reserve in a fresh reviewed V2-style pool. Activation must succeed atomically. All LP tokens minted to this protocol position go directly to a custody contract with no owner, unlock, transfer, approval, arbitrary call or rescue function. The proposed lock is permanent. V2 LP fees compound in the locked pool; they are not withdrawable developer income under this design. The other 30%, 3,105 nominal USDT, remains in sale escrow for a deterministic rebate to public minters. Each successful public claim receives its reserved linked units and 30% of that wallet’s paid USDT. This replaces the earlier unspecified community-cash use. There is no personal developer share of mint receipts. The rebate is separate from finite secondary-trade AN404 cashback. If the entire 78.741M token reserve is paired with 7,245 USDT in an empty pool, the initial ratio is about 0.00009201053 USDT per AN404. That ratio is not a floor, redemption right or promise that holders can sell at it. Trading changes reserves and price; USDT also has issuer and price risks. ### Failure: paid reservations can claim a full USDT refund If the funding target is not reached by the end of seven days, paid participants may claim their original USDT payment back. If funding is complete but LP activation cannot succeed within the additional 24-hour grace period, refunds become available instead. No token/NFT delivery has occurred before activation, so a refund does not require surrendering an NFT. Refunds return the recorded payment, excluding blockchain gas. They are claimed by the paying wallet and cannot also be claimed after successful activation. The local design has no owner cash-withdrawal or cancellation route. Actual integration and independent review are still required. ### Free-mint windows and what users must see Verified GTD access opens only after successful launch activation and lasts 24 hours; each eligible ID can claim two units. The next 24 hours is the FCFS window, one unit per eligible ID while allocation is available. Registration alone does not guarantee launch, verification or a successful claim. No automatic unclaimed-slot rollover is enabled. Before payments open, the mint page must show the exact chain and payment asset, funding target/progress, escrow status and deadlines, refund conditions, 70/30 split, rebate, LP token/USDT amounts, verified pair and lock addresses, locked LP balance and permanent withdrawal policy. While these are undeployed, they must read proposed/not deployed rather than a live “locked” badge. ### Developer fees and remaining release gates Developer income comes from 5% USDT fees on settled official marketplace NFT sales and 2.5% AN404 service fees on the official token route, when users use those services. Ordinary transfers are untaxed, and external DEX activity does not automatically pay the project route fee. Local tests cover accounting, refunds and lock delivery with test doubles. A separate local BNB fork test exercises the deployed PancakeSwap V2 router/factory using synthetic tokens; it is not a public testnet deployment or an independent audit. Identity/history verification, queue-to-root generation, final rarity/reveal, production addresses, wallet signing review and testnet validation remain launch gates. ## How DN404 works Understand the balance before trading the picture. ### Base token and mirror NFT DN404 links a fungible ERC-20 base and an ERC-721 mirror. One 404 Strays unit represents 100,000 AN404 in this proposal. The project must enforce that unit and its cap in the actual contracts. Pool and vault accounts may skip NFT synchronization. Whole-unit capacity is not a promise that all 7,777 mirror NFTs exist at the same time. ### Transfers and specific identities NFT transfers move the linked token unit once. A marketplace must not separately charge or transfer another 100,000 AN404 as a second NFT delivery. Token-side trades may remove or recycle specific NFT IDs. Buying back the same token amount does not guarantee recovering the same art. Precise removal, recycling and fixed-ID rules must be implemented and disclosed. ### Two entry routes, after launch Token route: acquire AN404 through a supported market once available. Eligible whole-unit balances can synchronize to NFTs when the wallet’s NFT synchronization is enabled. Smaller balances can be held without a whole NFT. Pools and vaults may skip NFT synchronization. NFT route: acquire a specific 404 Strays NFT listed on a supported marketplace. Delivery moves its linked 100,000-AN404 unit once. The NFT purchase price is the seller’s listing price, not a second delivery of the same token unit. Neither trading route is live today. ### Market prices and rarity premiums AN404 units are fungible. A specific NFT can have a collectible premium or discount based on the actual buyer’s interest in its identity and rarity. A listing price is not proof that buyers will pay it. Rarity does not guarantee a higher resale price or a profitable gap against the token market. Any comparison between NFT and token prices must include real executable prices, project/external fees, gas, slippage and available liquidity. Token-side trades can change which NFT ID is held; buying a whole token unit is not a guarantee of a particular Rare, Epic or Legendary. ### Approvals and order safety ERC-20 allowances and NFT operator approvals are different. Concurrent open listings for a linked token and NFT position can create conflicting obligations. The market must recheck ownership, nonce, expiry, chain and balances at settlement. ## Supply & allocation One cap. Five disclosed buckets. ### Maximum token supply 7,777 whole-unit equivalents × 100,000 AN404 = 777,700,000 AN404. GTD: 200,000,000. FCFS: 233,300,000. Public: 189,000,000. Protocol LP: 78,741,000. Genesis event: 76,659,000. Buffer allocation: zero. The initial personal developer allocation is zero. LP/event reserves are protocol allocations, not freely transferable personal balances. The project needs reviewed custody contracts to enforce that policy. Earned service fees may later become operator holdings; fees in the permanent V2 LP position stay compounded and cannot be withdrawn. ### Why paid public is 1,890 Free slots remain 4,333. Funding a token-side LP reserve and a finite event reserve inside the same cap leaves 1,890 public units. The reserves are not extra tokens minted above the 777.7M maximum. ### Public payment split Public USDT reservations remain in escrow until successful launch activation. Then 70% (7,245 nominal USDT at full funding) seeds permanent LP, and 30% (3,105) is rebated proportionally to public minters at their token/NFT claim. Personal developer share of mint receipts is zero. The public-minter rebate is USDT, not a second allocation of reward tokens. The seven-day reservation window requires full funding; failure or missed activation allows refund of recorded USDT excluding gas. Exact rules are in Funding, refunds & LP lock. Initial development and gas are not deducted from these user funds. ### No buffer allocation There is no separate buffer. The former 1,040,000 buffer plus the former 1,000 unused cashback remainder are assigned to the LP token reserve, bringing LP to 78,741,000. The reward vault is funded exactly to its 76,659,000 maximum payout. This does not change the total cap or mint allocations. Neither the LP allocation nor unclaimed event entitlements are a developer gas budget or loss-insurance promise. The proposed permanent V2 lock and event contract have no operator sweep. ## Liquidity & operator fees LP principal and fee income are different things. ### Why reserve tokens for LP? A trading pool needs both the project token and a paired payment asset. The proposed 78.741M-AN404 reserve supplies the token side; 70% of public mint receipts funds the other side. Buyers and sellers trade against these reserves. Liquidity does not guarantee a price floor, a buyer at your price or protection from loss. Pool configuration and actual paired quantities determine initial trading conditions. LP means liquidity pool. Its principal is trading inventory, not the cashback or holder payout fund. Reward payouts must debit only the separately funded event vault. Under the proposed permanent V2 LP lock, LP fees compound inside locked liquidity and cannot be withdrawn by the developer. ### Custody requirement The proposed protocol vault seeds the AN404/USDT pool once and sends all protocol-minted LP tokens directly to permanent custody with no owner, unlock, transfer, approval, rescue or arbitrary-call method. Local code is tested, but no LP position or lock is deployed. Funding, the 24-hour activation grace period, refunds and permanent-lock delivery are specified in Funding, refunds & LP lock. Real router/pair integration, independent review and testnet validation are still required. Do not advertise a live LP lock before it exists. ### Operator income Proposed service fees are 5% on USDT-settled project NFT marketplace sales and 2.5% only on the project swap route, separate from DEX fees/gas. Token transfer tax is 0%. Direct external swaps do not pay the project routing fee. The proposed permanently locked V2 position does not allow operator withdrawal of LP fees; those fees remain compounded in the pool. Token creation alone does not grant creator DEX fees. Income depends on real use and earned fees; gross receipts are not guaranteed profit. ### What must actually be locked LP token or NFT-position custody must enforce the withdrawal policy after liquidity is deposited. Merely holding the AN404 reserve or publishing a lock badge is insufficient. If a normal wallet controls a withdrawable LP position, it may be able to remove the deposited assets. The proposed policy permanently prohibits LP principal withdrawal, transfer and separate fee extraction. Local lock code has no owner or unlock method, but no lock is deployed. The eventual mint screen must link the actual pair/lock and show the locked LP balance. External integration and independent review remain required. ## The fishing-world concept A possible next chapter for 404 Strays: NFT-linked characters and fishing gear. This is an early design direction, not a live game. ### From collectible to a game representation We are exploring a future fishing game where a held 404 Strays NFT could be represented as a character or a gear loadout based on its rarity. This connects the collection art to a possible game experience; it is not an announced game launch or a guaranteed mint benefit. The initial concept keeps the NFT in the holder’s wallet. “NFT to item” means a game representation of an owned NFT, not an approved burn, permanent redemption, or an extra independently tradable asset. No conversion contract or game-item economy exists today. ### Illustrative rarity-to-gear mapping Base — Street Stray: Streetwear character and starter dock gear. Uncommon — Dockhand: Hand-line spool and tackle-tin theme. Rare — Net Runner: Landing net and teal-lure theme. Epic — Deepwater: Violet dock coat and fish-net theme. Legendary — Tidekeeper: Captain appearance, rod, reel and trophy-fish theme. These are art and item-theme directions, not finalized item allocations or gameplay statistics. Catch rates, progression, access requirements, item trading and balance have not been decided. Higher rarity does not currently grant increased earnings or a guaranteed gameplay advantage. ### One owner, one linked position Any future implementation would need to recheck the NFT owner, identity and rarity. If the NFT moves, the former holder must not keep duplicating its ownership-based game entitlement. Token-side balance changes can also remove or recycle an NFT ID, so game access cannot assume the same art is permanently attached to a wallet. Every rarity still represents the same proposed 100,000-AN404 whole unit. This concept changes neither the 777.7M token cap nor the existing finite event budgets. Fungible AN404 tokens have no individual art rarity. ### What is available and what comes next Today: collection artwork concepts, project documentation and server-side registration of interest. Minting, token/NFT markets, reward claims and the game are not live. Next work: validate community interest, define the game loop and ownership model, assess the development budget and test a prototype. A production game, a release date, game access, playable items, token yields and return on investment are not promised with registration or minting. Any later concrete terms must be published before users rely on them. ## The finite genesis event A budget that can be checked, and an event that ends. ### Fixed bonus from reserved supply Exactly 1,000 AN404 per eligible recipient claim, funded by the exact 9.999M event cashback allocation. Operator service fees are collected separately and are not reduced to fund this bonus. The old percentage-of-fee amount is superseded. No claim is live. The exact 76.659M event envelope contains 66.66M holder funding plus 9.999M cashback funding. There is no separate buffer. The former 1.041M unused reserve is reassigned to the LP allocation, now 78.741M. Both remain inside the 777.7M cap. ### Fair cap: three claims per approved ID Freeze an event allowlist of at most 3,333 verified Agent IDs before launch. Each approved identity has three recipient claims over seven days, without a daily limit. Name, wallet or identity ownership changes must not reset its counter. Verification is not proof of one human. Maximum cashback is 3,333 x 3 x 1,000 = 9,999,000. The 9.999M allocation exactly covers this ceiling. There is no budgeted cashback remainder or buffer. Valid entitlements must be funded before opening and still need real settlement and deadline checks. The earlier 10,000-claims-per-ID idea is superseded: funding that for 3,333 IDs would need 33.33B tokens. Current cap and allocations are unchanged. ### Eligible buys, sells and two-party NFT claims A real secondary buy or sell of at least 100,000 AN404 through the official route can qualify its approved verified trader for 1,000. A paid secondary NFT sale settled in USDT on the official marketplace can qualify buyer and seller separately: 1,000 each, two recipient claims and 2,000 event cost. Each uses one of its own three claims. No stacking per 100k or NFT quantity in one order. Linked NFT/token movement is delivery of the same order, not another trade. Ordinary transfers, free/primary mints, external routes, failed/cancelled orders, self/operator/known-related-wallet trades and duplicate claims are excluded. Require actual settlement and published service-fee receipts. If both NFT parties qualify, reserve 2,000 atomically or disclose no bonus before execution. If only one party qualifies, its claim costs 1,000. Never promise an unfunded second payout. Real identity binding, receipt replay protection and settlement remain unimplemented. ### Fee income and marketing cost A 100k AN404 trade basis produces a 2,500-AN404 project service fee at 2.5%. An exact-net buy requests 102,500 AN404 from the DEX, delivers 100,000 to the user and sends 2,500 to the fee recipient. A sell executes 100,000 into the DEX and charges an additional 2,500 AN404, requiring 102,500 total input. Quotes must show this full amount, slippage limits and any external DEX fees/gas. A separate eligible 1,000 bonus debits event inventory; it is not deducted from the operator fee. An NFT sold for 10 USDT pays a 0.50-USDT marketplace fee and leaves 9.50 USDT for the seller. The NFT transfer separately delivers its linked 100,000 AN404. Each eligible buyer/seller may claim 1,000 AN404 from event inventory; USDT fees and AN404 rewards are different assets with no fixed value equivalence. Fees are gross operator income, not guaranteed net profit. Bonuses are finite acquisition spending. Repeated/related-party trading can consume subsidies without real demand. Per-ID limits bound exposure but do not prove one person per ID or make the event wash-proof. ### Holder rewards and transfers Holder plan: up to 3,333 verified event wallets x 5,000 x four fully funded rounds = 66.66M. Require 100,000 continuously held for 24 hours at each snapshot. Per eligible wallet, not per NFT or rarity. Selection and history/duplicate checks must be implemented. Planned claim opening is 8:00 AM America/New_York on D1-D4, exact UTC/DST windows and blocks TBA. New recipients do not inherit the sender holding history. Falling below 100,000 interrupts the minimum; balances continuously above it can remain eligible. ### Ending, unused tokens and release status Cashback lasts at most seven days. Proposed common claim deadline D14; real dates/blocks TBA. There is no buffer or budgeted remainder. Valid reward entitlements that users do not claim remain restricted in the event contract, with no operator sweep or automatic renewal. Preview arithmetic uses whole tokens and simulated verification. Production requires base units, real receipts, stable ID counters, funded settlement and reviewed custody. No live event, wallet, contract, lock or audit is claimed.