MIME-Version: 1.0
From: ha su <hasu.research@gmail.com>
Date: Fri, 31 Jan 2020 14:38:22 +0100
Message-ID: <CAEmzEcO51GEETunPBXuecpVtZCvH4rpvcNcLsYCrDaDH=3_qVQ@mail.gmail.com>
To: bitcoin-dev@lists.linuxfoundation.org
Content-Type: multipart/alternative; boundary="0000000000002504f0059d6fb12d"
Subject: [bitcoin-dev] Purge attacks (spin on sabotage attacks)
Precedence: list

--0000000000002504f0059d6fb12d
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi all,

I think I discovered an interesting form of sabotage attack (possible for
miners) that tries to create coordination disincentives among Bitcoin users
- named after the dystopian movie The Purge, where all crime is legal for
one night every year.

TLDR
* An attacker replaces the most recent blocks full of transactions with
empty blocks.
* Previously confirmed txns return into the mempool, where anyone with a
minimum of technical knowledge or access to public tools can
opportunistically double-spend their txns back to themselves. (the process
is the same as double-spending regular zero-conf txns)

The attack seems useful to undermine trust in Bitcoin's assurances, e.g.
the future finality of transactions. It differs from other forms of
sabotage (e.g. DoS by mining only empty blocks) in that it specifically
disrupts the coordination process among users in response to the attack.

By giving some users a chance to benefit from the attack, the attacker
gives them a vested interest in staying on the attack chain. If enough
users accept the invitation to double-spend, it might become harder to come
to consensus on how to deal with the attack.

Purge attacks probably don=E2=80=99t constitute a bigger risk than other kn=
own
forms of sabotage attacks, but seem like an interesting spin where the
attacker specifically targets the pre-coordination of defenders.

You can find the full report, incl. some mitigations against sabotage
attacks, at
https://blog.deribit.com/insights/destabilizing-bitcoin-consensus-with-purg=
e-attacks/

Your feedback is highly appreciated.

Regards,
Hasu

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

<div dir=3D"ltr">Hi all,<br><br>I think I discovered an interesting form of=
 sabotage attack (possible for miners) that tries to create coordination di=
sincentives among Bitcoin users - named after the dystopian movie The Purge=
, where all crime is legal for one night every year.<br><br>TLDR<br>* An at=
tacker replaces the most recent blocks full of transactions with empty bloc=
ks. <br>* Previously confirmed txns return into the mempool, where anyone w=
ith a minimum of technical knowledge or access to public tools can opportun=
istically double-spend their txns back to themselves. (the process is the s=
ame as double-spending regular zero-conf txns)<br><br>The attack seems usef=
ul to undermine trust in Bitcoin&#39;s assurances, e.g. the future finality=
 of transactions. It differs from other forms of sabotage (e.g. DoS by mini=
ng only empty blocks) in that it specifically disrupts the coordination=C2=
=A0process among users in response to the attack.=C2=A0<br><br>By giving so=
me users a chance to benefit from the attack, the attacker gives them a ves=
ted interest in staying on the attack chain. If enough users accept the inv=
itation to double-spend, it might become harder to come to consensus on how=
 to deal with the attack.<br><br>Purge attacks probably don=E2=80=99t const=
itute a bigger risk than other known forms of sabotage attacks, but seem li=
ke an interesting spin where the attacker specifically targets the pre-coor=
dination of defenders.<br><br>You can find the full report, incl. some miti=
gations against sabotage attacks, at=C2=A0<a href=3D"https://blog.deribit.c=
om/insights/destabilizing-bitcoin-consensus-with-purge-attacks/">https://bl=
og.deribit.com/insights/destabilizing-bitcoin-consensus-with-purge-attacks/=
</a><br><br>Your feedback is highly appreciated.<br><br>Regards,<br>Hasu<br=
><br></div>

--0000000000002504f0059d6fb12d--