v0.10.9.x Help test RC2 forking issues

Status
Not open for further replies.
chaeplin said:
GMT+9 Good afternoon :wink:
Click to expand...
Will get some wall clocks and write teammembers name underneath it :-D

duratimezone_300px_animation.gif
 
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

If anyone could help, I'd sure appreciate it. Also, has anyone noted that they've had success doing this? Thank :)
Click to expand...


This is what I have found in local machine
Code: 
ms06@x60t:~> darkcoind masternode debug
Missing masternode input, please look at the documentation for instructions on masternode creation

But, I do this.
Code: 
ms06@x60t:~> darkcoind masternode start wallet_password
successfully started masternode
ms06@x60t:~> 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:
yidakee said:
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)
Click to expand...
Thanks for spotting that one, I only opened 9999 in my security group. Wasnt prepared for testnet :)
 
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" : ""
}
ubuntu@ip-172-31-23-208:~$ darkcoind masternode debug
successfully started masternode
ubuntu@ip-172-31-23-208:~$
Click to expand...

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?
 
yidakee said:
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?
Click to expand...

There are other commands.
masternode list lastseen
masternode list activeseconds

darktest@sv1:~> 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,
~~
Click to expand...

activeseconds is somehow lower than others.
54.178.139.242 is mine.

What is your node configuration ?
local / remote ?
 
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
 
yidakee said:
While my other node is still getting regular pays under 10.9.6. ... now this does seem odd right?
Click to expand...

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:
chaeplin said:
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 ?
Click to expand...

here; mine is 54.209.226.236

lastseen;

ubuntu@ip-172-31-23-208:~/.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,
Click to expand...

active seconds

ubuntu@ip-172-31-23-208:~$ 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,
Click to expand...

From your list chaeplin

54.209.226.236:19999 1 mrPbaoAeVVeaiuezEmqs7zQimHHcAtKAqq 1402650857863895 463 83518
Click to expand...

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
Click to expand...

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
#--------------------
Click to expand...
 
Last edited by a moderator:
flare said:
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?
Click to expand...
darkcoind masternode list == darkcoind masternode active

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

active shows with flag 0.
 
Last edited by a moderator:
flare said:
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
}
Click to expand...


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
 
chaeplin said:
http://tdrk.poolhash.org/blocks/masterlist/mysBdRyDRFSYgBGUVjrEM1TyXsNxHMEUgQ.txt
http://tdrk.poolhash.org/blocks/masterlist/myVSR4kptFPTSFjARc3DD8RkFvkLQ2CJ8c.txt

masternode list active + getblocktemplate
Click to expand...

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:
 
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",
Click to expand...

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:
yidakee said:
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?
Click to expand...

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? :grin:
 
Last edited by a moderator:
yidakee said:
Why the "ouch" flare? Doesnt that mean on that block the address got payed?
Click to expand...

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 :grin:

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",
[...]
 
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.
Back
Top