The suite
Four instruments, one contract set, one proof page format.
Token locks
Lock any Robinhood Chain token to a date. Every lock mints a public verification page with the amount, the date and the hash.
Vesting
Cliff then linear release for teams and treasuries. The schedule is written on chain, not in a spreadsheet.
Airdrops
Push one token to thousands of wallets in a single pass. Merkle claim or direct send, receipts either way.
Streams
Payroll that moves every second. Start it, top it up, cancel the future without touching the past.
How it works
Three steps, about forty seconds, one flat fee.
Point at the token
Connect a wallet, paste the token contract, set the amount. Sherlock Finance reads the pool and shows you exactly what you are about to lock.
Set the date
Anywhere from 7 days to 5 years. The date is a ratchet: you can push it further out at any time, and nothing pulls it closer.
Share the proof
You get a permanent link and a snapshot hash. Paste it in your pinned post and let anyone re-run the check themselves.
Fees
Flat, in the chain's native token, paid once.
Any amount, any duration. Locking ten million costs what locking ten costs.
One fee for the whole schedule, however many release tranches it holds.
The per-wallet part is gas we pass through at cost, not margin.
Pushing a date further out costs nothing. Neither does anyone checking your lock.
Why flat. A percentage fee charges the projects that lock the most, which is exactly backwards. We charge for the transaction, not for your treasury.
Security
The contract is the argument. Everything here is checkable without asking us.
Zero admin access
No owner function reaches locked funds. Not pause, not migrate, not rescue. The privilege does not exist to be stolen.
Verified and open source
Full source published on Blockscout with matching bytecode. Read it before you trust it.
Extend only dates
The unlock timestamp is monotonic. Every path that writes it requires the new value to be greater than the old one.
Permanent public record
Locks, extensions and releases are events, not database rows. They outlive this website.
The proof page
What the other side sees when you send the link.
PONS / WRHCLockedOne link, no account
Nobody has to connect a wallet or trust a dashboard. The page renders from chain state at load.
The history is on it
If a date has ever moved, the page says so and says which direction. Silence would be the suspicious part.
It re-checks itself
Every proof page carries the exact command to reproduce it against a node you choose. Ours is not the authority.
It outlives us
Locks are events on Robinhood Chain. If this site disappears tomorrow, the proof does not.
The ledger
Every lock written this week, newest first. Nothing here is editable.
| Lock | Token | Amount | Locked | Unlocks | Snapshot | State |
|---|---|---|---|---|---|---|
| #2914 | PONS | 4,200,000 | 2026-07-11 | 2027-07-11 | 0x9f31c0…b7ea | Locked |
| #2913 | CASHCAT | 12,400,000 | 2026-07-11 | 2028-07-10 | 0x41ba7e…03c9 | Locked |
| #2912 | HMM | 1,120,000 | 2026-07-10 | 2031-07-09 | 0xc8d902…1f47 | Extended |
| #2911 | DELTA | 880,000 | 2026-07-10 | 2027-01-06 | 0x77e415…9ab2 | Locked |
| #2910 | PIPEDOG | 31,800,000 | 2026-07-09 | 2027-01-05 | 0x0ac6bb…54d1 | Locked |
| #2909 | TENDIES | 5,400,000 | 2026-07-09 | 2027-04-05 | 0xb3f108…e27c | Extended |
| #2908 | YOLO | 19,900,000 | 2026-07-08 | 2028-01-04 | 0x5d2a91…8f30 | Locked |
| #2907 | AI | 640,000 | 2026-07-08 | 2027-07-08 | 0xee7c33…a915 | Locked |
Inspector
Paste any Robinhood Chain address. It reads the chain, not our database.
Returns every lock touching that token, the share of supply held, the earliest unlock and whether any date has ever moved. Works for wallets you do not control and tokens we have never heard of.
Build on it
Read-only, no key, 60 requests a minute.
Roadmap
Shipped, shipping, and what comes after.
Token locks and proof pages
The core contract, extend-only dates, the public verification page and Blockscout source verification.
Vesting, airdrops, inspector, API
Cliff and linear schedules, Merkle distribution, the address inspector and the read-only public API.
LP pair detection and lock badges
Automatic detection of which pool a locked LP token belongs to, plus an embeddable badge any token page can drop in.
Streams and unlock alerting
Per-second payroll, and a subscription that tells holders before a large lock reaches its date rather than after.
Multi-sig locks and cross-chain proof
Locks that require several signers to extend, and proof pages that resolve for tokens bridged off Robinhood Chain.
Questions
Short answers. The contract is the long one.
Q1What can I lock?
Any token on Robinhood Chain, including LP positions. Paste the contract and Sherlock Finance works out the rest. There is no listing process and no approval queue.
Q2Can a lock be opened early?
No. The unlock timestamp only accepts a larger value than the one already stored, and withdrawal is gated on block time. There is no owner path, no pause, no rescue function.
Q3What does it cost?
A flat fee per lock, paid once, in the chain's native token. No percentage of what you lock. Extending a date and verifying a lock are both free.
Q4How does someone else verify my lock?
Send them the proof link. They see the amount, both dates, the snapshot hash and a one-line command to re-run the same check against the chain themselves.
Q5Lock or vesting, which do I want?
A lock holds everything until one date, then releases in full. Vesting releases continuously after a cliff. Liquidity is almost always a lock. Team supply is almost always vesting.
Q6What happens after the unlock date?
Nothing, until you act. The tokens sit in the contract until the owning wallet withdraws them, and the record of the lock stays public forever either way.