v0.10.9.x Help test RC2 forking issues

Status
Not open for further replies.
I'm still getting MN payment. Still flag :0.
I only check by opening the "local" wallet.dat in the qt wallet. Then I close the qt wallet after a few minutes.
The "remote" MN is always running. I also enabled setgenerate true on the remote MN, if that makes a difference. It has found 3 blocks. It's a core2duo dell D430 with 2GB of RAM. The last block it found was over 900 blocks ago.
Code: 
getinfo
{
    "version" : 100909,
    "protocolversion" : 70018,
    "walletversion" : 60000,
    "balance" : 360.80000000,
    "blocks" : 16542,
    "timeoffset" : -1,
    "connections" : 23,
    "proxy" : "",
    "difficulty" : 0.67739235,
    "testnet" : true,
    "keypoololdest" : 1401930356,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "mininput" : 0.00001000,
    "errors" : ""
}
{
"account" : "",
"address" : "mwunMQV81M62BND26fhTn5W4AZRc129h4t",
"category" : "generate",
"amount" : 120.00000000,
"confirmations" : 933,
"generated" : true,
"blockhash" : "00000000ee7593a57a2c4b392a14bbb120e39b0e787f9bb49a1e87b667ce7660",
"blockindex" : 0,
"blocktime" : 1402157939,
"txid" : "6c40d7a6f9a6b2b7784a7fac226633145f3977b870e9a5c99013fdc7e1826660",
"time" : 1402157939,
"timereceived" : 1402157939
}
]
[/code]
Code: 
masternode list
{
    "98.165.130.67:19999" : 1,
    "184.73.179.148:19999" : 1,
    "184.73.179.187:19999" : 1,
    "184.73.179.196:19999" : 1,
    "188.226.133.22:19999" : 1,
    "188.226.248.36:19999" : 1,
    "188.226.243.116:19999" : 1,
    "37.187.47.129:19999" : 1,
    "23.242.106.27:19999" : 0,
    "68.32.185.63:19999" : 0,
    "104.33.210.231:19999" : 0,
    "54.203.217.224:19999" : 1,
    "108.61.199.47:19999" : 1,
    "93.188.161.89:19999" : 0,
    "211.99.224.198:19999" : 1,
    "54.76.47.232:19999" : 1,
    "54.86.103.191:19999" : 1
}
 
archLinuxUser said:
I'm still getting MN payment. Still flag :0.
I only check by opening the "local" wallet.dat in the qt wallet. Then I close the qt wallet after a few minutes.
The "remote" MN is always running. I also enabled setgenerate true on the remote MN, if that makes a difference. It has found 3 blocks. It's a core2duo dell D430 with 2GB of RAM. The last block it found was over 900 blocks ago.
Code: 
getinfo
{
    "version" : 100909,
    "protocolversion" : 70018,
    "walletversion" : 60000,
    "balance" : 360.80000000,
    "blocks" : 16542,
    "timeoffset" : -1,
    "connections" : 23,
    "proxy" : "",
    "difficulty" : 0.67739235,
    "testnet" : true,
    "keypoololdest" : 1401930356,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "mininput" : 0.00001000,
    "errors" : ""
}
{
"account" : "",
"address" : "mwunMQV81M62BND26fhTn5W4AZRc129h4t",
"category" : "generate",
"amount" : 120.00000000,
"confirmations" : 933,
"generated" : true,
"blockhash" : "00000000ee7593a57a2c4b392a14bbb120e39b0e787f9bb49a1e87b667ce7660",
"blockindex" : 0,
"blocktime" : 1402157939,
"txid" : "6c40d7a6f9a6b2b7784a7fac226633145f3977b870e9a5c99013fdc7e1826660",
"time" : 1402157939,
"timereceived" : 1402157939
}
]
[/code]
Code: 
masternode list
{
    "98.165.130.67:19999" : 1,
    "184.73.179.148:19999" : 1,
    "184.73.179.187:19999" : 1,
    "184.73.179.196:19999" : 1,
    "188.226.133.22:19999" : 1,
    "188.226.248.36:19999" : 1,
    "188.226.243.116:19999" : 1,
    "37.187.47.129:19999" : 1,
    "23.242.106.27:19999" : 0,
    "68.32.185.63:19999" : 0,
    "104.33.210.231:19999" : 0,
    "54.203.217.224:19999" : 1,
    "108.61.199.47:19999" : 1,
    "93.188.161.89:19999" : 0,
    "211.99.224.198:19999" : 1,
    "54.76.47.232:19999" : 1,
    "54.86.103.191:19999" : 1
}
Click to expand...
can you post remote server getpeerinfo and getinfo ?
 
Did anyone receive a masternode payment more than TWO hours after turning off the masternode? Payments can be delayed up to an hour, maybe even two hours if the hashrate is slowing.

TTL is 35 minutes + payments can take up to 10 blocks after getting elected. So if you get elected exactly 34 minutes after you turn the node off, then it takes 10 blocks at 3-4 minutes per block you're at about an hour and a half after you turned it off.
 
eduffield said:
Did anyone receive a masternode payment more than TWO hours after turning off the masternode? Payments can be delayed up to an hour, maybe even two hours if the hashrate is slowing.

TTL is 35 minutes + payments can take up to 10 blocks after getting elected. So if you get elected exactly 34 minutes after you turn the node off, then it takes 10 blocks at 3-4 minutes per block you're at about an hour and a half after you turned it off.
Click to expand...
How viable would it be for a malicious person to setup a ton of empty-wallet masternodes then write a script where the 1000drk are transferred from node wallet to node wallet taking advantage of that lag time?
 
I don't think that would be a problem, because it takes 1/2 an hour to show up, at that point it's sort of like being on all the time. The reason/way the one masternode gets paid so late is because it was elected just before turning itself off, then it's a matter of waiting for it's reward. A new node can't be elected until it shows up on the system, which is about the same amount of time as going off the system. So you would lose up-time because you'd have to transfer funds which takes time.

Why does it take so long to show up on the list?
 
chaeplin said:
Hmm
please test this.
at local, add addnode=remoteip to conf.
check if remoteip is connected, getpeerinfo will show remoteip if connected.
after then, start masternode.
Click to expand...
I did as you instructed and it's been over 30 minutes but the remote ip doesn't show up on my local when I do getpeerinfo. What might I have done wrong? Here is my config:

Code: 
rpcuser=WootWoot
rpcpassword=la;iueljraalkdfOIUUOIJPIOTY***IIjkaruoUOjfera
masternodeaddr=54.215.181.251:19999
masternodeprivkey=91rpLavb52g4zvPVo1Dfkjvd6DZo9FzYmMYYcJfjyeLKmHC3opb
addnode=23.23.186.131:19999
addnode=54.215.181.251:19999
testnet=1
maxconnections=256
masternode=1

Should we still be starting our remote darkcoind with the "darkcoind masternodeaddr=ipofremote:19999" command?

Also, we never do any kind of "masternode start" on the remote node?
 
Last edited by a moderator:
TanteStefana said:
I did as you instructed and it's been over 30 minutes but the remote ip doesn't show up on my local when I do getpeerinfo. What might I have done wrong? Here is my config:

Code: 
rpcuser=WootWoot
rpcpassword=la;iueljraalkdfOIUUOIJPIOTY***IIjkaruoUOjfera
masternodeaddr=54.215.181.251:19999
masternodeprivkey=91rpLavb52g4zvPVo1Dfkjvd6DZo9FzYmMYYcJfjyeLKmHC3opb
addnode=23.23.186.131:19999
addnode=54.215.181.251:19999
testnet=1
maxconnections=256
masternode=1
Click to expand...

Oh.. local ip should be listed in remote server, not in local.

Meaning remote 19999 is not opened or remote is not 54.215~~.
 
Last edited by a moderator:
chaeplin said:
Oh.. local ip should be listed in remote server, not in local.

Meaning remote 19999 is not opened or remote is not 54.215~~.
Click to expand...
Oh dang!!!! I thought about the port, but kept thinking it was open for some reason, but the TESTNET port is NOT open on my amazon, ROFL. With me it's always something super obvious but my mind blocks it, ROFL :confused: Welp, sorry to take up everyone's time, I'm glad you can't reach me to smack me upside the head! LOL
 
TanteStefana said:
Oh dang!!!! I thought about the port, but kept thinking it was open for some reason, but the TESTNET port is NOT open on my amazon, ROFL. With me it's always something super obvious but my mind blocks it, ROFL :confused: Welp, sorry to take up everyone's time, I'm glad you can't reach me to smack me upside the head! LOL
Click to expand...
One of my job was help desk for internet connection ;D
added : dial-up
 
Hi, i'm setting up a testnet masternode. Can you send 1k to mimbetjLREPGTgWMbeHiwU8yTGKqgNn3z2
Thanks
 
So, as it turns out there's no bug. When the checkpointer is enabled, any blocks that pay out the wrong amount are orphaned and a new chain is started.
merge said:
Hi, i'm setting up a testnet masternode. Can you send 1k to mimbetjLREPGTgWMbeHiwU8yTGKqgNn3z2
Thanks
Click to expand...

Sent!
 
Just got back and updated, successfully started masternode.

from the darkcoind masternode list

"98.165.130.67:19999" : 1,
"184.73.179.148:19999" : 1,
"184.73.179.187:19999" : 1,
"188.226.133.22:19999" : 1,
"188.226.248.36:19999" : 1,
"188.226.243.116:19999" : 1,
"37.187.47.129:19999" : 1,
"68.32.185.63:19999" : 1,
"104.33.210.231:19999" : 1,
"54.203.217.224:19999" : 1,
"108.61.199.47:19999" : 1,
"93.188.161.89:19999" : 1,
"54.76.47.232:19999" : 1,
"54.86.103.191:19999" : 1,
"87.230.94.57:19999" : 1,
"211.99.224.198:19999" : 1,
"84.25.161.117:19999" : 1,
"37.187.216.11:19999" : 1,
"54.255.159.230:19999" : 1
Click to expand...

Mine is the last one.
It got instantly picked up by chaeplin's list

54.255.159.230:19999 1 f912e108979186ce9e4782dc150a12ef25397c00e15749767ede9eba9b9b3dbe moqpGCABQQefuujQ9nsAMJVEiwAXyAMw6o 1000.0
Click to expand...
 
Wooooooaahh !! What just happened? MN list just got humungous! Like... holy crap!
 
Hi all

Please could some one send me some test coins
mgW35d9qQQjN3D66U957rirpZE57XPftjR
Just a quick question on my local pc i`m on:







"version" : 100909,
"protocolversion" : 70018,
"walletversion" : 60000,
"balance" : 0.00000000,
"blocks" : 16765,
"timeoffset" : 0,
"connections" : 4,
"proxy" : "",
"difficulty" : 0.49529906,
"testnet" : true,
"keypoololdest" : 1402340303,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"mininput" : 0.00001000,
"errors" : ""
}

on my ec2 server i`m on :

"version" : 90411,
"protocolversion" : 70015,
"walletversion" : 60000,
"balance" : 0.00000000,
"blocks" : 0,
"timeoffset" : 0,
"connections" : 0,
"proxy" : "",
"difficulty" : 0.00024414,
"testnet" : true,
"keypoololdest" : 1402338091,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"mininput" : 0.00001000,

Please could someone explain or direct me on how to update my ec2 sever to rc3

Many Thanks
 
flare said:
eduffield said:
The checkpointer is now actively enforcing the rules for masternode payments. Can everyone check and see if they're on the same blockchain?

http://23.23.186.131:1234/chain/DarkCoin

I've checked all of my clients, everything is looking great as far as I can tell.
Click to expand...

I am trying to solomine some 33% blocks on my side to test it :smile:
Click to expand...

Mined two blocks (16778 and 16779) with 33% MN payout - checkpointer not intercepting so far

EDIT: Blocks got orphaned :smile: checkpointer working!

So am i getting this right: The blocks are only checked for validity regarding MN payout by the central checkpointer at the moment?

https://github.com/darkcoinproject/darkcoin/blob/forkfix/src/main.cpp#L2628 translates to "only if you are the checkpoint master, check the blocks for masternode payouts validity"

So the checkpoint master is a specially compiled darkcoind version for this purpose (to include private master key) and this machine will be a bottleneck and target for DDoS attacks, since the clients/miners are not capable to check the payouts for validity by themselves. If checkpointmaster is not available the miners will confirm any payout ratio after the usual 150 block confirmations.
 
Last edited by a moderator:
Status
Not open for further replies.
Back
Top