v0.10.9.x Help test RC2 forking issues

Status
Not open for further replies.
Ok...

I fired up my MN nº2 to update, still on version v0.10.9.6-16-gaff5d03-beta. Its listed as :1 and still getting payed.

ubuntu@ip-172-31-3-203:~$ darkcoind getinfo
{
"version" : 100910,
"protocolversion" : 70018,
"walletversion" : 60000,
"balance" : 60.20000000,
"blocks" : 18308,
"timeoffset" : 0,
"connections" : 9,
"proxy" : "",
"difficulty" : 0.53303890,
"testnet" : true,
"keypoololdest" : 1401985547,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"mininput" : 0.00001000,
"errors" : ""
}
Click to expand...

http://23.23.186.131:1234/address/moqpGCABQQefuujQ9nsAMJVEiwAXyAMw6o
 
eduffield said:
From here on I'm going to be setting rough deadlines (Late June) for projects because the coding is what is unpredictable. Then after everything is working and everyone signs off on the release setting a firm date via the code and pushing out the changes to the network. The vast majority of the network can update in 8 days, so that's definitely not an issue. If it were more complicated of an update, I'd set it further out.
Click to expand...

I back the decision by Evan and signed off on the release. The last days we have driven various attacks on the masternode network and voting system, and as far as we can see there were no forks or other hickups. Evan was even able to remove the temporary checkpointer solution, which caused headache for some people (including me).

RC3 is more mature than RC2 was, fixing various problems including

- perma forking on payment dissent
- hot/cold wallet support
- ghost masternodes
- basic proof-of-service support

As the testnet has an average size of 70(!) masternodes, 3 pools and another 30ish clients, we are quite confident that all scenarios that could arise in mainnet are addressed.

But lets stay clear: A go-live is a go-live, and has its own rules. But the core team is here to address any issue which will arise. DRK will go places!

flare, Darkcoin QA
 
(Tante, close your eyes for this one please!!)

I just got a major boner. Which makes me uneasy, as caused by male specimen of the DRK coding species. Huge man-crush on flare and Evan.
Wow !! So this is it?

Fasten your seat belts, gentlemen!! (and gentlewomen(s)!)
 
Team,

Should we request key personnel from pools and exchanges to be there in a private IRC room with us during hard fork? This should be as important to them as it is to anyone not mining or trading. Typically collaboration like that is not expected and it is their prerogative to participate or not, but it was a big lesson from RC2. It was frustrating to see pool ops not checking in IRC and posting on forums where there was enough confusion already. It took a long time to get hold of Pheeleep when everyone else was on the correct emergency fork.

Also we should be prepared for any potential emergencies/fallouts just in case things are not going to perfection.

Is p2pool ready for the HF? I think it was another cause of concern as p2pool nodes were coming online last time.
 
tifozi said:
Team,

Should we request key personnel from pools and exchanges to be there in a private IRC room with us during hard fork? This should be as important to them as it is to anyone not mining or trading. Typically collaboration like that is not expected and it is their prerogative to participate or not, but it was a big lesson from RC2. It was frustrating to see pool ops not checking in IRC and posting on forums where there was enough confusion already. It took a long time to get hold of Pheeleep when everyone else was on the correct emergency fork.

Also we should be prepared for any potential emergencies/fallouts just in case things are not going to perfection.

Is p2pool ready for the HF? I think it was another cause of concern as p2pool nodes were coming online last time.
Click to expand...
Join #darkcoin-test on freenode. This is were the people start to panic during hard forks :)
I will poke dstorm about p2pool. The fix is trivial and I guess he will update the repository in time.
 
After updating my testnet masternode from 0.10.4.11 to 0.10.10 I get:

Code: 
$ darkcoind masternode start
inbound port is not open. Please open it and try again. (19999 for testnet and 9999 for mainnet)

My conf has:
Code: 
externalip=54.76.47.232
masternodeaddr=54.76.47.232:19999

Any idea? I'm using the iptables rules from chaeplins thread.
 
vertoe said:
After updating my testnet masternode from 0.10.4.11 to 0.10.10 I get:

Code: 
$ darkcoind masternode start
inbound port is not open. Please open it and try again. (19999 for testnet and 9999 for mainnet)

My conf has:
Code: 
externalip=54.76.47.232
masternodeaddr=54.76.47.232:19999

Any idea? I'm using the iptables rules from chaeplins thread.
Click to expand...
I think you don't need masternodeaddr.
Try without it.

If fail, wait other node is connected to NM's port 19999.
Then try.

Please let me know the result.
 
chaeplin said:
I think you don't need masternodeaddr.
Try without it.

If fail, wait other node is connected to NMs port 1999.
Then try.

Please let me know the result.
Click to expand...
I tried both, first without and then with masternodeaddr=...
Still no success...
 
vertoe said:
Join #darkcoin-test on freenode. This is were the people start to panic during hard forks :)
I will poke dstorm about p2pool. The fix is trivial and I guess he will update the repository in time.
Click to expand...

I am aware of the test room and I am there. I meant more in terms of a separate private room with representation from pool ops and exchanges.
 
vertoe said:
I tried both, first without and then with masternodeaddr=...
Still no success...
Click to expand...

Vertoe, are you running hot only, or cold/remote? mastenodeaddr=xx.xx.xx.xx:19999 goes in the local conf file, not the remote. Also, if you're on EC2 (or other VPS) double check that you have TCP inbound port open. Should only be SSH port 22 locked to your local IP, then 9999 mainnet on 0.0.0.0, and also 19999 on 0.0.0.0 (meaning anywhere)
 
Just installed the latest RC3. testnet:true
Could someone pls send 1000 DRK to:
msDJSxrCw3Hin2J1pNbfKK5jz65JhxvKDW

Just trying to see if my setup is okay.
Thanks!
 
This has been the longest run without payouts. Installed 9.13 this morning, its been 13:30 hours without payouts. Masternode shows up fine, no problems that I'm aware of. Guys think this is expected? The other node (10.9.6) that has been running for a while got 5 payouts today.
 
flare said:
So it's not that trivial to determine what the actual payee/amount vout was :cool:
Click to expand...
20 % get my attention.

I have found, as you mentioned, I can't bet vout[1].
block 18490 : http://23.23.186.131:1234/block/00000001a06c978076f1e55b62a2d2e8be9f1248d3053180af0c44c3b006831d
http://tdrk.poolhash.org/blocks/masterlist/18490.txt
Votes show next block will have no payee.

block 18491 :
http://23.23.186.131:1234/block/000000017a009eb3a5a0c1d2c613a857fe50265a849b1e161667294cc75085d3
http://tdrk.poolhash.org/blocks/masterlist/18491.txt


1 hour ago06/13 08:08:4014184910.540150unknownmt2ScQSwpsohN8KC9CuFGCuCuvyJkCY8iE148.505

My payout checking scripts should be changed.

This was my thought.
real time
- Get mastenode list pubkey, compare to vout
- or Use getblocktemplate

past block
- Sum of vout * 0.2, matched vout address

Then block 18491 get my attention.
http://tdrk.poolhash.org/blocks/masterlist/18491.txt

No payment block has vout[1] with huge amount.

If a user uses his Masternode address as username of a direct payment pool like p2pool.
Or nomp pool owner uses his Masternode address for pool fee address.

What will be happend ?

Is there p2pool opened for testing ?
(I will change my nomp..)


RESULT:
I have changed nomp rewardRecipients.
"mkLN57jC9sYqMkp8RBcJF2H9hvhz6vabwQ": 25
(one of masternode)
http://184.73.179.148:1234/block/00000001827bbf913c4e39a1cb9939f0675727ddb3630e13bfab9b3273abd5cc

Two masternode address ;D.

I should learn how to read votes result in past block.

TransactionFeeSize (kB)From (amount)To (amount)
e379b47d2e...00.191Generation: 150 + 0 total feesmq6hAJRXkH94a2Dp38akBj1LwNNP8tubJV: 90
miVBSbPnpdhGLhmqXzic7VyUuCQWqENv87: 30
mkLN57jC9sYqMkp8RBcJF2H9hvhz6vabwQ: 30
837645c9d9...00.192mq6hAJRXkH94a2Dp38akBj1LwNNP8tubJV: 120.8moQD1AbtbDgPhDCXhK5x9rkUQrTHK3ZE7H: 120.8


: Status of payment is inaccurate now LOL
http://tdrk.poolhash.org/blocks/masterpay.txt
http://tdrk.poolhash.org/verify/masterverify.txt
 
Last edited by a moderator:
Hi everyone, here I am again trying to get the remote wallet to work. I keep ending up on the masternode list with my local wallet on my home computer's iP address. I have every port open, with the security thingy at amazon, and I used Chaeplin's tutorial to set up a fresh Ubuntu 14.04 amazon EC2 tiny. Instead of following with the 9999 port, I used 19999. I did use 19998 for the rcp (hope that was right?)

My local darkcoin.conf looks like this:
Code: 
rpcuser=Name
rpcpassword=blahblah
masternodeaddr=54.193.124.32:19999
masternodeprivkey=92u4E3pc3YCyqEATiWP2YfMhkLBSmnBzFV4wKZMvVoQiTkgX42E
addnode=23.23.186.131:19999
addnode=54.193.124.32:19999
testnet=1
maxconnections=256
masternode=1
listen=1
server=1
daemon=1
logtimestamp=1

And my remote looks like this:
Code: 
rpcuser=DiffName
rpcpassword=diffblahblah
listen=1
server=1
daemon=1
logtimestamps=1
externalip=54.193.124.32:19999
masternodeprivkey=92u4E3pc3YCyqEATiWP2YfMhkLBSmnBzFV4wKZMvVoQiTkgX42E
addnode=23.23.186.131:19999
testnet=1
maxconnections=256

If anyone could help, I'd sure appreciate it. Also, has anyone noted that they've had success doing this? Thank :)
 
TanteStefana said:
Hi everyone, here I am again trying to get the remote wallet to work. I keep ending up on the masternode list with my local wallet on my home computer's iP address. I have every port open, with the security thingy at amazon, and I used Chaeplin's tutorial to set up a fresh Ubuntu 14.04 amazon EC2 tiny. Instead of following with the 9999 port, I used 19999. I did use 19998 for the rcp (hope that was right?)

My local darkcoin.conf looks like this:
Code: 
rpcuser=Name
rpcpassword=blahblah
masternodeaddr=54.193.124.32:19999
masternodeprivkey=92u4E3pc3YCyqEATiWP2YfMhkLBSmnBzFV4wKZMvVoQiTkgX42E
addnode=23.23.186.131:19999
addnode=54.193.124.32:19999
testnet=1
maxconnections=256
masternode=1
listen=1
server=1
daemon=1
logtimestamp=1

And my remote looks like this:
Code: 
rpcuser=DiffName
rpcpassword=diffblahblah
listen=1
server=1
daemon=1
logtimestamps=1
externalip=54.193.124.32:19999
masternodeprivkey=92u4E3pc3YCyqEATiWP2YfMhkLBSmnBzFV4wKZMvVoQiTkgX42E
addnode=23.23.186.131:19999
testnet=1
maxconnections=256
Click to expand...
I will try to setup one.
 
Aw, thank you chaeplin, I'm sorry I'm being such a butt, I'm also sure it'll end up being something super stupid, LOL
 
chaeplin said:
I should learn how to read votes result in past block.

[...]

: Status of payment is inaccurate now LOL
http://tdrk.poolhash.org/blocks/masterpay.txt
http://tdrk.poolhash.org/verify/masterverify.txt
Click to expand...

Like i wrote: With current blockchain implementation it's not trivial to determine what the actual MN payment vout of a generation tx was, as the vote winner from last block is not easy to retrieve.

eduffield is facing the same challenge in his CheckBlock() method, and has to scan the votes of the previous block to determine if the current block is valid.

Maybe we should extend blockchain to include payee info to facilitate validity check and stat retrieval in RC4?

Till then you will have no other choice than to scan previous block votes for accurate MN payout stats :)

BTW: are you planning to push all new tools you developed from tdrk.poolhash.org to mainnet as well? I find them extremely useful, and some glitches i found would have been a lot harder to find without them. It's my swiss knife for debugging DRK blockchain - keep up with this brilliant work :)
 
Last edited by a moderator:
flare said:
Like i wrote: With current blockchain implementation it's not trivial to determine what the actual MN payment vout of a tx was, as the vote winner from last block is not easy to retrieve.

eduffield is facing the same challenge in his CheckBlock() method, and has to scan the votes of the previous block to determine if the current block is valid.

Maybe we should extend blockchain to have payee info to facilitate validity check and stat retrieval in RC4?

Till then you will have no other choice than to scan previous block votes for accurate MN payout stats :)

BTW: are you planning to push all new tools from tdrk.poolhash.org to mainnet as well? I find them extremely useful, and some glitches i found would have been harder to find without them. Keep up with this brilliant work :)
Click to expand...

Hmm I should run getblocktemplate and record it to file.

http://drk.poolhash.org/masternode.html has new info. Address, lastseen, activeseconds.

drkcoin.io and poolhash are perpectely synced . ;D
 
Status
Not open for further replies.
Back
Top