Receipt ceae9de4fcf54a1f - bsc

0x922ab6df `0x922ab6df7778392bb5a27eb305948e9c099f7fdc`

HONEYPOT🔴 DANGER — cannot exit; funds would be trappedRead the receipt

PROVEN HONEYPOT

Proven honeypot: the exit was executed and refused — this token would not let our buyer sell at the size we tested. Do not buy.

The signed receipt

Receipt ceae9de4fcf54a1f

HONEYPOT

Chain: bsc
Verdict: HONEYPOT
OmniScore
Checked: 2026-11-10
Signature: ed25519

I have read and understand this risk label.

Verify this yourself

Re-check the Ed25519 signature on receipt ceae9de4fcf54a1f and confirm the transparency-log entry. This receipt was signed before the replay recipe recorded its probe size, so it cannot be re-derived independently — the signature and the log entry are still fully checkable.

This is a point-in-time exit proof at the checked block, not a guarantee of future behavior.

Fork execution evidence

The exact on-fork call that proved the verdict — reproducible at the pinned block.

Trace ref: 0x35afd8cc98445db293528d9f928e492dc99f1ea2f89d97350a61219fea6d618a

Revert / proof: trap proven by revert (valid at any depth); pool holds 0.000000000 native (< 0.250 needed for a 2%-of-pool buy at the 0.005 floor); our buy was inf% of the pool

Chain: bsc · OmniScore: · verdict: HONEYPOT · checked: 2026-11-10 · receipt: ceae9de4fcf54a1f

How we proved it

Four steps, all replayable

Fork the chain at a pinned block.
Buy a fixed amount through the real router.
Sell it back and measure what returns.
Sign the receipt so anyone can re-check it offline.

OmniGuard gives you a proof you can verify, not a score to trust. This is not financial advice and is not a guarantee about future behavior — it states what was proven at the checked block. Re-run it live in the honeypot checker, read the Verdict Standard, or browse the ranked directory.