public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
* [bitcoin-dev] New paper: On Bitcoin Security in the Presence of Broken Crypto Primitives
       [not found] <CAEM=y+W0XkWEPcKwBsyHSp8OSVyZ0B0YN65v11No5kK05fE1wg@mail.gmail.com>
@ 2016-02-22 18:06 ` Ethan Heilman
  0 siblings, 0 replies; only message in thread
From: Ethan Heilman @ 2016-02-22 18:06 UTC (permalink / raw)
  To: Bitcoin Dev

[-- Attachment #1: Type: text/plain, Size: 1020 bytes --]

"*Abstract: *Digital currencies like Bitcoin rely on cryptographic
primitives to operate. However, past experience shows that cryptographic
primitives do not last forever: increased computational power and advanced
cryptanalysis cause primitives to break frequently, and motivate the
development of new ones. It is therefore crucial for maintaining trust in a
crypto currency to anticipate such breakage.
We present the first systematic analysis of the effect of broken primitives
on Bitcoin. We identify the core cryptographic building blocks and analyze
the various ways in which they can break, and the subsequent effect on the
main Bitcoin security guarantees. Our analysis reveals a wide range of
possible effects depending on the primitive and type of breakage, ranging
from minor privacy violations to a complete breakdown of the currency.
Our results lead to several observations on, and suggestions for, the
Bitcoin migration plans in case of broken cryptographic primitives."

https://eprint.iacr.org/2016/167

[-- Attachment #2: Type: text/html, Size: 1128 bytes --]

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2016-02-22 18:06 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <CAEM=y+W0XkWEPcKwBsyHSp8OSVyZ0B0YN65v11No5kK05fE1wg@mail.gmail.com>
2016-02-22 18:06 ` [bitcoin-dev] New paper: On Bitcoin Security in the Presence of Broken Crypto Primitives Ethan Heilman

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox