Search results

@xkcd Yepp, you've already spotted it :) We've activated spork21 yesterday. Shortly after that, I accidentally spent collaterals of 150 tMNs due to a bug in one of my provisioning scripts :D I've setup 300 new MNs with 0.16 and 75 with 0.15. Spork21 already caused multiple of the 0.15 MNs to...

Just released RC2: https://github.com/dashpay/dash/releases/tag/v0.16.0.0-rc2. @Pasta can you update the link in your post? We are still working on / investigating the mixing issues and plan to include a potential fix for RC3. We'd like to have RC2 rolled out on testnet as fast as possible so...

RC4 has been released today. It only contains a single fix for mixing on the masternode side, so only MNs need to update.

RC3 has been released today, please upgrade your nodes and re-test.

RC2 has been released yesterday, please upgrade your nodes and re-test.

Upgraded 75 MNs and letting this run for a few days.

Release candidate v0.15.0.0-rc4 is ready for testnet! Github release candidate: https://github.com/dashpay/dash/releases/tag/v0.15.0.0-rc4 Release notes are not ready yet and will be prepared in the next few days. Post will be updated. Gitian sigs can be found here...

There is still http://test.faucet.masternode.io/ which should have enough funds.

FYI, we solved this issue in a private conversation. The issue was a severely corrupted wallet.dat which caused Dash to abort everything.

I'd suggest to compres it with a tool of your choice and then send it to [email protected]. If it's too large for emails, upload it to transfer.sh and send me the link instead

Can you send me the debug.log from the data directory? As I'm not a Windows user, I unfortunately don't know where that file is located on your machine so hopefully someone else can give us that info.

@camosoul the docs and instructions are pretty good IMHO, and if details are missing/misleading then it is something that is usually fixed fast. Your babbling about bad documentation is out of place here tbh. When it comes to misconfiguration, everyone who has issues please run "dash-cli...

So, just had a private discussion with a MNO that had PoSe problems. Turned out that he was running a second copy of the same MN in a different location as a backup solution, which means he used the same BLS operator key on two instances of dashd. This is NOT supported and will lead to your node...

Can everyone who is affected please add these lines to dash.conf of the masternodes: debug=llmq debug=llmq-sigs debug=llmq-dkg Can you also give me protx hashes of failed MNs that you believe should not have failed? You can send these in private to me. So far, all cases that have been...

To add to what @thephez already wrote: There is no need to change anything in mining pool software in this release. The changes to the coinbase are internal and reflected in the coinbase_payload from the block template. So, as long as you just take that field 1:1 (which seems to be the case)...

v0.14.0.0-rc5 has just been released: https://github.com/dashpay/dash/releases/tag/v0.14.0.0-rc5 Please upgrade when you find time. This RC is very close to what's going to be the final version. This RC mostly contains bug fixes and performance improvements for LLMQ based ChainLocks and...

RC4 has just been released. Please upgrade masternodes. This RC contains some performance improvements which should give better results with the next InstantSend load tests on testnet.

@f8192 Thanks for reporting this. Just confirmed on my local node that there is indeed some tendency to only connect to 0.13 nodes. Turns out the reason is that most masternodes are running on non-default (19999) ports, which makes the address selection algorithm prefer non-masternodes, which...

@f8192 can you give me the transaction ID of these TXs and also the output of "getrawtransaction <txid> 1"?

You have just successfully tested LLMQ-based InstantSend, which is currently enabled on testnet ;) RC3 has just been released and can be found here: https://github.com/dashpay/dash/releases/tag/v0.14.0.0-rc3 Everyone please upgrade. We will start signalling the BIP9 deployment for DIP8 next...