v0.10.9.x Help test RC2 forking issues

Status
Not open for further replies.
Wouldn't it be nice if you could send testnet coins to mainnet? Good attempt, we've all tried at one point or another. :wink:
 
Hi again...

thanks for patience guys... I had the RC3 binaries, but did not know to include testnet=1 into darkcoin.conf...
now I really am on testnet (also wallet sw shows it in title) :)
Sorry for confusion.
Here is my address: muu6HVowG7rQatYCagd1QcaxjTqN1ecayM

thanks,
W


TanteStefana said:
Maybe he doesn't know, LOL. To join testnet, get the RC3 wallet on the first post, then post your address, it'll start with an M or N or somesuch. I'll send you dark ;) You seem to have the regular wallet.
Oh, and you need to put this in your config file;
Code: 
rpcuser=me
rpcpassword=tralalalalalalalalala123$%^blahblahSOMECAPSTOO
server=1
port=19999
masternodeprivkey=weirdlongnuber if you want to run one
addnode=23.23.186.131
testnet=1
rpcallowip=127.0.0.1
maxconnections=256
masternode=0

If you do want to run a masternode on testnet, then you need to start darkcoind, then do darkcoind getkey..... or was it darkcoind masternode getkey? I forget... and put it next to masternodeprivkey=___ above :) Then set masternode= to 1 instead of 0

Yikes, memory sucks, it's : ./darkcoind masternode genkey
Click to expand...
 
Awaiting for my testnet darkcoins :) ... Can someone please send me first 1000, so I can start playing with MN. Thank you!

Wallet shows 10 connections, so everything looks ok... 14076 blocks of transactions history... OK?
 
Last edited by a moderator:
weirdgod said:
Awaiting for my testnet darkcoins :) ... Can someone please send me first 1000, so I can start playing with MN. Thank you!

Wallet shows 10 connections, so everything looks ok... 14076 blocks of transactions history... OK?
Click to expand...
1k sent. enjoy :smile:
 
Ah, BrainShudown beat me to it. Here is another 1k to play with...
darkcoind sendtoaddress muu6HVowG7rQatYCagd1QcaxjTqN1ecayM 1000.0"
1d390c1314603b63c309a430aae65a2bcab7aa11b514ee96d809ae97ad8a9c4a
 
We should split our mining power. P2Pool seems not to find any blocks currently.

Or wait, all the blocks are orphaned. What's going on with P2Pool?
 
http://tdrk.poolhash.org/ and http://23.23.186.131:1234/chain/DarkCoin are on different chains.

Code: 
ubuntu@ip:~$ darkcoind getinfo
{
    "version" : 100903,
    "protocolversion" : 70015,
    "walletversion" : 60000,
    "balance" : 51292.71173104,
    "blocks" : 14139,
    "timeoffset" : 0,
    "connections" : 8,
    "proxy" : "",
    "difficulty" : 0.45385921,
    "testnet" : true,
    "keypoololdest" : 1401783372,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "mininput" : 0.00001000,
    "errors" : ""
}
ubuntu@ip:~$ darkcoind getblockhash 14139
00000000710a3022cea14d01f9a3b6b228539877503918517b4449c768dae110
 
My node has this log.
I will backup log and restatrt with 9.5.3
from 14131 , different chain.
Code: 
2014-06-05 00:04:27 ProcessSyncCheckpoint: pending for sync-checkpoint 00000000710a3022cea14d01f9a3b6b228539877503918517b4449c768dae110

2014-06-05 00:04:27 ProcessSyncCheckpoint: pending for sync-checkpoint 00000000710a3022cea14d01f9a3b6b228539877503918517b4449c768dae110

2014-06-05 00:04:28 ProcessSyncCheckpoint: pending for sync-checkpoint 00000000710a3022cea14d01f9a3b6b228539877503918517b4449c768dae110

2014-06-05 00:04:28 ProcessMessages(block, 207 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length

2014-06-05 00:04:28 ProcessMessage(block, 207 bytes) FAILED

2014-06-05 00:04:28 ProcessMessages(block, 371 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length

2014-06-05 00:04:28 ProcessMessage(block, 371 bytes) FAILED

2014-06-05 00:04:31 ProcessSyncCheckpoint: pending for sync-checkpoint 000000008e44396520693acf1cf90801a57b1dd80fb1d1500a411bdea29ac4f3

2014-06-05 00:04:31 ProcessSyncCheckpoint: pending for sync-checkpoint 000000008e44396520693acf1cf90801a57b1dd80fb1d1500a411bdea29ac4f3

2014-06-05 00:04:31 ProcessSyncCheckpoint: pending for sync-checkpoint 000000008e44396520693acf1cf90801a57b1dd80fb1d1500a411bdea29ac4f3

2014-06-05 00:04:32 ProcessMessages(block, 207 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length

2014-06-05 00:04:32 ProcessMessage(block, 207 bytes) FAILED

2014-06-05 00:04:32 ProcessMessages(block, 371 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length

2014-06-05 00:04:32 ProcessMessage(block, 371 bytes) FAILED

2014-06-05 00:04:40 ProcessMessages(block, 207 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
 
Last edited by a moderator:
synced.

masternode count is zeroed.

Code: 
12 "subver" : "/Satoshi:0.10.9.2/",
2 "subver" : "/Satoshi:0.10.9.3/",
1 "subver" : "/Satoshi:0.9.5.2/",
2 "subver" : "/Satoshi:0.9.5.3/",
 
eduffield said:
*** Please update to 10.9.3 or 9.5.3 ***

I think I've fixed all of our masternode voting problems and 1/2 of the ghost masternode problem. I'll fix the other half tomorrow.
Click to expand...
I know you must have a loving mom, so I'm just asking if I can adopt you as a nephew, are you game? LOL You're a wonderful young man! I've been waiting all my life to be able to call young people "kiddo" but I realized I disliked being called that, so I can't get myself to do it :confused: But I think young man is ok, at least I hope so! I mean it with deep respect!
 
Upgraded to 10.9.3. So far I am the only masternode in the network:
{
"54.76.52.216:19999" : 1
}

I've noticed that the votes list started with just one entry:
./darkcoind masternode votes

{
"14153" : "OP_DUP OP_HASH160 0d82037de937dc7d3d6136eb7c19b13a8b588e57 OP_EQUALVERIFY OP_CHECKSIG"
}

but now it's up to three (the same) entries a few minutes later (I am still the only MN the moment I checked this):
{
"14153" : "OP_DUP OP_HASH160 0d82037de937dc7d3d6136eb7c19b13a8b588e57 OP_EQUALVERIFY OP_CHECKSIG",
"14154" : "OP_DUP OP_HASH160 0d82037de937dc7d3d6136eb7c19b13a8b588e57 OP_EQUALVERIFY OP_CHECKSIG",
"14155" : "OP_DUP OP_HASH160 0d82037de937dc7d3d6136eb7c19b13a8b588e57 OP_EQUALVERIFY OP_CHECKSIG"
}

Not sure if it's anything out of the ordinary, but someone mentioned duplicate votes a few pages earlier.
 
I was just going to say the same thing, that I am the only masternode on the network. But I know that's not true because my other one is on as well, but maybe because I started that one first, it sees itself and my second masternode but nobody else. The blocks are rising regularly... I'm on block 14166 on both, but internet slow, can't get on blockchain explorer....
 
Well, one of my nodes shows
"54.193.124.32:19999" : 1,
"54.215.181.251:19999" : 1,
"98.165.130.67:19999" : 1

And the other shows
"54.215.181.251:19999" : 1,
"98.165.130.67:19999" : 1

I wonder why one of mine doesn't see the other? I also wonder if only 3 masternodes have been updated so far?
 
TanteStefana said:
Well, one of my nodes shows
"54.193.124.32:19999" : 1,
"54.215.181.251:19999" : 1,
"98.165.130.67:19999" : 1

And the other shows
"54.215.181.251:19999" : 1,
"98.165.130.67:19999" : 1

I wonder why one of mine doesn't see the other? I also wonder if only 3 masternodes have been updated so far?
Click to expand...

nodes are not updated fully.

http://tdrk.poolhash.org/blocks/subver.txt

Code: 
1 "subver" : "/Satoshi:0.10.7.3/",
1 "subver" : "/Satoshi:0.10.9.1/",
22 "subver" : "/Satoshi:0.10.9.2/",
5 "subver" : "/Satoshi:0.10.9.3/",
2 "subver" : "/Satoshi:0.9.2.2/",
2 "subver" : "/Satoshi:0.9.5.3/",

my node see 5
Code: 
54.76.52.216:19999 : 1,
54.193.124.32:19999 : 1,
54.215.181.251:19999 : 1,
98.165.130.67:19999 : 1,
184.73.179.148:19999 : 1

nomp node see 5 also
Code: 
   "54.76.52.216:19999" : 1,
    "54.193.124.32:19999" : 1,
    "54.215.181.251:19999" : 1,
    "98.165.130.67:19999" : 1,
    "184.73.179.148:19999" : 1
 
kktr said:
Not sure if it's anything out of the ordinary, but someone mentioned duplicate votes a few pages earlier.
Click to expand...

It was me that mentioned that, but that was different as i was having identical votes in the same block

TanteStefana said:
I wonder why one of mine doesn't see the other? I also wonder if only 3 masternodes have been updated so far?
Click to expand...

Same here, updared my 3 nodes to 0.10.9.3 and only seeing my own nodes voting for themselves...

chaeplin said:
my node see 5
Click to expand...

My nodes only see themselves and a maximum of one other

*.148 sees
Code: 
{
    "184.73.179.148:19999" : 1,
    "184.73.179.196:19999" : 1
}


*.187 sees
Code: 
{
    "184.73.179.187:19999" : 1,
    "184.73.179.196:19999" : 1
}


*.196 (last one restarted) only sees
Code: 
{
    "184.73.179.196:19999" : 1
}

EDIT:

Additonally no votes make it to the blockchain

http://184.73.179.148:1234/chain/DarkCoin
http://184.73.179.187:1234/chain/DarkCoin
http://184.73.179.196:1234/chain/DarkCoin

EDIT2:

Ok, masternode payments not started yet :rolleyes:

Code: 
"masternode_payments" : false
 
Last edited by a moderator:
chaeplin said:
nodes are not updated fully.

http://tdrk.poolhash.org/blocks/subver.txt

Code: 
1 "subver" : "/Satoshi:0.10.7.3/",
1 "subver" : "/Satoshi:0.10.9.1/",
22 "subver" : "/Satoshi:0.10.9.2/",
5 "subver" : "/Satoshi:0.10.9.3/",
2 "subver" : "/Satoshi:0.9.2.2/",
2 "subver" : "/Satoshi:0.9.5.3/",

my node see 5
Code: 
54.76.52.216:19999 : 1,
54.193.124.32:19999 : 1,
54.215.181.251:19999 : 1,
98.165.130.67:19999 : 1,
184.73.179.148:19999 : 1

nomp node see 5 also
Code: 
   "54.76.52.216:19999" : 1,
    "54.193.124.32:19999" : 1,
    "54.215.181.251:19999" : 1,
    "98.165.130.67:19999" : 1,
    "184.73.179.148:19999" : 1
Click to expand...
Mine sees 8:
"54.203.217.224:19999" : 1,
"54.76.52.216:19999" : 1,
"54.193.124.32:19999" : 1,
"54.215.181.251:19999" : 1,
"98.165.130.67:19999" : 1,
"184.73.179.148:19999" : 1,
"184.73.179.187:19999" : 1,
"184.73.179.196:19999" : 1
Click to expand...

Can someone tell a noob how to figure out what my MN hash would be that shows in the voting?
Code: 
ubuntu@ip-10-252-204-115:~$ darkcoind masternode votes
{
    "14187" : "OP_DUP OP_HASH160 a83cc7c0004906c57957d420e7dbc19cbc8c2fdb OP_EQUALVERIFY OP_CHECKSIG",
    "14188" : "OP_DUP OP_HASH160 a83cc7c0004906c57957d420e7dbc19cbc8c2fdb OP_EQUALVERIFY OP_CHECKSIG",
    "14189" : "OP_DUP OP_HASH160 012ca2df8c1a5c77c794dd5b9237e595d86d5bf3 OP_EQUALVERIFY OP_CHECKSIG",
    "14190" : "OP_DUP OP_HASH160 7f898281b5ca5b7ec9385e04421b4e2a1aa008d4 OP_EQUALVERIFY OP_CHECKSIG",
    "14191" : "OP_DUP OP_HASH160 012ca2df8c1a5c77c794dd5b9237e595d86d5bf3 OP_EQUALVERIFY OP_CHECKSIG",
    "14192" : "OP_DUP OP_HASH160 012ca2df8c1a5c77c794dd5b9237e595d86d5bf3 OP_EQUALVERIFY OP_CHECKSIG",
    "14193" : "OP_DUP OP_HASH160 0d82037de937dc7d3d6136eb7c19b13a8b588e57 OP_EQUALVERIFY OP_CHECKSIG",
    "14194" : "OP_DUP OP_HASH160 34d7e6bdc2a0131d752f03b6410839657d8d9edc OP_EQUALVERIFY OP_CHECKSIG",
    "14195" : "OP_DUP OP_HASH160 012ca2df8c1a5c77c794dd5b9237e595d86d5bf3 OP_EQUALVERIFY OP_CHECKSIG",
    "14196" : "OP_DUP OP_HASH160 a83cc7c0004906c57957d420e7dbc19cbc8c2fdb OP_EQUALVERIFY OP_CHECKSIG"
}
 
Status
Not open for further replies.
Back
Top