# Teku opinion on Pectra split and scope

As it is, Pectra's scope is too big, and we need to do something about it. Either we need to split it in two or push the release forward. In the spirit of delivering value earlier, and minimizing risk, splitting into two forks is the correct approach. Also, if we are going to split the fork into two parts because the scope is already too big, there is no point in trying to add many more things into either of the parts.

**Pectra 1:**
- EIP-6110: Validator deposits on chain
- EIP-7002: Execution layer triggered exits
- EIP-7251: Increase MAX_EFFECTIVE_BALANCE
- EIP-7549: Move committee index outside attestation
- Cleanup changes:
- Switch to compounding when consolidating with source==target (consensus-specs#3918)
- Queue deposit requests and apply them during epoch processing (consensus-specs#3818)
- Engine API: unified list of opaque requests (execution-api#577)
- Engine API: Remove engine_getPayloadBodiesBy{Hash/Range}V2 (execution-apis#586)
- Engine API: extract execution requests from payload (execution-apis#587)

**Pectra 2:**
- EIP-7594: PeerDAS
- EIP-7742: Uncouple blob count between CL and EL
- EIP-7762: Increase MIN_BASE_FEE_PER_BLOB_GAS
- Further attestation changes
- Separate type for onchain attestation aggregates
- Separate type for unaggregated network attestations

**Whenever (either Pectra 1 or Pectra 2):**
- EIP-7495: SSZ Stable Containers
- EIP-7688: Forward compatible consensus data structures