detect.halowerk.com/v1/F-A-NIGHT-PROTOCOL-WILL/mqtt5-will-delay-session-expiry-resumption working

Trust Score

34 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,284 payments from 46 wallets, $37.71

USDC on Base into this address since 2026-10-14; alalanet's own test wallet excluded

Repeat payers

24 paid on two or more days

Largest payer

60.8% of the payments

Independent payers

9 of 46 counted

alalanet 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 36 payers are not counted

This address also receives for 114 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 days

the catalogue's own counter (x402 Bazaar), not checked by alalanet

Description (from the catalogue, unverified)

An offline MQTT session fixture author needs whether an old pending Will is published, delayed or suppressed when a client resumes versus clean-starts before session expiry, without involving message delivery QoS or contacting a broker.

Signed history

Verify any statement offline: how.

For agents and owners

JSON: https://alalanet.com/v1/services/qu6hfwmqcrug3khl

Badge:

<a href="https://alalanet.com/s/qu6hfwmqcrug3khl"><img src="https://alalanet.com/badge/qu6hfwmqcrug3khl" alt="alalanet status"></a>

Own this service? Claim it (free). Do not want it checked? See the prober page.