KYP Know Your Presalers

How KYP works

An antidote to the race-to-dump meta: early supply goes to capable, committed hands, enforced by contracts rather than promises.

1

Launcher sets terms

Picks presalers (hashed invites), presale cap (≤ 50%), per-wallet limits, a window of up to 7 days, unlock milestones, TWAP rules, reveal waves and the fee split. The coordinator deploys the token with the full supply minted to itself.

2

Presalers deposit wNEAR

Each invited wallet deposits with its private invite code. Limits and the cap are enforced on-chain; any excess is refunded in the same transaction.

3

One launch transaction

The launcher calls launch. In one promise chain the coordinator prices every fill at the same opening price, sends all presale tokens into the lock, creates the RHEA DCL pool at that price, and seeds it with the remaining supply and all presale proceeds.

4

Market-cap milestones

Anyone can poke the lock to record the pool price and token supply. A tranche qualifies only when the time-weighted FDV over the public window stays above its target, with enough observations and liquidity. Then, after a short delay, every presaler can claim that tranche.

5

Reveal waves

After launch, presaler accounts are revealed on a fixed schedule, smallest first. Reserved slots for bigger names can be bought after launch at the same price and lock on the same terms.

6

Fees flow back

LP positions are owned by the coordinator and can't be removed. Fees and reserved-slot proceeds are split on-chain between holders, liquidity and competitions/bounties.

Why TWAP, not spot

A thin meme pool can be pushed to any price for one block. KYP's lock averages the pool's price over a public window (e.g. 60 minutes, at least 6 observations spaced 5 minutes apart, with minimum liquidity), and qualified milestones only become claimable after a delay. A one-block spike barely moves the average.

What is public, and when

Terms, sizes, slot counts and milestones: from day one. Who was invited: only salted hashes until reveal. Note that deposits are ordinary NEAR transactions, so a determined observer can see depositing accounts on-chain; the reveal waves are what KYP publishes and indexes, not cryptographic privacy.

MVP scope

Runs on NEAR testnet by default (PUBLIC_NEAR_NETWORK switches to mainnet; no mainnet contracts are deployed yet). The site runs in demo mode (a simulated chain in your browser) unless it is built with contract accounts for the selected network, in which case it reads live state and signs writes with the connected NEAR wallet (NEAR CLI commands are shown as a fallback). The pool step targets RHEA DCL's interface; tests run against a mock pool with the same methods.