This article was first published on Stories by Raiden Network on Medium
It is time for our bi-monthly summary of all things Raiden: overall development progress, product updates, event participation and all the other stuff that we’ve been up to in January and February. We hope you all had a good start to the new decade. Let’s dig into what’s new with Raiden!
Development Updates towards Alderaan mainnet
The last two months have mainly been used for fixing known bugs in the messaging transport layer. The goal of this is to get Raiden into a state where it is stable and robust enough to make it into a new release candidate and ultimately become the Alderaan milestone.
Alderaan will be the first integrated mainnet release coming with a service layer (monitoring and pathfinding service) together with new features (channel withdrawal, source routing, mediation fees).
- Raiden Client: Fixing bugs, optimizing Matrix and improving the scenario player have been our main priorities over the last two months. The team has been working on fixing bugs, which are mostly related to Matrix, which is the protocol that we use for messaging transport. There has also been a focus on optimizing how we use Matrix as well as making Raiden more robust in the way that it utilizes Matrix.
Lastly, the scenario player, which is used on a nightly basis to run end to end tests of Raiden, has seen some improvements especially to the infrastructure on which it runs. With these changes, we are getting closer to announcing a new release. All releases can be found on the Raiden client release page.
- Raiden Light Client: The light client has seen plenty of improvements and there’s been two new releases as well as two minor releases. The main focus of the releases has been UI/UX improvements. The Raiden dApp frontend now includes support for derived subkeys. ...
To keep reading, please go to the original article at:
Stories by Raiden Network on Medium