Platform
Diggers does not ask you to trust anyone, because there is nothing to trust anyone with. This page is the complete threat model: every way meme coins have historically robbed people, and what makes each one physically impossible here.
| The classic rug | On Diggers | Why |
|---|---|---|
| Pull the liquidity | ✕ | no withdrawal function exists |
| Mint new supply and dump | ✕ | no mint function exists |
| Pause trading, trap holders | ✕ | no pause switch exists |
| Upgrade to malicious code | ✕ | no proxy, no upgrade path |
| Blacklist or seize balances | ✕ | no admin over balances |
| Honeypot: buys only, no sells | ✕ | sell path is core, immutable |
| Drain via old approvals | ✕ | sells need no approvals at all |
| Snipe supply early | ✕ | 2% cap per wallet until graduation |
| Block the fee split (griefing) | ✕ | pull fallback pays around it |
Each row is worth reading twice, because the answer is never "the team promises not to". Liquidity cannot leave because the launchpad is the pool's only LP and has no withdrawal code. Supply cannot grow because no mint exists and burning only shrinks it. Sells cannot be blocked because approve-free sellingis part of the token's own transfer logic: only the launchpad and the vesting locker can move your tokens without an allowance, and that power is strictly narrower than a normal approval, never broader. The only admin powers in the entire system are the two per-coin config keys, and neither can touch a holder's money.
The protections stack. The 2% whale cap guards the pool from launch until graduation, then lifts for good. Pool-legs-only telemetry makes holder counts and points sybil-resistant. Pull-payment fallbacks in the harvest mean no recipient can hold the others hostage. Vesting runs through the standalone DiggersLocker, ID-based and approve-free, not a discretionary escrow anyone can drain. And every coin runs the exact same audited code: there is no per-coin contract for a scammer to customize with a hidden trapdoor.
One final property ties it together: the machine does not need Diggers to exist. If the website went dark tomorrow, every pool would keep trading through any DEX interface, every contest would keep settling on the first trade past each deadline, every harvest would keep splitting fees, and every lock would keep vesting on schedule. Every one of those actions emits an event from the hub, so anyone can rebuild the full state from the chain itself. The site is a window. The mine is on-chain.
By removing the functions rugs need. Liquidity has no withdrawal, supply has no mint, trading has no pause, contracts have no upgrade path, and no owner has power over balances. Each classic rug vector is structurally absent rather than merely promised away.
No. Coins are gas-cheap clones of one immutable implementation, and the launchpad itself has no proxy and no upgrade mechanism. Code deployed on day one is the code forever.
Market risk (most meme coins go to zero), smart contract risk inherent to any code, and infrastructure risk in the chain and DEX layers. Diggers removes specific technical rug vectors; it does not remove volatility or guarantee any coin's success.
No. It activates only when the wallet whose tokens move is the same wallet signing the transaction, and only inside the sell flow. It is strictly narrower than the unlimited approvals other DEXes require.
Yes. The contracts are source-available on-chain, every mechanic (burns, pots, harvests, graduations, buybacks) emits events from the hub, and every number the site shows is reconstructable from public chain data.