vape-x402.vapex402.workers.dev/scan/rug_pull_alert
1.Catalog declaration
| Resource URL | https://vape-x402.vapex402.workers.dev/scan/rug_pull_alert |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x8aab9a6d28e9aba2a15a613c90f24f352f0cce15 |
| Declared price (base units) | 30000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-09-29 01:02 UTC |
| Catalog-reported calls / payers (30d) | 1 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-28 16:40 UTC | GET | pass | 402 | 2837 ms | — |
| 2026-09-27 22:40 UTC | GET | pass | 402 | 6804 ms | — |
| 2026-09-27 04:40 UTC | GET | pass | 402 | 881 ms | — |
| 2026-09-26 13:40 UTC | GET | pass | 402 | 465 ms | — |
| 2026-09-25 16:40 UTC | GET | pass | 402 | 640 ms | — |
| 2026-09-24 22:40 UTC | GET | pass | 402 | 590 ms | — |
| 2026-09-24 04:40 UTC | GET | pass | 402 | 288 ms | — |
| 2026-09-23 13:40 UTC | GET | pass | 402 | 1305 ms | — |
| 2026-09-22 16:40 UTC | GET | pass | 402 | 9643 ms | — |
| 2026-09-21 22:40 UTC | GET | pass | 402 | 649 ms | — |
| 2026-09-21 04:40 UTC | GET | pass | 402 | 578 ms | — |
| 2026-09-20 13:40 UTC | GET | pass | 402 | 647 ms | — |
| 2026-09-19 16:40 UTC | GET | pass | 402 | 7484 ms | — |
| 2026-09-18 22:40 UTC | GET | pass | 402 | 2382 ms | — |
| 2026-09-18 04:40 UTC | GET | pass | 402 | 562 ms | — |
| 2026-09-17 16:40 UTC | GET | pass | 402 | 357 ms | — |
| 2026-09-16 22:40 UTC | GET | pass | 402 | 1372 ms | — |
| 2026-09-15 22:40 UTC | GET | pass | 402 | 8047 ms | — |
| 2026-09-15 04:40 UTC | GET | pass | 402 | 759 ms | — |
| 2026-09-14 16:40 UTC | GET | pass | 402 | 842 ms | — |
| 2026-09-13 22:40 UTC | GET | pass | 402 | 955 ms | — |
| 2026-09-13 13:40 UTC | GET | pass | 402 | 685 ms | — |
| 2026-09-12 16:40 UTC | GET | pass | 402 | 9842 ms | — |
| 2026-09-11 22:40 UTC | GET | fail | — | 10001 ms | timeoutNo response headers arrived within 10 seconds. |
| 2026-09-11 13:40 UTC | GET | fail | — | 10001 ms | timeoutNo response headers arrived within 10 seconds. |
| 2026-09-10 17:40 UTC | GET | pass | 402 | 525 ms | — |
| 2026-09-10 05:40 UTC | GET | pass | 402 | 254 ms | — |
| 2026-09-09 17:40 UTC | GET | pass | 402 | 235 ms | — |
| 2026-09-09 05:40 UTC | GET | pass | 402 | 771 ms | — |
| 2026-09-07 23:40 UTC | GET | pass | 402 | 619 ms | — |
3.L1 — real purchases
2 of 2 paid attempts settled on-chain, and 2 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.
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.
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-12 18:002026-09-12 18:00 UTC | settled (nonce-bound) | 200 | 0xf39a0d70…8c97 | 2633 ms |
| 30000 units (≈ $0.03 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-06 12:072026-09-06 12:07 UTC | settled (nonce-bound) | 200 | 0xe07ca647…302e | 1762 ms |
| 30000 units (≈ $0.03 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 2/2 settled · 2 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/727def9e-b6cd-4e1a-a78c-04ad279b0109)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-09 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-09-08 | delisted | {"status":"active"} | {"status":"delisted"} |
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.