Skip to content

Commit 15d522e

Browse files
committed
Add draft
1 parent 6e0dea8 commit 15d522e

2 files changed

Lines changed: 80 additions & 0 deletions

File tree

Lines changed: 38 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,38 @@
1+
# 区块链共识级别的攻击
2+
3+
## Double spending attacks
4+
5+
## Grinding attacks
6+
7+
## Transaction denial attacks
8+
9+
## Desynchronization attacks
10+
11+
## Eclipse attacks
12+
13+
## 51% attacks
14+
15+
## Bribery attacks
16+
17+
## Long-range attacks
18+
19+
## Nothing at stake attacks
20+
21+
当发生分叉时,验证人的最优策略是承认每一条分叉,并在所有分叉上继续挖。
22+
23+
- https://en.wikipedia.org/wiki/Proof-of-stake
24+
- https://blog.goldmint.io/nothing-at-stake-and-longrange-attack-in-pos-4ec486f1fc89
25+
- https://github.com/ethereum/wiki/wiki/Problems
26+
- https://pivx.org/nothing-considered-a-look-at-nothing-at-stake-vulnerability-for-cryptocurrencies/
27+
- https://medium.com/@abhisharm/understanding-proof-of-stake-through-its-flaws-part-2-nothing-s-at-stake-8d12d826956c
28+
- https://medium.com/coinmonks/understanding-proof-of-stake-the-nothing-at-stake-theory-1f0d71bc027
29+
30+
## Past majority attacks
31+
32+
## Selfish-mining
33+
34+
自私挖矿,恶意挖到块以后,并不广播出去,而是偷偷藏在手里,然后继续挖。当监听到有节点挖出同样高度的块时,迅速将手里的块广播出去,如果恶意节点的网络更好, 那么恶意节点手中同高度的块就会被接受,如此一来,恶意节点就会更有优势挖到下面的块。
35+
36+
## Reference
37+
38+
- Ouroboros

content/cardano/ouroboros.md

Lines changed: 42 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1 +1,43 @@
11
[The Bitcoin Backbone Protocol: Analysis and Applications](https://eprint.iacr.org/2014/765.pdf)
2+
3+
4+
# Ouroboros: A Provably Secure Proof-of-Stake Blockchain Protocol
5+
6+
- Proof of Stake
7+
- Proof of physical resources(e.g., proof of work)
8+
9+
10+
First, we provide a model that formalizes the problem of realizing a PoS-based blockchain protocol. The model we introduce is in the spirit of [24], focusing on persistence and liveness,
11+
12+
- *persistence*
13+
- *liveness*
14+
15+
16+
coin-flipping protocol ==> produce the randomness for the leader election process
17+
18+
19+
Also, unique to our approach is the fact that the system ignores round-to-round stake modifications. Instead, a snapshot of the current set of stakeholders is taken in regular
20+
intervals called epochs; in each such interval a secure multiparty computation takes place utilizing the blockchain itself as the broadcast channel.
21+
22+
23+
Specifically, in each epoch a set of randomly selected stakeholders form a committee which is then responsible for executing the coin-flipping protocol. The outcome of the protocol determines the set of next stakeholders to execute the protocol in the next epoch as well as the outcomes of all leader elections for the epoch.
24+
25+
26+
- a snapshot of the current set of stakeholders is taken in regular intervals called epochs
27+
28+
- in each such interval a secure multiparty computation takes place utilizing the blockchain itself as the broadcast channel
29+
30+
31+
Our protocol is secure under a number of plausible assumptions:
32+
(1) the network is synchronous in the sense that an upper bound can be determined during which any honest stakeholder is able to communicate with any other stakeholder,
33+
(2) a number of stakeholders drawn from the honest majority is available as needed to participate in each epoch,
34+
(3) the stakeholders do not remain offline for long periods of time,
35+
(4) the adaptivity of corruptions is subject to a small delay that is measured in rounds linear in the security parameter (or alternatively, the players have access to a sender-anonymous broadcast channel).
36+
37+
Sleepy consensus considers a fixed stakeholder distribution (i.e., stake does not evolve over time) and targets a “mixed” corruption setting, where the adversary is allowed to be adaptive as well as perform fail-stop and recover corruptions in addition to Byzantine faults.
38+
39+
Snow White [7] addresses an evolving stakeholder distribution and uses a corruption delay mechanism similar to ours for arguing security. Nevertheless, contrary to our protocol, the Snow White design is susceptible to a “grinding” type of attack that can bias high probability events in favor of the adversary
40+
41+
Algorand
42+
43+
- [Ouroboros: A Provably Secure Proof-of-Stake Blockchain Protocol](https://eprint.iacr.org/2016/889.pdf)

0 commit comments

Comments
 (0)