looks like your bitbar may be on a (soft) fork.
can't seem to match your latest block hash with what i got (i have 8 connections.)
seems block 257849 is where things diverge
i noticed this because i didnt receive the payout you made to me this morning
also, not sure if you are updated to the latest bitbar wallet release from this last fall (v0.7.5.1)
explorer prohashing.com/explorer/Bitbar/
Forum rules
Welcome to the System Support forum! Encounter a problem related to the pool? Post your issue here and we will help you out.
Keep in mind that the forums are monitored by PROHASHING less closely than the official support channels, so if you have a pressing issue, please submit an official support ticket so that our Support Analyst can look into your issue in a timely manner.
We cannot answer financial questions related to your account on a public forum, so those questions should always be submitted through the orange Support button on prohashing.com/about.
For the full list of PROHASHING forums rules, please visit https://prohashing.com/help/prohashing- ... rms-forums.
Welcome to the System Support forum! Encounter a problem related to the pool? Post your issue here and we will help you out.
Keep in mind that the forums are monitored by PROHASHING less closely than the official support channels, so if you have a pressing issue, please submit an official support ticket so that our Support Analyst can look into your issue in a timely manner.
We cannot answer financial questions related to your account on a public forum, so those questions should always be submitted through the orange Support button on prohashing.com/about.
For the full list of PROHASHING forums rules, please visit https://prohashing.com/help/prohashing- ... rms-forums.
- Steve Sokolowski
- Posts: 4585
- Joined: Wed Aug 27, 2014 3:27 pm
- Location: State College, PA
Re: explorer prohashing.com/explorer/Bitbar/
Please submit a ticket to Chris about this problem.
If it is true that this daemon forked, we can't upgrade to the latest fork until we have a solution to the Meltdown vulnerability. Chris is working on that and hopes to have more information soon.
If it is true that this daemon forked, we can't upgrade to the latest fork until we have a solution to the Meltdown vulnerability. Chris is working on that and hopes to have more information soon.