← Opportunities · Pairs

WBNB/TOPAZ

0xbb4cdb9cbd36b01bd1cbaebf2de08d9173bc095c / 0xdf002282c1474c9592780618adda7eaa99998abd
pairKey 0xbb4cdb9cbd36b01bd1cbaebf2de08d9173bc095c-0xdf002282c1474c9592780618adda7eaa99998abd · as of 2026-10-08 (UTC)

Opportunity score

Score
0
Confidence
low
Topaz present
yes

Types: ignore_or_monitor

Recommended action: monitor only; do not incentivize yet

Reason codes: topaz_only_no_competitor

Scored as of 2026-10-08.

Trends (daily, 34d window)

Volume over time
Fees earned over time
Effective fee (bps) over time
Topaz volume share over time

Trade-size mix (Topaz, last 14d)

82.8% of this pair's Topaz volume is sub-$1k fills. Small, aggregator-routed flow is generally less sensitive to a fee change than size shopping for execution — so a book weighted to the top of this table has more fee headroom than its volume alone suggests.

Trade sizeSwapsVolumeShare of volume
< $1001,747$31.8K36.9%
$100 – $1k163$39.6K45.9%
$1k – $10k8$14.8K17.2%
$10k – $100k0$00.0%
≥ $100k0$00.0%

Fee change effectiveness (hourly)

Competitor-normalized before/after at the hour level. The change hour is excluded; "before" is the 24 closed hours prior, each "after" window the first 6/24/72/168 closed hours since (bounded by the next change). Verdict weighs Topaz fees/hr and volume share and competitor flow — a fee that lifts revenue but bleeds routing share is not "working". Topaz hourly data refreshes hourly (:05), so a change shows pending only until its first 6 post-change hours close; competitor flows ride the 6-hourly collect, so the normalized side can trail by up to ~6h.

topaz2026-09-03 17:13 UTCcap 2000→20000inconclusiveconfident168h elapsed

no pre-change Topaz volume to compare against

WindowAfter hrsTopaz fees/hr before→afterΔVol share before→afterΔCompetitor vol/hrΔEff bps before→after
6h6$0 → $0—— → ——$0 → $0—— → —
24h24$0 → $0—— → ——$0 → $0—— → —
72h72$0 → $11—— → 100%—$0 → $0—— → 109.80
7d168$0 → $12—— → 100%—$0 → $0—— → 110.50
topaz2026-09-03 16:59 UTCcap 30000→2000, K 8000000→5000000pendingpending0h elapsed

only 0 post-change hour(s) so far — too early to judge

WindowAfter hrsTopaz fees/hr before→afterΔVol share before→afterΔCompetitor vol/hrΔEff bps before→after
6h0$0 → pending—— → pending—$0 → ——— → —
24h0$0 → pending—— → pending—$0 → ——— → —
72h0$0 → pending—— → pending—$0 → ——— → —
7d0$0 → pending—— → pending—$0 → ——— → —
topaz2026-09-03 16:48 UTCcap ?→30000, K ?→8000000, base 10000→15000inconclusiveconfident168h elapsed

no pre-change Topaz volume to compare against

WindowAfter hrsTopaz fees/hr before→afterΔVol share before→afterΔCompetitor vol/hrΔEff bps before→after
6h6$0 → $0—— → ——$0 → $0—— → —
24h24$0 → $0—— → ——$0 → $0—— → —
72h72$0 → $1—— → 100%—$0 → $0—— → 165.71
7d168$0 → $1—— → 100%—$0 → $0—— → 167.95
Router reaction (volume/hr before → after)
RouterBeforeAfterΔSwaps
0x691e6171…fcf6a6$0$38new0 → 61
0x9b63ca87…6e0cae$0$13new0 → 39
0x8f10b468…13f996$0$9new0 → 9
0x00f67f6f…73f2e1$0$4new0 → 8
0x63aeff0f…e8407d$0$4new0 → 1
0x4579a59b…4085b0$0$3new0 → 4
topaz2026-09-03 04:32 UTCcap ?→30000, K ?→8000000, base ?→10000inconclusiveearly11h elapsed

no pre-change Topaz volume to compare against

WindowAfter hrsTopaz fees/hr before→afterΔVol share before→afterΔCompetitor vol/hrΔEff bps before→after
6h6$0 → $0—— → ——$0 → $0—— → —
24h11$0 → $0—— → ——$0 → $0—— → —
72h11$0 → $0—— → ——$0 → $0—— → —
7d11$0 → $0—— → ——$0 → $0—— → —
topaz2026-06-18 23:16 UTCbase ?→10000inconclusiveconfident168h elapsed

no pre-change Topaz volume to compare against

WindowAfter hrsTopaz fees/hr before→afterΔVol share before→afterΔCompetitor vol/hrΔEff bps before→after
6h6$0 → $0—— → ——$0 → $0—— → —
24h24$0 → $0—— → ——$0 → $0—— → —
72h72$0 → $0—— → ——$0 → $0—— → —
7d168$0 → $0—— → ——$0 → $0—— → —

Fee change impact

On-chain fee changes on this pair's Topaz pool(s), with volume & fee generation before vs after each change. Each side spans all days until the adjacent change; rates are per active day (the two sides usually differ in length). Marked on the charts above. Values are raw module units (pips, ÷100 = bps; scaling is the raw uint64 K).

topaz v3 0x1ff0…6f71
When (UTC)ChangeVol/day before→afterΔFees/day before→afterΔEff bps before→afterWindow
2026-09-03 16:48cap ?→30000, K ?→8000000, base 10000→15000$0 → $414—$0 → $7—— → 169.420d vs 34d
2026-06-18 23:16base ?→10000$0 → pending—$0 → pending—— → —0d vs —
topaz v3 0x71f0…69a8
When (UTC)ChangeVol/day before→afterΔFees/day before→afterΔEff bps before→afterWindow
2026-09-03 17:13cap 2000→20000$0 → $14.2K—$0 → $157—— → 110.440d vs 34d
2026-09-03 16:59cap 30000→2000, K 8000000→5000000$0 → pending—$0 → pending—— → —0d vs —
2026-09-03 04:32cap ?→30000, K ?→8000000, base ?→10000$0 → pending—$0 → pending—— → —0d vs —

Pools (3)

DEXFeeTick7d vol14d vol30d vol7d fees14d fees30d feesLiquidityCandidate reasons
topaz v3dynamic2000$35.6K$86.5K$340.7K$404$990$3.7K$121.4K—
topaz v3dynamic200$368$716$7.5K$6$12$127$6.2K—
pancake v3100 bps200$0$0$0$0$0$0$0pair_scoped_supplement #1

Candidate reasons explain why an external pool entered the discovery set (recent 14d/28d fees & volume, liquidity, lifetime volume). Tick spacing is a secondary review signal.