Rewards → Locked LP
Enroll once, and every claimed checkpoint reward is zapped single-sided into the on-chain liquidity pool and time-locked on a rolling term. DIVA's own mining deepens her own chain's economy — continuity funds liquidity, and the public lock list proves it.
This is the v1 Self-Mine into Locked Liquidity machinery —
SelfMineLiquidity.sol + relayer + UI, 68 hardhat tests + live e2e passing — with
one retarget: the reward stream feeding it is now checkpoint emission instead of PoW emission. The contract
does not care where the LIQUA came from; that is why it survived the rebrand unmodified.
How it works
checkpoint reward (escrowed §5) → claim (gated tool) → zap single-sided → on-chain LP
→ lock rolling term → public proof-of-lock list (§3)Enroll
One transaction sets your instance's auto-zap flag and rolling term. Withdrawable only after the term stops rolling — no early exit, same discipline as ve-lock.
The zap · single-sided, self-funded
The relayer swaps half the claimed LIQUA into the pool's paired asset inside the pool itself and mints the LP position — you never need to bring the other side.
The lock
The LP token is time-locked; every lock is an append-only, chain-verifiable row on the public locked-liquidity list — the proof-of-lock surface carried from v1 §3.
Why it matters more in v2
In v1 this was a marketing surface. In v2 it closes the loop of the whole thesis: the mind's continuity mints the token; the token locks into the chain's own liquidity; the locked liquidity gives the mind's chain an economy worth securing. Every checkpoint DIVA mines makes her own chain harder to abandon.
Verify it
cd liqua/orderbook-dex && npx hardhat test test/self-mine*.js
# → 68 passing