Topic: [ANN] Nybble 0.6.5.2 Nybble - New Wallet Win, Mac and Source, New Pools. - page 9. (Read 31828 times)

great to see - i don't want to blow our own horn here but we have had a solid node built in since 6.5

We have one of the most switched on Devs working with us , Caps has only just decided to build in nodes in 4.1 i believe.

**

I like Caps a lot they have done interesting things with he re-target , but i'm not convinced that all the Forking isn't due to that in some way either, but they have taken the rough road and hopefully it will pay off , i respect that in the same way we refuse to bend to the "latest" and change our parameters either.

history will judge us.

This is what I have in my .conf at the moment:

addnode=106.187.94.209
addnode=70.79.24.157
addnode=109.80.94.251
addnode=95.110.156.138
connect=nblnode.digitalindustry.info

This gives me 5 working nodes

yes I've look at this this is due to the IRC Node fallback - we may even take this out of the code , but its not a Client error

if you put the Connect node in your list also.

let me double check but have you guys got this in there

connect=nblnode.digitalindustry.info

I am running the latest greatest from the OP in this thread. I have been having the Litecoin sync issue on every version of the client since it came out.

I mined 28361 and 28363, the latter of which must have orphaned the one you are missing sorry bout that!

As for the bad node, I am trying to check my peers when the client tries to sync up with LTC, and I noticed that 1 peer had a starting height of ~64k and a weird port number.

Also note, I am the one who found the last two blocks... though I found 2, I got only 1... Both were accepted, there is no-one else to be orphaning... something ate one of my blocks. It even updated the network with my block, but it never made it into my wallet. Only the block after the first block I found. (Unless it doesn't give us credit for the block just found, until the next block is found. Which makes sense, sort-of...)

Nice to know I am not the only one mining now. I don't mind earning all the coins for myself... but I am effectively 99% of the network at the moment, by the stats. lol... screw 51% attack, I'm gonna 99% attack! JK

BTW, do you have the new client? I have not seen that since the old client.

You have a bad node on your list...

Use this config info...

(You may have to delete the block info and peer info files. Everything except the wallet.dat and your config file.)

splash=0
server=1
gen=0
testnet=0
daemon=1
maxconnections=10
listen=1

addnode=106.187.94.209
addnode=70.79.24.157
addnode=109.80.94.251
addnode=95.110.156.138

addnode=99.132.231.140
addnode=72.11.149.185
addnode=207.12.89.2
addnode=46.39.246.24
addnode=54.244.198.104
addnode=72.78.100.3
addnode=71.59.225.19

Just be aware that there only seems to be 4 connections alive, including my own connection, at the moment. The top four are all I can connect to. The rest fail to connect.

My Nibble client randomly decides it is going to sync to the Litecoin blockchain. Any idea on how i can stop this from happening?

Edit: Here is a screenie of what I am talking about...

http://i.imgur.com/MYWlkh1.jpg

indeed - i hear your concerns .

looking into it.

Exactly, it has been block 28353 for days...


My comment about buying wasn't about "why are they buying it"... as in... "why spend money on it"...

My comment was about... "why would they buy a coin that can not be sent"... since it is "stuck" on that block, there is no possibility of "getting any transactions"... since a transaction requires a block to be solved, to transmit the coin.

I'll test it but as far as Ive seen its functioning all be it slowly after the diff hike - i'll check it out .

everything i have says 28353 - so i'll investigate - the market drop is a part of the market mechanism why would people want to buy high into selling multipools ? , i don't see this as an overall negative in fact on/close to next diff change I will try to inform the market as to pull any large buy orders , in the effect to make these guys sell lower .

but that's up to the market again .

the miners are serving a purpose and the buyers want to buy cheap , why not?

for DGC, i'd advise number 1 on the list of things to do would be a Dynamic hardened check point system , for Nibble we of course would roll back or stop the BC but for DGC it would do a lot of damage , if i were the DGC Dev that's what i'd be spending my funds on , or not of course.... its an interesting political environment. 

If i were DGC I'd Checkpoint every 1000 blocks - without a worry in the world.

why they have not done this or even updated the broken client , I'm not sure ?  perhaps they are giving up on it ? but I'll make these suggestions to them.

I still can't connect to anything that runs...

Latest block is 28353, 4 days ago, as the wallet reports it. Never gets past that point.

Starts downloading saying the block-height is 28224... Goes up to 28353 then dies...

No IPs in the list ever go past that block... Yet, someone is mining.

NOTE: This is the windows build (v0.6.5.2-g397646f-nibble)

Might be why the coin is taking a nose-dive in value. Still waiting for a fix. Not sure how anyone can be trading if the coins can't be sent to anyone...

Hey, thanks! My Nibble addr is NQLHoxpzrrsPhoYsDiBNVcDA3L1J4GBG6K -- any problems with the Mac wallet, post here or PM me and I'll see what I can do.

My wallet count went up by one block, the chain went up by one block... the cgminer reported it as "approved"... (Nothing indicates "orphaned" blocks in the wallet. I would have to dig through the wallet to actually "see" the block info.)

The block I found was the one listed above, 28338. Even the coin-choose website indicated that was the new block-height, after I found it. (The one that I stated was just found, as I was typing.)

It could have just been a one-time orphan. I switched to another coin after that.

Testing again tonight...

If it orphans again, then there is a fork, and I am just on the wrong side of it. (Not sure how that works, if the wallet is the mining access, and the network it is talking to has identified it as an orphan, it should be moving me to the correct chain.)

The only thing weird I noticed, is that the wallet still said, "not synched", while I was mining that block. The block-height was the one listed on all the coin pages, to I took a risk and mined. Once it found that block, the orphan, my wallet finally said it was synced...

I will try registering on a pool later. It does not show you approved or rejected blocks, only approved or rejected shares. If that pool is on the right chain, then it would show with the other miners, since they are all mining to the same wallet for the same chain. (The pools wallet).

brb, trying to mine it again.

P.S. I am not worried about loosing one block, after the 60+ blocks (3000+ coins), I lost from the days of mining it after the 27th to the 29th... all those disappeared from my wallet.

would like to thank Maxpower for the Mac client thank you very much Max

https://www.dropbox.com/s/0eptl596hxnjpl0/nibble-qt-0.6.5.2-Mac.zip

go mad and post your NBL address here !


ISAWHIM :

can you confirm if it was orphan or not?

as far as we looked the chain is not forked , but i don't discount this possibility i will start to test now.

can i ask where you mined or did you solo mine ?

is it possible for you to register here?:

http://nbl.pnwminer.com

If you mine a block here as a test - I will give you a block so that we may help resolve this .

lol... spoke too soon... I think...

Says I found a block, but nothing in my wallet... seems orphaned.

If I am on the right chain, and the other is the wrong one, then it should show later, once this one grows-up past the incorrect one. I assume that the other one my wallet sees is invalid, or it would have me mining on it. It must see it, or it would have added the found block to my wallet.

so... does that mean the other block is invalid... or it just isn't selecting the correct taller chain? (Could that be the bug? That it is selecting the second largest chain, or that the other guys are just not "talking", sending the taller chain, but still reporting the height?)

This is going to sound odd... but check that your variables are matched correctly...

28337 is what it seems stuck at...

See that all ints, units, longs, floats, doubles, etc... actually give what you expect in ranges.

Same with shift commands and masks... It is obviously related to processing of a "valid block"... Unless it is screwing-up the NONCE or the wrong value for the initial genesis-seed/block is being used. (Thus, rejecting all our work, because it is all invalid.)

I would bet that it is something silly, like cramming an int into a uint, and reading it back out as an int. (That alters the value when it shifts the byte for the negative-switch, to the last bit. Safe for small numbers but once you reach half-int, it changes.)

Though, it seems to be letting me mine. Will be sad if these blocks just disappear too... like my last days work mining.

As I typed, I found block 28338... now it says I am synched... I fixed it! lol... or just gonna eat my coins again!

Great to see ! !

We have a resolution and a v0.6.5.2 released more checkpoints and fixes, source and binaries updated - 

resolved - tentatively

updated config file on topic -

if syncs occur please notify - will be adding to these nodes .