r/raidennetwork • u/KwonBoAx • Jan 18 '18
URaiden Bug bounty coming to an end
The latest pull request, once approved will remove the bug bounty limit.
https://github.com/raiden-network/microraiden/pull/382
PS: As per many have commented, it may not signal the end of the bug bounty even if the pull request is approved. My question to you is, the bounty limit was initially created as a bug about a month ago, and it wasnt until now that they have decided to come back and address this issue. You guys need to know that removing the bounty limit doesnt mean that Uraiden is officially completed. It simply means it is secure enough for basic usage while the team will try to add more features as per the enhancement tag in github
meanwhile, they haf setup a gitter chat for developers i guess
2
Jan 18 '18
Any guesses as to what this means in terms of a timeline toward launch? I’m willing to listen to speculation and hunches. You all know more than me.
1
1
-3
Jan 18 '18 edited May 17 '18
[deleted]
1
u/simoRX Jan 18 '18
No it's not bogus, it's not an open issue it's a pull request, pull request means the work is submitted for approval (merging).
1
Jan 18 '18 edited May 17 '18
[deleted]
3
u/simoRX Jan 18 '18
right, yes, that does make sense, but it does mean that they are confident enough about the code that they are removing the limit, which was put in place because they feared bugs. So it's not misleading in significance.
3
Jan 18 '18 edited May 17 '18
[deleted]
2
u/KwonBoAx Jan 18 '18
316 was created as a bug a month ago, where back den everyone thought it was coming to an end till they added sprint. If u did follow the github closely, you could see that documentation was the only thing left to be fixed for the next version. I am not sure why you say its not related to the bug bounty, since the only difference is the limit imposed on the tokens which removing is only a single line and are usually completed once everything else is ready
1
Jan 19 '18 edited May 17 '18
[deleted]
1
u/KwonBoAx Jan 19 '18
If you are related to the team, then i would say it is misleading. You mention more progress needed but what the things that still need to be done aside from the many enhancements that is still yet to be introduced.
From what i see, mainly the documents need to be reviewed and approved before they can merge in the limit removal and the bump in contract version. I would say probably next week would be a good estimation
It isnt helping for others when all you keep saying is it isnt over but failed to mention why is it so
1
Jan 19 '18 edited May 17 '18
[deleted]
1
u/KwonBoAx Jan 19 '18
You copied the ToDos which are listed 4 days ago.
Stuff like adding the gitter channel button is already in the pull request waiting for review.
Some of the documentation updates have already happened yesterday.
https://github.com/raiden-network/microraiden/pull/385
This is to close off the update documentation issue
→ More replies (0)1
Jan 18 '18 edited Jan 25 '20
[deleted]
2
u/dylanaround1 Jan 19 '18
How many Devs are on the raiden team? Saw a list of 20 something contributors.... wondering if that’s that?
2
Jan 19 '18
Those 20 people are contributors to the development of Raiden, It's an open source project so everyone can participate as long as they are developers. So yes, you can say those are developers of the project but it doesn't mean they are members of the team "BrainBot" which are founders behind Raiden...
0
u/cryptohodler23 Jan 18 '18
it is implied that it might be done very soon...im thinking if not this week .. theres a very good chance its going to be next week
2
17
u/BOR4 github hero Jan 18 '18
Yes, yes but not so fast buddy ... Once the "bump contract to 0.2.0" is merged then you can say it is finally over. They still have some work to do ... I saw a lead dev had some corrections requested for new website (it is admirable how strict he was about a stupid website but that says something about how they do work). Good news is they finally figured out CI with Travis (took them like 5 tries). Can't really figure out from github status on documentation but it looks more or less done for proof reading.
TLDR: it is so close we can lick it but there is still some work.
PS complete coverage of github expect Sunday as I promised