As an established member of this forum has said mining talk is ok, I advise suprnova as you simply use your worker name in the -zwal parameter and don’t need an address. For the official wallet check the GitHub or homepage, beware of any others than the official as they might be illegitimate wallets.

I think suprnova pool to start off with. Though this isn’t a mining talk thread and there are separate mining boards in this forum, so we should be respectful of that. https://btcp.suprnova.cc

I just made a mistake and posted that we went live, but that was in fact the dev fee connecting and mining on my rig, hmf. Apologies to anyone who saw that, I deleted it very quickly after noticing.

The failure to connect on suprnova is universal. Pool is showing 0 workers and 0.00 MH/s for those ITT with this issue.

As no one is able to connect it’s likely that we’re just waiting for the main pool to go live quite soon, so I’m leaving my rigs on, retrying to connect at the default of 20s. I was mining on testnet with the same settings as now so there’s no issue with settings. Suprnova pool operator is also advising people to test their rigs on the ZEC pool now which also increases probability that we are simply waiting for the main pool to go live.

The development team should update the thread with the exact time the main net mining goes live, or at least tell us that they plan on releasing the mining start time. Otherwise this gives a mining advantage to whomever knows the exact launch time.

Sure, “a couple of days” after the snapshot is fine when updating on final QA but they should elaborate on this exactly when things are ready, then give a definitive time (preferably at least a few hours) for the main net launch so all the miners can start the race at the same time. I know suprnova usually switches from test to main automatically which is a solution for some but does not address the core issue.

Unless there is another valid reason for this such as avoiding chain splits or 51% attacks?

Thanks for the clarification, that is what made initial sense to me but was just seeking some clarification. The only other fork I bothered with was bitcoin cash. From the forks I’ve seen, the snapshot & fork block number have been pre determined and simultaneous, I assumed that was necessary prior to BTCP. Not that I have any issue with the way this is being rolled out. There’s also apparently a bit of an underlying knowledge gap on the specifics of forks on my part hence the uncertainty, which again I appreciate you clarifying.

As the snapshot has now occurred, does that mean I can now move my BTC from the address that was holding the BTC during the snapshot (with bitcoin core full node, while cold storing the priv key from said address to import to BTCP when necessary) Or, do I have to wait the dev stated “couple of days” before moving my BTC from the snapshot address?

Also, any clues as to when mining starts, I see suprnova are running a testnet pool which is a good sign, will be pointing my rig there so a more specific mining start time would be useful.