Fix plumtree link (#10755) (#10759)

Co-authored-by: publish-docs.sh <maintainers@solana.com>
(cherry picked from commit c52f06a54a)

Co-authored-by: Dan Albert <dan@solana.com>
This commit is contained in:
mergify[bot]
2020-06-23 23:42:25 +00:00
committed by GitHub
parent 52eea215ce
commit a4d373f0af

View File

@ -82,7 +82,9 @@ Just like _pull message_, nodes are selected into the active set based on weight
## Notable differences from PlumTree
The active push protocol described here is based on [Plum Tree](https://haslab.uminho.pt/jop/files/lpr07a.pdf). The main differences are:
The active push protocol described here is based on
[Plum Tree](https://haslab.uminho.pt/sites/default/files/jop/files/lpr07a.pdf).
The main differences are:
* Push messages have a wallclock that is signed by the originator. Once the wallclock expires the message is dropped. A hop limit is difficult to implement in an adversarial setting.
* Lazy Push is not implemented because its not obvious how to prevent an adversary from forging the message fingerprint. A naive approach would allow an adversary to be prioritized for pull based on their input.