Here's a transaction to broadcast:


The error message is:

Error: rlp: non-canonical integer (leading zero bytes) for uint64, decoding into (types.Transaction)(types.txdata).AccountNonce

Decoding the transaction the result is:


What is wrong with the transaction? Why does it have an error when it is broadcasted?

2 Answers 2


The gas price, limit, and value are all unparsed from _bn (big number) when they should be a number. Not sure if that's happening when you decide the signed transaction or encode the unsigned transaction, but it's a good place to start to solve your issue.

Ps: please please please tell me you are on the testnets for these. Sending with a too high gas price could result in a very very expensive lesson.



signed r and s need to clear leading zero bytes

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.