Skip to content

Instantly share code, notes, and snippets.

@machard
Created June 19, 2025 21:29
Show Gist options
  • Save machard/90f653077353f1c81e5d2e91c95abb44 to your computer and use it in GitHub Desktop.
Save machard/90f653077353f1c81e5d2e91c95abb44 to your computer and use it in GitHub Desktop.

The Resonance Protocol — Implementation Overview

The Resonance Protocol is a decentralized, semantic communication system where each message — called a push — is filtered, relayed, and economically settled based on its capacity to resonate through intentional human interaction.

Core Components

1. Client Application (Browser-Native)

The frontend is a lightweight browser interface. It renders one push at a time — image and text — fetched from the user’s connected OpenStreaming node. Navigation is blocked until the user explicitly chooses to relay or block the push.

Each action is cryptographically signed (e.g. via wallet or ephemeral key), timestamped, and broadcast to the user’s node. This forms a propagation event and becomes part of the global relay graph.

There is no scrolling, feed, or queue. One decision. Then the next.

2. OpenStreaming Semantic Mesh

OpenStreaming acts as the execution environment for the protocol. It provides push routing, propagation tracking, and preference-based dissemination. Each node maintains:

  • A registry of active pushes
  • A semantic preference vector per user
  • A log of signed relay/block events

Propagation uses semantic gossip — new pushes are shared only with nodes whose preferences align, based on natural language anchors and model embeddings.

Pushes are discrete entities, not streams. They contain image, text, creator ID, USD budget, and digital signatures. Nodes record who relayed what, when, and under what semantic alignment.

Full details: OpenStreaming Spec

3. EigenLayer-Secured Validation

EigenLayer validators run the scoring layer. These operators must be registered through AVS and are backed by ETH restakers.

Each validator computes push resonance scores after the observation window (e.g. 24h) by analyzing:

  • Propagation depth and timing
  • Semantic consistency of relay paths
  • Relay diversity and entropy curve

Upon confirmation, rewards are disbursed:

  • Relayers receive USD, proportional to influence
  • OpenStreaming operators receive infra coordination fees
  • A USD portion is converted to ETH to compensate EigenLayer restakers
  • Any residual surplus (if push strongly outperforms) may return to the creator

Slashing applies for dishonest reporting or failure to validate.

Economic Logic

  • Push creators must commit USD upfront — no commitment, no propagation
  • Users relay/block pushes without payment, but only relayers of resonant pushes are rewarded
  • Failed pushes are discarded with no refund
  • Operators convert reward slices into ETH to fulfill Eigen AVS payments
  • No tokens, no inflation, no minting — value precedes propagation, reward follows resonance

Outcome

The result is a fully intentional, semantically-aligned content mesh.
Each message becomes an economic wager.
Each click a declaration.
Each relay a public gesture of belief.


Built to reward attention as curation.
Built to make meaning earn its movement.
Built one push at a time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment