針對昨日EOS 的宕機和重啟,如果想知道細節,可以參考以下EOS NewYork (EOS紐約社區)的記錄,
英文/中文/韓文 三種語言,EOS NewYork非常的nice
-----------------------------------
我個人的理解:
1. EOS才出生,有一些bug在所難免
2. EOS的社區共識很強大,遇到問題第一時間就全球召集BP會議討論問題并達成共識!
3. Block.one支持給力,BM第一時間加入問題解決
4. 全程信息公開,開源的力量和價值體現,未來會吸引更多的人才討論,只會更強大
5. EOS的機制設計很好,底層安全大家放心(BTS/Steemit跑了這么久,自己要有信心!):
EOSIO軟件設置了這樣一種機制,當這類錯誤出現時,主網將停止運轉從而避免硬分叉。一旦超級節點們共同發現一個故障,所有的超級節點都將停止。修復版代碼已經完成并正在進行測試,并且將會被所有超級節點同步
6、EOS的很多創新功能,需要時間去檢驗,創新者必須勇敢面對未知世界!
7、遇到問題,面對問題,解決問題!
8、我們有:
這么強大的社區!
這么有共識基礎的BP Teams!
這么強大的技術團隊!
這么高的關注度!
給EOS一點時間,給整個EOS生態一點時間!
勇敢面對未知世界!
我們并不追求“立刻完美”,但在“讓明天變得更好的路上”,砥礪前行!
-----------------------------------
為什么會寫這點東西?
1. 昨晚"打死不賣EOS 4群"里有很多人關心宕機問題,但不知道細節;其實國外社區很多討論,只是大家因為語言不通,難以直接交流。如果知道了整個過程,你會更堅定持有EOS;
2. 正好EOS NewYork發布了整個細節,我也就傳遞下信息
3. 我買EOS的目的是為了向女兒(現6歲)長大后顯擺用:你爸也參與過一個“改變世界的大事”!不管成不成,整個歷程我會記錄下來,這怎么也將是一份教程。
4. 2018.6.17 父親節,加倉了一部分湊個整數,封箱窖藏!什么時候開封?等環球旅行時機成熟,用這筆錢!
5. 特殊的日子,寫點東西做個標記!如果能讓大家對EOS更有信心些,也算是隊長對EOS的一點的貢獻
I'm a EOSer!
感激EOS!
感激all EOSers!
-- 成都隊長@2018.6.17 morning in CHENGDU.
=================================================
EOS Mainnet Status?Update
EOS主網的更新(含6.16宕機和重啟細節)
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主網區塊鏈的21個超級節點和全體備用節點。
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主網于UTC時間9:56凍結。超級節點和許多備用節點于UTC時間10:01緊急召開了國際會議來定位和解決問題。
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時間10:57做出決定,所有備用節點將停止節點,并且支持一切對診斷這一問題有幫助的信息。
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時間11:02,節點們制定了一個方案來重啟EOS主網,并且目前已經在緊密施行過程中。EOS主網預計將于本聲明發布之時起3到6個小時后恢復正常。在EOS主網恢復正常之前,接入主網的所有請求將被拒絕。在EOS主網上進行交易前請耐心等待21個主節點的更新通知。
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時間13:03?—?— 更新#1:我們已經明確這一問題的根本原因,并且正在著手解決。一旦我們完成這一解決工作,將完全公布這一根本原因。
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時間13:09?—?— 更新#2:BlockOne 正在1.0.5標簽中發布一個補丁,這將在未來的幾小時內同步。以下是將要采取的步驟:
13:09 UTC?—?update#2: ???? ? ?? ?? 1.0.5 ??? ? ??? ?????. ??? ?? ???? ??? ????:
________________________________________
A nodeos fix will be released.
發布修復版nodeos代碼。
nodeos ????? ?? ???.
The block producer nodes will be upgraded.
出塊節點將會進行更新。
?? ???? ???? ?????? ?????.
Block producers which had locally produced blocks will need to resync up until block 1027926, with production paused, and enable-stale-production disabled.
過去已經出塊的節點們將需要重新同步至11027926這一區塊,同時停止出塊,并且停止enable-stale-production。
??? ??? ??? ?? ????? ??? 1027926?? ?????? ??, ?? ??? ?? ???? enable-stale-production? ????? ?????.
All nodes will upgrade to 1.0.5
所有的節點將會更新到1.0.5
?? ???? ?? 1.0.5? ?????? ?????.
Block producers will sync to each other to resume production
超級節點們將會互相同步到第1027926塊并恢復出塊
?? ?????? ?? ??? ???? ?? ??? ??? ?????.
Chain will be opened up for public access.
EOS主網將會面向公眾開放。
??? ? ??? ????.
________________________________________
At 13:28 UTC The root cause was due to an issue with how deferred transactions were handled.
UTC時間13:28?—?— 更新#3:產生本次情況的根源在于一個處理交易延遲的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時間13:36?—?— 更新#4:Pull Request 4158:http://github.com/EOSIO/eos/pull/4158
EOSIO軟件設置了這樣一種機制,當這類錯誤出現時,主網將停止運轉從而避免硬分叉。一旦超級節點們共同發現一個故障,所有的超級節點都將停止。修復版代碼已經完成并正在進行測試,并且將會被所有超級節點同步。
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時間14:13- 更新#5:Block.One 發布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時間14:48?—?— 主網恢復。參與這一修復版代碼的超級節點和備用節點與Block.One一起在5小時內明確問題,完成修復版代碼。
14:48 UTC?—?????? ?? ??? ?????. ?? ??? ?? ???? ? ??? ?? ??? ?? ????? ?? ?? ????? ???? ?? ??? ???? 5?? ?? ?? ??? ???? ??? ? ?????.