Release 33

Breaking Changes

• The clustering configuration has changed! The new shareRelays element resides at the cluster-configuration level as opposed to the old externalStratums element that used to live at pool-configuration level, which is completely replaced by shareRelays. You also don't need to specify topics anymore.

Example:

On the slave (relay) node:

"shareRelay": {
  "publishUrl": "tcp://0.0.0.0:6000"
}

On the master (receiver):

"shareRelays": [{
    "url": "tcp://relay1:6000"
}],

Changes

• A resource leak in the Stratum Client has been fixed
• Stratum Sockets now have TCP keep-alive enabled to prevent sporadic disconnects of slow miners before varDiff can tone down their difficulty
• The ZeroMQ based Master/Slave functionality now supports ZeroMQs Curve Encryption which can be configured using a shared secret known by Master and Slave.

Example:

On the relay node:

"shareRelay": {
  "publishUrl": "tcp://0.0.0.0:6000",
  "sharedEncryptionKey": "foobar"
}

On the master (receiver):

"shareRelays": [{
    "url": "tcp://relay1:6000",
    "sharedEncryptionKey": "foobar"
}],

The keys must match otherwise no shares will be received and recorded. Since this encryption is completely transparent to the Application there's currently no way for MiningCore to detect that the crypto-handshake failed. But sure to test your setup carefully.