Describe the bug
Assuming you have a contract, the admin is a 2/3 multisig address. You have 1 of 3 private keys. Some NEP-17 tokens are deposited in that contract but now you guys want to withdraw. You need create tx by RPC invokefunction and add 2 witness scope on that(your address and the contract address). Finally CLI can't get completed signatures and it should print incompleted context and then you can send it to another admin to get another 1/3. But apparently, the contract witness has nothing, the script is null and can't be converted by Convert.ToBase64String(Script)
To Reproduce
Steps to reproduce the behavior:
- Deploy a contract, add owner address and verify() method to ensure it could pass checkwitness()
- Set a 2/3 multisigaddress as owner and send some NEP-17 tokens into it
- Invoke RPC
openwallet and then invokefunction to withdraw
Expected behavior
No exception is threw. Should see context ouput to ask for signature.
Screenshots

Platform:
Any
Describe the bug
Assuming you have a contract, the admin is a 2/3 multisig address. You have 1 of 3 private keys. Some NEP-17 tokens are deposited in that contract but now you guys want to withdraw. You need create tx by RPC
invokefunctionand add 2 witness scope on that(your address and the contract address). Finally CLI can't get completed signatures and it should print incompleted context and then you can send it to another admin to get another 1/3. But apparently, the contract witness has nothing, the script is null and can't be converted byConvert.ToBase64String(Script)To Reproduce
Steps to reproduce the behavior:
openwalletand theninvokefunctionto withdrawExpected behavior
No exception is threw. Should see context ouput to ask for signature.
Screenshots

Platform:
Any