Algorithms

Algorithm can be defined in 3 ways:

By pool, using algorithm negotiation, in this case no need specify algorithm on miner side.
Per pool coin option, currently only usable values for this option is monero and arqma.
Per pool algo option.

Option coin useful for pools without algorithm negotiation support or daemon to allow automatically switch algorithm in next hard fork. If you use xmrig-proxy don't need specify algorithm on miner side.

Algorithm names

Name	Memory	Version	Description	Notes
`kawpow`	-	6.0.0+	KawPow (Ravencoin)	GPU only
`astrobwt`	20 MB	5.8.0+	AstroBWT (Dero).
`cn-pico/tlo`	256 KB	5.5.0+	CryptoNight-Pico (Talleo).
`rx/sfx`	2 MB	5.4.0+	RandomSFX (RandomX variant for Safex).
`rx/arq`	256 KB	4.3.0+	RandomARQ (RandomX variant for ArQmA).
`rx/0`	2 MB	3.2.0+	RandomX (Monero).
`argon2/chukwa`	512 KB	3.1.0+	Argon2id (Chukwa).	CPU only
`argon2/wrkz`	256 KB	3.1.0+	Argon2id (WRKZ)	CPU only
`rx/wow`	1 MB	3.0.0+	RandomWOW (RandomX variant for Wownero).
`rx/loki`	2 MB	3.0.0+	RandomXL (RandomX variant for Loki).
`cn/fast`	2 MB	3.0.0+	CryptoNight variant 1 with half iterations.
`cn/rwz`	2 MB	2.14.0+	CryptoNight variant 2 with 3/4 iterations and reversed shuffle operation.
`cn/zls`	2 MB	2.14.0+	CryptoNight variant 2 with 3/4 iterations.
`cn/double`	2 MB	2.14.0+	CryptoNight variant 2 with double iterations.
`cn/r`	2 MB	2.13.0+	CryptoNightR (Monero's variant 4).
`cn-pico`	256 KB	2.10.0+	CryptoNight-Pico.
`cn/half`	2 MB	2.9.0+	CryptoNight variant 2 with half iterations.
`cn/2`	2 MB	2.8.0+	CryptoNight variant 2.
`cn/xao`	2 MB	2.6.4+	CryptoNight variant 0 (modified).
`cn/rto`	2 MB	2.6.4+	CryptoNight variant 1 (modified).
`cn-heavy/tube`	4 MB	2.6.4+	CryptoNight-Heavy (modified).
`cn-heavy/xhv`	4 MB	2.6.3+	CryptoNight-Heavy (modified).
`cn-heavy/0`	4 MB	2.6.0+	CryptoNight-Heavy.
`cn/1`	2 MB	2.5.0+	CryptoNight variant 1.
`cn-lite/1`	1 MB	2.5.0+	CryptoNight-Lite variant 1.
`cn-lite/0`	1 MB	0.8.0+	CryptoNight-Lite variant 0.
`cn/0`	2 MB	0.5.0+	CryptoNight (original).

Migration to v3

Since version 3 mining algorithm should specified for each pool separately (algo option), earlier versions was use one global algo option and per pool variant option (this option was removed in v3). If your pool support mining algorithm negotiation you may not specify this option at all.

Example

json

{
  "pools": [
    {
      "url": "...",
      "algo": "cn/r",
      "coin": null
      ...
    }
 ],
 ...
}