Token unlocks are cliffs. Glidepath turns them into a glide path anyone can verify.
10b5-1-style selling plans for crypto, verified on NEAR.
Founders and investors commit to how they will sell before they sell. The plan stays sealed inside an enclave, the tokens sit in an account with no keys, and every sale publishes a receipt that proves it followed the plan. Changing or cancelling it waits out a public cooling-off first.
ARB’s March 2024 team and investor cliff, read from the chain, beside the same allocation under a sealed plan.
What a holder can check, without trusting us
- ●The plan account has 0 keys, read live from NEAR.
- ●Which plan is in force: its commitment and when it was made.
- ●The public caps and floor the registry enforces on every sale.
- ●Each sale’s signature, enclave and compliance answers, checked in the browser.
- ●Any pending change, and when its cooling-off ends.
Insider selling hurts holders, even when it is honest
A public schedule gets front-run. A quiet sale cannot be checked. Today insiders have to pick one.
~90%
of more than 16,000 token unlocks studied by Keyrock pushed the price down, often starting about 30 days before the date.
−25%
is the average price move around team unlocks, the worst category in the same study, partly because teams sell without a coordinated plan.
How it works
Architecture, guarantees and limitsStep 1
Seal the plan
The founder writes the plan in the browser. The browser checks the enclave’s attestation, encrypts the plan to the enclave’s key and publishes only a salted hash on NEAR.
Step 2
Lock the tokens
The team allocation is minted straight into a plan account with no keys. Its code obeys only the registry, so nobody, the founder included, can move the tokens directly.
Step 3
Sell inside the limits
The enclave sells at random times through NEAR Intents (1Click). The registry also enforces a public envelope of caps and a floor on every sale, whatever the enclave says.
Step 4
Publish a receipt
Every sale leaves a signed receipt that anyone can check in the browser. Any change to the plan is public and waits out a cooling-off period first.