Monero Weekend Update
On October 17th Monero (XMR), a privacy-oriented cryptocurrency, conducted a major upgrade of its network called “Oxygen Orion.” The goal of the upgrade was to increase transaction speed, reducing transaction size and improving the overall performance of the network.
This Monero upgrade was significant enough to be considered a hard fork, so for the next few days customers experienced some instabilities in the network. This Monero fork was an expected and necessary event, however, some worries about the previous version proved to be justifiable.
What Is A Hard Fork?
A hard fork is a change in a blockchain protocol that influences the structure of the blocks, including block hash, which forces customers to upgrade the block sequence, thus making ‘old’ information invalid.
Usually, hard forks are performed when there is a need to create a new coin with new rules on the network. But in some cases, if major software changes occur on the blockchain, the changes can also be described as a hard fork, because customers have to go through the same update procedure.
The new ‘CLSAG’ link signature protocol implemented by Monero this weekend required all participants of the Monero network to upgrade their software, so it can be considered a hard fork.
What Impact Did This Have On Monero Transactions?
After the upgrade, there was a minor bug present in v0.17. Some blocks got stuck, potentially affecting local operators, especially those who were not online during the XMR fork but wanted to sync soon afterwards.
Thanks to Monero developers, the hotfix was implemented in just a few hours, and fortunately, the network was restored to smooth operation without major issues — only a few transactions got stuck, and people on the network at the time simply had to update manually.
Delayed Monero Transactions On ChangeNOW
Exchange platforms tend to prepare for events like hardforks, and some of our major liquidity providers temporarily turned off XMR payouts. From October 17th to October 19th, Huobi and Bitfinex alternately closed and opened Monero exchanges.
We were not properly prepared for this hard fork and some exchanges were able get in the queue. Normally, we have standard protocol for such situations including a variety of steps:
– Verifying the availability of coins from liquidity providers
– Verifying our own liquidity resources
– Planning downtime if necessary
– Promptly announcing the downtime to our clients
In this particular case, the process led to a few failures, and as a result, the situation on Monday looked as follows:
1. Liquidity providers temporarily denied access to the coin
2. Our own liquidity reserves were not sufficient for long-term operations without an external liquidity provider.
3. We missed the moment when the queue of unfinished exchanges started to accumulate (due to monitoring failures).
4. As a result, on Monday, the coin had to be turned off for several hours to process all unfinished exchanges
Current Status And Conclusions
As of this moment, all exchanges are successfully finished.
The situation was informative for us because we discovered a combination of errors that led to such a delay in our services. The main problem was that we were poorly prepared for potential instabilities on the network in advance, and the monitoring system wasn’t responsive enough in the process.
The ChangeNOW team analyzed this case and the problems encountered. We made plans to reorganize the internal workflow, so that certain eventualities will not happen in the future, namely:
- Increased the liquidity reserves
- Improved the monitoring system
- Expanded our support team
We view situations like this as an opportunity to learn and make our services even better for our customers. We therefore consider it necessary to review such cases in detail and improve our services to prevent missteps in the future.
Thank you for contacting our support team and for your patience while we were fixing these issues. If you have any other questions or inquiries left regarding this case — please contact our support team at firstname.lastname@example.org.