QA: nftproto registration tokenProtocolName validation failure
Summary
QA: nftproto register does not validate the new tokenProtocolName according to the rules given in the help
Steps to reproduce
mark@x230:~/.crowntest/testnet3$ tcrowncli nftproto register test2 t2 tCRWPpEZVu93MVGYS9FqEjV9XAW9sgKz3MMTp
d2abac509c6f0dbdfeef5d1de542a5fc6cdec57826a37f131cad78891d4ce9fb
Expected behavior
Should be rejected because the name is too short
Problematic behavior
Protocol is created
mark@x230:~/.crowntest/testnet3$ tcrowncli nftproto get test2
{
"blockHash" : "df8c062121f5c3ffce990b9243614a0ee2ac5b5fa3ff65055fab1ca7a7571652",
"registrationTxHash" : "d2abac509c6f0dbdfeef5d1de542a5fc6cdec57826a37f131cad78891d4ce9fb",
"height" : 351844,
"timestamp" : 1581606210,
"nftProtocolId" : "test2",
"tokenProtocolName" : "t2",
"tokenMetadataSchemaUri" : "",
"tokenMetadataMimeType" : "text/plain",
"isTokenTransferable" : true,
"isMetadataEmbedded" : false,
"nftRegSign" : "SignByCreator",
"maxMetadataSize" : 255,
"tokenProtocolOwnerId" : "tCRWPpEZVu93MVGYS9FqEjV9XAW9sgKz3MMTp"
}
Crown-core environment info
Ubuntu 16.04
Crown-core application info
v0.13.9.3 build 1166
Relevant logs, dumps and/or screenshots
(Paste any relevant logs - please use code blocks (```) to format console output, logs, and code; it's very hard to read otherwise.)
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