Search results

Well it is not a bug that can be used practically by the users, but it is a bug which could allow an Ubernode to elect anyone as a masternode payee even if a) the guy is not in the masternode list b) even if the 1000 DRK TxIn is long spent So sending around 1000 DRK many times to different...

Did that, for transparency reasons, here the relevant code part which clearly allows spent TxIn for the Block Payees. I originally thought that we all can submit the consensus vote, so I was sending around many 1000 DRK transactions to have enough inputs for winning every vote. Then I realized I...

I have found a bug in the "centralized masternode winner" Algorithm by the way. Included CTxIn are just checked for having 1000 DRK, but not if they are already spent or not. This would allow the Uber-Node to include Winning-Masternodes which no longer have a valid TxIn.

Thank you for the pointer. I will get a steaming cup of coffee and read the complete thread right now. At the first glance, this looks like one of the major issues to me.

Hi, I am a holder of several thousand DRK, and I have taken some time to dig deeper into the DRK source code. First of all, I have found the DOS attack on the masternodes list by sending TxVin's with varying nSequence number which allowed me to include as many entries as I wanted into the...