The gossip protocol and event-driven state replication. All 46 event types, signing, propagation, sync, and data retention.
The event system is the backbone of the network. Every state change -- listings, purchases, attestations, governance votes, MPC ceremonies, everything -- is captured as a signed protocol event and replicated across all nodes via gossip. The event log is the single source of truth. Database tables are materialized views over the event stream.
Every protocol event follows a common envelope:
interface ProtocolEvent {
id: string; // UUIDv4, unique per event
kind: EventKind; // One of 46 event types
actor: string; // Ed25519 public key of the emitter
payload: Record<string, unknown>; // Event-specific structured data
signature: string; // Ed25519 signature (hex-encoded)
timestamp: number; // Unix milliseconds (UTC)
hash: string; // SHA-256 of canonical JSON payload
protocolVersion: string; // "mvp-1"
}Every event is signed by the emitting node's Ed25519 key. The signing process:
signature and hash) to canonical JSON (sorted keys, no whitespace).hash and signature to the event.Any node can verify any event by re-canonicalizing the payload, recomputing the hash, and checking the signature against the actor's known public key. Tampered events are detected and discarded.
| Kind | Description |
|---|---|
AGENT_ANNOUNCE | Node announces itself to the network with its capabilities, version, and endpoints |
AGENT_REGISTER | Node formally registers and bonds stake to become an active participant |
AGENT_HEARTBEAT | Periodic liveness signal broadcast to neighbors (default: every 30 seconds) |
| Kind | Description |
|---|---|
LISTING_CREATE | A new listing is published (includes asset data, price, expiration) |
LISTING_DELIST | Seller removes a listing. Names the listing and carries the seller's proof (their wallet signature for that listing, or their cancel transaction on an EVM chain), which every node checks before it stores the event |
ORDER_INTENT | Buyer declares intent to purchase (pre-session) |
BTC_PURCHASE_SUBMITTED | A Bitcoin purchase transaction has been broadcast |
EVM_PURCHASE_SUBMITTED | An EVM-chain purchase transaction has been broadcast |
SOL_PURCHASE_SUBMITTED | A Solana purchase transaction has been broadcast |
TX_OBSERVED | A witness observes the transaction on-chain |
TX_ATTESTATION | A witness signs and publishes their validation verdict |
TX_FINALIZED | Supermajority reached -- transaction is settled |
| Kind | Description |
|---|---|
MISBEHAVIOR_PROOF | Evidence of witness misbehavior (wrong attestation with proof) |
RUNTIME_CONFIG_VOTE_CAST | Node votes on a governance parameter change |
NODE_FEE_WALLETS_UPDATED | Node updates its fee-receiving wallet addresses |
NODE_STAKE_UPDATED | Node's staked amount has changed (deposit or withdrawal) |
NODE_BENCHMARK_SUBMITTED | Node publishes its benchmark results for performance ranking |
NODE_DELEGATE_STATUS_CHANGED | Node toggles its delegate availability on or off |
NODE_DELEGATION_CHANGED | A delegator assigns or revokes delegation to a delegate |
REWARD_CLAIM_CREATED | A reward claim is initiated for earned fees |
REWARD_CLAIM_SIGNED | The MPC wallet co-signs a reward claim payout |
MODERATION_VOTE_CAST | Node votes on a content moderation action |
FOUNDATION_TREASURY_TX | Foundation executes a treasury transaction (fully transparent) |
| Kind | Description |
|---|---|
MPC_CEREMONY_PREPARE | Coordinator initiates a new DKG or signing ceremony |
DKG_COMMITMENT | Participant publishes their Feldman VSS commitment |
DKG_SHARE_EXCHANGE | Participant distributes encrypted key shares to peers |
DKG_VERIFICATION | Participant confirms received shares are consistent |
CEREMONY_FINALIZED | DKG complete -- public key derived, shares distributed |
SIGN_NONCE_COMMIT | Signing participant commits to a nonce (hash of R-value) |
SIGN_NONCE_REVEAL | Signing participant reveals their actual nonce |
SIGN_PARTIAL | Signing participant contributes their partial signature |
RESHARE_OLD_SHARE | Existing holder re-shares their key material to updated set |
CLAIM_EPOCH_UPDATED | Reward claim epoch boundary has advanced |
TREASURY_SPEND_PROPOSED | A treasury spend is proposed for governance approval |
| Kind | Description |
|---|---|
PROFILE_ANNOUNCED | User announces or updates their public profile |
CHAT_THREAD_OPENED | A new direct-message thread is opened between buyer and seller |
NODE_MESH_PING | Low-level mesh connectivity probe between neighbors |
RATE_LIMIT_VIOLATION | Node detected and logged a rate-limit breach from a peer |
| Kind | Description |
|---|---|
RELEASE_MANIFEST_SEEN | Node has observed and validated a new release manifest |
| Kind | Description |
|---|---|
SESSION_COMMIT | Purchase session is committed with buyer intent and timestamp |
UI_SESSION_QUOTE | UI agent produces a signed quote for the session |
UI_SESSION_ATTESTATION | UI agent attests to the session parameters it served |
Events propagate through the network using a push/pull model:
Push (WebSocket): When a node creates or receives a new valid event, it immediately pushes a 33-byte notification to all connected neighbors via the binary wire protocol (0x04 EVENT_NOTIFY + 32-byte hash). Neighbors that do not have the event pull the full payload.
Pull (HTTP fallback): Nodes that missed push notifications (due to disconnection, restart, or partition) catch up via HTTP sync:
GET /api/gossip/sync?since=<timestamp>&limit=250Sync is paginated at 250 events per page. The response includes a nextCursor for continuation. Nodes can filter by event kind to prioritize critical events during catch-up.
Pull on reconnect: When a node reconnects to a neighbor, it immediately initiates a sync from its last-known cursor. This ensures no events are lost during network partitions.
Not all events are stored forever. The protocol defines three retention tiers:
Tier 1 -- Permanent: Events that define protocol state and must be replayable forever.
Tier 2 -- Retention-bounded: Events kept for a configurable retention window (default: 90 days), then pruned.
Tier 3 -- Ephemeral: Events used for real-time coordination only. Not persisted after processing.
Events are projected into materialized state tables. The event log is always authoritative -- if a table disagrees with the event log, the table is wrong and must be rebuilt:
Event Log (source of truth)
|
v
Projectors
|
+---> Listing state (OPEN, SOLD, DELISTED, EXPIRED)
+---> Order state (PENDING, ATTESTING, FINALIZED, FAILED)
+---> UTXO tracking (spent/unspent)
+---> Node registry (active, suspended, banned)
+---> Governance config (current parameter values)
+---> MPC key state (ceremony status, share assignments)
+---> Delegation graph (who delegates to whom)
+---> Strike ledger (per-node misbehavior history)The entire protocol state can be reconstructed by replaying events from genesis. Deterministic replay means the same events always produce the same state, regardless of timing or order of receipt. The Rust node-core provides efficient batch replay:
POST /v1/events/replay
{
"fromSequence": 0,
"toSequence": "latest",
"batchSize": 1000
}All foundation actions -- treasury withdrawals, governance overrides, admin operations, parameter changes -- are signed protocol events gossiped to every node and visible in the public explorer. There is no off-chain authority. Everything is on the record, verifiable by anyone running a node.