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

multi: Use best state snapshot next stake diff. #2493

Merged

Conversation

davecgh
Copy link
Member

@davecgh davecgh commented Dec 9, 2020

The current best state snapshot was updated a long time ago to include the next required stake difficulty. This updates the RPC server, block manager, and broadcast pruning logic in server to make use of that versus making an explicit call.

It also removes the no longer used method from the rpcserver.Chain interface, the block manager infrastructure, and related test code accordingly.

@davecgh davecgh force-pushed the multi_use_best_state_snapshot_next_stake_diff branch from da48c4b to 53f521c Compare December 14, 2020 01:21
The current best state snapshot was updated a long time ago to include
the next required stake difficulty.  This updates the RPC server to make
use of that versus making an explicit call.

It also removes the no longer used method from the rpcserver.Chain
interface and related test code accordingly.
This removes unused code related to calculating the next required stake
difficulty through the block manager.
This updates the broadcast pruning logic in server to make use of the
next required stake difficulty from the best state snapshot versus
making an explicit call.
@davecgh davecgh force-pushed the multi_use_best_state_snapshot_next_stake_diff branch from 53f521c to ad0a2fe Compare December 14, 2020 01:25
@davecgh davecgh merged commit ad0a2fe into decred:master Dec 14, 2020
@davecgh davecgh deleted the multi_use_best_state_snapshot_next_stake_diff branch December 14, 2020 01:28
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

3 participants