Hey everyone,

it is Easter time in many countries. That is exact reason I am late with a post but I hope you don't mind too much. Raiden devs didn't take any day off and they even worked yesterday. Many new things were added to github repositories, so let's start.

EIP 712

After last week's comment on issue's github how people should limit this EIP to some reasonable extent and think about extending it's functionality in the future, we can see some new comments being added.

Most important one is from one of the Ethereum devs that has power to call EIP completed. Since sometimes in last 6 months since EIP 712 was opened. rules about how all EIPs should be formatted changed, he requested those changes to be done on EIP 712 as well.

Good news is that apart from someone requesting more clarification about the issue, no one suggested any more changes to the EIP 712 logic.

My estimation is that it will take some more time before it is finally done, but it got a jump start it needed since the issue was discussed on developer meeting two weeks ago.

raiden

Raiden github was even active yesterday (there were around 20 commits added). All devs are working tirelessly but hackaugusto (who seems to be responsible for raiden repository) doesn't know for a day off it seems. Thank you from all of us =).

I am not 100% sure what exactly they are currently trying to fix but my best guess is they are implementing state machine responsible for recoverability to the parts of project they still didn't. One of those parts would be token swaps they disabled few weeks ago until they are finished with implementing state machine.

In the meantime they are tidying up the code (removing parts they don't need any more, better naming). One thing they had small problem with is deep inheritance of classes inside code. Someone helped them with figuring that out by suggesting a trick that is supported in Java programming language natively but not in Python. It was a good suggestion so they fixed that as well. (Tip for devs if they are reading this: you can stop inheritance by declaring class final, but if you want to force it just make a class abstract with 0 abstract methods example from Java: Java's HttpServlet class).

They updated milestone goals inside repository. We can see that one big issue they have ahead is depending on state machine being finished. With those 2 done, project would reach that old "next minor release" goal.

MVP milestone was updated as well. Inside that milestone I see implementation of WAL (write ahead log) as something that would take the most time. Out of remaining 7 in that milestone there are some that are there just to remind them selves that it needs to be done but details of implementation are not specified. Issues like that are called meta issues.

All in all, raiden repository is headed slowly to it's MVP and it is really exciting to follow the process.

pathfining-service

Pathfinding service repository is interesting because issues inside are tagged with interesting tag. Some issues have tag "pre-mvp-release" which gives a hint they are planning to do one more release before MVP. I would guess that would be "next minor release" goal in raiden repository.

Good news is they figured out routing algorithm. Algorithm is done but they are missing a functionality to update fees on routes between nodes. Right now it is assumed that every route has a default fee. That makes route with least number of hops optimal one. If you are not sure how that makes sense just ask in comments and I will give an example =).

Tasks that they plan to do for pre-mvp-releasae are mostly related to updating fees in network and tests for the whole thing. They plan to do tests of security of the whole thing as well.

So, pathfinding is coming along nicely as well.

contracts

Contract repository is bit ahead in development in correlation to the remaining repositories.

I am pretty sure most of the hard logic tasks are done and they are focusing more on cosmetic things at the moment.

There is no milestone goal in this repository so I can't comment on what they are planning to do for the pre MVP release. I wouldn't be surprised if this repository is more or less ready for that.

Open tasks and pull requests are not giving away any big plans, so we are bit in the dark when it comes to this repository.

monitoring

Status of monitoring repository is very alike contract repository. Work inside is not giving much hints.

If I am honest, I am bit sceptical that monitoring is as done as contracts are. That is because contracts were being worked on for months before they were split inside dedicated repository and monitoring is a fresh repository.

I am sure they didn't hit the wall in development because it does not seem like that. I see two possibilities. Either monitoring was fairly simple and it is more or less done, or they are focused on different things at the moment.

We will just have to wait and see.

microraiden

Waiting for EIP 712 and cosmetic fixes.

rest

Nothing significant. If there will be anything big I will comment in comments =).

conclusion

Development is going nicely and it seems that pathfinding and raiden are main focus. Contracts are I believe pretty much ready and monitoring is a bit of enigma. They plan to do one more release before MVP but I am not sure when, it seems it is not that far away to be honest. Microraiden is waiting for EIP 712 which is as well coming to it's completion slowly but surely.

There, I hope you are excited about fresh news as much as I am. Weekly posts reached double digits and next goal is triple digits. You are all great support, community here is great and discussions are always very civilized. Keep it up that way.

If you want to leave some cheers for development team you can always comment here, I am sure they scroll trough every post =).

Have wonderful week and enjoy the Spring,

'till next week.