From: Peter Vessenes <peter@coinlab•com>
To: Christian Decker <decker.christian@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Some PR preparation
Date: Tue, 12 Mar 2013 13:09:17 -0700 [thread overview]
Message-ID: <CAMGNxUtcwO+masMDzkPN0kwzd=FTKXW39OYLF2dvB1yXKGMqhQ@mail.gmail.com> (raw)
In-Reply-To: <CALxbBHXdPJXoGp-W8y8ynUTCsSY5L0yN1juya-UhB9KhMYpfmg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3673 bytes --]
Thanks Chris.
Yep, looks like an honest-ish user managed to accidentally get one tx into
one chain and another into the other.
I think I'd cautiously say that if OKPay gets their cash back, or freezes
his balance nobody is out BTC for last night, (instead just time and
effort).
I'm doing a little FUD-fighting right now, but will try and pick up a bit
more if necessary tonight after my flight lands. I think this is mostly
over the heads of a lot of our typical media contacts, though.
Peter
On Tue, Mar 12, 2013 at 12:53 PM, Christian Decker <
decker.christian@gmail•com> wrote:
> Just a quick and dirty check if something bad actually happened. 430
> transactions that were confirmed in the alt-chain, are not confirmed
> in the true blockchain. The good news is that as far as I can tell
> most of them are low volume transactions destined for SD.
>
> 7 transactions were true double spends, or to be more precise
> transactions in which an conflicting transaction was confirmed in the
> new chain (with their respective amount):
>
> 12814b8ad57ce5654ba69eb26a52ddae1bff42093ca20cef3ad96fe7fd85d195 261 BTC
> cb36ba33b3ecd4d3177d786209670c9e6cdf95eb62be54986f0b49ca292714af 0.06 BTC
> 7192807f952b252081d0db0aa7575c4695b945820adaf7776b7189e6b3d86f96 0.01 BTC
> 355d4ea51c3b780cf0b10e8099a06a31484e0060bc140b63f3d6e5fb713ace5e 0.05 BTC
> b961bc0c663a46893afd3166a604e7e2639533522d9fec61fdb95eb665e86f5a 0.61 BTC
> 138063e4bdb76feaa511f1e7f9c681eb468ef9140c141671741c965e503b84c6 1.62 BTC
> a10bd194cdbf9aa4c12eb0b120056998a081a9b0d93d70570edff24dec831f90 0.81
>
> So the one transaction that really hurt was the one published on
> BitcoinTalk. We're not yet out of the woods as some of the 423
> transactions still have a chance of being doublespent, but looks like
> it's not that bad after all.
>
> Cheers,
> Chris
>
> P.S.: For a complete list of transactions see http://pastebin.com/wctJU3Ln
> --
> Christian Decker
>
>
> On Tue, Mar 12, 2013 at 7:39 PM, Gregory Maxwell <gmaxwell@gmail•com>
> wrote:
> > On Tue, Mar 12, 2013 at 11:09 AM, Gregory Maxwell <gmaxwell@gmail•com>
> wrote:
> >> On Tue, Mar 12, 2013 at 10:35 AM, Peter Vessenes <peter@coinlab•com>
> wrote:
> >>> 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.
> > [snip]
> >> I agree it would be good to confirm no one was ripped off, even though
> >> we can't say there weren't any attempts.
> >
> > https://bitcointalk.org/index.php?topic=152348.msg1616747#msg1616747
> >
> >
> ------------------------------------------------------------------------------
> > Everyone hates slow websites. So do we.
> > Make your web apps faster with AppDynamics
> > Download AppDynamics Lite for free today:
> > http://p.sf.net/sfu/appdyn_d2d_mar
> > _______________________________________________
> > Bitcoin-development mailing list
> > Bitcoin-development@lists•sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_mar
> _______________________________________________
> 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: 6131 bytes --]
prev parent reply other threads:[~2013-03-12 20:09 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
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 [this message]
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='CAMGNxUtcwO+masMDzkPN0kwzd=FTKXW39OYLF2dvB1yXKGMqhQ@mail.gmail.com' \
--to=peter@coinlab$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=decker.christian@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