ArcOrigin documentation

ArcOrigin is a non-custodial token launchpad and trading terminal on Arc. Every launch creates a fixed-supply ERC-20 token and its own USDC bonding curve. Wallets interact directly with the deployed contracts.

The current interface launches a one-billion-token fixed supply with zero free creator allocation. The creator may add an optional paid developer buy, executed as a normal curve purchase after launch.

1. 01ProfileSet the name, ticker, description, image, website, and X profile.
2. 02MetadataThe image and metadata are committed, signed by the wallet, and stored on IPFS.
3. 03DeployApprove the 10 USDC launch fee, then deploy the token and curve through the V6 Factory.
4. 04Optional buyApprove the chosen USDC amount and buy from the same curve as every other trader.

Supply

1,000,000,000

Free creator allocation

0%

Current launch fee

10 USDC

Developer buy

Optional · max 5% through the app

Each token trades against USDC. Before migration, quotes and trades use its dedicated curve. After a verified migration, the interface automatically uses the canonical Arc Uniswap V3 pool.

You receive

The current contract quote after the 1% trading fee.

Minimum received

The lowest output accepted onchain after applying your slippage setting.

Slippage

Execution tolerance. ArcOrigin provides 10%, 20%, 40%, and manual input.

Priority

A wallet fee preference. It affects inclusion speed, not the curve price.

Approval

USDC is approved before a buy; the launch token is approved before a sell.

Before graduation, pricing follows a constant-product curve using the real token reserve and an effective USDC reserve. The effective reserve is the 2,500 virtual-USDC seed plus USDC deposited by buyers.

effective USDC = virtual USDC + real USDC
spot price     = effective USDC / token reserve
x · y          = constant before each trade

Buy outputs round conservatively in favor of the reserve. Sell outputs cannot exceed the real USDC reserve. The contract returns a zero quote when a trade cannot be executed safely.

Graduation occurs when the curve reaches 10,000 real USDC. It first creates permanent, two-sided liquidity inside the curve. If that market's snapshotted migration path is enabled, a later verified transaction can move those reserves into its canonical Arc Uniswap V3 pool.

1. 01ThresholdThe final pre-graduation buy is capped so net real reserves cannot exceed 10,000 USDC.
2. 02RebalanceVirtual USDC is removed and the remaining token reserve is resized at the same spot price.
3. 03LockSurplus curve inventory is sent irreversibly to the dead address.
4. 04ContinueThe internal AMM remains active unless a verified migration atomically creates and permanently locks the canonical Uniswap V3 position.

V6 fee distribution is enforced by the deployed contracts, not estimated by the interface.

Curve fees accrue 70% to the creator and 30% to the protocol. After migration, the permanent 1% Uniswap V3 position is collected permissionlessly and its fees are split by the immutable locker at the same 70/30 ratio.

ORIGIN is the canonical ArcOrigin protocol token. Its mainnet buyback controller is active and governed by the published 2-of-3 Safe.

ORIGIN token

0xB65Fd34cc428492DdF000A2Ae100Dbfea62E4802

ORIGIN curve

0x18708Bd06e264E8147065159C90460be4b5B5312

Buyback controller

0x43ED0F9CD330FE8F093f2a0CE2FA05A155e7f746

Buyback allocation

80% of allocated protocol revenue

Operations allocation

20% of allocated protocol revenue

Maximum execution

25 USDC

Minimum interval

1 hour

Maximum slippage

3%

Destination

0x000000000000000000000000000000000000dEaD

1. 01WithdrawThe 2-of-3 Safe approves a Fee Vault USDC withdrawal to the controller.
2. 02AllocateAnyone can apply the immutable 80% buyback / 20% operations split.
3. 03ExecuteAn authorized executor buys no more than 25 USDC of ORIGIN per hourly slice.
4. 04BurnAll purchased ORIGIN is sent directly to the canonical burn address.

Network

Arc

Chain ID

5042

Quote asset

USDC

Public RPC

https://rpc.blockdaemon.mainnet.arc.io

Explorer

https://arc-mainnet.cloud.blockscout.com

V6 start block

12,881,762

These are the active ArcOrigin V6 addresses used by the interface. Always verify addresses before building an integration.

Index bounded block ranges from the V6 start block. Events are the authoritative source for launches, trades, fees, charts, and holders.

Use contract reads for current state and confirmed events for history. Never derive an executable quote from chart candles or cached market cards.

Discovery

Read TokenLaunched from the V6 Factory beginning at the published start block.

Token ↔ curve

Read getTokenInfo(token) on the Factory.

Venue

Read isMigrated() and migratedPool() on the curve; verify the pool against the official V3 Factory.

Buy quote

Use quoteBuy(usdcAmount) before migration, or QuoterV2 exactInputSingle after migration.

Sell quote

Use quoteSell(tokenAmount) before migration, or QuoterV2 exactInputSingle after migration.

USDC reserve

Read realLiquidity(); do not include virtual USDC.

Graduation

Read isGraduated() and getCurveProgress().

Holders

Replay ERC-20 Transfer events and reconcile balances.

const [tokensOut, fee] = await publicClient.readContract({
  address: curve,
  abi: bondingCurveAbi,
  functionName: "quoteBuy",
  args: [parseUnits("100", 6)],
});

The website uses a narrower, canonical launch profile than the Factory contract permits. This distinction matters for third-party integrations.

V6 administration is transparent onchain. Factory, Fee Vault, and Creator Registry are owned directly by the published 2-of-3 Governance Safe.

1. 01Governance SafeThree independent signers with a 2-of-3 confirmation threshold.
2. 02Protocol ownershipFactory, Creator Registry, and Fee Vault are directly controlled by the 2-of-3 Safe.
3. 03Emergency controlsThe guardian can pause new launches and migrations, but cannot resume them, seize reserves, or block sells.
4. 04TreasuryThe Safe approves Fee Vault withdrawals, which can only go to the active ORIGIN revenue controller.

ArcOrigin is deployed on Arc. User-created tokens can be volatile, illiquid, duplicated, or lose all value.

A repeatable internal security and logic review was completed on 30 July 2026 across the V6 contracts, wallet flows, metadata upload, indexing, caching, governance, and production configuration.