Quote from: niko on March 12, 2013, 06:08:31 AM

Quote from: MPOE-PR on March 12, 2013, 02:04:47 AM

Quote from: alexkravets on March 12, 2013, 02:01:44 AM

Another way to state the real problem: There is no Bitcoin Protocol Spec, most semantics buried in the hairball of the C++ reference implementation

That would be correct. It's a huge issue.

It is also a huge issue that those suggesting we need the protocol spec are brushed off with the "you don't get it" nonsense by elitist devs.
Bits and pieces, some expired, are scattered around Wiki. Is that the best we can do?
@MP: would you be willing to lead the effort of formulating the current protocol spec?

Sez MP:

Quote

I am willing to help, both by providing funding and by consulting pro bono on things I might have a clue about. These often enough are not coding, as I'm not a programmer. Nevertheless I would gladly strive to help avoid the sorts of strategic mistakes we've seen at work so far here.

I don't think this would necessarily constitute a lead role, and moreover if we focus on getting things right rather than propping egos and stroking issues leading might not even be so desperately needed. Let sense lead, not common but actual sense.

Maybe it's time to do a headcount, start a project... specified Bitcoin is certainly better than code-centralized Bitcoin.