Hey everyone!

​

Welcome to Weekly Update 65. For this update we’ll be looking at the recent medium article on the Raiden Trust. Another medium article worth highlighting would be Lightning VS Raiden #3 (by /u/SamAiken), although not covered in this update, it’s a great read if you’re interested in engineering challenges surrounding monitoring services. This update will also cover the usual Raiden Github development progress, Let’s dig in!

​

Raiden Trust

When the Raiden Network Token (RDN) launch was announced, it was communicated that 16 million tokens of the token fixed supply of 100 million RDN tokens would be used for funding an external development fund.

As per the original plan, the funds in the external development fund will be used to fund projects that help build and grow the Raiden ecosystem. Examples of those projects are: 3rd party researchers and developers of alternative client implementations, helper service providers or other external projects that provide complementary or foundational components or applications that help bootstrap the Raiden ecosystem.

Last week, on April 25th the Raiden Trust was established. Alongside the announcement, a Medium article explaining legal and organisational set up was released. The complete Trust’s deed is available online, with this link.

The trustees and the administrator are currently refining the grant application guidelines, the grant review process and the implementation of the transparency requirements. Once these final steps are completed, application guidelines will be announced and projects will have the opportunity to follow the formal process in applying for grant funding.

​

Development progress

Last week, the development team worked on tasks they prioritized during the last planning session. As we mentioned in the previous weekly update, some of the tasks with the highest priority are the introduction of the mypy type checker to the codebase and improvements of the continuous integration workflow and tests.

Significant progress has been made towards the complete introduction of mypy and large parts of the codebase have been adjusted to be compliant with it. All the modules that didn’t meet the required test coverage of 90% have been identified and separate tasks were created for this purpose. Additionally, the development team decided to extract the scenario player (custom tool built for testing real life scenarios) from the Raiden client repository and create a dedicated repo for the tool itself.

In the upcoming week we can expect for development team to continue working on high priority tasks and issues related to the “Next Release” milestone.

​

Conclusion

To finish up Weekly Update 65, this week consisted of mostly improvements to the code and the Raiden Trust. No meetups this week, although after the latest hackathon (covered in Weekly Update 64) there’s been an increase in developer interest in Raiden on Github. As always, thanks for reading and those contributing, feel free to leave a comment and we’ll get back to you the best we can.

​

Cheers!