[ANALYSIS] Fusaka Upgrade

The Fusaka upgrade is already live in Ethereum. We need to start analyzing whats the impact strategy, on Hedera

We need to conduct and Analysis producing a document with the following format:

**Intro**
Explaining main fusaka objective for ethereum

**EIPS included**
Explain EIPS included with exec summary

**EIPS that do not apply**
List all the EIPS that do not apply to hedera and Why

**EIPS that do apply on Hedera**

**Global needs for implementation**

Besu Version
Spect test version
How many HIPS are needed and why
Checklist needed?
Any POC Spike needed?
Split the Elephant. High level plan by Sprints (releases) No need to be accurate or estimation. Its strategizing the features
- Including EPIC-Features-User Storys to accomplish everything ( tests planm performance tests, checklist, demo etc)
Any feature flag
Evm versioning and properties
Risks per EIP
other teams dependencies

**Details per EIP for implementation**

What changes need to be done
- only besu library
- if code changes needed ( no need to go into the code changes details, only high high level impact)
- which test dimensions are neeede
- Any feature flag

Risks per EIP
other teams dependencies

Testing Strategy
- Per EIP define what testing dimension are picked and why (sdk, solidity, hapi, spec tests, checklist)

**References**
- Fusaka EIPS and sub EIPS links
- Others

No repository files, entry points, or tests are named. Start by collecting the Fusaka EIPs and comparing their applicability to Hedera, Besu, and EVM behavior. Done means producing the requested document with EIP summaries, implementation and testing strategy, risks, dependencies, planning items, and references.

Written by the indexing model from the issue text.