hexscan.xyz/honeypot
1.Catalog declaration
| Resource URL | https://hexscan.xyz/honeypot |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0x841ef35b7b7ee4c820bff040369a8ade4741b45d |
| Declared price (base units) | 1000 |
| Catalog status | active |
| First seen / last seen | 2026-08-29 01:11 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 9 / 6 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-19 13:40 UTC | POST | pass | 402 | 839 ms | — |
| 2026-10-17 22:40 UTC | POST | pass | 402 | 2130 ms | — |
| 2026-10-16 15:40 UTC | POST | pass | 402 | 465 ms | — |
| 2026-10-15 03:40 UTC | POST | pass | 402 | 771 ms | — |
| 2026-10-13 21:40 UTC | POST | pass | 402 | 181 ms | — |
| 2026-10-12 15:40 UTC | POST | pass | 402 | 258 ms | — |
| 2026-10-11 15:40 UTC | POST | pass | 402 | 374 ms | — |
| 2026-10-10 15:40 UTC | POST | pass | 402 | 260 ms | — |
| 2026-10-09 12:40 UTC | POST | pass | 402 | 3932 ms | — |
| 2026-10-08 04:40 UTC | POST | pass | 402 | 2010 ms | — |
| 2026-10-07 04:40 UTC | POST | pass | 402 | 318 ms | — |
| 2026-10-06 13:40 UTC | POST | pass | 402 | 69 ms | — |
| 2026-10-04 22:40 UTC | POST | pass | 402 | 289 ms | — |
| 2026-10-04 04:40 UTC | POST | pass | 402 | 161 ms | — |
| 2026-10-03 13:40 UTC | POST | pass | 402 | 198 ms | — |
| 2026-10-02 13:40 UTC | POST | pass | 402 | 365 ms | — |
| 2026-10-01 16:40 UTC | POST | pass | 402 | 184 ms | — |
| 2026-09-30 22:40 UTC | POST | pass | 402 | 314 ms | — |
| 2026-09-30 04:40 UTC | POST | pass | 402 | 1979 ms | — |
| 2026-09-29 13:40 UTC | POST | pass | 402 | 280 ms | — |
| 2026-09-28 16:40 UTC | POST | pass | 402 | 599 ms | — |
| 2026-09-27 22:40 UTC | POST | pass | 402 | 596 ms | — |
| 2026-09-27 04:40 UTC | POST | pass | 402 | 233 ms | — |
| 2026-09-26 13:40 UTC | POST | pass | 402 | 256 ms | — |
| 2026-09-25 16:40 UTC | POST | pass | 402 | 269 ms | — |
| 2026-09-24 22:40 UTC | POST | pass | 402 | 235 ms | — |
| 2026-09-24 04:40 UTC | POST | pass | 402 | 225 ms | — |
| 2026-09-23 13:40 UTC | POST | pass | 402 | 367 ms | — |
| 2026-09-22 16:40 UTC | POST | pass | 402 | 282 ms | — |
| 2026-09-21 22:40 UTC | POST | pass | 402 | 283 ms | — |
3.L1 — real purchases
3 of 3 paid attempts settled on-chain, and 3 of those also returned a 2xx response (delivered). Each settled row carries its on-chain transaction hash, and that transaction is the evidence. On this page a receipt means the seller's own settlement receipt (PAYMENT-RESPONSE); a settled row can have none (see “tx from our index”). A settled row reads as nonce-bound when the on-chain re-read also matched the one-time signature nonce we generated for that purchase, and amount + payee when it matched amount, payee, asset and chain with no nonce on record — the binding shipped on 2026-09-04, so earlier rows carry the weaker evidence and keep their label rather than being demoted (methodology). settled is the transfer we confirmed on-chain; delivered is the response arriving. A settled row whose paid request answered 5xx counts as settled and not as delivered — definitions.
A row marked tx from our index came back with no settlement receipt from the seller. Our own index of on-chain settlements found the transfer afterwards — our payer, this endpoint's payee, the exact amount, inside the time window — and the row goes through the same on-chain re-read as any other before it reads settled. The seller did not name that transaction; we did (methodology).
Terms in this table
settled (nonce-bound)- vet402 confirmed the USDC transfer on-chain, and the on-chain re-read also matched the one-time nonce vet402 signed for that purchase.
settled (amount + payee)- vet402 confirmed the USDC transfer on-chain; the on-chain re-read matched amount, payee, asset and chain; no nonce was on record (rows before 2026-09-04).
L2 no_declaration- the listing declares no output schema to check the response against.
Whose side- the same words as the seller page: seller's side only after failures on two different days (UTC), marked “under re-check”; vet402's side; or not sorted (the rules).
| Attempted at | Result | HTTP | On-chain tx | Latency |
|---|---|---|---|---|
| 09-23 12:022026-09-23 12:02 UTC | settled (nonce-bound)tx from our index | 200 | 0x9a773596…d4fb | 1930 ms |
| 1000 units (≈ $0.001 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-15 23:502026-09-15 23:50 UTC | settled (nonce-bound)tx from our index | 200 | 0xd46ffaf9…7e78 | 1309 ms |
| 1000 units (≈ $0.001 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-04 07:022026-09-04 07:02 UTC | settled (amount + payee)tx from our index | 200 | 0x374c545a…c28b | 1246 ms |
| 1000 units (≈ $0.001 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 3/3 settled · 3 delivered and updates as the record grows. It carries the host it is about and the date it was last measured, so a saved copy cannot pass itself off as current. It states a measurement, not a rating.
[](https://vet402.com/observatory/e/755b74cb-50cf-431b-9360-a7ede8cd9436)4.Catalog listing events
No listing changes observed.
unverified is not a failure; a fail is published only after two consecutive failing probes. Definitions: methodology.
5.Dispute this record
Think a measurement above is wrong? Say which probe or purchase and what you observed instead. One person reads it and replies. The record is never deleted on dispute: if it was wrong, the correction is published with the same weight; if it was right, it stands. Operators who control the receiving address can also sign a dispute via POST /api/v1/observatory/disputes (API reference), which re-measures through the normal publication gate.