2016
DOI: 10.48550/arxiv.1612.02916
|View full text |Cite
Preprint
|
Sign up to set email alerts
|

Solida: A Blockchain Protocol Based on Reconfigurable Byzantine Consensus

Abstract: The decentralized cryptocurrency Bitcoin has experienced great success but also encountered many challenges. One of the challenges has been the long confirmation time. Another challenge is the lack of incentives at certain steps of the protocol, raising concerns for transaction withholding, selfish mining, etc. To address these challenges, we propose Solida, a decentralized blockchain protocol based on reconfigurable Byzantine consensus augmented by proof-of-work. Solida improves on Bitcoin in confirmation tim… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
16
0

Year Published

2018
2018
2022
2022

Publication Types

Select...
4
1
1

Relationship

0
6

Authors

Journals

citations
Cited by 9 publications
(16 citation statements)
references
References 13 publications
(28 reference statements)
0
16
0
Order By: Relevance
“…Another approach to improving blockchain-based money transfer protocols is to replace Nakamoto consensus with a more classical Byzantine fault tolerant consensus protocol such as PBFT [9]. These protocols [3,25] typically offer more classical safety and liveness guarantees than Nakamoto consensus, such as transaction finality. However, they still adopt the fault tolerance model that up to < 3 of agents may be Byzantine and that the rest are correct.…”
Section: Related Workmentioning
confidence: 99%
“…Another approach to improving blockchain-based money transfer protocols is to replace Nakamoto consensus with a more classical Byzantine fault tolerant consensus protocol such as PBFT [9]. These protocols [3,25] typically offer more classical safety and liveness guarantees than Nakamoto consensus, such as transaction finality. However, they still adopt the fault tolerance model that up to < 3 of agents may be Byzantine and that the rest are correct.…”
Section: Related Workmentioning
confidence: 99%
“…that The nodes have to know the latest blocks to avoid forks (the same as BFT assumption) but do not set an upper bound of message delivery time (partial synchronous network assumption). The solutions include the dBFT of NEO, the BFT of Mir-BFT [35], the BFT of Hotstuff [36], the PoS+PBFT of Tendermint [37] [38], the vote-based BFT of Algorand [39], the Raft+PBFT of Tangaroa [40], the variant PBFT of Thunderella [41], PeerConsensus [42], ByzCoin [43], and Solida [44]. Several systems [45] even directly weaken the safety assumption of BFT consensus, by modifying a strictly ordered sequence into a partially ordered sequence.…”
Section: Q3how To Mitigate the Issue?mentioning
confidence: 99%
“…These parameters encapsulate the effects of both fundamental network properties (e.g., hardware, topology), as well as resources consumed by the network's relaying mechanism, such as validity checking of transactions or blocks. 1 Assuming that each transaction needs to be communicated at least once across the network, it holds that λ, the number of transactions which can be confirmed per second, is at most C, i.e. λ < C.…”
Section: Physical Limitsmentioning
confidence: 99%
“…At the same time, Prism achieves a confirmation latency for honest transactions matching the two physical limits (2) and (3). In particular, if the desired security parameter log 1 ε ≪ CD/B v , the confirmation latency is of the order of the propagation delay and independent of log 1/ε. Put another way, one can achieve latency close to the propagation delay with a confirmation error probability exponentially small in the bandwidth-delay product CD/B v .…”
Section: 𝑂(𝐷)mentioning
confidence: 99%
See 1 more Smart Citation