CHIA-3737 Simplify BundleCoinSpend's tracking of fast forward spends #20069
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.
Purpose:
Instead of tracking
eligible_for_fast_forward
introduce asupports_fast_forward
property that is true when a spend has fast forward unspent lineage information.This simplifies determining when a spend supports fast forward without data duplication, and it renders the state where
eligible_for_fast_forward
is true without lineage information, impossible.Current Behavior:
We track fast forward spends information through both
eligible_for_fast_forward
andlatest_singleton_lineage
.New Behavior:
We determine
supports_fast_forward
based onlatest_singleton_lineage
.Testing Notes: