Multipool.us - Orphan blocks

Hi,

I run Multipool.us, we’ve been having a rather large problem with orphans lately on Peercoin.

$ ppcoind listtransactions “” 25 | egrep cat.*(orph|gen|imm)|sort|uniq -c
5 “category” : “generate”,
1 “category” : “immature”,
10 “category” : “orphan”,

As you can see out of our last 16 blocks found, 10 have been orphaned.

This seems quite a bit higher than it should be. I read about an attack that might be responsible for this, but I can no longer find the post.

Are there some addnodes I could be using to help better our connectivity?

Hello and welcome to the forums flound1129,

First thing I would check is the block count you are on compared to block explorers, just double check that there is no issue in the blockchain and yours. here are a few:

http://peerchain.net/
http://blockexplorer.peercointalk.org/


https://bkchain.org/ppc

currently they all in agreement on 160,944 blocks

Next check the version of the client you are running. Are you running ppcoin master built from source? are you running peerunity? are you running your own custom build of peercoin?

How many connections do you have? the default is for the client to connect to 8, and if you are not getting more than that you may need to addnode… and something else i can’t remember off the top of my head.

If your client is up to date and on the correct chain, and has more than 8 connections then yes adding more nodes should help reduce the orphan’s

Here is a printout from my getpeerinfo


[
{
"addr" : "37.187.98.144:9901",
"services" : "00000001",
"lastsend" : 1424996282,
"lastrecv" : 1424996246,
"conntime" : 1424996132,
"version" : 60004,
"subver" : "/Satoshi:0.6.3/Peercoin:0.4.0/Peerunity:0.1.1(v0.1.1)/",
"inbound" : false,
"releasetime" : 0,
"height" : 160944,
"banscore" : 0
},
{
"addr" : "212.83.172.152:9901",
"services" : "00000001",
"lastsend" : 1424996281,
"lastrecv" : 1424996227,
"conntime" : 1424996149,
"version" : 60004,
"subver" : "/Satoshi:0.6.3/Peercoin:0.4.0(v0.4.0ppc-2-g6219e88-beta)/",
"inbound" : false,
"releasetime" : 0,
"height" : 160944,
"banscore" : 0
},
{
"addr" : "176.9.65.41:9901",
"services" : "00000001",
"lastsend" : 1424996281,
"lastrecv" : 1424996229,
"conntime" : 1424996166,
"version" : 60004,
"subver" : "/Satoshi:0.6.3/Peercoin:0.4.0/Peerunity:0.1.1(v0.1.1.0-unk)/",
"inbound" : false,
"releasetime" : 0,
"height" : 160944,
"banscore" : 0
},
{
"addr" : "89.155.84.38:9901",
"services" : "00000001",
"lastsend" : 1424996282,
"lastrecv" : 1424996231,
"conntime" : 1424996172,
"version" : 60004,
"subver" : "/Satoshi:0.6.3/Peercoin:0.4.0/Peerunity:0.1.1(v0.1.1)/",
"inbound" : false,
"releasetime" : 0,
"height" : 160944,
"banscore" : 0
},
{
"addr" : "78.46.189.202:9901",
"services" : "00000001",
"lastsend" : 1424996281,
"lastrecv" : 1424996281,
"conntime" : 1424996173,
"version" : 60004,
"subver" : "/Satoshi:0.6.3/Peercoin:0.4.0(v0.4.0.0-g1f058b6-beta)/",
"inbound" : false,
"releasetime" : 0,
"height" : 160944,
"banscore" : 0
},
{
"addr" : "146.185.137.249:9901",
"services" : "00000001",
"lastsend" : 1424996283,
"lastrecv" : 1424996241,
"conntime" : 1424996174,
"version" : 60004,
"subver" : "/Satoshi:0.6.3/Peercoin:0.4.0(v0.4.0ppc-beta)/",
"inbound" : false,
"releasetime" : 0,
"height" : 160944,
"banscore" : 0
},
{
"addr" : "198.58.109.235:9901",
"services" : "00000001",
"lastsend" : 1424996281,
"lastrecv" : 1424996229,
"conntime" : 1424996174,
"version" : 60004,
"subver" : "/Satoshi:0.6.3/Peercoin:0.4.0(v0.4.0ppc-beta)/",
"inbound" : false,
"releasetime" : 0,
"height" : 160944,
"banscore" : 0
},
{
"addr" : "121.67.5.230:9901",
"services" : "00000001",
"lastsend" : 1424996283,
"lastrecv" : 1424996231,
"conntime" : 1424996225,
"version" : 60004,
"subver" : "/Satoshi:0.6.3/Peercoin:0.4.0/Peerunity:0.1.1(v0.1.1)/",
"inbound" : false,
"releasetime" : 0,
"height" : 160944,
"banscore" : 0
}
]

so

addnode=121.67.5.230:9901 addnode=198.58.109.235:9901 addnode=146.185.137.249:9901 addnode=78.46.189.202:9901 addnode=89.155.84.38:9901 addnode=176.9.65.41:9901 addnode=212.83.172.152:9901 addnode=37.187.98.144:9901

You can also add the ip of the block explorers as they will be running clients but the port may be different

Out of interest what is your IP, I will add you and see if you have a “banscore” or if anything else strange going on with connecting to you.

Would be interested in reading what you read about the attack you mention, without context hard to see if it applies to Peercoin or just other POS coins. Are you aware SunnyKing still does some checkpointing behind the scenes to ensure many of the POS style attacks can not happen on Peercoin and the parameters chosen in Peercoin were specifically chosen to reduce such attacks that have been raised that I have seen so far. Hence I will not judge till I see your article so if you can dig it out that would be great. Sorry about the orphans though tough tiime when running a pool i know :frowning: so hopefully we cn help you get more connections and reduce your orphans :slight_smile:

Here a list of ip’s running peercoin nodes https://www.google.com/fusiontables/DataSource?docid=1MaPs_lTQbq5iff36WAy9dMNUmQwSBXaqgY_O_RN0#rows:id=1

Fuzzybear

fuzzy@anonymized.invalid

P8jMq35pQKu812iB36YtjDc9XS5K5TArKn is peercoin.ecoining.com
PXXSMVjnP6geKo7B6mA5F7HZBD1J6Huxmz is give-me-coins.com
PKj3Tzmfux7tDWJa7e8zvxkPz3LgfnfMLA is ppcoin.d7.lt
PKtAghhyy1qrDsfPjLpu7Z5v95Tf3HfAsv is coinotron.com

Network hashrate is calculated from the Peercoin’s PoW diff, which is adjusted progressively and reaches its peak value only a few blocks after PoW’s current real hashrate. Also, the difficulty is an average of the ongoing PoW’s hashrate. Which is also the reason why whales only mine for a few minutes, sometimes at 2PH/s and leave immediately after the first 2 blocks are found and consequently before the diff completely adjusts (so that their reward is based on the current PoW’s diff and not on the PoW’s diff resulting from their 2PH/s). I may write something about this later, it’s in the pipe.

very helpful Thireus thank you

I have started a new project almost there for the pie chart

http://charts.peercointalk.org/

Fuzzybear