Indeed.

see https://bitcointalk.org/index.php?topic=509173.msg5917397#msg5917397 for nodes

https://bltz.crunchharder.net <----------- CORRECT FORK

Anyone got some working nodes? The ones in the OP don't work for me - had 0 connections, waited over an hour...

Thanks. I think all the forking has stopped now for quite some time (although I am not sure if Suprnova is still on the wrong fork, haven't seen anything posted by them)  -  even if they are forked, the vast majority of the network seems to be correct now so I wouldn't expect any further issues.

In any case, https://bltz.crunchharder.net has:

"blocks" : 852,
    "connections" : 9,
    "proxy" : "",
    "difficulty" : 61.26421419,

Probably around 1.5% actually if it takes a week to mine it all? That's about 0.5% per hour.

https://bltz.crunchharder.net <------------ CORRECT FORK

Yes, https://bltz.crunchharder.net is the correct fork

Yes that's one of the other big pools I've been checking https://bltz.crunchharder.net against to make sure we are on the right chain.


"blocks" : 784,
    "connections" : 11,
    "proxy" : "",
    "difficulty" : 44.94073338,

At https://bltz.crunchharder.net and the other pools I'm cross-checking against.

Haven't seen any significant forking for ages now apart from Suprnova.

It's not for pool operators to provide free bandwidth for you. Nor should any pool operator who cares about security for their users be opening their firewalls to their wallet servers - even if there are no known exploits for blockchain sync connections at present, I would consider that an unnecessary increase of the attack surface, and wouldn't expose users at https://bltz.crunchharder.net to an unnecessary risk.

What should happen is seed nodes in the source code, and seed nodes provided by _you_ running at launch, all it takes is a few cheap VPSs.

I mean, good on you for releasing a working wallet that compiles and works fine etc. which is more than a lot of launches, however more nodes should have been provided - it's not the pools responsibility to do that.

I have no idea what you are talking about - we have been constantly in IRC and here posting nodes, posting block heights and difficulties and attempting to help ensure the network reaches consensus as quickly as possible.

The devs should have put an adequate number of seed nodes up, and put then in the code, then there wouldn't be any partitioning like there has been.

Fortunately, it all seems to be resolving now. We've been on the same chain as the vast majority of the other big pools for ages now at https://bltz.crunchharder.net

 "blocks" : 756,
    "connections" : 10,
    "proxy" : "",
    "difficulty" : 39.41482576,

This whole thread is an example of why coin devs should certainly not be claiming that 30 confirms are sufficient for mined coins - they certainly are not, especially at a launch. We're on 120 confirms at https://bltz.crunchharder.net to ensure the safety of everyones payouts - we're also actively checking that we're in consensus with the other big pools as to the block height and difficulty (ie. making sure we're on the right fork).

Network seems to be converging now. Pretty sure all the pools (all the big ones at least) are on the right fork:

https://bltz.crunchharder.net has:

 "blocks" : 730,
    "connections" : 9,
    "proxy" : "",
    "difficulty" : 34.20972034

No we didn't, there have been multiple forks - did you read the thread or just come here to unjustly accuse people of stealing?

We have no confirmed blocks yet!!!

 "blocks" : 711,
    "connections" : 9,
    "proxy" : "",
    "difficulty" : 29.89330539,

"blocks" : 703,
    "connections" : 10,
    "proxy" : "",
    "difficulty" : 27.56629927,

Unless your post is just outdated by the time I'm replying, this chain is longer/harder ie. is the right one.

http://Https://bltz.crunchharder.net is 99% sure we're on the right fork - we're actively in IRC and checking the other pools to ensure we're on the longest chain with the highest difficulty.

EDIT: To posted above, sorry, you're on a shorter/easier fork - block 667 diff 17 here right now.

Here are our nodes:

addnode=89.164.145.53:24058
addnode=31.19.188.145:24058
addnode=81.65.237.181:24058
addnode=78.112.253.32:24058
addnode=88.125.4.64:24058
addnode=86.144.48.108:24058
addnode=94.79.181.2:24058
addnode=82.233.228.104:24058
addnode=176.9.9.88:24058
addnode=68.225.239.123:24058
addnode=84.99.198.95:24058
addnode=112.15.226.80:24058
addnode=84.238.145.127:24058
addnode=79.32.154.40:24058
addnode=178.33.228.14:24058
addnode=86.210.90.115:24058
addnode=80.236.198.72:24058
addnode=94.79.181.2:24058
addnode=5.71.5.180:24058
addnode=180.154.45.2:24058
addnode=176.9.9.88:24058
addnode=89.164.145.53
addnode=93.11.124.36:24058
addnode=98.126.98.138:45991

[19:08] <PCFiL>     "blocks" : 641,
[19:08] <PCFiL>     "connections" : 16,
[19:08] <PCFiL>     "proxy" : "",
[19:08] <PCFiL>     "difficulty" : 13.70832421,
[19:08] == Sy_ has changed nick to Sy_fuuuuu
[19:08] <PCFiL> yep
[19:08] <CrunchHarder> https://bltz.crunchharder.net now on that fork - based on the diff and height I think that must be the correct (hardest/most-work) chain