Pool depth and LP concentration are not visible before execution. A large LP can exit before your transaction confirms.
Pillar: Safety
The problem
A user executing a swap or exit can see total pool TVL, but not how that liquidity is distributed across providers. If 80% of liquidity sits in two wallets, a coordinated withdrawal before the user’s transaction confirms can result in drastically worse execution than expected.
This is a structural information asymmetry that benefits large, coordinated actors at the expense of individual participants.
Why it matters
- Safety: My execution depends on liquidity that can disappear between signing and confirmation.
- Agency: I cannot make an informed execution decision without this information.
What exists today
On-chain data is queryable. No standard for surfacing LP concentration as a pre-execution risk signal in protocol UIs.
The gap
No standard for LP concentration disclosure as a required pre-execution data point.
Open questions
- What concentration threshold should trigger a warning?
- How do you handle JIT liquidity, which is added and removed within a single block?