Proof of lock.
A lock nobody can see does no work. Every record gets a URL that renders current on-chain state, opens without a wallet, and is safe to hand to someone who does not trust you.
The problem it solves#
Telling people your tokens are locked is worth nothing. Anyone can say it. Pointing at a block explorer is technically sufficient and practically useless, because the person you are trying to convince usually cannot read one and should not have to.
A proof page is the middle ground: it states the facts in plain language, and every fact on it is read from the chain at the moment the page loads.
What each page shows#
| Field | Notes |
|---|---|
| Token | Symbol, name and contract address, linked to the explorer |
| Amount | Locked, burned or vesting, in the token's own units |
| Share of supply | The amount as a percentage of total supply, which is usually the number people actually want |
| Unlock or schedule dates | Unlock date for a lock; start, cliff and end for a schedule |
| Status | Locked, unlockable, withdrawn, burned, or the percentage vested and claimed |
| Transaction | A direct link to the transaction that created the record |
The page is generated per record, so the state is never cached into something stale. If a lock is extended, withdrawn or claimed against, the page shows that the next time it is opened. It is a live view, not a certificate issued once.
URL shapes#
| Record | URL |
|---|---|
| Lock | hoodlock.tech/proof/lock/<id> |
| Burn | hoodlock.tech/proof/burn/<id> |
| Vesting schedule | hoodlock.tech/proof/vesting/<id> |
Each also carries a share card, so pasting one into a social post or a chat renders a preview with the token and the amount rather than a bare link.
Where to use it#
- In your pinned post and your docs. The link is the claim; the words around it are commentary.
- In listing and directory applications. Most ask for evidence of locked liquidity, and a URL that a reviewer can open without installing a wallet is the easiest form to supply.
- When someone asks in your community. Answering with a link ends the conversation in a way that answering with a sentence does not.
- In your own interface. If you run a token page or a launchpad, embedding the link next to the supply figures saves your users the question.
Verifying one you were shown#
A proof page is evidence about one record, and there are two things worth checking before you treat it as evidence about a project.
Check the token address, not the symbol. Symbols are not unique and cost nothing to copy.
A proof page for a token called $PEPE is a proof page for whichever contract that page names —
compare it to the address of the token actually trading.
Check the share of supply. A lock of ten million tokens sounds substantial until you learn the supply is ten billion. The page states the percentage precisely so you do not have to work it out.
Verify someone else's lock walks through the full check, and reading holder distribution covers what the rest of the supply is doing.
Token pages#
Alongside per-record proof pages, HoodLock publishes a page per token that clears a quality threshold, summarising every lock, burn and schedule against that token in one place. Those are reachable from the explorer.
Create something worth linking to
Lock, burn or vest — every record gets a page anyone can open.
Open HoodLock →