laso.finance/auth
1.Catalog declaration
| Resource URL | https://laso.finance/auth |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x3291e96b3bff7ed56e3ca8364273c5b4654b2b37 |
| Declared price (base units) | 1000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-09-29 01:02 UTC |
| Catalog-reported calls / payers (30d) | 26 / 24 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-29 16:40 UTC | GET | pass | 402 | 671 ms | — |
| 2026-09-28 22:40 UTC | GET | pass | 402 | 227 ms | — |
| 2026-09-28 04:40 UTC | GET | pass | 402 | 195 ms | — |
| 2026-09-27 13:40 UTC | GET | pass | 402 | 257 ms | — |
| 2026-09-26 16:40 UTC | GET | pass | 402 | 159 ms | — |
| 2026-09-25 22:40 UTC | GET | pass | 402 | 191 ms | — |
| 2026-09-25 04:40 UTC | GET | pass | 402 | 434 ms | — |
| 2026-09-24 13:40 UTC | GET | pass | 402 | 409 ms | — |
| 2026-09-23 22:40 UTC | GET | pass | 402 | 284 ms | — |
| 2026-09-23 04:40 UTC | GET | pass | 402 | 253 ms | — |
| 2026-09-22 13:40 UTC | GET | pass | 402 | 276 ms | — |
| 2026-09-21 16:40 UTC | GET | pass | 402 | 204 ms | — |
| 2026-09-20 22:40 UTC | GET | pass | 402 | 510 ms | — |
| 2026-09-20 04:40 UTC | GET | pass | 402 | 430 ms | — |
| 2026-09-19 13:40 UTC | GET | pass | 402 | 379 ms | — |
| 2026-09-18 16:40 UTC | GET | pass | 402 | 126 ms | — |
| 2026-09-18 04:40 UTC | GET | pass | 402 | 606 ms | — |
| 2026-09-17 12:35 UTC | GET | pass | 402 | 137 ms | — |
| 2026-09-14 11:24 UTC | GET | pass | 402 | 213 ms | — |
| 2026-09-10 11:24 UTC | GET | pass | 402 | 265 ms | — |
| 2026-09-07 11:24 UTC | GET | pass | 402 | 604 ms | — |
| 2026-09-02 11:24 UTC | GET | pass | 402 | 203 ms | — |
| 2026-08-14 08:52 UTC | GET | fail | 402 | 134 ms | accepts_invalid402 without a payable accept in the header or the body (which part was missing was not recorded before the 2026-09-29 change). |
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 match- the response had the fields the listing's output schema declares.
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-24 12:012026-09-24 12:01 UTC | settled (nonce-bound) | 200 | 0xe8be5eac…bd63 | 1333 ms |
| 1000 units (≈ $0.001 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 09-18 06:002026-09-18 06:00 UTC | settled (nonce-bound) | 200 | 0x9cebfc3d…543f | 1678 ms |
| 1000 units (≈ $0.001 USDC) · L2 matchWhose 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/1196750c-ebdd-4f04-974c-649a117010a0)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.