gaming.halowerk.com/v1/cross-game-bridge
1.Catalog declaration
| Resource URL | https://gaming.halowerk.com/v1/cross-game-bridge |
| Source | cdp_bazaar |
| Declared method | POST |
| Catalog network | eip155:8453 |
| Receiving address | 0x2880edfff13100677bf97a3cbdf3bc34771c4e5e |
| Declared price (base units) | 4000 |
| Catalog status | active |
| First seen / last seen | 2026-09-02 01:03 UTC / 2026-10-21 13:01 UTC |
| Catalog-reported calls / payers (30d) | 3 / 3 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-20 13:40 UTC | POST | pass | 402 | 546 ms | — |
| 2026-10-18 16:40 UTC | POST | pass | 402 | 829 ms | — |
| 2026-10-17 13:40 UTC | POST | pass | 402 | 498 ms | — |
| 2026-10-15 21:40 UTC | POST | pass | 402 | 541 ms | — |
| 2026-10-14 15:40 UTC | POST | pass | 402 | 337 ms | — |
| 2026-10-13 03:40 UTC | POST | pass | 402 | 318 ms | — |
| 2026-10-12 03:40 UTC | POST | pass | 402 | 444 ms | — |
| 2026-10-11 03:40 UTC | POST | pass | 402 | 378 ms | — |
| 2026-10-10 03:40 UTC | POST | pass | 402 | 333 ms | — |
| 2026-10-08 22:40 UTC | POST | pass | 402 | 481 ms | — |
| 2026-10-07 16:40 UTC | POST | pass | 402 | 486 ms | — |
| 2026-10-06 22:40 UTC | POST | pass | 402 | 365 ms | — |
| 2026-10-05 04:40 UTC | POST | pass | 402 | 438 ms | — |
| 2026-10-04 13:40 UTC | POST | pass | 402 | 612 ms | — |
| 2026-10-03 13:40 UTC | POST | pass | 402 | 384 ms | — |
| 2026-10-02 16:40 UTC | POST | pass | 402 | 404 ms | — |
| 2026-10-01 22:40 UTC | POST | pass | 402 | 412 ms | — |
| 2026-09-30 22:40 UTC | POST | pass | 402 | 393 ms | — |
| 2026-09-30 04:40 UTC | POST | pass | 402 | 446 ms | — |
| 2026-09-29 13:40 UTC | POST | pass | 402 | 386 ms | — |
| 2026-09-28 16:40 UTC | POST | pass | 402 | 401 ms | — |
| 2026-09-27 22:40 UTC | POST | pass | 402 | 408 ms | — |
| 2026-09-27 04:40 UTC | POST | pass | 402 | 368 ms | — |
| 2026-09-26 16:40 UTC | POST | pass | 402 | 675 ms | — |
| 2026-09-25 22:40 UTC | POST | pass | 402 | 615 ms | — |
| 2026-09-25 04:40 UTC | POST | pass | 402 | 606 ms | — |
| 2026-09-24 13:40 UTC | POST | pass | 402 | 399 ms | — |
| 2026-09-23 16:40 UTC | POST | pass | 402 | 344 ms | — |
| 2026-09-22 22:40 UTC | POST | pass | 402 | 404 ms | — |
| 2026-09-22 04:40 UTC | POST | pass | 402 | 348 ms | — |
3.L1 — real purchases
1 of 1 paid attempts settled on-chain, and 1 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 matched the one-time value stored for that purchase, so the transaction is the one for this purchase. Stellar is not in this count. The Stellar re-read checks payer, payee, amount and asset. A row reads as amount + payee when the re-read matched payer, payee, amount and asset and did not bind a one-time value. That tier holds rows from before 2026-09-04 and Stellar rows. They keep the settled label rather than being demoted (methodology). settled is the transfer vet402 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 re-read the transfer on-chain in that chain's pinned settlement asset, and the on-chain re-read matched the one-time value stored for that purchase, so the transaction is the one for this purchase. Stellar is not in this count.
L2 no_declaration- the listing's output schema gave vet402 nothing to check this response against (no schema, a schema with no required keys and no example properties, or example properties with a content type that is not JSON). An output example the seller puts in the 402 (extensions.bazaar.info.output.example) is not checked yet.
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 | Payment chain | Latency |
|---|---|---|---|---|---|
| 09-19 00:012026-09-19 00:01 UTC | settled (nonce-bound) | 200 | 0x0ba27a0c…4787 | Base | 2180 ms |
| 4000 units (≈ $0.004 USDC) · L2 no_declarationWhose side: no failure (delivered) | |||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 1/1 settled · 1 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/9f368771-2acf-469e-88ee-3aabbf6561a0)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-10-06 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-10-06 | 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.