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 
)
22 Likes