How it works
Five things worth knowing.
The supply goes in once and stays
A launch mints a thousand million tokens and puts every one of them into a single position on Rhea, the exchange NEAR actually trades on. The position sits entirely above the opening price, which is what makes the launch one-sided: no NEAR goes in with it, and every coin that ever comes out of that pool was paid in by a buyer.
The position is handed to a contract whose source contains no function that removes liquidity. The word appears once, passed a zero, because zero is how Rhea pays out the fees a position has earned while leaving the position alone. The amount is written into the contract rather than handed to it.
The fee is yours to shape
Between one and five percent on every trade, buys and sells alike. You decide what share goes to your own wallets, what share buys the token back and burns it, and what share reaches the people holding. Up to three wallets can share the creator's cut, in whatever proportion you set.
The split is fixed when the token is made. Nobody can change it afterwards, including us.
At one percent the token is bare
Rhea's pools stop at a one percent tier. A launch that wants no more than that sets no fee of its own: the pool takes it, and the token is a plain NEP-141 with nothing unusual in it at all.
Above one percent the token carries the difference itself, taken only when the exchange is on one end of a transfer. Wallet to wallet costs nothing. The rate is written into the token at birth and there is no function anywhere that changes it.
Holders claim, we do not push
On NEAR an account has to be registered on a token before it can be paid in it, and registration costs storage. Pushing a payout to three hundred holders would mean paying three hundred registrations in advance and watching the ones that fail fail quietly.
So rewards wait to be claimed. A holder who claims registers themselves in the same breath, and a cycle can never half land. Unclaimed rewards stay claimable; nothing expires.
What we can do, and what we cannot
We can add a pairing asset, point new launches at a new build of the token contract, and stop new launches. That is the list.
We cannot reach a launch that already exists, its pool, its liquidity or anyone's tokens. A launched token has no access key on its account at all: it is created, its code is set, its constructor runs, and after that nobody can deploy over it or call it as an owner. Not the creator either.
Read it yourself
- Factory
- handspan.testnet
- Locker
- lock.handspan.testnet
- Exchange
- dclv2.ref-dev.testnet
Every contract is open and verifiable on chain. The claims on this page are ones you can check rather than ones you have to take.