Search results

***************************** Please update to 11.2.4 ***************************** This update is for everyone on testnet (Normal clients, masternodes, miners, etc) - Protocol / Version bump to kick off older nodes. - Changed a relay rule, seemed to be causing significant problems for DS...

***************************** Please update to 11.2.3 ***************************** This update is for everyone on testnet (Normal clients, masternodes, miners, etc) - Protocol / Version bump to kick off older nodes. - Something is weird with masternode payment messages, please restart with...

The "Transaction not valid, please try again. Will retry..." isn't really an error anymore, the masternode will keep asking people to sign while they're still relaying entries. Each time they relay a few more inputs/outputs until the whole transaction is built. I've had 2 successful...

***************************** Please update to 11.2.2 ***************************** This update is for everyone on testnet (Normal clients, masternodes, miners, etc) - New Masternode Blinding Trickle System. Inputs are sent a few at a time, along with re-broadcasting other users inputs...

This issue has been fixed in the repo, but I'm still working on some blinding enhancements. Testing will start again after I'm done writing all of this.

***************************** Please update to 11.2.1 ***************************** This update is for everyone on testnet (Normal clients, masternodes, miners, etc) Updates: - Version/protocol bump - Fixed shared key usage, there were lots of "Downgrades" happening, which results in lower...

***************************** Please update to 11.2.1 ***************************** This update is for everyone on testnet (Normal clients, masternodes, miners, etc) Included in 0.11.2 so far: - Masternode Blinding (eduffield) - New Masternode Management Class (UdjinM6) - Masternode cache...

It's a bug and the reference node is being patched as we speak EDIT: The reference node is patched, this shouldn't happen anymore

We can go with #1, but allow users/masternode operators to use Tor if they like. In my opinion, it's a bad idea for us to base our technology off of something already highly scrutinized, it will make the system as a whole much more vulnerable.

Nope, that's completely separate.

The goal of Darkcoin was NEVER to support illegal markets. The goal is to provide a crypto-currency that does a better job at being a crypto-currency than Bitcoin does and compete with it. IX is a powerful addition to the technology and shouldn't be discounted. I just don't agree with your...

If that's true, can't a medium sized botnet take down Bitcoin? It only has ~6000 full nodes (https://getaddr.bitnodes.io/)? My experience with tor/i2p is quite limited, you could definitely be correct about this. I'll see if I can get a masternode running under tor/i2p to test them out.

Ah, ok. Yes that part can be fixed for sure.

That doesn't make the masternode owners anonymous. It just makes the communication a more secure. It doesn't protect the source of the communication at all, just the contents. Here's how you de-anonymize the masternodes in a system like that: http://arxiv.org/pdf/1405.7418v1.pdf Any...

OK, #1 it is! Thanks everyone

There's a couple of competing ideas that have been floating around and I'm not sure which one is superior. The basic question is, should the masternodes show their IPS or not? The answer everyone immediately comes up with is "No", but there are some trade offs to both systems. Keep in mind, the...

v0.11.1.25 - MANDATORY UPDATE Due to some pools taking advantage of paying the incorrect masternodes (on purpose), enabling enforcement failed earlier today. Please update to the latest version of the software, 11.1.25, which includes a much stronger policy for enforcing masternode payments...

Mandatory Update to 11.1.23 After thoroughly testing masternode payments on testnet, we were surprised when they didn't work properly on mainnet and caused issues. As it turns out someone found a way to alter the masternode payment messages in transit and cause this behavior on mainnet. This...

I tried activating enforcement earlier and the message didn't propagate correctly, as a result It looks like some clients are stuck on block 218580. Please check, if you are then restart with --reindex. This was fixed in 11.1.21, so we shouldn't have this problem again. Your client should match...

Downloads - 11.1.21 Core - All Users ******** Please Update to 11.1.21 if you can, once that's done we can turn on enforcement ********* * No cold start needed Source: https://github.com/darkcoin/darkcoin Compiled Binaries: https://www.darkcoin.io/downloads/ Updates: v0.11.1.20 - Limit IX to...