Coming soon - Get a detailed view of why an account is flagged as spam!
view details

This post has been de-listed

It is no longer included in search results and normal feeds (front page, hot posts, subreddit posts, etc). It remains visible only via the author's post history.

12
[GIT] Weekly Update 104
Author Summary
BOR4 is age 10 in git
Post Body

Hey everyone!

Welcome to Weekly Update 104. It’s great to see the team’s dedicated development resulted in the project being listed again as one of the top 10 ERC-20 projects with the highest recorded developer activity on Santiment for January. Let’s dig into the development progress of last week and other fun facts about Raiden!

Raiden testing infrastructure

Raiden’s testing infrastructure consists of the test suite and two testing tools which have been internally developed by the Raiden’s development team. There are more than 800 test variants within the test suite, from unit and smoke tests to more complex integration and stress tests. Custom-built tools used in testing include the Raiden Scenario Player and Raiden Echo node.

The Scenario Player allows developers to define a scenario which is then simulated using real nodes in the environment of choice (either the Ethereum main chain, one of the testnets or a private chain). To give some examples, tasks that can be defined in a scenario include: join a token network, create a channel, top up a channel, etc. An example of such a scenario can be seen here.

The Raiden Echo node enables users who want to try out Raiden to send transfers to a node operated by a bot with a fixed set of automatic responses. Corresponding documentation describing automatic responses can be found here. Last week echo node was moved from the Raiden client to the separate repository. This decision makes sense as the echo node is not a client related feature. Decoupling unrelated features makes code cleaner and easier to maintain.

Development progress

Developers working on the Raiden client were focused on identifying and fixing the remaining open issues inside the Alderaan milestone goal. In the upcoming week, they plan to continue working on optimizing parts of the codebase to enhance performance.

A new release of the Raiden light client has been introduced. The changelog can be found here. Changes include optimizations for event polling, which will help run the light client on low-end devices, such as a NanoPi. Also included in this version are: improved PFS url matching, updated Raiden Contracts to v0.36.0 and derived subkey support. If you are interested to try it out yourself you can via this link and following the Try Out the Raiden Demo dApp guide.

Conclusion

Wrapping up this Weekly Update, the development team focused on adjusting for new settlement timeouts, improved error catching, testing enhancements and fine-tuning. The development of the Light Client has seen a promising number of improvements, improving its utility and UX with the new version. That’s everything we have for you this week, another reminder for anyone in the area, the next event coming up where the Raiden team is attending and hosting a workshop (!) will be EthCC. If you have any questions about this update or Raiden Network in general then please leave a comment and we’ll get back to you the best we can.

Cheers!

Author
Account Strength
100%
Account Age
9 years
Verified Email
Yes
Verified Flair
No
Total Karma
5,900
Link Karma
3,489
Comment Karma
1,615
Profile updated: 5 days ago
Posts updated: 8 months ago
github hero

Subreddit

Post Details

Location
Age
10
We try to extract some basic information from the post title. This is not always successful or accurate, please use your best judgement and compare these values to the post title and body for confirmation.
Posted
4 years ago