A treasury owns the pool. The page calls it permanent liquidity. Owned is treated as stuck. The composition of the pair is not.
Protocol-owned liquidity can replace hired LP for a while. It can also be a bag of the same token on both sides of the pair, dressed as a reserve. I read a POL page the way a pantry is read: whose name is on the jar, and what is actually in it.
- Owned liquidity is the first reading
- A bond is a purchase, not a resident
- The reserve that is the same token
- Log I kept for a pool called HEARTH
- A pool the protocol actually holds
- Count the pair before you call it owned
Owned liquidity is the first reading
The problem is easy to name. Hired LP leaves when the reward ends. POL tries to buy the pool so the protocol holds the LP token. The first reading treats that holding as a floor that cannot walk. LP tokens can still be pulled. A pair that is mostly the native token can still thin out.
Is the first reading always false? No. A treasury that holds LP in an outside unit — a fee coin, a widely used stable unit — and does not spend that LP for emissions is a different object. The first reading fails when the “reserve” is the same token minted to buy the LP, when bonds pay a premium in native units, or when owned LP is later sold to defend a number on a card.
My claim is narrow. Ownership is a name on the LP token. Durability is a later fact: the pair still has an outside unit, and the treasury still holds the LP. Mixing them turns a deed into a wall.
Opinion, not a law for every design: “we own the pool” is a costume. The two sides of the pair are the room.
A bond is a purchase, not a resident
Many POL designs sell native tokens at a discount for LP shares or for an outside unit. The buyer is paid in the native token. The treasury receives LP or reserve. That is a purchase. It is not proof the buyer will stay as a user.
Question I keep on the page: what did the treasury receive, and what did it print to receive it? If it printed more native units than the outside unit it took in, the pantry grew in name and thinned in mix.
Exception: a bond that only accepts an outside unit and holds that unit, without flooding the pair with native emissions, is closer to a reserve. Write the incoming unit. Do not paste that case onto a mint-heavy bond.
The reserve that is the same token
A pool is two assets. If both sides trend toward the native token — through mint, through buybacks of the outside unit, through a reserve that is itself a receipt for the native token — POL is a mirror. Mirrors do not hedge the native token.
Observation from public explorers: I have opened a treasury address, found LP tokens, and opened the pair. One side was the native token. The other side was a receipt that redeemed into the same token. That pairing is a fact on two contracts. It is not a biography of every POL attempt.
Condition: if the outside unit can still be redeemed from a solvent hook, write that. If the hook is the same system, the pair is not outside.
Log I kept for a pool called HEARTH
I keep a log for a made-up pool I call HEARTH. Week one: treasury holds LP worth 40 units of an outside coin plus 40 of HEARTH. Bonds print 15 HEARTH a week to buy more LP. Week eight: the pair is 90 HEARTH and 12 outside. The page still says “protocol owned.”
Question in the margin: what was owned? Answer I could defend: LP tokens, yes. A balanced outside reserve, no. The deed stayed. The pantry mix did not.
Was I looking at a live book? No. HEARTH is a page. The experience was watching the outside side shrink while the label stayed proud. A reader can repeat that watch on any public pair without taking a position.
Exception I left beside the log: if HEARTH stops the mint and the 12 outside remains, the owned LP is a small, real hook. Until the mint stops, the label is ahead of the mix.
A pool the protocol actually holds
The first reading works when the treasury still holds the LP, when the other side of the pair is an outside unit that can leave the system, and when emissions used to buy that LP have stopped or fallen under fees. It works for that window.
It fails when owned is treated as permanent because the noun sounds like a vault. It fails when a second bond round is called depth because the LP count went up.
I do not treat a thinning pair as a command to act. I treat it as a reason to keep the deed and the mix on two lines.
Count the pair before you call it owned
The solution that holds under the conditions above is a short count, not a slogan.
Write who holds the LP token. Write both sides of the pair and their units. Write how many native tokens were minted to acquire that LP. Write whether the treasury can pull the LP. If a page will not show the pair, the “permanent liquidity” sentence is not ready to stand.
If the dashboard and the pair contract disagree, say so and stop before owned becomes certain.
The spare thought on the desk is small. A deed can be real. The jar can still be the same token twice. I count the pair first. I do not call the pool a wall because the first reading stopped at the name on the lid.
The articles on this site are not investment recommendations or financial advice. They are structural analysis based on on-chain data and project documents.
Comments
Post a Comment