____  ___    _  _     _   _ _____     _______
 / ___|/ _ \  | || |   | | | |_ _\ \   / / ____|
| |  _| | | | | || |_  | |_| || | \ \ / /|  _|
| |_| | |_| | |__   _| |  _  || |  \ V / | |___
 \____|\___/     |_|   |_| |_|___|  \_/  |_____|

 --- A GOPHER-LIKE INTERFACE FOR HIVE BLOCKCHAIN ---

BitShares entered unplanned maintenance mode

BY: @ash | CREATED: July 10, 2017, 9:58 a.m. | VOTES: 119 | PAYOUT: $138.79 | [ VOTE ]

around 1 hour ago BitShares network halted due to unknown reasons.

Witnesses and Developers are debugging at the moment and working on a fix

What does that mean for you

Will keep you updated

Update 10

network is operational.

Update 9 (UTC 17:25)

Roelandp:
participation rate at 22% witnesses rebuilding and running on a slowly rolling out network of seednodes.

Roelandp:
as per @dan: 'exchanges also need to update software'

Update 8 (17:18 UTC)

Ryan R. Fox (Fox):
The BitShares blockchian is currently bringing witnesses online at this time.

Update 7 (16:04 UTC)

@dan

> I have identified a fix that enabled my local node to produce blocks. Witnesses are testing the fix now.
https://github.com/bitshares/bitshares-core/pull/324/files

Update 6 (15:50 UTC)

Ryan R. Fox (Fox):
The BitShares blockchain remains halted. The root cause has been identified. The Core Development Team is coordinating a release at this time. Witnesses will be notified to update their nodes thereafter. Please expect another update in nearly 30 minutes.

Update 5 (15:05 UTC)

Ryan R. Fox (Fox):
The BitShares blockchain remains halted. The Core Development Team continues to actively identify the root cause. Witnesses are available to implement the resulting patch when it becomes available. Please expect another update in nearly 30 minutes.

Update 4

Ryan R. Fox (Fox):
The BitShares blockchain remains halted. Daniel Larimer is actively working with the BitShares Core development team to identify the root cause of the issue.

Update 3

Ryan R. Fox (Fox):
The BitShares network remains halted. The Core Developers are actively debugging. A re-sync is in progress to further their investigation. Expect another update in ~30 minutes.

Update 2

From Telegram:

> The BitShares blockchain is halted. No blocks are being produced. No transactions are being processed. This results in all blockchain data being protected as is. The Witnesses and developers are actively debugging the issue and working to restore the blockchain at this time. Please expect another update within the hour.

Update 1

join our Telegram to get live updates as they come in: https://t.me/BitSharesDEX

TAGS: [ #bitshares ] [ #maintenance ]

Replies

@idakwo1 | July 10, 2017, 9:59 a.m. | Votes: 0 | [ VOTE ]

Thanks for the information

@arckrai | July 10, 2017, 10 a.m. | Votes: 0 | [ VOTE ]

Thank you for the notice.
Luckily I wasn't planning to move around any BTS.

@ash | July 10, 2017, 10:04 a.m. | Votes: 0 | [ VOTE ]

it's not a big deal. your withdrawal would be cleared the second the network restarts

@rauzah | July 10, 2017, 10 a.m. | Votes: 2 | [ VOTE ]

good info please upvote me thank you

@joeyarnoldvn | July 10, 2017, 10 a.m. | Votes: 0 | [ VOTE ]

sad

@izbing | July 10, 2017, 10:02 a.m. | Votes: 0 | [ VOTE ]

Thank you for his information. I hope everything is going to be fine.

@traderr | July 10, 2017, 10:05 a.m. | Votes: 0 | [ VOTE ]

tank you for the information,greetings

@mountrock | July 10, 2017, 10:28 a.m. | Votes: 0 | [ VOTE ]

Thanks for posting

@peacekeeper | July 10, 2017, 10:42 a.m. | Votes: 0 | [ VOTE ]

hope this does not happen to EOS for an unknown reason....

@ash | July 10, 2017, 10:45 a.m. | Votes: 5 | [ VOTE ]

Update1: join our Telegram to get live updates as the come in: https://t.me/BitSharesDEX

@ash | July 10, 2017, 12:23 p.m. | Votes: 0 | [ VOTE ]

From Telegram:

> The BitShares blockchain is halted. No blocks are being produced. No transactions are being processed. This results in all blockchain data being protected as is. The Witnesses and developers are actively debugging the issue and working to restore the blockchain at this time. Please expect another update within the hour.

@ash | July 10, 2017, 1:33 p.m. | Votes: 0 | [ VOTE ]

Ryan R. Fox (Fox):
The BitShares network remains halted. The Core Developers are actively debugging. A re-sync is in progress to further their investigation. Expect another update in ~30 minutes.

@ash | July 10, 2017, 2:37 p.m. | Votes: 0 | [ VOTE ]

Ryan R. Fox (Fox):
The BitShares blockchain remains halted. Daniel Larimer is actively working with the BitShares Core development team to identify the root cause of the issue.

@ash | July 10, 2017, 2:42 p.m. | Votes: 1 | [ VOTE ]

> Witnesses are incapable of producing blocks b/c there is an issue that prevents verifying the previous chain - a particular transaction is fouling up the works. Dan Larimer and witnesses are working the problem as fast as possible.

@ash | July 10, 2017, 3:05 p.m. | Votes: 0 | [ VOTE ]

Update 5 (15:05 UTC)

Ryan R. Fox (Fox):
The BitShares blockchain remains halted. The Core Development Team continues to actively identify the root cause. Witnesses are available to implement the resulting patch when it becomes available. Please expect another update in nearly 30 minutes.

@ash | July 10, 2017, 3:51 p.m. | Votes: 0 | [ VOTE ]

Update 6 (15:50 UTC)

Ryan R. Fox (Fox):
The BitShares blockchain remains halted. The root cause has been identified. The Core Development Team is coordinating a release at this time. Witnesses will be notified to update their nodes thereafter. Please expect another update in nearly 30 minutes.

@ash | July 10, 2017, 5:18 p.m. | Votes: 2 | [ VOTE ]

Update 8 (17:18 UTC)

Ryan R. Fox (Fox):
The BitShares blockchian is currently bringing witnesses online at this time.

@ash | July 10, 2017, 5:25 p.m. | Votes: 1 | [ VOTE ]

Update 9 (UTC 17:25)

Roelandp:
participation rate at 22% witnesses rebuilding and running on a slowly rolling out network of seednodes.

Roelandp:
as per @daniellarimer: 'exchanges also need to update software'

@bagsk | July 10, 2017, 11:32 a.m. | Votes: 1 | [ VOTE ]

I hope for a quick recovery.

@magicstone1412 | July 10, 2017, 11:54 a.m. | Votes: 0 | [ VOTE ]

It is very strange. I can not access the telegram group. It says no username with this account

@ropaga | July 10, 2017, 12:08 p.m. | Votes: 0 | [ VOTE ]

It works for me.

@gnimeets | July 10, 2017, 12:05 p.m. | Votes: 1 | [ VOTE ]

Some serious BTS dumping was happening last night on Poloniex.

One must wonder about the timing of the dumps and just hours later an unplanned maintenance.

I presumed it was because the HERO was failing at first but maybe this is the cause?

@ash | July 10, 2017, 12:20 p.m. | Votes: 1 | [ VOTE ]

all altcoins are taking a hit right now, I doubt this has anything to do with it.

there will be an investigation/report afterwards

@gnimeets | July 10, 2017, 12:24 p.m. | Votes: 0 | [ VOTE ]

True hope thing's get sorted quickly.
Just a little speed bump in the road!

@cryptographic | July 11, 2017, 3:40 p.m. | Votes: 1 | [ VOTE ]

Please let us know when you see that. It will be important to do our best to get it out there once we have it . . . if only to project a professional image. 😉

@cm-steem | July 10, 2017, 5:23 p.m. | Votes: 0 | [ VOTE ]

HERO isn't failing, perhaps the liquidity isn't great but if you hold HERO tokens they are secure and gaining value each year as designed, regardless of todays network issues.

@gnimeets | July 10, 2017, 5:57 p.m. | Votes: 0 | [ VOTE ]

Oh that is not why I assumed so at all. It was just the timing of the dumps in relation to the HERO news today so I presumed it was not well received.

@arcaneinfo | July 10, 2017, 1:19 p.m. | Votes: 0 | [ VOTE ]

TY! Couldn't login:)

@lukestokes | July 10, 2017, 2:24 p.m. | Votes: 8 | [ VOTE ]

Geez. This is not good at all. Having an entire decentralized blockchain halt all at once, effectively locking everyone out of their wallets and their stores of value ... that't not supposed to be able to happen. Is there a flaw in DPOS? Was it a specific error or attack? How BitShares recovers from this is going to impact its future in important ways. Might also impact Steem, Peerplays, and EOS.

Thanks for keeping us informed. Resteeming.

@ash | July 10, 2017, 2:37 p.m. | Votes: 3 | [ VOTE ]

steem was down a lot in the past, it's not a big deal. unlike centralized exchanges, nothing can happen to your money on a blockchain.

@lukestokes | July 10, 2017, 2:44 p.m. | Votes: 0 | [ VOTE ]

That must have happened over a year ago, prior to when I was here. It's just surprising to me since BitShares has been running for a long time. I'll be very interested to see how this all shakes out. I agree with what I'm seeing in Telegram: software always has bugs. What matters his how those involved recover from them.

@peacekeeper | July 10, 2017, 4:27 p.m. | Votes: 0 | [ VOTE ]

This is definitely not good. I was to understand the blockchain had resources to avoid this from happening. Witnesses and all.... Research time....

@alexpmorris | July 10, 2017, 4:50 p.m. | Votes: 2 | [ VOTE ]

they'll fix it and move on, and that'll likely be the end of it. stuff like this happens all the time, even on exchanges like CME, NYSE, etc. sh!t happens, and if this "scares" anyone out of their bitshares holdings, I'd be happy to buy 'em all up from them, real cheap of course! :D

what I'm actually more concerned about is the "glitch" we uncovered yesterday, which I hope to post about later today...

@cm-steem | July 10, 2017, 5:22 p.m. | Votes: 0 | [ VOTE ]

Halting isn't as bad as forking, if it's just a matter of a large transaction backlog when going back online there's nothing to be concerned about.

@johnsmith | July 10, 2017, 3:20 p.m. | Votes: 1 | [ VOTE ]

Dan is now working with the Bitshares core devs to resolve.

@dan | July 10, 2017, 3:22 p.m. | Votes: 26 | [ VOTE ]

All software has potential for undiscovered bugs even after years of stable use. This is not a consensus failure because all nodes stopped at once and there are no forks. All nodes "agree" on the bug.

Once the bug is fixed all nodes will resume.

@rangertx | July 10, 2017, 3:41 p.m. | Votes: 1 | [ VOTE ]

Thanks for clarifying. I think everyone panics when they don't know what's going on. Easy to imagine the worst.

@johnsmith | July 10, 2017, 3:50 p.m. | Votes: 8 | [ VOTE ]

It is worth noting this is the first glitch in over two years of operations - during much which BTS was processing more daily tx than BTC. It is much better to find and resolve these issues now when BTS/STEEM/EOS are in their infancy than a few years down the road when they have become global financial titans.

@intelliguy | July 10, 2017, 4:04 p.m. | Votes: 7 | [ VOTE ]

If you've ever seen a bank machine ATM say "Sorry, currently unavailable. Or not in service" in your entire life. You'll understand this happens rarely, but it does happen. Anything that runs on software needs to be tweaked, upgraded, and maintained from time to time.

My level of worry from 0% to 100% is exactly 0%

@kingscrown | July 10, 2017, 6:32 p.m. | Votes: 2 | [ VOTE ]

is this bug affecting (possibly) other graphene coins? ie should STEEM add this?

@cptnsolo | July 10, 2017, 3:41 p.m. | Votes: 0 | [ VOTE ]

what about margin calls after blockchain relaunch? will there be some delay to make it possible to increase collateral, etc. ?

@btcmillionaire | July 10, 2017, 3:46 p.m. | Votes: 1 | [ VOTE ]

Wonder if this is related to Steem crashing in price too?!

@fractalnode | July 10, 2017, 4:29 p.m. | Votes: 0 | [ VOTE ]

I don't think so
[IMAGE: https://steemitimages.com/DQmPDfqUwqScmYzvxD7e2iyBT41SqW348rRuMnNPsqNg8gE/image.png]

@dan | July 10, 2017, 3:56 p.m. | Votes: 30 | [ VOTE ]

I have identified a fix that enabled my local node to produce blocks. Witnesses are testing the fix now.

https://github.com/bitshares/bitshares-core/pull/324/files

@ash | July 10, 2017, 3:59 p.m. | Votes: 10 | [ VOTE ]

[IMAGE: http://i.imgur.com/ABuYms4.png]

@johnsmith | July 10, 2017, 4:25 p.m. | Votes: 2 | [ VOTE ]

dantheman

@vitaly-lvov | July 10, 2017, 6:41 p.m. | Votes: 1 | [ VOTE ]

superman :)

@karensuestudios | July 10, 2017, 4:33 p.m. | Votes: 1 | [ VOTE ]

thanks for all that you do! Rockin it.

@cm-steem | July 10, 2017, 5:20 p.m. | Votes: 3 | [ VOTE ]

Legend! :D

@clayop | July 10, 2017, 6:37 p.m. | Votes: 0 | [ VOTE ]

delegate-clayop is fixed now and is generating blocks

@johnsmith | July 10, 2017, 6:45 p.m. | Votes: 2 | [ VOTE ]

Aaaand we're back and this why BTS is the best crypto on the planet.

@kauslevi | July 10, 2017, 6:46 p.m. | Votes: 1 | [ VOTE ]

I am still receiving an error.

@kauslevi | July 10, 2017, 6:48 p.m. | Votes: 0 | [ VOTE ]

Scratch that. It is operational now.

@space-pirate | July 10, 2017, 7:08 p.m. | Votes: 0 | [ VOTE ]

I am still getting the "failed to sync" error. Do you have anymore information beyond "network is operational"? Do I need to select a different API server?

@ash | July 10, 2017, 7:20 p.m. | Votes: 0 | [ VOTE ]

try transwiser or openledger

@arcaneinfo | July 10, 2017, 8:50 p.m. | Votes: 0 | [ VOTE ]

None of the online sync are working? Can I use my same wallet to open my account on downloaded version? bitshares.org not functioning.

@ash | July 10, 2017, 9:58 p.m. | Votes: 0 | [ VOTE ]

Transwiser and OpenLedger api nodes are working

@kyawsantun | July 12, 2017, 4:48 p.m. | Votes: 0 | [ VOTE ]

It still having errors

@ash | July 12, 2017, 5:36 p.m. | Votes: 0 | [ VOTE ]

it's working fine. try another API node

@jlcrypto | Oct. 5, 2017, 7:11 a.m. | Votes: 0 | [ VOTE ]

Hi Ash

I'm in New Zealand and I can't connect to the bitshare light wallet and even the web wallet. I have Failed Sync API server coming everytime. I tried all servers and changing my clock to match with each of them but nothing happen. I hold a lot of BTC on bittrex and don' want to be forced to sell because this issue ... Thanks

[ BACK TO TRENDING ] [ BACK TO MENU ]
CMD>