Leaderboard / wallet.halowerk.com / endpoint
POST https://wallet.halowerk.com/v1/useroperation-lifecycle-tracker
Scores measure reliability and honesty, not output quality.
- Listed only 1 day ago; new listings earn trust over 30 days.
- Answered all 7 probes in the last 7 days.
- Category
- Chain read by llm, confidence 35%
- Latest quote
- $0.001 on Base to 0x2880…4E5E
- Uptime
- 100% / 7d, 100% / 30d
- Delivery
- none not yet paid-tested
- Observed
- none reported yet (opt-in wrapper telemetry)
- HTTPS
- yes
- First listed
- 2026-11-16
- Last probe
- 6h ago
- Next probe
- 2026-11-18 00:03 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 | 1h 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. Judged results feed the "Delivery after payment" component (pass 1, error after payment 0.25, fail 0); inconclusive rows are excluded; a fail in the last 14 days caps the verdict at caution. Methodology.
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 |
|---|---|---|---|---|---|
| 9h ago | Chain read | 35% | llm | v1 | claude-haiku-5-5: The description says the endpoint analyses only caller-supplied evidence and explicitly does not query a chain, so it is not chain_read despite the UserOperation (ERC-4337) name. It returns a classification of supplied evidence with thresholds and missing-signal lists, which is closest to a generic analysis or verdict tool. No service name or tags are given, and the listing is vague, so the fit to any category is weak. 'other' is the most honest choice here. |
| 26h ago | Other | 40% | rules | v1 | rule none matched "" in none |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 6h ago | free | 402 | 215 ms | v2 | yes | $0.001 | 0x2880…4E5E | — |
| 12h ago | free | 402 | 751 ms | v2 | yes | $0.001 | 0x2880…4E5E | — |
| 18h ago | free | 402 | 737 ms | v2 | yes | $0.001 | 0x2880…4E5E | — |
| 24h ago | free | 402 | 720 ms | v2 | yes | $0.001 | 0x2880…4E5E | — |
| 31h ago | free | 402 | 180 ms | v2 | yes | $0.001 | 0x2880…4E5E | — |
| 37h ago | free | 402 | 744 ms | v2 | yes | $0.001 | 0x2880…4E5E | — |
| 43h ago | free | 402 | 793 ms | v2 | yes | $0.001 | 0x2880…4E5E | — |