THE MEMPOOL MUST DIE. The mempool must die, and Teranode is…

THE MEMPOOL MUST DIE.
The mempool must die, and Teranode is about to kill it completely. Instead of digital purgatory, transactions will immediately climb micro trees on broadcast and escape the morass of waiting in limbo to be mined.
The focus on SPV transactions was the primary focus of the SPV-Relay-Federation, and my contributions to same were the secondary focus and related to ephemeral data packets, overlay communication and application integrations.
Anvil nodes were designed for both. SPV transactions and temporal node-2-node communications in order to enable real-time application cohesion and amplification.
But @___siggi___ and team are now arriving with the big sump-pump, and the mempool will dry up.
What dies with the mempool
Everything I planned to build for the April hackathon. The mempool marketplace — monitoring unconfirmed transactions, indexing by address, selling access via micropayments — was the perfect entry. It used every piece of infrastructure Anvil already had: P2P mempool observation, address watching, mesh gossip, x402 payment gating.
Teranode makes all of that irrelevant. No mempool means no mempool product. The hackathon idea died the morning I read that tweet.
What survives
I had to ask the uncomfortable question: without the mempool, what's left for this project?
Strip away the mempool features and what remains is:
Nodes that form persistent authenticated connections
Signed data published to topics
Real-time gossip to every interested peer
Consumers subscribe or query
Payments can gate access
That's not an SPV node with communication bolted on. That's a communication layer that happens to verify payments. The SPV verification still works — it's how x402 payments are validated. But it's plumbing, not the product.
The answer
The Anvil answer: the communication layer was always the value.
Teranode handles transactions. It validates, assembles subtrees, mines blocks. But it does not index data by topic. It does not push real-time updates to app subscribers. It does not route signed messages between identities. It does not gate access with micropayments.
That gap — between transaction processing and application-level data — is where Anvil-Mesh lives. Apps publish signed data to topics. The mesh replicates it across every node. Consumers subscribe for real-time push or query on demand. Operators earn per request.
What Anvil v2.0.0 brings
The pivot forced a complete rethink of what the mesh should do. v2.0.0 is the result:
Addressed messaging.Apps can now send messages to specific identities, not just broadcast to topics. Point-to-point communication with sender signature verification, forwarded across the mesh. This is how agents coordinate, how apps signal each other, how the mesh becomes a communication layer and not just a data relay.
Self-describing mesh.Topics carry metadata — what the data is, how often it updates, what it costs. Publishers declare their identity. Demand is visible across the mesh. A developer arriving at any node can understand what's available without reading documentation.
Topic discovery.Browse all topics, see what data flows, who publishes it, how popular it is. The mesh explains itself.
Node-signed publishing.Operators can publish metadata and identity from the Explorer UI. No curl commands, no external signing tools. The node signs with its identity key.
The protocol question
Anvil-Mesh is an open protocol with a reference implementation, not a product with a gatekeeper. I hold the keys to my nodes. Anyone can run their own. The protocol is documented so that someone could build a compatible node without reading my Go code.
The mesh becomes a real protocol the moment a second independent implementation exists. Until then, it's a reference implementation with documentation and a growing network.
Where the Mesh stands
7 nodes and independent operators I've never coordinated with. They found the repo, installed the binary, and joined the mesh. The gossip works. The data replicates. The payments verify. The apps are magnified.
The mempool had to die for me to see what this project actually was. Not an SPV relay. The coordination seam between Teranode's transaction processing and the applications that people use.
One command to see for yourself:
npm install anvil-mesh