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

Release v0.9.0 #1453

Merged
merged 317 commits into from
Oct 28, 2019
Merged

Release v0.9.0 #1453

merged 317 commits into from
Oct 28, 2019

Conversation

djrtwo
Copy link
Contributor

@djrtwo djrtwo commented Oct 28, 2019

Release primarily focused on the phase 0 simplifications to facilitate the new sharding proposal.

Detailed notes to be found in release

Note: Phase 1+ specs are highly in flux and are not currently in a functional state. Because of this, testing of Phase 1 in CI is currently disabled.

vbuterin and others added 30 commits August 11, 2019 23:18
Co-Authored-By: Carl Beekhuizen <carl@ethereum.org>
Add shard state transition function
* Stab at Legendre custody construction + some tests

* Fix some problems and fix function puller to remove phase0 only lines in phase1

* Pass the linter

* Add headings

* Fix domain for BLS stub

* Change Jacobi to Legendre

* n -> q to clarify notation

* Headings

* Another missing heading

* Custody subchunks via padding

* Fix max_reveal_lateness stuff

* Better names for reveal period functions

* Better parametrization of max_reveal_lateness computation and tests for custody reveal processing

* Fix linter

* Allow challenging for one period after the custody reveal, shorter periods for minimal tests

* Fix lint

* Fix linter error
Add link from DepositData reference to definition
Co-Authored-By: Danny Ryan <dannyjryan@gmail.com>
Co-Authored-By: Hsiao-Wei Wang <hwwang156@gmail.com>
Co-Authored-By: Hsiao-Wei Wang <hwwang156@gmail.com>
MAX_PERSISTENT_COMMITTEE_SIZE -> TARGET_PERSISTENT_COMMITTEE_SIZE
Minor corrections and clarifications to the network specification
djrtwo and others added 12 commits October 28, 2019 14:10
Implement solution for #1446, based on suggested use of eth1 hash
Co-Authored-By: Hsiao-Wei Wang <hwwang156@gmail.com>
sync protocol: clarify committee type
add explicit comments for int_to_bytes and bytes_to_int
Co-Authored-By: Danny Ryan <dannyjryan@gmail.com>
* Update README.md

* Update README.md

* Update p2p-interface.md

* Update simple-serialize.md

* Update README.md

* Update initialization.md

* Update README.md

* Update 0_beacon-chain-validator.md

* Update README.md

* Update README.md

* Update README.md

* Update README.md

* Update README.md

* Update README.md

* Update README.md

* Update README.md
state,
get_period_committee(state, Shard(shard), Epoch(get_current_epoch(state) + 1)),
)
for shard in range(SHARD_COUNT)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

SHARD_COUNT removed?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All of the phase 1 stuff is in a state of disarray. Thus the turning off of phase 1 tests in CI 😬

This is noted in the comment for the PR and again in the release notes so will leave as is for now

Copy link
Contributor

@terencechain terencechain left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me! Thanks for getting this out in a timely manner 😄

Copy link
Contributor

@protolambda protolambda left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎉

Copy link
Contributor

@hwwhww hwwhww left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:shipit: 🎉

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.