Search results

mm, try downloading again

v0.12.0.31 - Fixed some DS propagation issues, it should be a million times faster now. - Syncing is also working perfectly now Linux32: https://dashpay.atlassian.net/builds/browse/DASHL-DEV/latest/artifact/JOB1/gitian-linux-dash-dist//dash-0.12.0-linux32.tar.gz Linux64...

Sorry I'm late to the party :wink: 1. Yes 2. There's multiple layers of defense against this type of attack. First off, the masternode network reduces the network propagation latency to about 4 seconds from side to side. That means you would need to propagate the conflicting transaction within...

I think it will come down to whichever offers more upside. Masternode operators will have to concider if destroying the coins is better than the project being proposed. At least it they can't pay themselves with the budget, that would be much worse.

Yes, the budget system on testnet creates a ton of extra coins. On mainnet it will reduce the total supply, unless we always utilize 100% of the budget money. On testnet, budgets are paid every 50 blocks so that we have lots of opportunity to test the system, whereas on mainnet it will happen...

I don't think we've changed anything with DS in a few versions, so it can't be broken. Actually, I just turned it on and I got mixed instantly. So I guess no one was mixing except for you. We were focusing on trying to get the syncing process working (which is working beautifully now).

Enforcement is now ON! There's also a new build of 12.0.30 that has super-syncing ability, it's quite nice!

That should be fixed in .30, let me know

v0.12.0.30 This should fix the syncing issues with masternodes and v29. Also, people should be able to start masternodes within a couple minutes of when the client starts now. There's also significant changes to the security model of the proposal system, which should work better, but we'll need...

I bet there's no different with just the new protocol, see what this command says on each: masternode list protocol 70097

Aug 26, 2015. We'll probably launch v12 a week or so from today.

This is the correct chain -> dash_c getblockhash 89756 000000101c521ddc9e9f84ce06e1769f53821c8e16ec0616d0d560f4d3081a6a

v12.0.29 This should be a million times more stable, I found a few rather large bugs and dealt with them. Please restart with --reindex and we shouldn't have any more forks or other consensus issues. We will probabably need to recreate the budget proposals because I changed the format of...

If you're not on this chain, please reindex. I'll watch it this time and see if anything wierd happens, we might just not have enough hashpower. getblockhash 89354 0000000e61467909da94761e656415db29dd6e140a04d07f3642a1a6c0e151fb

Is anyone else having issues staying with the current chain or is it just moli?

v0.12.0.28 Links should work this time! THis should also fix some syncing issues and consensus between the winners list. Filter SigTime modes / version / proto bump remove sync forcing and count already seen as a success instead Improve portability of mn ranking algos Fix syncing issues …...

New Version - v0.12.0.27 This should fix a few bugs that we've seen popup such as syncing issues, client hanging on quit and some display issues. @evan82 do not sync while IBD delete comment protocol bump Various improvements … Check for existing budget hash before submitting inc min peer...

On testnet, payments happen every 50 blocks. So we're on a very accelerated version of the mainnet implementation. RemainingPaymentCount definitely had a bug, thanks for pointing it out! https://github.com/dashpay/dash/commit/f727b2dbd714c9fdaf336db1d9ae4522c759a3ed Voted!

dash-cli spork active { "SPORK_2_INSTANTX" : true, "SPORK_3_INSTANTX_BLOCK_FILTERING" : true, "SPORK_5_MAX_VALUE" : true, "SPORK_7_MASTERNODE_SCANNING" : true, "SPORK_8_MASTERNODE_PAYMENT_ENFORCEMENT" : true, "SPORK_9_MASTERNODE_BUDGET_ENFORCEMENT" : true...

Looks like we have consensus with no reference node. I'll turn on enforcement :grin: "88107" : "yEeSSUjQKPVJKZYeMRtaRiSoUqYuid3Wuv:10", "88108" : "yJX2hdQG7Uno57yzunutg4pj5xFzK4vJtx:10", "88109" : "yJX2hdQG7Uno57yzunutg4pj5xFzK4vJtx:10", "88110" ...