Pool Doctor
EthereumHigh Risk

WETH/USDC

2 things keep this pool out of Best Practices: 1 that Metric has to confirm and 1 that needs a new pool.

Explore a better configuration.

Import this pool into Lab and compare your proposed changes.

Improve this pool ↗

Where it stands, where it can go

  1. Best Practices
    • A new pool, with Metric's confirmation
  2. Neutral
    • A new pool built to the recipe
  3. High Risk
    Now

Is it tradable right now

Separate from the tier: whether swaps work and routers will find the pool.

  • Price feed: OKHealthy

    The provider returned a usable price on Metric's last reading.

  • Trading: OKActive

    The pool is not paused.

  • Liquidity for routing: Check$0.00

    Most aggregators only route to pools holding about $1,000 or more. Below that, expect little or no aggregator flow.

  • Executable depth: OKBoth directions have depth

    Available output: 11703562004026 raw WETH units; 19667 raw USDC units. This is a depth snapshot, not a guarantee for any trade size.

  • Spread split: InfoLPs 75% / curator 10% / Metric 15%

    How the spread each trade pays is divided. The admin can change the curator share within the factory's cap.

  • Last 24 hours: Info11 swaps, $4.53K volume

    Swaps that reached this pool in the last day.

Contracts & extensions
Price Provider0x9141…247D

Anchored, immutable parameters, 10s staleness

These depend on Metric

Nothing to change onchain. Metric has to verify or confirm something.

Curator not verified by Metric

Needs Metric

LPs can't tell who runs the pool. The app shows an unverified admin as an operator, not a curator.

Verification is done by Metric: KYB, identity checks and due diligence.

View fix instructions (2 steps)
  1. 01
    Apply through Metric's curator application form. Most reviews take less than a week.
  2. 02
    Apply from the wallet that created the pool: the verified admin must also be the creator.
curator_unverifiedCurators ↗

These are permanent on this pool

Fixed at creation. The only way past them is a new pool.

No StopLoss attached

Needs a new pool

Without StopLoss nothing limits how far one swap can push a bin's value down. In a pool like this a single transaction may drain it.

Extension addresses are fixed when the pool is created, so StopLoss can't be added later.

View fix instructions (2 steps)
  1. 01
    Create a new pool with OracleValueStopLossExtension in its extension list.
  2. 02
    Initialize it locked: drawdown 15% or less, decay 15% per day or less, timelock at the uint40 maximum.
    abi.encode(uint32(150000), uint64(1736111111111), uint40(1099511627775))
stop_loss_missingExtensions ↗

Recipe for the replacement pool

The settings a new pool needs for Best Practices, next to what this pool has. Rows marked Change are the ones that differ.

SettingThis poolNew pool
Price ProviderAnchored, immutable parametersAnchored, immutable parametersKeep
Feed staleness bound10 s15 s or lessKeep
Provider replacementFixedFixed: priceProviderTimelock = type(uint256).maxKeep
StopLossNot attachedAttached, 15% drawdown or less, 15%/day decay or less, timelock 1099511627775Change
Widest bin1% or less1% or lessKeep
Withdrawal extensionsNoneNoneKeep
CuratorNot verifiedCreator is the admin and is verified by MetricChange

Open the planner to try a configuration and get the StopLoss initialization payload.