Cargo404 ($C404)

Cargo404 is a BNB Chain terminal-themed ERC20 cargo mint.

Load cargo with BNB. Trigger 404. Receive $C404.

Users connect an EVM wallet, choose how many cargo units to load, pay BNB, and receive $C404 directly from the contract under fixed on-chain mint limits.

ERROR 404: CARGO NOT FOUND
Route missing. Cargo loaded. Convoy deployed.

• Live app: https://www.cargo404.app/
• Repository: https://github.com/cargoterminal/cargo404
• Network: BNB Smart Chain Mainnet
• Verified contract: 0xEe563fe51d8903F7Bfc38489C60e4e797365b7FF
• Token: Cargo404 (C404)

Cargo404 is experimental meme-token software. It is not financial advice. Always verify the official contract address and confirm every wallet transaction manually.

What Cargo404 is

Cargo404 turns a simple BNB Chain token mint into a terminal-style cargo loading event. Each cargo unit costs a fixed amount of BNB and delivers a fixed amount of $C404 to the minter's wallet.

Cargo404 is a fixed-supply ERC20 token contract. The 404 identity is terminal/error-cargo branding; Cargo404 is not an ERC404 or NFT contract.

Project status

Cargo404 is deployed with the 40.4M fixed-supply Option A tokenomics on BNB Chain:

• Official verified contract is live at 0xEe563fe51d8903F7Bfc38489C60e4e797365b7FF.
• BscScan source verification is complete.
• Web mint terminal points at the official contract address.
• Public repo is cleaned and documented.
• Mint is controlled by an owner switch and should only be enabled when the launch post, wallet QA, contract transparency checks, and liquidity plan are ready.
• Liquidity creation and LP lock/burn proof happen after the mint phase.

Mint details

• Total supply: 40,400,000 C404
• Public mint allocation: 28,280,000 C404
• Reserve allocation: 12,120,000 C404
• Mint price: 0.0025 BNB
• Tokens per cargo unit: 4,040 C404
• Max cargo units: 7,000
• Max per wallet: 10 cargo units

If the public mint sells out:

7,000 cargo units × 0.0025 BNB = 17.5 BNB raised

Raised BNB plan

Raised BNB stays in the contract until the owner calls the one-time distribution function after the mint phase:

70% -> Liquidity bucket / owner deployer
20% -> Treasury
10% -> Buyback wallet

Liquidity creation is manual. After distribution, reserve C404 should be paired with the liquidity BNB on PancakeSwap, then LP should be locked or burned and proof should be posted publicly.

How Cargo404 works

1. User opens the official Cargo404 site.
2. User connects a wallet on BNB Smart Chain.
3. User chooses how many cargo units to load.
4. Wallet confirms the mint transaction.
5. C404 lands directly in the user's wallet.
6. Public mint progress and wallet limits are read from the contract.

The frontend never asks for seed phrases or private keys.

Clear claims

Cargo404 can accurately be described as:

• a BNB Chain ERC20 cargo mint;
• a fixed-supply token contract;
• a terminal-themed meme-token mint;
• a contract-based public mint with fixed price, fixed wallet cap, and fixed public mint cap;
• a project with a hardcoded raised-BNB distribution split.

Cargo404 should not be described as:

• an ERC404 contract;
• an NFT mint;
• an auto-liquidity contract;
• audited, renounced, LP-locked, or burned unless those steps have actually happened and public proof is posted.

Repository contents

contracts/                    C404 contract source
scripts/                      owner operation scripts
frontend/                     live mint terminal
frontend/public/              Cargo404 logo and favicon assets
frontend/src/                 mint UI and wallet logic
docs/MAINNET_LAUNCH.md        operator launch checklist
docs/CONTRACT_PROOF.md        on-chain proof and safety notes
docs/ROADMAP.md               public roadmap
.github/workflows/ci.yml      automated contract/frontend checks
SECURITY.md                   security reporting notes

For operators

Use the launch runbook for owner-side actions:

• docs/MAINNET_LAUNCH.md
• docs/CONTRACT_PROOF.md

Minimum launch flow:

1. Confirm the live site shows the correct contract address.
2. Confirm the wallet connect and mint panel work in-browser.
3. Prepare the official website + contract announcement post.
4. Enable mint from the owner wallet.
5. Test one mint from a non-owner wallet.
6. Monitor mint progress and failed transactions.
7. After the mint phase, distribute raised BNB.
8. Create PancakeSwap liquidity, then lock or burn LP and publish proof.

Local verification

For maintainers who want to verify the repo locally:

git clone https://github.com/cargoterminal/cargo404.git
cd cargo404
npm install
npm --prefix frontend install
npm run check

Local environment files are intentionally ignored. Never commit .env, private keys, seed phrases, or deployer wallets.

Frontend deployment uses the frontend/ folder:

Root directory: frontend
Build command: npm run build
Publish directory: dist
Node version: 20.x

Required public frontend variables:

VITE_CARGO404_ADDRESS=0xEe563fe51d8903F7Bfc38489C60e4e797365b7FF
VITE_BSC_RPC_URL=https://bsc-dataseed.binance.org
VITE_REOWN_PROJECT_ID=your_reown_project_id # optional, enables WalletConnect/mobile fallback

Roadmap

See docs/ROADMAP.md for the public Cargo404 roadmap covering completed foundation/terminal work, liquidity proof, transparency, and post-mint experiments.

Security notes

• The site never asks for seed phrases or private keys.
• All mint actions require wallet confirmation.
• Verify the official contract address before minting.
• Mint price, supply, wallet cap, and BNB split are fixed in the contract.
• Liquidity creation and LP lock/burn are manual operational steps.

For reporting security issues, see SECURITY.md.

License

MIT. See LICENSE.