Search results

New Version - v0.12.0.26 I'm still tweaking the masternode payments system, this is a slightly different implementation. It also includes other fixes for syncing the winners list, and I fixed a bug that was not allowing masternodes to update their protocol version when remotely activated by the...

New Version - V0.12.0.25 This should fix the masternode inconsistances across the network and addresses the differences that we've seen in "masternode winners". The differences in that list should fix themselves pretty quickly. It allows fixes various syncing bugs, so that part should also be...

Is anyone having trouble keeping masternodes online? I saw 20 masternodes drop off the network a bit ago, but I haven't had any trouble myself.

Running a masternode is great, so is mixing. If you want to test the proposal system, you could try adding a proposal and make sure it's doing exactly what it's designed to do. Flare alread spammed the system, so we know it can take that . We just need to make sure it does what's it's suppose to...

New Version - V0.12.0.24 *** If you downloaded 12.0.24 earlier when I posted, please update again, there's a couple extra changes included :) *** eduffield - Reprocess best chain for coinbase payee on each block - Disabled coinpayee cleanup - Dont ask for mnb of known masternodes - vesion...

Testnet allows non-standard transactions, and there is a multi-sig check here: https://github.com/dashpay/dash/blob/v0.12.0.x/src/script/standard.cpp#L194

It's not causing issues in testnet (we've been paying multisig addresses with no problem), but that might actually be an issue on mainnet. Udjin was saying something to that effect awhile ago. I'll look into it.

New Version - V0.12.0.23 This should help us to vote for the same payee each block. Also we've included some other security fixes and a clearer API for the budget system. Evan Duffield - version/proto bump - Better NewBlock sync check - Only check vote sigs once / payee cache update on...

Yeah, I just fixed the cause of it in v23. It was masternode payment related.

When you start a HOT node via a COLD node, it updates the lastTimeSeen for that masternode. That sets the masternode to ENABLED. After that, the HOT node should take over pinging, which then happens shortly after that (it signs using the shared private key --mnpivkey). If the HOT node fails to...

You're kind of right though, HOT has the keys the network uses. COLD only signs the 1000 DASH vin 1 time to let the network know what the new key is.

NEW Version : V0.12.0.21 ** Compiling, should be done in about 30 minutes ** Eduffield - version bump - Small syncing improvement - Resync on sleep/wake or failure - Only ask for missing masternodes/budget items after sync is complete - Set fValid=true when receiving new votes - Added more...

Enforcement is enabled, everything is looking good so far.

I just added the vote time to get-votes, so you can do something like "mnbudget getvotes evan-fund" and it outputs this type of data: "e08d48d1550a84dace5ef5bd2c40d3ec181358e4aee175bbdb904f234efba266-4" : { "Vote" : "YES", "nTime" : 1437008703, "fValid" : 1 }

NEW Version : V0.12.0.20 This adresses what was causing people to get stuck while syncing and a few other things. I'll be turning on enforcement to make sure everything is working properly on that side. Linux32...

Yep, thanks. It's fixed and compiling as we speak.

Yeah, can you send me the logs pls?

I'm actually seeing 105 votes everywhere, which includes yours. Maybe it was delayed. There's some passive rechecking of the proposals that happens every 20 minutes or so, that might have done it. I guess it's OK

I'm seeing the same thing everywhere. Moo, did you do something or did it fix itself?

Maybe try deleting blocks and chainstate, then resync? Nothing actually changed as far as that logic goes, so I'm guessing it's got to be related to the blockchain+txindex change