Standardise PowBlock between fork-choice and validator

This commit is contained in:
Mikhail Kalinin 2021-03-24 20:58:31 +06:00
parent ea5f606bd0
commit 63ae9f2bdb
2 changed files with 1 additions and 8 deletions

View File

@ -30,6 +30,7 @@ This is the modification of the fork choice according to the executable beacon c
```python
class PowBlock(Container):
block_hash: Bytes32
is_processed: boolean
is_valid: boolean
total_difficulty: uint256

View File

@ -16,7 +16,6 @@
- [Block proposal](#block-proposal)
- [Constructing the `BeaconBlockBody`](#constructing-the-beaconblockbody)
- [Application Payload](#application-payload)
- [`PowBlock`](#powblock)
- [`get_pow_chain_head`](#get_pow_chain_head)
- [`produce_application_payload`](#produce_application_payload)
@ -43,13 +42,6 @@ All validator responsibilities remain unchanged other than those noted below. Na
##### Application Payload
###### `PowBlock`
```python
class PowBlock(Container):
block_hash: Bytes32
total_difficulty: uint256
```
###### `get_pow_chain_head`
Let `get_pow_chain_head() -> PowBlock` be the function that returns the head of the PoW chain. The body of the function is implementation specific.