Orba Docs
How Orba's target mainnet release works, what users control, and which facts still require release verification.
Mainnet draft — not yet effective. Contract addresses, parameters, ownership, verified source, and external-audit status must be checked against the final deployment before publication.
What is Orba?
Orba is a token launch and discovery application built for Arc, a USDC-native EVM network. A newly launched token begins on an Orba bonding curve priced in USDC. Users can buy from and sell to that curve until the token reaches its graduation condition. The graduation process then moves eligible liquidity into Orba's automated market maker (AMM), and curve trading ends.
The target token model has a fixed supply of 1,000,000,000, no team allocation, no later mint function, and no per-wallet holding cap. Orba is independent and is not affiliated with or endorsed by Circle.
How the bonding curve works
Orba uses a constant-product curve with virtual reserves, not a linear price schedule. As USDC enters the curve, the remaining token reserve falls and the marginal price rises. A sell moves the state in the opposite direction. Quotes depend on the current reserve state and can change before a transaction confirms.
What that means in practice
- Larger trades move the price more than smaller trades.
- Displayed quotes are estimates until the transaction executes.
- Caller-supplied minimum output protects buys and sells from excess slippage.
- The target curve fee is 1% on both buys and sells.
Selling remains subject to contract state, available curve liquidity, slippage protection, network conditions, and successful token approval. Orba does not guarantee a particular price or execution time.
Graduation to the AMM
The target release graduates a curve at a market capitalization of 30,000 USDC. Graduation retires curve trading, creates or funds the token's AMM pair, and allocates the configured liquidity seed. The target seed is 8,500 USDC, but the final deployed contracts are authoritative.
After a successful graduation:
- the bonding curve no longer accepts buys or sells;
- the token trades through the AMM at pool-determined prices;
- liquidity-provider tokens are intended to be burned to the configured dead address;
- token ownership is intended to be renounced; and
- the pre-graduation transfer cooldown is disabled.
Protocol safeguards and limits
Fixed supply. The target token has 1,000,000,000 units, all created at launch, with no later mint function.
No creator allocation. Supply starts on the bonding curve rather than in a creator wallet. A creator can still buy like any other participant and can earn the disclosed creator-fee share.
Uncapped holdings. New tokens do not enforce the former 4% max-wallet rule. One person may also control multiple wallets, so wallet caps would not be reliable identity controls.
Transfer cooldown. Before graduation, ordinary wallet-to-wallet transfers are separated by approximately 30 Arc blocks. Curve buys and sells remain usable. This slows some automated transfer patterns but does not prevent bots or manipulation.
Slippage minimums and bounded approvals. Trades enforce a minimum output supplied by the user. The Orba interface targets exact or bounded token approvals, but users must still review every wallet request.
Graduation controls. The release candidate intends to burn LP tokens and renounce token ownership after migration. These protections must be verified from final mainnet transactions and bytecode.
These controls reduce specific creator and execution risks; they do not prevent market loss, compromised wallets, contract defects, misleading content, MEV, or protocol-administration risk.
Fees and costs
Target parameters are summarized below. See the Fees page for calculations and important distinctions between fees, gas, approvals, slippage, and price impact.
The Arc blockchain
Arc is an EVM-compatible network that uses USDC as its native gas asset. Orba also interacts with Arc's six-decimal ERC-20 representation of USDC for contract accounting. They represent the same asset at different decimal precisions, so interface and contract amounts must not be mixed.
The planned mainnet network identifier is chain ID 5042. The final RPC endpoints, explorer, USDC address, and Orba contract addresses will be published only after deployment verification.
Wallets and USDC
- Use a supported self-custody EVM wallet and verify that it is connected to the official Arc mainnet configuration.
- Hold enough native USDC for network gas and enough ERC-20 USDC for the intended launch or trade.
- Verify the Orba domain, contract, amount, recipient, quote, slippage, and approval before signing.
- Keep your seed phrase and private key offline and never enter them into Orba.
Wallet balances, quotes, and receipts depend on wallets and RPC providers. A delayed interface does not by itself mean a transaction failed; confirm the transaction with the official explorer before retrying.
Referral program
A referral link can attribute a wallet to a referrer on a first-valid- attribution basis. Orba records attributed trade count, volume, and a target reward accrual of 0.1% of eligible bonding-curve volume.
Referral amounts are off-chain accounting records. They are not an on-chain balance or guarantee of payment. No payout is available unless Orba separately launches a claim or distribution process with published eligibility and verification rules. Self-referrals and manipulated volume may be rejected.
Smart-contract architecture
MemeToken creates the fixed supply and applies the pre-graduation transfer cooldown.
BondingCurve holds token inventory, quotes constant-product trades, enforces slippage minimums, and accrues fees.
TokenFactory deploys token and curve pairs and charges the configurable creation fee.
LiquidityMigration moves eligible curve liquidity to the AMM and completes graduation safeguards.
AMMFactory, AMMPair, and AMMRouter support post-graduation liquidity and atomic swaps.
Mainnet addresses, owner and guardian roles, compiler settings, source- verification links, and deployed-bytecode evidence must be added or checked after deployment. This draft does not claim that mainnet contracts are deployed.
Security and audit status
Orba has performed internal pre-audit reviews and local or Arc-testnet testing across contracts, APIs, indexing, wallet flows, agent limits, and graduation mechanics. Those activities help find defects but are not an independent security audit and do not prove that the system is secure.
Mainnet publication remains blocked on an independent external audit, remediation and retesting, final deployed-bytecode verification, confirmed multisig or Safe ownership, production RPC and monitoring readiness, and a bounded launch canary. Security findings and final audit references should be published only when the underlying evidence exists.
FAQ
Is Orba affiliated with Circle?
No. Orba is an independent project. Arc, Circle, and USDC references identify third-party technology and assets; they do not imply sponsorship or endorsement.
Can one wallet hold more than 4%?
Yes. The target uncapped token model has no per-wallet holding limit. Fixed supply, transfer cooldown, slippage minimums, bounded approvals, and agent-wallet limits address different risks and remain separate controls.
Can a creator remove graduation liquidity?
The target migration burns LP tokens and renounces token ownership. Verify those actions on-chain for the specific token. These safeguards do not eliminate price, contract, wallet, content, or protocol-administration risk.
Are referral rewards withdrawable?
Not by default. The displayed amount is an off-chain accrual until Orba announces and enables a separate payout process.
Has Orba passed an external audit?
Not yet. Internal reviews and testnet evidence are pre-audit work. An independent external audit remains a mainnet release gate.
Questions? hello@orba.fun