• Reminder: the Gray Glacier upgrade is scheduled for block 15,050,000, expected June 29, 2022
• The Kiln Merge testnet, launched earlier this year, will be shut down shortly after the Ethereum mainnet’s transition to proof-of-stake.
• Ropsten, Ethereum’s longest-lived proof-of-work testnet, has transitionned to proof-of-stake. It will be shut down in Q4 2022.
• Rinkeby, a geth-based proof-of-authority testnet, will not transition to proof-of-stake and will be shut down in Q2/Q3 2023.
• Users and developers are encouraged to migrate ASAP to Goerli or Sepolia to test Ethereum in a post-merge context. After The Merge, Rinkeby will not be a suitable testing environment for the Ethereum mainnet. Unplanned mainnet upgrades may no longer be applied to deprecated testnets.

Ethereum has many testnets for users and developers to test things on before interacting with mainnet. These are effectively copies of the Ethereum mainnet on which Ether and other tokens have no value. They allow application, tooling, infrastructure and protocol developers to deploy changes to their products (or the protocol itself!) in a low stakes environment, before moving to mainnet.

That said, because testnets are full-featured blockchains, their history and state grow over time. This eventually makes them harder to run nodes on and to maintain. For this reason, some testnets are periodically sunsetted. This happened last year with the Pyrmont Beacon Chain testnet and more recently with the Kovan execution layer testnet.

With The Merge approaching, client developers have decided to deprecate more testnets in order to focus their efforts on properly maintaining two of them over the long-term: Goerli and Sepolia.

The Kiln, Rinkeby and Ropsten testnets are now being deprecated.

Testnet Shutdown Timeline

While these three testnets are now considered deprecated, users and developers still have time to plan their migration before they are completely shut down. Kiln, Ropsten and Rinkeby will be shut down according to the schedule below.

Kiln: After Mainnet Merge

The Kiln testnet, launched in 2022 to provide a post-merge testing environment, will be shut down shortly after the Ethereum mainnet’s transition to proof-of-stake, expected in the second half of 2022.

Developers should not use Kiln as a long-lasting testing environment. It is expected to be the first testnet to be shut down after The Merge happens on the Ethereum mainnet.

Ropsten: Q4 2022

The Ropsten testnet, which ran through The Merge on June 8, 2022, will be shut down in Q4 2022.

Developers who currently use Ropsten as a staging/testing environment should migrate to Goerli or Sepolia.

Rinkeby: Q2/Q3 2023

The Rinkeby testnet will not run through The Merge. It is being replaced by Sepolia, and will be shut down roughly one year after Sepolia has transitioned to proof-of-stake, around Q2/Q3 2023.

Once the Ethereum mainnet transitions to proof-of-stake, Rinkeby will no longer be an accurate staging environment for mainnet. A list of changes introduced by The Merge that application developers should be aware of is available here. Again, note that these changes will not be deployed to Rinkeby.

Developers who currently use Rinkeby as a staging/testing environment should prioritize migrating to Goerli or Sepolia, and projects who are affected by Ethereum’s transition to proof-of-stake should aim to do so as soon as possible.

Goerli & Sepolia

The two testnets which client developers will maintain post-merge are Goerli and Sepolia.

The Goerli network will merge with the Prater Beacon Chain testnet. A new Beacon Chain has been created to transition Sepolia to proof-of-stake.

Goerli’s Beacon Chain will remain open for users wanting to run a testnet validator. Sepolia will operate with a permissioned validator set, similarly to how some testnets work today. Stakers wanting to test protocol upgrades before they are deployed to mainnet should therefore use Goerli.

Goerli also has a strong community and a lot of existing infrastructure supporting it. Its state is the closest to mainnet, which can be useful for testing smart contract interactions.

Sepolia, on the other hand, is fairly new, meaning its state and history are both quite small. This means the network is quick to sync to and that running a node on it requires less storage. This is useful for users who want to quickly spin up a node and interact with the network directly.

Summary

In short, Kiln, Ropsten and Rinkeby are now deprecated. While Kiln and Ropsten have already transitioned to proof-of-stake, Rinkeby will not run through this upgrade.

After The Merge happens on mainnet, Kiln will be sunset. Then, by the end of the year, Ropsten will be as well. Roughly one year after Sepolia has transitioned to proof-of-stake, around Q2/Q3 2023, Rinkeby will be turned off.

Two testnets, Goerli and Sepolia, will be maintained going forward. Goerli is recommended for stakers to test protocol upgrades and developers who want to interact with a large existing state. Sepolia is recommended for users and developers who want a lighter weight chain to sync to and interact with.

To everyone who has helped run, maintain or support these networks, thank you!

Header photo by Karl Hedin.

Microsoft has published guidance for users of Microsoft Publisher as it will no longer be supported after October 2026 and removed from Microsoft 365.

Specifically, the products to be deprecated are Publisher for Microsoft 365, Publisher 2021, 2019, 2016, 2013, 2010, and 2007, and also 2010 and 2013 Developer.

Microsoft Publisher is an Office application designed for layout-focused projects and visually rich print materials. Compared to Word, it provides better layout control, an extensive set of pre-designed templates, and convenient drag-and-drop functionality.

The product is popular among non-professional designers in education (schools), churches, hobbyists/home users, nonprofit and community organizations, and small businesses.

Microsoft had announced plans to sunset Publisher since last year, but as the time approaches, the tech giant has now shared additional information on what impacted users can do not to lose their projects.

The main recommendation is to convert existing Publisher files (.pub) to PDF or Word formats, depending on how much further editing they need.

To do this, open the said files, go to ‘File’ > ‘Save as’, and select the file type (DOCX or PDF) and location to save it.

For large sets of files where doing this process individually can be cumbersome, Microsoft recommends automating the process by means of a macro.

The tech company acknowledges the existence of third-party conversion tools but notes that these aren’t officially supported. Microsoft also warns about their varying quality and consistency.

Microsoft recommends that impacted users replace Publisher with Word or PowerPoint, although these solutions cannot accommodate some use cases at the same level.

The company has shared the following information on how you can achieve a certain task in another Microsoft Office application:

For more advanced and specialized projects that Microsoft Office applications cannot support, users can also try third-party cools like Canva (subscription), Adobe InDesign (subscription), and Affinity Publisher (one-time payment).

The updated FAQ page in the Publisher’s announcement explains that those who wish to continue using the product and have the ‘Perpetual’ version may do so indefinitely outside of Microsoft 365. 

However, there will be no security updates, new features, or technical support after October 2026.