Litcoincash

[belmix]

LCC add minotaurx
https://github.com/litecoincash-project/litecoincash/releases/tag/v0.16.3

RPC / Config changes
getblockheader and getblock will now show the algo for a given pow block.

Block templates differ between MinotaurX and sha256d blocks. Therefore, the getblocktemplate RPC method accepts a new parameter, powalgo, to specify either minotaurx or sha256d:

getblocktemplate '{"powalgo":"minotaurx"}'
or
getblocktemplate '{"powalgo":"sha256d"}

use
"gbtArgs": [{"rules": [ "segwit" ]}, "minotaurx"], - gbtArgs - not used already in new version core?
"gbtArgs": [{"powalgo": [ "minotaurx" ]}], maybe? )
"blockTemplateRpcExtraParams": [ "minotaurx" ], - right?

[belmix]

[belmix]

[belmix]

[belmix]

why does it add {"rules": [ "segwit" ]} -
because BlockTemplateRpcExtraParams?

[belmix]

only a parameter is needed {"powalgo": "minotaurx" } - maybe this is possible through - GBTArgs?

[belmix]

ideas suggestions are we correct the code or is it possible to run it? )))

[belmix]

litecoincash disabled asicboost - failed to submit block: high-hash

Note to sha256d ASIC miners
As part of our multi-pow implementation, we have elected to take back control of the 32-bit block version field.

It was previously observed that some ASIC miners would abuse ~13 high bits of the version fields to give them extra nonce space.

This will no longer be tolerated, and block versions are validated more tightly. To ensure your blocks don't get rejected, we recommend using the exact version field value that getblocktemplate gives you.