Terms of use
BeaconHarbor is a non-custodial launchpad on Arc where every launch registers on-chain and waits its turn. These rules are written in plain language, with no hidden clauses. By connecting a wallet or using this site, you accept them.
Plain-language draft · Arc mainnet
Languages These terms are published in English and in Simplified Chinese. Where the two versions differ, the English version governs.
1. What BeaconHarbor is
BeaconHarbor is a non-custodial token launchpad on Arc, the USDC-native L1 built by Circle. A creator who meets the registration rules registers a token launch on-chain, the launch waits for its turn in one public queue, and anyone can then trade the token, on its bonding curve first and on Uniswap v4 after graduation. BeaconHarbor never takes custody of your funds or your tokens. Every action is a transaction you sign with your own wallet, and network gas is paid in USDC from the same balance you trade with.
2. The queue decides the order
Every launch registers on-chain before it can launch, and the contract only lets the head of the line launch. No registration can pay to jump the queue, and BeaconHarbor, its owner and its keeper cannot reorder the line, hold a place or sell one.
A round is one minute of block time, counted from the chain's own timestamp. At most 5 launches can land in one round, which is 50 in ten minutes. A round does not wait to fill up. The head launches as soon as someone executes it.
Execution is permissionless. BeaconHarbor runs a keeper that executes the head of the line, and any wallet can execute it instead with nothing but an RPC endpoint. The contract checks the order and the round, so whoever sends that transaction gains no place and no priority.
- Queue positions and times shown on this site are estimates. A cancellation ahead of you moves your registration earlier, and a round only releases launches when someone executes them.
- The queue schedules the creation of launches. It does not control trading. Once a token is live, anyone may buy or sell it under that token's own rules.
- You can cancel your own registration while it waits. Cancelling gives up its place in line and makes everything the registration holds claimable by you.
3. Registering a launch
A standard registration needs your wallet to hold at least 1,000 $BEACON. The queue takes exactly that amount into the registration when you register, and the same amount comes back to you once the registration resolves, whether it launched, was cancelled or failed. It is held, never spent and never taken.
You claim it back yourself, with the claim button on the queue page or by calling claimBeacon on the queue contract. Nobody can claim it for you, and nobody else can move it.
- A registration also needs an X account you prove is yours, by publishing a post that carries a one-time code or, where the site offers it, through X's own sign-in. BeaconHarbor stores the account id, the username, the verified type and the profile picture, and never sees your X password. A verification post is public on X for as long as you keep it, and you can delete it once the account is bound. One X account belongs to one wallet at a time.
- One open registration per wallet, and one per X account.
- There is no registration fee. You pay the network gas for your own transactions, in USDC.
- A dev buy is optional. The USDC for it waits with your registration and is spent inside the launch itself, on the same curve and under the same max wallet as any other buyer. If the registration does not launch, that USDC is claimable in full.
4. $BEACON launches first
$BEACON is the first launch on BeaconHarbor, registered by the founder wallet written into the queue contract. It runs on the same curve, with the same token type and the same tax choice open to every launch. The ticker BEACON is reserved on-chain, so nobody else can launch it, and standard registrations stay closed until $BEACON is trading.
Genesis holds no $BEACON, because the token the holding rule names is the one being created. Every other rule is the one everybody else gets.
5. Token type and tax
Each launch picks its token type when it registers. A Normal token has 0% tax on both sides, so the protocol earns nothing from it. A Tax token carries a buy tax and a sell tax between 1% and 10% a side, chosen by the creator and shown on the token page before you trade.
On the curve the pool contract collects the tax on every buy and every sell. After graduation BeaconHarbor's hook contract collects it on every swap in the token's Uniswap v4 pool, always in USDC. Both split it 70% to the creator-fee address named at registration and 30% to the protocol treasury, and both shares are claimed in USDC from the contract that collected them. Once a token is launched, nobody can change its tax, the creator and BeaconHarbor included.
6. What the contract enforces
- Max wallet: while a token is on its bonding curve, no address may hold more than 0.5% of the launch supply. The share is measured against the launch supply, so the graduation burn does not change it, and there are no market cap tiers.
- The token contract checks the max wallet on every transfer, not only on buys. It ends for good at graduation: on Uniswap v4 there is no max wallet, and anyone may buy any amount.
- Per block: while a token is on its curve, one block can sell at most 3 times the max wallet in tokens, 1.5% of supply, counting every buy from every wallet in that block, the dev buy included. Sells are never limited, and the budget ends at graduation.
- No presale. The dev buy happens inside the launch transaction, on the same open curve, priced by the same formula with no discount and under the same max wallet, and it is labelled on the token page.
- Liquidity cannot be pulled, on the curve or after it. On the curve the raised USDC stays in the pool contract and leaves only through sells, or into the Uniswap pool at graduation. At graduation the pool keeps exactly the tokens the last curve price needs, burns the rest, and BeaconHarbor's graduator contract moves the raised USDC and those tokens into a TOKEN/USDC pool on Uniswap v4 at the same price, as one full-range position that the graduator contract owns and has no function to remove. There is no withdraw path and there are no LP tokens to hold or to sell. The Uniswap pool's own fee is zero, and the only charge on a swap is the tax described in section 5.
- Mint authority is renounced, so the supply cannot grow.
These are enforced by the contract, not promised by us.
7. Who can change what
The launchpad owner binds the graduator contract once, before the first launch, and can never replace it. The owner can propose new curve parameters for future launches and a new treasury address, and each takes effect only after a 24 hour timelock. A new treasury receives the protocol share of later launches and of every claim from the hook contract made after it takes effect. The queue owner can rotate the signer that issues registration permits, also after 24 hours, and can raise the gas the queue hands to a launch, up to a cap written into the contract. It can also remove that signer immediately, which stops new registrations and changes nothing about the registrations already in line.
Nobody can reorder the queue, take what a registration holds, change the tax of a launched token, mint new supply, or move liquidity out of a curve pool or out of the Uniswap v4 position. Those powers do not exist in the contracts, and the graduator and the hook contract have no owner at all.
8. What we do not promise
- Nothing on BeaconHarbor is financial, investment, legal or tax advice. No price, no profit and no partnership is promised anywhere on this site. Graduation onto Uniswap v4 is what the contracts do, not a promise, and no listing or exchange beyond it is promised. You are responsible for your own decisions and for the laws that apply to you.
- No audit exists. The contracts have not been reviewed by an outside security firm. Read them before you send real money.
- A registration can fail. If the launch transaction reverts, the registration resolves as failed and everything it held becomes claimable. A place in line is not a promise that a launch will succeed.
- Smart contracts, RPC endpoints and third-party wallets can fail. Tokens launched here can lose all of their value.
- On Arc, tokens and balances are real assets that can go to zero.
9. What you publish
The name, ticker, description, artwork, links and posts you submit are public. The metadata document is served publicly by BeaconHarbor and its address is written on-chain with the launch, so a launch record cannot be edited or deleted afterwards. You confirm you hold the rights to anything you upload. You keep ownership of your content and grant BeaconHarbor a licence to display it.
We can hide content on this site and restrict accounts that are illegal, deceptive, infringing or abusive. Removing something from this site does not remove it from the chain, which nobody controls.
10. Prohibited use
- Impersonation, fraud, or tokens built to mislead buyers.
- Infringing intellectual property, or uploading unlawful content.
- Market manipulation, exploiting the contracts, or attacking the platform.
- Registering with an X account you do not control, or selling a proven account to someone else.
- Using BeaconHarbor where the laws that apply to you prohibit it.
11. No warranty and limitation of liability
BeaconHarbor is provided as it is, without warranties of any kind. To the maximum extent permitted by law, BeaconHarbor and its contributors are not liable for any loss arising from use of the platform, of the contracts, or of any token launched through them.
12. Privacy
BeaconHarbor is wallet-based. We do not ask for a name, an email or a document to use the product. Your wallet address and your on-chain activity are public by nature. Proving your X account stores your X account id, username, verified type and profile picture, all of which are public on X, and BeaconHarbor never receives your X password. You can unlink the account at any time.
Everything the public API returns is listed on the API and developers page. API and developers
13. Changes
These terms may change as the protocol changes. Material changes are posted here, with the date.
Note These terms are written in plain language by the BeaconHarbor team, and they have not been reviewed by legal counsel yet.