Commit Graph

23 Commits

Author SHA1 Message Date
Danny Ryan
d299b06a1c fix custody bit calculation format 2020-03-16 09:52:27 -06:00
Dankrad Feist
9b7e0ab2be Fix error in custody bit computation 2020-03-13 17:15:25 +00:00
Danny Ryan
e2918c6364 Merge pull request #1626 from ethereum/proposer-index
add proposer index to BeaconBlock
2020-03-10 15:10:07 -06:00
Danny Ryan
3b7704a78f Merge pull request #1649 from ethereum/eth1-voting-period-in-epochs
Eth1 voting period in epochs [updated for configs/phase1/tests compat.]
2020-03-10 13:24:03 -06:00
protolambda
2d7a292d36 eth1 vote period constant in epochs: update configs, phase1, tests 2020-03-10 18:36:53 +01:00
Danny Ryan
7e04989e29 add genesis_validators_root to beaconstate and utilize in sig domain separation as well as fork separation 2020-03-05 09:21:32 -07:00
Hsiao-Wei Wang
b4c7481b35 Fix the misc table 2020-03-03 01:28:58 +01:00
Danny Ryan
757f5a31dd add proposer index and add/modify tests 2020-02-18 11:38:17 -06:00
terence tsao
fe58c78da8 Fix table 2020-01-29 14:08:48 -08:00
vbuterin
52fb929978 Update specs/core/1_beacon-chain.md 2020-01-28 17:32:57 -07:00
vbuterin
2a91b43eaf Remove shard block chunking
Only store a 32 byte root for every shard block

Rationale: originally, I added shard block chunking (store 4 chunks for every shard block instead of one root) to facilitate construction of data availability roots. However, it turns out that there is an easier technique. Set the width of the data availability rectangle's rows to be 1/4 the max size of a shard block, so each block would fill multiple rows. Then, non-full blocks will generally create lots of zero rows. For example if the block bodies are `31415926535` and `897932` with a max size of 24 bytes, the rows might look like this:

```
31415926
53500000
00000000
89793200
00000000
00000000
```
Zero rows would extend rightward to complete zero rows, and when extending downward we can count the number of zero rows, and reduce the number of extra rows that we make, so we only make a new row for every nonzero row in the original data. This way we get only a close-to-optimal ~4-5x blowup in the data even if the data has zero rows in the middle.
2020-01-28 17:31:51 -07:00
protolambda
d9f62f9303 Remerkleable - merkle tree based ssz for better and faster spec 2020-01-25 00:43:43 +01:00
Danny Ryan
7a412534d9 remove test_shard_blocks (outdated) and reduce PERSISTENT_COMMITTEE_PERIOD in minimal config 2020-01-15 18:17:07 -07:00
Danny Ryan
c0b69e531f cycle through committee indexes instead of through active shards when forming crosslinks 2020-01-15 17:43:11 -07:00
Danny Ryan
3c07b2c954 Make phase 0 fork choice more modular to more easily adopt for slight modifications in phase 1 2020-01-15 16:40:50 -07:00
protolambda
5785b4fc5b custody bits temporary solution 2020-01-14 01:59:01 +01:00
protolambda
f04a686db7 doctoc 2020-01-14 01:42:19 +01:00
protolambda
f6f8bd5350 no custody bits fallback 2020-01-14 01:36:16 +01:00
protolambda
702b253361 update configs for phase1 2020-01-13 19:50:36 +01:00
protolambda
419b6a3250 config change, need more space for worst-case reveals 2020-01-13 19:00:24 +01:00
protolambda
507a9afbfb apply custody bit fix suggestion from Dankrad 2020-01-13 18:57:56 +01:00
protolambda
4732c7beb1 merge in dev (v0.10) and fix reorg/lint issues 2020-01-13 18:55:21 +01:00
Danny Ryan
676e216beb reorg specs by fork and move ssz out to own folder. make all of the build and link changes to support move 2020-01-10 11:55:13 -07:00