---
# System prepended metadata

title: Week 15 Updates - P2P Topics

---

## Week 15 Updates
Last week, we finished all changes required in the validator client to support self-building in gloas.  This week, I shifted focus over to analyzing and implementing the gloas p2p changes required for the self-building flow included in the devnet-0 release per the [spec](https://ethereum.github.io/consensus-specs/specs/gloas/p2p-interface/#gloas-networking)

### Global Topics
`beacon_aggregate_and_proof` was updated in [PR](https://github.com/shane-moore/lighthouse/pull/12) since the `aggregate.data.index` has some additional validations now.

`beacon_block` was also updated in [PR](https://github.com/shane-moore/lighthouse/pull/12) since checks related to the `BeaconBlockBody.ExecutionPayload` are removed and additional validations regarding the CL block's parent execution payload via envelope are added.  The envelope related checks are contingent upon `envelope_verification.rs`, which is upcoming.  Also note that we'll need to update `block_verification.rs` to rip out anything related to blobs/payloads. ideally, this file will only handle CL block validation going forward

`execution_payload` global topic was added in [PR](https://github.com/shane-moore/lighthouse/pull/11) since we'll need to be able to forward gossiped signed envelopes.  The topic was added, and the next step is to add the validations, which will also be handled in `envelope_verification.rs`.  In order to fully understand how the `execution_payload` validations were required, I did a bit of a deep dive into the lifecycle of an envelope and documented my findings along the way [here](https://hackmd.io/@blockshane/rJc4XHxnxl).

`payload_attestation_message` global topic was also added in [PR](https://github.com/shane-moore/lighthouse/pull/11) in order to forward gossiped `PayloadAttestationMessage`, and we will need to create a new `payload_attestation_verification.rs` for this.

`beacon_attestation_{subnet_id}` was updated in [PR](https://github.com/shane-moore/lighthouse/pull/12) since the `aggregate.data.index` has some additional validations now.

## Next Week
- add `ExecutionPayloadEnvelopesByRange v1` and `ExecutionPayloadEnvelopesByRoot v1` to handle requests from syncing peers asking for a range of `ExecutionPayloadEnvelopes` to verify incoming blocks as to catch up with the head

## Could Do (no blockers)
- `PayloadAttestationData` to include signature instead of aggregatedbls signature
- remove fields from `DataColumnSidecar` - superstruct and handle all downstream changes
- rename `ExecutionBid` to `ExecutionPayloadBid`
- build out a `payload_attestation_verification.rs` for handling gossiped payload attestations as well as ones received via rpc
- check through all my open PR’s in my repo against possible changes to the spec introduced by devnet-0 consensus spec updates https://github.com/ethereum/consensus-specs/releases/tag/v1.6.0-beta.0
- update https://github.com/sigp/lighthouse/issues/7850 with current status
- figure out which tests can be fixed or added atm, i.e. some tests are integration test, where we will need full VC and BN implementation, whereas some unit testing can be isolated