v0.10.11.x RC3 Prelaunch Testing
- Thread starter eduffield
- Start date
- Status
daaarkcoins
Member
just updated to 10.11.2
is that right?
Code:
darkcoind getblockhash 24644
00000000595195f2b1d69ade26c69c39321daec7edb238f8748ac99b7e044aa8is that right?
flare
Well-known member
Yep
Code:
./darkcoind getblockhash 24644
00000000595195f2b1d69ade26c69c39321daec7edb238f8748ac99b7e044aa8flare
Well-known member
I think the estimation stat of the client got confused by the blockchain reversal Evan did. As soon as 24639 is reached the clients will "unstuck". So more cosmetic than a issue right now.
Testnet seems stable so far
HammerHedd
Active member
OK, got a p2pool set up and mining on testnet at 54.88.71.248:18998. Once I've got some testnet DRK, I'll try setting up a masternode as well.
I'm curious to see how p2pool handles the change to MN payments....
I'm curious to see how p2pool handles the change to MN payments....
Last edited by a moderator:
finally got home to check... all my blocks where good and I am at block 24771. I just let it run and it worked itself out.I think the estimation stat of the client got confused by the blockchain reversal Evan did. As soon as 24639 is reached the clients will "unstuck". So more cosmetic than a issue right now.
Testnet seems stable so far
give me an address to send some drk to for testnet
HammerHedd
Active member
darkcoind sendtoaddress mghAuBWNMdeqm5TzvevY5i91nqd6Kyj17A 3333
8d93ea34ef4f4b3cdea66231a2d736a1fc9ad9fe119ebdd03b5d0b628af31b9c
HammerHedd
Active member
Thanks a bunch... one masternode up, and I"m trying to remote the other.. not as easy as I thought it would be lol
minersday
Member
not a big deal but tdrk,poolhash,org
show the ip _._.45.36 listed twice, with two different wallet addresses.
mvTxKB6Akb2rk9jC1JAZLyw2Lu9PwpwUDF was originally correct, but I added new address alongside that address (mjeLkyqoDXGrAD6JXGtKNkdaZu6T6WsnBp) with 1000 tDRKs.
There were the case that two different machines had the same wallet / same masternodekey but with different IPs..
-----
EDIT: and 5 masternodes are up, setting up 5 more later..
show the ip _._.45.36 listed twice, with two different wallet addresses.
mvTxKB6Akb2rk9jC1JAZLyw2Lu9PwpwUDF was originally correct, but I added new address alongside that address (mjeLkyqoDXGrAD6JXGtKNkdaZu6T6WsnBp) with 1000 tDRKs.
There were the case that two different machines had the same wallet / same masternodekey but with different IPs..
-----
EDIT: and 5 masternodes are up, setting up 5 more later..
Last edited by a moderator:
chaeplin
Well-known member
mvTxKB6Akb2rk9jC1JAZLyw2Lu9PwpwUDF is inactive.
ip is not a key. vin(aka pubkey/vin) is primary key.
(maybe part of multiple 1k holding to 1 ip)
mjeLkyqoDXGrAD6JXGtKNkdaZu6T6WsnBpDNA OyFinland
mvTxKB6Akb2rk9jC1JAZLyw2Lu9PwpwUDFDNA OyFinland
http://tdrk.poolhash.org/blocks/masterlist.txt (thanks guys!)
is showing duplicate actives after 30 minutes.
Node caching bad entry? or web page?
update: node finally went inactive, but proper *FFm address still missing
page shows:
nodes show:
is showing duplicate actives after 30 minutes.
Node caching bad entry? or web page?
update: node finally went inactive, but proper *FFm address still missing
page shows:
Code:
mfpSMCgkVjrtkSVhfswSWUsdbRUxU6gFFm 034e7d69106de61044ba46079b3c4c893cd73802 64.32.6.185:19999 1 1403677737417273 1563 34646
mpgNHgxhtGHhYX98wam8X9DWzpNMNaNuEA 6480e797bbf4ef1838d8ac4a9aa1d7f2e6b2f538 64.32.6.185:19999 1 1403677935575317 1365 10762
mzCKvrXb42KekMJcFGhneNVnJRcuRPc5Mt cce48bd2c49675e73d49d45c0f633de72367430d 208.98.43.109:19999 1 1403677708108963 1592 22779nodes show:
Code:
$ for x in 1 2 3 ; do echo $x ; ssh drk-$x darkcoind masternode list | grep 9999 | grep "\ 1" | sort -u | egrep "64.32.6.172|208.98.43.109|64.32.6.185" ; done
1
"208.98.43.109:19999" : 1,
"64.32.6.172:19999" : 1
"64.32.6.185:19999" : 1,
2
"208.98.43.109:19999" : 1,
"64.32.6.172:19999" : 1
"64.32.6.185:19999" : 1,
3
"208.98.43.109:19999" : 1,
"64.32.6.172:19999" : 1
"64.32.6.185:19999" : 1,
$ for x in 1 2 3 ; do echo $x ; ssh drk-$x darkcoind masternode list pubkey | grep 9999 | sort -u | egrep "64.32.6.172|208.98.43.109|64.32.6.185" ; done
1
"208.98.43.109:19999" : "mzCKvrXb42KekMJcFGhneNVnJRcuRPc5Mt",
"64.32.6.172:19999" : "mfpSMCgkVjrtkSVhfswSWUsdbRUxU6gFFm"
"64.32.6.185:19999" : "mpgNHgxhtGHhYX98wam8X9DWzpNMNaNuEA",
2
"208.98.43.109:19999" : "mzCKvrXb42KekMJcFGhneNVnJRcuRPc5Mt",
"64.32.6.172:19999" : "mfpSMCgkVjrtkSVhfswSWUsdbRUxU6gFFm"
"64.32.6.185:19999" : "mpgNHgxhtGHhYX98wam8X9DWzpNMNaNuEA",
3
"208.98.43.109:19999" : "mzCKvrXb42KekMJcFGhneNVnJRcuRPc5Mt",
"64.32.6.172:19999" : "mfpSMCgkVjrtkSVhfswSWUsdbRUxU6gFFm"
"64.32.6.185:19999" : "mpgNHgxhtGHhYX98wam8X9DWzpNMNaNuEA",
Last edited by a moderator:
chaeplin
Well-known member
page : http://tdrk.poolhash.org/blocks/masterlist.txt
Code:
address hash160 ip status lastseen sec(ago) activeseconds
mzCKvrXb42KekMJcFGhneNVnJRcuRPc5Mt cce48bd2c49675e73d49d45c0f633de72367430d 208.98.43.109:19999 1 1403679508364428 692 24579
mfpSMCgkVjrtkSVhfswSWUsdbRUxU6gFFm 034e7d69106de61044ba46079b3c4c893cd73802 64.32.6.185:19999 0 1403677737417273 2463 34646
mpgNHgxhtGHhYX98wam8X9DWzpNMNaNuEA 6480e797bbf4ef1838d8ac4a9aa1d7f2e6b2f538 64.32.6.185:19999 1 1403679735695332 465 12562server side
Code:
darktest@sv1:~/scripts> darkcoind masternode list | grep 6.185
"64.32.6.185:19999" : 0,
"64.32.6.185:19999" : 1,
darktest@sv1:~/scripts> darkcoind masternode list pubkey | grep 6.185
"64.32.6.185:19999" : "mfpSMCgkVjrtkSVhfswSWUsdbRUxU6gFFm",
"64.32.6.185:19999" : "mpgNHgxhtGHhYX98wam8X9DWzpNMNaNuEA",
darktest@sv1:~/scripts>
darktest@sv1:~/scripts> darkcoind masternode list pubkey | grep 6.172
darktest@sv1:~/scripts> darkcoind masternode list | grep 6.172
darktest@sv1:~/scripts>stat page http://tdrk.poolhash.org/
mfpSMCgkVjrtkSVhfswSWUsdbRUxU6gFFmSharktechUnited States
mpgNHgxhtGHhYX98wam8X9DWzpNMNaNuEASharktechUnited States
I think key mfpSMCgkVjrtkSVhfswSWUsdbRUxU6gFFm has problem.
This bothers me the most:
I think the cache has a problem still. Restarting daemon repopulates cache with valid addresses/ip's, but we can't expect the entire network to restart in sync.
I think the cache has a problem still. Restarting daemon repopulates cache with valid addresses/ip's, but we can't expect the entire network to restart in sync.
chaeplin
Well-known member
Check other node's debug.log.
mfpSMCgkVjrtkSVhfswSWUsdbRUxU6gFFm has issue.
https://www.darkcointalk.org/threads/help-test-rc2-forking-issues.1009/page-44#post-8910
New ip, New Address, New Genkey.
edit:
https://www.darkcointalk.org/threads/new-version-9-4-0-and-10-8-0.690/
Code:
Masternodes now sign their 1000DRK vin for the first message to the network,
then they specific a second pubkey that they will sign all further messages with.
This second signing key must be specified for all masternodes in the configuration with the option "masternodeprivkey"
"masternode genkey" : generates a completely random key that is never used in the wallet and has no funds associated with it.1000DRK vin ==> Pubkey ==> Specific Genkey.
If vin/pubkey is changed, Genkey should be changed also.
Otherwise network will not be noticed.
Last edited by a moderator:
chaeplin
Well-known member
done ;D
edit:
oh ~~ doubled.
Code:
darktest@sv1:~> darkcoind sendtoaddress msYutqQEWZffG1Suabe68NSbdeBtq2DFnQ 1000
3ba2f373dbbc355a0e5b262e280df27f6a385634f060fb8217e002cad2a8477f
darktest@sv1:~> darkcoind sendtoaddress mxXzjr3E1AtMGwauVbZ5NNHsaecnXhXdA8 1000
ebf1870ce7279849d96bc0350d83c02599b8fa62a5ce708dff48cda50863b309
darktest@sv1:~> darkcoind sendtoaddress mhYnT3kUwuZr68ECQMvaVywCwZNVWmmpcT 1000
4acc22b882cdbaf6f5e50cb64442c38d767e0bad936d2edc83027e3832a560c4
darktest@sv1:~> darkcoind sendtoaddress mkwhKitKC8g44QUwb68okX4Ac8m6GqDWQx 1000
bc1a187bcc6c979d04e2d0ed69d4c518efed53bcff0bb7853f9f1995029565ab
darktest@sv1:~> darkcoind sendtoaddress mjPo4a6zS3L8GvWZCjDNVG3GeYwc9vQYmA 1000
70fc00ebe63529261041973ea28ada0f8f0c93b04b35fb257409ebc9fa772cea- Status