Token gates
Launch a token with the drop, and let it decide who may mint.
A gated collection requires the payer to hold a set amount of an ERC-20 before they can mint. The token can be one you already have, one launched somewhere else entirely, or one you launch in the same session.
Launching the token
The launcher is Pons, which already exists on this chain and does the whole job in one transaction: deploys the token, opens its bonding curve, and buys you in. We did not write a competing launcher, because that would leave you with a market nobody trusts and us owning an AMM we do not need.
A token launched today has no Uniswap pool yet. It trades against the curve's virtual reserve from the first block, and it graduates to a real pool once the curve has taken in enough. That is a real difference from the way this page described it before 15 August, when Pons still pooled and locked in the launch transaction.
| Supply | 1,000,000,000, fixed |
| Trades on | A bonding curve, from the first block |
| Graduates to Uniswap | Once 4.2 ETH has gone into the curve |
| Curve fee | 1% of each trade, of which your cut is 1% |
| Launch fee | 0.0005 ETH, paid to Pons |
| Anti-snipe | 99% tax on the first three seconds |
The address is CREATE2, so the interface shows you the address you are about to create before you sign — it gets it by simulating the launch, which means the address only appears once the whole transaction is known to work. Two transactions in order: the token, then the collection pointed at it.
One rule worth knowing before you fill the form: a launch has to buy something. Pons refuses a launch whose buy is zero, so the amount in Buy at launch cannot be left empty.
Charging the mint in your own token
A gate on its own gives the token one job: opening a door. Holding it lets somebody mint, the mint is paid in something else, and nothing about the drop ever consumes the token.
So a collection can price its mint in the token it is gated on, and send a share of every payment to the dead address as it is paid. A collector has to go and buy the ticket to get in, and buying it is what takes it out of circulation. The demand and the removal are the same event.
| Priced in | the collection's own gate token |
| Destroyed per mint | whatever share you set, up to the whole payment |
| Set | once, at launch. There is no function that changes it |
| Paid to you | the remainder, direct from the collector |
The factory allows this for exactly two currencies: $NIGHT, or the collection's own gate token. A drop gated on one token and priced in another could destroy a token its collectors never had to touch, which is the value destruction the rule exists to prevent.
The contract guarantees the tokens are gone and that the share cannot be changed afterwards. What a smaller supply does to what the rest of them trade for is a separate question with more than one input, and nothing here claims to answer it.
How the gate behaves
- It checks the payer, not the recipient. A holder can mint one for a friend who holds nothing: the same honesty as the per-wallet limit, and the alternative is a gated drop whose holders cannot introduce anybody to it.
- It fails closed. If the token's
balanceOfcannot be read, the mint stops. A gate that opens itself when a call reverts sells the drop out from under the holders it was promised to, and nobody notices until afterwards. - It can be lowered, never raised.
relaxGateonly accepts a smaller number. Raising a gate after people bought the token to clear it would be selling a ticket and then moving the door.
Keep enough of your own token to clear your own gate. The launch buy is the amount you send above the fee, and a creator holding nothing cannot mint from their own drop.