Questions, answered straight
What people actually ask, with the rule behind each answer. The full mechanism is on Mechanics, and the live line is on the queue page.
Why a queue at all?
Because a launchpad where everyone can deploy in the same second turns into a race, and the winner is whoever runs the fastest bot. Here every launch takes a number on-chain and goes in that order, at most 5 in each round of 60 seconds. The order is a number anyone can read, nobody can pay to move up, and the platform cannot reorder it: the contract only ever accepts the head of the line.
Why do I have to hold 1,000 $BEACON to register?
It is the one filter on the line. A place in the queue costs nothing, so without a holding rule a script could take every slot for free. 1,000 $BEACON moves into the queue contract when you register, where it is held, never spent and never taken by anyone. It is not a fee and not a purchase.
When do I get the 1,000 $BEACON back?
As soon as your registration ends, whichever way it ends: launched, cancelled or failed. You claim it back with one transaction from My launches on the queue page, and it pays the full amount once. The same button returns any dev buy USDC your launch did not spend. Only the wallet that registered can claim, and nothing in the contract lets BeaconHarbor move either amount.
Why does BeaconHarbor want my X account?
So that a launch carries an identity someone can be held to, and so that one person cannot hold ten places in line at once. You prove the account by publishing a post from it that carries a one-time code from the site and pasting the link. BeaconHarbor reads that public post to learn which account wrote it. Where the site offers X's own sign-in instead, BeaconHarbor asks X to read the profile and nothing else. Neither way lets BeaconHarbor post, follow or message from your account, and no password is stored. You can delete the verification post once the account is bound. One wallet binds one X account, and one X account can hold one open registration.
Do I need a verified X account?
No. If the account carries a badge it is shown as information next to the launch, and if it does not, nothing changes. A badge buys no place in the line and no priority.
How long will I wait?
Count the registrations ahead of you and divide by 5 for the number of rounds, at 60 seconds a round. The form and the queue page both show an estimate, and it is labelled an estimate on purpose: a cancellation ahead of you moves it earlier, and a round only launches when someone runs it.
How do I register a launch?
Open the registration form and work through six steps: identity, deployer and socials, tokenomics, tax, launch and review. Your wallet signs once to prove itself, then one transaction puts you in line, plus an approval first if you hold a dev buy. There is no registration fee. You pay network gas in USDC for your own transactions.
What does it cost to launch?
No registration fee exists in these contracts, and there is no paid lane beside the queue. You pay network gas in USDC for your own transactions, the 1,000 $BEACON you get back, and whatever you choose to spend on a dev buy. If your token carries a tax, 30% of it goes to the protocol treasury and 70% to your fee address.
Can I cancel, and what do I get back?
Yes, any time while your registration is still waiting. Cancelling gives up the place in line, and both the 1,000 $BEACON and the whole dev buy become claimable. A cancelled registration at the head is cleared by the next execution without using a slot in that round, so it never blocks anyone.
What if my launch fails when its turn comes?
Then nothing is created: no token, no pool. The line moves on, the round keeps its slot, and the 1,000 $BEACON and the whole dev buy stay claimable by you. The queue checks at registration that the request can actually launch, so this is rare, and a dev buy that would revert inside the launch is refused before it takes a place in line.
What happens if the keeper is down?
Launches keep happening. Execution is permissionless: BeaconHarbor runs a keeper as a convenience, but the contract checks the order and the round itself, so any wallet with an RPC can run the head of the line, including your own. the queue page shows a button for it when nothing has run for a while. Running a launch gives the runner no place, no priority and no fee, so the queue cannot be held hostage by a server.
What if my $BEACON balance changes after I register?
It cannot drop below the rule, because the 1,000 $BEACON is not sitting in your wallet any more. It moves into the queue contract at registration and comes back when the registration ends. Anything else you hold is yours to trade freely, and it changes nothing about your place in line.
My registration did not launch this round.
A round holds 5 launches. When it is full, the next one goes in the next round, which starts at the next 60 second boundary of block time. Nothing is lost and no place changes. A round also does not wait to fill up, so an empty round simply passes.
Can someone launch another $BEACON?
Not on this launchpad. The ticker BEACON is reserved in the queue contract: genesis is the only registration allowed to use it, and every other one is refused on-chain. The real $BEACON is the token and pool the genesis launch recorded in the contract, which is where the site links every mention of it. Anything with that ticker from somewhere else was not launched here.
My buy failed with block full. What does that mean now?
That is a trading rule, not a queue rule. While a token is on its curve, each block can sell at most 3 max wallets' worth of it, which is 1.5% of supply. Every buy in that block counts toward it, from every wallet, the dev buy included, and it counts tokens rather than wallets, so a swarm of tiny buys cannot fill a block. Your buy did not fit in what was left. The site retries in the next block a few times. Selling is never limited, and the budget ends at graduation.
What is the max wallet?
The most one address may hold while the beacon is on its curve: 0.5% of the launch supply. The token contract checks it on every transfer, so a second wallet does not get around it, and the share is measured against the launch supply, so the graduation burn does not move it. There are no market cap tiers and nothing widens it on the way up. It ends at graduation: on Uniswap anyone may buy any amount. It is per address, not per person: it stops one wallet from taking a launch, not a determined actor with many wallets.
What does the tax pay for, and can it change?
A Normal token has no tax at all. A Tax token carries a buy tax and a sell tax its creator chose between 1% and 10% a side, shown on the token page and on the explore cards. On the curve the pool collects it on every trade. After graduation BeaconHarbor's hook contract collects it on every Uniswap swap, always in USDC, on a buy from the USDC paid and on a sell from the USDC received. Both pay 70% to the creator's fee address and 30% to the protocol. It cannot change after launch: none of the contracts has a function for it, so a tax can never be raised on people already in.
Can the dev dump on me?
A dev can hold at most what the max wallet allows while the token is on its curve, 0.5% of supply, bought on the same open curve, priced by the same formula with no discount and taxed like your buys, inside the launch transaction, and labelled on the token. There is no presale and no team allocation to dump. Selling walks the same curve down like any other sell and pays the same sell tax. After graduation the cap ends for everyone, the dev included, and every sell on Uniswap still pays that tax.
What is graduation?
When a curve has raised 6,000 USDC it closes, inside the buy that fills it. The pool keeps exactly the tokens the last curve price needs, burns the rest, about 11% of supply with this launchpad's numbers, and BeaconHarbor's graduator contract moves the raised USDC and those tokens into a TOKEN/USDC pool on Uniswap v4, opened at exactly the price the curve ended on, so the price does not jump. The liquidity goes in as one full-range position owned by that contract, which has no function to remove it, so nobody can pull it. From then on the token trades on Uniswap, the site trades it through its own router, the max wallet and the block budget are over, and a creator's tax keeps applying in USDC through the hook contract. The diagrams are on Mechanics.
Why Uniswap v4?
A graduated token needs two things: liquidity nobody can pull, and a tax that keeps paying its creator. Uniswap v4 does both on-chain. A v4 pool can carry a hook contract, and BeaconHarbor's hook takes the creator's tax in USDC on every swap, on a buy from the USDC paid and on a sell from the USDC received, so the tax is never taken in the token and never needs converting. The liquidity is one full-range position owned by the graduator contract, which has no function to remove it, so the lock is code, not a promise. The pool's own fee is zero. And because this is Uniswap's own deployment on Arc, any Uniswap interface or aggregator can trade the token, and DexScreener picks the pool up by itself.
How do I connect to Arc?
Press Jump Arc L1 at the top right and pick your wallet. BeaconHarbor adds and switches the network for you, with chain id 5042 and the RPC included, and gas is paid in USDC. There is nothing to type by hand.
Do I need a separate gas token?
No. Gas on Arc is USDC, paid from the same balance you trade with. The trade panel shows what gas costs right now, keeps that amount aside when you press MAX, and tells you before you sign if a buy would leave nothing for gas.
Why does my wallet show more decimals of USDC than the site?
Arc keeps one USDC balance with two views. Your wallet reads it as the native gas token, which has 18 decimals. The ERC-20 interface the curves use, and this site, read it with 6 decimals. Same money, one balance. Amounts smaller than 0.000001 USDC only show up in the 18 decimal view.
My transaction failed, or the price moved.
Every trade carries a slippage floor you set on the token page. If the curve moves past it before your transaction lands, the contract refuses the trade instead of filling you at a worse price. Nothing is charged for a refused trade except gas. Try again with a fresh quote.
What is not built yet?
The contracts do not implement holder rewards, burn from tax, automatic liquidity or buybacks, so the form offers none of them. A graduated token trades on Uniswap v4 and appears on DexScreener by itself, and beyond that no listing is promised. The queue keeps an ineligible status that nothing in this version can reach, because the $BEACON is held from the moment you register. The site marks a token as split supply only when it can prove it, which needs a transfer graph the indexer does not build yet, so that label stays off real data. And there is no audit.
Has any of this been audited?
No. The contracts have not been audited. They are tested, rehearsed against a real chain and readable on Developers, and none of that is an audit. An unaudited contract is a risk to price in before you put real money on a curve, and we will say so here until the day a report exists to link.
Why can I not post in the Harbor?
Posting rights are read live from your wallet's portfolio value, so they are earned rather than claimed, and your rank with the threshold of every rank is listed on your harbor profile. Liking, commenting and reposting need only a small holding in any beacon. A launch gets one launch post, published automatically when the registration executes, so you do not have to be at the screen when your turn comes.
What do light points get me?
An honest answer: they are an on-chain record of what you actually did, and what they become is decided in public. We promise no airdrop. The full story is on Lightkeeper.
Is my data private?
BeaconHarbor is wallet-based: no email, no password and no KYC to use the core product. Your address and your on-chain actions are public by nature. The X account you connect is shown with your launch, which is the point of connecting it, and BeaconHarbor keeps your profile name, handle and avatar, never a password. See Terms.
Is this real money? Is it safe?
Yes, it is real money, and no launchpad is safe in the sense of a promise. Every token here can go to zero. What the contracts do enforce is mechanical and checkable: fixed tax, a max wallet on the curve, no presale, liquidity locked at graduation, fixed supply and the order of the queue, each one a public read listed on Developers. The audit answer above is part of that picture.