We have discovered an error in how the getmotions RPC counts motion votes. This means the vote counts as displayed in the block explorer and your Nu client have been incorrect for the open source motion. The blockchain record of votes is not corrupted in any way. Using a fixed getmotions RPC, we see that the vote to open source code only cleared 44% so far. Previous motions were properly counted. As the issue came to the team’s attention in recent days, someone began exploiting the issue which caused vote counts as reported by the getmotions RPC to become skewed. Other types of voting that result in protocol actions such as custodial grants and parking rates are unaffected by the defect. Previously passed motions are also unaffected.
The open source code motion content gives us 45 days to open the source, and it has been our plan to release it during the later portion of that time window. I’m certain that the open source motion will pass very soon with the corrected counting method so that we will still release source code within 45 days.
However, to provide clarity and fairness to those who are opposed to opening the source code, we need to keep voting on the motion. If you support the motion and have removed it from your client, please put it back. Here is the hash:
A new release will be posted very soon with a fix to this issue, probably within 24 hours.