Leaderboard / mev.halowerk.com / endpoint
POST https://mev.halowerk.com/v1/sandwich-victim-detector
Scores measure reliability and honesty, not output quality.
- Listed only 2 days ago; new listings earn trust over 30 days.
- Answered all 10 probes in the last 7 days.
- Category
- Signal by llm, confidence 50%
- 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
- 9m ago
- Next probe
- 2026-11-19 01:56 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 | 3h 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 |
|---|---|---|---|---|---|
| 30h ago | Signal | 50% | llm | v1 | claude-haiku-5-5: The endpoint classifies whether a trade was a sandwich-attack victim from caller-supplied evidence and returns a verdict with confidence and thresholds, which is a risk verdict. It is MEV-related, so crypto_market or chain_read could fit, but it explicitly does not query a chain and returns an analytical classification rather than market data, so signal is the closest match. |
| 46h ago | Crypto market data | 60% | rules | v1 | rule crypto_market matched "mev" in metadata |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 9m ago | free | 402 | 770 ms | v2 | yes | $0.001 | 0x2880…4E5E | — |
| 7h ago | free | 402 | 711 ms | v2 | yes | $0.001 | 0x2880…4E5E | — |
| 14h ago | free | 402 | 701 ms | v2 | yes | $0.001 | 0x2880…4E5E | — |
| 20h ago | free | 402 | 691 ms | v2 | yes | $0.001 | 0x2880…4E5E | — |
| 26h ago | free | 402 | 771 ms | v2 | yes | $0.001 | 0x2880…4E5E | — |
| 33h ago | free | 402 | 238 ms | v2 | yes | $0.001 | 0x2880…4E5E | — |
| 39h ago | free | 402 | 818 ms | v2 | yes | $0.001 | 0x2880…4E5E | — |
| 45h ago | free | 402 | 194 ms | v2 | yes | $0.001 | 0x2880…4E5E | — |
| 2d ago | free | 402 | 237 ms | v2 | yes | $0.001 | 0x2880…4E5E | — |
| 2d ago | free | 402 | 207 ms | v2 | yes | $0.001 | 0x2880…4E5E | — |
| 3d ago | free | 402 | 191 ms | v2 | yes | $0.001 | 0x2880…4E5E | — |