You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 26, 2024. It is now read-only.
It should be possible to increment the nonce of an unlocked account via an RPC call.
Current Behavior
A user may wish to deploy to contract at a specific address, where that deployment address requires a very high nonce. Currently this can only be achieved by broadcasting many empty transactions in a for loop as a way to increment the nonce. This is time consuming and inefficient.
Possible Solution
Add an RPC endpoint evm_nonce that accepts two parameters: the hex address of the account to increment, and an integer value to be added to the nonce. The return value is the new nonce.
The text was updated successfully, but these errors were encountered:
Expected Behavior
It should be possible to increment the nonce of an unlocked account via an RPC call.
Current Behavior
A user may wish to deploy to contract at a specific address, where that deployment address requires a very high nonce. Currently this can only be achieved by broadcasting many empty transactions in a for loop as a way to increment the nonce. This is time consuming and inefficient.
Possible Solution
Add an RPC endpoint
evm_nonce
that accepts two parameters: the hex address of the account to increment, and an integer value to be added to the nonce. The return value is the new nonce.The text was updated successfully, but these errors were encountered: