Patent Explainer: How the Bit Trust Stack Runs on the Federated SPV Mesh

Two Layers, Ten Patents

BSV now has two infrastructure layers:

ARC — the miner-operated transaction submission service. You POST a raw transaction. ARC broadcasts it into Teranode, tracks the lifecycle, and gives you callbacks and Merkle proofs. Direct line to miners. Battle-tested. This is the write layer.

Federated SPV Mesh — a network of lightweight bridge nodes that peer with each other over WebSocket and with the Bitcoin network over native P2P. Each bridge syncs headers, verifies Merkle proofs, relays ephemeral data, and discovers peers automatically via on-chain registration. This is the read layer, the data layer, and the relay layer.

The Bit Trust patent portfolio maps onto both layers. Here's how.

The Mapping

F-001: The $402 Protocol → Mesh Facilitator

The $402 protocol turns URL paths into token markets. A server returns HTTP 402 Payment Required. A client pays. The server delivers content.

The protocol specifies DNS-based facilitator routing — a CNAME record pointing to a service that handles payment verification and content delivery. A Federated SPV bridge IS a facilitator. It can verify payments via Merkle proofs (Section 8 of the whitepaper), serve content, and route between clients and miners.

A $402 facilitator running as a mesh bridge means payment verification is decentralised. No single API to rate-limit or take down. The mesh absorbs node failures. The facilitator routes around them.

F-002: Autonomous Agent Discovery → Agents Crawl the Mesh

F-002 describes AI agents that crawl the web for $ URLs, evaluate content as investments, acquire tokens, and re-serve content for revenue. These agents need a read layer — somewhere to discover content, check prices, verify ownership.

The mesh provides this. Any bridge exposes REST + WebSocket APIs for querying address history, token balances, inscription data, and transaction status. An agent can query any bridge in the mesh. If one goes down, the agent queries another. Discovery is resilient because the mesh is self-healing.

An autonomous agent running on a ClawMiner connects to the mesh, crawls for $ URLs, evaluates bonding curve positions, and acquires tokens — all through decentralised reads. No single point of failure.

F-003: Bit Trust → IP Registration Verified Through Mesh

Bit Trust registers intellectual property on-chain with identity binding and encrypted vaults. Third parties verify IP claims by querying blockchain state — checking inscription data, identity chains, and timestamp proofs.

The mesh provides the verification layer. Any bridge can return the inscription data for a Bit Trust registration. The Merkle proof confirms inclusion in a block. The identity chain ($401 strands) can be resolved through mesh queries. No need to trust a single indexer.

F-004: ClawMiner → IS a Mesh Node

This is the direct connection. A ClawMiner is a hardware AI agent device. The Federated SPV mesh is a network of bridge nodes. Every ClawMiner ships with a federation bridge.

npm install -g @relay-federation/bridge
relay-bridge init
relay-bridge start

The ClawMiner joins the mesh on boot. It syncs headers, peers with other bridges, relays data, and serves as a $402 facilitator. Every device sold strengthens the network. The $402 licence buys you a node in the infrastructure.

The ClawMiner's three functions — INDEX, TRADE, EARN — all benefit from mesh participation:

INDEX: Query the mesh for content to index instead of relying on a single API
TRADE: Verify token balances and transaction status through mesh reads
EARN: Submit Proof of Indexing proofs through the mesh as well as through ARC

F-005: DNS-DEX → Domain Verification Through Mesh

DNS-DEX tokenises domain names with multi-proof ownership verification. The mesh adds a decentralised layer for verifying domain token state — querying balances, checking ownership proofs, and resolving domain-to-token mappings across multiple bridges.

F-006: HTTP Status Code Suite → The Full Stack on Mesh

The tripartite $401/$402/$403 stack runs on the mesh:

$401 identity chains — root and strand inscriptions queried via any bridge
$402 payment tokens — balances and Merkle proofs verified through mesh reads
$403 permission tokens — compliance state checked against mesh-served data

The mesh provides the decentralised read layer that makes the entire protocol suite queryable without a centralised API.

F-007: Proof of Indexing → Runs ON the Mesh

This is the deepest integration. F-007 describes trustless verification of derived state in overlay networks — exactly what the Federated SPV mesh does. Bridges verify each other's state via Merkle proofs and header chains.

Proof of Indexing consensus can run as a mesh protocol. Bridges that index content submit proofs. Other bridges verify those proofs. Consensus emerges from the mesh itself rather than from a single pool server.

F-008: Signed Semantic Triples → Relayed as Ephemeral Data

The mesh relays "signed ephemeral signals — rates, attestations, notifications — without on-chain transactions." Signed semantic triples — subject-predicate-object relationships with identity-bound authorship — are exactly this kind of ephemeral data.

A ClawMiner can broadcast semantic triples across the mesh: "this domain → is-owned-by → this identity" or "this patent → is-licensed-to → this entity." Topic-filtered, TTL-bounded, gossip-propagated. The triples live on the mesh without requiring an on-chain transaction for every assertion.

F-009: Ticket CDN → Mesh IS the CDN

Ticket CDN describes content distribution controlled by limited-supply ticket tokens. The mesh IS a content distribution network — bridges serve content, verify ticket token ownership, and route around failures.

A ticket holder queries any bridge to verify their balance. The bridge serves the gated content. If that bridge goes down, the ticket holder queries another. The CDN is the mesh. The mesh is self-healing.

F-010: Tokenised Patent Licensing → Licence Verification Through Mesh

PATL licence grants are inscribed on-chain. Any third party can verify a licence by querying token balances and PATL inscriptions. The mesh provides the decentralised query layer — no need to hit a single API to check whether someone holds a valid licence.

The Architecture

Your App / ClawMiner
         |
+--------+---------+
|                  |
Federated SVP    ARC
Mesh             Endpoint
(read, relay,    (tx submission,
verify, P2P)     miner callbacks)
|                  |
+--------+---------+
         |
   Miners / Teranode

Every patent in the portfolio uses both layers. ARC for writing transactions. The mesh for everything else.

What This Means for ClawMiner

Every ClawMiner ships with:

Federation bridge — joins the mesh, serves as a node
$402 facilitator — verifies payments, serves gated content
Proof of Indexing — indexes content, submits proofs via mesh + ARC
MCP agent — autonomous economic actor with $KWEG tools
$402 Startup Licence — PATL inscription, 1M+ $KWEG tokens

The device is a mesh participant. The licence grants the right to run the patents. The mesh is the infrastructure the patents describe. Buy a ClawMiner, join the mesh, strengthen the network.