Raiden Network: Route

Content

In order not to let the specific details of the route bore you, let's look at an obvious question: when is it ready?

We think µRaiden is ready and can be used by many applications.

The answer to Raiden Network is a bit more complicated, but according to the original Raiden concept, the answer should be: "Once it supports transmission between participants without a direct payment channel, and the software has been security audited and deployed to the host On the chain, then it is ready." It took us 2 years, but we are about to reach this point. Add a security audit, deploy it to the main chain, and we are done.

But you know the 80/20 rule. You can complete 80% of the work in 20% of the time, and the remaining 20% ​​of the work needs to consume another 80% of the time to complete. Successful projects are as much as possible to deliver the final 20% in order to gain adoption and maintain competitiveness.

The Raiden network can and should be improved. For example, privacy, efficiency of finding a path, longevity of channels, accessibility of light clients, shorter liquidation cycles, management mechanisms, applicability, and so on. Some of them must meet our standards for minimum viable products.

Fortunately, the Raiden Network was created as an abstract design to allow the continuous development of parallel programs on many improved components. Although it takes time, research and effort, it is all worthwhile.

At the moment we have only discussed the protocol and software. But in order to see widespread use, a greater effort is to guide a healthy ecological environment around the Raiden Network, so that developers will choose the Raiden Network when deciding on payment infrastructure.