P2P Mesh Network

Overview

The YoorQuezt mesh network is a decentralized P2P relay layer that privately routes transactions from users to block builders. Nodes communicate over QUIC with encrypted gossip, ensuring transactions never touch the public mempool.

Why Run a Node

1. Earn relay fees — Nodes earn a share of protocol revenue proportional to the traffic they relay
2. Lower latency — Nodes closer to block builders reduce inclusion time for your transactions
3. Strengthen the network — More nodes means better censorship resistance and redundancy
4. Multi-chain coverage — Each node can subscribe to multiple chains, increasing network reach
5. Reputation rewards — High-reputation nodes receive priority routing and higher fee shares

Protocol Stack

QUIC + TLS Transport

All peer-to-peer communication runs over QUIC with mutual TLS authentication. Each node generates an ECDSA P-256 keypair and self-signed certificate during yqmesh init.

• Connection multiplexing — Multiple streams over a single QUIC connection
• 0-RTT handshake — Returning peers reconnect instantly
• NAT traversal — QUIC's UDP transport works through most firewalls

Gossip Protocol

Messages propagate through the network via batched gossip:

1. Receive — Node receives a transaction, bundle, or block message
2. Deduplicate — Check the bloom filter (100K capacity, 0.1% FP rate). Drop if seen.
3. Validate — Verify ECDSA signature, decompress (zstd), decrypt (AES-256-GCM)
4. Process — Add to local mempool, trigger block building if applicable
5. Batch — Accumulate messages for up to 100ms or 64 messages (whichever comes first)
6. Propagate — Compress, encrypt, sign, and send the batch to all connected peers

Reputation System

Each peer maintains a reputation score for every connected peer. Peers below the threshold (-10) are disconnected.

Message Types

Security

Block Building

When a node has enough transactions and bundles, it builds a candidate block:

1. Fee-priority ordering — Transactions sorted by gas price (descending)
2. Bundle-first inclusion — Bundles are placed at the top of the block to capture MEV
3. Validation — Each transaction is checked for nonce correctness and sufficient balance

Built blocks are gossiped to the network and forwarded to the MEV engine webhook (if configured) for submission to builders.

Incentive Model

Node operators earn revenue from two sources:

• Relay fees — A percentage of the backrun auction revenue for transactions the node relayed. Distributed proportionally based on the node's position in the relay path.
• Reputation bonus — High-reputation nodes are preferred for priority routing, increasing their share of relay traffic and fees.

Payouts are processed weekly on Ethereum mainnet via the RebateDistributor contract.

Network Topology

                    ┌─────────────┐
                    │  Bootstrap  │
                    │   Server    │
                    └──────┬──────┘
                           │
              ┌────────────┼────────────┐
              │            │            │
        ┌─────┴─────┐ ┌───┴───┐ ┌─────┴─────┐
        │  Node A   │ │ Node B│ │  Node C   │
        │ ETH, BSC  │ │  ETH  │ │ ETH, SOL  │
        └─────┬─────┘ └───┬───┘ └─────┬─────┘
              │            │            │
         ┌────┴────┐  ┌───┴───┐  ┌────┴────┐
         │ Node D  │  │Node E │  │ Node F  │
         │ETH, ARB │  │BSC,SOL│  │ETH, BASE│
         └─────────┘  └───────┘  └─────────┘
              │                        │
              └────────┐  ┌────────────┘
                       │  │
                 ┌─────┴──┴─────┐
                 │  MEV Engine  │
                 │  (webhook)   │
                 └──────────────┘

Nodes discover each other through the bootstrap server, then form a fully connected mesh. Each node can subscribe to different chains. Transactions are relayed only to peers subscribed to the same chain. The MEV engine receives bundles via webhook from any node configured with a webhook_url.