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: Latest consensus active from simnet genesis. #1482

Conversation

davecgh
Copy link
Member

@davecgh davecgh commented Oct 5, 2018

This requires PRs #1480 and #1481.

This modifies simnet to include the latest consensus changes that have been successfully voted into mainnet to date starting from its genesis block. This means it is no longer necessary to vote those changes in to simnet first before making use of them.

The changes entail removing the deployment entries for those votes, updating the mining templates to start from version 5, which matches the current mainnet version, and modifying the various sections in blockchain which make decisions accordingly.

The chaincfg and blockchain modules are affected, but since their version has already been bumped since their last release tags, they are not bumped again.

@davecgh davecgh added this to the 1.4.0 milestone Oct 5, 2018
@davecgh davecgh force-pushed the multi_simnet_latest_consensus_changes_active_from_genesis branch 2 times, most recently from fb25fef to 8e6cd7c Compare October 5, 2018 08:30
@jrick
Copy link
Member

jrick commented Oct 5, 2018

I'm confused, why aren't the modules being given new versions? Those versions are already published, and we can't change them now (and more practically, it breaks Go's build cache).

@davecgh
Copy link
Member Author

davecgh commented Oct 5, 2018

@jrick The versions are not yet published.

@davecgh davecgh force-pushed the multi_simnet_latest_consensus_changes_active_from_genesis branch from 8e6cd7c to af5131a Compare October 10, 2018 00:54
This modifies simnet to include the latest consensus changes that have
been successfully voted into mainnet to date starting from its genesis
block.  This means it is no longer necessary to vote those changes in to
simnet first before making use of them.

The changes entail removing the deployment entries for those votes,
updating the mining templates to start from version 5, which matches the
current mainnet version, and modifying the various sections in
blockchain which make decisions accordingly.

The chaincfg and blockchain modules are affected, but since their
version has already been bumped since their last release tags, they are
not bumped again.
@davecgh davecgh force-pushed the multi_simnet_latest_consensus_changes_active_from_genesis branch from af5131a to 15f7f61 Compare October 10, 2018 20:59
@davecgh davecgh merged commit 15f7f61 into decred:master Oct 10, 2018
@davecgh davecgh deleted the multi_simnet_latest_consensus_changes_active_from_genesis branch October 10, 2018 21:04
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.

4 participants