Home Tags Posts tagged with "testnet"
Tag:

testnet

Ethereum & Smart Contracts

Ethereum Network Upgrade Glamsterdam Postponed on Hoodi Testnet

by Neng Nana
written by Neng Nana

The scheduled activation of the Glamsterdam network upgrade on the Hoodi testnet, originally slated for October 26, 2026, has been officially postponed. This critical development, announced by Ethereum core developers on October 22, 2026, includes the delay of a highly anticipated increase in the network’s gas limit to 200 million. As a result of this rescheduling, all previously published activation instructions and timelines for the Hoodi environment have been rendered obsolete. Ethereum stakeholders, particularly node operators and infrastructure providers, are advised to consult the latest developer documentation for updated guidance as the community recalibrates its testing roadmap.

This delay follows the successful, albeit preliminary, deployment of the Glamsterdam upgrade on the Sepolia testnet on October 6, 2026. The Glamsterdam initiative represents a significant leap forward in Ethereum’s long-term scaling strategy, focusing on high-impact architectural changes to the Layer 1 (L1) protocol. By integrating the Amsterdam execution layer improvements with the Gloas consensus layer upgrades, the Ethereum Foundation and the broader developer ecosystem aim to resolve systemic bottlenecks that have long constrained network throughput and efficiency.

The postponement of the Hoodi activation serves as a reminder of the rigorous, multi-stage testing process inherent to the Ethereum governance model. Before any upgrade reaches the mainnet, it must undergo a series of stress tests across various testnets—including Sepolia, Holesky, and Hoodi—to ensure stability, security, and backward compatibility. By prioritizing a cautious deployment schedule, developers can mitigate the risks of network disruption, ensuring that the complex interactions between proposer-builder separation and block-level access lists function as intended in a live, decentralized environment.

The Core Architecture of Glamsterdam

At the heart of the Glamsterdam upgrade lies a suite of Ethereum Improvement Proposals (EIPs) designed to fundamentally alter how blocks are produced and validated. One of the primary pillars of this upgrade is the implementation of Enshrined Proposer-Builder Separation (ePBS), as outlined in EIP-7732. Currently, Ethereum relies on external, off-protocol middleware to manage the separation of block proposers (validators) and block builders (specialized entities that construct blocks). By enshrining this process within the consensus protocol, Ethereum aims to decentralize the block-building market, reduce the influence of trusted third parties, and provide a more robust mechanism for the exchange of execution payloads.

Under the new ePBS framework, a proposer will commit to a builder’s proposed payload, and the protocol will handle the subsequent validation and payment. This transition is expected to introduce a more efficient separation of consensus and execution duties. By providing validators with additional time to perform execution-level verification, the protocol enhances the overall security of the chain while maintaining performance standards.

Complementing ePBS is the introduction of Block-Level Access Lists (BALs) via EIP-7928. This change is designed to improve the parallel processing capabilities of Ethereum clients. By enforcing that every block includes a comprehensive list of accessed accounts and storage locations, clients can read state data from disk and validate transactions concurrently. This shift is vital for supporting a higher gas limit, as it allows the network to handle significantly larger volumes of activity without placing an undue burden on node operators or sacrificing the network’s decentralization.

Economic and Technical Implications

The Glamsterdam upgrade also addresses the long-standing challenge of state growth and resource pricing. Through EIP-8037 and EIP-8038, the protocol introduces a more granular approach to gas accounting. These EIPs increase and separately meter the costs associated with state creation and state access, ensuring that the price of network resources more accurately reflects the actual cost of execution and storage. This adjustment is essential for maintaining the health of the Ethereum state database over the long term.

For application developers, these changes necessitate a proactive approach to testing. Contracts that rely on hardcoded gas limits or fixed gas stipends may face compatibility issues under the new pricing model. The Ethereum community has provided a dedicated repricing impact guide to assist developers in auditing their smart contracts and adjusting their gas estimation logic accordingly. Failure to update these systems could lead to transaction failures or increased costs once the upgrade is eventually deployed to the mainnet.

Beyond these major changes, Glamsterdam introduces several developer-friendly features, including ETH transfer logs, a new slot-number opcode, an increased maximum contract size, and a deterministic factory contract. These additions aim to simplify the development of complex decentralized applications (dApps) while expanding the creative possibilities for smart contract architects.

Chronology of the Upgrade

The path to Glamsterdam has been characterized by meticulous planning and cross-team coordination. The journey began with the release of initial specifications and the formation of working groups to refine the proposed changes.

  • September 17, 2026: The official announcement for the Glamsterdam testnet launch, outlining the goals for the upgrade.
  • October 6, 2026: Successful activation of the Glamsterdam upgrade on the Sepolia testnet, serving as the first major real-world test of the new architecture.
  • October 16, 2026: Initial announcement for the Hoodi testnet activation, establishing a schedule for a late October deployment.
  • October 22, 2026: Announcement of the postponement of the Hoodi activation, citing the need for further refinements before proceeding.

The delay of the Hoodi activation, while inconvenient for some, is viewed by industry observers as a positive sign of the ecosystem’s commitment to reliability. By opting to postpone the activation, the developer community demonstrates that security and protocol integrity take precedence over arbitrary deadlines.

Validator and Operator Responsibilities

Node operators and validators play a critical role in the success of any network upgrade. Unlike centralized systems where updates are pushed by a single authority, Ethereum upgrades require the active participation of thousands of independent operators. For the Glamsterdam upgrade, this means that every validator must update both their execution layer client and their consensus layer client to versions that explicitly support the new protocol rules.

Operators running staking infrastructure are particularly encouraged to review the new ePBS duties and ensure their client configurations are fully aligned with the requirements. Furthermore, those utilizing external builder services must coordinate with their providers to verify that their tools are prepared for the transition. The "client release tables" provided by the Ethereum Foundation remain the primary source of truth for identifying compatible software versions.

Broader Industry Context

The implications of Glamsterdam extend far beyond the technical details of the Ethereum protocol. As the network continues to scale, its ability to support higher throughput is essential for maintaining its position as the leading blockchain for decentralized finance (DeFi) and institutional applications. By optimizing gas usage and streamlining block validation, Ethereum is positioning itself to handle the next wave of global adoption.

Furthermore, the focus on enshrined proposer-builder separation reflects a broader trend toward trustless, protocol-level solutions. By removing the need for external, centralized middleware, Ethereum strengthens its decentralized ethos and improves its resilience against censorship and systemic failures.

As the community awaits a new date for the Hoodi activation and subsequent mainnet rollout, the focus remains on rigorous testing and transparent communication. The Ethereum Foundation has encouraged developers to use this extended timeline to conduct additional audits and simulations, ensuring that the eventual transition to the Glamsterdam ruleset is as seamless as possible.

While the mainnet activation date remains undetermined, stakeholders are encouraged to stay informed through official channels. For those who wish to follow the progress of the upgrade, the Ethereum Foundation periodically hosts technical workshops and Q&A sessions, providing insights into the challenges and triumphs of the upgrade process. The commitment of the core developer teams to this high-stakes endeavor underscores the vitality and maturity of the Ethereum ecosystem, as it continues to evolve into a more scalable, efficient, and secure global infrastructure.

0 comment
0 FacebookTwitterPinterestEmail
Ethereum & Smart Contracts

The Glamsterdam Upgrade on the Hoodi Testnet Has Been Officially Postponed Indefinitely

by Raul Delapena Setiawan
written by Raul Delapena Setiawan

The core development community behind the Hoodi testnet has officially announced the indefinite postponement of the highly anticipated Glamsterdam network upgrade. Originally scheduled for activation on October 26, 2026, at 17:42:48 UTC—corresponding to epoch 132,352—the upgrade has been pulled from the deployment roadmap to facilitate deeper technical investigation. This strategic retreat, finalized during All Core Developers Execution (ACDE) meeting #248, marks a critical pivot point in the testing phase of the protocol’s evolution, reflecting the cautious approach developers maintain when dealing with core infrastructure changes.

The decision to pause the deployment centers on the need to rigorously analyze the complex interactions between the proposed EIP-8037 (Ethereum Improvement Proposal) and existing mainnet smart contract architectures. While the Glamsterdam upgrade was intended to bring significant advancements to both the execution layer and the consensus layer—including a notable increase in the network’s gas limit to 200 million—developers have prioritized network stability and security over strict adherence to the previously established timeline.

A Chronology of the Glamsterdam Development Lifecycle

The trajectory of the Glamsterdam upgrade has been defined by a iterative, multi-phase testing process. The initial roadmap, which was formalized in mid-October 2026, outlined a clear path for the implementation of the Amsterdam execution layer and the Gloas consensus layer.

On October 16, 2026, the official announcement regarding the Hoodi testnet upgrade provided the community with the necessary parameters for the October 26 activation. At that time, the consensus among core developers was that the implementation was ready for public testing. However, the subsequent ten days involved intensive pre-deployment stress testing and simulation. During these final evaluations, engineers identified potential edge cases regarding how EIP-8037 might interact with legacy contracts currently deployed on the Ethereum mainnet.

By the time ACDE meeting #248 convened, it became apparent that the potential risks associated with the current configuration required a comprehensive review. The decision to remove the scheduled activation, rather than simply delaying it by a few days, indicates that the required changes to the EIP’s implementation or the network’s configuration may be substantial. As of now, there is no replacement activation epoch or timestamp assigned to the upgrade, and the development team has signaled that any future scheduling will only occur after a period of prolonged analysis and peer review.

Technical Implications and the 200M Gas Limit Adjustment

One of the most significant components of the Glamsterdam upgrade was the proposed adjustment to the Hoodi testnet’s gas limit, which would have been increased to 200 million units. This change was designed to facilitate higher throughput and provide developers with greater flexibility for complex, high-compute smart contracts.

The postponement of the upgrade effectively rolls back these configuration changes. It is important to note that this action does not alter the historical state of the Hoodi chain; the ledger remains intact, and no previous transactions have been reverted. Instead, the network has effectively "reset" its path forward, removing the hard-coded activation logic that would have triggered the changes at epoch 132,352.

For the developer community, this means that any applications or smart contracts currently being tested for compatibility with the 200 million gas limit must be adjusted. Testing environments configured to anticipate the October 26 transition will need to be re-synchronized to the current, stable state of the network. The removal of the gas-limit hike from the immediate roadmap serves as a reminder of the inherent volatility in experimental testnets, where the primary objective is to harden code against unforeseen failure modes before it ever reaches the production mainnet.

Obligations for Node and Validator Operators

The burden of this postponement falls primarily on node operators and validator stakeholders who maintain the infrastructure of the Hoodi testnet. Because the upgrade was originally scheduled as a hard fork—requiring mandatory updates to client software—the subsequent cancellation necessitates an immediate reversal of any preparation steps already taken.

Operators are being urged to exercise extreme caution. Relying on previously released client versions that were designed to trigger the Glamsterdam upgrade at the original epoch could lead to nodes falling out of sync with the network, or worse, becoming partitioned. The current directive from the core development team is clear: operators must review their execution and consensus layer clients and ensure they are running versions that explicitly acknowledge the removal of the October 26 activation.

Furthermore, validator operators are reminded that the client release tables circulated in the initial October 16 announcement are now obsolete. These tables were accurate at the time of publication but do not reflect the new reality of the postponed upgrade. Operators should look for updated release notes from their respective client teams (such as Geth, Nethermind, Lighthouse, or Prysm, among others) that confirm the removal of the Glamsterdam transition logic. For those utilizing external block-building infrastructure or MEV-boost relays, additional coordination with those service providers is essential to ensure that the entire validator stack remains aligned with the current, non-upgraded state of the network.

Strategic Analysis: Why Caution Prevails

The decision to delay Glamsterdam highlights a broader industry trend toward "safety-first" deployment strategies. In the wake of previous high-profile network disruptions in the broader blockchain ecosystem, core developer groups have become increasingly risk-averse.

The investigation into EIP-8037 is not merely a box-ticking exercise; it represents a fundamental concern regarding the long-term integrity of the Ethereum execution environment. EIP-8037, which aims to optimize specific cryptographic operations, has the potential to alter the way gas is consumed and how contracts interact with the underlying state. If the implementation is not perfectly aligned with existing gas-pricing models, it could lead to unexpected behavior in legacy decentralized finance (DeFi) applications. By postponing the upgrade, the developers are providing the necessary "breathing room" to simulate these interactions in a controlled environment, ensuring that when the upgrade does eventually occur, it does so with a high degree of confidence.

This delay also provides a lesson in the importance of testnet agility. The Hoodi testnet is, by design, the proving ground for these advancements. The fact that the process worked as intended—identifying a risk and halting the deployment before it reached the mainnet—should be viewed as a success of the development process rather than a failure of the timeline.

Broader Context and Future Outlook

It is critical to distinguish between the Hoodi testnet and the Ethereum mainnet. This announcement is specific to Hoodi; it does not set a date for, or provide any information regarding, a potential Glamsterdam activation on the Ethereum mainnet. For the average user or ETH holder, this news carries no immediate impact, nor does it require any action.

The lack of a defined replacement date for the Hoodi upgrade is perhaps the most telling detail of the current situation. It suggests that the core development team is not working toward a fixed calendar deadline, but rather a set of technical milestones. The timeline will be driven by the results of the ongoing investigations into EIP-8037.

Moving forward, the community should expect a period of quiet, during which developers will likely publish technical reports or Github issue updates detailing the findings from the investigation. Once the concerns surrounding the EIP are resolved, a new, revised configuration will be proposed, tested in isolation, and eventually re-introduced to the Hoodi testnet.

For the ecosystem at large, this episode serves as a reminder of the complexity involved in maintaining a decentralized, global financial network. While users often crave rapid innovation and new features, the robustness of the network relies on the ability of the development community to identify potential pitfalls and hit the "pause" button when necessary. As the industry matures, these moments of collective reflection and caution are becoming the hallmark of a resilient, secure, and sustainable infrastructure. Developers and stakeholders alike are advised to monitor the official developer communications channels, such as GitHub repositories and the ACDE meeting minutes, for the next update regarding the rescheduled Glamsterdam deployment.

0 comment
0 FacebookTwitterPinterestEmail
Altcoins & Token Projects

Coinbase Expands Ecosystem Integration with Sui Staking Launch and Hashi Testnet Deployment Amid Significant SEC Legal Settlement

by Ammar Sabilarrohman
written by Ammar Sabilarrohman

Coinbase, the leading United States-based cryptocurrency exchange, has officially announced the integration of staking support for Sui (SUI), the native token of the high-performance Layer 1 blockchain. This strategic expansion allows eligible Coinbase customers to earn rewards directly through the platform’s interface, marking a significant milestone in the exchange’s effort to diversify its staking-as-a-service (SaaS) offerings. The announcement, made on Wednesday, July 22, coincides with a pivotal development within the Sui ecosystem: the launch of the Hashi testnet. This new infrastructure is designed specifically to serve developers and institutional partners focused on Bitcoin-centric financial applications, providing a secure environment to test key features before a full migration to the Sui mainnet.

The rollout of SUI staking on Coinbase represents a bridge between retail accessibility and sophisticated blockchain infrastructure. By lowering the barrier to entry for staking, Coinbase aims to increase network participation and liquidity within the Sui ecosystem. This move comes at a time of heightened activity for Sui, which has positioned itself as a competitor to established networks like Ethereum and Solana by utilizing the Move programming language and an object-centric data model.

Technical Specifications and Reward Structure of Coinbase Sui Staking

The staking program introduced by Coinbase is designed to be accessible while maintaining the technical requirements of the Sui network. According to the exchange, users can begin staking with a minimum balance of just 1 SUI. This low threshold is a departure from the more stringent requirements often found in direct on-chain staking, where hardware costs and minimum delegations can be prohibitive for casual investors.

Rewards for SUI staking on Coinbase are currently estimated to range between 1.4% and 3.3% per annum. These yields are dynamic and subject to change based on network inflation rates, the total amount of SUI staked across the entire network, and the performance of the validators. A key feature of the Coinbase integration is the frequency of payouts; rewards are distributed daily at the conclusion of every 24-hour network epoch. Furthermore, the exchange has implemented an auto-compounding mechanism, whereby earned rewards are automatically added back into the user’s staked balance, allowing for the potential of exponential growth over time without manual intervention.

Coinbase emphasized the user experience in its announcement, stating that the integration allows for "less time spent searching, and more time spent earning." By handling the technical complexities of validator selection and node maintenance, Coinbase provides a "one-click" solution for users seeking yield on their digital assets. However, the exchange also issued a caveat regarding jurisdictional availability, noting that staking services are not available in all regions due to varying local regulations. This is particularly relevant in the United States, where the Securities and Exchange Commission (SEC) has previously scrutinized staking-as-a-service products offered by centralized exchanges.

The Hashi Testnet: A New Frontier for Bitcoin Infrastructure on Sui

Parallel to the staking announcement, the Sui ecosystem celebrated the launch of the Hashi testnet. Hashi is a specialized platform designed to facilitate the development of Bitcoin-focused financial applications. Its primary goal is to extend the utility of Bitcoin beyond its traditional role as a passive store of value, transforming it into a productive asset within the decentralized finance (DeFi) space.

The Hashi testnet introduces the "Guardian Layer," a sophisticated security protocol that enhances the management and control of Bitcoin collateral. By combining Sui’s high-throughput architecture with the Guardian Layer, Hashi provides a framework for transparent, programmable, and secure on-chain finance. This infrastructure is particularly targeted at institutional players, including financial institutions, custodians, and developers who require robust security measures before deploying capital.

More than 25 partners within the Sui ecosystem have already committed to building on the Hashi testnet. These partners are exploring a variety of use cases, such as Bitcoin-backed lending, credit products, and complex yield strategies. By leveraging Sui’s ability to process transactions in parallel and its low-latency finality, Hashi aims to solve the scalability issues that have traditionally hindered Bitcoin’s integration into high-frequency DeFi environments.

Chronology of Events: A Mid-Year Pivot for Coinbase and Sui

The events of July 22 represent the culmination of several months of development and legal maneuvering. To understand the significance of these announcements, it is necessary to look at the timeline leading up to this date:

  • May 2023: The Sui Mainnet officially launches, backed by Mysten Labs and a team of former Meta (Facebook) engineers who worked on the Diem project.
  • Q1 2024: Coinbase continues its aggressive expansion of staking services despite regulatory pressure, adding support for various emerging Layer 1 tokens.
  • Early July 2024: Sui developers signal the upcoming release of Bitcoin-interoperability layers, sparking interest among institutional "BTCFi" (Bitcoin DeFi) proponents.
  • July 22, 2024 (Morning): Coinbase and the SEC reach a settlement in a long-standing Freedom of Information Act (FOIA) lawsuit, with the SEC agreeing to pay $150,000 to the exchange.
  • July 22, 2024 (Afternoon): Coinbase officially announces SUI staking support. Simultaneously, the Sui Foundation and its partners unveil the Hashi testnet.
  • July 22, 2024 (Market Close): Despite the positive news, Coinbase (COIN) stock experiences a 3.67% decline, closing at $169.40, reflecting broader market volatility and investor caution.

Legal Context: The SEC FOIA Settlement and Regulatory Clarity

The timing of the Sui staking launch is particularly noteworthy as it occurred the same day Coinbase concluded a significant legal battle with the U.S. Securities and Exchange Commission. The lawsuit, centered on the Freedom of Information Act, was initiated by Coinbase to compel the SEC to release documents regarding its internal deliberations on the classification of digital assets.

The SEC’s agreement to pay $150,000 to Coinbase to settle the case is viewed by many legal analysts as a symbolic victory for the exchange. While the settlement does not resolve the larger ongoing litigation between the SEC and Coinbase regarding the exchange’s alleged operation as an unregistered broker and clearinghouse, it demonstrates Coinbase’s willingness to use the judicial system to challenge the regulator’s "regulation by enforcement" approach.

This legal backdrop is critical for the staking industry. The SEC has previously targeted staking services, most notably reaching a $30 million settlement with Kraken in 2023, which forced the latter to shut down its staking program for U.S. users. Coinbase has remained defiant, arguing that its staking services do not constitute investment contracts under the Howey Test. The launch of SUI staking suggests that Coinbase remains confident in its legal position and is committed to expanding its product suite while the broader regulatory framework remains in flux.

Market Analysis: COIN Stock Performance and Investor Sentiment

Despite the dual positive catalysts of a new product launch and a legal settlement, Coinbase Global Inc. (COIN) saw its share price retreat during the Wednesday trading session. The stock slumped 3.67% to $169.40. Financial analysts attribute this disconnect to several factors:

  1. Macroeconomic Pressures: The broader tech sector and crypto-correlated stocks have faced headwinds due to uncertainty regarding interest rate cuts and inflationary data.
  2. Profit Taking: Following a period of relative strength, some investors may have used the "news" of the SUI staking and SEC settlement as an opportunity to realize gains.
  3. Bitcoin Volatility: As the primary driver of market sentiment, fluctuations in the price of Bitcoin often overshadow asset-specific news for exchange stocks like Coinbase.
  4. Regulatory Overhang: While the FOIA settlement is a win, the primary SEC lawsuit against Coinbase remains a significant risk factor that continues to weigh on the company’s valuation.

However, from a long-term perspective, the addition of SUI staking is expected to contribute to Coinbase’s non-transactional revenue. Staking rewards and custodial fees provide a more stable income stream compared to the highly volatile trading commissions that depend on retail market volume.

Institutional Implications: The Rise of BTCFi on Sui

The launch of the Hashi testnet is a clear signal that the Sui network is positioning itself as a hub for institutional Bitcoin activity. Traditionally, Bitcoin has been difficult to use in DeFi because its scripting language is limited compared to Ethereum’s Solidity or Sui’s Move. Previous attempts to bring Bitcoin to other chains, such as Wrapped Bitcoin (WBTC), rely on centralized or semi-centralized custodians.

The Hashi approach, utilizing a Guardian Layer, seeks to provide a more decentralized and secure alternative. By allowing institutions to use their Bitcoin as collateral for lending and credit on the Sui network, Hashi opens up a multi-billion dollar market. For Sui, this is a strategic move to capture "sticky" institutional liquidity. For Bitcoin holders, it represents a way to generate yield on the world’s largest digital asset without selling it.

Industry experts suggest that if the Hashi testnet proves successful, it could lead to a wave of new financial products. "The goal is to move from Bitcoin as digital gold to Bitcoin as a foundational layer for global finance," noted one developer involved in the testnet. "Sui’s architecture is uniquely suited for this because it can handle the throughput required for institutional-grade applications."

Conclusion and Future Outlook

The integration of Sui staking on Coinbase and the simultaneous launch of the Hashi testnet represent a maturing of the cryptocurrency ecosystem. For retail users, the ease of earning rewards on SUI through a trusted platform like Coinbase enhances the utility of the asset. For the Sui network, the partnership with a major exchange provides a significant boost in visibility and decentralization.

As the Hashi testnet progresses toward a mainnet launch, the industry will be watching closely to see if Sui can truly bridge the gap between Bitcoin’s massive liquidity and the innovative potential of modern smart contract platforms. Meanwhile, Coinbase continues to navigate a complex regulatory landscape, balancing its role as a compliant financial institution with its mission to advance the frontiers of the crypto economy.

The $150,000 settlement with the SEC may be a small sum in the context of Coinbase’s multi-billion dollar balance sheet, but it serves as a reminder of the ongoing friction between the crypto industry and federal regulators. As the 2024 election cycle approaches and the conversation around crypto regulation intensifies, the developments surrounding Coinbase and Sui will likely serve as a barometer for the health and direction of the broader digital asset market. For now, the focus remains on building robust infrastructure and providing users with the tools to participate in the next generation of decentralized finance.

0 comment
0 FacebookTwitterPinterestEmail