Hsiao-Wei Wang
Hsiao-Wei Wang
### What is wrong? The current calling route: ```python class Chain(BaseChain): def import_block(self, block: BaseBlock, perform_validation: bool=True ) -> Tuple[BaseBlock, Tuple[BaseBlock, ...], Tuple[BaseBlock, ...]]: .... base_header_for_import = self.create_header_from_parent(parent_header) imported_block =...
### What is wrong? For #89, discussion offline: If I call mypy --strict --follow-imports=silent --ignore-missing-imports py_ecc (without `--no-strict-optional`), then 50+ errors about "None" infinity point would show up If I...
### Issue Currently, the documents are not labeled to which spec version they are. That makes it difficult to sync with upstream eth2.0-specs repo, especially the phase 1 specs are...
https://github.com/ethereum/eth2.0-specs/pull/140
1. Update readme, redirect to eth2.0-specs, py-evm, or py-ssz. 2. Archive the source code except for the Vyper contract?
### Issue `slash_random_validators` function would force slash `state.validators[0]`. However, we expect it doesn't slash any validator when we call `randomize_state(spec, state, slash_fraction=0)`. ### Proposed fix Remove `index == 0` condition....
[Notes for myself] - `should_update_justified_checkpoint`: - `compute_slots_since_epoch_start(get_current_slot(store)) == SAFE_SLOTS_TO_UPDATE_JUSTIFIED` - `and get_ancestor(store, new_justified_checkpoint.root, justified_slot) == store.justified_checkpoint.root` - `and get_ancestor(store, new_justified_checkpoint.root, justified_slot) != store.justified_checkpoint.root`
Opening this PR to signal the plan of deprecating Pyspec Python3.8 support. Benefits: - There are some post-Python3.9 functionalities that we want to utilize in `random` in tests (#2961). -...
### Background https://github.com/ethereum/execution-apis uses bold font format for the indicating requirement keywords like "MUST", "SHOULD", and "MAY" in specs. I found it is more readable. 👍 ### Proposed suggestion We...