v0.10.17.x Testing

Status
Not open for further replies.
defunctec said:
What's the command to set how many IX confirmation's you want?
Click to expand...
--instantxdepth=6 was what Evan used in his demonstration video. I don't think we can IX yet though, MN's don't seem to be networking too well.

Seeing some IX type stuff on stdout though:
Code: 
ProcessMessageInstantX::txlreq
signing strMessage c6c1ae0df77f26ed5bf516c057dbcb398354653dde10537cf0fc30607f3edb7e707711
signing privkey 932ZyRKNcwwW7ijevLJGMQEEQJxz8cuSM7nig8P5MYTvoQX9uHq
signing pubkey2 msK3EXq5V6NHthvYKSQCbcAkSdciaPzAxU
verify strMessage c6c1ae0df77f26ed5bf516c057dbcb398354653dde10537cf0fc30607f3edb7e707711
verify addr 50.254.73.148:19999
verify addr 176.126.241.100:19999
verify addr 1 176.126.241.100:19999
verify pubkey2 msK3EXq5V6NHthvYKSQCbcAkSdciaPzAxU
InstantX::DoConsensusVote --- connected, sending vote 50.254.73.148:19999
ProcessMessageInstantX::txlreq - Transaction Lock Request: 188.165.205.82:19999 /Satoshi:0.10.16.5/ : accepted c6c1ae0df77f26ed5bf516c057dbcb398354653dde10537cf0fc30607f3edb7e
 
Last edited by a moderator:
I've run through all these steps yet I'm still getting inbound port is not open. Please open it and try again.
 
Does everybody see 10 tMNs?

{
"64.251.69.134:19999" : 1,
"188.226.225.170:19999" : 1,
"178.62.203.249:19999" : 1,
"50.254.73.148:19999" : 1,
"107.170.168.162:19999" : 1,
"50.254.73.146:19999" : 1,
"50.254.73.149:19999" : 1,
"50.254.73.147:19999" : 1,
"107.170.157.216:19999" : 1,
"86.20.185.139:19999" : 1
}
 
skillit said:
I've run through all these steps yet I'm still getting inbound port is not open. Please open it and try again.
Click to expand...
Post your local and remote darkcoin.conf files, we might be able to help. The error you mention usually means you haven't opened 19999 on yout MN or there's a typo in a conf somewhere.
 
Raico said:
Just wake up and get the wonderful news~!
4 tMN on the way~


Edit:
very strange thing happened. On the local, my qt wallet shows
successfully started masternode but on the remote: all my 4 tMN says not capable masternode
here is some info that may help:
Code: 
"version" : 101700,
    "protocolversion" : 70046,
    "walletversion" : 60001,
    "balance" : 0.00000000,
    "darksend_balance" : 0.00000000,
    "blocks" : 70769,
    "timeoffset" : -1,
    "connections" : 11,
    "proxy" : "",
    "difficulty" : 0.73593487,
    "testnet" : true,
    "keypoololdest" : 1412930615,
    "keypoolsize" : 1001,
    "paytxfee" : 0.00000000,
    "mininput" : 0.00001000,
    "errors" : ""
btw: i've took part in the testing for many times. And the testing environment is the same as last time (maybe 10.16.5). The only different is the new client(10.17.0).


Well, corrected: They show on the masternode list
Is there a wrong feedback when you have successfully setup the masternode remotely but got the not capable masternode massage? is it only me or anyone else?

Nevermind. My mistake. I found local shows everything correct but the remote seems not. Will delete block chainstats peer and debug then try is again.
Click to expand...


After deleting all my block, chainstat, peer, log files (Both local & remote). And do it again on my 4 tMN. Still haven't setup the tMN successfully.

in local, it report successfully started masternode and it's in the masternode list (later it disappear if i closed the local client)
snapshot39.png


in remote:
snapshot42.png

masternode debug :
not capable masternode

Edit:
snapshot43.png



very strange~
 
Last edited by a moderator:
Lukas_Jackson said:
Does everybody see 10 tMNs?

{
"64.251.69.134:19999" : 1,
"188.226.225.170:19999" : 1,
"178.62.203.249:19999" : 1,
"50.254.73.148:19999" : 1,
"107.170.168.162:19999" : 1,
"50.254.73.146:19999" : 1,
"50.254.73.149:19999" : 1,
"50.254.73.147:19999" : 1,
"107.170.157.216:19999" : 1,
"86.20.185.139:19999" : 1
}
Click to expand...
I see only 9:

{
"50.254.73.146:19999" : 1,
"50.254.73.148:19999" : 1,
"64.251.69.134:19999" : 1,
"50.254.73.149:19999" : 1,
"50.254.73.147:19999" : 1,
"188.226.225.170:19999" : 1,
"178.62.203.249:19999" : 1,
"107.170.168.162:19999" : 1,
"107.170.157.216:19999" : 1
}
 
Lukas_Jackson said:
Does everybody see 10 tMNs?

{
"64.251.69.134:19999" : 1,
"188.226.225.170:19999" : 1,
"178.62.203.249:19999" : 1,
"50.254.73.148:19999" : 1,
"107.170.168.162:19999" : 1,
"50.254.73.146:19999" : 1,
"50.254.73.149:19999" : 1,
"50.254.73.147:19999" : 1,
"107.170.157.216:19999" : 1,
"86.20.185.139:19999" : 1
}
Click to expand...
Nope.
MN:
Code: 
{
  "50.254.73.148:19999" : 1,
  "176.126.241.100:19999" : 1,
  "64.251.69.134:19999" : 1,
  "50.254.73.149:19999" : 1,
  "50.254.73.147:19999" : 1,
  "188.226.225.170:19999" : 1,
  "178.62.203.249:19999" : 1,
  "107.170.168.162:19999" : 1
}
Local:
Code: 
{
  "50.254.73.148:19999" : 1,
  "50.254.73.146:19999" : 1,
  "64.251.69.134:19999" : 1,
  "50.254.73.147:19999" : 1,
  "50.254.73.149:19999" : 1
}
 
Official testnet explorer display X address, not m.

Only seeing 5 nodes atm, same 5 as above but they do seem to be v.17
 
Not having luck getting 20 testnet masternodes online with version 0.10.17.0.
Ports 19999 listening (externally verified), logs show happy signs:

Code: 
2014-11-28 06:47:32 CActiveMasternode::RegisterAsMasterNode() - Is capable master node!
2014-11-28 06:47:32 CActiveMasternode::RegisterAsMasterNode() - Adding myself to masternode list 162.243.76.23:19999 - CTxIn(COutPoint(de664d6b8dee103e8ef4b93df62288a2c836000907a659f568bf2ed0bb7bf217, 0), scriptSig=)
2014-11-28 06:47:32 CActiveMasternode::RegisterAsMasterNode() - Masternode input = CTxIn(COutPoint(de664d6b8dee103e8ef4b93df62288a2c836000907a659f568bf2ed0bb7bf217, 0), scriptSig=)

But none of them show up in either https://test.drk.mn/masternodes.html or my desktiop qt (v17) instance.

Tried all the usual tricks: delete peers.dat, add externalip, add masternodeminprotocol=70046 -- no joy.

(ignore the v0.16.16 entry in test.drk.mn, started wrong version once. Is a dead entry):

Code: 
ubuntu@node-01:~/testnet$ darkcoind -datadir=. getinfo
{
    "version" : 101700,
    "protocolversion" : 70046,
    "walletversion" : 60001,
    "balance" : 3705.10204772,
    "darksend_balance" : 0.00000000,
    "blocks" : 70903,
    "timeoffset" : 0,
    "connections" : 3,
    "proxy" : "",
    "difficulty" : 0.83244417,
    "testnet" : true,
    "keypoololdest" : 1415838109,
    "keypoolsize" : 1001,
    "paytxfee" : 0.00000000,
    "mininput" : 0.00001000,
    "errors" : ""
}
 
And thank you flare for being the brains and hard work behind my good intentions. You've seen what happens when somebody in my line of work tries to get technical :D
 
stonehedge said:
I have given flare 15 instances to be used as testnet masternodes for a few months. Hopefully this will help make the most mature test environment possible. Lets make this the biggest and best testnet yet! My free time is limited but I can't wait to get involved.
Click to expand...
Holy cow!!! You sir are a gentleman and a scholar! Hopefully flare has more luck then the rest of us getting masternodes into the list!

Edit: If anyone wants to donate MN instances to testnet I'd be more then happy to look after any ones that flare can't maintain.
 
That's very kind of you to say so but lets face it, making testnet as "real" as possible for InstantTX testing needs to be a community priority. Lets do this! (He says as he runs off to work late)
 
Status
Not open for further replies.
Back
Top