From: Justus Ranvier <justus@openbitcoinprivacyproject•org>
To: "Rune Kjær Svendsen" <runesvend@gmail•com>
Cc: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] Hash of UTXO set as consensus-critical
Date: Sat, 19 Sep 2015 12:19:11 -0500 [thread overview]
Message-ID: <55FD990F.8060102@openbitcoinprivacyproject.org> (raw)
In-Reply-To: <4424FA4D-C84F-43DD-BA7F-BAC2D570A373@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 586 bytes --]
On 19/09/15 10:45, Rune Kjær Svendsen wrote:
> We need to distinguish between two different things here:
>
> 1) A 51% attack, where the majority of mining power is *malicious* (hence “attack”)
What does "malicious" mean?
In other words, If miner A is mining honestly, and miner B is mining
maliciously, what are some of the possible difference in their behaviour
we would observe?
--
Justus Ranvier
Open Bitcoin Privacy Project
http://www.openbitcoinprivacyproject.org/
justus@openbitcoinprivacyproject•org
E7AD 8215 8497 3673 6D9E 61C4 2A5F DA70 EAD9 E623
[-- Attachment #1.2: 0xEAD9E623.asc --]
[-- Type: application/pgp-keys, Size: 18729 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2015-09-19 17:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-18 19:05 Rune Kjær Svendsen
2015-09-18 19:43 ` Patrick Strateman
2015-09-18 20:07 ` Alex Morcos
2015-09-18 20:11 ` Matt Corallo
2015-09-18 20:17 ` Rune Kjær Svendsen
2015-09-18 20:37 ` Jorge Timón
2015-09-18 20:38 ` Jorge Timón
2015-09-18 22:22 ` Vincent Truong
2015-09-19 2:30 ` Justus Ranvier
2015-09-19 15:45 ` Rune Kjær Svendsen
2015-09-19 17:19 ` Justus Ranvier [this message]
2015-09-19 20:11 ` Rune K. Svendsen
2015-09-20 0:48 ` Dave Scotese
2015-09-21 17:15 ` Justus Ranvier
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=55FD990F.8060102@openbitcoinprivacyproject.org \
--to=justus@openbitcoinprivacyproject$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=runesvend@gmail$(echo .)com \
/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