How does ICP ensure that developers follow NNS voting results for code development?

These are great questions. The proposal that has passed was a BS proposal. It was just to try to “see if they should start working on it”. Whether that proposal passed or not didnt change anything about the internet-computer-system. They call it a Motion, just like when a Motion is filed in a court, it does nothing. After the code for the new feature is complete then yes they will have to submit a new proposal, one that has the new binary within it, but this proposal they won’t make public, (at least they haven’t been) they will put it up quietly and then vote on it themselves quickly and then come out and say hey that feature we were talking about is done. Even though no one outside dfinity had time to check the hash of the proposed-binary, check the proposed-source-code for malicious code, build the proposed source code, and check if the hashes are the same. Not just that they give nobody time to do this, but us people outside dfinity cannot build the source ourselves at this time, see this thread: Ic code dump incomplete? and many other threads. This means that at this time we cannot even check that the source code that is on their github is the same source code that is being proposed and updated into the system. They don’t even put the latest code onto their github before they propose it. Until we can build the complete proposed source code for the whole IC on each proposal, so that we can verify that the hash of the proposed binary is the same as the hash of the source-code-build by our selves, all of these community conversations are bs.

6 Likes