From: Ethan Heilman <eth3rs@gmail•com>
To: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] New paper: On Bitcoin Security in the Presence of Broken Crypto Primitives
Date: Mon, 22 Feb 2016 13:06:56 -0500 [thread overview]
Message-ID: <CAEM=y+WhxR-GNY_O1pvY0F_DjB1XSpDRR28q38HhscUES9tR3g@mail.gmail.com> (raw)
In-Reply-To: <CAEM=y+W0XkWEPcKwBsyHSp8OSVyZ0B0YN65v11No5kK05fE1wg@mail.gmail.com>
[-- 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 --]
parent reply other threads:[~2016-02-22 18:06 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAEM=y+W0XkWEPcKwBsyHSp8OSVyZ0B0YN65v11No5kK05fE1wg@mail.gmail.com>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAEM=y+WhxR-GNY_O1pvY0F_DjB1XSpDRR28q38HhscUES9tR3g@mail.gmail.com' \
--to=eth3rs@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox