Hey everyone,

how you all doing? I hope this week's market didn't spoil your week. This week I earned cool flair "github hero" (big thanks to all the admins) and I am here once again to bring some fresh news from the github. Agenda for this week is next: First, don't mess up the title again, apparently it is not editable. Second thing I have planned is, since they published 3 new repos on Friday I didn't have enough time to study them properly, so I have planned to do a brief introduction on them in this post and then do a special 8.5 post mid week where I'll just analyze them. So, without any more useless talk, let's dig into the github!

spec

Spec is one of the 3 new repos they exposed to public on github this Friday. So, what is spec exactly? Imagine you are in beginning of 20th century and there is something new called "car". Spec for a car would explain what are it's parts, what is an engine and how it works, what are it's limitations, how it drives and so on.

In other words it is explanation of what are responsibilities of what part of code, how different parts of code work together, what needs to be implemented and what needs some changes.

I scrolled trough it for couple of hours and I can tell you in my 8 year experience with technology I never read something even close to it. Every part, every name, every decision in development is explained in great detail. Stuff that is written there is some pretty high level coding and I can't understand everything yet, but I am sure someone with better knowledge would not have any problems to fully understand raiden.

raiden-contracts

Contracts are essential part of raiden tech. It seems, that since they are such big part, they wanted to separate them in different place so they can be managed more easily. My first impression is that code inside repository is mix of old code, plus some new code.

I think separation of contracts in different repository is good call by the dev team. More in-depth review will be in 8.5 post.

raiden-monitoring-service

Monitoring service is last repo they added. Monitors will be big part of raiden tech and they will be responsible for keeping an eye on channels when one side won't be able to (example: loss of connection). Their successful implementation is essential to achieving 100% potential of raiden tech.

microraiden

Microraiden is still in sleep mode waiting for EIP712. When it comes to EIP712 progress, there was some activity regarding it on it's github, but I would not say status of an issue changed significantly since last week.

They continued work on documentation. Difference between documentation in microraiden project and what is in spec project will be covered more in 8.5. Long story short, spec is theory behind the tech, documentation is details of the implementation of spec.

They had some issue with updates of external project, which caused microraiden to not work properly, so they prevented it by limiting release versions of external projects. It is really not big deal, happens in development very often.

raiden

Devs continued to merge business logic code for state machines and I think they are pretty much done. They have planned few little changes to it (like naming things more clearly) but that is not something we should worry about. Most important thing that really really big feature is coming to an end.

They still didn't merge "one contract per token" pull request. It is very understandable since work around state machines was pretty big, they just want to take their time and not make stupid mistakes. That part looks pretty much done as well and I think they will look into merging it this upcoming week. They even might decide to put those changes in the new repository with smart contracts, but that is just matter of their preference.

Even tho my report for raiden is pretty short, dev teams work is huge. It is just that almost all work is around two big issues so there is not much to say about it.

conclusion

microraiden - docs and waiting for EIP712

raiden - work around state machines almost done, "one contract per token" is next in line to be merged

That is all. I appreciate your feedback and questions, so big thanks once again.

I wanted to ask you guys one question. In video from ETHCC they mentioned they are looking for a community manager. I am very interested to reach Brainbot and talk to them about that position. I see big benefit in that, because I will probably be able to provide you guys with more concrete reports and answers. On the other hand, you might feel that since then I would be officially presenting Brainbot I would not tell you what I think and see and would rather be influenced by Brainbot. Don't know how to say it nicely, but that I would become a sellout.

So do you guys think that I should apply or not? Please respond to that in comments =). Your feedback is essential to that.

Now, that would really be all.

See ya in the comments and in 8.5 post!