Paguro

Flow

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

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.