Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-10-02 · today

ip.halowerk.com/ip

1.Catalog declaration

Catalog declaration for this endpoint
Resource URL	https://ip.halowerk.com/ip
Source	cdp_bazaar
Declared method	POST
Network	eip155:8453
Receiving address	0x2880edfff13100677bf97a3cbdf3bc34771c4e5e
Declared price (base units)	1000
Catalog status	active
First seen / last seen	2026-08-14 08:52 UTC / 2026-10-02 01:04 UTC
Catalog-reported calls / payers (30d)	2 / 2

2.Probe history

2026-08-302026-10-02

Figure 1. Probe timeline, last 13 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap. Marks closer than one mark width are stepped down one lane.

L0 probe history, newest first
Probed at	Method	Verdict	HTTP	Latency	Reason
2026-10-02 13:40 UTC	POST	pass	402	2373 ms	—
2026-10-01 16:40 UTC	POST	pass	402	384 ms	—
2026-09-30 22:40 UTC	POST	pass	402	341 ms	—
2026-09-30 04:40 UTC	POST	pass	402	452 ms	—
2026-09-29 13:40 UTC	POST	pass	402	560 ms	—
2026-09-26 10:30 UTC	POST	pass	402	334 ms	—
2026-09-22 11:24 UTC	POST	pass	402	332 ms	—
2026-09-18 11:24 UTC	POST	pass	402	337 ms	—
2026-09-15 11:24 UTC	POST	pass	402	356 ms	—
2026-09-11 11:24 UTC	POST	pass	402	333 ms	—
2026-09-08 11:24 UTC	POST	fail	400	334 ms	no_402HTTP 400 instead of 402 to an unpaid POST. Recorded before the 2026-09-29 change; the POST carried an empty JSON body, and since that change this answer is recorded as request_shape (unverified), not as a fail.
2026-09-03 11:24 UTC	POST	pass	402	331 ms	—
2026-08-30 11:24 UTC	POST	fail	402	812 ms	accepts_invalidRecorded before the 2026-09-29 change, when the probe read only the first 4,000 bytes of the 402 body; this body began like an x402 envelope, so the fail may be vet402's measuring error rather than the seller's.

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 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).

1/1

Figure 2. Settle-through: one cell per paid attempt. Filled = settled on-chain, crossed = signed, and not settled on-chain.

L1 purchase history, newest first
Attempted at	Result	HTTP	On-chain tx	Latency
09-29 12:012026-09-29 12:01 UTC	settled (nonce-bound)	200	0x1af82e3b…8a61	5359 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 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.

[![vet402 receipt](https://vet402.com/api/badge/endpoint/05dc5e26-200e-41de-9afe-2b7c8965c3bb.svg)](https://vet402.com/observatory/e/05dc5e26-200e-41de-9afe-2b7c8965c3bb)

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.