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

[APPROVED] put phase outs of C32 and beyond on hold #2714

Merged
merged 3 commits into from
Jun 26, 2019

Conversation

tromp
Copy link
Contributor

@tromp tromp commented Mar 27, 2019

Limit Cuckatoo phaseouts to C31. This is a hard forking change that only takes effect when C32 would originally phase out in early 2021.

@yeastplume
Copy link
Member

@tromp Should we get this in for 2.0.0?

@tromp
Copy link
Contributor Author

tromp commented Jun 6, 2019

At least a decision on this should be taken before freezing 2.0.0 as it requires an 18 month advance notice on Cuckatoo changes and includes such a change taking effect in Jan 2021.

I would very much like to see it approved. Can we decide in the next Gov meeting?

prepare to apply phaseout on hold to 2.0.0
@quentinlesceller quentinlesceller changed the base branch from master to milestone/2.0.0 June 25, 2019 16:28
@yeastplume yeastplume added this to the 2.0.0 milestone Jun 26, 2019
@yeastplume yeastplume merged commit 07f259a into mimblewimble:milestone/2.0.0 Jun 26, 2019
@tromp tromp changed the title [PENDING APPROVAL] put phase outs of C32 and beyond on hold [APPROVED] put phase outs of C32 and beyond on hold Jun 26, 2019
yeastplume added a commit that referenced this pull request Jun 27, 2019
* create 2.0.0 branch

* fix humansize version

* update grin.yml version

* PoW HardFork (#2866)

* allow version 2 blocks for next 6 months

* add cuckarood.rs with working tests

* switch cuckaroo to cuckarood at right heights

* reorder to reduce conditions

* remove _ prefix on used args; fix typo

* Make Valid Header Version dependant on ChainType

* Rustfmt

* Add tests, uncomment header v2

* Rustfmt

* Add FLOONET_FIRST_HARD_FORK height and simplify logic

* assume floonet stays closer to avg 60s block time

* move floonet hf forward by half a day

* update version in new block when previous no longer valid

* my next commit:-)

* micro optimization

* Support new Bulletproof rewind scheme (#2848)

* Update keychain with new rewind scheme

* Refactor: proof builder trait

* Update tests, cleanup

* rustfmt

* Move conversion of SwitchCommitmentType

* Add proof build trait to tx builders

* Cache hashes in proof builders

* Proof builder tests

* Add ViewKey struct

* Fix some warnings

* Zeroize proof builder secrets on drop

* Modify mine_block to use wallet V2 API (#2892)

* update mine_block to use V2 wallet API

* rustfmt

* Add version endpoint to node API, rename pool/push (#2897)

* add node version API, tweak pool/push parameter

* rustfmt

* Upate version api call (#2899)

* Update version number for next (potential) release

* zeroize: Upgrade to v0.9 (#2914)

* zeroize: Upgrade to v0.9

* missed Cargo.lock

* [PENDING APPROVAL] put phase outs of C32 and beyond on hold (#2714)

* put phase outs of C32 and beyond on hold

* update tests for phaseouts on hold

* Don't wait for p2p-server thread (#2917)

Currently p2p.stop() stops and wait for all peers to exit, that's
basically all we need. However we also run a TCP listener in this thread
which is blocked on `accept` most of the time. We do an attempt to stop
it but it would work only if we get an incoming connection during the
shutdown, which is a week guarantee.

This fix remove joining to p2p-server thread, it stops all peers and
makes an attempt to stop the listener.

Fixes [#2906]

* rustfmt
quentinlesceller added a commit to quentinlesceller/grin that referenced this pull request Jul 24, 2019
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.

2 participants