NFT framework is inadvertently disabled in mainnet
Summary
NFT operations are not possible in mainnet
Steps to reproduce
Attempt to register a protocol
Expected behavior
It should be possible to perform NFT framework operations in mainnet.
Problematic behavior
No operations are possible because it's not possible to register a protocol. Attempting to do so produces error: {"code":-26,"message":"64: version"}
Crown-core environment info
MX Linux 18.3
Crown-core application info
Crown version v0.14.0.0-Emerald (2020-03-09 07:53:34 +0000)
Relevant logs, dumps and/or screenshots
mark@x230:~/.crown$ crown-cli nftproto register marbles "Round Spherical Objects" CRWPsXLr4AUHK8RDvcGP6wFfndZc3P5hv4Sn 3
error: {"code":-26,"message":"64: version"}
The debug.log contains
ERROR: AcceptToMemoryPool : nonstandard transaction: version
which is due to chainparams.cpp:296
fRequireStandard = true;
and main.cpp:1088
// Rather not work on nonstandard transactions (unless -testnet/-regtest)
string reason;
if (Params().RequireStandard() && !IsStandardTx(tx, reason))
return state.DoS(0,
error("AcceptToMemoryPool : nonstandard transaction: %s", reason),
REJECT_NONSTANDARD, reason);
Drop full logs & dumps here: https://nextcloud.crownplatform.com/index.php/s/Q6H8enXNmJsQYCD
Possible fixes
(Any comments on what you think might be responsible for the problem, if you have particular insight.)
/cc @artem
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information