Chrysalis Weekly Status Update — November 27
Published weekly as a summary of Chrysalis phase 2 updates. Please click here if you want to ready the full monthly dev status update.
IOTA 1.5 (also known as Chrysalis) is the mainnet’s intermediate stage before Coordicide is complete. You can read more about the strategy for releasing Chrysalis here.
The Chrysalis phase 1 components were deployed to mainnet in August. The engineering team is now working on Chrysalis phase 2.
- Last week, the Bee team successfully connected a Bee node to Hornet nodes on the Chrysalis testnet. This allowed the team to successfully test synchronization between the nodes.
- The team is updating the network protocol, with tweaks on the ledger and snapshot implementation.
- An endpoint for sending messages remains to be implemented from the new API.
- Moving crates to the main Bee repository.
- The upcoming focus will be largely on documentation, testing, and auditing the necessary crates.
- Progressing on refactoring gossip, tangle, and snapshot plug-ins.
- Reset the internal Chrysalis testnet on the addition of network IDs to the message layout.
- MQTT websocket implementation added.
- Added delta snapshot import and export functionality.
Our Rust implementation of standard client library and wallet functionalities.
- Reattachment, promotion and retry logic has been merged.
- Node synchronization process is now working.
- The first integration with Hornet’s MQTT interface has been merged.
- Python bindings for iota.rs are well in progress. Sending messages and checking balance works, other APIs in progress.
- There will be two documented ways to handle seeds in the library, one using Stronghold, the other using dotenv.
- Wallet.rs node.js bindings via Neon have been merged.
Crypto.rs is a crate for all cryptographic algorithms used by many of the projects at IF. Stronghold is a secure software implementation for safe digital secrets isolation.
- Introduction of changelog, release management and polyglot artifact publishing workflow via covector.
- Cross-platform introduction of secure zone.
- Revised client, top level actor, and libp2p.
- Participation in cross-project bindings working-group.
- Collaboration with riker.rs project (the Actor Model used by Stronghold).
- Top-level library for Stronghold is in progress, this will be used as an entry point to Stronghold for all consuming applications (and bindings).
- Main focus is to get the wallet and its integration with the libraries in working order.
Chrysalis phase 2 will come with a new wallet implementation, named Firefly, that replaces Trinity.
- Work continues on hooking up wallet.rs to the wallet application.
- The goal of this week is to complete the integration of the UI. This will allow us to have the first wallet alpha available for the community in the upcoming weeks.
- Work on the new faucet, which will be powered by wallet.rs using Neon bindings is in progress. Front-end has been designed, integration will follow.
We are now in a phase of testing Chrysalis functionality on a private testnet. We are working on bringing all the necessary bits and pieces for making the testnet public together. This includes
- the CLI wallet — close to being finished,
- new faucet,
- complete infrastructure, which we are now reworking, set-up,
- node software stabilized — breaking changes will still be part of the testnet,
- wallet.rs with JS bindings,
- iota.rs with JS bindings.
The current aim is to have the necessary tooling ready by the end of next week.
A large part of the Chrysalis phase 2 effort is auditing the new functionality. We have booked the relevant availability with multiple external auditing firms for the upcoming weeks to start auditing the different components as soon as possible.
As always, we welcome everyone to stop by on Discord— every project mentioned here has a channel (or more) for discussion with the devs!
Follow us on Twitter to keep track of all the latest news: https://twitter.com/iotatoken