MIME-Version: 1.0
From: Riccardo Casatta <riccardo.casatta@gmail.com>
Date: Mon, 28 Aug 2017 17:50:23 +0200
Message-ID: <CADabwBBrrPM2f9h_sgxY12tg=FUvKKCcnCC8ixnct93YL9uEFQ@mail.gmail.com>
To: bitcoin-dev@lists.linuxfoundation.org
Content-Type: multipart/alternative; boundary="001a11473df6ebd7600557d241a0"
Subject: [bitcoin-dev] "Compressed" headers stream
Precedence: list

--001a11473df6ebd7600557d241a0
Content-Type: text/plain; charset="UTF-8"

Hi everyone,

the Bitcoin headers are probably the most condensed and important piece of
data in the world, their demand is expected to grow.

When sending a stream of continuous block headers, a common case in IBD and
in disconnected clients, I think there is a possible optimization of the
transmitted data:
The headers after the first could avoid transmitting the previous hash
cause the receiver could compute it by double hashing the previous header
(an operation he needs to do anyway to verify PoW).
In a long stream, for example 2016 headers, the savings in bandwidth are
about 32/80 ~= 40%
without compressed headers 2016*80=161280 bytes
with compressed headers 80+2015*48=96800 bytes

What do you think?


In OpenTimestamps calendars we are going to use this compression to give
lite-client a reasonable secure proofs (a full node give higher security
but isn't feasible in all situations, for example for in-browser
verification)
To speed up sync of a new client Electrum starts with the download of a file
<https://headers.electrum.org/blockchain_headers> ~36MB containing the
first 477637 headers.
For this kind of clients could be useful a common http API with fixed
position chunks to leverage http caching. For example /headers/2016/0
returns the headers from the genesis to the 2015 header included while
/headers/2016/1 gives the headers from the 2016th to the 4031.
Other endpoints could have chunks of 20160 blocks or 201600 such that with
about 10 http requests a client could fast sync the headers


-- 
Riccardo Casatta - @RCasatta <https://twitter.com/RCasatta>

--001a11473df6ebd7600557d241a0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi everyone,</div><div><br></div><div>the Bitcoin hea=
ders are probably the most condensed and important piece of data in the wor=
ld, their demand is expected to grow.</div><div><br></div><div>When sending=
 a stream of continuous block headers, a common case in IBD and in disconne=
cted clients, I think there is a possible optimization of the transmitted d=
ata:</div><div>The headers after the first could avoid transmitting the pre=
vious hash cause the receiver could compute it by double hashing the previo=
us header (an operation he needs to do anyway to verify PoW).</div><div>In =
a long stream, for example 2016 headers, the savings in bandwidth are about=
 32/80 ~=3D 40%</div><div>without compressed headers 2016*80=3D161280 bytes=
</div><div>with compressed headers 80+2015*48=3D96800 bytes</div><div><br><=
/div><div>What do you think?</div><div><br></div><div><br></div><div>In Ope=
nTimestamps calendars we are going to use this compression to give lite-cli=
ent a reasonable secure proofs (a full node give higher security but isn=
9;t feasible in all situations, for example for in-browser verification)</d=
iv><div>To speed up sync of a new client Electrum starts with the download =
of a <a href=3D"https://headers.electrum.org/blockchain_headers">file</a>=
=C2=A0~36MB containing the first 477637 headers.=C2=A0</div><div>For this k=
ind of clients could be useful a common http API with fixed position chunks=
 to leverage http caching. For example /headers/2016/0 returns the headers =
from the genesis to the 2015 header included while /headers/2016/1 gives th=
e headers from the 2016th to the 4031.</div><div>Other endpoints could have=
 chunks of 20160 blocks or 201600 such that with about 10 http requests a c=
lient could fast sync the headers</div><br clear=3D"all"><div><br></div>-- =
<br><div class=3D"gmail_signature"><div dir=3D"ltr">Riccardo Casatta - <a h=
ref=3D"https://twitter.com/RCasatta" target=3D"_blank">@RCasatta</a></div><=
/div>
</div>

--001a11473df6ebd7600557d241a0--