Topic: [ANN][BERN] BERNcash - X14 PoW/PoS Hybrid - BERN the big banks - page 12. (Read 151757 times)

idaho votes for democrat elective on the 24th noone here likes hillary think bernie will get this one with ease

http://ame-po01.chainworksindustries.com/bern/index.php though stratum difficulty might be high for smaller rigs, even on the low difficulty port.

Me, I am seizing the opportunity to grab solo blocks.

#FeelTheBERN
#MineTheBERN

Thank You so much! I'll follow your instructions!

Actually, Cryptopia is not forked.

@Rednex, you may have forked and it seems you have. You will need to resync, not Cryptopia, sorry to inform you. Follow these steps at your earliest convenience to correct your wallet:

Close your BERNcash wallet. Navigate in Windows Explorer to the %appdata%\BERNcash\ folder. Delete everything besides your wallet.dat file. Again, do NOT delete your wallet.dat file. Then start your BERNcash wallet and allow it to sync. It will take a considerable amount of time to sync, days even. But please allow it to run its course.

Once you have gotten onto the correct blockchain by this resyncing, your bigger amount transfer will be unconfirmed, meaning it never happened (on the real blockchain). You would want to make a new transaction to move your coins.

Sorry for the inconvenience. Please do not hesitate to ask if you have questions.

#rEVOLution

Hi rednex,

v1.2.3 is the current release.

I will test Cryptopia and if they have forked, contact them and ask them to resync.

Thanks for bringing this to attention. Your transferred bigger amount will be fine once they have resynced, do not be alarmed. Sorry for the hassle.

Just noticed the BernCash wallet synced block height (status green) much lower than actual block height. On the wallet bern statistics shows: 1565191. On cryptopia actually shows: 1586688 block height. My wallet BERN version: v1.2.3.0 where I found a newer version please?
Also transferred 2 days ago a bigger amount of BernCash to cryptopia, still not arrived. Anyone? Thx.

There is an explorer running at http://78.47.134.33:3001/ should anyone need it presently. transactions.bern.cash is being worked on, sorry for its absence. It will be sorted soon.

Work is ongoing with the wallet code to find and resolve the issues. It is being worked on with diligence and persistence. Sorry they conclude without a resolution thus far.

Thanks for the support. #rEVOLution

EDIT (minutes later): That mentioned explorer is still indexing, but it is synced. So the block list on the front is not complete. However; the block count in the lower right hand corner is accurate and blocks can be searched.

Messaged also in the CWI-Development Group as well mate.

Read back and you will find what the new daemon is doing on our end with the new CWI-Pool BernCash.

Hope we can work the issue out.

Just off topic here - and on a side note - Crackers, could you please PERMANENTLY remove GRN and OZC from your pool? The diff from your pool is killing stopping a LOT happening mate. ZPool is one hell of a pool, but not for the 'smaller' coins like GRN and OZC. Would be greatly appreciated mate.

Back to BERN.

#crysx

I had to travel for some personal matters this past weekend. I have been doing what I can remotely from my laptop when I can. I will be back at my desk in < 24 hours where more focused work on the matter can continue. Sorry for the continued hassles.

stuck again...

restarted again and seems to accept this time.

:\

resynced but seems all blocks are rejected right off the start now:

ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
ThreadRPCServer method=submitblock
connection timeout
trying connection 47.247.171.47:32020 lastseen=1262.1hrs
connection timeout
trying connection 31.200.140.175:32020 lastseen=2809.8hrs
ERROR: ConnectBlock() : UpdateTxIndex failed
InvalidChainFound: invalid block=00000000047690ac7e26  height=1578287  trust=1952224469896987  date=04/15/18 13:05:24
InvalidChainFound:  current best=9786aec597be552b2174  height=1578286  trust=1952224469856370  date=04/15/18 12:47:25
ERROR: SetBestChain() : SetBestChainInner failed
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
ThreadRPCServer method=submitblock
connection timeout
trying connection 90.220.67.149:32020 lastseen=7572.1hrs
socket no message in first 60 seconds, 0 1
disconnecting node 174.138.37.189:32020
ThreadRPCServer method=submitblock
connection timeout
ERROR: ConnectBlock() : UpdateTxIndex failed
InvalidChainFound: invalid block=000000000a8f5aa8fd08  height=1578287  trust=1952224469896987  date=04/15/18 13:05:24
InvalidChainFound:  current best=9786aec597be552b2174  height=1578286  trust=1952224469856370  date=04/15/18 12:47:25
ERROR: SetBestChain() : SetBestChainInner failed
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
ThreadRPCServer method=submitblock
trying connection 149.202.49.98:32020 lastseen=85.5hrs
connect() failed after select(): No route to host
trying connection 37.150.102.118:32020 lastseen=9117.9hrs
ThreadRPCServer method=getinfo
accepted connection 93.84.202.72:12775
connection timeout
trying connection 130.105.214.98:32020 lastseen=16769.5hrs
ERROR: ConnectBlock() : UpdateTxIndex failed
InvalidChainFound: invalid block=00000000182f371ad623  height=1578287  trust=1952224469896987  date=04/15/18 13:05:54
InvalidChainFound:  current best=9786aec597be552b2174  height=1578286  trust=1952224469856370  date=04/15/18 12:47:25
ERROR: SetBestChain() : SetBestChainInner failed
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
connection timeout
trying connection 193.70.40.19:32020 lastseen=83.3hrs
connect() failed after select(): No route to host
trying connection 178.45.25.76:32020 lastseen=1301.8hrs
connection timeout
trying connection 201.1.199.194:32020 lastseen=1605.9hrs
ERROR: ConnectBlock() : UpdateTxIndex failed
InvalidChainFound: invalid block=0000000019ce0cf8e476  height=1578287  trust=1952224469896987  date=04/15/18 13:05:24
InvalidChainFound:  current best=9786aec597be552b2174  height=1578286  trust=1952224469856370  date=04/15/18 12:47:25
ERROR: SetBestChain() : SetBestChainInner failed
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
ThreadRPCServer method=submitblock
send version message: version 60016, blocks=1578286, us=xxxxxx:32020, them=93.84.202.72:12775, peer=93.84.202.72:12775
receive version message: version 60016, blocks=1578286, us=xxxxxx:32020, them=93.84.202.72:32020, peer=93.84.202.72:12775
ThreadRPCServer method=getpeerinfo
connection timeout
trying connection 62.216.203.50:32020 lastseen=11.0hrs
ERROR: ConnectBlock() : UpdateTxIndex failed
InvalidChainFound: invalid block=000000000a97c2dfa9f7  height=1578287  trust=1952224469896987  date=04/15/18 13:05:24
InvalidChainFound:  current best=9786aec597be552b2174  height=1578286  trust=1952224469856370  date=04/15/18 12:47:25
ERROR: SetBestChain() : SetBestChainInner failed
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED

Thanks for the info. I tried the chainworksindustries pool, but it seems that it's also not working at the moment.
Is there any chance for me foro solo mining too?

its been re-syncing for a few days now... the daemon wouldn't start anymore and was stuck at a tx not found in mempool

Zpool appears to be stuck. I apologize for that. I am confident it will be addressed at their earliest convenience.

Some are solo mining. Difficulty has been low enough to make that advantageous the past ~48 hours.   

http://ame-po01.chainworksindustries.com/bern/index.php   is still in a bit of testing, but is mining. The share difficulty is very high however, even on the low diff port (7201). Smaller hash rates will have a difficult time getting accepted shares.

Thanks for your interest and thanks in advance for mining!

I see in the Bern blockchain that mining is in progress. But that's not from Zpool.
Is there another pool where Bern can be mined?

A resolution to the stuck wallets / daemons continues to be investigated. I will do my best to keep the chain moving consistently until that resolution is found and released.

Thanks in advance for your understanding and continued patience.

#notMeUS

I only mentioned that because you indicated you had seemingly forked but then it was resolved. It sounded like reorg might have been the case. Sorry if I was mistaken.

Still eagerly awaiting the sync of the CWI pool while we investigate some registration problems.

Crackers was just now kindly asked to restart zpool's daemon via IRC. One way or another, we will get PoW blocks moving soon. Fortunately PoS blocks are keeping the chain going. Of course I am very curious if the CWI pool has the same issues or if the new and much better checkpoint server resolves the, seemingly connectivity / response time related, issue.

Rest assured, work continues. Thanks for the understanding.

#NotMeUS