I think the last team consisted of only @Eleven. @glv’s last work was in April and @erasmospunk’s last work was in February. And I was barely involved when the Nu crisis happened.
Last week I asked @Eleven whether he was still working on B&C and he told me he was on vacation but was now ready to get back to work. I asked him to put the development on hold until we have a proper plan.
@glv and @erasmospunk did pretty good work on Nu and B&C but I don’t think they are available. I still need to review @Eleven’s work on the trading messages to get a better opinion on his work. What he did on the abstention is not satisfying.
It’s very hard to say. It depends on lots of parameters, including who would be working on it and how we actually implement the remaining parts. The trading user interface for example can be done in very different ways that need to be analyzed.
When a block is received from another node you determine whether it’s abstaining by reading the abstention flag of the current node (indirectly, but that’s the end result). In other words if I’m abstaining then I’ll consider that all other blocks are abstaining. The information that a block is abstaining is not even put inside the blockchain.
I only reviewed quickly the trading messages code he wrote, and it didn’t look bad. This code was built on top a an architecture started by @glv. So maybe it could work if I provide @Eleven more detailed instructions on how it should be implemented. But that requires more time from me.
I’m not sure what “co-author” implies. Jordan wrote it and asked me to review it. A made some remarks that made him change some parts.
There are parts that are still not very clear to me, like the trading user interface.
- reviewing and testing the already implemented trading messages
- implementing the few messages that have not yet been implemented
- designing and implementing the signer’s logic
- designing and implementing the trading user interface