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

stop wallet rebroadcasting expired transactions #2399

Merged
merged 1 commit into from
Oct 25, 2022

Conversation

hughy
Copy link
Contributor

@hughy hughy commented Oct 22, 2022

Summary

we rebroadcast any transactions in the wallet that have not been added to a block. however, now that we continue to store expired transactions in the wallet we must ensure that we do not rebroadcast them.

rebroadcasting expired transactions also updates them in the wallet db with the current head as submittedSequence. when this update is made they are added to the wallet db store for pending transaction hashes. they then 're-expire' and their notes are reverted to unspent (even if they have later been spent in another transaction).

Testing Plan

added unit test

Breaking Change

Is this a breaking change? If yes, add notes below on why this is breaking and
what additional work is required, if any.

[ ] Yes

we rebroadcast any transactions in the wallet that have not been added to a
block. however, now that we continue to store expired transactions in the wallet
we must ensure that we do not rebroadcast them.

rebroadcasting expired transactions also updates them in the wallet db with the
current head as submittedSequence. when this update is made they are added to
the wallet db store for pending transaction hashes. they then 're-expire' and
their notes are reverted to unspent (even if they have later been spent in
another transaction).
@hughy hughy requested a review from a team as a code owner October 22, 2022 01:14
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.

None yet

2 participants