Search results

New Version - v0.12.0.43 Fixed flooding issues Linux32: https://dashpay.atlassian.net/builds/browse/DASHL-DEV/latest/artifact/JOB1/gitian-linux-dash-dist//dash-0.12.0-linux32.tar.gz Linux64...

New Version - v0.12.0.43 Updates for unconfirmed denom bug. ** still compiling ** Linux32: https://dashpay.atlassian.net/builds/browse/DASHL-DEV/latest/artifact/JOB1/gitian-linux-dash-dist//dash-0.12.0-linux32.tar.gz Linux64...

Did they confirm? getmininginfo { "blocks" : 82861, "pooledtx" : 5, }

It looks like we just don't have enough miners on v42 yet, I have 61 transactions I'm mining atm { "blocks" : 82854, "currentblocksize" : 11718, "currentblocktx" : 11, "difficulty" : 0.02403653, "errors" : "", "genproclimit" : 1, "networkhashps" : 624025...

New Version - v0.12.0.42 Updates to fix block propagation issues Linux32: https://dashpay.atlassian.net/builds/browse/DASHL-DEV/latest/artifact/JOB1/gitian-linux-dash-dist//dash-0.12.0-linux32.tar.gz Linux64...

New Version - v0.12.0.41 DS Update - removed a couple time based limitations for DS. Masternodes need not update. Only people mixing should. Linux32: https://dashpay.atlassian.net/builds/browse/DASHL-DEV/latest/artifact/JOB1/gitian-linux-dash-dist//dash-0.12.0-linux32.tar.gz Linux64...

New Version - v0.12.0.41 I had a few clients not sync correctly, so I added a checkpoint. Currently compiling Linux32: https://dashpay.atlassian.net/builds/browse/DASHL-DEV/latest/artifact/JOB1/gitian-linux-dash-dist//dash-0.12.0-linux32.tar.gz Linux64...

New Version - v0.12.0.41 *** please delete chainstate/blocks/peers.dat and restart *** - Fixed a few banning issues - DS now uses single denominations -- should be faster Linux32...

New Version - v0.12.0.40 Please update your client, delete chainstate, blocks, mn*.dat, budget.dat and peers.dat then restart. Linux32: https://dashpay.atlassian.net/builds/browse/DASHL-DEV/latest/artifact/JOB1/gitian-linux-dash-dist//dash-0.12.0-linux32.tar.gz Linux64...

New Version - v0.12.0.39 **** compiling .39 currently *** - Added some functionality to track immature budget/props and then add them to the list when they mature. Linux32...

Can everyone search their logs for "invalid finalized budget" and post what it says the last few matches.

New Version - v0.12.0.38 - Fixed a couple client hang issues, it seems very stable thus far. Linux32: https://dashpay.atlassian.net/builds/browse/DASHL-DEV/latest/artifact/JOB1/gitian-linux-dash-dist//dash-0.12.0-linux32.tar.gz Linux64...

As everyone knows, we’ve been hard at work developing the version 12 release on testnet. To date, this is our largest release with nearly 21000 lines of changes to the codebase. Due to the massive amount of changes and some small glitches that we are continuing to debug, we’re going to delay the...

Unfortunately there's another client hanging issue that needs to be found before we can launch. I'll work on this today and then we'll launch once we're sure it's stable.

I forgot to disable the spork earlier when I released .37 and we're having a fork (.36 and .37 were incompatible). Can everyone please reindex?

I'm still not really sure what has changed since the vote? The original version, plus existing changes were all made prevote so they should still be favorable to everyone that voted. There's no change that was made to the system after the vote that was non-technical in nature. Maybe I'm missing...

I rephrased my question, but you answered to my original statement before I even clicked submit! I don't think it's changed at all from what we originally discussed, just the implementation strategy has. For example, I don't think they voted on if everyone was paid in 1 block, vs 10 blocks, vs...

What exactly is different that you're referring to? Having a series of payments per proposal at the end of the month?

New Version - v0.12.0.37 Fixed a bunch of minor bugs that Tante/moli found, along with a few issues that could have cropped up in the future. The GetBudget code is a bit different, so I had to turn off enforcement until the network updates. Once we update, I'll turn it back on and make sure...

Yep. There can only be 100 proposals and it's probably going to be much, much lower for awhile. If it's 10, that means the masternodes will have payments delayed by 25 minutes per month on average. I don't think they'll even notice.