Endpoint

C

data.rcqsignals.com/v1/fetch/btc-funding-regime

RC Quantum Data Oracle · score 62/100 · recomputed 4h ago

Compact BTC funding regime state from a four-venue normalized surface: regime label, surface median, 30d z-score, same-sign share, spread, dispersion, venue count, freshness. Ed25519-signed. Data, not advice.

NOT_RESPONDINGNEW_UNKNOWN
First seen
5d ago
Probes stored
5
Payers
2
On-chain volume
$0.05

Score

C
62 of 100
recomputed 4h ago

The score is built from observations we collect ourselves: how the endpoint responds, what the envelope contains, how stable the price and the recipient are, who pays and how often. It is deterministic — the same input always produces the same result.

We do not publish the exact methodology yet. If you own this endpoint, write to us and we will show you, item by item, what drags the score down.

Recent probes

WhenCodeLatencyScheme and network RecipientPriceFindings
6h ago 402 878 ms exact
eip155:8453
0x510d…9690 0.010000 clean
12h ago 402 726 ms exact
eip155:8453
0x510d…9690 0.010000 clean
4d ago — 10409 ms — — — E_UNREACHABLE:fetch failed
4d ago 402 1114 ms exact
eip155:8453
0x510d…9690 0.010000 clean
5d ago 402 1068 ms exact
eip155:8453
0x510d…9690 0.010000 clean

Settlements to this wallet

WhenPayerAmountFacilitatorTransaction
3d ago 0xc9c7…1670 $0.01 not in registry 0xe3887f…3b0f
4d ago 0x556d…0484 $0.01 not in registry 0x47a244…43c3
4d ago 0x556d…0484 $0.01 not in registry 0x6cf4cf…9c2c
4d ago 0x556d…0484 $0.01 not in registry 0x090dac…9e50
4d ago 0x556d…0484 $0.01 not in registry 0x6e6d3a…766b

Reference

URLhttps://data.rcqsignals.com/v1/fetch/btc-funding-regime
Sourcesbazaar
Recipient per catalogue0x510d1c21788166b0a39f83796bf624e006849690
Price per catalogue0.010000
Machine access/v1/endpoint · /full · badge

Is this your endpoint?

The score is built only from public observations. If something we recorded is wrong — say our prober hit you during maintenance — write to us. We will recheck and publish your reply next to the score.

We do not delete accurate observations. The prober makes at most one request per second per host and only asks for the payment challenge — it never pays and never takes content.

Next

Market overview →

Payments, median ticket, who pays whom, who settles.

Wallets →

Payers, recipients and facilitators, listed separately.

Facilitators →

Who actually settles — including those in no public registry.

API →

Verdict before payment, seller and wallet scores, market aggregates.