Block 39108 has finally been solo-mined - took 9.5 hours.  Now my wallet says 2 transactions, no details, but Immature is 50.00 NBL - shouldn't it show 100.00 NBL?

listtransactions in debug console shows:

[
{
"account" : "",
"category" : "immature",
"amount" : 50.00000000,
"confirmations" : 2,
"blockhash" : "b03e6b6e004265075d0d3081e05880b65b5117bb7c79ce40a310fbb09d41f78c",
"blockindex" : 0,
"txid" : "9503ba399997b3d31d4c8d268c4e8f6f10e89e53e226049958ff9d69429274c6",
"time" : 1388288694
},
{
"account" : "",
"category" : "immature",
"amount" : 50.00000000,
"confirmations" : 1,
"blockhash" : "7174020a2afb1c18ff8a6013cf9b4f2309049c62da49836f731185abb8a02064",
"blockindex" : 0,
"txid" : "d03143658f3b16200148fb5aecfcc29466b43bc0047e1064bf0f6b5386b1ef11",
"time" : 1388322989
}
]

Also the client is again trying to synchronize to the litecoin blockchain.  When I check the debug.log file, it appears to be wanting to connect to a peer on port 9333.  The debug.log file shows that mostly these clients on port 9333 are disconnected for misbehavior when they respond with a different version i.e.

Disconnected 85.11.41.149:9333 for misbehavior (score=100)

But, this is not happening to all of them, and eventually one is used as a peer, then we have the problem of trying to sync.  I read that previously this was fixed by using the connect=nblnode.digitalindustry.info but this node is not working, so the problem continues.

I stopped my wallet, then deleted the peers.dat file and restarted my wallet.  Now it comes up and didn't try to sync with the litecoin blockchain so I guess this is fine now.  Also I changed my firewall settings to allow port forwarding of tcp/8550 to come to my wallet machine - maybe it will make it easier for others who may need to locate a node.

After 5 hours still working on block 39108 - but noticed that the wallet now says out of sync.  This is probably based on the time of the last block received or found.  The 4 other peers that my wallet is connected to - show 39107 as the current block number.

I solo mined block 39107 - cgminer shows block accepted, and my wallet shows 1 transaction, but no details - so what is going on?  No amounts unconfirmed either.

I checked the nbl.pnwminer.com pool and it is showing as currently working on 39107 - so did I just waste my 2 hrs of mining for nothing?

Also, somehow the wallet is trying to sync onto the litecoin chain.  Somehow it connected to a litecoin wallet and thinks "~44817 block(s) remaining".

So, do I close my wallet and open it again?  If I do this, will the block that I just solved stay?

[Edit]

I closed my wallet, then reopened, and it got connected to the network - yes, green tick.  It still says 1 transaction but no transaction details.

I went to the debug console, and the listtransaction command gave me the following:

[
{
"account" : "",
"category" : "immature",
"amount" : 50.00000000,
"confirmations" : 1,
"blockhash" : "b03e6b6e004265075d0d3081e05880b65b5117bb7c79ce40a310fbb09d41f78c",
"blockindex" : 0,
"txid" : "9503ba399997b3d31d4c8d268c4e8f6f10e89e53e226049958ff9d69429274c6",
"time" : 1388288694
}
]

So, I guess this is good, and I just have to keep mining away!  A pity that the wallet only shows Confirmed and Unconfirmed amounts, so maybe have to wait for the immature amount to get a few more confirmations before it becomes unconfirmed...

[Edit2]

Sorry spoke too soon, the green tick went away and it is trying to sync again to the litecoin blockchain.  I guess it won't succeed, but maybe I should just delete my peers.dat and start again.

Last block found is 39106 - although the mining pool was still working on this for the past 5 hours, so I am having to do other things with my rigs for the time being - need to try to earn some more coins somehow.  Most of the other miners are gone, so I am having a go at solo mining.

One thing I should mention is that this morning, I was unable to get connections to the network until I realized what I had changed since last night.  I changed my nibble.conf to put back the connect line last night and after that it failed to connect.  Then I removed the connect line, i.e. changed it to

;connect=nblnode.digitalindustry.info

and then restarted my Nibble client, and it got a connection - 1 and now 2, and updated to the current block 39106, but the green tick hasn't come up yet - maybe it takes a while, so try this - everyone who is having trouble connecting and synchronizing.

Looks like there is still life in this old bird.  A couple of other miners have come out to help - one of them with a lot of hashing power.  However these blocks are still taking their time to crack.  Also I opened my Nibble wallet again, and now it hasn't found any connections - will leave it for a while.

Ok, upgraded to Grain 1.2 without any issues.  The network traffic is still there, but it is due to nodes that are stuck on block 35583 and something like that.

I took my laptop to my sister's place and used her internet - Nibble eventually synchronized although it sat there saying there was 7600 blocks to go, for a very long time.  After dinner I found it had synchronized.

Now at home, I start the Nibble client and it got one connection to the network and appears to be synchronized - certainly it is at block 39102 which agrees with the mining pool that I am mining at.  I think the problem for me is that I go through two firewalls at home, so may need to look at that and work out if I should dedicate a virtual machine to running the client and have it available 24/7.  I have a few hardware upgrades to do first though.

Anyway, the peer that I am connected to is:

"addr" : "109.10.236.54:8550"

That might help you.

That pool has problems at the moment, on the wrong chain or not sync'ed I believe.  I would like to try it out once they sort it out.

Current block is 39099 - taking a bit of time to crack, been working away for just over 3 hrs now.  Next difficulty change in 1221 blocks - something to look forward to.

[Edit] Now current block is 39102 - been taking its time.

Hi, I would love to hold some but my wallet won't sync.  This is happening to others as well, so how do we fix this - or give you some time to get the celebrations out of the way.

Merry Christmas and Happy New Year to everyone!

Finally some movements, 2 blocks in the past 3 hrs, means 2 confirmations on transfers it seems.  So we need to keep mining blocks to keep the system running.  Now - how do we get our wallets synchronized?

It seems that most of the network mining power disappeared and left the difficulty of the coin at 7.1957 which is quite high for the remaining miners.  I have a pending transfer at Cryptsy that has been sitting there for over 10 hours with 0 confirmations so have decided to put some mining power back on NBL and see if I can get some movement.  Up to now there appears to be only 4.4MH/s mining, so with my 2.3MH/s - maybe we can start moving blocks.  One problem that I foresee is that the difficulty will stay this way for at least another 1200 blocks or so, before it will drop down to match the mining power and get reasonable.  It isn't helping when we cannot synchronize our wallets and when our transactions cannot confirm.

bosian,

Hi.  I set my Wireshark to capture my network traffic for a period of 15 minutes.

74467 packets were captured and saved to a file size of 59,391KB.

When I filter these packets for those to/from tcp port 11054, I get 70342 packets and saved these to a file - size 58,659KB.  This is in .cap format so these are generally the raw capture data with just a small header.

Here in Australia, we are generally on metered internet connections, so running my Grain wallet for a day would use up possibly 5.6GB a day - and this is just having the wallet open on a computer.  I think this is something we need to look at, since this would use up 86% of my monthly allowance - that explains why things have been going so slowly in the past few days.

-John

[Edit] Just had a look at my firewall traffic graph - shows average outbound traffic of 56.5 KBps during the time everyone here was sleeping.  I took a snapshot but can't work out how to insert the jpg.

[Edit2] I closed my wallet, then waited for the firewall to refresh its traffic graphs.  Outbound traffic on my internet connection dropped from 64.397KBps to 2.960KBps.

bosian,

Hi - my concern is that this debug shows that the client maybe is causing a lot of network traffic, if it does this each time a new block is received.  My internet connection isn't great at best and lately with all my miners and my son's bitcoin miners - our internet is a bit slower than usual.  I will have a look and see what network traffic is being generated.

One thing, has anyone else noticed that the debug.log file is growing very large?  As of this morning it was over 110MB so I stopped my wallet, renamed it to start a new one, and restarted my wallet.

What it is showing are lots of these.

trying connection 184.78.158.84:11054 lastseen=9.0hrs
getblocks 37083 to 00000000000000000000 limit 500
  getblocks stopping at limit 37582 000000001f656535fd6f
received getdata (3 invsz)
getblocks 37083 to 00000000000000000000 limit 500
  getblocks stopping at limit 37582 000000001f656535fd6f
getblocks 37583 to 00000000000000000000 limit 500
  getblocks stopping at limit 38082 73c9a23843e09cdc019e
getblocks 37583 to 00000000000000000000 limit 500
  getblocks stopping at limit 38082 73c9a23843e09cdc019e
getblocks 37583 to 00000000000000000000 limit 500
  getblocks stopping at limit 38082 73c9a23843e09cdc019e

etc, etc - it seems to be going through each peer and checking what block it is up to - and does this every time it receives a new block.  Currently it is 1MB and has been running only 40 minutes or so.

Right now it is 47186

I am also having trouble getting connections in order to synchronize.  So far, my nibble client is showing 0 connections.  I am using the config from the first post.  Are there any working nodes that we should know about?

With other clients, if the sync was stuck at a particular block, I have closed the client and reopened it and the sync then continues, but I cannot even get started.

Thanks bosian,

My wallet has synchronized finally, I tried solo mining for a little while but found nothing, but then my 1.7MH/s compared to 80+MH/s network should not get much unless I run for much longer.

9QnnqgmyZsPH5T8zGM64je3GAadQXGNNdr

[Edit]  Merry Christmas to everyone!

Thanks Jollyburner, I am running the fixed qt file with the downloaded blockchain.  It is at block 41133 but says there are 1222 blocks or so to go, but I guess this is ok as it is?  Or should I remove my peers.dat file and start it again?

[Edit]
Ok - decided to remove my peers.dat file then started the wallet again, after a few minutes - I get a green tick - synchronized!

[Edit2]
Now back to saying a couple of thousand blocks to go, so I guess this is as good as it gets.

I just tried solo mining with a Radeon 5850 card getting 320kH/s - my cgminer is saying "Found block for pool 0!" but am not getting accepts.  I checked the wallet, still on block 43551 - this message came up a couple more times, then I get a REJECTED ...

The debug.log file showed only the reject as follows:

BitcoinMiner:
new block found  
  hash: 0000000289575a1100c858f3b302c6e56795a0a68240aa5b92f6f08b90ec5537  
target: 0000000362c00000000000000000000000000000000000000000000000000000
CBlock(hash=0000000289575a1100c858f3b302c6e56795a0a68240aa5b92f6f08b90ec5537, ver=4, hashPrevBlock=36f0fe774d3cf8e7256f2c3cdf7f0c14ecfe6563306d2b72163873165de40c78, hashMerkleRoot=102f67309ec2f273da5def5956b9576addd88a6b2396c57d9eeff5a6adcab481, nTime=1387916134, nBits=1d8362c0, nNonce=1570598144, vtx=1, vchBlockSig=3046022100f7dcf994aaba301b6fbb2776ddaf13ae25f3c57a0a56d4cf07ea987324e228dc022100b628010c3b4c1fc29cee1587c60db3a14e174f7f23599dad192697b7e25b948b)
  Coinbase(hash=102f67309e, nTime=1387916040, ver=1, vin.size=1, vout.size=1, nLockTime=0)
    CTxIn(COutPoint(0000000000, 4294967295), coinbase 0320aa000110062f503253482f)
    CTxOut(nValue=1163.00, scriptPubKey=02083c6df2de9a7ff8bdf12a8f9e65a63019fb59fbad38c8b8a74d9332396b3f9d OP_CHECKSIG)
  vMerkleTree: 102f67309e
generated 1163.00
ERROR: CheckProofOfWork() : nBits below minimum work
ERROR: CheckBlock() : proof of work failed
ERROR: ProcessBlock() : CheckBlock FAILED
ERROR: BitcoinMiner : ProcessBlock, block not accepted

So, what gives?