eduffield
Core Developer
Despite the forking issues with enforcing masternode payments, the code and strategy that we're using now is looking really good. The problem was simply blocks coming in out of order, which are now properly ordered before being checked for the correct payment. I reviewed many different logs and this was the only issue I found, which caused all problems we had.
The question to the community:
It's pretty much impossible to test mastenode payments on testnet and some users/mining pools are very sick of updating. Should I have everyone update again, and enable enforcement on Friday? Alternatively we could wait until InstantX, which is what I'm also working on. Testing InstantX is probably still a couple weeks out, then we have the testing phase, so that could add another month or so. Alternatively, we just have the network update until it works and we move on.
The question to the community:
It's pretty much impossible to test mastenode payments on testnet and some users/mining pools are very sick of updating. Should I have everyone update again, and enable enforcement on Friday? Alternatively we could wait until InstantX, which is what I'm also working on. Testing InstantX is probably still a couple weeks out, then we have the testing phase, so that could add another month or so. Alternatively, we just have the network update until it works and we move on.