Pool Doctor
BNB ChainHigh Risk

USDC/USDT

3 things keep this pool out of Best Practices: 1 you can fix on this pool and 2 that need 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 built to the recipe
  2. Neutral
  3. High Risk
    Now

Is it tradable right now

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

  • Price feed: ProblemFeed down

    The provider had no usable price on Metric's last reading, so swaps revert until it does.

  • 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: ProblemTrading blocked

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

  • Spread split: InfoLPs 70% / curator 15% / 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: Info0 swaps, $0.00 volume

    No swaps reached this pool in the last day.

Contracts & extensions
Price Provider0x9502…34b6

Metric Price Provider, not anchored

You can fix these on this pool

Calls the pool admin can make today. No new pool, no one else involved.

Admin is not the pool's creator

Fix in place

Verification belongs to the creator. An admin role transferred to another address loses it.

Transfer the admin role back to the creator address.

View fix instructions (1 steps)
  1. 01
    From the current admin wallet, transfer the pool admin role to:
    0x2029a5D4A7Fca6e19130184233716A591C8b7371
curator_not_creatorPool tiers ↗

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 ↗

Pricing is not anchored

Needs a new pool

Nothing independent bounds the bid and ask. A wrong or malicious quote can sell the pool's assets cheaply.

This pool's provider is fixed forever, so the fix is a new pool.

View fix instructions (3 steps)
  1. 01
    Deploy an Anchored Price Provider through AnchoredProviderFactory with immutable parameters and feed staleness of 15 seconds or less.
  2. 02
    Create a new pool that uses it, with the provider fixed.
    priceProviderTimelock = type(uint256).max
  3. 03
    Move liquidity to the new pool once it passes the launch checks.

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 ProviderNot anchoredAnchored, immutable parametersChange
Feed staleness boundn/a15 s or lessChange
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
CuratorVerified creator, different adminCreator is the admin and is verified by MetricChange

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