passlisted in Coinbase#2 by calls of 7 on this host
0.02 USDC
per call, as the listing declares it on eip155:
- Validation state
- pass
- Uptime, 7 / 30 / 90 days
- 100% / 100% / 100%
- Calls, trailing 30 days
- 1
- Unique payers, trailing 30 days
- 1
- Last called
- 2026-09-27 22:31 UTC
- First observed by TOLLderived
- 2026-09-28
- Pricederived
- 0.02 USDC
- Networks
- 1
How big is this endpoint among the ones like it?
No trace is drawn of this endpoint’s own volume. Its counters have changed 1 time across 26 observations, and 3 changes are the fewest this site will draw a trace through, because two points and a guess are not a series. Every observation is in the JSON.
At www.securaw.com, cryptovar proof verify takes POST requests, is listed in the Coinbase registry, and falls under identity by TOLL's rules.
On Base, cryptovar proof verify asks 0.02 USDC per call.
Its declared inputs are a json body with the fields service and parameters.
cryptovar proof verify returns json; the example shows result and service.
The daily sweep got a valid payment challenge from cryptovar proof verify on 2026-10-05, as at every sweep since 2026-09-28.
www.securaw.com lists 7 endpoints; cryptovar proof verify is tied 2nd by calls with 5 others.
It accounts for 13% of the calls counted across the host.
cryptovar proof verify drew a single call from a single payer in the trailing 30 days.
The last call to cryptovar proof verify came 8 days before the snapshot, 2026-09-27.
Closest in price to cryptovar proof verify within identity: check at crosscheckapi.com and contract at oracle.cyberwarex.com.
cryptovar proof verify is priced above 72% of comparable listings in identity.
The wallet paid by cryptovar proof verify is the payee of 7 endpoints on one host.
Exactly this price appears on 156 other listings in identity.
the payment options, as of 2026-10-06 06:18 UTC · method · pinnable
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.02 USDC | exact | 0x2cf1aa…ada470 |
the checks, as of 2026-10-05 07:12 UTC · method · pinnableendpoint answered HTTP 402
No named check failed.
Every sweep that observed this endpoint, newest first.
| observed, UTC | state | failed checks | sweep |
|---|---|---|---|
| 2026-10-05 07:12 UTC | pass | 0 | daily-2026-10-05 |
| 2026-10-04 09:54 UTC | pass | 0 | daily-2026-10-04 |
| 2026-10-03 04:54 UTC | pass | 0 | daily-2026-10-03 |
| 2026-10-02 14:09 UTC | pass | 0 | daily-2026-10-02 |
| 2026-10-01 07:12 UTC | pass | 0 | daily-2026-10-01 |
| 2026-09-30 06:30 UTC | pass | 0 | daily-2026-09-30 |
| 2026-09-29 18:50 UTC | pass | 0 | daily-2026-09-29 |
| 2026-09-28 05:36 UTC | pass | 0 | daily-2026-09-28 |
| 2026-09-28 05:31 UTC | pass | 0 | new-after-daily-2026-09-28 |
Presence in a registry, not liveness of the service (method). Newest first.
- listed in Coinbase
From the registry record, not validated by TOLL.the declared schema, as of 2026-09-27 22:31 UTC · method · live
The input and output block
{
"input": {
"body": {
"service": "proof_verify",
"parameters": {
"sha256": "1aa02dbff8eca9062771ff32967ce149ae1f3f837de31e214ae417eed4ebb6e2",
"event_id": "fileproof-20260927191946-1429"
}
},
"type": "http",
"method": "POST",
"bodyType": "json"
},
"output": {
"type": "json",
"example": {
"result": {
"found": true,
"status": "timechain2_verified",
"proof_url": "https://www.securaw.com/cryptovar/proofs/fileproof-20260927191946-1429/status.json",
"hash_match": true,
"recorded_at": "2026-09-27 19:19:46+00",
"bitcoin_status": "pending",
"status_message": "TimeChain2 confirmed. Bitcoin anchoring pending; this is NOT yet a confirmed Bitcoin proof.",
"anchoring_stage": "timechain2_confirmed_bitcoin_pending",
"snapshot_notice": "This receipt is a snapshot. Anchoring status may change; consult the proof link for its current state. generated_at dates this observation, not the payment or settlement.",
"bitcoin_verified": false,
"registered_sha256": "1aa02dbff8eca9062771ff32967ce149ae1f3f837de31e214ae417eed4ebb6e2",
"registry_proof_url": "https://www.securaw.com/securaw/proof.php?event=fileproof-20260927191946-1429",
"status_is_snapshot": true,
"timechain2_anchored": true,
"timechain2_verified": true,
"verification_method": "Securaw server verification; no independent Bitcoin node replay performed by this ACP adapter",
"verification_source": "https://www.securaw.com/api/file-proof-level3.php?event=fileproof-20260927191946-1429",
"registry_block_bitcoin_attested": false
},
"service": "proof_verify"
}
}
}Cite this page
The pinned URL below renders this page from the snapshot of 2026-10-06 06:18 UTC and does not change; the live page does, every six hours. Data reuse is under CC BY 4.0 (terms).
Plain text
TOLL, "cryptovar proof verify on www.securaw.com", snapshot of 2026-10-06 06:18 UTC. https://tollindex.com/e/www-securaw-com-cryptovar-x402-proof-verify-3e3118/at/2026-10-06T06-18Z. Accessed [access date].
BibTeX
@misc{toll-e-www-securaw-com-cryptovar-x402-proof-verify-3e3118-2026-10-06T06-18Z,
author = {TOLL},
title = {cryptovar proof verify on www.securaw.com},
howpublished = {\url{https://tollindex.com/e/www-securaw-com-cryptovar-x402-proof-verify-3e3118/at/2026-10-06T06-18Z}},
year = {2026},
month = {10},
note = {Pinned view of the snapshot of 2026-10-06 06:18 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.