account abstraction, MaxEB increase, blob target increase, calldata cost increase, execution layer validator exits, more secure validator deposits, BLS12-381 precompile, serving historical block hashes in state...

...moving committee index outside attestation and adding blob schedule to EL config.

1. AA account abstraction via EIP-7702 means every EOA can run smart contract code too. this allows for better UX, batching, delegating keys, etc. however, it does not allow for key rotation

2. max effective balance increase right now, every validator can only have 32 ETH of "effective stake", or stake that has voting power and rewards. this creates load on the network as big providers split up their validators and every validator has to vote

if we increase the max to 2048 ETH then big staking providers can consolidate into a few big validators, leaving small stakers unaffected. it also helps small solo stakers compound automatically

3. blob target increase blobs are a special place where the network guarantees data will be available for up to 2 weeks. its needed to make proofs to exit rollups in case the sequencer evil we target 3 blobs per block rn, but we can go up to 6. more blobs = more L2 scalability

4. increase calldata cost we need to incentivize rollups to use blobs instead of calldata (the previous method) bc calldata bloats up the chain history

5. execution layer validator exits this makes liquid staking more trustless. unstaking ETH requires a consensus layer message signed by the validator with this, stakers will be able to exit with a message on the execution layer. this means smart contracts can force exits too

6. more secure validator deposits the system for validator deposits rn is a huge tech debt hack that was made before the merge. rn it uses the eth1data poll which is a vote of validators on whether or not a deposit was legit now deposits are gonna be execution layer based

7. BLS12-381 precompile BLS is a signature scheme used to aggregate votes from the consensus layer. Ethereum uses the BLS12-381 curve for that adding a precompile means contracts can use it too, making restaking, staking pools, etc easier

8. serving historical blockhashes in state atm we have the BLOCKHASH opcode which returns the latest ethereum block hash, however this might be a problem for stateless clients in the future EIP-2935 means the last 8192 block hashes can be served from a system contract

9. move committee index outside attestation an attestation message (a vote that a block is legit) has 3 elements: two votes and the committee index. taking the committee index out can make aggregating votes and ZK proving so much easier + more efficiency for consensus clients

10. add blob schedule to EL config atm only the consensus client keeps track of blob fee history but sometimes it might be needed by the execution client. this update means the CL client dont have to be passing the blob fee data to the EL client

hopefully this was helpful :-) buy more eth, have a good day