Standardise PowBlock between fork-choice and validator

status-im · Mar 24, 2021 · 63ae9f2 · 63ae9f2
1 parent ea5f606
commit 63ae9f2
Show file tree

Hide file tree

Showing 2 changed files with 1 addition and 8 deletions.
diff --git a/specs/merge/fork-choice.md b/specs/merge/fork-choice.md
@@ -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

diff --git a/specs/merge/validator.md b/specs/merge/validator.md
@@ -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.