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.

62
[GIT] Weekly Update 3
Author Summary
BOR4 is in git
Post Body

Hi all,

another interesting crypto week is behind us, another weekly raiden git post is ahead =). Hope everyone is having a great Sunday and is ready for some fresh news from raiden github. This week was not so eventful when it comes to github, but there was a Etherum convention in Berlin where raiden team did a successful demonstration of microraiden. Nevertheless here comes my weekly analysis.

microraiden

As we know microraiden project is currently waiting for 2 weeks to pass without major bugs being discovered. As far as I see it there were no major bugs discovered so if my memory is right project should exit bugbounty phase this Tuesday.

Only 2 commits were added to the project this week and they were purely cosmetic.

In pull requests we can see more work in preparation for exiting bugbounty phase (docs and demo design update), a temporary fix needed because of bug in some library microraiden depends on and old pull requests which are either waiting for bugbounty phase to finish or team just didn't review and merge yet ( I don't know what is wrong with these).

As for what they plan in future I don't see anything on github. I am sure we will get that update once bugbounty phase is over (lets hope it is Tuesday).

raiden

Raiden is aiming to release a new minor release.

Since last week they added 2 more issues that need to be completed in order for it to happen. Good news is these 2 issues don't sound so serious. One Issues is about them not covering an edge case when someone requests a token that does not exist (if I can have any influence on how that will be fixed please return 404 and not empty list). Other issue is about them forgetting to switch something to python3 when they were doing a switch from python2 to python3. As I already said many times I don't have complete understanding of codebase but in a standard project these 2 issues would not take more than a day to implement.

Work on 1 out of 4 remaining issues (PR #1205) is halfway done and is waiting for merge to master.

Work on remaining 3 issues is not visible on github which shouldn't concern us since as I said in last week's post they usually like to merge a completed big feature once it is done. I would go so far and say that lack of visible work is a good sign since it means devs are probably working on these big issues and not spending time on small fixes.

conclusion

No big bugs on microraiden in last week so we can expect exit from bugbounty phase this Tuesday.

2 more simple tasks in raiden project before next minor release but they seem very simple. One task is half way done. 3 remaining tasks are probably worked hard on but I can't see it on github (this is how they usually do big tasks).

PS all PSes and disclaimers are still active from weekly post 1 and 2.

Have a great day =)

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: 23 hours ago
Posts updated: 9 months ago
github hero

Subreddit

Post Details

Location
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
6 years ago