summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorUser <naumenko.gs@gmail.com>2019-11-04 13:30:08 -0500
committerUser <naumenko.gs@gmail.com>2019-11-04 13:30:08 -0500
commit2e7dab87ef6822d2ed81df0eaa8e4fa9a665e86c (patch)
tree0bcd7f799bea69558569da0880002da9becd6ed0
parent161c482f123fee4cabe06b045bad68bac805f24c (diff)
added missing leading zero
-rw-r--r--bip-330.mediawiki4
1 files changed, 2 insertions, 2 deletions
diff --git a/bip-330.mediawiki b/bip-330.mediawiki
index 36dbdd4..197f94e 100644
--- a/bip-330.mediawiki
+++ b/bip-330.mediawiki
@@ -112,13 +112,13 @@ For announcing and relaying transaction outside of reconciliation, we need an un
Set reconciliation primarily consists of the transmission and decoding of a reconciliation set sketch upon request.
-[[File:bip-330/recon_scheme_merged.png|framed|center|Set reconciliation protocol flow]]
+[[File:bip-0330/recon_scheme_merged.png|framed|center|Set reconciliation protocol flow]]
====Bisection====
If a node is unable to reconstruct the set difference from the received sketch, the node then makes an additional reconciliation request, similar to the initial one, but this request is applied to only a fraction of possible transactions (e.g., in the range 0x0–0x8). Because of the linearity of sketches, a sketch of a subset of transactions would allow the node to compute a sketch for the remainder, which saves bandwidth.
-[[File:bip-330/bisection.png|framed|300px|center|Bisection]]
+[[File:bip-0330/bisection.png|framed|300px|center|Bisection]]
===New messages===
Several new protocol messages are added: sendrecon, reqreconcil, sketch, reqbisec, reconcildiff, invtx, gettx. This section describes their serialization, contents, and semantics.