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
- What has been added stays added for as long as the vault is locked. The reading beside this text says whether it is locked now, and whether that lock can ever end. That was fixed when the vault was deployed: either never, or from one stated time on, by one stated address.
- While the position is locked, nobody else can add liquidity to this pool. The hook refuses it. The locked position is the pool's only liquidity.
- If the lock has an end, from that time on this part of the fee goes to Ebb instead.
- Between batches the savings sit idle. If nobody makes the call, or the price is above its average, they wait. That is a delay, not a loss.
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
- The figures as JSON: /api/stats.json
- This page with JavaScript: /functions/liquidity
- The hook: 0x39fa481754A3Aa4198Cd367d93d153788e9668cC
Before you rely on any of this
- The hook's code is fixed: it cannot be replaced, so a fault cannot be repaired. The fee-sharing programs and the token's name can change after the public delay.
- The token itself cannot be upgraded, minted or frozen. Only its name and ticker can change.
- The launch liquidity position is locked in a contract that can only add to it.
- No independent security audit has been completed.
- Nothing here is investment advice. You can lose everything you put in.