I have no idea.
I donāt. He has always been very careful about hiding his identity.
I havenāt, but my communication with him was very sparse these last weeks.
Sometimes he was absent from the chatroom for several days. He usually came back to answer if we mentioned him (but not always), but I think nobody mentioned him since the crisis started.
I think we could finish the core system. Iām not sure about the front end because there are a few things I never took the time to think about. But if something unclear came up we could certainly find a solution without Jordan (unless itās a fundamental flaw without good solution but Jordan probably wouldnāt help either).
I think the main problem is my available time. He asked me at the beginning of the year to lead the team, but I failed mostly because I lacked time. So he took this role again. I can probably take it back, but my available time is still uncertain.
Right now itās unlikely. If we consider the shareholders who didnāt upgrade their client are apathetic then we currently only have 63% of active shareholders so we would need about 80% of them to vote for a motion or a grant to make it pass. And they include Jordan.
But as Sentinelrv said, if we switch to protocol v5 then it should not be a problem as long as 50% of the non-abstaining shareholders agree.
I wrote the detailed protocol specs, so about the core system the answer is probably yes. Iām not sure about the front end though, but I think it was not planned for this development round anyway.
I could probably lead on the technical side of the project but I lack time.
I have recently had a few important disagreements with Jordan on some technical parts, but I didnāt have the time or the energy to debate them with him (except for the default data feed, which was very bad for the future in my opinion so I took the time). So if Iām going to lead the development we may have to discard some of the very recent work Eleven did. An advantage of this way would be that a part of the remaining code (the signer logic) could be written by any coder, not only by C++ coders with good knowledge of blockchain internals.
Iām not sure about that because BKS is very illiquid right now.
Thatās a very hard question that has always been in the hands of Jordan only. I donāt know anything about the costs involved besides my own. Evaluating the time only is also very difficult, especially because I donāt know how the other developers are efficient nor how much time testing requires. I may be able to evaluate how much time I would need to do everything myself, but even that would take quite some time and would be very uncertain.
Do you mean do we support the design paper as it is written? I think many parts are unclear but I was able to write more detailed protocol specs from it. These specs include changes from the design paper though (about which Jordan never gave his opinion, so I donāt even know if he read them).
My contacts with Angela have been through BitMessage only, and I guess itās the same for the others.
Iām not sure the others are able to build the packages right away. I was usually the one doing it. It takes an hour or so, but itās mostly automated so it doesnāt cost very much (it could be fully automated by the way, by anyone with Linux system administration skills). Thatās for Linux and Windows builds only though.
I can probably find some time to review your changes.