0x442f6f9d 0x442f6f9d714f2ae85a012f3a5dafb1ba2af1e206

🔴 DANGER — cannot exit; funds would be trapped

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.

I have read and understand this risk label.

Verify this yourself

Re-check the Ed25519 signature on receipt 2e6da96046f5a9f0 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: 0x62ca5a685eb1a380386ff8b1a7d73209600e97043bedd7afe6cd9368943d26d5

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-09-11 · receipt: 2e6da96046f5a9f0

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, or read the Verdict Standard.