From: Peter Vessenes <peter@coinlab•com>
To: Alan Reiner <etotheipi@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Some PR preparation
Date: Tue, 12 Mar 2013 10:35:21 -0700 [thread overview]
Message-ID: <CAMGNxUu-beLK4ZWqQrmoSfk9RgxTTJ3D9wmphPPGyFxQiE9uXg@mail.gmail.com> (raw)
In-Reply-To: <CALf2ePwae8Y0KxYqcZxEk_KZjUcQN=jaAp=QWa20QeZtJU7UAA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2604 bytes --]
Can some enterprising soul determine if there were any double-spend
attempts?
I'm assuming no, and if that's the case, we should talk about that publicly.
Either way, I think it's generally another test well done by everyone;
people pitched in on PR, tech, communication, yay Bitcoin!
On Tue, Mar 12, 2013 at 9:55 AM, Alan Reiner <etotheipi@gmail•com> wrote:
> 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."
>
>
>
> ------------------------------------------------------------------------------
> Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester
> Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the
> endpoint security space. For insight on selecting the right partner to
> tackle endpoint security challenges, access the full report.
> http://p.sf.net/sfu/symantec-dev2dev
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
--
------------------------------
[image: CoinLab Logo]PETER VESSENES
CEO
*peter@coinlab•com * / 206.486.6856 / SKYPE: vessenes
811 FIRST AVENUE / SUITE 480 / SEATTLE, WA 98104
[-- Attachment #2: Type: text/html, Size: 4729 bytes --]
next prev parent reply other threads:[~2013-03-12 17:59 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
2013-03-12 17:35 ` Peter Vessenes [this message]
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=CAMGNxUu-beLK4ZWqQrmoSfk9RgxTTJ3D9wmphPPGyFxQiE9uXg@mail.gmail.com \
--to=peter@coinlab$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=etotheipi@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