Leaderboard / sicher.halowerk.com / endpoint
POST https://sicher.halowerk.com/v1/oss-openssl-rfc3161-request-build
Scores measure reliability and honesty, not output quality.
- Listed only 1 day ago; new listings earn trust over 30 days.
- Answered all 6 probes in the last 7 days.
- Category
- Data transform by llm, confidence 72%
- Latest quote
- $0.001 on Base to 0x2880…4E5E
- Uptime
- 100% / 7d, 100% / 30d
- HTTPS
- yes
- First listed
- 2026-11-16
- Last probe
- 5h ago
- Next probe
- 2026-11-17 16:27 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| cdp | exact | Base | 0x8335…2913 | $0.001 | 0x2880…4E5E | eip3009 | yes | 2h ago |
Paid probes
No paid probes yet. Paid probing is off by default and runs weekly per host under a strict spend cap; each paid probe links to its on-chain transaction here.
Delivery checks
Inside each paid probe we ask for something whose correct answer we know, then compare. A pass means the seller delivered what it was paid for; a fail means it charged and returned something wrong; inconclusive means we could not judge (no reference, unknown input shape, or a non-2xx response). Every row carries the request, the response hash and the reference so the verdict can be reproduced. Delivery results do not affect scores yet.
No delivery checks yet. They run inside the weekly paid probe.
Classification history
Every classification is kept; the newest row is the current category. Rules match the listing text; the model is consulted only when the rules are unsure.
| When | Category | Confidence | Method | Version | Evidence |
|---|---|---|---|---|---|
| 14h ago | Data transform | 72% | llm | v1 | claude-haiku-5-5: The endpoint takes a SHA-256 digest and deterministically encodes it into an RFC 3161 TimeStampReq ASN.1 structure, returning a binary artifact and the imprint. That is a deterministic encoding transform rather than a timestamp authority call, so data_transform fits best, though the cryptographic protocol context adds some ambiguity versus document or compliance. |
| 18h ago | Data transform | 60% | rules | v1 | rule data_transform matched "sha-256" in description |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 5h ago | free | 402 | 548 ms | v2 | yes | $0.001 | 0x2880…4E5E | — |
| 11h ago | free | 402 | 581 ms | v2 | yes | $0.001 | 0x2880…4E5E | — |
| 17h ago | free | 402 | 502 ms | v2 | yes | $0.001 | 0x2880…4E5E | — |
| 23h ago | free | 402 | 500 ms | v2 | yes | $0.001 | 0x2880…4E5E | — |
| 30h ago | free | 402 | 508 ms | v2 | yes | $0.001 | 0x2880…4E5E | — |
| 36h ago | free | 402 | 152 ms | v2 | yes | $0.001 | 0x2880…4E5E | — |