# Launch a token on Nexus V3

These are vendor-neutral instructions for a wallet-owning agent. Nexus uses Arc Testnet chain `5042002`. Public planning needs HTTPS and JSON; execution additionally needs an EVM wallet capable of ERC-20 approvals, typed-data signatures when policy requires them, and transactions on chain `5042002`.

An agent without wallet access stops after presenting the unsigned plan. Never transmit a private key to Nexus.

## Network constants

- Arc USDC system contract: `0x3600000000000000000000000000000000000000`, 6 decimals through its ERC-20 interface.
- V3 factory, NonfungiblePositionManager, SwapRouter02, and QuoterV2:
  require the exact pairwise-distinct addresses returned by Nexus readiness
  for the reviewed release.
- Fee tier: `10000`.

Arc has not published a canonical production V3 stack. Testnet addresses are
disposable and must not be copied into agent instructions or treated as
mainnet constants. Always verify the configured addresses and bytecode through
Nexus readiness. An address list alone is not deployment approval.

## Workflow

1. Fetch capabilities and readiness. Require `ok:true`, `ready:true`, no blockers, and the exact reviewed proxy and implementation identities.
2. Collect creator, name, symbol, fee recipient, optional first buy, slippage, profile, protection, method, wallet identifier, deadline, and salt.
3. Request the unsigned launch plan.
4. If the result is approval-required, ask the wallet to approve exactly the returned six-decimal USDC requirement to the returned launchpad spender. Verify and finalize that approval before re-planning.
5. Require a ready version-7 plan and a passed, non-broadcast simulation.
6. Present the complete plan and transaction to the user.
7. Generate and obtain any required exact-plan EIP-712 approval.
8. Revalidate the unchanged ready plan immediately before the creator signs.
9. Broadcast once, preserve the hash, and verify every onchain postcondition.
10. Wait for Safe-head finality and reconcile the nonce before any later write.

Illustrative inputs:

```json
{
  "creator": "0xCREATOR",
  "name": "Signal",
  "symbol": "SIGNAL",
  "initialBuyUsdc": "10",
  "initialBuySlippageBps": "500",
  "creatorFeeRecipient": "self",
  "profileHash": "0x0000000000000000000000000000000000000000000000000000000000000000",
  "antiSniperBlocks": "300",
  "maxWalletBps": "200",
  "blockSameBlockBuys": true,
  "launchMethod": "agent"
}
```

The ready plan must bind:

- `planVersion:"7"`;
- `launchFunction:"launchGuarded"`;
- `launchSelector:"0xd555e4e4"`;
- `launchGuardVersion:"2"`;
- six-decimal `launchFeeUsdcRaw`, `initialBuyUsdcRaw`, and `totalFundingUsdcRaw`;
- exact simulated `expectedInitialBuyTokens` and the reviewed minimum;
- zero native transaction value; and
- all proxy, implementation, authority, protocol, token, profile, attribution, deadline, salt, and protection fields.

Do not substitute values, infer identity from symbols, edit the saved envelope, or treat a fresh estimate difference as permission to change a committed field.

## Economics and risk

The `1 USDC` fee and initial tick magnitude of `398400`, corresponding to
approximately `4,995.43 USDC` starting FDV for the fixed one-billion supply,
were approved on 2026-07-23. Those economic approvals do not authorize an
exact deployment, token launch, or trade.

Liquidity principal is permanent. The launcher is upgradeable. Launch protection expires. Thin pools can move sharply, and slippage and MEV remain possible. The Arc port is unaudited and not deployed unless the exact configured readiness evidence proves a reviewed deployment exists.