Launching
A locked bag on Diggers is not a promise in a pinned message. The coins sit in the standalone DiggersLocker, a single immutable contract shared by every coin, and they unlock on a fixed schedule that nobody, including the team, can accelerate or revoke.
Every lock is a schedule: a total amount, a duration, and a number of equal tranches. One tranche makes it a cliff, four make it a staircase. Coins unlock in equal steps as time passes. Nothing unlocks early and no admin can accelerate or revoke the schedule. When a tranche's moment arrives, that slice becomes withdrawable and anyone can trigger its release.
Enforcement is physical, not a promise. The locked coins leave the wallet and sit in the DiggersLocker until they vest. When a tranche's moment arrives, that slice becomes withdrawable, and anyone can trigger the withdrawal, but the coins can only ever land back in the lock's own wallet, never anywhere else. Before a coin graduates the withdrawal still respects the 2% cap, so a lock can only release up to your remaining headroom; once the coin graduates the cap is gone and the full vested amount flows.
At launch: any wallet in the initial buy split can be locked in the create transaction itself. Later, with transfer-and-lock: send tokens to someone with a vesting schedule attached in one move, perfect for paying contributors. Later, with buy-and-lock: buy from the pool and lock the output in the same transaction, ideal for a creator topping up their committed position.
| Diggers locker | Typical escrow | |
|---|---|---|
| Locked supply equals the locker's balance | ✓ | hard to verify |
| Funds only ever return to the lock's wallet | ✓ | ✕ |
| Immutable schedule, no admin unlock | ✓ | ✕ |
| Approve-free, no allowance to grant | ✓ | ✕ |
| Anyone can trigger a vested withdrawal | ✓ | usually a claim |
| Multiple ID-based locks per wallet | ✓ | ✕ |
A typical escrow spins up a fresh contract per project, each one its own codebase to trust, and usually needs the beneficiary to grant an allowance and file a claim. Diggers routes every lock through one shared, immutable locker. It is approve-free: the locker moves coins only from the wallet that signed the outer transaction, so there is no allowance to grant and no phishing surface. Its balance of any coin is that coin's locked supply, full stop.
A lock is a position in the standalone Diggers locker: it escrows a wallet's tokens and releases them in equal tranches over a chosen duration. Until they unlock, the tokens sit in the locker, and the locker's balance of a coin is exactly that coin's still-locked supply — verifiable on-chain.
No. Locks are immutable once created: no admin, including the coin's creator, can shorten, extend or delete one. The schedule you see is the schedule that happens, and only the lock's own wallet ever receives the unlocked tokens.
A single lock call can register up to 100 positions, and a wallet can hold multiple independent locks on the same coin. Locks are set at launch through the team split, or later with transfer-and-lock and buy-and-lock.
Yes, up to the cap. Before a coin graduates, the 2% anti-whale cap still applies to your wallet, so the locker lets you withdraw unlocked tokens up to the headroom you have. Once the coin graduates the cap lifts and you can pull everything that has vested.
Two ways to create a lock after launch: transfer-and-lock escrows your own tokens for someone under a vesting schedule, and buy-and-lock buys from the pool and locks the output for a recipient, both in one transaction.