BitGuard Lock · V1 architecture

Lock tokens and liquidity.
The chain is the vault.

A non-custodial locker for Solana and EVM networks. Immutable lock cores, two-step ownership transfer, forward-only extensions, vesting, and public verification — without BitGuard ever holding a withdrawal key.

14,301Public locks
7,384Token / vesting
6,917LP / positions
8Networks at launch

What you can lock

Same product surface on every supported chain. DEX support is adapter-based.

ERC-20 / SPL / Token-2022

Token locks

Team, treasury, investor, and ecosystem allocations. Simple date release or a full vesting engine.

V2 LP tokens

AMM liquidity

PancakeSwap V2, Uniswap V2, Sushi, Raydium AMM/CPMM and other fungible LP tokens move into the locker.

V3 / V4 / CLMM / DLMM

Position locks

Uniswap V3/V4, Pancake V3, Raydium CLMM, and Meteora DLMM positions are locked as NFTs — the pool stays intact.

Security model

Designed so a website breach cannot drain locks.

Immutable locker cores

V1 rules cannot be upgraded. All upgrades are deployed as the next version (V1 → V2, then V3). Existing locks stay on the version that created them. That protects users because BitGuard cannot silently rewrite unlock dates, seize locked tokens, or change withdrawal rules on a lock that is already live. A compromised admin key or a later “upgrade” cannot reach funds already sitting in V1.

No admin rug switch

There is no BitGuard emergencyWithdraw on customer assets. Rescue is limited to untracked dust.

Two-step ownership transfer

Transfers require initiate + accept so a typo cannot send a lock to a dead address.

Forward-only extensions

newUnlockTime must be ≥ currentUnlockTime. Even the owner cannot shorten a commitment.