Pre-Dev-Update Thread! Yay! :D

I’m sure we’ll be informed in today’s dev update. They still have time to do such things while node ageing and routing model is being fully implemented.


Link please…

You can find it right here.


Wonder what this means for the paper that was sent for review.

AFAIK absolutely nothing. They have parsec v2 completely figured out, it’s just more time and resource intensive than they can currently provide for Fleming to implement the threshold crypto BLS stuff. Seems like this is a quick fix that should work for Fleming in the meantime till they can fully implement parsec v2. I’m sure we’ll hear more soon :slightly_smiling_face:


Yeah, for clarity on this PR 310, the commit message should give a good explanation.
Basically, we realized that our concrete coin (which was always going to be replaced by a common coin once we invest the resources) didn’t play well with some assumptions we’re making.
In this PR, we replaced it with an alternative that makes PARSEC not theoritically asynchronous (btw, also a problem the concrete coin has), but that patches the soak tests for the time being.
If anything, this may bump the common coin work up the priority list a bit, but not more than that. I don’t foresee it delaying Fleming (@anon94252342 :wink:)


In the github comments you speak of a rfc of the actual common coin you’re going to implement (as replacement of the fake one in PR 310). Which rfc is that? I do find #0049 PARSEC, where there is talk of a concrete coin (2/3th of the time common). And that is what I remember (maybe wrongly) as being the (initial) Parsec breakthrough (Byzantine Agreement, Made Trivial), because a common coin was very difficult.


Oops. My bad! I thought we had released an RFC for a proper common coin. We definitely edited the paper to include a real common coin, but haven’t released this yet as it’s making its way through the formal publication process.
We also did a POC of proper common coin but didn’t finish it as we ran out of allocated time to investigate pre-Fleming. We also wrote up the lessons learnt in this POC with the intent to raise a RFC, but it seems we didn’t actually publish it yet.

A common coin is difficult, but now the hard bits are available as other projects such as POA Network released some important components such as Distributed Key Generation in the open. It makes it feasible, now in 2019 to implement and rely on an actual common coin rather than our concrete coin which limited how asynchronous the algorithm was.


Fleming today? Or what is missing to get there? :smiley:

EDIT: Maidsafe we need it so badly! :wink:

1 Like

Can we get any insight into the Node Aging bit. I can see that there are 3 completed tasks out of 14… and that have been the case for some time now. Is there any ongoing issue which is halting the progress in this area? Just hope that it will not take same amount of time to finish as Parsec :slight_smile:


Feels like we might all need to be sitting when reading tonight’s update.

I wonder what’s new. :hugs:


It looks that everything in going towards next stage as was planned in a schedule last week.


ever heard of tabbed terminal?
also you can make a script that controls them all

1 Like

Or a terminal multiplexer like tmux or GNU Screen.




Does this mean that reliable message delivery is finished?


According to the Back End roadmap only 1 issue in progress to go


It feels great to see you guys no longer second guessing, but using the same tools we use to measure progress. We are all seeing the same story now and it’s a great one. This is all a lot more comfortable now, of course we will see slippage and delays, but know where and can be told why.


Don’t know about you guys, but I am hoping a real bombshell gets dropped tomorrow :wink: feels like we are getting really close to critical milestones that will make people have to re-evaluate their fundamental analysis on the value of MAID


I think adopting quic-p2p accelerated the project immensely.