Read before
you sign.

$70,000 FDV—not $70,000 raised.

The requested target is 70,000 USDC of fully diluted valuation, treating 1 USDC as approximately $1 for display. With 1 billion tokens, that implies a marginal token price of 0.00007 USDC. This is a nominal valuation, not an oracle-backed USD guarantee.

The replacement candidate fixes supply at 1 billion tokens: 750 million for the curve and 250 million for DEX liquidity. Initial virtual reserves are 1.125 billion tokens and 8,750 USDC. At the sale boundary, the real reserve is 17,500 USDC and the marginal price is exactly 0.00007 USDC, giving 70,000 USDC FDV. These parameters are implemented in the deployed mainnet contracts and covered by local Arc fork tests.

Reserve required at sold supply S is ceil(K / (1,125,000,000 − S)) − 8,750, using full 18-decimal units and K equal to the product of the initial virtual reserves. The 250 million-token / 17,500-USDC DEX allocation matches the terminal price. Virtual USDC is not withdrawable collateral. The final buy caps output and returns unused input; fees apply to actual executed principal.

State needs evidence.

Fresh

Verified factory launch and an open curve. Unknown RPC state must remain unknown, not default to Fresh.

Migrating

A confirmed transition requiring liquidity settlement. A failed attempt must have a tested recovery or rollback path.

Migrated

Confirmed pool identity, funding and LP custody. Both DEX buy and sell paths must work.

Indexed

A separate external observation of the actual pair on the selected indexer. Not equivalent to Migrated.

Manual status changes are disabled. The candidate event indexer derives state from the factory, token and migration adapter. It requires a matching pool-funding event before accepting Migrated, deduplicates logs and rejects conflicting block histories. The persistent worker verifies contract runtimes, saves checkpoints atomically, rebuilds conflicting history and rejects unapproved production configurations. The persistent worker is connected to the validated mainnet factory. A token at the cap remains sellable until successful atomic migration; selling below the cap returns it to Fresh.

Transfer tax ≠ trading fee.

A transfer tax changes how many tokens arrive when an ERC-20 transfer happens. A curve fee is charged by the bonding-curve trade. A DEX pool fee is a third, separate mechanism. These must not be silently combined.

Arc’s EVM compatibility makes custom token logic possible in principle; it does not establish router compatibility. Uniswap v3 does not support fee-on-transfer tokens through its routers. Do not enable 1%, 3% or 5% transfer taxes until the chosen DEX explicitly supports them and actual transfer, liquidity and swap paths pass tests.

The candidate supports immutable 1% / 3% / 5% fees on curve buys and sells, paid to the factory’s fixed treasury. Token transfers remain untaxed. Fees become claimable credits; the treasury cannot block trades by rejecting a payment. Uniswap v4’s selected pool fee is separately fixed at 0.3%. Curve fees cease when trading moves to the DEX. Curve and LP fees accrue to the immutable treasury: 0xf9044785F5b2BaB8cD23998312c344C0b5E13Dd7.

One USDC balance. Two interfaces.

Mainnet chain ID: 5042. Official RPC: rpc.mainnet.arc.io. Explorer: explorer.arc.io. Chain identity and deployed contract code must be verified before signing. A network label in the UI is not verification.

Native USDC uses 18 decimals; ERC-20 USDC uses 6 decimals against the same underlying balance. Raw-unit conversion uses a factor of 10¹². Never add the two balances together or treat them as two different pool assets. Preserve native-unit dust in accounting and test the DEX’s exact interface.

Arc enforces restrictions on native transfers, including blocklisted addresses and forbidden burns. Treasury payout failure must not freeze unrelated users’ trades. Standard Ganache tests cannot reproduce Arc-specific execution; Arc Foundry and network integration tests are required.

Official network configuration ↗ · Arc EVM differences ↗

Uniswap v4 migration.

Uniswap v4 is the selected integration target. Its official Arc mainnet addresses have been checked for code presence on chain 5042, and PositionManager points to the listed PoolManager. This is not a source/bytecode audit. The candidate uses a direct full-range PoolManager position, native 18-decimal USDC, a 0.3% pool fee, tick spacing 60 and an initialization-only hook. Local Arc fork tests funded the canonical pool and executed DEX buys and sells. Liquidity principal is permanently locked in the adapter; permissionless fee collection pays the immutable treasury. There is no liquidity withdrawal or upgrade function and no PositionManager NFT. Official Uniswap deployments ↗

An initialization-only hook restricts pool creation to the token’s immutable migrator during atomic migration. Tests reject hostile initialization and confirm an unrelated pre-created pool cannot block migration. The hook has no swap callbacks, dynamic fees, owner controls or custody. Its required address permissions are verified during CREATE2 deployment. The hook has not received an independent audit. Further cases include minimum liquidity bounds, donations, unexpected token balances and Arc blocklist behavior. LP ownership or locking must be explicit and verifiable; migration must not give the admin an undisclosed withdrawal path.

DEX Screener describes automatic listings after a pool and transaction exist. We still need to establish support for the chosen Arc DEX and observe the actual pair. External listing speed or acceptance cannot be guaranteed.

Admin access is not custody.

The existing six-digit PIN protects a web session only. It is not sufficient protection for production deployment authority or treasury management. Contract actions must require the authorized wallet; a reviewed multisig and explicit ownership policy should precede public deposits.

The candidate frontend now uses verified factory, token and router interfaces, with quote review, exact token approvals, deadlines, credit claims and migration actions. The admin stages five wallet-signed deployment transactions and records receipt proof. All five mainnet deployment receipts and constructor linkages were independently checked against the tested bundle by this deployment workflow. Mainnet token lifecycle rehearsal and external DEX discovery remain unproven; independent audit was waived by the owner. Persistent indexer backfill, restart, duplicate handling, checkpoint recovery and runtime verification pass local tests. The unsafe legacy contract is excluded from release. Native payout failures retain credits for the rightful recipient, who can claim to another permitted address.

Mainnet launch and trading are enabled. Manual migration labels remain disabled. Five production contracts are deployed; factory: 0xEDaf9816FCE9ce052D8e42F4C3CC4A71C7BBA6AC. Explorer verification is pending.

Test every way funds move.

• Unit and randomized invariant tests: supply conservation, reserve solvency, rounding, fees, refunds and quote/execution agreement.
• Adversarial tests: invalid configuration, unauthorized administration, slippage, reentrancy and rejecting recipients.
• Boundary tests: exact $70k threshold, oversize final buy, migration failure, retries and duplicate execution.
• Real DEX integration: liquidity seeding, LP custody, post-migration buys and sells, USDC decimal handling.
• Arc-specific simulation, then a controlled network rehearsal with receipts and balance reconciliation.
• Indexer replay/restart and external pair discovery; browser tests for rejected signatures, wrong network and unavailable RPCs.
• Independent security review, verified source, deployment bytecode hashes, ownership and incident procedures.

The candidate records 26 lifecycle checks, including exact balance reconciliation, 60 deterministic mixed trades, the $70k boundary, rejecting recipients, reentrancy, failed/fake migration, guarded pool initialization, real Uniswap fork funding and post-migration swaps. Five indexer checks cover backfill and persistence. DOM-based frontend tests execute local-fork launch, buy/sell and admin-deployment transactions, test quote confirmation and approvals, and reject wrong networks, signatures and unauthorized operators. These do not exercise a real browser extension. This remains local simulation, not release certification. The owner authorized public operation without an independent audit. Passing local tests does not guarantee that users cannot lose funds.