aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorcheshirecatnick <cheshirecatnick@gmail.com>2018-08-29 10:54:31 +0800
committercheshirecatnick <cheshirecatnick@gmail.com>2018-08-29 10:54:31 +0800
commitb9b74a092723939d46575468dc6db3a661e5044d (patch)
tree7f74777a1f58820e605eb09b012c1d7f1ef2f25e
parent74ed26988adf51bc8cdf9a29caff81d344495f5c (diff)
downloaddexon-wiki-b9b74a092723939d46575468dc6db3a661e5044d.tar
dexon-wiki-b9b74a092723939d46575468dc6db3a661e5044d.tar.gz
dexon-wiki-b9b74a092723939d46575468dc6db3a661e5044d.tar.bz2
dexon-wiki-b9b74a092723939d46575468dc6db3a661e5044d.tar.lz
dexon-wiki-b9b74a092723939d46575468dc6db3a661e5044d.tar.xz
dexon-wiki-b9b74a092723939d46575468dc6db3a661e5044d.tar.zst
dexon-wiki-b9b74a092723939d46575468dc6db3a661e5044d.zip
fix links
-rw-r--r--Home.md36
1 files changed, 18 insertions, 18 deletions
diff --git a/Home.md b/Home.md
index 91f4e84..5ddaf2e 100644
--- a/Home.md
+++ b/Home.md
@@ -15,23 +15,23 @@ This document explains how DEXON is different compared to other blockchain infra
- <img src="https://latex.codecogs.com/svg.latex?f" />: ack frequency
### Contents
-- [DEXON](#DEXON)
-- [Algorand](#Algorand)
-- [Bitcoin](#Bitcoin)
-- [Cardano](#Cardano)
-- [Dfinity](#Dfinity)
-- [EOS](#EOS)
-- [Ethereum](#Ethereum)
-- [Hashgraph](#Hashgraph)
-- [Hyperledger](#Hyperledger)
-- [IOTA](#IOTA)
-- [NANO](#NANO)
-- [Omniledger](#Omniledger)
-- [Phantom](#Phantom)
-- [Snowflake](#Snowflake)
-- [Spectre](#Spectre)
-- [Stellar](#Stellar)
-- [Tendermint](#Tendermint)
+- [DEXON](#dexon)
+- [Algorand](#algorand)
+- [Bitcoin](#bitcoin)
+- [Cardano](#cardano)
+- [Dfinity](#dfinity)
+- [EOS](#eos)
+- [Ethereum](#ethereum)
+- [Hashgraph](#hashgraph)
+- [Hyperledger](#hyperledger)
+- [IOTA](#iota)
+- [NANO](#nano)
+- [Omniledger](#omniledger)
+- [Phantom](#phantom)
+- [Snowflake](#snowflake)
+- [Spectre](#spectre)
+- [Stellar](#stellar)
+- [Tendermint](#tendermint)
## DEXON
|Throughput (TPS)|Latency (seconds)|Data Structure|Consensus|Smart Contract|
@@ -157,7 +157,7 @@ To resolve conflict transactions, nodes need to execute Avalanche algorithm on e
|-|-|-|-|-|
|NA|1 ~ 10|DAG-blocklattice|block voting algorithm|X|
-Spectre is a DAG-based digital ledger system that uses recursive block voting to decide which conflict block should be finalized. This consensus algorithm allows participants to propose block arbitrarily fast, which means its scalability and latency is bounded by the network. However, its lack of total ordering of blocks makes it impossible to execute smart contract. That is the reason why they propose "Phantom", a consensus that is also DAG-based but with total ordering properties. We also [compare](#Phantom) DEXON to Phantom.
+Spectre is a DAG-based digital ledger system that uses recursive block voting to decide which conflict block should be finalized. This consensus algorithm allows participants to propose block arbitrarily fast, which means its scalability and latency is bounded by the network. However, its lack of total ordering of blocks makes it impossible to execute smart contract. That is the reason why they propose "Phantom", a consensus that is also DAG-based but with total ordering properties. We also [compare](#phantom) DEXON to Phantom.
## Stellar
|Throughput (TPS)|Latency (seconds)|Data Structure|Consensus|Smart Contract|