Directory / detect.halowerk.com
detect.halowerk.com/v1/rest-b16-proto2/xmpp-stream-management-counter-resumption-replay-ledger working
https://detect.halowerk.com/v1/rest-b16-proto2/xmpp-stream-management-counter-resumption-replay-ledger
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
- 4 h ago · 15 ms · HTTP 402
- Detail
- 402 with valid terms
Reliability
- Uptime 24 h
- 100.0% (9 checks)
- Uptime 7 days
- 100.0% (69 checks)
- Uptime, 9 days observed
- 100.0% (signed daily)
- Listed by
- x402-bazaar
- First seen by alalanet
- 2026-11-05 22:12 UTC
Trust Score
62 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,123 payments from 47 wallets, $37.02USDC on Base into this address since 2026-10-15; alalanet's own test wallet excluded
- Repeat payers
- 24 paid on two or more days
- Largest payer
- 61.1% of the payments
- Independent payers
- 9 of 47 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 37 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)
An XMPP stream fixture author needs exact unacknowledged-stanza counts and replay positions after transport loss/resumption, including uint32 wrap and too-many-handled errors, independently of roster presence or end-to-end delivery receipts.
Signed history
| When | Statement | Log index |
|---|---|---|
| 2026-11-14 00:19 UTC | 487ab2a1…f912de daily summary | 718390 |
| 2026-11-13 00:17 UTC | ba8a46d3…796ea3 daily summary | 640738 |
| 2026-11-12 00:20 UTC | fd4b722f…4b547b daily summary | 562218 |
| 2026-11-11 00:20 UTC | a7b9365d…1e9cf6 daily summary | 481612 |
| 2026-11-10 00:19 UTC | 613d3287…55c498 daily summary | 399278 |
| 2026-11-09 00:17 UTC | 1e0e8ae5…f2379c daily summary | 307858 |
| 2026-11-08 00:15 UTC | 11f9285e…46e7d8 daily summary | 229683 |
| 2026-11-07 00:18 UTC | c354dd11…6b17e0 daily summary | 150933 |
| 2026-11-06 00:14 UTC | f5b1170c…6a2dc2 daily summary | 58016 |
Verify any statement offline: how.
For agents and owners
JSON: https://alalanet.com/v1/services/wp2r7zkzywopqywv
Badge:
<a href="https://alalanet.com/s/wp2r7zkzywopqywv"><img src="https://alalanet.com/badge/wp2r7zkzywopqywv" alt="alalanet status"></a>
Own this service? Claim it (free). Do not want it checked? See the prober page.