DEMAND is the first pool to support template declaration for pooled mining.
Leveraging the power of StratumV2 DEMAND offer's better latency and less bandwidth usage to miners.
- Improved security through encryption and authentication.
- More freedom thanks to template declaration.
- Best transperency with open PPLNS.
Miners that still want to use Stratum V1 can do so via our sv1 endpoint or by using our translator proxy which allows sv1 mining with all the advantages of an StratumV2 pool.
Get Started
The pool is in beta but anyone can already try it
Pooled Sv2
                  Pooled mining through the Sv2 enpoint                  
Solo Sv2
                  Pooled mining through the Sv2 endpoint                  
Pooled Sv1
                  Pooled mining through the Sv1 endpoint                  
Solo Sv1
                  Solo mining through the Sv1 endpoint                  
With Job Declarator
                  Solo mining through the Sv1 endpoint                  
With Translator
                  Solo mining through the Sv1 endpoint                  
Pooled Sv2
Pooled mining through the Sv2 enpoint
SetupConnection {
protocol: Protocol::MiningProtocol,
min_version: 2,
max_version: 2,
flags: 0b0000_0000_0000_0000_0000_0000_0000_0001,
endpoint_host: "mining.dmnd.work",
endpoint_port: 2000,
vendor: "vendor",
hardware_version: "hw_version",
firmware: "firmware_version",
device_id: "[device_id]::pooled::[token]",
}
The important part here is device_id: "[device_id]::pooled::[token]" [device_id] will be used to log the downstream activity.
pooled intsructs the pool to use pooled mining for that connection.
[token] is a securty check so that we are sure which account must be credited for the share produced.
Sv2 endpoint is: mining.dmnd.work:2000
Solo Sv2
Solo mining through the Sv2 endpoint
SetupConnection {
protocol: Protocol::MiningProtocol,
min_version: 2,
max_version: 2,
flags: 0b0000_0000_0000_0000_0000_0000_0000_0001,
endpoint_host: "mining.dmnd.work",
endpoint_port: 2000,
vendor: "vendor",
hardware_version: "hw_version",
firmware: "firmware_version",
device_id: "[device_id]::solo::[bitcoin address]",
}
The important part here is device_id: "[device_id]::pooled::[bitcoin address]" [device_id] will be used to log the downstream activity.
pooled intruct the pool to use pooled mining for that connection.
[bitcoin address] is the address that will be used in the coinbase output, it must be a bitcoin address for bitcoin network (not testnet) serialized as a bech32 or base58 string.
Sv2 endpoint is: mining.dmnd.work:2000
Pooled Sv1
Pooled mining through the Sv1 enpoint
{
"message": {
"id": 3,
"method": "mining.authorize",
"params": ["username", "[token]"]
},
"id": "mining.authorize"
}
The important part here is device_id: ""params": ["[username]", "[token]"]" [username] will be used to log the downstream activity.
[token] is a securty check so that we are sure which account must be credited for the share produced.
Sv1 endpoint is: mining.dmnd.work:1000
Solo Sv1
Solo mining through the Sv1 enpoint
{
"message": {
"id": 3,
"method": "mining.authorize",
"params": ["username", "[bitcoin address]"]
},
"id": "mining.authorize"
}
The important part here is device_id: ""params": ["[username]", "[bitcoin address]"]" [username] will be used to log the downstream activity.
[bitcoin address] is the address that will be used in the coinbase output, it must be a bitcoin address for bitcoin network (not testnet) serialized as a bech32 or base58 string.
Sv1 endpoint is: mining.dmnd.work:1000
Team
DEMAND team
Alejeandro De La Torre
Chief Executive OfficerMining pool veteran, former vp of btccom and poolin, taprootactivation coordinator
Filippo Merli
Chief Technology OfficerCreator of SRI the first stratum v2 open source implementation