Robinhood Chain · Uniswap v4 positions · keyless reads
NAME THE POOL.
NAME THE HOUR.
REMOVE AT THE STRIKE.
Liquidity providers coordinate visible exits on this chain. The clock, the pledges and the drain are all on-chain. Each of you removes only your own capital, by your own transaction.
2,642,594 v4 positions minted on this chain. 20 pools on the deck. 62% of the pledges that reached an hour were kept — the rest are published as broken, because a pledge has no escrow.
STRIKES ON THE CLOCK
50 rows per page · read from PositionManager and StateView6 on record
| Pool | Hour (UTC) | Threat before the hour | Positions | Kept / broken | Grievance |
|---|---|---|---|---|---|
| UBIK / USDG 1% | 2026-09-18 01:49 | 86.19% | 10 | ahead | [showcase] This pool carried the launch week and the terms changed once the volume arrived. The roster below is the size of the answer. It is published before the hour, not after. |
| SWARM / USDG 10% | 2026-09-14 03:49 | 0.00% | 10 | ahead | [showcase] Eleven days, three threads, zero replies. The pool is the only channel left that gets read. At the hour it gets quieter. |
| Jacob / USDG 4% | 2026-09-14 03:49 | 50.58% | 10 | ahead | [showcase] A hook contract now sits in front of every removal on this pool and nobody who provides the depth was asked. This strike reads the hook address out of the pool key and publishes it before the hour. |
| FRONTIER / USDG 3.01% | 2026-09-12 15:48 | struck | 13 | 8 / 5 | [showcase] Incentives on this range were cut after the positions were in. The capital that priced the pool was the last to hear. At the hour the depth that was promised the old terms walks out. |
| FRONTIER / USDG 5% | 2026-09-12 15:47 | struck | 13 | 8 / 5 | [showcase] Order flow was routed around this pool for two weeks while the same depth was still being asked for. Depth answers to routing. At the hour it leaves. |
| ANTHROPIG / USDG 4.032% | 2026-09-12 15:44 | struck | 13 | 8 / 5 | [showcase] The fee tier moved while positions were open. No announcement, no window to exit at the old terms. This roster leaves at the hour and comes back when the change is reversed or explained on-chain. |
START THE CLOCK
the chain records itPick any of the DEX pools on this chain. Write exactly why you are angry. Set the hour. The protocol you name gets a reply box on this same page, always. Before the hour we publish the size of the threat — pledged liquidity over pool liquidity — so a strike that is too small says so itself.
SHOW YOUR POSITION
three keyless reads per pledge · nothing moves, nothing is approvedConnect your wallet and list your PositionManager ids. We read ownerOf, getPoolAndPositionInfo and getPositionLiquidity. No funds leave until the hour you named, and when they leave it is your transaction that moves them.
| Token id | Wallet | Liquidity pledged | Share of L | State |
|---|---|---|---|---|
| #2555248 | 0x8233…35dd | 22,408,452,332,252,930,000 | 86.08% | PLEDGED |
| #2553709 | 0x32a9…e8cb | 1,011,297,832,624,674,200 | 39.08% | PLEDGED |
| #2546538 | 0x5a54…1dc5 | 741,615,692,610,740,600 | 38.81% | KEPT |
| #2555922 | — | 529,717,467,476,177,540 | out of range | PLEDGED |
| #2555741 | 0x0554…4d73 | 482,747,105,206,432,060 | out of range | PLEDGED |
| #2553868 | 0x33a1…80be | 375,949,843,474,007,500 | out of range | KEPT |
| #2555921 | — | 252,349,271,821,186,300 | out of range | PLEDGED |
| #2555687 | 0xbcb9…d5fb | 215,089,243,794,763,650 | out of range | PLEDGED |
| #2555689 | 0xbcb9…d5fb | 198,623,424,919,120,060 | out of range | PLEDGED |
| #2555692 | 0xbcb9…d5fb | 175,012,165,936,347,900 | out of range | PLEDGED |
| #2555688 | 0xbcb9…d5fb | 165,410,674,152,155,040 | out of range | PLEDGED |
| #2552510 | 0xa198…9694 | 157,369,063,080,576,260 | 15.28% | KEPT |
| #2555695 | 0xbcb9…d5fb | 153,007,112,187,875,520 | out of range | PLEDGED |
| #2555690 | 0xbcb9…d5fb | 152,530,640,362,642,800 | out of range | PLEDGED |
| #2553856 | 0x2611…0a59 | 150,191,046,186,623,070 | 12.80% | BROKEN |
| #2555977 | 0x4601…7394 | 148,451,234,028,069,950 | 14.42% | BROKEN |
| #2555691 | 0xbcb9…d5fb | 146,085,986,554,782,820 | out of range | PLEDGED |
| #2545222 | 0x9286…8ff6 | 133,789,403,735,767,920 | 7.00% | KEPT |
| #2554273 | 0x4e88…2e93 | 127,124,017,128,689,840 | 10.84% | KEPT |
| #2554484 | 0x64ac…b920 | 124,455,689,977,449,300 | 4.81% | PLEDGED |
| #2554192 | 0xd67d…811d | 110,904,390,956,769,150 | 9.46% | KEPT |
| #2553863 | 0x33a1…80be | 106,314,881,176,366,370 | 9.06% | KEPT |
A pledge has no escrow. It is a promise, and this page says so on the row — kept or broken, read back from the chain after the hour.
WATCH THE DRAIN
two lines, two labels, never one numberAt the exact second, each signer removes their own liquidity. We draw two separate lines and never merge them, because removing a position that sits outside the range moves the reserves and does not move the active liquidity. Calling either of them “TVL” would be a lie about which quantity moved.
The removal is your transaction: DECREASE_LIQUIDITY plus TAKE_PAIR, wrapped in modifyLiquidities, returning to your own address. We build the calldata and hand it to your wallet. We are never in the path of the money, and we never ask for an approval.
THE BACKDROP, NOT THE PROOF
protocol-level, refreshed hourlyThe day after, we draw the protocol-level chart behind the strike hour. It is a platform number, lagging by up to an hour, so it can never show one pool. It sits behind the two pool lines as context and is labelled every time it appears. We do not use it to attribute a drop to anybody.
That is the whole argument for keeping them apart. A strike moves the orange sliver; the grey bar is what DefiLlama redraws an hour later. Reading a dent out of the grey bar would be reading noise.
Last read: $164,456,448 · protocol-level, not pool-level · 2026-09-12 15:52 UTC
Illustration · not dataTHE TEAM ANSWERS HERE
same page, same size as the dentEvery protocol named on this deck gets a reply box bolted beside the dent. Stamped, not moderated. The point of a strike is an answer, not a dent.
8 of 13 pledges kept at the hour, 5 broken. A pledge has no escrow, so this row is the whole enforcement: the record of who did what they said.
13 positions on the roster
Acknowledged. Routing weights are restored and the epoch is being re-run. No further comment until the numbers on this page say it worked.
Stamped, not moderated8 of 13 pledges kept at the hour, 5 broken. A pledge has no escrow, so this row is the whole enforcement: the record of who did what they said.
13 positions on the rosterThe hook stays. Every removal it fronts is still the LP's own transaction and this page can read the address. Nothing else changes.
Stamped, not moderated8 of 13 pledges kept at the hour, 5 broken. A pledge has no escrow, so this row is the whole enforcement: the record of who did what they said.
13 positions on the rosterTerms are reverted as of the block above. The fee tier is back where it was when the positions were opened, and the next change is announced before it ships, not after.
Stamped, not moderated
OR THE EXIT REPEATS NEXT WEEK
the return loopA strike that gets an answer closes. A strike that gets silence re-opens on the same pool, one week later, carrying forward the pledges that kept. The deck keeps its own record of who kept and who did not, because a promise with no escrow is worth exactly its history.
CHECK ALL OF IT WITHOUT US
three keyless reads, no signature
ownerOf(tokenId) on the PositionManager. Keyless, no signature, and anybody else's roster checks the same way.
getPoolAndPositionInfo(tokenId). Read the hooks address in the PoolKey too: a hook can block beforeRemoveLiquidity, and then the hour is theatre.
getPositionLiquidity(tokenId) over StateView.getLiquidity(poolId). That ratio is the whole threat, and we publish it before the hour instead of after.
Each participant withdraws only their own capital, at a time they chose, by their own transaction. This is expressive protest, not an agreement between competing suppliers to withhold supply from a market. Nothing here is custody, nothing here is advice, and the deck never holds a key, a token or a position.
Showcase records. The pools, positions, wallets and every number are read from chain; the grievance text and the protocol replies are written to show the product's shape and were not filed by those wallets.