Iota news chrysalis7/24/2023 One of the important parts of Chrysalis Phase 2 will be having a testnet with the initial changes live prior to the release. All of this is included in our planning process for Chrysalis. Some will require more effort than others, some only need their dependencies - specific libraries - to be adjusted. IOTA Product UpdatesĪll the other products that we are developing at the Foundation, including IOTA Streams, IOTA Access, or Chronicle, will be adjusted for Chrysalis Phase 2. This will enable a new level of security for wallet users. Stronghold will be a strong basis for the new wallet. With desktop having a higher priority in the development process. The new wallet will be built for both desktop and mobile. This includes the UX, all the implementations, and even a new wallet library to support all the underlying functionality through the new Rust library. The new wallet is being rebuilt from the ground up. The wallet team has been working on the new wallet to replace Trinity for some time now. Some will remain native, like C or Go.Ĭlient libraries will come with a high-level API that will make integrating and maintaining solutions on top of IOTA simpler than before.Ĭlient libraries will also completely replace Hub, our wallet management solution for exchanges and custodians. Many of the libraries will be covered with bindings to our core Rust library. An extendable address format for different types of signature schemes based on bech32Īll the client libraries need to change significantly for Chrysalis Phase 2.Proof of work changes to reflect different message size.A new message object, this is the object that nodes gossip around the network and contains different payloads.Below is a brief rundown of some of those changes we currently have in the works: However, the changes to the node software side are happening on many fronts. This work led us to adjust some of the types in the proposed RFCs. The Bee and Hornet teams are already busy planning for and implementing the changed transaction layout, for example. The development of Chrysalis Phase 2 changes in the node software is ongoing now. Most recently, we added an initial version of the new node API into the proposals. Either directly or by providing feedback, that’s why we also publish the changes as RFCs. It is important for everyone to be involved in designing the changes. The development itself is a significant team effort as the protocol changes every part of the ecosystem. Atomic transactions - Move from the current Bundle construct and use of simpler atomic transactions instead.Binary transaction layout - validation, IO and other processing working on binary data without the need to have many binary-ternary conversions as in the current node software.UTXO - A better fund and state management approach.Ed25519 support - a more commonly used signature scheme and support for reusable addresses.To reiterate, Chrysalis Phase 2 includes: From the node software, client libraries, products like Streams and Chronicle, to anything that takes any kind of dependency on those, as well as wallet users. The components of Chrysalis Phase 2 affect every part of the IOTA ecosystem. Developing Chrysalis Phase 2Ĭhrysalis Phase 2 will be the biggest network update we have ever performed at the IOTA Foundation. Depending on the progress of testing, we would like to release Chrysalis Phase 2 later this year. Currently, our plan is to start testing the first version of Chrysalis node software in October or November. You can read more about the release strategy for Chrysalis here. The IOTA Foundation is now actively working on the development of Chrysalis Phase 2 components. Since then, the network has been running with fast confirmation times and sustaining high TPS. The Chrysalis Phase 1 components have been deployed on the IOTA mainnet a few weeks back. You can read more about the strategy for releasing Chrysalis here. The first phase of IOTA 1.5 (also known as Chrysalis) - the mainnet’s intermediate stage before Coordicide - is complete.
0 Comments
Leave a Reply. |