data.rcqsignals.com/v1/fetch/btc-dca-indicator
1.Catalog declaration
| Resource URL | https://data.rcqsignals.com/v1/fetch/btc-dca-indicator |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x510d1c21788166b0a39f83796bf624e006849690 |
| Declared price (base units) | 50000 |
| Catalog status | active |
| First seen / last seen | 2026-08-31 01:03 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 1 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-18 22:40 UTC | GET | pass | 402 | 354 ms | — |
| 2026-10-17 16:40 UTC | GET | pass | 402 | 416 ms | — |
| 2026-10-15 21:40 UTC | GET | pass | 402 | 633 ms | — |
| 2026-10-14 15:40 UTC | GET | pass | 402 | 568 ms | — |
| 2026-10-13 10:31 UTC | GET | pass | 402 | 337 ms | — |
| 2026-09-29 22:40 UTC | GET | pass | 402 | 558 ms | — |
| 2026-09-29 04:40 UTC | GET | pass | 402 | 446 ms | — |
| 2026-09-28 13:40 UTC | GET | pass | 402 | 677 ms | — |
| 2026-09-27 16:40 UTC | GET | pass | 402 | 285 ms | — |
| 2026-09-26 22:40 UTC | GET | pass | 402 | 85 ms | — |
| 2026-09-26 13:40 UTC | GET | pass | 402 | 384 ms | — |
| 2026-09-25 16:40 UTC | GET | pass | 402 | 219 ms | — |
| 2026-09-24 22:40 UTC | GET | pass | 402 | 464 ms | — |
| 2026-09-24 04:40 UTC | GET | pass | 402 | 385 ms | — |
| 2026-09-23 13:40 UTC | GET | pass | 402 | 456 ms | — |
| 2026-09-22 16:40 UTC | GET | pass | 402 | 296 ms | — |
| 2026-09-21 22:40 UTC | GET | pass | 402 | 176 ms | — |
| 2026-09-21 04:40 UTC | GET | pass | 402 | 229 ms | — |
| 2026-09-20 13:40 UTC | GET | pass | 402 | 2171 ms | — |
| 2026-09-19 16:40 UTC | GET | pass | 402 | 85 ms | — |
| 2026-09-18 22:40 UTC | GET | pass | 402 | 505 ms | — |
| 2026-09-18 13:40 UTC | GET | pass | 402 | 343 ms | — |
| 2026-09-17 16:40 UTC | GET | pass | 402 | 233 ms | — |
| 2026-09-16 22:40 UTC | GET | pass | 402 | 337 ms | — |
| 2026-09-16 13:40 UTC | GET | pass | 402 | 378 ms | — |
| 2026-09-15 13:40 UTC | GET | pass | 402 | 191 ms | — |
| 2026-09-14 16:40 UTC | GET | pass | 402 | 370 ms | — |
| 2026-09-14 04:40 UTC | GET | pass | 402 | 295 ms | — |
| 2026-09-13 13:40 UTC | GET | pass | 402 | 295 ms | — |
| 2026-09-12 22:40 UTC | GET | pass | 402 | 168 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 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-06 19:022026-09-06 19:02 UTC | settled (nonce-bound) | 200 | 0x8fc56b01…dba9 | 1269 ms |
| 50000 units (≈ $0.05 USDC) · L2 matchWhose 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/1f99292b-a97f-4bc0-ac0d-a40e1396aa39)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-10-11 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-09-30 | 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.