An internal process caused a new signing key to be released on the COO before nodes were able to validate the new signature set provided in milestones. For this reason, node configurations have to be extended to provide the missing key to validate newly emitted milestones #IOTA
Node maintainers should apply configuration changes as described here gist.github.com/rajivshah3/0… to their Hornet version (latest release is Hornet v1.0.3)
The genesis snapshot for the #Chrysalis network has been prepared and can be validated using the following instructions: github.com/iotaledger/hornet…
We would like to invite everyone to participate in the Chrysalis snapshot validation process. The process will take place on April 28. You can find the pre-requisites and instructions, with further info coming on April 28, here:
chrysalis.docs.iota.org/guid…
Chrysalis will change all of the developer tools and node software in the #IOTA ecosystem. We are working on a lot of new documentation for all of this! You can find some the #documentation already available for #Chrysalis at chrysalis.docs.iota.org/
The #Chrysalis testnet was successfully updated! The update includes changes to messages to dynamically allow referencing up to 8 parents, and changes to the Dust protection mechanism. Join the #chrysalis-testnet channel on Discord for all the details: discord.iota.org/
We will be performing maintenance of Mainnet infrastructure tomorrow at 9 AM UTC. Please expect a short period of time with no milestones.
We have released a new version of Hornet. Please make sure you upgrade your node to the latest version.
We are investigating a situation on the mainnet. See status.iota.org/ for updates.
We will be performing an upgrade to mainnet on September 23, 10 AM UTC. We expect this upgrade to to only take a couple minutes.
The upgrade to #Chrysalis (IOTA 1.5) Phase 1 has finished. Restart Hornet 0.5.0 with the --overwriteCooAddress command once. Make sure to update your Trinity Desktop version. A Trinity Mobile update is also required but we are still awaiting reviews from Apple and Google. #IOTA
The upgrade to #Chrysalis (IOTA 1.5) Phase 1 is in progress. Once the network resumes, update #Hornet to 0.5.0. Please do not try to send transactions using wallet software while the network is upgrading. We will keep you posted about the progress. #IOTA
We are now officially performing the network upgrade for #Chrysalis (IOTA 1.5) Phase 1. The upgrade will take a few hours. Please do not try to send transactions using wallet software during the downtime. We will keep you posted throughout the day. Stay Tuned! #IOTA
Tomorrow at 8AM UTC | 10AM CEST, we will start upgrading the mainnet to #Chrysalis (IOTA 1.5) Phase 1. Node operators will be required to run the latest version of #Hornet and restart their node once the operation resumes. Instructions in this post. #IOTA
blog.iota.org/dev-status-upd…
If you have solutions running on top of the #IOTA network, or are operating a node, please make sure that you upgrade to #Hornet before Chrysalis phase 1! Currently slated for release on August 19. Check our last Dev Update for all the details: blog.iota.org/dev-status-upd…
We published the IOTA 1.5 - Chrysalis phase 2 specifications as RFCs this week. We ask our community and partners to provide feedback within the next two weeks. medium.com/@jakubcech/iota-1…
Devnet upgrade has finished. Milestones are being issued and nodes are back online. Thank you for your patience!
We will be performing an upgrade to Devnet on June 23, 7 PM UTC. We expect this upgrade to finish in the morning of June 24. No new milestones will be issued on the network during this period.