Chrysalis update — December 4Published weekly as a summary of Chrysalis phase 2 updates. Please click here if you want to read the full monthly dev status update.IOTA 1.5IOTA 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.This week’s updates and statusBeeThis week, the Bee team performed a special live session where they demonstrated running the Bee node on a private Chrysalis testnet, connecting to Hornet nodes and synchronizing.The team is fixing and updating pieces across network, ledger state, tangle storage, and API implementations.The new API is close to being fully implemented, with a few bits of the message sending API ongoing. Changes to the API in both Bee and Hornet are still expected throughout the testing phase of Chrysalis.Moving crates to the main Bee repository is ongoing.HornetThe Delta snapshots functionality has been merged.Added bech32 encoding to the REST API.Progressing on configuration and set up of the public Chrysalis testnet.Iota.rs and wallet.rsOur Rust implementation of standard client library and wallet functionalitiesFixing outstanding issues on the wallet.rs side, for example a timeout when sending tokens with neon bindings.Wallet.rs is undergoing internal testing.Neon bindings for iota.rs have been merged.Adjusting the libs to breaking changes in node API.Crypto.rs and StrongholdCrypto.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.bip32 path and slip10 derivation are being vetted within stronghold, will promote to crypto.rs soon.Audit for crypto.rs is outstanding.The top-level client interface in Stronghold is finished and is now being adapted to the needs of wallet.rsCrypto.rs assets are integrated where available.Performance gains in Stronghold snapshotting have been identified.The aim is to finish everything required for the wallet integration by the end of this week.FireflyChrysalis phase 2 will come with a new wallet implementation that replaces Trinity.We have published a post to start educating people and making them aware of our upcoming next-generation wallet, Firefly, and its future.Work continues on hooking all the components and dependencies together, fixing issues as they are found in underlying libraries, and more.The current plan is to launch the first rounds of alpha testing in the upcoming weeks, with an audit starting in early January.TestnetWe 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 — done.New faucet — close to being done, will be deployed soon,Complete infrastructure, which we have been working on with the Hornet team.Node software stabilized — breaking changes will still be part of the testnet.Wallet.rs with JS bindings — doneIota.rs with JS bindings — doneOnce all the pieces have come together, we will publish them as the first version of our public Chrysalis testnet, stay tuned!AuditsA 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/iotatokenChrysalis update — December 4 was originally published in IOTA on Medium, where people are continuing the conversation by highlighting and responding to this story.