Following the conclusion of the Amphora merge workshop, development teams have been diligently working on the implementation of the most recent merge specifications and conducting tests on development networks.
After completing four temporary devnets, Kintsugi 🍵, a more enduring public testnet, is now operational!
While client development and user experience continue to be enhanced, we encourage community members to start using Kintsugi in order to acclimate themselves to Ethereum in a post-merge environment. For application developers, as mentioned earlier, not much will be altered. Tools that interact solely with either the consensus or execution layer remain largely unchanged. Infrastructure reliant on both layers will likely require adjustments to accommodate The Merge.
We suggest that most projects initiate testing and prototyping on Kintsugi promptly to uncover any possible issues. This approach will allow modifications to be integrated more effortlessly into upcoming client and specification iterations.
Utilizing Kintsugi
Visit the Kintsugi landing page for details on interacting with the Kintsugi network. You will find network configurations, a faucet, a block explorer, and a JSON-RPC endpoint, along with documentation that has been updated to reflect supported combinations of consensus and execution layer clients.
As a reminder, in the post-merge landscape, a complete Ethereum client consists of both a Beacon / Consensus node and an Execution engine (managed by an existing “Eth1” client). Each layer maintains independent API endpoints and peer connections to fulfill their respective functions. For a comprehensive overview of Ethereum’s architecture after the merge, refer to this post.
Assistance & Feedback
The EthStaker community is ready to offer support for Kintsugi. If you have inquiries, experience issues, or need further explanations, they are willing to help in the #testingthemerge🐼 channel of their Discord server.
With the introduction of Kintsugi, we hope the community participates in #TestingTheMerge. Check out this compilation of test scenarios for suggestions on how to elevate your testing efforts.
If you discover bugs or concerns regarding the specifications, the most suitable location to address these is in the #merge-general channel of the Ethereum R&D Discord server. If Discord isn’t your preference, alternative methods to report such matters include the specification repositories (consensus, execution, APIs), and Ethereum Magicians ✨.
Upcoming Steps
The Kintsugi testnet offers the community a chance to explore post-merge Ethereum and start identifying any issues. Once feedback is integrated into the client software and specifications, a final series of testnets will be released. Concurrently, testing initiatives will continue to escalate.
Subsequently, existing long-term testnets will undergo The Merge. Following their upgrade and stabilization, the next step will be the transition of Ethereum mainnet to proof of stake 🎊.
For those keen to track the developments at a more detailed level, a mainnet readiness checklist is publicly accessible and regularly refreshed.
See you on Kintsugi 🍵!
