Orphan block

Post Reply
moa
Posts: 255
Joined: Mon May 23, 2011 6:13 am

Orphan block

Post by moa »

Code: Select all

./namecoind listtransactions

Code: Select all

    {
        "account" : "",
        "category" : "orphan",
        "amount" : 50.00000000,
        "confirmations" : 0,
        "txid" : "dc8161afe5a3fcd4ee082f109d9d2199edfa8d135b582e1b486bacab7f5e46bb",
        "time" : 1306519280
    },
debug.log

Code: Select all

ERROR: ConnectInputs() : 97c005b98b mapTransactions prev not found f350f782c7
ERROR: AcceptToMemoryPool() : ConnectInputs failed 97c005b98b
storing orphan tx 97c005b98b
What's the standard procedure for dealing with an orphan block in namecoin?

Do we need to flush it out of the wallet or something?

Does it stop me from getting further valid blocks in the chain while it is hanging around?

moa
Posts: 255
Joined: Mon May 23, 2011 6:13 am

Re: Orphan block

Post by moa »

So getting a few more orphan blocks coming through and then this message.

Code: Select all

ConnectInputsHook() : connecting inputs on 7f0ecb7df6c39a3425f2cd45143b6ebd03a07513295e8a1a82dd98876f179890 which was not in pending - must be someone elsesSetBestChain: new best=00000000000f2263595f  height=7068  work=17603620395152068
Have we got a major namecoin blockchain split?

Or something else "not quite right"?

khal
Site Admin
Posts: 708
Joined: Mon May 09, 2011 5:09 pm
os: linux

Re: Orphan block

Post by khal »

I didn't see this split in my logs (but one older on block height=5998).

Things are not different from bitcoin on that part.
NamecoinID: id/khal
GPG : 9CC5B92E965D69A9
NMC: N1KHAL5C1CRzy58NdJwp1tbLze3XrkFxx9
BTC: 1KHAL8bUjnkMRMg9yd2dNrYnJgZGH8Nj6T

Register Namecoin domains with BTC
My bitcoin Identity - Send messages to bitcoin users
Charity Ad - Make a good deed without paying a cent

moa
Posts: 255
Joined: Mon May 23, 2011 6:13 am

Re: Orphan block

Post by moa »

Okay, it has happened again, this crap showed again in debug.log immediately after I got a block orphaned.

Code: Select all

received: inv (37 bytes)
  got inventory: tx 8356f24d4b6316bf32e8  new
askfor tx 8356f24d4b6316bf32e8   0
sending getdata: tx 8356f24d4b6316bf32e8
sending: getdata (37 bytes) 
received: tx (2711 bytes)
ERROR: invalid number of arguments for name op
ERROR: ConnectInputsHook() : name_firstupdate on an unexpired name
ERROR: AcceptToMemoryPool() : ConnectInputs failed 8356f24d4b
storing orphan tx 8356f24d4b
Have we got a rogue node on the namecoin network?

khal
Site Admin
Posts: 708
Joined: Mon May 09, 2011 5:09 pm
os: linux

Re: Orphan block

Post by khal »

It can be :
- an old client
- a modified client
- someone without the full blockchain

We need a patch to purge those things and don't relay them...
NamecoinID: id/khal
GPG : 9CC5B92E965D69A9
NMC: N1KHAL5C1CRzy58NdJwp1tbLze3XrkFxx9
BTC: 1KHAL8bUjnkMRMg9yd2dNrYnJgZGH8Nj6T

Register Namecoin domains with BTC
My bitcoin Identity - Send messages to bitcoin users
Charity Ad - Make a good deed without paying a cent

demonbl@ck
Posts: 8
Joined: Thu Jun 02, 2011 2:20 pm
os: linux

Re: Orphan block

Post by demonbl@ck »

Yesterday i got this:

Code: Select all

{
    "account" : "",
    "category" : "orphan",
    "amount" : 50.00000000,
    "confirmations" : 0,
    "txid" : "fdd3b41cce1039d05e7bd3b65c0b8b4a038ad707c8094bc88b77713af6c9397f",
    "time" : 1307245908
},

Code: Select all

sending: getdata (109 bytes) 
received: block (20733 bytes)
received block 0000000000019b44c413
ProcessBlock: ORPHAN BLOCK, prev=000000000013454ef275
sending: getblocks (709 bytes) 
received: tx (256 bytes)
ERROR: ConnectInputs() : fb506f00cc mapTransactions prev not found d1cf871af9
ERROR: AcceptToMemoryPool() : ConnectInputs failed fb506f00cc
storing orphan tx fb506f00cc
received: tx (256 bytes)
ERROR: ConnectInputs() : 1b450f5469 mapTransactions prev not found 6bcd44adbe
ERROR: AcceptToMemoryPool() : ConnectInputs failed 1b450f5469
storing orphan tx 1b450f5469

Do i have to do something?
After getting it i also got a valid block

moa
Posts: 255
Joined: Mon May 23, 2011 6:13 am

Re: Orphan block

Post by moa »

No, you do not have to do anything. It will just sit in only your blockchain all alone for a special little reminder of the block that never was ... (unless the blockchain on your puter is deleted.)

penta
Posts: 9
Joined: Tue Jun 07, 2011 10:46 am

Re: Orphan block

Post by penta »

of the 3 first blocks ive found 2 have been orphans, and then after that i havnt found any blocks something wrong here? iam doing 350mhash and mined for over 2days now, is this normal?

penta
Posts: 9
Joined: Tue Jun 07, 2011 10:46 am

Re: Orphan block

Post by penta »

also using guiminer i get
Listener for "namecoin": 07/06/2011 17:33:30, Bitcoin is not connected!
constantly spammed, is this a guiminer/namecoin bug or am i not mining anymore? i havnt changed anything and found 1 block but dont remember seein that msg before.
guiminer reports mhash/s and difficulty 1 hashes: 9002

moa
Posts: 255
Joined: Mon May 23, 2011 6:13 am

Re: Orphan block

Post by moa »

There is some very strange behaviour surrounding orphan blocks going on the namecoin network.

Of the 11 orphan blocks I have so far 10 have all been orphaned by competing blocks within 60 seconds of my block getting solved. This means the network has found two blocks inside 90 seconds after I found my block that got orphaned. The other one was orphaned in 5 mins (more normal solve time).

I have relatively good connectivity 13 or 14 nodes. What can be causing this kind of bizarre behaviour?

I think I may stop mining namecoins until this settles down as it is unstable/unusable as it is.

EDIT: okay, it seems like the problem was most likely IN MY CLIENT. It was a home-brew build on Fedora 12. Everything seems to run fine but there is some kind of problem that the client is missing tx on the network somehow and reports the "ConnectInputsHook(): message when a block is passed to it that has the tx that it didn't have. Seems to co-incide with orphaned blocks. Anyway, now I got a binary from the wiki link http://dot-bit.org/files/namecoin_linux32.tgz and seems to have gone away .... watching. Hopefully can say goodbye to the orphanage in my wallet. If you are having lots of orphan problems it may be your client causing the issue.

Post Reply