From: Alan Reiner <etotheipi@gmail•com>
To: Luke-Jr <luke@dashjr•org>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Some PR preparation
Date: Tue, 12 Mar 2013 12:55:26 -0400 [thread overview]
Message-ID: <CALf2ePwae8Y0KxYqcZxEk_KZjUcQN=jaAp=QWa20QeZtJU7UAA@mail.gmail.com> (raw)
In-Reply-To: <201303121210.34515.luke@dashjr.org>
[-- Attachment #1: Type: text/plain, Size: 1398 bytes --]
On Tue, Mar 12, 2013 at 8:10 AM, Luke-Jr <luke@dashjr•org> wrote:
>
>
> I think we should be careful not to downplay the reality either.
> For a number of hours, transactions could have received up to N
> confirmations
> and then still been reversed. While we could contact the bigger payment
> processors, I saw people still trying to buy/sell on OTC, whom could have
> been
> scammed even by taking standard precautions.
>
>
I don't want to misrepresent what happened, but how much of that was really
a risk? The block was rejected, but the transactions were not. Any valid
transactions to hit the network would get added to everyone's memory pool
and mined in both chains. Thus all nodes would still reject double-spend
attempts. As far as I understood it, you would've had to have majority
mining power on one of the chains (and both had non-negligible computing
power on them), so double-spending still required an exceptional amount of
resources -- just not the normal 50% that is normally needed. Perhaps...
10%? But how many people can even have 10%? In addition to that, a
victim needs to be found that hasn't seen the alert, is willing to execute
a large transaction, and is on the wrong side of the chain.
Is this incorrect? Yes, there was less resources needed to execute an
attack -- but it still required a very powerful attacker, way outside the
scope of "regular users."
[-- Attachment #2: Type: text/html, Size: 2018 bytes --]
next prev parent reply other threads:[~2013-03-12 16:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-12 7:03 Alan Reiner
2013-03-12 12:10 ` Luke-Jr
2013-03-12 16:55 ` Alan Reiner [this message]
2013-03-12 17:35 ` Peter Vessenes
2013-03-12 18:09 ` Gregory Maxwell
2013-03-12 18:39 ` Gregory Maxwell
2013-03-12 19:53 ` Christian Decker
2013-03-12 20:09 ` Peter Vessenes
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='CALf2ePwae8Y0KxYqcZxEk_KZjUcQN=jaAp=QWa20QeZtJU7UAA@mail.gmail.com' \
--to=etotheipi@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=luke@dashjr$(echo .)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