Serving node
Serves the network's public relay capabilities from its own HTTPS endpoint and holds shard leases.
- Requires
- Public HTTPS endpoint · provider admission
- May serve
- Mailbox V2 · Queue V1 · Group Object V1
Gao DePIN
Serving nodes carry the network's public capabilities and shard leases; contributors verify them from the outside under probe.v1. Each role is read live from its own signed source.
Reading the signed directory, node readiness and shard leases.
Needs both the serving-node list and the contributor set; one of them is not in hand.
Public HTTPS endpoints · provider admission · signed directory and leases
Outbound-only verification work · no public endpoint · control-plane-signed accounting
Mailbox payloads are end-to-end encrypted and are hard-deleted after acknowledged delivery or when they expire (TTL).
Usage figures are aggregate operational accounting — counts and byte totals per application and shard — never message contents, routes or recipients.
Reading the probe authority's signed contributor set.
Contribution accounting is active. Token payout is currently disabled. Work units count verified probes on control-plane-signed receipts; they are not a token amount.
A serving node and a contributor are different roles with different requirements. A NodeID that holds both is one participant.
Serves the network's public relay capabilities from its own HTTPS endpoint and holds shard leases.
Verifies the relay network from the outside under assignments it cannot choose. Any desktop, phone or node behind NAT can take part.
No usable node answer.
No usable lease answer.
No usable node answer.