-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CLI gov deposit JSON errors with ledger #9055
Comments
also fails with |
cc @jleni |
Where in the JSON are there whitespaces? Could you |
same question. Could you post the payload you are sending? |
{"body":{"messages":[{"@type":"/cosmos.gov.v1beta1.MsgDeposit","proposal_id":"44","depositor":"cosmos1849m9wncrqp6v4tkss6a3j8uzvuv0cp7wcgvqa","amount":[{"denom":"uatom","amount":"255000000"}]}],"memo":"","timeout_height":"0","extension_options":[],"non_critical_extension_options":[]},"auth_info":{"signer_infos":[],"fee":{"amount":[{"denom":"uatom","amount":"54"}],"gas_limit":"106309","payer":"","granter":""}},"signatures":[]} |
Ah, my bad, I added manually a fmt.Println of the amino SignDoc while testing on a local chain (explicity with spaces in the memo), and it printed: {"account_number":"8","sequence":"2","chain_id":"my-chain","memo":"A B C","fee":{"amount":[],"gas":"200000"},"msgs":[{"type":"cosmos-sdk/MsgDeposit","value":{"amount":[{"amount":"10","denom":"stake"}],"depositor":"cosmos1xl2256vdh0j68khz9wq88hnyqcq0f5f4za2480","proposal_id":"1"}}]} which seems correct. I also managed to deposit, so I couldn't reproduce the initial error. BTW, afaiu the @fedekunze Could you provide more details about the reproduction steps? |
ok this is super weird but this only fails if the amount is ≥ 100 atoms (100000000uatom) |
prob a parsing issue? |
Added test for parser and integration! This is working fine! |
Summary of Bug
Deposit JSON can't be signed by ledger due to whitespace
Version
Gaia v4.2.0
Ledger Cosmos v2.18.0
Steps to Reproduce
gaiad tx gov deposit <proposal> <amount> <flags> --ledger
For Admin Use
The text was updated successfully, but these errors were encountered: