types: allow nonce to be zero #20
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
As you can see, nonce is optional parameter https://github.com/ethereum/wiki/wiki/JSON-RPC#eth_sendtransaction |
|
@onrik I am using geth, and if "nonce" is not specified in the request, geth treats it as invalid. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As far as I understand nonce might be zero, but current version of library doesn't allow it, and just do not place "nonce" in json request, which later interpreted by daemon that nonce specified at all, and request is not valid.
Not sure for 100% but that seems like this bug caused our transaction stuck on queue pool of ethereum daemon.