Directory / detect.halowerk.com
detect.halowerk.com/v1/F-TD2000-DOCUMENTS-17/matrix-v11-state-resolution-v2-auth-chain-mainline-conf working
https://detect.halowerk.com/v1/F-TD2000-DOCUMENTS-17/matrix-v11-state-resolution-v2-auth-chain-mainline-conflict-projection
Before you pay
- Advice
ok- Protocol
- x402 · http · POST
- Asks for
- 0.003 USDC on base
- Catalogue says
- 0.003 USDC
- Pays to
0x2880EdfFF13100677Bf97A3CBdF3Bc34771C4E5E- Last check
- 10 h ago · 16 ms · HTTP 402
- Detail
- 402 with valid terms
Reliability
- Uptime 24 h
- 100.0% (2 checks)
- Uptime 7 days
- 100.0% (7 checks)
- Uptime, 7 days observed
- 100.0% (signed daily)
- Listed by
- x402-bazaar
- First seen by alalanet
- 2026-11-05 22:12 UTC
Trust Score
47 of 95
Open formula: /trust. Recomputed once a day from what alalanet observed and its sources publish; nothing here can be bought.
shared_pay_to— the same receiving address serves 50 or more hosts (−5).single_payer_demand— at most one paying wallet counts — on chain, after the funding check when one was made, or in the catalogue's own figures; often it is the seller's own (paid demand counts 2 at most).
Payments
- Read on chain by alalanet
- 11,192 payments from 49 wallets, $37.54USDC on Base into this address since 2026-10-17; alalanet's own test wallet excluded
- Repeat payers
- 25 paid on two or more days
- Largest payer
- 60.8% of the payments
- Independent payers
- 9 of 49 countedalalanet read the wallets of the 10 largest payers: 1 funded by the seller, not counted; 0 joined to another payer (funded by it, or by the same address within 72 hours before both paid); 6 first funded within 72 hours before paying; the other 39 payers are not counted
This address also receives for 115 other hosts; the payments above are for all of them.
This listing was first seen on 2026-11-05; payments before that day may be missing, so the figures are a lower bound.
- Catalogue says
- 1 calls from 1 payer in 30 daysthe catalogue's own counter (x402 Bazaar), not checked by alalanet
Description (from the catalogue, unverified)
Resolve finite room-v11 state conflicts using auth-chain difference, reverse-topological power ordering, mainline sorting and iterative auth. Complete graph and publicly exact auth facts/rules required; no network/moderation verdict.
Signed history
| When | Statement | Log index |
|---|---|---|
| 2026-11-16 00:14 UTC | 22665b5b…cc7336 daily summary | 836247 |
| 2026-11-15 00:15 UTC | 57553bfa…e5e12e daily summary | 760098 |
| 2026-11-13 00:12 UTC | b781ec42…c41afd daily summary | 606705 |
| 2026-11-11 00:15 UTC | 87154975…dc4cc4 daily summary | 448175 |
| 2026-11-09 00:13 UTC | d5c1094e…025bb5 daily summary | 274182 |
| 2026-11-08 00:10 UTC | 00b25276…2a0d4c daily summary | 195711 |
| 2026-11-07 00:13 UTC | 08583df3…fae31c daily summary | 116504 |
Verify any statement offline: how.
For agents and owners
JSON: https://alalanet.com/v1/services/gyvumyxsaer2sunh
Badge:
<a href="https://alalanet.com/s/gyvumyxsaer2sunh"><img src="https://alalanet.com/badge/gyvumyxsaer2sunh" alt="alalanet status"></a>
Own this service? Claim it (free). Do not want it checked? See the prober page.