Receipt db2be059f2ddd70f - bsc

0x0cee7a04 0x0cee7a04355b2e2d7248d9566db8889cf44f7777

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 db2be059f2ddd70f

HONEYPOT
Chain
bsc
Verdict
HONEYPOT
OmniScore
Checked
2026-11-08
Signature
ed25519

Verify this yourself

Re-check the Ed25519 signature on receipt db2be059f2ddd70f 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: 0x97b95298acfa0170d03e8854775e330bf7030cd433464f819a105eca36a88424

Revert / proof: SELL trapped: ~0 tokens left the wallet, or ~0 ETH returned though the pool should pay - the exit was executed and refused — this token would not let our buyer sell at the size we tested

Chain: bsc · OmniScore: · verdict: HONEYPOT · checked: 2026-11-08 · receipt: db2be059f2ddd70f

How we proved it

Four steps, all replayable

  1. Fork the chain at a pinned block.
  2. Buy a fixed amount through the real router.
  3. Sell it back and measure what returns.
  4. 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.