epbs related copy changes

Author: shane-moore

apis/beacon/blocks/blocks.v2.yaml

@@ -11,7 +11,7 @@ post:
     The beacon node is also expected to integrate the block into the state, but may broadcast it
     before doing so, so as to aid timely delivery of the block. Should the block fail full
     validation, a separate success response code (202) is used to indicate that the block was
-    successfully broadcast but failed integration. After Deneb and before Gloas, this additionally instructs
+    successfully broadcast but failed integration. For Deneb/Electra/Fulu, this additionally instructs
     the beacon node to broadcast all given blobs. The broadcast behaviour may be adjusted via the
     `broadcast_validation` query parameter.
   parameters:

apis/beacon/execution_payload/bid.yaml

@@ -2,8 +2,8 @@ post:
   operationId: publishExecutionPayloadBid
   summary: Publish signed execution payload bid
   description: |
-    Instructs the beacon node to broadcast a signed execution payload bid to the beacon network,
-    to be gossiped for potential inclusion in block building. A success response indicates
+    Instructs the beacon node to broadcast a signed execution payload bid to the network,
+    to be gossiped for potential inclusion in block building. A success response (20x) indicates
     that the bid passed gossip validation and was successfully broadcast onto the network.
   tags:
     - Beacon

apis/beacon/execution_payload/envelope.yaml

@@ -2,11 +2,12 @@ post:
   operationId: publishExecutionPayloadEnvelope
   summary: Publish signed execution payload envelope
   description: |
-    Instructs the beacon node to broadcast a signed execution payload envelope to the beacon network,
+    Instructs the beacon node to broadcast a signed execution payload envelope to the network,
     to be gossiped for payload validation. A success response (20x) indicates
     that the envelope passed gossip validation and was successfully broadcast onto the network.
   tags:
     - Beacon
+    - ValidatorRequiredApi
   requestBody:
     description: "The `SignedExecutionPayloadEnvelope` object to be broadcast."
     required: true

apis/validator/block.v4.yaml

@@ -1,7 +1,7 @@
 get:
   tags:
-    - ValidatorRequiredApi
     - Validator
+    - ValidatorRequiredApi
   operationId: "produceBlockV4"
   summary: "Produce a new block, without signature."
   description: |

apis/validator/execution_payload_envelope.yaml

@@ -7,6 +7,7 @@ get:
     either as json or as bytes serialized by SSZ.
   tags:
     - Validator
+    - ValidatorRequiredApi
   parameters:
     - name: slot
       in: path

validator-flow.md

@@ -15,7 +15,9 @@ On start of every epoch, validator should [fetch proposer duties](#/Validator/ge
 Result is array of objects, each containing proposer pubkey and slot at which he is suppose to propose.
 
 If proposing block, then at immediate start of slot:
-1. [Ask Beacon Node for BeaconBlock object](#/Validator/produceBlock)
+1. Ask Beacon Node for BeaconBlock object:
+   - Pre-Gloas forks: [produceBlockV3](#/Validator/produceBlockV3)
+   - Post-Gloas fork: [produceBlockV4](#/Validator/produceBlockV4)
 2. Sign block
 3. [Submit SignedBeaconBlock](#/ValidatorRequiredApi/publishBlock) (BeaconBlock + signature)
 
@@ -36,13 +38,15 @@ Attesting:
       been assigned to. If any validators in the committee are aggregators,
       set `is_aggregator` to `True`,
 2. Wait for new BeaconBlock for the assigned slot (either stream updates or poll)
-    - Max wait: `SECONDS_PER_SLOT / 4` seconds into the assigned slot
+    - Pre-Gloas forks: Max wait `SECONDS_PER_SLOT / 3` seconds into the assigned slot
+    - Post-Gloas forks: Max wait `SECONDS_PER_SLOT / 4` seconds into the assigned slot
 3. [Fetch AttestationData](#/ValidatorRequiredApi/produceAttestationData)
 4. [Submit Attestation](#/ValidatorRequiredApi/submitPoolAttestations) (AttestationData + aggregation bits)
     - Aggregation bits are `Bitlist` with length of committee (received in AttesterDuty)
     with bit on position `validator_committee_index` (see AttesterDuty) set to true
 5. If aggregator:
-    - Wait for `SECONDS_PER_SLOT / 2` seconds into the assigned slot
+    - Pre-Gloas forks: Wait for `SECONDS_PER_SLOT * 2 / 3` seconds into the assigned slot
+    - Post-Gloas forks: Wait for `SECONDS_PER_SLOT / 2` seconds into the assigned slot
     - [Fetch aggregated Attestation](#/ValidatorRequiredApi/getAggregatedAttestation) from Beacon Node you've subscribed to your subnet
     - [Publish SignedAggregateAndProofs](#/ValidatorRequiredApi/publishAggregateAndProofs)
 
@@ -51,7 +55,7 @@ If reorg is detected, ask for new attester duties and proceed from 1..
 
 ### PTC Attesting
 
-On start of every epoch, validator should [fetch PTC duties](#/Validator/getPtcDuties) for epoch + 1.
+On start of every epoch beginning with the Gloas fork, validator should [fetch PTC duties](#/Validator/getPtcDuties) for epoch + 1.
 Result are array of objects with validator index and assigned slot for payload timeliness committee participation.
 
 PTC Attesting:
@@ -68,7 +72,7 @@ If reorg is detected, ask for new PTC duties and proceed from 1..
 
 ### Builder (Optional)
 
-Validators may optionally act as builders to submit execution payload bids for block inclusion.
+Post-Gloas fork, validators may optionally act as builders to submit execution payload bids for block inclusion.
 This requires registering with builder-specific withdrawal credentials (`BUILDER_WITHDRAWAL_PREFIX`).
 
 Building: