aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJimmy Hu <jimmy.hu@dexon.org>2019-04-24 10:15:25 +0800
committerJimmy Hu <jimmy.hu@dexon.org>2019-04-24 10:15:25 +0800
commit66a42dae900bccbba12db3f035b44228db094be5 (patch)
treeabe2defdc6b30a262d9d39c9d368dfd3a70db5da
parent5d007d93c6a9115183c3ada02592b76331865a93 (diff)
downloaddexon-wiki-66a42dae900bccbba12db3f035b44228db094be5.tar.gz
dexon-wiki-66a42dae900bccbba12db3f035b44228db094be5.tar.zst
dexon-wiki-66a42dae900bccbba12db3f035b44228db094be5.zip
Created Recovery Mechanism (markdown)
-rw-r--r--Recovery-Mechanism.md3
1 files changed, 3 insertions, 0 deletions
diff --git a/Recovery-Mechanism.md b/Recovery-Mechanism.md
new file mode 100644
index 0000000..ffe9483
--- /dev/null
+++ b/Recovery-Mechanism.md
@@ -0,0 +1,3 @@
+DEXON's automatic recovery mechanism will kick in in the catastrophic event that complete DEXON Network shutdown to ensure DEXON can still reach consensus even without DEXON consensus algorithm.
+
+Nodes in the last notary set will vote on the external decentralized blockchain to determine which block height to be the point of recovery. Once a particular block height `h` has more than half of the notary set voted, the recovery consensus is reached. Block height of `h+1` will be an empty block and DEXON consensus algorithm will continue running at height `h+2`. \ No newline at end of file