v0.10.9.x Help test RC2 forking issues

Status
Not open for further replies.

yidakee

Well-known Member
Foundation Member
Apr 16, 2014
1,812
1,168
283
I tried both, first without and then with masternodeaddr=...
Still no success...
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)
 
  • Like
Reactions: vertoe

DrkMiner

Member
Jun 7, 2014
204
63
88
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!
 

yidakee

Well-known Member
Foundation Member
Apr 16, 2014
1,812
1,168
283
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.
 

chaeplin

Active Member
Core Developer
Mar 29, 2014
749
356
133
So it's not that trivial to determine what the actual payee/amount vout was :cool:
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:

TanteStefana

Grizzled Member
Foundation Member
Mar 9, 2014
2,871
1,863
1,283
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 :)
 

chaeplin

Active Member
Core Developer
Mar 29, 2014
749
356
133
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
I will try to setup one.
 

TanteStefana

Grizzled Member
Foundation Member
Mar 9, 2014
2,871
1,863
1,283
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
 

flare

Administrator
Dash Core Team
Moderator
May 18, 2014
2,286
2,404
1,183
Germany
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
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:

chaeplin

Active Member
Core Developer
Mar 29, 2014
749
356
133
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 :)
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
 

chaeplin

Active Member
Core Developer
Mar 29, 2014
749
356
133
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 :)

This is what I have found in local machine
Code:
[email protected]:~> darkcoind masternode debug
Missing masternode input, please look at the documentation for instructions on masternode creation
But, I do this.
Code:
[email protected]:~> darkcoind masternode start wallet_password
successfully started masternode
[email protected]:~> darkcoind masternode debug
successfully started masternode
local
Code:
2014-06-13 05:57:22 Found unspent output equal to nValue
2014-06-13 05:57:22 CDarkSendPool::RegisterAsMasterNode() - Is capable master node!
2014-06-13 05:57:22 CDarkSendPool::RegisterAsMasterNode() - Adding myself to masternode list ip... CTxIn(COutPoint(8cb2f7cae9b0d1d508ea79538e0f3013563e4d76d0160c7ed8a4feead87b894e, 0), scriptSig=)

2014-06-13 05:57:22 CDarkSendPool::RegisterAsMasterNode() - Masternode input = CTxIn(COutPoint(8cb2f7cae9b0d1d508ea79538e0f3013563e4d76d0160c7ed8a4feead87b894e, 0), scriptSig=)

remote
Code:
2014-06-13 05:57:22 dsee - Accepted masternode entry -1 -1
2014-06-13 05:57:22 CDarkSendPool::EnableHotColdMasterNode() - Enabled! You may shut down the cold daemon.

It started.. and listed.

Please try 'masternode start'


EDIT:
In hot/cold setup, cold wallet try to connect hot wallet port 19999.
Code:
2014-06-13 05:57:22 CDarkSendPool::RegisterAsMasterNode() - Checking inbound connection to 'romote:19999'
 
Last edited by a moderator:

vertoe

Three of Nine
Mar 28, 2014
2,573
1,652
1,283
Unimatrix Zero One
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)
Thanks for spotting that one, I only opened 9999 in my security group. Wasnt prepared for testnet :)
 
  • Like
Reactions: yidakee

yidakee

Well-known Member
Foundation Member
Apr 16, 2014
1,812
1,168
283
Its been basically 24h and no payouts on 10.9.13, correctly listed as :1 & successful debug

{
"version" : 100913,
"protocolversion" : 70018,
"walletversion" : 60000,
"balance" : 0.00000000,
"blocks" : 18703,
"timeoffset" : -24,
"connections" : 25,
"proxy" : "",
"difficulty" : 0.66230419,
"testnet" : true,
"keypoololdest" : 1401955602,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"mininput" : 0.00001000,
"errors" : ""
}
[email protected]:~$ darkcoind masternode debug
successfully started masternode
[email protected]:~$
http://23.23.186.131:1234/address/mrPbaoAeVVeaiuezEmqs7zQimHHcAtKAqq

While my other node is still getting regular pays under 10.9.6. ... now this does seem odd right?
 

chaeplin

Active Member
Core Developer
Mar 29, 2014
749
356
133
Its been basically 24h and no payouts on 10.9.13, correctly listed as :1 & successful debug



http://23.23.186.131:1234/address/mrPbaoAeVVeaiuezEmqs7zQimHHcAtKAqq

While my other node is still getting regular pays under 10.9.6. ... now this does seem odd right?
There are other commands.
masternode list lastseen
masternode list activeseconds

[email protected]:~> darkcoind masternode list activeseconds | sort -n -k3
"54.224.80.160:19999" : 0,
"54.187.111.243:19999" : 9399,
"54.178.139.242:19999" : 9822
"211.99.224.197:19999" : 10759,
"93.188.161.89:19999" : 75118,
"37.187.47.129:19999" : 75605,
"54.209.226.236:19999" : 81717,
"211.99.224.196:19999" : 101198,
"98.165.130.67:19999" : 119903,
"54.83.143.1:19999" : 153666,
"23.23.55.5:19999" : 153862,
"107.22.42.148:19999" : 153885,
~~
activeseconds is somehow lower than others.
54.178.139.242 is mine.

What is your node configuration ?
local / remote ?
 

MykelSIlver

New Member
Apr 25, 2014
28
2
3
Is it possible to setup a HOT only masternode (on MainNet 9999)?
When I setup a HOT only masternode starting my masternode returns the message:
"inbound port is not open. Please open it and try again. (19999 for testnet and 9999 for mainnet)"

I 'm 100% sure I have the TCP/UDP port 9999 open

Any suggestions what might be the case?
Thanks in advance
 
  • Like
Reactions: vertoe

flare

Administrator
Dash Core Team
Moderator
May 18, 2014
2,286
2,404
1,183
Germany
While my other node is still getting regular pays under 10.9.6. ... now this does seem odd right?
Yes, kind of odd. I additionally noticed atavacron shut down his 50 nodes since 10 hours (thanks for the testcase), but the IPs are still listed in masternode list (being inactive) and still getting votes and payments! Seems the miners are still voting on the inactive IPs/addresses - is this a pool-code issue?

And the number of unpaid block rose to 40%. It seems that the deactivation does not get propagated properly through the network, and network can't find consensus on votes, that why votes often expire --> unpaid blocks.

Code:
54.234.251.170:19999    0    n1HRzCV9RBxVJoC5noKVNBCx4gAbTZPyPZ    1402610608423963    39692    155377
[...]
204.236.211.102:19999    0    mysBdRyDRFSYgBGUVjrEM1TyXsNxHMEUgQ    1402610638577940    39662    155407
[..]
54.198.191.99:19999    0    myVSR4kptFPTSFjARc3DD8RkFvkLQ2CJ8c    1402610611150936    39689    155380
[...]
Code:
current valid no of masternode : 17

last 20 blocks
      4 -
      1 n1HRzCV9RBxVJoC5noKVNBCx4gAbTZPyPZ
      1 mysBdRyDRFSYgBGUVjrEM1TyXsNxHMEUgQ
      1 myVSR4kptFPTSFjARc3DD8RkFvkLQ2CJ8c
      1 mwnfhj5k4dvzTycttN5249FvtMNMzisPiy
      1 mvaUy1oHfEykY5SohyfpRWP8YzqGb7r5qf
      1 mtDk3CAwEoPo2yRwzbNhrUiJL8Jytr2arp
      1 moqpGCABQQefuujQ9nsAMJVEiwAXyAMw6o
      1 miRmicKoQPqEbem31CX8Pe59YGpfzsy5Zn
eduffield what is the timeout for inactive ':0' nodes being removed from network list and why do they still take part in the voting and get network confirmations?

Was thinking about the hard vote expiration factor of 10 anyway: Perhaps we should think of dynamically adjusting the vote expiration factor (like DGW), as this factor must scale to network size: It's much harder to find vote consensus in a large P2P network than in a small one. And expiration of 10 might not be sufficient in a network with 300 masternodes (was thinking about something like 51% no. of masternodes so that there is the mathematical chance that majority of network has confirmed). So network size "difficulty" should be part of blockchain like hash difficulty...

EDIT: inactive nodes continue to get payments, 40% unpaid blocks

Code:
current valid no of masternode : 17

last 20 blocks
      8 -
      3 mysBdRyDRFSYgBGUVjrEM1TyXsNxHMEUgQ  <--
      2 myVSR4kptFPTSFjARc3DD8RkFvkLQ2CJ8c <--
      2 miRmicKoQPqEbem31CX8Pe59YGpfzsy5Zn
      1 mwnfhj5k4dvzTycttN5249FvtMNMzisPiy
      1 mtDk3CAwEoPo2yRwzbNhrUiJL8Jytr2arp
      1 moqpGCABQQefuujQ9nsAMJVEiwAXyAMw6o
      1 mfwFQXpRNhBFakKR6tMCgRaMB19yszGf2y
      1 mfmqKHWKdS6juPjUMwDo6cTSWJSoKtAsGs
Code:
{
    "version" : 2,
    "previousblockhash" : "00000001724bbdad7c03c44364a659feebfab5da14f8c74a5ed877f4da0baea2",
    "transactions" : [
    ],
    "coinbaseaux" : {
        "flags" : "062f503253482f"
    },
    "coinbasevalue" : 15100000000,
    "target" : "000000033c330000000000000000000000000000000000000000000000000000",
    "mintime" : 1402651794,
    "mutable" : [
        "time",
        "transactions",
        "prevblock"
    ],
    "noncerange" : "00000000ffffffff",
    "sigoplimit" : 20000,
    "sizelimit" : 1000000,
    "curtime" : 1402652221,
    "bits" : "1d033c33",
    "height" : 18725,
    "votes" : [
        "1e490000000000001976a914c945b6ce1ff2bdbadef37ffdc3e22ed17eddcb8188ac06000000",
        "1f490000000000001976a914b27ad157bd495c98eebfb588cc071c7be6f7ad3788ac04000000",
        "20490000000000001976a914a534bcf52ac17918da047319ac113cbf5a9912ad88ac03000000",
        "21490000000000001976a9144aa9f48fc2153ab8e0dd56cc20b42792ae7ac8a488ac03000000",
        "22490000000000001976a9148b5855369051c6ca305952021112ca973dffc6bd88ac02000000",
        "23490000000000001976a914c945b6ce1ff2bdbadef37ffdc3e22ed17eddcb8188ac02000000",
        "24490000000000001976a914d8d3cef6e63fa5104f75e2e42a26d69ad9b13dff88ac01000000",
        "25490000000000001976a914e3c2bf5d17901d8cf423b787aa5146994837d81a88ac01000000"
    ],
    "payee" : "myVSR4kptFPTSFjARc3DD8RkFvkLQ2CJ8c",            <------------
    "masternode_payments" : true
}
 
Last edited by a moderator:

yidakee

Well-known Member
Foundation Member
Apr 16, 2014
1,812
1,168
283
There are other commands.
masternode list lastseen
masternode list activeseconds



activeseconds is somehow lower than others.
54.178.139.242 is mine.

What is your node configuration ?
local / remote ?
here; mine is 54.209.226.236

lastseen;

[email protected]:~/.darkcoin$ darkcoind masternode list lastseen | grep 236
"188.226.243.116:19999" : 1402650886062361,
"204.236.211.102:19999" : 0,
"54.242.139.236:19999" : 0,
"37.187.216.11:19999" : 1402650983039236,
"54.209.226.236:19999" : 1402650882837515,
active seconds

[email protected]:~$ darkcoind masternode list activeseconds | grep 236
"204.236.211.102:19999" : -1402455230,
"50.16.10.185:19999" : -1402455236,
"54.227.119.61:19999" : -1402455236,
"54.225.6.1:19999" : -1402455236,
"54.242.139.236:19999" : -1402455278,
"54.209.226.236:19999" : 83543,
From your list chaeplin

54.209.226.236:19999 1 mrPbaoAeVVeaiuezEmqs7zQimHHcAtKAqq 1402650857863895 463 83518
remote conf

#----
addnode=23.23.186.131
rpcuser=Darkaramma
rpcpassword=stupidpassword
rpcallowip=127.0.0.1
testnet=1
listen=1
server=1
daemon=1
masternodeprivkey=935E5AJNJrNXoN78v2uQCfRFdTgiGXEJK7mMNvmkjVUqfYcTrsV
masternode=1
logtimestamps=1
maxconnections=256
#--------------------
# change ami_public_ip to public ip address which you connected by ssh
externalip=54.209.226.236
local conf

#----
addnode=23.23.186.131
testnet=1
rpcuser=hi_caheplin!
rpcpassword=thisisnotmypassword
rpcallowip=127.0.0.1
listen=1
server=1
daemon=1
masternode=1
masternodeprivkey=935E5AJNJrNXoN78v2uQCfRFdTgiGXEJK7mMNvmkjVUqfYcTrsV
masternodeaddr=54.209.226.236:19999
logtimestamps=1
maxconnections=256
#--------------------
 
Last edited by a moderator:

chaeplin

Active Member
Core Developer
Mar 29, 2014
749
356
133
Yes, kind of odd. I additionally noticed atavacron shut down his 50 nodes since 10 hours, but the IPs are still listed in masternode list (being inactive), but still getting votes and payments! And the number of unpaid block rose to 40%. It seems that the deactivation does not get propagated properly through the network, and network can't find consensus on votes, that why votes often expire --> unpaid blocks.

Code:
54.234.251.170:19999    0    n1HRzCV9RBxVJoC5noKVNBCx4gAbTZPyPZ    1402610608423963    39692    155377
[...]
204.236.211.102:19999    0    mysBdRyDRFSYgBGUVjrEM1TyXsNxHMEUgQ    1402610638577940    39662    155407
[..]
54.198.191.99:19999    0    myVSR4kptFPTSFjARc3DD8RkFvkLQ2CJ8c    1402610611150936    39689    155380
[...]
Code:
current valid no of masternode : 17

last 20 blocks
      4 -
      1 n1HRzCV9RBxVJoC5noKVNBCx4gAbTZPyPZ
      1 mysBdRyDRFSYgBGUVjrEM1TyXsNxHMEUgQ
      1 myVSR4kptFPTSFjARc3DD8RkFvkLQ2CJ8c
      1 mwnfhj5k4dvzTycttN5249FvtMNMzisPiy
      1 mvaUy1oHfEykY5SohyfpRWP8YzqGb7r5qf
      1 mtDk3CAwEoPo2yRwzbNhrUiJL8Jytr2arp
      1 moqpGCABQQefuujQ9nsAMJVEiwAXyAMw6o
      1 miRmicKoQPqEbem31CX8Pe59YGpfzsy5Zn
eduffield what is the timeout for inactive ':0' nodes being removed and why do they take part in the voting?
darkcoind masternode list == darkcoind masternode active

https://github.com/darkcoinproject/darkcoin/blob/master/src/rpcdarksend.cpp#L38-L43

active shows with flag 0.
 

flare

Administrator
Dash Core Team
Moderator
May 18, 2014
2,286
2,404
1,183
Germany
Last edited by a moderator:

chaeplin

Active Member
Core Developer
Mar 29, 2014
749
356
133
Yes, kind of odd. I additionally noticed atavacron shut down his 50 nodes since 10 hours (thanks for the testcase), but the IPs are still listed in masternode list (being inactive) and still getting votes and payments! Seems the miners are still voting on the inactive IPs/addresses - is this a pool-code issue?

And the number of unpaid block rose to 40%. It seems that the deactivation does not get propagated properly through the network, and network can't find consensus on votes, that why votes often expire --> unpaid blocks.

Code:
54.234.251.170:19999    0    n1HRzCV9RBxVJoC5noKVNBCx4gAbTZPyPZ    1402610608423963    39692    155377
[...]
204.236.211.102:19999    0    mysBdRyDRFSYgBGUVjrEM1TyXsNxHMEUgQ    1402610638577940    39662    155407
[..]
54.198.191.99:19999    0    myVSR4kptFPTSFjARc3DD8RkFvkLQ2CJ8c    1402610611150936    39689    155380
[...]
Code:
current valid no of masternode : 17

last 20 blocks
      4 -
      1 n1HRzCV9RBxVJoC5noKVNBCx4gAbTZPyPZ
      1 mysBdRyDRFSYgBGUVjrEM1TyXsNxHMEUgQ
      1 myVSR4kptFPTSFjARc3DD8RkFvkLQ2CJ8c
      1 mwnfhj5k4dvzTycttN5249FvtMNMzisPiy
      1 mvaUy1oHfEykY5SohyfpRWP8YzqGb7r5qf
      1 mtDk3CAwEoPo2yRwzbNhrUiJL8Jytr2arp
      1 moqpGCABQQefuujQ9nsAMJVEiwAXyAMw6o
      1 miRmicKoQPqEbem31CX8Pe59YGpfzsy5Zn
eduffield what is the timeout for inactive ':0' nodes being removed from network list and why do they still take part in the voting and get network confirmations?

Was thinking about the hard vote expiration factor of 10 anyway: Perhaps we should think of dynamically adjusting the vote expiration factor (like DGW), as this factor must scale to network size: It's much harder to find vote consensus in a large P2P network than in a small one. And expiration of 10 might not be sufficient in a network with 300 masternodes (was thinking about something like 51% no. of masternodes so that there is the mathematical chance that majority of network has confirmed). So network size "difficulty" should be part of blockchain like hash difficulty...

EDIT: inactive nodes continue to get payments, 40% unpaid blocks

Code:
current valid no of masternode : 17

last 20 blocks
      8 -
      3 mysBdRyDRFSYgBGUVjrEM1TyXsNxHMEUgQ  <--
      2 myVSR4kptFPTSFjARc3DD8RkFvkLQ2CJ8c <--
      2 miRmicKoQPqEbem31CX8Pe59YGpfzsy5Zn
      1 mwnfhj5k4dvzTycttN5249FvtMNMzisPiy
      1 mtDk3CAwEoPo2yRwzbNhrUiJL8Jytr2arp
      1 moqpGCABQQefuujQ9nsAMJVEiwAXyAMw6o
      1 mfwFQXpRNhBFakKR6tMCgRaMB19yszGf2y
      1 mfmqKHWKdS6juPjUMwDo6cTSWJSoKtAsGs
Code:
{
    "version" : 2,
    "previousblockhash" : "00000001724bbdad7c03c44364a659feebfab5da14f8c74a5ed877f4da0baea2",
    "transactions" : [
    ],
    "coinbaseaux" : {
        "flags" : "062f503253482f"
    },
    "coinbasevalue" : 15100000000,
    "target" : "000000033c330000000000000000000000000000000000000000000000000000",
    "mintime" : 1402651794,
    "mutable" : [
        "time",
        "transactions",
        "prevblock"
    ],
    "noncerange" : "00000000ffffffff",
    "sigoplimit" : 20000,
    "sizelimit" : 1000000,
    "curtime" : 1402652221,
    "bits" : "1d033c33",
    "height" : 18725,
    "votes" : [
        "1e490000000000001976a914c945b6ce1ff2bdbadef37ffdc3e22ed17eddcb8188ac06000000",
        "1f490000000000001976a914b27ad157bd495c98eebfb588cc071c7be6f7ad3788ac04000000",
        "20490000000000001976a914a534bcf52ac17918da047319ac113cbf5a9912ad88ac03000000",
        "21490000000000001976a9144aa9f48fc2153ab8e0dd56cc20b42792ae7ac8a488ac03000000",
        "22490000000000001976a9148b5855369051c6ca305952021112ca973dffc6bd88ac02000000",
        "23490000000000001976a914c945b6ce1ff2bdbadef37ffdc3e22ed17eddcb8188ac02000000",
        "24490000000000001976a914d8d3cef6e63fa5104f75e2e42a26d69ad9b13dff88ac01000000",
        "25490000000000001976a914e3c2bf5d17901d8cf423b787aa5146994837d81a88ac01000000"
    ],
    "payee" : "myVSR4kptFPTSFjARc3DD8RkFvkLQ2CJ8c",            <------------
    "masternode_payments" : true
}

http://tdrk.poolhash.org/blocks/masterlist/mysBdRyDRFSYgBGUVjrEM1TyXsNxHMEUgQ.txt
http://tdrk.poolhash.org/blocks/masterlist/myVSR4kptFPTSFjARc3DD8RkFvkLQ2CJ8c.txt

masternode list active + getblocktemplate

Code:
/dev/shm/darktest/masterlist/18030.txt:54.198.191.99:19999 1 myVSR4kptFPTSFjARc3DD8RkFvkLQ2CJ8c 1402541648774158 1095 86417
/dev/shm/darktest/masterlist/18031.txt:54.198.191.99:19999 1 myVSR4kptFPTSFjARc3DD8RkFvkLQ2CJ8c 1402541648774158 1394 86417
/dev/shm/darktest/masterlist/18032.txt:54.198.191.99:19999 1 myVSR4kptFPTSFjARc3DD8RkFvkLQ2CJ8c 1402541648774158 1791 86417
/dev/shm/darktest/masterlist/18033.txt:54.198.191.99:19999 0 myVSR4kptFPTSFjARc3DD8RkFvkLQ2CJ8c 0 1402543622 -1402455230
/dev/shm/darktest/masterlist/18034.txt:54.198.191.99:19999 0 myVSR4kptFPTSFjARc3DD8RkFvkLQ2CJ8c 0 1402543701 -1402455230
/dev/shm/darktest/masterlist/18035.txt:54.198.191.99:19999 0 myVSR4kptFPTSFjARc3DD8RkFvkLQ2CJ8c 0 1402544132 -1402455230

~~~

/dev/shm/darktest/masterlist/18469.txt:54.198.191.99:19999 1 myVSR4kptFPTSFjARc3DD8RkFvkLQ2CJ8c 1402610611150936 1174 155380
/dev/shm/darktest/masterlist/18470.txt:54.198.191.99:19999 1 myVSR4kptFPTSFjARc3DD8RkFvkLQ2CJ8c 1402610611150936 1378 155380
/dev/shm/darktest/masterlist/18471.txt:54.198.191.99:19999 1 myVSR4kptFPTSFjARc3DD8RkFvkLQ2CJ8c 1402610611150936 1666 155380
/dev/shm/darktest/masterlist/18472.txt:54.198.191.99:19999 1 myVSR4kptFPTSFjARc3DD8RkFvkLQ2CJ8c 1402610611150936 1683 155380
/dev/shm/darktest/masterlist/18473.txt:54.198.191.99:19999 0 myVSR4kptFPTSFjARc3DD8RkFvkLQ2CJ8c 1402610611150936 2397 155380
/dev/shm/darktest/masterlist/18474.txt:54.198.191.99:19999 0 myVSR4kptFPTSFjARc3DD8RkFvkLQ2CJ8c 1402610611150936 2618 155380
/dev/shm/darktest/masterlist/18475.txt:54.198.191.99:19999 0 myVSR4kptFPTSFjARc3DD8RkFvkLQ2CJ8c 1402610611150936 2693 155380
/dev/shm/darktest/masterlist/18476.txt:54.198.191.99:19999 0 myVSR4kptFPTSFjARc3DD8RkFvkLQ2CJ8c 1402610611150936 2731 155380
 
  • Like
Reactions: flare

flare

Administrator
Dash Core Team
Moderator
May 18, 2014
2,286
2,404
1,183
Germany
Code:
/dev/shm/darktest/masterlist/17386.txt:204.236.211.102:19999 0 9419a0cc1d96533861188b21c750b0da8298299e68309bfcbc9c58e28a7224d6 mysBdRyDRFSYgBGUVjrEM1TyXsNxHMEUgQ 1000.0
/dev/shm/darktest/masterlist/17386.txt:    "payee" : "mysBdRyDRFSYgBGUVjrEM1TyXsNxHMEUgQ",
[...]
Ouch :rolleyes:
 

yidakee

Well-known Member
Foundation Member
Apr 16, 2014
1,812
1,168
283
Thats my address "mrPbaoA ....", though I cannot interpret the txt. Is anything wrong? It was setup exactly 24h ago (give or take a few mins) - why the lack of payments?

I also have multiple of these on my other address

18706.txt:54.255.159.230:19999 1 moqpGCABQQefuujQ9nsAMJVEiwAXyAMw6o 1402649294650054 427 309838
18706.txt: "payee" : "moqpGCABQQefuujQ9nsAMJVEiwAXyAMw6o",
Why the "ouch" flare? Doesnt that mean on that block the address got payed?

EDIT: Yes, it does seem so, though through the explorer the actual block has an increment of 1. So in this case does this mean I got voted on 18706, but actually got payed on block 18707?
 
Last edited by a moderator:

flare

Administrator
Dash Core Team
Moderator
May 18, 2014
2,286
2,404
1,183
Germany
Thats my address "mrPbaoA ....", though I cannot interpret the txt. Is anything wrong? It was setup exactly 24h ago (give or take a few mins) - why the lack of payments?
It's strange - even if we account all 78 servers (active and inactive) to take part in the voting, and worst case 40% blocks unpaid, you should have been elected winner for around 4 blocks the last 24hours.

But it's Friday 13th - maybe just bad luck? :D
 
Last edited by a moderator:

flare

Administrator
Dash Core Team
Moderator
May 18, 2014
2,286
2,404
1,183
Germany
Why the "ouch" flare? Doesnt that mean on that block the address got payed?
Sure, but the server being paid is inactive since 10 hours (denoted by the 0 next to the IP:port) - so it should not take part in the voting, and even less WIN :D

Code:
/dev/shm/darktest/masterlist/17386.txt:204.236.211.102:19999 0 9419a0cc1d96533861188b21c750b0da8298299e68309bfcbc9c58e28a7224d6 mysBdRyDRFSYgBGUVjrEM1TyXsNxHMEUgQ 1000.0
/dev/shm/darktest/masterlist/17386.txt:    "payee" : "mysBdRyDRFSYgBGUVjrEM1TyXsNxHMEUgQ",
[...]
 

yidakee

Well-known Member
Foundation Member
Apr 16, 2014
1,812
1,168
283
ahh, missed the "0"...

Ok, I'll let you guys keep talking klingon and I'll be spectating. Please let me know what I can do to understand why on earth my active and updated node is not getting voted/elected/payed.
 
Status
Not open for further replies.