STRATUM_EXT.md

Stratum protocol extensions

1. Mining algorithm negotiation

Subset of protocol extensions, used to negotiate algorithm between miner and pool/proxy. All extensions is backward compatible with standart stratum protocol.

1.1. Miner defined algorithms list

Miner should send list of algorithms supported. Multiple algorithms in list meant miner can switch algorithms in runtime.

{
  "id": 1, "jsonrpc": "2.0", "method": "login",
  "params": {
    "login": "...", "pass": "...", "agent": "...",
    "algo": ["cn", "cn/0", "cn/1", "cn/xtl"]
  }
}

In case if miner not support dynamic algorithm change, miner should send list with one item, for example "algo": ["cn-heavy"], pool/proxy should provide work for selected algorithm or send error.

1.2. Extended job object

To each job object pool/proxy should add additional field algo and optional variant field.

{
  "id": 1, "jsonrpc": "2.0", "error": null,
  "result": {
    "id": "...",
    "job": {
      "blob": "...", "job_id": "...", "target": "...", "id": "...",
      "algo": "cn/1", "variant": 1
    },
    "status": "OK"
  }
}

{
  "jsonrpc": "2.0", "method": "job",
  "params": {
    "blob": "...", "job_id": "...", "target": "b88d0600", "id": "...",
    "algo": "cn/1"
  }
}

Possible values for variant:

• 1 Force use variant 1 of algorithm.
• 0 Force use original cn/cn-lite algorithm.

This field used for backward compatibility with xmrig 2.5, new miner implementations should support only algo.

If miner not support algorithm connection should be closed by miner to initiate switch to backup pool.

1.3. Algo extension

This extension is backward compatible with xmr-stak extended mining statistics. First, pool should add algo to extensions list:

{
  "id": 1, "jsonrpc": "2.0", "error": null,
  "result": {
    "id": "...",
    "job": {
      "blob": "...", "job_id": "...", "target": "...", "id": "...",
      "algo": "cn", "variant": 1
    },
    "extensions" : ["algo"],
    "status": "OK"
  }
}

Second, miner add fields algo to submit request.

{
  "id": 2, "jsonrpc": "2.0", "method": "submit",
  "params": {
    "id": "...", "job_id": "...", "nonce": "...", "result": "...",
    "algo": "cn/1"
  }
}

Note about xmr-stak, this miner use different algorithm names.

1.4 Algorithm names and variants

Both miner and pool should support short algorithm name aliases:

Long name	Short name	Base algorithm	Variant	Notes
cryptonight	cn	cn	-1	Autodetect works only for Monero.
cryptonight/0	cn/0	cn	0	Original/old CryptoNight.
cryptonight/1	cn/1	cn	1	Also known as monero7 and CryptoNightV7.
cryptonight/2	cn/2	cn	2	CryptoNight variant 2.
cryptonight/xtl	cn/xtl	cn	"xtl"	Stellite (XTL).
cryptonight/msr	cn/msr	cn	"msr"	Masari (MSR), also known as cryptonight-fast
cryptonight/xao	cn/xao	cn	"xao"	Alloy (XAO)
cryptonight/rto	cn/rto	cn	"rto"	Arto (RTO)
cryptonight-lite	cn-lite	cn-lite	-1	Autodetect works only for Aeon.
cryptonight-lite/0	cn-lite/0	cn-lite	0	Original/old CryptoNight-Lite.
cryptonight-lite/1	cn-lite/1	cn-lite	1	Also known as aeon7
cryptonight-lite/ipbc	cn-lite/ipbc	cn-lite	"ipbc"	IPBC variant, obsolete
cryptonight-heavy	cn-heavy	cn-heavy	0	Ryo and Loki
cryptonight-heavy/xhv	cn-heavy/xhv	cn-heavy	"xhv"	Haven Protocol
cryptonight-heavy/tube	cn-heavy/tube	cn-heavy	"tube"	BitTube (TUBE)

Proper pool/proxy implementation should avoid any automatic/autodetect variants, variant must explicitly specified.

1.5 XMR-Stak algorithm names

Mapping between XMR-Stak algorithm names and XMRig names.

XMR-Stak name	XMRig Short name
cryptonight	cn/0
cryptonight-monerov7	cn/1
cryptonight_v7	cn/1
cryptonight_v7_stellite	cn/xtl
cryptonight_masari	cn/msr
cryptonight_lite	cn-lite/0
cryptonight-aeonv7	cn-lite/1
cryptonight_lite_v7	cn-lite/1
cryptonight_lite_v7_xor	cn-lite/ipbc
cryptonight_heavy	cn-heavy
cryptonight_haven	cn-heavy/xhv

Rig identifier

User defined rig identifier. Optional field rigid in login request. More details: fireice-uk/xmr-stak#849

Extended mining statistics

More details: fireice-uk/xmr-stak#66