• Forum has been upgraded, all links, images, etc are as they were. Please see Official Announcements for more information

v0.10.9.x Help test RC2 forking issues

Status
Not open for further replies.
eduffield said:
***** Update to 9.5.6 or 10.9.6 ********
This update provides hot/cold masternode support!

  • To setup, copy the configuration options masternode=1 and masternodeprivkey=KEY from your daemon with the 1000DRK to the hot daemon.
  • Add masternodeaddr=HOTMASTERNODEIP:19999 to your COLD daemon.
  • On the hot daemon run "masternode debug" you should see "Missing masternode input, please look at the documentation for instructions on masternode creation"
  • On the cold daemon run "masternode start"
  • In the debug log of the hot daemon you should see "CDarkSendPool::EnableHotColdMasterNode() - Enabled! You may shut down the cold daemon."
  • You may now turn off the cold node, but DO NOT move the funds. This will immediately disable your masternode.

------------------------

There's also a fix for ghost masternodes (there was still a problem), TTL is now 30 minutes and the protocol is not backwards compatible. So please update!

Binaries (stable)
http://www.darkcoin.io/downloads/forkfix/darkcoin-qt
http://www.darkcoin.io/downloads/forkfix/darkcoind

RC3 Binaries ( masternodes )
http://www.darkcoin.io/downloads/rc3/darkcoin-qt
http://www.darkcoin.io/downloads/rc3/darkcoind
Click to expand...
So I'm trying this out now, and I want to be clear, we never actually do masternode start on the hot wallet? Because the remote wallet isn't working for me the way Evan described doing it? Anyone got remote wallet working?

I think this is me:
2014-06-08 03:51:27 CDarkSendPool::NewBlock - Is Masternode, resetting
2014-06-08 03:51:27 ProcessBlock: ACCEPTED

but as you can see it's not a cold wallet, and I see my home's ip on the list, so no go :*( How do you do this properly. I did it per Evan verbatim.
 
Last edited by a moderator:
chaeplin said:
TanteStefana said:
Is the RC3 wallet also updated ?
Click to expand...

No I don't think so.
There must be a code to check the amount of payment.

Anyway I will restart nomp with 20% payment.
Click to expand...

The code you are looking for is here https://github.com/darkcoinproject/darkcoin/blob/forkfix/src/main.cpp#L5367-L5375

The reward was raised by Evan 2 days ago -- https://github.com/darkcoinproject/...72#diff-7ec3c68a81efff79b6ca22ac1f1eabbaL5356

eduffield said:
chaeplin,

This will set the masternode payments to 20%. Can you update NOMP? I just added a pull request to have this merged in.

lib/transactions.js
136 :
var payeeReward = Math.ceil(reward / 5);

https://github.com/zone117x/node-stratum-pool/pull/79/commits
Click to expand...

Evan, do i get this right: The pools stratum code is deciding the amount to pay (10% vs. 20%), not the miners? I mean, the payout amount raise was around in the clients for 2 days (since 0.9.5.3) but the 20% payout by the pools first started when the pools external code got changed.

There were even alternating payouts during the transition phase (depending on whether the pool was updated or not i guess)

Block 15779 --> 20%
Block 15780 --> 20%
Block 15781 --> 10%
Block 15782 --> 20%
Block 15783 --> 20%
Block 15784 --> 10%
Block 15785 --> 20%
Block 15786 --> 20%
Block 15787 --> 20%
Block 15788 --> 10%

Wouldn't it be a better approach to have the network itself check/confirm the correct value of the MN payout for each block through block confirmations (just like you do with the votes)?

Currently the client/pool can be patched to pay out any ratio the owner likes (like donation ratio) - and the network will accept it :what:

In the future (beyond 1.0) there also could be code to check the payout against its service type - masternode proof of service is a very powerful concept, superior to PoW for me, since a service has an intrinsic value, whereas the search for hashes has not. So darksend relays are only the first type of service a masternode can offer. Think of TOR relays (20% payout), email mixers (15% payout), distributed DNS (10%, greetings to Namecoin) - as long as the service can be verified to work by the network (not just by pinging, but actually using the service --> proof of service) the possibilites are endless, and your brilliant voting system is the foundation :smile:

just my 0.01 DRK :grin:
 
Last edited by a moderator:
I'm still unable to get the remote/local setup to work. I tried it by starting local wallet first, then remote, issue the debug command, go to local and issue masternode start, it starts, but it uses my home ip address.

I've checked my conf file several times, all is correct. Once I forgot the port #, but I fixed that with no joy. So anyway, I think I need to go to bed now. Maybe my head will be clearer in the morning :what:
 
flare said:
Currently the client/pool can be patched to pay out any ratio the owner likes (like donation ratio) - and the network will accept it :what:
Click to expand...

As a proof of concept i modified my local client and did some solomining ---> Block 15989 pays 50% to the lucky masternode winner :grin:

http://tdrk.poolhash.org/
Code: 
6 mins ago    06/08 11:12:21    5    15989    0.304    151    mt4tHZtz2b8dnyUP2DeVzc8vxPLwWpEUpR    mqGXfPgqp2Gr4qKm2CSjeCHjJnAhimFMQB    75.510    mqGXfPgqp2Gr4qKm2CSjeCHjJnAhimFMQB

EDIT: We have another winner, Block 15992

Code: 
1 min ago    06/08 11:21:39    4    15992    0.345    151    n2TnVWkgFQ3sq95beCay4aj5AXPbznqSdS    ms9JqmHQ6QrLbeFFyAp22cofqnR5PNuHkK    75.533    moqpGCABQQefuujQ9nsAMJVEiwAXyAMw6o
 
Last edited by a moderator:
..
flare said:
As a proof of concept i modified my local client and did some solomining ---> Block 15989 pays 50% to the lucky masternode winner :grin:

http://tdrk.poolhash.org/
Code: 
6 mins ago    06/08 11:12:21    5    15989    0.304    151    mt4tHZtz2b8dnyUP2DeVzc8vxPLwWpEUpR    mqGXfPgqp2Gr4qKm2CSjeCHjJnAhimFMQB    75.510    mqGXfPgqp2Gr4qKm2CSjeCHjJnAhimFMQB

EDIT: We have another winner, Block 15992

Code: 
1 min ago    06/08 11:21:39    4    15992    0.345    151    n2TnVWkgFQ3sq95beCay4aj5AXPbznqSdS    ms9JqmHQ6QrLbeFFyAp22cofqnR5PNuHkK    75.533    moqpGCABQQefuujQ9nsAMJVEiwAXyAMw6o
Click to expand...
There should be something like more to masternode is ok, less to masternode is rejected.. :tongue:
 
I updated the MN to 10.9.7 and got a few payments since then so it works!! :smile:
Checked debug.log and the only error is this one

Code: 
2014-06-08 09:40:12 ERROR: CTxMemPool::accept() : inputs already spent
2014-06-08 09:40:12 0e2c7f76c6b09df00f71231a5e55463886bf75af7b18eb08aed4f4fa1325ef82 from 54.183.73.24:19999 /Satoshi:0.9.5.8/ was not accepted into the m
emory pool
 
http://tdrk.poolhash.org/blocks/masterlist.txt updated.
Code: 
23.242.106.27:19999 1 e9d61186034aadce053f5c3d3cf6418869a2d280b23c79479969082bb09025bf mnKjtxAsabarv2y2kb3sGyHz7rFEnm7Uu4 1000.0
37.187.47.129:19999 1 b9282fb8eec1e2ba25a94b9c4528ea88f76783faebcf8cf491736be3715fea38 mqGXfPgqp2Gr4qKm2CSjeCHjJnAhimFMQB 1000.0
50.191.199.127:19999 1 4b63f74ad24f5d6729d5febfe6ebd1a7bd0c8740b0c78efb87fbf45dc20d8f2a mmqqx1CbNtvXYSCEqRCfJWTNmNqWo5pXGN 1000.0
54.76.52.216:19999 1 babead9e25fbbcd382c676dc83c14a491616b5f70eb5149d37daee3fbe0b7df4 mmxUk26YbAMRpBqn376js3fuQrmVxzptbV 1000.0
~~~
 
yidakee said:
Would someone please take the time to un-jam my head? My node got loads of 15 DRK payments until chaeplin updated block reward in NOMP, and at that time I got first payment of 30 DRK on block 15782. I since went to bed.

Today I'm unhappy, that was the last payout I got.
http://23.23.186.131:1234/address/moqpGCABQQefuujQ9nsAMJVEiwAXyAMw6o
Testnet explorer is stuck on that exact same block - http://23.23.186.131:1234/chain/DarkCoin (checked on another browser).

My remote server is on block 16034, confirmed with http://184.73.179.148:1234/chain/DarkCoin.
I have only addnode=23.23.186.131 in darkcoind.conf.
Masternode debug = successfully started masternode, and populated :1 on chaeplin's http://tdrk.poolhash.org/blocks/masterlist.txt

Why did I stop getting payouts?
Click to expand...
Is this yours ?
Code: 
54.255.159.230:19999 1 f912e108979186ce9e4782dc150a12ef25397c00e15749767ede9eba9b9b3dbe moqpGCABQQefuujQ9nsAMJVEiwAXyAMw6o 1000.0


Code: 
total blocks : 166
starting block no : 15874
22 mqGXfPgqp2Gr4qKm2CSjeCHjJnAhimFMQB
14 mfwFQXpRNhBFakKR6tMCgRaMB19yszGf2y
13 mq5CyKChT5UU7r9Wb53cViqXfu9Q8Z5VmE
12 miZrHTdqK5x5JLXxKbXveTmL2aWhcU7UHR
11 moqpGCABQQefuujQ9nsAMJVEiwAXyAMw6o
11 mkLN57jC9sYqMkp8RBcJF2H9hvhz6vabwQ
9 mw23256bSTqEkP6ThTRrY3KNicB9cfwzLR
8 mysBdRyDRFSYgBGUVjrEM1TyXsNxHMEUgQ

http://tdrk.poolhash.org/blocks/masterpay.txt
 
Last edited by a moderator:
yidakee said:
Yes, thats the one. I had since edited my post, since I was checking balance of the node on 23.23.186.131 explorer, but its stuck, so obviously I saw no more payouts listed... (coffee still brewing, I cant think without coffee hehe) -

But what about 75 DRK payout on block 16000 I got?
http://184.73.179.148:1234/block/00000002651a01a7c5d51b22a92662c2324fe199fd872ce061f48a8dd9a2cc42
Hold on... could that have been flare's hacked solo-mined daemon?
Click to expand...

Yep, that's me - after return from lunch i will set payout to 0.1% :smile:
 
I had just figured it out... I can smell the coffee now, so I am starting to wake up... thanks chaeplin!
 
BTW we have only ~10 days left to go live on main network. shouldnt we prepare an version for the main net soon?
 
Well this ain't normal, is it?
The node itself is the only one flagged 1. I have only one MN running on the testnet, so I can't say if other nodes behave like this as well. But looking at http://tdrk.poolhash.org/ it seems like it!
Code: 
xxx@lvps87-230-94-57:~$ ./darkcoind masternode list | grep 19999 | uniq | sort -V
    "23.242.106.27:19999" : 0,
    "37.187.47.129:19999" : 0,
    "50.191.199.127:19999" : 0,
    "54.76.47.232:19999" : 0
    "54.76.52.216:19999" : 0,
    "54.86.103.191:19999" : 0,
    "54.203.217.224:19999" : 0,
    "54.255.159.230:19999" : 0,
    "87.230.94.57:19999" : 1,
    "98.165.130.67:19999" : 0,
    "104.33.210.231:19999" : 0,
    "184.73.179.148:19999" : 0,
    "184.73.179.187:19999" : 0,
    "184.73.179.196:19999" : 0,
    "188.226.133.22:19999" : 0,
    "188.226.243.116:19999" : 0,
    "188.226.248.36:19999" : 0,

edit: darkcoind has enormous CPU usage... Something's going on there!
edit2: after restarting the daemon everything seems to be fine.

Code: 
xxx@lvps87-230-94-57:~$ ./darkcoind masternode list | grep 19999 | uniq | sort -V
    "23.242.106.27:19999" : 1,
    "54.76.47.232:19999" : 0
    "87.230.94.57:19999" : 1,
    "104.33.210.231:19999" : 1,
    "184.73.179.187:19999" : 1,
    "188.226.133.22:19999" : 1,
    "188.226.243.116:19999" : 1,
    "188.226.248.36:19999" : 1,
 
Last edited by a moderator:
I have tried to restart my nodes.
Seems like ban is returned.
My node is banned by others.

Code: 
2014-06-08 13:18:37 Misbehaving: my_ip:19999 (98 -> 99)
2014-06-08 13:18:37 Misbehaving: my_ip:19999 (99 -> 100) DISCONNECTING
2014-06-08 13:18:37 disconnecting node my_ip:19999
2014-06-08 13:18:38 connection from my_ip:13284 dropped (banned)

Code: 
2 "subver" : "",
3 "subver" : "/Satoshi:0.10.9.7/",
2 "subver" : "/Satoshi:0.9.5.8/",
 
Last edited by a moderator:
daaarkcoins said:
Well this ain't normal, is it?
The node itself is the only one flagged 1. I have only one MN running on the testnet, so I can't say if other nodes behave like this as well. But looking at http://tdrk.poolhash.org/ it seems like it!
Code: 
xxx@lvps87-230-94-57:~$ ./darkcoind masternode list | grep 19999 | uniq | sort -V
    "23.242.106.27:19999" : 0,
    "37.187.47.129:19999" : 0,
    "50.191.199.127:19999" : 0,
    "54.76.47.232:19999" : 0
    "54.76.52.216:19999" : 0,
    "54.86.103.191:19999" : 0,
    "54.203.217.224:19999" : 0,
    "54.255.159.230:19999" : 0,
    "87.230.94.57:19999" : 1,
    "98.165.130.67:19999" : 0,
    "104.33.210.231:19999" : 0,
    "184.73.179.148:19999" : 0,
    "184.73.179.187:19999" : 0,
    "184.73.179.196:19999" : 0,
    "188.226.133.22:19999" : 0,
    "188.226.243.116:19999" : 0,
    "188.226.248.36:19999" : 0,

edit: darkcoind has enormous CPU usage... Something's going on there!
edit2: after restarting the daemon everything seems to be fine.

Code: 
xxx@lvps87-230-94-57:~$ ./darkcoind masternode list | grep 19999 | uniq | sort -V
    "23.242.106.27:19999" : 1,
    "54.76.47.232:19999" : 0
    "87.230.94.57:19999" : 1,
    "104.33.210.231:19999" : 1,
    "184.73.179.187:19999" : 1,
    "188.226.133.22:19999" : 1,
    "188.226.243.116:19999" : 1,
    "188.226.248.36:19999" : 1,
Click to expand...

I have the same behaviour. I restarted the cold MN and at the start the situation was this

Code: 
./darkcoind masternode list
{
  "184.73.179.187:19999" : 1,
  "54.76.47.232:19999" : 0,
  "188.226.243.116:19999" : 1,
  "188.226.248.36:19999" : 1,
  "87.230.94.57:19999" : 1,
  "104.33.210.231:19999" : 1,
  "23.242.106.27:19999" : 1,
  "188.226.133.22:19999" : 1
}

After a while it's this
Code: 
./darkcoind masternode list
{
  "184.73.179.187:19999" : 1,
  "54.76.47.232:19999" : 0,
  "188.226.243.116:19999" : 0,
  "188.226.248.36:19999" : 0,
  "87.230.94.57:19999" : 1,
  "104.33.210.231:19999" : 0,
  "23.242.106.27:19999" : 0,
  "188.226.133.22:19999" : 0
}

The log shows this, don't know if it's worthwhile checking
Code: 
2014-06-08 13:00:50 Misbehaving: 112.175.123.94:19999 (0 -> 1)
2014-06-08 13:00:50 ProcessMessage(dsee, 249 bytes) FAILED
2014-06-08 13:00:50 Misbehaving: 112.175.123.94:19999 (1 -> 2)
2014-06-08 13:00:50 ProcessMessage(dsee, 249 bytes) FAILED
2014-06-08 13:00:50 Misbehaving: 112.175.123.94:19999 (2 -> 3)
2014-06-08 13:00:50 ProcessMessage(dsee, 249 bytes) FAILED
2014-06-08 13:00:50 Misbehaving: 112.175.123.94:19999 (3 -> 4)
2014-06-08 13:00:50 ProcessMessage(dsee, 249 bytes) FAILED
2014-06-08 13:00:50 Misbehaving: 112.175.123.94:19999 (4 -> 5)
2014-06-08 13:00:50 ProcessMessage(dsee, 249 bytes) FAILED
2014-06-08 13:00:50 Misbehaving: 112.175.123.94:19999 (5 -> 6)
2014-06-08 13:00:50 ProcessMessage(dsee, 249 bytes) FAILED
2014-06-08 13:00:50 Misbehaving: 112.175.123.94:19999 (6 -> 7)
2014-06-08 13:00:50 ProcessMessage(dsee, 249 bytes) FAILED
2014-06-08 13:00:50 Misbehaving: 112.175.123.94:19999 (7 -> 8)
2014-06-08 13:00:50 ProcessMessage(dsee, 249 bytes) FAILED
2014-06-08 13:00:50 Misbehaving: 112.175.123.94:19999 (8 -> 9)
2014-06-08 13:00:50 ProcessMessage(dsee, 249 bytes) FAILED
...
2014-06-08 13:00:51 Misbehaving: 112.175.123.94:19999 (99 -> 100) DISCONNECTING
2014-06-08 13:00:51 disconnecting node 112.175.123.94:19999
2014-06-08 13:00:51 ProcessMessage(dsee, 249 bytes) FAILED
...
2014-06-08 13:17:37 connection from 112.175.123.94:59524 dropped (banned)
 
1) 123.82, 123.94 is mine
2) github 9.5.8
3) changed 123.94's daemon to rc version, and testing darksend.
(a lot of Masternode un available...)
4) sometime later, 123.94's rc changed to github 9.5.8
5) several hours nothing happened.
6) I setup other rc node, to test darksend.

My node 83 and 94 relaying a lot of wtx.

I will down my 3 nodes(82, 94, nomp) at least 10 min, and remove wallet.
 
chaeplin said:
1) 123.82, 123.94 is mine
2) github 9.5.8
3) changed 123.94's daemon to rc version, and testing darksend.
(a lot of Masternode un available...)
4) sometime later, 123.94's rc changed to github 9.5.8
5) several hours nothing happened.
6) I setup other rc node, to test darksend.

My node 83 and 94 relaying a lot of wtx.

I will down my 3 nodes(82, 94, nomp) at least 10 min, and remove wallet.
Click to expand...

I'm recompiling everything, half the network is on the wrong version without the spam fix. I think the auto-compile code failed to work on the stable side
 
Status
Not open for further replies.
Back
Top