Search results

Great notes, just my inner grammar nazi kicks in: participants not partisipants :tongue: P.S: Sorry :sad:

Wont be an issue with the rc4 release though, due to the changes to the voting system all their blocks will be orphaned if they dont comply with the MN payments.

This would have nothing to do to multi investors really. think you understanding it wrong

This multi ticket solution is not a good idea: 1. Reduces the number of MNs, which decreases resiliency. 2. If malicious party infiltrated the large pot MN, you will have a compromised coinjoin service. i.e. This is back to the centralised coinjoin problem again.

2014-05-26 08:11:08 ERROR: CheckBlock() : Bad vote detected 2014-05-26 08:21:52 ERROR: CheckBlock() : Bad vote detected 2014-05-26 08:26:48 ERROR: CheckBlock() : Bad vote detected 2014-05-26 08:45:48 ERROR: CheckBlock() : Bad vote detected 2014-05-26 11:06:15 ERROR: CheckBlock() : Bad vote...

No, if you wanna run masternode you need the 10.8.6

double quotes will can attempt to expand some of the characters that are used in your password, the single quotes will take it at a face value, example: host:~$ test="this is a test" host:~$ echo $test this is a test host:~$ echo "$test" this is a test host:~$ echo '$test' $test

7500kh/s seems quite low actually, I could easily get 2.4Mh/s from my 7970 (under linux and OC-ed) with this config: https://gist.github.com/Scriptiee/e925a6d8b339c0eec264 And tbh if you believe in the long term valuation of this coin mining now will not be at a loss. I was mining bitcoin...

-daemon will run it in the background. When entering your password in the command line just put it between ' ' (singelquotes) like this: darkcoind walletpassphrase 'mycra$yp@ssphrase' 60 This ill ensure that bash is not trying to interpret any special characters contained inside of your password

Are you starting your darkcoind witth 'darkcoind -daemon' ?

If you weren't in another country on the otherside of the planet I would totally give you a pat on the back. Well done mate!!! Keep it up!

ahh , could not see that with the font here, my bad

think that would be a better way of getting the correct count darkcoind masternode list | grep ' : 1' | sort -n | uniq | wc -l your will match ips that have a 1 in them as well

from what I can see the main net is kinda divided in 3 if it comes to wallet versions, take I a masternode or stable wallet. It is hard to tell what is really going on until everyone updates their wallets to the correct versions (or at least majority of people)

Still getting different results between the stable and the RC for the masternode votes. $ ./darkcoind getinfo { "version" : 100804, "protocolversion" : 70015, "walletversion" : 60000, "balance" : 1000.00000000, "blocks" : 71587, "timeoffset" : 0, "connections" : 15...

You updated your local wallet to the latest version as well yeah? I found that adding the addnode=23.23.186.131 to my local wallet allowed it to sync faster and correctly display the info. It probably is due to the network being divided into 2 currently (in a way)

$ darkcoind getinfo { "version" : 90402, "protocolversion" : 70015, "walletversion" : 60000, "balance" : 102.18701116, "blocks" : 70580, "timeoffset" : 0, "connections" : 8, "proxy" : "", "difficulty" : 1600.07248364, "testnet" : false, "keypoololdest"...

{ "70565" : "OP_DUP OP_HASH160 84b3b76e57961b021eebda3f693ee9b0ba16d886 OP_EQUALVERIFY OP_CHECKSIG", "70566" : "OP_DUP OP_HASH160 6fa380600134982350cc440d7f2be0e0095272fb OP_EQUALVERIFY OP_CHECKSIG", "70567" : "OP_DUP OP_HASH160 3b7cb7a63e631b067161fc20d5214045741cab58 OP_EQUALVERIFY...

Hmm getting the same here :/ very odd EDIT: and yeah the new wallet is not showing any masternodes being active at the moment, is this a mandatory update for current masternodes?

it's the same really, you already had a 644 permission on it, and doing +x added 1 to each of these numbers making it 755