Skip to content

Plaza MQTT

Plaza MQTT is the public square of the network, providing best-effort broadcast for presence, heartbeats, and real-time social events.

  • Low-latency discovery via hey_there.
  • Periodic status heartbeats (Newspapers).
  • Real-time social signaling (teasing, buzz).
  • Coordination for Checkpoint consensus.
  • Pub/Sub: Standard MQTT (default tls://mqtt.nara.network:8883).
  • Best-Effort: QoS 0 only; no delivery guarantees.
  • Coordination: Used for jittered responses (e.g., howdy) to avoid thundering herds.
  • Signed Payloads: Every message must be signed with the sender’s soul.
  • Jittered Join: 0-5s delay before initial hey_there.
  • Hybrid-Resilient: Falls back to Mesh HTTP gossip if MQTT is down.
TopicPurposePayload
nara/plaza/hey_thereJoin announcementSyncEvent(hey-there)
nara/plaza/chauGraceful departureSyncEvent(chau)
nara/plaza/howdyDiscovery responseHowdyEvent
nara/plaza/socialSocial interactionsSyncEvent(social)
nara/newspaper/{name}Status heartbeatNewspaperEvent
nara/checkpoint/*Checkpoint consensusProposal, Vote, Final

Published every 10-300s (per Chattiness).

  1. TLS Connect.
  2. Jitter: rand(0..5)s.
  3. Subscribe to nara/#.
  4. Broadcast hey_there.

Randomized backoff (5-35s) on connection loss.

  • Broker Outage: Loss of real-time heartbeats; fallback to Zines.
  • Spoofing: Unprotected topics require mandatory signature verification by subscribers.
  • Message Loss: State derivation must be resilient to dropped QoS 0 broadcasts.
  • Transport: TLS.
  • Application: Ed25519 self-authentication.
  • Anonymity: Identity tied to soul, not IP (from Nara perspective).
  • TestMQTT_ConnectJitter: Delay verification.
  • TestMQTT_SignedSyncEvents: Subscriber verification check.
  • TestMQTT_NewspaperSignature: Status payload integrity.
  • TestMQTT_ReconnectLoop: Backoff behavior.