Search results

Yeah, the simply answer is to just make sure you're on the chain with the highest difficulty. That's going to be the one explorer.darkcoin.io, so as long as their last block hash matches the explorer, then they're good.

Nope, nearly all of the miners are up-to-date. The problem was "mnw" messages failed to propagate to part of the network, which then couldn't tell who to pay. So we just had fragmentation.

The entire cause of the fork appears to be network fragmentation, so masternode payments will remain non-enforced until we have a good portion of the network on a recent version.

I've just made a masternode from scratch on windows and successfully started a remote machine on linux, which in turn started pinging. 1.) Start the remote masternode 2.) Open your local wallet, with the 1000DRK, then type "masternode outputs". You should see the output you're trying to start...

I've tested v0.11.0.11 with a remote masternode and everything seems to function correctly, nothing was changed that would cause any problems. However if you run "masternode start" on a remotely activated masternode, it's state will be reset and it'll stop pinging (this existed on all v11...

v0.11.0.11 This is the last protocol bump and we're moving back to testnet, sorry about all the updates I just wanted DS to be as secure as possible before moving on to InstantX. There's going to be 1 more version (11.0.12) after this with some stability fixes (still some segfaults happing for...

Hah, apparently I missed a whole page of comments. Looks like we're on the right track though. I also like Minotaur's suggestion also, maybe we should even go further? 100.00100000 DRK 10.00010000 DRK 1.00001000 DRK 0.10000100 DRK 0.01000010 DRK (disabled presently) 0.00100001...

Ah, I just read your post about convertibility (missed it somehow). However, I did implement a fix to the issue you describe in 11.0.10, as it was a known issue. The solution is that if you submit 1DRK x 10, you'll get back 1DRK x 10 back with no change. Beyond that, I've added a lot of random...

Try re-syncing from scratch and see if it goes away?

Ah, I misread your original statement. By exact amounts, I meant if you ask for 1000DRK, the new algo will give you 1000 DRK of denoms to anonymize.

Do a getinfo and make sure it says 110010. If that doesn't work, can you give me all of the transaction IDs in the new wallet? It definitely shouldn't be possible

11.0.10 Core - All Users Source: https://github.com/darkcoin/darkcoin Windows .exe: https://github.com/darkcoinproject/darkcoin-binaries/raw/master/darkcoin-0.11.0.10-win.zip Mac OSX: https://raw.githubusercontent.com/d...in-binaries/master/darkcoin-0.11.0.10-osx.dmg Linux...

11.0.9 Core - All Users Source: https://github.com/darkcoin/darkcoin Windows .exe: https://github.com/darkcoinproject/darkcoin-binaries/raw/master/darkcoin-0.11.0.9-win.zip Mac OSX: https://raw.githubusercontent.com/darkcoinproject/darkcoin-binaries/master/darkcoin-0.11.0.9-osx.dmg Linux...

Hey, I've read through your posts and I believe all issues you bring up are presently fixed in 11.0.8. UdjinM6 wrote a nice patch which entirely removes non-denomination DRK from being in the pool at all. I'm going to compile and release this version in the morning, as a nice side effect, mixing...

Please email me directly, I'd love to talk about it: [email protected]

V11 just became a mandatory update: https://darkcointalk.org/threads/mandatory-all-users-must-update-to-v11.3619/#post-36936

Try --reindex

We have seen an issue on the network, which comes from a disagreement between v10 and v11 clients. It appears to be an issue the network has always had, but never caused an issue until we upgraded the core client. This caused the v11 client to get stuck this morning, when a block was created and...

Yikes, that's really weird.

Should be working now