Pool Doctor
BNB ChainHigh Risk

ANTX/USDT

6 things keep this pool out of Best Practices: 4 you can fix on this pool and 2 that Metric has to confirm.

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
    • After your fixes and Metric's confirmation
  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: OKHealthy

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

  • Trading: OKActive

    The pool is not paused.

  • Liquidity for routing: OK$7.80K

    Above the roughly $1,000 most aggregators need before they route to a pool.

  • Executable depth: OKBoth directions have depth

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

  • StopLoss: OK25% drawdown

    Rejects a swap that takes a bin more than 25% below its peak. The peak decays 25% per day. A bin's first trade is exempt.

  • Spread split: InfoLPs 80% / curator 5% / 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: Info7 swaps, $3.02K volume

    Swaps that reached this pool in the last day.

Contracts & extensions
Price Provider0xe8Cc…Dd95

Anchored, immutable parameters, 12s staleness

You can fix these on this pool

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

StopLoss drawdown above 15%

Fix in place

A single swap may take a bin further below its peak than the tier allows.

Currently 25%. Lower it while the StopLoss is still unlocked, then lock it.

View fix instructions (3 steps)
  1. 01
    From the pool admin wallet, propose a value inside the limit on 0xE4038fA09f0bB9963068afaF97BE0c045155090D:
    proposeOracleStopLossDrawdown(0xceC9a6939b4be3B3A1931A79b2409e430C4EEE3b, 150000)
  2. 02
    Wait out the current timelock (24 hours), then call:
    executeOracleStopLossDrawdown(0xceC9a6939b4be3B3A1931A79b2409e430C4EEE3b)
  3. 03
    Only then lock the StopLoss (the next finding). Once locked, this value can never be changed.
stop_loss_drawdown_exceededExtensions ↗

StopLoss decay above 15% per day

Fix in place

The recorded peak fades too fast, so losses can add up quicker than the tier allows.

Currently 25% per day. Lower it while the StopLoss is still unlocked, then lock it.

View fix instructions (3 steps)
  1. 01
    From the pool admin wallet, propose a value inside the limit on 0xE4038fA09f0bB9963068afaF97BE0c045155090D:
    proposeOracleStopLossDecay(0xceC9a6939b4be3B3A1931A79b2409e430C4EEE3b, 1736111111111)
  2. 02
    Wait out the current timelock (24 hours), then call:
    executeOracleStopLossDecay(0xceC9a6939b4be3B3A1931A79b2409e430C4EEE3b)
  3. 03
    Only then lock the StopLoss (the next finding). Once locked, this value can never be changed.
stop_loss_decay_exceededExtensions ↗

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:
    0xf2CFD0293d7B737784a25CA8Acf10264b052cF8C
curator_not_creatorPool tiers ↗

StopLoss settings can still change

Fix in place

The admin can loosen or disable the StopLoss after LPs deposit. Any timelock shorter than the maximum only delays that.

Lock the StopLoss, but only after its values are inside the limits. Locking is permanent.

View fix instructions (4 steps)
  1. 01
    Do not lock yet. Right now drawdown is 25% and decay is 25% per day, and one of them is above 15%. Bring it inside the limit first (the finding above): locking now would freeze the pool in High Risk for good.
  2. 02
    Cancel any drawdown, decay or watermark proposal that is still queued. A queued change stays executable after the lock and fails the tier check.
  3. 03
    From the pool admin wallet, call this on 0xE4038fA09f0bB9963068afaF97BE0c045155090D:
    proposeOracleStopLossTimelock(0xceC9a6939b4be3B3A1931A79b2409e430C4EEE3b, 1099511627775)
  4. 04
    Wait out the current timelock (24 hours), then call:
    executeOracleStopLossTimelock(0xceC9a6939b4be3B3A1931A79b2409e430C4EEE3b)
stop_loss_mutableConfigure a pool ↗

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 ↗

Feeds not confirmed for these tokens

Needs Metric

Metric hasn't confirmed that the anchored provider's feeds price this pool's own tokens. This drops the pool one tier.

A feed mapping Metric hasn't confirmed yet counts as a mismatch.

View fix instructions (2 steps)
  1. 01
    Ask Metric to confirm the feed mapping for both tokens.
  2. 02
    If the provider really reads the wrong feed, deploy a new provider and pool on the right one.
anchored_feed_unmatchedPool tiers ↗