Skip to content
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

Use pending transaction nonce as a default #58

Merged
merged 2 commits into from
Feb 27, 2018

Conversation

kulerskim
Copy link
Contributor

Fixes issues with colliding transactions, additionally allow passing alternate transaction nonce value if needed. Please comment if you see a better solution for sending more than one similar transaction per single mined block.

Relates to: #35

Reason: Submitting more than one transaction from the same account
before the block is mined resulted with colliding transactions, because
of the same nonce. This change takes the nonce from the pending
transactions, so it's incrementes as the pool growths before block is
mined.

Relates to: EthWorks#35
Reason: It allows a developer to calculate transaction nonce on his own.
May be needed when you want to control transactions order or calculate
nonce using transaction pool rather than relying on current client
algorithm.

Relates to:
- EthWorks#35
- ethereum/go-ethereum#2880
@kulerskim kulerskim changed the title Use pending nonce as a default Use pending transaction nonce as a default Feb 22, 2018
@marekkirejczyk marekkirejczyk merged commit 433a6e8 into EthWorks:master Feb 27, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants