disruption.forgemesh.io/companies/names
1.Catalog declaration
| Resource URL | https://disruption.forgemesh.io/companies/names |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0xa8774facfd3da2ea11f240c977b9973d78adfcfe |
| Declared price (base units) | 10000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 8 / 5 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-19 22:40 UTC | GET | pass | 402 | 243 ms | — |
| 2026-10-18 04:40 UTC | GET | pass | 402 | 315 ms | — |
| 2026-10-16 21:40 UTC | GET | pass | 402 | 140 ms | — |
| 2026-10-15 12:40 UTC | GET | pass | 402 | 263 ms | — |
| 2026-10-14 03:40 UTC | GET | pass | 402 | 188 ms | — |
| 2026-10-12 21:40 UTC | GET | pass | 402 | 423 ms | — |
| 2026-10-11 15:40 UTC | GET | pass | 402 | 93 ms | — |
| 2026-10-10 15:40 UTC | GET | pass | 402 | 119 ms | — |
| 2026-10-09 15:40 UTC | GET | pass | 402 | 269 ms | — |
| 2026-10-08 13:40 UTC | GET | pass | 402 | 226 ms | — |
| 2026-10-07 13:40 UTC | GET | pass | 402 | 422 ms | — |
| 2026-10-06 13:40 UTC | GET | pass | 402 | 129 ms | — |
| 2026-10-04 22:40 UTC | GET | pass | 402 | 82 ms | — |
| 2026-10-04 04:40 UTC | GET | pass | 402 | 135 ms | — |
| 2026-10-03 13:40 UTC | GET | pass | 402 | 236 ms | — |
| 2026-10-02 16:40 UTC | GET | pass | 402 | 399 ms | — |
| 2026-10-01 16:40 UTC | GET | pass | 402 | 243 ms | — |
| 2026-09-30 22:40 UTC | GET | pass | 402 | 118 ms | — |
| 2026-09-30 04:40 UTC | GET | pass | 402 | 66 ms | — |
| 2026-09-29 13:40 UTC | GET | pass | 402 | 264 ms | — |
| 2026-09-28 16:40 UTC | GET | pass | 402 | 322 ms | — |
| 2026-09-27 22:40 UTC | GET | pass | 402 | 217 ms | — |
| 2026-09-27 04:40 UTC | GET | pass | 402 | 132 ms | — |
| 2026-09-26 13:40 UTC | GET | pass | 402 | 270 ms | — |
| 2026-09-25 16:40 UTC | GET | pass | 402 | 312 ms | — |
| 2026-09-24 22:40 UTC | GET | pass | 402 | 188 ms | — |
| 2026-09-24 04:40 UTC | GET | pass | 402 | 87 ms | — |
| 2026-09-23 16:40 UTC | GET | pass | 402 | 295 ms | — |
| 2026-09-22 22:40 UTC | GET | pass | 402 | 303 ms | — |
| 2026-09-22 04:40 UTC | GET | pass | 402 | 204 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.
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-30 12:022026-09-30 12:02 UTC | settled (nonce-bound) | 200 | 0xf044302c…f5a7 | 1115 ms |
| 10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-04 07:022026-09-04 07:02 UTC | settled (amount + payee) | 200 | 0x3d50515a…b577 | 761 ms |
| 10000 units (≈ $0.01 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/76dc789e-a953-4135-b989-0e5464e1d116)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.