針對(duì)昨日EOS 的宕機(jī)和重啟江掩，如果想知道細(xì)節(jié)镊掖，可以參考以下EOS NewYork (EOS紐約社區(qū))的記錄丘喻，
英文/中文/韓文 三種語言诵竭，EOS NewYork非常的nice
-----------------------------------
我個(gè)人的理解：
1. EOS才出生话告，有一些bug在所難免
2. EOS的社區(qū)共識(shí)很強(qiáng)大，遇到問題第一時(shí)間就全球召集BP會(huì)議討論問題并達(dá)成共識(shí)卵慰！
3. Block.one支持給力沙郭，BM第一時(shí)間加入問題解決
4. 全程信息公開，開源的力量和價(jià)值體現(xiàn)裳朋，未來會(huì)吸引更多的人才討論病线，只會(huì)更強(qiáng)大
5. EOS的機(jī)制設(shè)計(jì)很好，底層安全大家放心(BTS/Steemit跑了這么久鲤嫡，自己要有信心送挑！)：
EOSIO軟件設(shè)置了這樣一種機(jī)制，當(dāng)這類錯(cuò)誤出現(xiàn)時(shí)暖眼，主網(wǎng)將停止運(yùn)轉(zhuǎn)從而避免硬分叉惕耕。一旦超級(jí)節(jié)點(diǎn)們共同發(fā)現(xiàn)一個(gè)故障，所有的超級(jí)節(jié)點(diǎn)都將停止罢荡。修復(fù)版代碼已經(jīng)完成并正在進(jìn)行測(cè)試赡突，并且將會(huì)被所有超級(jí)節(jié)點(diǎn)同步
6对扶、EOS的很多創(chuàng)新功能，需要時(shí)間去檢驗(yàn)惭缰，創(chuàng)新者必須勇敢面對(duì)未知世界浪南！
7、遇到問題漱受，面對(duì)問題络凿，解決問題！
8昂羡、我們有：
這么強(qiáng)大的社區(qū)絮记！
這么有共識(shí)基礎(chǔ)的BP Teams!
這么強(qiáng)大的技術(shù)團(tuán)隊(duì)！
這么高的關(guān)注度虐先！
給EOS一點(diǎn)時(shí)間怨愤，給整個(gè)EOS生態(tài)一點(diǎn)時(shí)間！
勇敢面對(duì)未知世界蛹批！
我們并不追求“立刻完美”撰洗，但在“讓明天變得更好的路上”，砥礪前行腐芍！
-----------------------------------
為什么會(huì)寫這點(diǎn)東西差导？
1. 昨晚"打死不賣EOS 4群"里有很多人關(guān)心宕機(jī)問題，但不知道細(xì)節(jié);其實(shí)國外社區(qū)很多討論猪勇，只是大家因?yàn)檎Z言不通设褐，難以直接交流。如果知道了整個(gè)過程泣刹，你會(huì)更堅(jiān)定持有EOS助析；
2. 正好EOS NewYork發(fā)布了整個(gè)細(xì)節(jié)，我也就傳遞下信息
3. 我買EOS的目的是為了向女兒(現(xiàn)6歲)長大后顯擺用：你爸也參與過一個(gè)“改變世界的大事”项玛！不管成不成貌笨，整個(gè)歷程我會(huì)記錄下來，這怎么也將是一份教程襟沮。
4. 2018.6.17 父親節(jié)，加倉了一部分湊個(gè)整數(shù)昌腰，封箱窖藏开伏！什么時(shí)候開封？等環(huán)球旅行時(shí)機(jī)成熟遭商，用這筆錢！
5. 特殊的日子，寫點(diǎn)東西做個(gè)標(biāo)記溜畅！如果能讓大家對(duì)EOS更有信心些，也算是隊(duì)長對(duì)EOS的一點(diǎn)的貢獻(xiàn)
I'm a EOSer!
感激EOS丛忆！
感激all EOSers！
-- 成都隊(duì)長@2018.6.17 morning in CHENGDU.
=================================================
EOS Mainnet Status?Update
EOS主網(wǎng)的更新(含6.16宕機(jī)和重啟細(xì)節(jié))
This message is from the Top 21 Block Producers and Standby Nodes of the EOS Mainnet Blockchain. This update has been translated into Korean and Chinese. Line breaks indicate a new paragraph or section.
這一信息來自EOS主網(wǎng)區(qū)塊鏈的21個(gè)超級(jí)節(jié)點(diǎn)和全體備用節(jié)點(diǎn)仍秤。
EOS ??? ????? ?? 21? ?? ????? ?? ?? ????? ?? ?? ??????.
________________________________________
AT 9:56 UTC the EOS Mainnet halted. At 10:01 UTC Block Producers and many Standby Nodes joined together on an international conference call to identify and fix the issue.
EOS主網(wǎng)于UTC時(shí)間9:56凍結(jié)熄诡。超級(jí)節(jié)點(diǎn)和許多備用節(jié)點(diǎn)于UTC時(shí)間10:01緊急召開了國際會(huì)議來定位和解決問題。
UTC 9:56? EOS ???? ???????. UTC 10:01? ?? ?????? ?? ?? ?? ?????? ?? ??? ? ??? ???? ???? ??? ???? ???? ?? ?????.
________________________________________
At 10:57 UTC The choice was made that all Standby Block Producers would stop their nodes and backup any information that could helpful in diagnosing the problem.
UTC時(shí)間10:57做出決定诗力，所有備用節(jié)點(diǎn)將停止節(jié)點(diǎn)凰浮，并且支持一切對(duì)診斷這一問題有幫助的信息。
UTC 10:57? ?? ?? ?? ?????? ??? ??? ???? ????? ??? ? ?? ?? ??? ????? ???????.
________________________________________
At 11:02 UTC, a method to unpause the chain was formulated and is currently underway. Normal EOS chain functions should be available within 3 to 6 hours from the time of the publication. Incoming connections to the network are not being accepted while the work is taking place. Please wait for an update from the Top 21 Block Producers before attempting EOS mainnet transactions.
UTC時(shí)間11:02苇本，節(jié)點(diǎn)們制定了一個(gè)方案來重啟EOS主網(wǎng)袜茧，并且目前已經(jīng)在緊密施行過程中。EOS主網(wǎng)預(yù)計(jì)將于本聲明發(fā)布之時(shí)起3到6個(gè)小時(shí)后恢復(fù)正常瓣窄。在EOS主網(wǎng)恢復(fù)正常之前笛厦，接入主網(wǎng)的所有請(qǐng)求將被拒絕。在EOS主網(wǎng)上進(jìn)行交易前請(qǐng)耐心等待21個(gè)主節(jié)點(diǎn)的更新通知俺夕。
UTC 11:02? ??? ?? ???? ???? ??? ????? ?? ?? ????. ???? EOS ?? ??? ? ??? ??? ???? 3~ 6?? ??? ??? ?????. ?????? ??? ??? ???? ???? ?? ???? ????. EOS ??? ????? ????? ?? Top 21? ?? ??????? ????? ??? ??????.
________________________________________
At 13:03 UTC we identified the root cause and are working on a fix. A full release outlining the root cause will be issued once we’ve completed the work.
UTC時(shí)間13:03?—?— 更新#1：我們已經(jīng)明確這一問題的根本原因裳凸，并且正在著手解決。一旦我們完成這一解決工作啥么，將完全公布這一根本原因登舞。
13:03 UTC?—?Update#1: ??? ??? ??? ????? ??? ?? ???? ????. ?? ??? ???? ?? ??? ??? ??? ? ??? ????.
________________________________________
At 13:09 UTC BlockOne is issuing a patch in tag 1.0.5 which will be rolling out in the next few hours. The following steps will be taken:
UTC時(shí)間13：09?—?— 更新#2：BlockOne 正在1.0.5標(biāo)簽中發(fā)布一個(gè)補(bǔ)丁，這將在未來的幾小時(shí)內(nèi)同步悬荣。以下是將要采取的步驟：
13:09 UTC?—?update#2: ???? ? ?? ?? 1.0.5 ??? ? ??? ?????. ??? ?? ???? ??? ????:
________________________________________
A nodeos fix will be released.
發(fā)布修復(fù)版nodeos代碼菠秒。
nodeos ????? ?? ???.
The block producer nodes will be upgraded.
出塊節(jié)點(diǎn)將會(huì)進(jìn)行更新。
?? ???? ???? ?????? ?????.
Block producers which had locally produced blocks will need to resync up until block 1027926, with production paused, and enable-stale-production disabled.
過去已經(jīng)出塊的節(jié)點(diǎn)們將需要重新同步至11027926這一區(qū)塊氯迂，同時(shí)停止出塊践叠，并且停止enable-stale-production。
??? ??? ??? ?? ????? ??? 1027926?? ?????? ??, ?? ??? ?? ???? enable-stale-production? ????? ?????.
All nodes will upgrade to 1.0.5
所有的節(jié)點(diǎn)將會(huì)更新到1.0.5
?? ???? ?? 1.0.5? ?????? ?????.
Block producers will sync to each other to resume production
超級(jí)節(jié)點(diǎn)們將會(huì)互相同步到第1027926塊并恢復(fù)出塊
?? ?????? ?? ??? ???? ?? ??? ??? ?????.
Chain will be opened up for public access.
EOS主網(wǎng)將會(huì)面向公眾開放嚼蚀。
??? ? ??? ????.
________________________________________
At 13:28 UTC The root cause was due to an issue with how deferred transactions were handled.
UTC時(shí)間13:28?—?— 更新#3：產(chǎn)生本次情況的根源在于一個(gè)處理交易延遲的issue禁灼。
13:28 UTC?—?Update #3: ??? ???? ??? ?? ????(deferred transactions)? ???? ??? ??? ???????.
________________________________________
At 13:36 UTC Pull Request 4158:?https://github.com/EOSIO/eos/pull/4158
The EOSIO software is designed in such a way that when an error of this type occurs the chain will pause to prevent a hard fork. All block producers were halted when they detected a break in consensus. A fix was written, and is being tested and will be rolled out by the block producers community.
UTC時(shí)間13:36?—?— 更新#4：Pull Request 4158:http://github.com/EOSIO/eos/pull/4158
EOSIO軟件設(shè)置了這樣一種機(jī)制，當(dāng)這類錯(cuò)誤出現(xiàn)時(shí)轿曙，主網(wǎng)將停止運(yùn)轉(zhuǎn)從而避免硬分叉弄捕。一旦超級(jí)節(jié)點(diǎn)們共同發(fā)現(xiàn)一個(gè)故障，所有的超級(jí)節(jié)點(diǎn)都將停止导帝。修復(fù)版代碼已經(jīng)完成并正在進(jìn)行測(cè)試守谓，并且將會(huì)被所有超級(jí)節(jié)點(diǎn)同步。
13:36 UTC?—?Update #4: Pull Request 4158:?https://github.com/EOSIO/eos/pull/4158
EOSIO ?????? ?? ??? ??? ????? ????? ?? ????(hard fork)? ?? ? ? ??? ???? ????. ?? ?? ?????? ??? ??? ???? ?? ??? ????. ?? ??? ?????, ?? ???? ????? ??? ????? ??? ?? ????? ??? ????.
________________________________________
At 14:13 UTC Tag 1.0.5 was issued by Block.One:?https://github.com/EOS-Mainnet/eos/tree/mainnet-1.0.5
UTC時(shí)間14:13- 更新#5：Block.One 發(fā)布1.0.5您单。
14:13 UTC?—?Update #5: ?? 1.0.5? ???? ?? ???????.?https://github.com/EOS-Mainnet/eos/tree/mainnet-1.0.5
_______________________________________
At 14:48 UTC the network went live. The Block Producers and Standby Nodes responsible for responding to this fix were able to work with Block.One, identify the issue, and merge a fix within 5 hours time.
UTC時(shí)間14:48?—?— 主網(wǎng)恢復(fù)斋荞。參與這一修復(fù)版代碼的超級(jí)節(jié)點(diǎn)和備用節(jié)點(diǎn)與Block.One一起在5小時(shí)內(nèi)明確問題，完成修復(fù)版代碼虐秦。
14:48 UTC?—?????? ?? ??? ?????. ?? ??? ?? ???? ? ??? ?? ??? ?? ????? ?? ?? ????? ???? ?? ??? ???? 5?? ?? ?? ??? ???? ??? ? ?????.
