moskvanaft
commented
6 years ago @eosstore you need to have quotes around arguments containing {. Also requested_permissions should be array of objects (not object).
Please check usage example in https://github.com/EOSIO/eos/blob/master/contracts/eosio.msig/README.md
root@ip-172-30-101-34:~/EOS-Jungle-Testnet# ./cleos.sh multisig propose pro111 [{"actor": "eosio.prods", "permission": "active"}] [{"actor": "eosio", "permission": "active"}] transfer {"from": "eosio", "to": "eosstore4321", "quantity": "'123.0000 EOS'", "memo": "test"} eosstore4321 34 -p eosstore4321 ERROR: ConversionError: proposal_expiration=permission: Transfer EOS from account to account Usage: /root/eos/build/programs/cleos/cleos transfer [OPTIONS] sender recipient amount [memo]
Positionals: sender TEXT The account sending EOS (required) recipient TEXT The account receiving EOS (required) amount TEXT The amount of EOS to send (required) memo TEXT The memo for the transfer
Options: -c,--contract TEXT The contract which controls the token -x,--expiration set the time in seconds before a transaction expires, defaults to 30s -f,--force-unique force the transaction to be unique. this will consume extra bandwidth and remove any protections against accidently issuing the same transaction multiple times -s,--skip-sign Specify if unlocked wallet keys should be used to sign transaction -j,--json print result as json -d,--dont-broadcast don't broadcast transaction to the network (just print to stdout) -r,--ref-block TEXT set the reference block num or block id used for TAPOS (Transaction as Proof-of-Stake) -p,--permission TEXT ... An account and permission level to authorize, as in 'account@permission' (defaults to 'sender@active') --max-cpu-usage-ms UINT set an upper limit on the milliseconds of cpu usage budget, for the execution of the transaction (defaults to 0 which means no limit) --max-net-usage UINT set an upper limit on the net usage budget, in bytes, for the transaction (defaults to 0 which means no limit)