{"id":"fusaka","title":"Ethereum Fusaka Upgrade","content":"**Fusaka** is a major network upgrade for the [Ethereum](https://iq.wiki/wiki/ethereum) [blockchain](https://iq.wiki/wiki/blockchain) that activated on [mainnet](https://iq.wiki/wiki/mainnet) on December 3, 2025. As the second major upgrade of 2025, following [Pectra](https://iq.wiki/wiki/ethereum-pectra-upgrade), Fusaka's primary objective was to enhance the network's scalability, efficiency, and security. The name is a portmanteau of **Fulu** and **Osaka**, representing the simultaneous upgrades to Ethereum's consensus and execution layers, respectively. The upgrade's developer-chosen mascot is a zebra, symbolizing the column-based data sampling method of its main feature, PeerDAS. This upgrade was designed to significantly reduce data costs for Layer-2 rollups and increase the network's overall throughput. [\\[17\\]](#cite-id-ueGefuNdUQLTbNTj) [\\[18\\]](#cite-id-NccqDNRiEKIJWKaJ) [\\[28\\]](#cite-id-vXDEbYmwhaBf8NUn)​\n\n[YOUTUBE@VID](https://youtube.com/watch?v=_6471x7Wzvg)\n\n## Overview\n\nThe Fusaka [hard fork](https://iq.wiki/wiki/hard-fork) represented the next significant step in [Ethereum](https://iq.wiki/wiki/ethereum)'s ongoing development roadmap, following the [Pectra](https://iq.wiki/wiki/ethereum-pectra-upgrade) upgrade in May 2025. Its primary objective was to improve the overall performance and resilience of the [Ethereum](https://iq.wiki/wiki/ethereum) network by focusing on backend enhancements rather than direct user-facing features. A central component was the implementation of PeerDAS (Peer Data Availability Sampling), which was designed to make Ethereum's base layer more efficient at handling the vast amounts of data from its growing Layer-2 ecosystem. The upgrade bundled a set of [Ethereum Improvement Proposals](https://iq.wiki/wiki/ethereum-improvement-proposal-eip) (EIPs) designed to optimize core protocol functions related to scalability, [node](https://iq.wiki/wiki/node) health, and efficiency, leaving existing smart contracts untouched. [\\[19\\]](#cite-id-1lxY5LvZF46toqAS) [\\[21\\]](#cite-id-kTsbmu7b0NyblaBm)​\n\n## Technology\n\nThe Fusaka upgrade is a comprehensive update that included 13 [Ethereum Improvement Proposals](https://iq.wiki/wiki/ethereum-improvement-proposal-eip) (EIPs) aimed at enhancing the network's capabilities. The flagship feature was **EIP-7594 (PeerDAS)**, which enhances data availability for L2s by allowing nodes to verify data by checking small, random samples (\"slices\") instead of downloading entire datasets. This enables a theoretical 8x increase in data space for blobs, significantly reducing costs for rollups. [\\[28\\]](#cite-id-vXDEbYmwhaBf8NUn) [\\[19\\]](#cite-id-1lxY5LvZF46toqAS)​\n\nHowever, not all initially considered proposals were part of the Fusaka release. EIP-7907, which aimed to double the contract code size limit and introduce [gas](https://iq.wiki/wiki/gas) metering, was excluded to streamline the testing process and avoid potential delays. Similarly, the controversial EVM Object Format (EOF) upgrade, which proposed an overhaul of the [Ethereum Virtual Machine](https://iq.wiki/wiki/ethereum-virtual-machine-evm) (EVM) to simplify [smart contract](https://iq.wiki/wiki/smart-contract) development, was officially removed from Fusaka due to technical uncertainties and community pushback regarding its complexity and implications. The decision to remove EOF was made to prioritize other critical features like PeerDAS and to ensure the upgrade's timeline was not jeopardized. [\\[14\\]](#cite-id-fN49vIBZ8W) [\\[3\\]](#cite-id-NekYkczXCZ) [\\[4\\]](#cite-id-XoxU96IfHw)​\n\nAnother significant change included in Fusaka was the increase of the [Ethereum](https://iq.wiki/wiki/ethereum) [gas](https://iq.wiki/wiki/gas) limit. EIP-7935 was an informational EIP that coordinated client teams to raise the default block gas limit to approximately 60 million, up from the pre-Fusaka level of 45 million. This allows more transactions and computations to be processed in each block, enhancing network throughput and supporting more complex operations on the base layer. [\\[17\\]](#cite-id-ueGefuNdUQLTbNTj) [\\[28\\]](#cite-id-vXDEbYmwhaBf8NUn)​\n\n[YOUTUBE@VID](https://youtube.com/watch?v=_6471x7Wzvg)\n\n### Key Ethereum Improvement Proposals (EIPs)\n\nFusaka bundled 13 infrastructure-level EIPs that refine scalability, improve efficiency, and harden the network without breaking existing contracts. The key proposals are categorized below.\n\n#### Blob Scaling\n\n* **EIP-7594 (PeerDAS):** The central feature of the upgrade, this EIP implemented Peer Data Availability Sampling. It allows nodes to verify data availability by downloading small, random \"slices\" of data [blobs](https://iq.wiki/wiki/blobs) instead of the entire dataset. This lightens the load on most nodes and enabled a theoretical 8x increase in data throughput for rollups. [\\[28\\]](#cite-id-vXDEbYmwhaBf8NUn)\n* **EIP-7892 (Blob Parameter-Only Forks):** This created a lightweight framework for future adjustments to blob capacity (target and maximum per block) without requiring a full hard [fork](https://iq.wiki/wiki/fork), streamlining subsequent scalability upgrades. [\\[28\\]](#cite-id-vXDEbYmwhaBf8NUn)\n* **EIP-7918 (Blob Base Fee Bound):** This EIP linked blob fees to execution costs by establishing a minimum reserve price for data [blobs](https://iq.wiki/wiki/blobs). This creates a fairer, more predictable pricing mechanism by preventing the blob base fee from collapsing to near-zero during periods of low demand. [\\[28\\]](#cite-id-vXDEbYmwhaBf8NUn)\n\n#### L1 Scaling & Security\n\n* **EIP-7642 (History Expiry):** An informational EIP that mandated client support for history expiry. This built on the partial history expiry implemented in July 2025 to further reduce node storage and synchronization burdens, supporting long-term decentralization.\n* **EIP-7825 (Spam Resistance Checks):** This proposal prevents malicious transaction spam by capping the [gas](https://iq.wiki/wiki/gas) limit for any single transaction at 16,777,216 (2^24). This helps nodes remain [stable](https://iq.wiki/wiki/stable) and enables safer future increases to the block gas limit. [\\[28\\]](#cite-id-vXDEbYmwhaBf8NUn)\n* **EIP-7823 & EIP-7883 (MODEXP Adjustments):** These two EIPs strengthened Ethereum’s resilience to denial-of-service (DoS) attacks. EIP-7823 capped the input sizes for the MODEXP precompile to a maximum of 1024 bytes, while EIP-7883 adjusted its [gas](https://iq.wiki/wiki/gas) pricing to better reflect its real-world computational cost. [\\[28\\]](#cite-id-vXDEbYmwhaBf8NUn)\n* **EIP-7934 (RLP Execution Block Size Limit):** This imposed an upper limit of 10 MiB on the size of RLP-encoded execution blocks to limit network bloat and reduce denial-of-service risks.\n* **EIP-7935 (Default Block Gas Limit):** An informational EIP that coordinated client teams to raise the default [block](https://iq.wiki/wiki/block) [gas](https://iq.wiki/wiki/gas) limit to approximately 60 million, enabling more transactions per [block](https://iq.wiki/wiki/block).\n\n#### User Experience (UX) and Developer Improvements\n\n* **EIP-7951 (secp256r1 Precompile):** This introduced a precompile for `secp256r1` signature verification, enabling native support for passkeys and device-based signers (e.g., Apple Secure Enclave, WebAuthn). This paves the way for wallets to use biometrics like Face ID instead of seed phrases. [\\[28\\]](#cite-id-vXDEbYmwhaBf8NUn)\n* **EIP-7917 (Deterministic Proposer Lookahead):** This allows the Beacon Chain to precompute [block](https://iq.wiki/wiki/block) proposers for the entire next epoch. This streamlines the validation process and enables L2 networks to offer features like near-instant transaction preconfirmations. [\\[28\\]](#cite-id-vXDEbYmwhaBf8NUn)\n* **EIP-7939 (CLZ Opcode):** This added a low-cost \"count leading zeros\" (CLZ) instruction to the EVM, which cheapens and optimizes certain bitwise and arithmetic calculations used in cryptography and compression. [\\[28\\]](#cite-id-vXDEbYmwhaBf8NUn)\n\n#### Meta EIPs\n\n* **EIP-7910 (`eth_config` RPC Method):** An informational EIP for a new RPC endpoint allowing node operators to query fork configurations. This helps prevent misconfigurations that caused issues on testnets during the Pectra upgrade, ensuring smoother transitions. [\\[28\\]](#cite-id-vXDEbYmwhaBf8NUn)\n\nThis set of EIPs was finalized after an EIP freeze on August 1, 2025, to ensure a focused and testable upgrade. \\[\\[cointelegraph.com/explained/ethereums-fusaka-upgrade-set-for-november-what-you-need-to-know]\\[Cointelegraph explanation of Fusaka upgrade]] \\[\\[etherworld.co/2025/06/17/all-you-need-to-know-about-ethereum-fusaka-upgrade/]\\[EtherWorld overview of Fusaka]]\n\n## Development and Timeline\n\nPreparations for the Fusaka [hard fork](https://iq.wiki/wiki/hard-fork) were actively underway throughout 2025, following an aggressive development schedule. The process involved client teams preparing their software for the upgrade and multiple development networks (devnets) to test and refine the included EIPs. After an initial devnet, Fusaka Devnet 2 launched on June 27, 2025, serving as a \"bug-hunt\" to identify issues, followed by Devnet 3 to test the \"happy-path\" scenario. A final devnet was launched on July 23, 2025, with public testnets following in October. [\\[1\\]](#cite-id-Li6n5BiGIo) [\\[22\\]](#cite-id-uWpRV3iLKT8amVNs) [\\[15\\]](#cite-id-1x3xkpqNCw)​\n\nDespite the ambitious timeline, some members of the [Ethereum](https://iq.wiki/wiki/ethereum) community had expressed concerns about meeting the proposed launch window. Nixo, an [Ethereum](https://iq.wiki/wiki/ethereum) protocol support member, noted the tight schedule required to ship the upgrade before Devconnect. However, developers successfully conducted all planned tests, leading to a finalized mainnet date. [\\[7\\]](#cite-id-lg9BI061ys) [\\[5\\]](#cite-id-z1uuYyootg)​\n\n## Testnet and Mainnet Launch\n\nThe [testnet](https://iq.wiki/wiki/testnet) deployment for the Fusaka upgrade was successfully completed in October 2025 across three \"dress rehearsals.\" The upgrade was activated on Holesky (October 1), Sepolia (October 14), and finally on Hoodi (October 28), concluding the testnet phase and confirming the upgrade's readiness for mainnet. [\\[23\\]](#cite-id-dVCayHCLFoO3ZJQz) [\\[24\\]](#cite-id-5LqfjqzSe6QQYXvd)​\n\nOn November 12, 2025, the [Ethereum](https://iq.wiki/wiki/ethereum) [Foundation](https://iq.wiki/wiki/foundation) formally announced the mainnet launch date. The Fusaka hard fork activated on **December 3, 2025, at 21:49:11 UTC**, corresponding to block `13,164,544`. The launch date was finalized by core developers on October 30, following the successful testnet deployments, placing it after the Devconnect conference held in Buenos Aires in mid-November. [\\[25\\]](#cite-id-04a2PqDqFtHN859K) [\\[26\\]](#cite-id-Npco7HoH9LoQMsNl) [\\[6\\]](#cite-id-ZyBgGDVANz)​\n\nFollowing the main fork, two smaller \"Blob Parameter Only\" (BPO) forks are planned to increase blob capacity:\n\n* **BPO Fork 1:** Scheduled for December 17, 2025, this fork will increase the maximum blob count per block from 9 to 15.\n* **BPO Fork 2:** Scheduled for January 7, 2026, this fork will further increase the maximum blobs per block to 21.\n\nThese lightweight forks are designed to scale network data capacity without requiring full client updates. [\\[17\\]](#cite-id-ueGefuNdUQLTbNTj) [\\[20\\]](#cite-id-04wG6fFUs9j0iY3L)​\n\n## Security Audit Contest\n\nTo bolster security ahead of the [mainnet](https://iq.wiki/wiki/mainnet) launch, the [Ethereum Foundation](https://iq.wiki/wiki/ethereum-foundation-ef) announced a 100,000 and [Lido ](https://iq.wiki/wiki/lido-dao)contributed $25,000 to the prize pool. The competition invited security researchers to identify vulnerabilities in the upgrade's codebase, with a 2x points multiplier for valid findings in the first week and a 1.5x multiplier in the second week to incentivize early discoveries. [\\[16\\]](#cite-id-eAKX2MP3Os) [\\[20\\]](#cite-id-04wG6fFUs9j0iY3L)​\n\n## Impact on Stakeholders\n\n### Impact on Users and Developers\n\nFor developers, Fusaka was designed to be a non-disruptive, backwards-compatible upgrade. Existing smart contracts were not expected to break, though contracts with very high gas consumption (approaching the new 16.7 million transaction gas cap) or heavy `MODEXP` precompile usage may have required optimization. The primary benefits for builders come from the increased [gas](https://iq.wiki/wiki/gas) limit, which allows for more complex operations, and performance improvements from PeerDAS, which lowers data fees for rollups. New tools like the `CLZ` opcode and native passkey support (`secp256r1`) provide new tools for optimizing on-chain logic and creating user-friendly wallets. [\\[28\\]](#cite-id-vXDEbYmwhaBf8NUn)​\n\nFor everyday users, the main benefit of Fusaka is expected to be lower transaction fees on Layer-2 networks. By making it cheaper for rollups to post data to [Ethereum](https://iq.wiki/wiki/ethereum), the upgrade should lead to more affordable user transactions on L2s. The upgrade was not expected to significantly lower gas fees on the [Ethereum](https://iq.wiki/wiki/ethereum) mainnet itself. Additionally, the `secp256r1` precompile paves the way for a new generation of wallets secured by device biometrics (e.g., Face ID) instead of seed phrases, simplifying user onboarding and account recovery. [\\[18\\]](#cite-id-NccqDNRiEKIJWKaJ) [\\[28\\]](#cite-id-vXDEbYmwhaBf8NUn)​\n\n### Impact on Node Operators\n\nAll node operators and stakers had to update their execution and consensus client software to Fusaka-compatible versions to remain synced with the network. The hardware impact varies by operator type: [\\[28\\]](#cite-id-vXDEbYmwhaBf8NUn)​\n\n* **Full Nodes (Non-validating):** Experienced a significant decrease (around 80%) in bandwidth and storage needs related to blobs, as they now only need to store a fraction (approx. 1/8th) of the total blob data.\n* **Solo Stakers:** Saw a moderate decrease in download bandwidth. However, those who build blocks locally may require higher upload bandwidth as blob capacity increases via subsequent BPO forks.\n* **Large Validators / Supernodes (>= 4096 ETH):** These operators, who now custody all blob data, saw a substantial increase in storage and bandwidth requirements as blob capacity scales. They play a key role in \"healing\" the network by providing full data copies.\n\n## Future Upgrades\n\nFollowing Fusaka, attention is already turning to the subsequent [Ethereum](https://iq.wiki/wiki/ethereum) upgrade, codenamed [Glamsterdam](https://iq.wiki/wiki/ethereum-glamsterdam-upgrade), which is anticipated in 2026. While plans are not finalized, developers intend to include enshrined Proposer-Builder Separation (ePBS) in the upgrade. Another proposal, put forth by [Ethereum](https://iq.wiki/wiki/ethereum) core developer Barnabé Monnot, suggests [halving](https://iq.wiki/wiki/halving) Ethereum's [block](https://iq.wiki/wiki/block) time from 12 seconds to six seconds to enhance the performance and user experience of [decentralized applications](https://iq.wiki/wiki/decentralized-application) (dApps). [\\[23\\]](#cite-id-dVCayHCLFoO3ZJQz) [\\[8\\]](#cite-id-19F7DaZ4oq) [\\[2\\]](#cite-id-xv4DRVOBy1)​\n\n## Regulatory Discussions\n\nIn parallel with the technical developments, the U.S. Securities and Exchange Commission (SEC) engaged in discussions in 2025 with key [blockchain](https://iq.wiki/wiki/blockchain) industry stakeholders, including representatives from [Ethereum](https://iq.wiki/wiki/ethereum)-aligned organizations such as the ERC-3643 Association, [Chainlink](https://iq.wiki/wiki/chainlink) Labs, the Enterprise [Ethereum](https://iq.wiki/wiki/ethereum) Alliance, and LF Decentralized Trust. The meeting focused on exploring potential token standards that could facilitate the compliant issuance and transfer of tokenized securities.\n\nThe discussions primarily revolved around integrating open standards like ERC-3643 and compliance frameworks such as Chainlink’s Automated Compliance Engine (ACE) into the existing regulatory landscape. ERC-3643 is a token standard designed for compliant capital markets on [Ethereum](https://iq.wiki/wiki/ethereum), while Chainlink’s ACE provides a [smart-contract](https://iq.wiki/wiki/smart-contract)-based compliance framework for managing tokenized assets, including securities and [real-world assets](https://iq.wiki/wiki/real-world-assets-rwas).\n\nDennis O’Connell, president of the ERC-3643 Association, indicated that the meeting signaled a notable shift in the SEC's approach, demonstrating increased engagement and a willingness to understand how [blockchain](https://iq.wiki/wiki/blockchain) standards can align with regulatory oversight. He noted that the discussions helped illustrate how standardized frameworks could enable regulatory compliance while fostering innovation.\n\nFollowing the meeting, SEC Chair Paul Atkins suggested that the agency is considering an \"innovation exemption\" within its regulatory framework to support tokenization. Atkins acknowledged the inevitable migration of assets onto [blockchain](https://iq.wiki/wiki/blockchain) networks and indicated that the SEC might implement changes to accommodate new trading methods tailored for tokenized securities. [\\[9\\]](#cite-id-EAEAFDwgL4) [\\[10\\]](#cite-id-i9hSUNr5TI) [\\[11\\]](#cite-id-MuLEm4ny3S) [\\[12\\]](#cite-id-GwXGrz9Wyu)​\n\n## Economic Considerations\n\nThe Fusaka upgrade has several economic implications. The increase in the [Ethereum](https://iq.wiki/wiki/ethereum) [block](https://iq.wiki/wiki/block) [gas](https://iq.wiki/wiki/gas) limit to 60 million, while intended to improve throughput, sparked concerns that higher hardware demands could strain smaller solo validators and nudge the network toward centralization. Similarly, while PeerDAS lowers the barrier for most nodes, its design may lead to the emergence of \"supernodes\"—highly capable nodes run by large entities that store the full L2 data. Critics worried this could centralize the critical function of data storage, though proponents argued this was a safe trade-off since all validators can still independently verify data availability via sampling. [\\[28\\]](#cite-id-vXDEbYmwhaBf8NUn) [\\[17\\]](#cite-id-ueGefuNdUQLTbNTj)​\n\nAnticipation for the upgrade was a key factor in market activity. In the months leading up to November 2025, large investors (\"whales\") accumulated over 7.6 million ETH. However, analysts noted a potential trade-off: by creating dedicated \"blob lanes\" for L2 data, Fusaka is expected to lower fee pressure on the base layer. This could reduce the amount of ETH burned via EIP-1559, potentially weakening Ethereum's deflationary monetary policy. [\\[27\\]](#cite-id-s47sKyfabvq6WkFU) [\\[26\\]](#cite-id-Npco7HoH9LoQMsNl)​\n\nAnalysts viewed the upgrade as a critical development for maintaining Ethereum's competitive position as the primary settlement layer for decentralized applications, especially as capital flows to rival blockchains. A successful implementation was expected to reinforce Ethereum’s market dominance by enhancing scalability and reducing transaction costs for the entire L2 ecosystem. [\\[13\\]](#cite-id-pyScdHPfQp)​","summary":"Fusaka is an upcoming Ethereum hard fork, tentatively scheduled for November 2025. It aims to enhance network scalability and efficiency through 11 Ethereum Imp...","images":[{"id":"QmbU5BC4Eb1HBEETE7aVmUzs5CaCN3Wx4hPiDpqF8hBPfZ","type":"image/jpeg, image/png"}],"categories":[{"id":"cryptocurrencies","title":"Cryptocurrencies"}],"tags":[{"id":"Ethereum"},{"id":"Protocols"},{"id":"Developers"},{"id":"Glossary"},{"id":"Blockchains"}],"media":[{"id":"https://www.youtube.com/watch?v=_6471x7Wzvg","size":null,"name":"_6471x7Wzvg","type":null,"source":"YOUTUBE"},{"id":"https://www.youtube.com/watch?v=Rdin4Rz7HkM","size":null,"name":"Rdin4Rz7HkM","type":null,"source":"YOUTUBE"},{"id":"QmdnNCnKyGnA4t2hYsLbG41tGWxEiSTsCjdueRKxru565b","size":null,"name":"a-digital-illustration-depicting-the-eth_j8-K2DE4QXWr7xxGk6p8JA_vj2rTHW-Saa_tV-ILI29VA.jpeg","type":null,"source":"IPFS_IMG"}],"metadata":[{"id":"website","value":"https://ethereum.foundation/"},{"id":"references","value":"[{\"id\":\"Li6n5BiGIo\",\"url\":\"https://cryptorank.io/news/feed/35f25-ethereum-plans-fusaka-upgrade-for-november-launch\",\"description\":\"Cryptorank news on Fusaka\",\"timestamp\":1753818761747},{\"id\":\"xv4DRVOBy1\",\"url\":\"https://cointelegraph.com/news/ethereum-s-fusaka-fork-tipped-for-november-as-glamsterdam-comes-into-view\",\"description\":\"Cointelegraph article on Fusaka and Glamsterdam\",\"timestamp\":1753818761747},{\"id\":\"NekYkczXCZ\",\"url\":\"https://eips.ethereum.org/EIPS/eip-7907\",\"description\":\"EIP-7907 documentation\",\"timestamp\":1753818761747},{\"id\":\"XoxU96IfHw\",\"url\":\"https://cryptoslate.com/ethereum-drops-eof-from-fusaka-upgrade-after-community-pushback/\",\"description\":\"CryptoSlate article on EOF removal\",\"timestamp\":1753818761747},{\"id\":\"z1uuYyootg\",\"url\":\"https://cryptoslate.com/ethereum-celebrates-10-years-with-symbolic-torch-nft-and-eyes-fusaka-upgrade/\",\"description\":\"CryptoSlate article on Fusaka and Ethereum's 10th anniversary\",\"timestamp\":1753818761747},{\"id\":\"ZyBgGDVANz\",\"url\":\"https://devconnect.org/\",\"description\":\"Devconnect official website\",\"timestamp\":1753818761747},{\"id\":\"lg9BI061ys\",\"url\":\"https://x.com/nixorokish/status/1945280052855283911\",\"description\":\"Nixo's tweet on timeline concerns\",\"timestamp\":1753818761747},{\"id\":\"19F7DaZ4oq\",\"url\":\"https://ethereum-magicians.org/t/eip-7782-the-case-for-2x-shorter-slot-times-in-glamsterdam/24616?u=barnabe\",\"description\":\"Barnabé Monnot's proposal\",\"timestamp\":1753818761747},{\"id\":\"EAEAFDwgL4\",\"url\":\"https://coinpaper.com/10063/ethereum-plans-fusaka-upgrade-for-november-launch\",\"description\":\"Coinpaper article on Fusaka and SEC discussions\",\"timestamp\":1753818761747},{\"id\":\"i9hSUNr5TI\",\"url\":\"https://x.com/RedoudouM/status/1945848016461611042\",\"description\":\"RedoudouM's tweet on SEC meeting\",\"timestamp\":1753818761747},{\"id\":\"MuLEm4ny3S\",\"url\":\"https://x.com/chainlink/status/1945966913693393134\",\"description\":\"Chainlink's tweet on SEC meeting\",\"timestamp\":1753818761747},{\"id\":\"GwXGrz9Wyu\",\"url\":\"https://www.bloomberg.com/news/articles/2025-07-17/sec-to-weigh-innovation-exception-tied-to-crypto-atkins-says\",\"description\":\"Bloomberg article on SEC's innovation exemption comments\",\"timestamp\":1753818761747},{\"id\":\"pyScdHPfQp\",\"url\":\"https://www.benzinga.com/markets/cryptocurrency/25/09/47685115/ethereum-faces-alt-season-pressure-why-fusaka-upgrade-could-be-a-gamechanger\",\"description\":\"Benzinga on Fusaka's market impact\",\"timestamp\":1758039148949},{\"id\":\"fN49vIBZ8W\",\"url\":\"https://cointelegraph.com/explained/ethereums-fusaka-upgrade-set-for-november-what-you-need-to-know\",\"description\":\"Cointelegraph explanation of Fusaka upgrade\",\"timestamp\":1758039721107},{\"id\":\"1x3xkpqNCw\",\"url\":\"https://etherworld.co/2025/06/17/all-you-need-to-know-about-ethereum-fusaka-upgrade/\",\"description\":\"EtherWorld overview of Fusaka\",\"timestamp\":1758039721107},{\"id\":\"eAKX2MP3Os\",\"url\":\"https://blog.ethereum.org/2025/09/15/fusaka-audit-content\",\"description\":\"Ethereum Foundation blog post on audit contest\",\"timestamp\":1758039721107},{\"id\":\"ueGefuNdUQLTbNTj\",\"url\":\"https://blog.quicknode.com/ethereum-fusaka-upgrade-what-you-need-to-know/\",\"description\":\"QuickNode overview of Fusaka upgrade\",\"timestamp\":1763177348420},{\"id\":\"NccqDNRiEKIJWKaJ\",\"url\":\"https://www.coindesk.com/tech/2025/10/08/ethereum-s-fusaka-upgrade-could-cut-node-costs-ease-adoption\",\"description\":\"CoinDesk report on Fusaka goals\",\"timestamp\":1763177348420},{\"id\":\"1lxY5LvZF46toqAS\",\"url\":\"https://www.dlnews.com/articles/defi/what-fusaka-upgrade-means-for-ethereum-410bn-blockchain/\",\"description\":\"DL News on Fusaka mainnet date\",\"timestamp\":1763177348420},{\"id\":\"04wG6fFUs9j0iY3L\",\"url\":\"https://blockworks.co/news/ethereum-fusaka-dec3-launch\",\"description\":\"Blockworks on Fusaka December 3 launch date\",\"timestamp\":1763177348420},{\"id\":\"kTsbmu7b0NyblaBm\",\"url\":\"https://www.bitget.com/academy/what-is-ethereum-fusaka-upgrade-complete-guide-2025\",\"description\":\"Bitget guide to Fusaka upgrade\",\"timestamp\":1763177678030},{\"id\":\"uWpRV3iLKT8amVNs\",\"url\":\"https://github.com/hyperledger/besu\",\"description\":\"Hyperledger Besu Github repository\",\"timestamp\":1763177678030},{\"id\":\"dVCayHCLFoO3ZJQz\",\"url\":\"https://www.coindesk.com/tech/2025/10/28/ethereum-s-fusaka-upgrade-completes-final-hoodi-test-ahead-of-mainnet-launch\",\"description\":\"CoinDesk on final Hoodi test\",\"timestamp\":1763177678030},{\"id\":\"5LqfjqzSe6QQYXvd\",\"url\":\"http://www.bitget.com/academy/what-is-ethereum-fusaka-upgrade-complete-guide-2025\",\"description\":\"Bitget guide to Fusaka upgrade\",\"timestamp\":1763177678030},{\"id\":\"04a2PqDqFtHN859K\",\"url\":\"https://x.com/ethereum/status/1988627667675906233\",\"description\":\"Official Ethereum announcement of Fusaka\",\"timestamp\":1763177678030},{\"id\":\"Npco7HoH9LoQMsNl\",\"url\":\"https://decrypt.co/348073/ethereum-spot-order-activity-institutional-re-entry\",\"description\":\"Decrypt on Fusaka mainnet date\",\"timestamp\":1763177678030},{\"id\":\"s47sKyfabvq6WkFU\",\"url\":\"https://coinspot.io/en/analysis/ethereum-strengthens-its-position-whales-accumulate-7-6-million-eth-ahead-of-fusaka-upgrade/\",\"description\":\"Coinspot on whale accumulation and Fusaka\",\"timestamp\":1763177678030},{\"id\":\"vXDEbYmwhaBf8NUn\",\"url\":\"https://ethereum.org/roadmap/fusaka/\",\"description\":\"Ethereum Foundation page on Fusaka upgrade\",\"timestamp\":1764753819988}]"},{"id":"previous_cid","value":"\"https://ipfs.everipedia.org/ipfs/QmenZMX1NiMMfxXXpizg3jJyW68hXq75Z7ANzWuH9JbEgw\""},{"id":"commit-message","value":"\"Removed Fusaka upgrade information.\""},{"id":"previous_cid","value":"QmenZMX1NiMMfxXXpizg3jJyW68hXq75Z7ANzWuH9JbEgw"}],"events":[{"id":"f4270f69-a4a4-4607-a0c2-7bdd35347de1","date":"2025-11-01","title":"Fusaka Hard Fork Scheduled","type":"CREATED","description":"Ethereum's Fusaka hard fork is tentatively scheduled for early November 2025, aiming to enhance network efficiency and scalability.","link":null,"multiDateStart":null,"multiDateEnd":null,"continent":null,"country":null},{"id":"170aae88-4a79-4318-831d-faaf1108dfa1","date":"2025-04-01","title":"EVM Object Format Excluded from Fusaka","type":"DEFAULT","description":"The controversial EVM Object Format (EOF) was officially removed from the Fusaka upgrade due to technical uncertainties and community pushback.","link":null,"multiDateStart":null,"multiDateEnd":null,"continent":null,"country":null},{"id":"b27de039-8f26-4267-b5fe-9acc89375969","date":"2025-07-01","title":"Devnet-3 Launched","type":"DEFAULT","description":"Devnet-3 for the Fusaka hard fork was launched to test 11 Ethereum Improvement Proposals (EIPs).","link":null,"multiDateStart":null,"multiDateEnd":null,"continent":null,"country":null},{"id":"69d8d195-5bf9-4bfa-992f-3abc1dc361f2","date":null,"title":"Public Testnets Conducted","type":"MULTIDATE","description":"Public testnets for the Fusaka hard fork are planned to run through September and October 2025, preparing for the mainnet launch.","link":null,"multiDateStart":"2025-09-01","multiDateEnd":"2025-10-31","continent":null,"country":null},{"id":"9c94b3bc-5c71-4fba-b41d-f538bf55475c","date":"2025-08-01","title":"Glamsterdam Features Confirmed","type":"DEFAULT","description":"Proposed features for the subsequent Glamsterdam hard fork are set to be confirmed during the AllCoreDevs – Execution meeting.","link":null,"multiDateStart":null,"multiDateEnd":null,"continent":null,"country":null},{"id":"49fa5030-1b2b-495f-9f38-b65d2cf80f29","date":"2025-07-01","title":"SEC Discusses Compliant Token Standards","type":"DEFAULT","description":"The US SEC met with Ethereum-aligned organizations, including ERC-3643 Association and Chainlink Labs, to discuss compliant token standards.","link":null,"multiDateStart":null,"multiDateEnd":null,"continent":null,"country":null}],"user":{"id":"0x8af7a19a26d8fbc48defb35aefb15ec8c407f889"},"author":{"id":"0x8AF7a19a26d8FBC48dEfB35AEfb15Ec8c407f889"},"operator":{"id":"0x212Cb3F4aE6611054637f9f78F18fB628AD258bb"},"language":"en","version":1,"linkedWikis":{"blockchains":["ethereum"],"founders":[],"speakers":[]},"recentActivity":"{\"items\":[{\"id\":\"273dd12d-64fd-4d43-aaef-6a58a7e94c00\",\"title\":\"Ethereum Fusaka Upgrade\",\"description\":\"Fusaka is an upcoming Ethereum hard fork, tentatively scheduled for November 2025. It aims to enhance network scalability and efficiency through 11 Ethereum Imp...\",\"timestamp\":\"2025-11-15T03:44:03.920Z\",\"category\":\"Wiki Update\",\"status\":{\"icon\":\"RiGlobalLine\",\"label\":\"Wiki Updated\",\"iconClassName\":\"text-green-500\"},\"user\":{\"name\":\"0x8AF7a19a26d8FBC48dEfB35AEfb15Ec8c407f889\",\"address\":\"0x1E23b34d3106F0C1c74D17f2Cd0F65cdb039b138\"},\"button\":{\"label\":\"View Summary\",\"icon\":\"RiFileTextLine\"},\"summarySections\":[{\"title\":\"Title\",\"subtitle\":\"The capitalization of the title was changed.\",\"variant\":\"modified\",\"changeCount\":1,\"changes\":[\"Changed title from \\\"cryptocurrencies\\\" to \\\"Cryptocurrencies\\\".\"]},{\"title\":\"Introduction\",\"subtitle\":\"The introductory paragraph was updated with a confirmed launch date and new details.\",\"variant\":\"modified\",\"changeCount\":5,\"changes\":[\"Updated the tentative launch from 'November 2025' to a specific mainnet activation date of 'December 3, 2025'.\",\"Added explanation of the name 'Fusaka' as a portmanteau of 'Fulu' and 'Osaka'.\",\"Added the zebra as the developer-chosen mascot.\",\"Removed one embedded YouTube video.\",\"Updated the summary to reflect a more efficient Layer-2 data cost reduction goal.\"]},{\"title\":\"Overview\",\"subtitle\":\"The overview was updated to highlight the main features and goals.\",\"variant\":\"modified\",\"changeCount\":2,\"changes\":[\"Updated the objective to focus on 'backend enhancements rather than direct user-facing features'.\",\"Added specific mention of 'PeerDAS (Peer Data Availability Sampling)' as a central component.\"]},{\"title\":\"Technology\",\"subtitle\":\"The technology section was updated with more EIPs and a higher gas limit.\",\"variant\":\"modified\",\"changeCount\":3,\"changes\":[\"Increased the number of EIPs from 11 to 13.\",\"Specified EIP-7594 (PeerDAS) as the flagship feature.\",\"Updated the block gas limit increase from 'around 45 million' to 'approximately 60 million'.\"]},{\"title\":\"Key Ethereum Improvement Proposals (EIPs)\",\"subtitle\":\"The list of EIPs was expanded and descriptions were updated with more technical detail.\",\"variant\":\"modified\",\"changeCount\":4,\"changes\":[\"Increased the number of listed EIPs from 11 to 13.\",\"Added EIP-7642 (History Expiry).\",\"Added EIP-7910 (`eth_config` RPC Method).\",\"Updated descriptions for multiple EIPs (e.g., EIP-7825, EIP-7823, EIP-7935) with more specific parameters and goals.\"]},{\"title\":\"Development and Timeline\",\"subtitle\":\"Minor wording changes were made to the development timeline.\",\"variant\":\"modified\",\"changeCount\":1,\"changes\":[\"Updated text to reflect that development tests were successfully conducted, resolving previous concerns about the schedule.\"]},{\"title\":\"Testnet and Mainnet Launch\",\"subtitle\":\"The launch section was completely rewritten with confirmed dates and future plans.\",\"variant\":\"modified\",\"changeCount\":3,\"changes\":[\"Replaced tentative schedule with confirmed testnet activation dates for Holesky (October 1), Sepolia (October 14), and Hoodi (October 28).\",\"Announced the official mainnet activation date and time: December 3, 2025, at 21:49:11 UTC.\",\"Added details about two subsequent 'Blob Parameter Only' (BPO) forks scheduled for December 2025 and January 2026.\"]},{\"title\":\"Security Audit Contest\",\"subtitle\":\"The text describing the security audit contest prize pool was altered.\",\"variant\":\"modified\",\"changeCount\":1,\"changes\":[\"Modified text describing the prize pool, removing the total amount and the Gnosis contribution amount details.\"]},{\"title\":\"Impact on Stakeholders\",\"subtitle\":\"The section on user and developer impact was expanded and restructured.\",\"variant\":\"modified\",\"changeCount\":2,\"changes\":[\"The previous 'Impact on Users and Developers' section was renamed and expanded under the new 'Impact on Stakeholders' heading.\",\"Added details about benefits for developers (new opcodes, passkey support) and users (lower L2 fees, biometric wallets).\"]},{\"title\":\"Impact on Node Operators\",\"subtitle\":\"A new section was added to detail the upgrade's impact on node operators.\",\"variant\":\"added\",\"changeCount\":1,\"changes\":[\"Added a new section explaining the hardware and bandwidth impact on Full Nodes, Solo Stakers, and Large Validators.\"]},{\"title\":\"Future Upgrades\",\"subtitle\":\"Information about the next upgrade, Glamsterdam, was updated.\",\"variant\":\"modified\",\"changeCount\":1,\"changes\":[\"Added 'enshrined Proposer-Builder Separation (ePBS)' as a planned feature for the Glamsterdam upgrade.\"]},{\"title\":\"Economic Considerations\",\"subtitle\":\"The economic impact analysis was updated with new concerns and market data.\",\"variant\":\"modified\",\"changeCount\":3,\"changes\":[\"Updated the gas limit to 60 million and added related centralization concerns.\",\"Added analysis on the emergence of 'supernodes' due to PeerDAS.\",\"Added information about whale accumulation of ETH and the potential impact on ETH's deflationary mechanism.\"]},{\"title\":\"Events\",\"subtitle\":\"All events were removed from the wiki's timeline.\",\"variant\":\"removed\",\"changeCount\":6,\"changes\":[\"Removed event: 'Fusaka Hard Fork Scheduled'\",\"Removed event: 'EVM Object Format Excluded from Fusaka'\",\"Removed event: 'Devnet-3 Launched'\",\"Removed event: 'Public Testnets Conducted'\",\"Removed event: 'Glamsterdam Features Confirmed'\",\"Removed event: 'SEC Discusses Compliant Token Standards'\"]},{\"title\":\"References\",\"subtitle\":\"The list of references was significantly updated with new sources.\",\"variant\":\"modified\",\"changeCount\":2,\"changes\":[\"Added 11 new reference sources.\",\"Removed 5 old reference sources.\"]},{\"title\":\"Summary\",\"subtitle\":\"The summary was updated to reflect new, more specific information about the upgrade.\",\"variant\":\"modified\",\"changeCount\":1,\"changes\":[\"Updated the summary from a tentative description to one reflecting a confirmed launch date and more detailed objectives.\"]}]}]}"}