Paguro

One crab. One shell.

Flow

Part of the fee is saved up and added to the pool's own liquidity position, which is locked.

Live Its contract is deployed and the hook uses it.

What it is for

Part of every fee is saved up and added to the pool's own liquidity, so that later trades meet a deeper pool.

How it works

The savings build up in ETH until they pass a set amount. Then one batch is processed: part of the ETH buys PAGU so that both sides match the position, and both are added to it. A batch uses exactly that set amount; anything above it waits for the next one.

A batch does not happen by itself. Someone has to call the function that processes it. A keeper does that on a timer, and anyone else may do the same: the call needs no permission and has no destination to choose.

Batches are at least a minute apart, and the purchase inside one follows the same rule as the burn: only while PAGU is at most about 3% dearer than its recent average.

The position belongs to a vault contract with no function for taking liquidity out. It can only add.

Where it stops

Readings

The pool position

Position
number 508510
Locked in the vault
Yes
The position can be taken out
Never
Added to the position
0 ETH and 0 PAGU
Spent buying the token side
0 ETH
Batches added
0
Saved for the next batch
0.000012 ETH and 0 PAGU
A batch is added at
0.001 ETH
Next batch ready
No
Next batch no earlier than
Unavailable
The hook buys tokens at the current price
Yes
Anyone else can add liquidity to this pool
No, not while the position is locked

Read at block 133,854,953, mined 2026-10-12 22:29:08 UTC. Checked 2026-10-12 22:29:12 UTC. Block hash 0x15585c8edbad80ec14a11e25516920d4888a93dfd6bde887a34d4a6ca07652a1.

Sources

Before you rely on any of this