Browse Source

Documentation: The character for 1/3 fraction could not be rendered in PDF on readthedocs. (#1326)

pull/1321/merge
racin 7 years ago
committed by Anton Kaliaev
parent
commit
066aee3045
1 changed files with 3 additions and 3 deletions
  1. +3
    -3
      docs/specification/byzantine-consensus-algorithm.rst

+ 3
- 3
docs/specification/byzantine-consensus-algorithm.rst View File

@ -329,11 +329,11 @@ collateral on all other forks. Clients should verify the signatures on
the reorg-proposal, verify any evidence, and make a judgement or prompt the reorg-proposal, verify any evidence, and make a judgement or prompt
the end-user for a decision. For example, a phone wallet app may prompt the end-user for a decision. For example, a phone wallet app may prompt
the user with a security warning, while a refrigerator may accept any the user with a security warning, while a refrigerator may accept any
reorg-proposal signed by +½ of the original validators.
reorg-proposal signed by +1/2 of the original validators.
No non-synchronous Byzantine fault-tolerant algorithm can come to No non-synchronous Byzantine fault-tolerant algorithm can come to
consensus when + of validators are dishonest, yet a fork assumes that
+ of validators have already been dishonest by double-signing or
consensus when 1/3+ of validators are dishonest, yet a fork assumes that
1/3+ of validators have already been dishonest by double-signing or
lock-changing without justification. So, signing the reorg-proposal is a lock-changing without justification. So, signing the reorg-proposal is a
coordination problem that cannot be solved by any non-synchronous coordination problem that cannot be solved by any non-synchronous
protocol (i.e. automatically, and without making assumptions about the protocol (i.e. automatically, and without making assumptions about the


Loading…
Cancel
Save