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

[feature] Resend txn #366

Open
roynalnaruto opened this issue Aug 1, 2019 · 6 comments
Open

[feature] Resend txn #366

roynalnaruto opened this issue Aug 1, 2019 · 6 comments
Labels
bounty Issues that are associated with a bounty

Comments

@roynalnaruto
Copy link

Feature

What is the feature?

This is a part of a bigger feature ticket

Re-sending txns with higher gas price

This scenario occurs when the blockchain network is congested. In this scenario, a user who sent a transaction with a gas price of say, 5 gwei, would have to wait for long time before their transaction is mined (if the average gas price during that time is say, 20 gwei). In such cases, some users may prefer and afford re-sending the same transaction with a higher gas price of say, 30 gwei, to force their transaction through.

In order to resend a transaction with updated gas price, this new transaction must have the same nonce as the older one. By modifying just the gas price of the transaction object, the new transaction can be signed again and sent to the Ethereum node. Both those transactions would now have the same nonce, but the latest one with a higher gas price. Whenever one of them is mined, the other is automatically dropped.

How can it be done?

Design

Resend-txn
Resend-modal

Other Comments

@roynalnaruto roynalnaruto added the bounty Issues that are associated with a bounty label Aug 1, 2019
@gitcoinbot
Copy link

Issue Status: 1. Open 2. Started 3. Submitted 4. Done


This issue now has a funding of 0.763 ETH (150.0 USD @ $196.59/ETH) attached to it.

@gitcoinbot
Copy link

gitcoinbot commented Aug 22, 2019

Issue Status: 1. Open 2. Started 3. Submitted 4. Done


Work has been started.

These users each claimed they can complete the work by 267 years, 2 months from now.
Please review their action plans below:

1) lacexd has applied to start work (Funders only: approve worker | reject worker).

i'd like to implement the fature, i the git repo and everything seems clear so far.
2) arbreton has applied to start work (Funders only: approve worker | reject worker).

Straight forward instructions, shouldn't be a problem to implement
3) bshevchenko has been approved to start work.

I'm approved by you to work on https://gitcoin.co/issue/DigixGlobal/dao-server/70/3349 so I think it makes sense to fix this issue for me as well

Learn more on the Gitcoin Issue Details page.

@gitcoinbot
Copy link

@bshevchenko Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

  • reminder (3 days)
  • escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

@bshevchenko
Copy link

@gitcoinbot yeap, will close backend part for this issue at first. Soft deadline for both of these issues is 2 weeks as discussed with the team in Discord

@gitcoinbot
Copy link

⚡️ A tip worth 0.76000 ETH (136.48 USD @ $179.58/ETH) has been granted to @bshevchenko for this issue from @tymat. ⚡️

Nice work @bshevchenko! To redeem your tip, login to Gitcoin at https://gitcoin.co/explorer and select 'Claim Tip' from dropdown menu in the top right, or check your email for a link to the tip redemption page.

@gitcoinbot
Copy link

Issue Status: 1. Open 2. Started 3. Submitted 4. Done


This Bounty has been completed.

Additional Tips for this Bounty:

  • tymat tipped 0.7600 ETH worth 137.46 USD to bshevchenko.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bounty Issues that are associated with a bounty
Projects
None yet
Development

No branches or pull requests

3 participants