-
Notifications
You must be signed in to change notification settings - Fork 225
Open
Labels
Description
In holodeck, running the following command fails:
secretcli tx compute instantiate 30303 '{"reward_token":{"address":"secret12q2c5s5we5zn9pq43l0rlsygtql6646my0sqfm", "contract_hash":"c7fe67b243dfedc625a28ada303434d6f5a46a3086e7d2b5063a814e9f9a379d"},"inc_token":{"address":"secret1pt60eq9hh3c4rk3gj9nus9ahjn948ccx7p2ghs", "contract_hash":"f86b5c3ca0381ce7edfffa534789501ae17cf6b21515213693baf980765729c2"},"reward_sources":[{"address":"secret13hqxweum28nj0c53nnvrpd23ygguhteqggf852", "contract_hash":"c8555c2de49967ca484ba21cf563c2b27227a39ad6f32ff3de9758f20159d2d2"}],"viewing_key":"123","token_info":{"name":"bulk-rewards","symbol":"BULKRWRDS"},"prng_seed":"YWE="}' --from test --label sdss --gas 2000000
It fails because code 30303
tries to send snip20 callbacks on init
to inc_token
- but the value for inc_token
in the command above is not a snip20. The expected outcome would be some kind of error indicating that an unexpected message was sent to this contract (secret1pt60eq9hh3c4rk3gj9nus9ahjn948ccx7p2ghs
).
However, the result from secretcli q compute tx <hash>
on this command results in:
ERROR: Got an error decoding base64 of the error: illegal base64 data at input byte 7
which probably indicates a bug in parsing the error message at some point, maybe in the secretcli
binary itself.
Should investigate further to generalize and understand the root cause of this problem.