replace PayloadStatus payload_status bu uint64 payload_revealed

Author: mehdi-aouadi

specs/gloas/beacon-chain.md

@@ -25,7 +25,6 @@
     - [`SignedExecutionPayloadBid`](#signedexecutionpayloadbid)
     - [`ExecutionPayloadEnvelope`](#executionpayloadenvelope)
     - [`SignedExecutionPayloadEnvelope`](#signedexecutionpayloadenvelope)
-    - [`PayloadStatus`](#payloadstatus)
   - [Modified containers](#modified-containers)
     - [`AttestationData`](#attestationdata)
     - [`BeaconBlockBody`](#beaconblockbody)
@@ -254,30 +253,20 @@ class SignedExecutionPayloadEnvelope(Container):
     signature: BLSSignature
 ```
 
-#### `PayloadStatus`
-
-```python
-class PayloadStatus(enum.Enum):
-    EMPTY = 0
-    FULL = 1
-```
-
 ### Modified containers
 
 #### `AttestationData`
 
-*Note*: The `AttestationData` container is modified to contain a
-`PayloadStatus`. The `Attestation`, `SingleAttestation` and `IndexedAttestation` containers are modified indirectly.
-The field `index` is removed from the `AttestationData` and a new field `payload_status` is added.
+*Note*: The `AttestationData` container is modified.
+The field `index` is renamed to `payload_revealed`.
+The `Attestation`, `SingleAttestation` and `IndexedAttestation` containers are modified indirectly.
 
 ```python
 class AttestationData(Container):
     slot: Slot
-    # [Modified in Gloas:EIP7732]
-    # Removed index
+    # [New in Gloas:EIP7732] Formerly 'index'
+    payload_revealed: uint64
     beacon_block_root: Root
-    # [New in Gloas:EIP7732]
-    payload_status: PayloadStatus
     source: Checkpoint
     target: Checkpoint
 ```
@@ -617,12 +606,11 @@ def get_attestation_participation_flag_indices(
     )
     is_matching_payload = False
     if is_attestation_same_slot(state, data):
-        assert data.payload_status == PayloadStatus.EMPTY
+        assert data.payload_revealed == 0
         is_matching_payload = True
     else:
         is_matching_payload = (
-            data.payload_status.value
-            == state.execution_payload_availability[data.slot % SLOTS_PER_HISTORICAL_ROOT]
+            data.payload_revealed == state.execution_payload_availability[data.slot % SLOTS_PER_HISTORICAL_ROOT]
         )
 
     # [Modified in Gloas:EIP7732]
@@ -1119,7 +1107,7 @@ def process_attestation(state: BeaconState, attestation: Attestation) -> None:
     assert data.slot + MIN_ATTESTATION_INCLUSION_DELAY <= state.slot
 
     # [Modified in Gloas:EIP7732]
-    assert data.payload_status in (PayloadStatus.EMPTY, PayloadStatus.FULL)
+    assert data.payload_revealed < 2
     committee_indices = get_committee_indices(attestation.committee_bits)
     committee_offset = 0
     for committee_index in committee_indices:

specs/gloas/fork-choice.md

@@ -97,7 +97,7 @@ def update_latest_messages(
 ) -> None:
     slot = attestation.data.slot
     beacon_block_root = attestation.data.beacon_block_root
-    payload_present = attestation.data.payload_status == PayloadStaus.FULL
+    payload_present = attestation.data.payload_revealed == 1
     non_equivocating_attesting_indices = [
         i for i in attesting_indices if i not in store.equivocating_indices
     ]
@@ -658,9 +658,9 @@ def validate_on_attestation(store: Store, attestation: Attestation, is_from_bloc
     assert block_slot <= attestation.data.slot
 
     # [New in Gloas:EIP7732]
-    assert attestation.data.payload_status in in (PayloadStatus.EMPTY, PayloadStatus.FULL)
+    assert attestation.data.payload_revealed  in [0, 1]
     if block_slot == attestation.data.slot:
-        assert attestation.data.payload_status == EMPTY
+        assert attestation.data.payload_revealed == 0
 
     # LMD vote must be consistent with FFG vote target
     assert target.root == get_checkpoint_block(

specs/gloas/p2p-interface.md

@@ -136,8 +136,8 @@ Let `block` be the beacon block corresponding to
 
 The following validations are added:
 
-- _[REJECT]_ `aggregate.data.payload_status in (PayloadStatus.EMPTY, PayloadStatus.FULL)`.
-- _[REJECT]_ `aggregate.data.payload_status == EMPTY` if `block.slot == aggregate.data.slot`.
+- _[REJECT]_ `aggregate.data.payload_revealed < 2`.
+- _[REJECT]_ `aggregate.data.payload_revealed == 0` if `block.slot == aggregate.data.slot`.
 
 The following validations are removed:
 
@@ -330,8 +330,8 @@ Let `block` be the beacon block corresponding to
 
 The following validations are added:
 
-- _[REJECT]_ `attestation.data.payload_status in (PayloadStatus.EMPTY, PayloadStatus.FULL)`.
-- _[REJECT]_ `attestation.data.payload_status == EMPTY` if
+- _[REJECT]_ `attestation.data.payload_revealed < 2`.
+- _[REJECT]_ `attestation.data.payload_revealed == 0` if
   `block.slot == attestation.data.slot`.
 
 The following validations are removed:

specs/gloas/validator.md

@@ -91,18 +91,18 @@ All validator responsibilities remain unchanged other than the following:
 ### Attestation
 
 The attestation deadline is changed with `ATTESTATION_DUE_BPS_GLOAS`. Moreover,
-the `attestation.data.payload_status` field is used to signal the payload status of
+the `attestation.data.payload_revealed` field is used to signal the payload status of
 the block being attested to (`attestation.data.beacon_block_root`). With the
 alias `data = attestation.data`, the validator should set this field as follows:
 
 - If `block.slot == current_slot` (i.e., `data.slot`), then always set
-  `data.payload_status = EMPTY`.
-- Otherwise, set `data.payload_status` based on the payload status in the validator's
+  `data.payload_revealed = 0`.
+- Otherwise, set `data.payload_revealed` based on the payload status in the validator's
   fork-choice:
-  - Set `data.payload_status = EMPTY` to signal that the payload is not present in the
-    canonical chain (payload status is `EMPTY` in the fork-choice).
-  - Set `data.payload_status = FULL` to signal that the payload is present in the canonical
-    chain (payload status is `FULL` in the fork-choice).
+  - Set `data.payload_revealed = 0` to signal that the payload is not present in the
+    canonical chain (payload status is `0` in the fork-choice).
+  - Set `data.payload_revealed = 1` to signal that the payload is present in the canonical
+    chain (payload status is `1` in the fork-choice).
 
 ### Sync Committee participations