- Creator
- 0x0000…00c1
- Beneficiary
- 0x0000…00b2
- Start
- 1 Oct 2026
- Cliff
- None
- End
- 1 Oct 2027
- Schedule
- Linear
Hold your supply.Control the release.
Set the terms. Control the timeline. Explore token locks, vesting and public proof in one clear workspace.
Interactive prototype · Example data · No wallet required
- Approval (exact amount)
- 500,000 EXMPL
- Network fee estimate
- Shown in wallet
- Withdrawable from
- 1 Oct 2027
Give your supply a clear unlock date.
Set aside a token allocation until a fixed date. Give your team, holders and community one clear timeline to follow.
- One fixed unlock date, set before you sign
- The withdrawal wallet is named explicitly
- Withdrawal opens only after the unlock date
A release plan.
Set in advance.
Make team and contributor allocations available over time. Set the start, optional cliff and end, then let each beneficiary claim their vested tokens.
- Beneficiary, start, optional cliff and end date
- Release curve and claimable amounts shown before signing
- Only the beneficiary can claim
- Current total supply
- 1,000,000,000 EXMPL
- Supply contraction
- -1.00% (-10,000,000 EXMPL)
- New total supply
- 990,000,000 EXMPL
- Receipt
- Illustrative preview
Erase the supply.
Prove the impact.
Preview two ways to reduce a token allocation. Native burn() can lower a compatible token’s totalSupply. A transfer to 0x...dEaD moves tokens to a dead sink while the reported total supply stays unchanged.
- True on-chain contraction for ERC20Burnable contracts (totalSupply decreases)
- Canonical dead sink (0x000...dEaD) routing for standard ERC-20 tokens
- Readable receipts with the amount, mechanism and supply impact
- Review the amount and supply impact before any transaction
From allocation
to onchain clarity.
Choose the terms. Review the details. Share a schedule your community can follow.
-
01
Choose token and amount
Choose a standard ERC-20 token and the allocation you want to set aside.
-
02
Set the schedule
An unlock date, or start, optional cliff and end, with a live preview.
-
03
Review and sign
Terms, token address, exact approval and gas estimate, then sign.
-
04
Share the proof
A public page with terms, history and Blockscout links. No wallet needed.
One position.
A public record.
Give holders and beneficiaries a shared view of the allocation, release schedule and claim history. Anyone can read a proof page without connecting a wallet.
- Terms, token and contract address
- Creator, beneficiary and full claim history
- Clear balances and schedule progress
Clear rules. Public records.
Contract addresses, deployment records and review reports will be published here as they become available.
Readable contract rules
Published source will let anyone inspect how a lock or schedule works.
Traceable positions
Each position will link to its contract and transaction history on the explorer.
Independent review
Security review status will be accompanied by a public report when available.
Every allocation.
In clear view.
A closer look at how positions will appear. Filter the examples and open a schedule to see its terms.
No positions match. Try a different name or filter.
Your terminal.
Your controls.
See how the same token workflows could feel in your terminal. This animated CLI preview walks through a sample login, balance, lock and positions list.
- Example login and session flow
- Readable lock and vesting commands
- Full JSON output for scripts and automation
- The same schedule terms as the visual interface
A few things
worth knowing.
The essentials of locks, vesting and public proof.
Can I use KEEL with real tokens today?
This page is an interactive product preview. The schedules and positions use example data. Live contract addresses and deployment details have not been published here yet.
When can locked tokens be withdrawn?
Only after the unlock date, and only by the withdrawal wallet named when the lock was created. Before that date the contract rejects every withdrawal.
How does vesting release tokens?
Tokens vest in a straight line from the start date to the end date. If the schedule has a cliff, nothing is claimable before it. The release curve is shown before you sign, including how much becomes available at the cliff.
How does the Token Burn feature work?
The demo shows two outcomes. Native burn() lowers totalSupply for compatible ERC20Burnable contracts. A dead-sink transfer moves tokens to 0x000...dEaD without necessarily changing totalSupply. This prototype creates no transactions.
Are vested tokens sent automatically?
No. The beneficiary claims them. Vested tokens stay in the contract until claimed, and only the beneficiary can claim.
Which tokens are supported?
Standard ERC-20 tokens on Robinhood Chain. Support for tokens with transfer fees, rebasing or other custom behavior will be documented before launch.
What if the app or indexer is down?
Positions are designed to be recorded in smart contracts. Published contract addresses will let users inspect their terms directly on the explorer, independently of the app.
How do I verify a position?
Open its proof page. It lists the terms, token address, creator, beneficiary, history and contract address, each linked to Blockscout. No wallet connection needed.
Your supply.
A clear path forward.
Give your token a schedule your community can follow. Start with a lock or explore a vesting plan.