[ANN] Nybble 0.6.5.2 Nybble - New Wallet Win, Mac and Source, New Pools.

[JL0z]

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?

[1714168643]

1714168643

[1714168643]

1714168643

[1714168643]

1714168643

[digitalindustry]

I have not abandoned Nybble - will come back to Nybble in the future -

Its a great crypto to hold IMO -

[JL0z]

I have not abandoned Nybble - will come back to Nybble in the future -

Its a great crypto to hold IMO -

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!

[JL0z]

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.

[mtbitcoin]

same here, no connections...

Yes, same here. Any known nodes to connect to?

[JL0z]

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.

[JL0z]

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.

[JL0z]

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.

[JL0z]

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.

[JL0z]

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.

[JL0z]

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.

[JL0z]

same here, no connections...

Yes, same here. Any known nodes to connect to?

Hi all, here is a list of nodes that I found my client was connecting to - for the past couple of days.

addnode=77.251.56.232
addnode=54.200.132.23
addnode=194.79.23.98
addnode=95.31.7.14

if you want to try my client, it is dynamic but at present would be

addnode=124.189.53.150

[JL0z]

I have been persisting with the Nibble/Nybble mining - current block being worked on is 39117.  However I am finding that the client is making connections to not just litecoin but also worldcoin and other altcoins.  This comes about because the client code is based on the original Bitcoin client - future developers should really change the subversion to make it distinct and then check for this when making peer connections.  This should avoid peering with incompatible altcoin clients.  An example of what I mean is:

09:17:45 getpeerinfo

09:17:45
[
{
"addr" : "54.200.132.23:8550",
"services" : "00000001",
"lastsend" : 1388441860,
"lastrecv" : 1388441839,
"conntime" : 1388395424,
"version" : 60001,
"subver" : "/Satoshi:0.6.5.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 39113,
"banscore" : 0
},
{
"addr" : "31.185.159.126:9336",
"services" : "00000001",
"lastsend" : 1388441857,
"lastrecv" : 1388441657,
"conntime" : 1388420589,
"version" : 60002,
"subver" : "/Satoshi:0.6.4.4/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 140029,
"banscore" : 0
},
{
"addr" : "176.25.115.107:11081",
"services" : "00000001",
"lastsend" : 1388441862,
"lastrecv" : 1388441556,
"conntime" : 1388425483,
"version" : 70001,
"subver" : "/WorldcoinFoundation:0.8.5.1/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 11583,
"banscore" : 0
},
{
"addr" : "95.31.7.14:8550",
"services" : "00000001",
"lastsend" : 1388441830,
"lastrecv" : 1388441834,
"conntime" : 1388434279,
"version" : 60001,
"subver" : "/Satoshi:0.6.5.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 39116,
"banscore" : 0
},
{
"addr" : "86.186.14.143:11081",
"services" : "00000001",
"lastsend" : 1388441816,
"lastrecv" : 1388441830,
"conntime" : 1388441336,
"version" : 70001,
"subver" : "/WorldcoinFoundation:0.8.5.1/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 30194,
"banscore" : 0
},
{
"addr" : "79.120.114.167:11081",
"services" : "00000001",
"lastsend" : 1388441859,
"lastrecv" : 1388441863,
"conntime" : 1388441343,
"version" : 70001,
"subver" : "/WorldcoinFoundation:0.8.5.1/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 5843,
"banscore" : 0
},
{
"addr" : "123.52.1.56:9333",
"services" : "00000001",
"lastsend" : 1388441864,
"lastrecv" : 1388441860,
"conntime" : 1388441487,
"version" : 70002,
"subver" : "/Satoshi:0.8.5.1/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 488351,
"banscore" : 0
},
{
"addr" : "84.245.71.31:9333",
"services" : "00000001",
"lastsend" : 1388441845,
"lastrecv" : 1388441858,
"conntime" : 1388441673,
"version" : 70002,
"subver" : "/Satoshi:0.8.5.1/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 488351,
"banscore" : 0
}
]

Here we see WDC client on port 11081, LTC client on port 9333, and FTC client on port 9336.  I realize that we cannot restrict based on port 8550 alone because some clients may be forced to use different ports due to local network restrictions, but maybe the "subver" could be used to indicate "/Nybble:0.6.5.3/" assuming 0.6.5.3 would be a later version to 0.6.5.2 - then we could make peer connections based on looking for Nybble etc.  I don't find this problem happening with other altcoin clients, and I do run quite a few of them from time to time - so can we get this fixed?

[JL0z]

Happy New Year!

I don't see much mining activity on NBL at present.

The last block solved was 39119 - very slow going.  The block has been broadcast, but I don't have any incoming confirmations as yet that the network has accepted it.  I think this might be due to too few operational nodes - maybe they have shutdown for the holidays.  I was looking at a pool but the nbl.pnwminer.com pool seems to be behind at 39117.

A few things I have done, I configure my Windows Firewall to block nibble-qt.exe from accessing certain outbound tcp ports.  After I did this and continued to block ports I find that my client now does not try to synchronize with other coin's blockchains.  I realize that this is really unnecessary as other blockchains cannot be incorporated but it does reduce the network traffic and reduce the cpu usage as the received blocks are not being orphaned all the time or being rejected.  I am blocking these ports, 2543, 4401, 7785, 7999, 9333-9337, 9527, 9556, 10333, 10442, 11081, 11351, 12128, 13809, 15678, 19667.  I realize that I could just block port ranges, but wanted to keep them individual - I check the debug.log file from time to time whenever I see it trying to sync incorrectly then block the port again etc.

Now I seem to only be connecting to one other node 54.200.132.23.  My client does connect to 70.79.24.157 but that node does not respond with a version message.  My node address is still 124.189.53.150 - so if there are any other working clients out there, can someone let me know.

[JL0z]

Hi - we need more miners on nbl.pnwminer.com - I tried solo mining, but gave up when I realized that solo mining requires 120 confirmations, now I am back on the pool which only needs 20 confirmations.  The current block is 39139 - been working on this for the past 8.4 hrs, we need more miners to speed this up - only 1181 blocks to go before the difficulty retargets to something a lot more reasonable.  I know this is a big ask, but if someone has spare mining power - NBL is still a good earner, but we need more miners so that transfers and deposits don't take forever.

[Edit]  This is just a long block, usually it has been taking around 2hrs per block, but if we get more miners, we can reduce the time.  Transfers and deposits generally need 8 or so confirmations, meaning 8 blocks to be solved - currently taking a day to confirm but more miners means more hashing power means quicker confirmation times.

[gizzig]

Hi JL0z

I Am mining in http://nbl.pnwminer.com, +1100 KH

do not let this coin die

[JL0z]

Hi JL0z

I Am mining in http://nbl.pnwminer.com, +1100 KH

do not let this coin die

Great - thanks.  Let's keep it up - there are 4 miners at the moment, so blocks should be getting quicker.  Currently on 39143.  That block 39139 took 19.5 hrs - I almost gave up on it, but glad I persisted.  Let's all keep this coin alive, although it looks like Cryptsy isn't confirming deposits - one I have is stuck at 8 confirmations for the past 4 blocks.

[gizzig]

If we are just 4 miners, we could change the source and recompile to change faster difficulty? is just an idea but we could do it by consensus.

(sorry english is not my native language)

[JL0z]

If we are just 4 miners, we could change the source and recompile to change faster difficulty? is just an idea but we could do it by consensus.

(sorry english is not my native language)

That is not advisable.  Also it will not work unless we only solo mine, since the wallet would have to be changed on the pool servers as well.  I suppose that there was never an expectation that the mining power would more or less disappear - which is sort of what happened.  With the release of new coins - many of the big speculative miners will jump onto a new coin, get a bundle then go onto the next coin.  They wait for the coin to hit an exchange, then sell out.  This then leaves a lot of coins in situations that the difficulty is high, and with little mining power.  However NBL still is worth something - more than some coins anyway, so it is worthwhile mining for a steady income.  I am aiming with my 2MH/s to get about 0.02BTC equivalent in coins a day.  With NBL I am not reaching my target, but am prepared to keep going.  Once the difficulty drops in 1176 blocks - we should be able get around 0.1BTC a day I expect if the coin value doesn't drop.  When will this happen - if we get a few more miners, maybe get to 20MH/s on the pool, we can do this in about 1 month.  If we can't - then it will take longer.  Don't forget that the target block time is 2.5 minutes, so once the difficulty retargets, we are aiming at about 576 blocks per day or 28,800 NBL a day or something like 2880 NBL for every 2MH/s miner - current value is 0.15BTC.  This is optimistic and might not work for very long before people find out about it and start mining it again - but if we are there at the beginning, we have a head start.

[Wekkel]

What is a reasonable bet for the difficulty to reset to normal values again? I may join the mining party if it makes sense (experienced Nibble from the start).