Announcement of Kintsugi Merge Testnet
Since returning from Amphora Merge WorkshopThe client team has been hard at work implementing the latest version of the merge spec and testing it on devnet.
Kintsugi after 4 temporary devnets šµ Long-lived public testnetCurrently broadcasting!
Client development and UX continue to improve, but we encourage the community to use Kintsugi to familiarize themselves with Ethereum post-merge. For application developers: As previously explained, not much will change. Tools that only interact with the consensus or execution layer are also not significantly affected. Infrastructure that relies on both layers will most likely need to be adapted to support The Merge.
For most projects, it’s a good idea to start testing and prototyping on Kintsugi to ensure any potential problems surface soon. This way, changes can be more easily incorporated into future client and specification versions.
Using Kintsugi
Please confirm Kintsugi landing page For information about interacting with the Kintsugi network, you can find Network Settings, Faucets, Block Explorer, and JSON-RPC Endpoints, with documentation updated to reflect the supported consensus <> execution layer client combinations.
After the merge, the full Ethereum client will consist of a beacon/consensus node and an execution engine (handled by the existing āEth1ā client). Both layers maintain independent API endpoints and peer connections to handle their respective roles. For a complete overview of Ethereum’s post-merge architecture, see: this post.
Support and Feedback
The EthStaker community can provide Kintsugi support. If you have questions, encounter an error, or need clarification, we’ll be happy to help. #testingthemergeš¼ their channel discord server.
With the launch of Kintsugi, we hope our community will #TestingTheMerge. Check out this list test scenario Get ideas on how to take your testing to the next level.
If you identify a bug or issue with the specification, the best place to raise it is #Merge-General channel Ethereum R&D Discord Server. If you don’t want to use Discord, another place to raise these issues is the spec repository (consensus, execution, apis), and Ethereum Magician āØ.
next stage
The Kintsugi testnet provides the community with the opportunity to experiment with Ethereum and identify issues post-merge. Once feedback is incorporated into the client software and specifications, the final testnet series will be released. At the same time, testing efforts will continue to increase.
After that, the existing long-term testnet will run through The Merge. Once this is upgraded and stabilized, the next step is for the Ethereum mainnet to transition to Proof-of-Stakeš.
For those who want to see progress at a more detailed level: Mainnet preparation checklist It is publicly available and updated regularly.
See you at Kintsugišµ!