{"id":18009,"date":"2026-03-06T17:51:39","date_gmt":"2026-03-06T17:51:39","guid":{"rendered":"https:\/\/cryptoted.net\/index.php\/2026\/03\/06\/announcing-the-kiln-merge-testnet\/"},"modified":"2026-03-06T17:51:39","modified_gmt":"2026-03-06T17:51:39","slug":"announcing-the-kiln-merge-testnet","status":"publish","type":"post","link":"https:\/\/cryptoted.net\/index.php\/2026\/03\/06\/announcing-the-kiln-merge-testnet\/","title":{"rendered":"Announcing the Kiln Merge Testnet"},"content":{"rendered":"


\n
<\/p>\n

\n

The Kintsugi \ud83c\udf75 merge testnet<\/a>, launched late December, has been a valuable testing ground for The Merge. Through various test suites, multi-client devnets, shadow forks of Goerli, application deployments, and the community’s help #TestingTheMerge, we’ve arrived at a set of stable and robust protocol specifications. Now that clients have implemented these latest specs, a successor to Kintsugi, Kiln \ud83d\udd25\ud83e\uddf1, is being launched!<\/p>\n

Like the Ethereum mainnet, Kiln’s execution layer was launched under proof-of-work in parallel to a Beacon Chain running proof-of-stake. The Merge happened on Kiln on March 15, 2022. The network is now running entirely under proof-of-stake!<\/p>\n

Kiln is expected to be the last merge testnet created before existing public testnets are upgraded. Application & tooling developers, node operators, infrastructure providers and stakers are strongly encouraged to test on Kiln to ensure a smooth transition on existing public testnets.<\/p>\n

Kintsugi, the previous merge testnet, will be deprecated in the coming weeks.<\/p>\n

<\/g><\/svg><\/a>Using Kiln<\/h2>\n

<\/g><\/svg><\/a>Getting Started<\/h3>\n

The easiest way to get started using Kiln is to visit the network’s landing page<\/a>. There, you can add the network to your browser wallet, view block explorers, request funds from the faucet, and connect to a JSON RPC endpoint. If you’d like to be a validator on Kiln, the staking launchpad<\/a> also supports the network.<\/p>\n

<\/g><\/svg><\/a>Application & Tooling Developers<\/h3>\n

With Kiln going live, now is the time to ensure that your product works as expected through the proof-of-stake transition and in a post-merge context. As explained in a previous post<\/a>, The Merge will have only minimal impacts on a subset contracts deployed on Ethereum, none of which should be breaking. Additionally, the lion’s share of user API endpoints remain stable (that is, unless you are using PoW specific methods such as eth_getWork<\/span>).<\/p>\n

That said, most applications on Ethereum involve much more than on-chain contracts. Kiln is where you want to make sure that your front end code, tooling, deployment pipeline and other off-chain components work as intended. We strongly recommend that developers run through a full testing & deployment cycle on Kiln and report any issues with tools or dependencies to those projects’ maintainers. If you are unsure about where to open an issue, please use this repository<\/a>.<\/p>\n

<\/g><\/svg><\/a>Node Operators<\/h3>\n

Post-merge, an Ethereum full node will be the combination of a consensus layer client, which runs proof-of-stake on the Beacon Chain, and an execution layer client, which manages the user-state and runs the computations associated with transactions. These communicate over an authenticated port using a new set of JSON RPC methods, called the Engine API<\/a>.<\/p>\n

Node operators will thus need to run both a consensus and execution layer client in tandem. In other words, if you were already running a node on the Beacon Chain, you now need to also run an execution layer client. Similarly, if you were running a node on the current proof-of-work network, you will need to run a consensus layer client.<\/p>\n

You can find the latest Kiln-supported release of clients here<\/a>.<\/p>\n

It is worth emphasizing that each layer will maintain an independent set of peers and expose its own APIs. The Beacon<\/a> and JSON RPC<\/a> APIs will thus both continue working as expected.<\/p>\n

<\/g><\/svg><\/a>Stakers<\/h3>\n

As explained above, validators on the Beacon Chain will need to run an execution layer client after The Merge. Pre-merge, this was strongly recommended, but it was possible for validators to outsource these functions to third party providers. This was possible because the only data required on the execution layer were updates to the deposit contract.<\/p>\n

Post-merge, validators need to ensure that transactions in blocks they create and attest to are valid. To do so, an execution layer client is required. While this expands validators’ responsibilities, it also gives a validator who proposes a block the right to its associated transaction priority fees (which currently go to miners).<\/p>\n

While validator rewards accrue on the Beacon Chain and will require a subsequent upgrade to be withdrawn, transaction fees will continue to be paid, burned, and distributed on the execution layer. Validators can thus specify any Ethereum address as a receipient for transaction fees.<\/p>\n

Kiln is the perfect environment for existing stakers to familiarise themselves with the post-merge Ethereum context. We recommend trying to mirror your production setup on the network and ensuring that you work through any issues now.<\/p>\n

Again, the staking launchpad<\/a> provides a simple interface to get started. Note that as part of the renaming away from “eth2.0”<\/a>, the ethereum\/eth2.0-deposit-cli<\/a> repository will soon be renamed to ethereum\/staking-deposit-cli<\/span>.<\/p>\n

<\/g><\/svg><\/a>FAQ<\/h2>\n

<\/g><\/svg><\/a>wen merge?<\/h3>\n

A date for the Ethereum mainnet proof-of-stake transition has not<\/strong> been set as of the publication of this post. Any source claiming otherwise is likely to be a scam. Updates will be posted on this blog. Please stay safe!<\/p>\n

Assuming no issues are found with Kiln, once clients have finalized the details of their implementations, the existing Ethereum testnets (Goerli, Ropsten, etc.) will run through The Merge. Once these have successfully transitioned and stabilized, again, assuming no issues are found, a difficulty value<\/a> will be set for the mainnet transition. Only then will it be possible to estimate the exact date for The Merge.<\/p>\n

<\/g><\/svg><\/a>As an Ethereum user or Ether holder, is there anything I need to do?<\/h3>\n

No. If you want to try out Kiln, please do. We hope many community members will join us in #TestingTheMerge on Kiln.<\/p>\n

The Ethereum mainnet is not affected by this testnet. Subsequent announcements will be made on this blog prior to mainnet’s transition.<\/p>\n

<\/g><\/svg><\/a>As a miner, is there anything I need to do?<\/h3>\n

No. If you are mining on the Ethereum mainnet, you should be aware that after The Merge, the network will operate completely under proof-of-stake. At that point, mining will no longer be possible on the network.<\/p>\n

<\/g><\/svg><\/a>As a validator, can I withdraw my stake?<\/h3>\n

No. The Merge is the most complicated upgrade to Ethereum to date. In order to minimize risks of network disruptions, a minimal approach was taken which excluded any non-transition changes from this upgrade.<\/p>\n

Withdrawals from the Beacon Chain will likely be available as of the first upgrade after The Merge. Specifications for both the consensus<\/a> and execution<\/a> layers are in progress.<\/p>\n

<\/g><\/svg><\/a>Why Kiln?<\/h3>\n

The previous merge testnet, Kintsugi, was named after the Japanese art of breaking pottery and fixing it using gold, making it both stronger and more beautiful.<\/p>\n

In a similar vein, a Kiln is a high-temperature oven used to turn clay into hardened objects, such as pottery or bricks \ud83d\udd25\ud83e\uddf1.<\/p>\n<\/div>\n


\n
Source link <\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

The Kintsugi \ud83c\udf75 merge testnet, launched late December, has been a valuable testing ground for The Merge. Through various test suites, multi-client devnets, shadow forks of Goerli, application deployments, and the community’s help #TestingTheMerge, we’ve arrived at a set of stable and robust protocol specifications. Now that clients have implemented these latest specs, a successor […]<\/p>\n","protected":false},"author":6,"featured_media":18010,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"tdm_status":"","tdm_grid_status":"","footnotes":""},"categories":[24],"tags":[],"kronos_expire_date":[],"class_list":["post-18009","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-ethereum"],"_links":{"self":[{"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/posts\/18009","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/comments?post=18009"}],"version-history":[{"count":0,"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/posts\/18009\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/media\/18010"}],"wp:attachment":[{"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/media?parent=18009"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/categories?post=18009"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/tags?post=18009"},{"taxonomy":"kronos_expire_date","embeddable":true,"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/kronos_expire_date?post=18009"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}