Add Fusaka pm docs

Fusaka/fusaka-mainnet-plan.md

@@ -0,0 +1,50 @@
+# Mainnet Upgrade & Incident Response Team Plan
+
+## Upgrade Information
+
+| Epoch | Start Slot | Unix | UTC (+00:00) | Moscow (+03:00) | Los Angeles (-07:00) | New York (-04:00) | Brisbane (+10:00)
+| 411392 | 13164544 | 1764798551 | 2025-12-03 21:49:11 | 2025-12-04 00:49:11 | 2025-12-03 13:49:11 | 2025-12-03 16:49:11 | 2025-12-04 07:49:11
+
+## Upgrade / Incident Response team
+
+### Client Team Coordinators
+| Client Team | Primary | Backup |
+|-------------|---------------------|--------------------|
+| Besu | ||
+| Erigon | ||
+| Geth | | |
+| Grandine | | |
+| Lighthouse | ||
+| Lodestar | | |
+| Nimbus | | |
+| Nethermind | | |
+| Prysm | | |
+| Reth | | |
+| Teku | | |
+
+### Coordinators
+| Role | Primary | Backup |
+|------|---------|----------------------------|
+| DevOps Coordinator | | |
+| Testing Coordinator | ||
+| Communication Coordinator | | |
+| Security Coordinator | ||
+
+## Communication Channels
+- **Primary Communication:** `#fusaka-upgrade` (Eth R&D Discord)
+    - Channel to be created ~24h before the upgrade and archived once upgrade has successfully activated.
+- **Status Updates:** `#announcements` (Eth R&D Discord)
+
+## Upgrade Verification post upgrade
+- [ ] All clients remained in consensus throughout the upgrade
+- [ ] Chain finalized
+- [ ] Validator participation and block production (monitored for at least 32 epochs)
+- [ ] Verified stability of the network for 48 hours after upgrade.
+
+## Disclaimer
+The individuals and organisations named in this document have been listed solely so that other community members know whom to contact for faster coordination and incident-response during the Fusaka network upgrade.
+
+Their inclusion does not:
+- Create any fiduciary, contractual, or other legal duty towards any other party;
+- Constitute any representation, warranty, or guarantee of the performance, security, or outcome of the Fusaka upgrade; or
+- Give rise to any liability, whether in negligence, tort, contract, or otherwise, for any direct, indirect, or consequential damages (including any loss of funds) arising out of or in connection with the Fusaka upgrade or reliance on this document.

Fusaka/fusaka-pm.md

@@ -0,0 +1,26 @@
+# Fusaka Devnets
+
+### Latest devnet:
+- [devnet-5](https://notes.ethereum.org/@ethpandaops/fusaka-devnet-5)
+  - [network-config](https://github.com/ethpandaops/fusaka-devnets/tree/master/network-configs/devnet-5)
+- [devnet-4](https://notes.ethereum.org/@ethpandaops/fusaka-devnet-4)
+  - [network-config](https://github.com/ethpandaops/fusaka-devnets/tree/master/network-configs/devnet-4)
+- [devnet-3](https://notes.ethereum.org/@ethpandaops/fusaka-devnet-3)
+  - [network-config](https://github.com/ethpandaops/fusaka-devnets/tree/master/network-configs/devnet-3)
+- [devnet-2](https://notes.ethereum.org/@ethpandaops/fusaka-devnet-2)
+  - [network-config](https://github.com/ethpandaops/fusaka-devnets/tree/master/network-configs/devnet-2)
+- [devnet-1](https://notes.ethereum.org/@ethpandaops/fusaka-devnet-1)
+  - [network-config](https://github.com/ethpandaops/fusaka-devnets/tree/master/network-configs/devnet-1)
+- [devnet-0](https://notes.ethereum.org/@ethpandaops/fusaka-devnet-0)
+  - [network-config](https://github.com/ethpandaops/fusaka-devnets/tree/master/network-configs/devnet-0)
+
+
+# Fusaka Deployments
+- Holesky: Oct 1, 2025 at 08:48:00 UTC (slot 5283840)
+  - [configuration](https://github.com/eth-clients/holesky)
+- Sepolia: Oct 14, 2025 at 07:36:00 UTC (slot 8724480)
+  - [configuration](https://github.com/eth-clients/sepolia)
+- Hoodi: Oct 28, 2025 at 18:53:12 UTC (slot 1622016)
+  - [configuration](https://github.com/eth-clients/hoodi)
+- Mainnet: Dec 3, 2025 at 21:49:11 UTC (slot 13164544)
+  - [configuration](https://github.com/eth-clients/mainnet)

Fusaka/peerdas-readiness.md

@@ -2,7 +2,7 @@
 
 This document outlines various tasks to work through to make PeerDAS ready for Mainnet release.
 
-*Note*: 
+*Note*:
 This document has been replaced by the following Google Docs to serve as the single source of truth and allow for easier modification. **Ongoing R&D and implementation work will be updated and tracked in the document below:**
 
 https://docs.google.com/document/d/1MXf5zTU58mRj0Yq88EPBP1gCJzWTY9FRfUdpZjcfgqw/edit?tab=t.0#heading=h.fg53pp2wx7q9
@@ -69,7 +69,7 @@ https://docs.google.com/document/d/1MXf5zTU58mRj0Yq88EPBP1gCJzWTY9FRfUdpZjcfgqw/
  * [ ] Stub out proof computation in the KZG lib and test CL performance with high blob count (to simulate proof computation offloaded).
  * [ ] Stress test mempool to make sure the ELs can handle high blob count.
 * [ ] High blob throughput testing (48/64 blobs) on a large network that mirrors mainnet network typology (after [proof computation changes](https://github.com/ethereum/EIPs/pull/9378) implemented in at least 1 CL/EL client pair)
- 
+
 ## R&D
 
 * [ ] Anaylsis of new blob count impact on bandwidth, hardware requirements once clients are feature complete (`peerdas-devnet-6`)