From a4d373f0afbcdc939b240e42dfdd07ebcf31e4d6 Mon Sep 17 00:00:00 2001 From: "mergify[bot]" <37929162+mergify[bot]@users.noreply.github.com> Date: Tue, 23 Jun 2020 23:42:25 +0000 Subject: [PATCH] Fix plumtree link (#10755) (#10759) Co-authored-by: publish-docs.sh (cherry picked from commit c52f06a54a9a2809edce4f640eb3587301db852a) Co-authored-by: Dan Albert --- docs/src/validator/gossip.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/src/validator/gossip.md b/docs/src/validator/gossip.md index e4b9576cf9..a5ebc3d402 100644 --- a/docs/src/validator/gossip.md +++ b/docs/src/validator/gossip.md @@ -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.