Stratum V2 Mining Protocol

Overview

The Stratum V2 mining stack is implemented primarily in the blvm-stratum-v2 module repository (pool/server/protocol). The reference node integrates P2P-side handling: TLV-shaped bytes on the Bitcoin transport can be demuxed into NetworkMessage::StratumV2MessageReceived for the Stratum module. Dedicated miner TCP is bound only by blvm-stratum-v2, not by the node process.

Merge mining is a separate optional plugin (blvm-merge-mining) that depends on the Stratum V2 module.

Where the code lives

Piece	Repository / path
Protocol, messages, pool, server, module API	blvm-stratum-v2 (`src/protocol.rs`, `messages.rs`, `pool.rs`, `server.rs`, `module.rs`, `config.rs`)
Node: P2P TLV demux → `StratumV2MessageReceived`	network_manager.rs (`stratum-v2` feature)
Node: `StratumV2Config`, `[stratum_v2]` in config	config/rpc.rs (type), config/mod.rs (top-level config)

Stratum V2 Protocol

Protocol features

Binary protocol: TLV framing (see module messages / protocol)
Server and pool: Implemented in blvm-stratum-v2 (server.rs, pool.rs)
Message encoding: protocol.rs, messages.rs

Dedicated miner TCP (module)

Miners connect to blvm-stratum-v2’s configured listen_addr. The node does not run an in-process stratum_v2_listener; TLV framing matches the module’s protocol / messages implementation.

P2P ingress

When the stratum-v2 feature is enabled and [stratum_v2].p2p_stratum_demux is true (default), the network layer may detect Stratum V2 TLV on P2P bytes and emit NetworkMessage::StratumV2MessageReceived for dispatch to modules. Set p2p_stratum_demux = false to disable that path (miner TCP on blvm-stratum-v2 is unchanged).

Code: network_manager.rs, network_message_dispatch.rs, network/mod.rs (message variants)

Transport

Mining traffic uses the same transport stack as P2P; see Transport abstraction.

Code: transport.rs

Merge mining (optional plugin)

Merge mining is not part of the core node. It is provided by blvm-merge-mining, which builds on blvm-stratum-v2.

Requires the Stratum V2 module
Activation fee / revenue model: see module and marketplace docs

Documentation

Module system
Merge-mining module repository (if present in your workspace): blvm-merge-mining

Configuration

Node blvm.toml (merge-mining / pool-related fields and P2P demux — does not open miner TCP):

[stratum_v2]
enabled = true
pool_url = "tcp://pool.example.com:3333"  # optional upstream / orchestration
# listen_addr here is informational on the node; miners connect to the module’s listen_addr
listen_addr = "0.0.0.0:3333"
p2p_stratum_demux = true   # false = disable P2P Stratum TLV demux only
transport_preference = "tcponly"
merge_mining_enabled = false
secondary_chains = []

Module config.toml (inside the blvm-stratum-v2 module directory — this is where miners connect):

[stratum_v2]
enabled = true
listen_addr = "0.0.0.0:3333"
pool_url = "stratum+tcp://pool.example.com:3333"  # optional pool mode

Code: StratumV2Config

Usage

Integrate via the blvm-stratum-v2 crate as a node module (StratumV2Module, lib.rs). Older snippets that imported blvm_node::network::stratum_v2::StratumV2Server are obsolete; use the module’s examples and the shared [stratum_v2] keys above (miner TCP is bound by the module, not by blvm-node).

Benefits

Bandwidth: Stratum V2 binary framing vs Stratum V1 text
Modularity: Server/pool logic and miner listen_addr live in blvm-stratum-v2; the node provides chain APIs, optional P2P Stratum TLV demux, and NodeAPI (including send_peer_transport_payload for peer-oriented bytes)
Optional merge mining: Separate commercial module

BLVM Documentation