So should I stop burdening the mainnet with false masternodes?? Or leave things as they are for debug purposes?
v0.10.15.x Testing
- Thread starter eduffield
- Start date
- Status
Started with a fresh Darkcoin directory using the test windows wallet, getting the same:
2014-10-11 07:52:41 send version message: version 70040, blocks=0, us=[2001:0:5ef5:79fb:1068:22e5:3f57:fe42]:9999, them=31.13.217.58:9999, peer=1
2014-10-11 07:52:41 Added 27 addresses from 5.45.101.232: 0 tried, 54 new
2014-10-11 07:52:41 27 addresses found from DNS seeds
2014-10-11 07:52:41 dnsseed thread exit
2014-10-11 07:52:41 trying connection 207.38.165.159:9999 lastseen=3.4days
2014-10-11 07:52:41 partner 31.13.217.58:9999 using obsolete version 70038; disconnecting
2014-10-11 07:52:41 ProcessMessage(version, 104 bytes) FAILED
2014-10-11 07:52:41 disconnecting node 31.13.217.58:9999
2014-10-11 07:52:42 connected 207.38.165.159:9999
2014-10-11 07:52:42 send version message: version 70040, blocks=0, us=[2001:0:5ef5:79fb:1068:22e5:3f57:fe42]:9999, them=207.38.165.159:9999, peer=2
2014-10-11 07:52:42 partner 207.38.165.159:9999 using obsolete version 70038; disconnecting
2014-10-11 07:52:42 ProcessMessage(version, 104 bytes) FAILED
2014-10-11 07:52:42 disconnecting node 207.38.165.159:9999
2014-10-11 07:52:42 trying connection 108.61.193.91:9999 lastseen=3.2days
2014-10-11 07:52:42 connected 108.61.193.91:9999
2014-10-11 07:52:42 send version message: version 70040, blocks=0, us=[2001:0:5ef5:79fb:1068:22e5:3f57:fe42]:9999, them=108.61.193.91:9999, peer=3
2014-10-11 07:52:43 partner 108.61.193.91:9999 using obsolete version 70038; disconnecting
2014-10-11 07:52:43 ProcessMessage(version, 104 bytes) FAILED
2014-10-11 07:52:43 disconnecting node 108.61.193.91:9999
2014-10-11 07:52:43 trying connection 37.235.55.79:9999 lastseen=5.1days
2014-10-11 07:52:43 connected 37.235.55.79:9999
2014-10-11 07:52:43 send version message: version 70040, blocks=0, us=[2001:0:5ef5:79fb:1068:22e5:3f57:fe42]:9999, them=37.235.55.79:9999, peer=4
2014-10-11 07:52:44 partner 37.235.55.79:9999 using obsolete version 70038; disconnecting
2014-10-11 07:52:44 ProcessMessage(version, 104 bytes) FAILED
What am I doing wrong?
2014-10-11 07:52:41 send version message: version 70040, blocks=0, us=[2001:0:5ef5:79fb:1068:22e5:3f57:fe42]:9999, them=31.13.217.58:9999, peer=1
2014-10-11 07:52:41 Added 27 addresses from 5.45.101.232: 0 tried, 54 new
2014-10-11 07:52:41 27 addresses found from DNS seeds
2014-10-11 07:52:41 dnsseed thread exit
2014-10-11 07:52:41 trying connection 207.38.165.159:9999 lastseen=3.4days
2014-10-11 07:52:41 partner 31.13.217.58:9999 using obsolete version 70038; disconnecting
2014-10-11 07:52:41 ProcessMessage(version, 104 bytes) FAILED
2014-10-11 07:52:41 disconnecting node 31.13.217.58:9999
2014-10-11 07:52:42 connected 207.38.165.159:9999
2014-10-11 07:52:42 send version message: version 70040, blocks=0, us=[2001:0:5ef5:79fb:1068:22e5:3f57:fe42]:9999, them=207.38.165.159:9999, peer=2
2014-10-11 07:52:42 partner 207.38.165.159:9999 using obsolete version 70038; disconnecting
2014-10-11 07:52:42 ProcessMessage(version, 104 bytes) FAILED
2014-10-11 07:52:42 disconnecting node 207.38.165.159:9999
2014-10-11 07:52:42 trying connection 108.61.193.91:9999 lastseen=3.2days
2014-10-11 07:52:42 connected 108.61.193.91:9999
2014-10-11 07:52:42 send version message: version 70040, blocks=0, us=[2001:0:5ef5:79fb:1068:22e5:3f57:fe42]:9999, them=108.61.193.91:9999, peer=3
2014-10-11 07:52:43 partner 108.61.193.91:9999 using obsolete version 70038; disconnecting
2014-10-11 07:52:43 ProcessMessage(version, 104 bytes) FAILED
2014-10-11 07:52:43 disconnecting node 108.61.193.91:9999
2014-10-11 07:52:43 trying connection 37.235.55.79:9999 lastseen=5.1days
2014-10-11 07:52:43 connected 37.235.55.79:9999
2014-10-11 07:52:43 send version message: version 70040, blocks=0, us=[2001:0:5ef5:79fb:1068:22e5:3f57:fe42]:9999, them=37.235.55.79:9999, peer=4
2014-10-11 07:52:44 partner 37.235.55.79:9999 using obsolete version 70038; disconnecting
2014-10-11 07:52:44 ProcessMessage(version, 104 bytes) FAILED
What am I doing wrong?
You are running on mainnet - 5.45.101.232 is a mainnet dnsseeder, port 9999 is mainnet
Did you set "testnet=1" in your darkcoin.conf?
in my case im on testnet
"version" : 101504,
"protocolversion" : 70040,
"walletversion" : 60001,
"balance" : 0.00000000,
"darksend_balance" : 0.00000000,
"blocks" : 45515,
"timeoffset" : -1,
"connections" : 10,
"proxy" : "",
"difficulty" : 0.25223717,
"testnet" : true,
"keypoololdest" : 1409011834,
"keypoolsize" : 1001,
"paytxfee" : 0.00000000,
"mininput" : 0.00001000,
"errors" : ""
"version" : 101504,
"protocolversion" : 70040,
"walletversion" : 60001,
"balance" : 0.00000000,
"darksend_balance" : 0.00000000,
"blocks" : 45515,
"timeoffset" : -1,
"connections" : 10,
"proxy" : "",
"difficulty" : 0.25223717,
"testnet" : true,
"keypoololdest" : 1409011834,
"keypoolsize" : 1001,
"paytxfee" : 0.00000000,
"mininput" : 0.00001000,
"errors" : ""
There is no difference between testnet and mainnet wallet binary - you switch by just adding testnet=1 to your config
I understand that for my MN, but do we have a darkcoin.conf in windows as well?There is no difference between testnet and mainnet wallet binary - you switch by just adding testnet=1 to your config
I've never looked outside the darkcoin roaming profile lol... I'm checking now...
Seems noone is mining on testnet - started my GPU, let's see if this works out
Block 45516 found! Please point some hashing power at testnetSeems noone is mining on testnet - started my GPU, let's see if this works out
Sure, difficulty is quite low on testnet - chaeplin mined on 1 CPU/thread for ages and got myriads of blocks
ok thx, im on it.Sure, difficulty is quite low on mainnet - chaeplin mined on 1 CPU/thread for ages and got myriads of blocks
It's something in the debug window, something along the lines of "set generate 1" to use 1 core. "set generate -1" to use all available cores.sorry for this question here, where can i find howto mine my own wallet hunder windows
Block 45516 found! Please point some hashing power at testnet
I've got 20Mh/s to spare...what are the pool details?
Just put "setgenerate true" in your debug console, it will use the built in miner
No pool yet - either solomine or wait till i have nomp up and running
Jeeze flare, I've been waiting like foreverNo pool yet - either solomine or wait till i have nomp up and running
. Solo mine it is. no problemo.
Be aware that your 20MH/s will currently mine 80% of all blocks, i have only 2MH/s
When nomp is running lemme know, I'll chuck a few rigs at you as well...Be aware that your 20MH/s will currently mine 80% of all blocks, i have only 2MH/s
I'll keep it pointed at a main net pool then. Only trying to helpBe aware that your 20MH/s will currently mine 80% of all blocks, i have only 2MH/s
I've only ever just run the Darkcoin QT executable after downloading, that time I actually ran the installer and noticed a Darkcoin directory in Program Files etc, I wonder what the difference is...Sure, windows wallet uses the same code as darkcoind
darkcoin.conf is located at %APPDATA%\DarkCoin - if not you need to create it
Anyhow, I created a file called darkcoin.conf and put testnet=1, dropped it in my roaming profile and voila... I saw a peach splash screen and I'm on testnet...
Thiat was too easy, thanks Flare...
There is no difference - the installer is just copying the darkcoin-qt.exe to Program FIles - along with the source code
- Status