passlisted in Coinbase#1 by calls of 2 on this host
0.005 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
- 3
- Unique payers, trailing 30 days
- 3
- Last called
- 2026-10-06 12:27 UTC
- First observed by TOLLderived
- 2026-09-10
- Pricederived
- 0.005 USDC
- Networks
- 1
How has the volume on this endpoint moved?
At sicher.halowerk.com, log chain verify takes POST requests, is listed in the Coinbase registry, and falls under identity by TOLL's rules.
On Base, log chain verify asks 0.005 USDC per call.
log chain verify takes a json body with the fields records and root_hash.
log chain verify declares nothing about its output; validate flags that as advisory, not a verdict.
log chain verify answered the sweep of 2026-10-06 with a valid 402, as at every sweep since 2026-09-11.
log chain verify shares sicher.halowerk.com with 1 other listed endpoint and is 1st by calls.
log chain verify takes 60% of the calls counted across sicher.halowerk.com.
The registry's counters give log chain verify 3 calls and 3 unique payers over 30 days, every call from a different payer.
The last call to log chain verify came 1 day before the snapshot, 2026-10-06.
Closest in price to log chain verify within identity: chain ens at api.onesource.io and by username at x402.twit.sh.
log chain verify is priced above 18% of comparable listings in identity.
Within identity, 71% of endpoints with counters have fewer calls.
The wallet paid by log chain verify is the payee of 1,679 endpoints across 73 hosts.
189 other listings in identity declare exactly the same price.
the payment options, as of 2026-10-07 05:57 UTC · method · pinnable
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.005 USDC | exact | 0x2880Ed…1C4E5E |
the checks, as of 2026-10-06 16:41 UTC · method · pinnableendpoint answered HTTP 402
bazaar.info.output· advisory, does not affect the verdict · output metadata is present (advisory)
Every sweep that observed this endpoint, newest first.
| observed, UTC | state | failed checks | sweep |
|---|---|---|---|
| 2026-10-06 16:41 UTC | pass | 1 | daily-2026-10-06 |
| 2026-10-05 13:03 UTC | pass | 1 | daily-2026-10-05 |
| 2026-10-04 15:26 UTC | pass | 1 | daily-2026-10-04 |
| 2026-10-03 08:29 UTC | pass | 1 | daily-2026-10-03 |
| 2026-10-02 17:34 UTC | pass | 1 | daily-2026-10-02 |
| 2026-10-01 10:11 UTC | pass | 1 | daily-2026-10-01 |
| 2026-09-30 09:37 UTC | pass | 1 | daily-2026-09-30 |
| 2026-09-29 21:44 UTC | pass | 1 | daily-2026-09-29 |
| 2026-09-23 08:35 UTC | pass | 1 | daily-2026-09-23 |
| 2026-09-22 08:48 UTC | pass | 1 | daily-2026-09-22 |
| 2026-09-21 09:08 UTC | pass | 1 | daily-2026-09-21 |
| 2026-09-19 07:05 UTC | pass | 1 | daily-2026-09-19 |
| 2026-09-17 06:57 UTC | pass | 1 | daily-2026-09-17 |
| 2026-09-16 06:53 UTC | pass | 1 | daily-2026-09-16 |
| 2026-09-15 07:09 UTC | pass | 1 | daily-2026-09-15 |
| 2026-09-14 06:35 UTC | pass | 1 | daily-2026-09-14 |
| 2026-09-13 06:24 UTC | pass | 1 | daily-2026-09-13 |
| 2026-09-12 13:57 UTC | pass | 1 | daily-2026-09-12 |
| 2026-09-11 14:55 UTC | pass | 1 | daily-2026-09-11 |
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-10-06 12:27 UTC · method · live
The input and output block
{
"input": {
"body": {
"records": [
{
"id": "evt-001",
"hash": "7f07223905bb01a5b3f2eda8a61c69280b6e75c938712afcb187bbf2a0d696c4",
"payload": {
"actor": "build-bot",
"action": "created",
"subject": "release-2026.08.19"
},
"sequence": 1,
"timestamp": "2026-08-19T09:00:00Z",
"previous_hash": null
},
{
"id": "evt-002",
"hash": "4584b3d398d3dd075f43d61a2c44991c61d3183c22243582c367cdccb1af664c",
"payload": {
"actor": "release-manager",
"action": "approved",
"subject": "release-2026.08.19"
},
"sequence": 2,
"timestamp": "2026-08-19T09:01:00Z",
"previous_hash": "7f07223905bb01a5b3f2eda8a61c69280b6e75c938712afcb187bbf2a0d696c4"
}
],
"root_hash": "f6e5b0a2eeed0102fcdd3480a6f7a851bb55679f2d3c7e532df3780f46c1b426"
},
"type": "http",
"method": "POST",
"bodyType": "json"
},
"output": null
}Cite this page
The pinned URL below renders this page from the snapshot of 2026-10-07 05:57 UTC and does not change; the live page does, every six hours. Data reuse is under CC BY 4.0 (terms).
Plain text
TOLL, "log chain verify on sicher.halowerk.com", snapshot of 2026-10-07 05:57 UTC. https://tollindex.com/e/sicher-halowerk-com-v1-log-chain-verify-ff0d2b/at/2026-10-07T05-57Z. Accessed [access date].
BibTeX
@misc{toll-e-sicher-halowerk-com-v1-log-chain-verify-ff0d2b-2026-10-07T05-57Z,
author = {TOLL},
title = {log chain verify on sicher.halowerk.com},
howpublished = {\url{https://tollindex.com/e/sicher-halowerk-com-v1-log-chain-verify-ff0d2b/at/2026-10-07T05-57Z}},
year = {2026},
month = {10},
note = {Pinned view of the snapshot of 2026-10-07 05:57 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.