Architecture

Tokens and Arcs

Each launch mints the fixed 1B supply once. The supply is placed into four contiguous concentrated-liquidity positions in one canonical pool. Those positions are Arcs, not separate pools, vesting tranches, or graduation steps.

Launch liquidity begins token-side only. Buyers introduce USDG into the pool; sellers later exchange tokens against USDG held by active liquidity. Price can move forward or backward through an Arc. The seeded Arc principal is designed to remain nonwithdrawable, while separately accrued Arc LP fees belong to the immutable creator.

How nonwithdrawable Arc principal works

1. At launch, the fixed token supply is deposited into four connected Arc positions in the canonical USDG pool.
2. A buyer sends USDG into the pool and receives tokens. The positions now hold more USDG and fewer tokens at the buyer's execution price.
3. A seller later returns tokens to the pool and receives available USDG. The positions' asset mix changes again as price moves through the Arcs.
4. The deployer and creator cannot withdraw the position principal or transfer an LP position to themselves. Trading changes the principal's composition, but it does not unlock it.
5. Native LP fees accrue separately from that principal. The creator can collect eligible fee balances without removing the tokens or USDG that make up the seeded Arc positions.

This removes the deployer's ability to drain the seeded launch liquidity. It does not freeze the pool's token and USDG balances; those balances continue to change whenever traders buy or sell.

Fees

Each swap applies a 0.5% oxley fee measured in USDG and a separate 0.5% native pool LP fee. The direct oxley fee is split equally between creator and platform. Native LP fees follow active liquidity ownership: seeded Arc fees go to the creator, and external LPs retain the fees earned by their own positions.

Direct fees accrue as claimable balances. A creator collection failure cannot block swaps or redirect the platform share.

Immutability and authority

The launched token has no future minting, contract owner, proxy, transfer tax, blacklist, or upgrade path. Contract addresses and fixed parameters can be verified directly against their onchain runtime and immutable configuration.

Immutability reduces administrator risk but does not remove implementation, integration, liquidity, quote-asset, or chain risk. Immutable code cannot be patched in place; corrected logic requires new contracts and explicit user migration.