release v0.12.0 #1829
Merged
release v0.12.0 #1829
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The amount of inactivity penalty was adjusted to half since we were applying penalty for missing FFG target and source. But now we only apply it for missing target, so `INACTIVITY_PENALTY_QUOTIENT` should be `2**24`.
…on of the given list, not `ValidatorIndex`
Strict `ValidatorIndex` definition
…ient_bug Fix `INACTIVITY_PENALTY_QUOTIENT`
Fix some phase 0 typing
Cosmetic changes from #1737
Co-Authored-By: Hsiao-Wei Wang <hwwang156@gmail.com>
sync v0.11.2 to `v012x`
1. Avoid negative computation in `is_candidate_block` 2. Fix `get_block_signature`: avoid extra casting; it's simpler to use BeaconBlock instead of BeaconHeader
1. "Becoming a validator" 2. "Validator assignments" 3. "Beacon chain responsibilities: Block proposal"
1. "Beacon chain responsibilities: Attesting" 2. "Beacon chain responsibilities: Attestation aggregation"
Fix get_eth1_vote test cases
…eth1 votes consensus
Add sanity, unit test for validator guide
Require "seen" aggregates to be valid
genesis: clarify that eth1 timestamp can be less than min genesis time
Bump `remerkleable` to 0.1.15
remerkleable 0.1.16
…g considered for genesis
Ensure balances remain unchanged for optimal validators during leak
Also verify it in BLS test generator
…t should be never_bls
Co-authored-by: Diederik Loerakker <proto@protolambda.com>
Per the spec, if I request range 5-10, it is permissible for a client to answer with block 7, 9 - even if the blocks 5, 6 and 8 exist. Because blocks 7 and 9 cannot be validated as they arrive in such a request, it seems better to close this gap - this update adds the spec language that forbids well-behaving clients from answering this way.
…hain, even with higher step
clarify that eth1 block follow distance for genesis
Strict block range (Rebase and extend #1827)
ensure can't undo progress with eth1data voting
BLS options for pyspec
protolambda
approved these changes
May 20, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Detailed notes will be accompanied with release