public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: bgroff@lavabit.com
To: "Gregory Maxwell" <gmaxwell@gmail.com>
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Discussion related to pull 349 and pull 319 (escrow transactions)
Date: Sun, 7 Aug 2011 20:21:48 -0400 (EDT)	[thread overview]
Message-ID: <42430.77.247.181.163.1312762908.squirrel@lavabit.com> (raw)
In-Reply-To: <CAAS2fgQ6GXfebUV8_PLVpLJ9jvPF8FXiBqwquhGFNZ+Vt3uCtg@mail.gmail.com>

> On Wed, Aug 3, 2011 at 2:10 AM,  <bgroff@lavabit.com> wrote:
>> Thank you!  (I think you mean 319 here)
>
> Correct.
>
>> With Eligius mining !IsStandard transactions and probably other pools
>> open
>> to the idea, I am hopeful that we can quickly get 30%+ of mining power
>> to
>> upgrade, which means that we could still mine these in a reasonable time
>> frame (under 1 hour).
>
> It's not just a matter of mining power, it's also a question of
> propagation.  Matt and I tried to perform a non-standard transaction
> weeks ago and weren't able to get in mined after many hours. (we
> eventually double spent the input with a normal transaction in order
> to make it go away, interestingly one point about non-propagating txn
> is that they're extra vulnerable to double spending by a standard txn,
> as the non-standard one won't preclude the propagation of the standard
> one)

Right, the user would have to connect directly to miners accepting
non-standard transactions.

> From discussion on IRC it seemed clear enough that the current focus
> on maturity/bugfixes is probably going to delay your full patch, but
> the IsStandard part is uncontroversial and could go in quickly.

With the latest high profile security breaches, I am hoping that the whole
things can be pulled relatively soon.  Building secure deposit systems
will improve trust in the ecosystem.

I've included a significant amount of unit tests to "pay" for the
additional feature, and I can add more if needed.

--
Bobby Groff






      reply	other threads:[~2011-08-08  0:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-23 23:39 [Bitcoin-development] Discussion related to pull 349 and pull 319 (escrow transactions) Gregory Maxwell
2011-08-03  6:10 ` bgroff
2011-08-04 20:35   ` Gregory Maxwell
2011-08-08  0:21     ` bgroff [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=42430.77.247.181.163.1312762908.squirrel@lavabit.com \
    --to=bgroff@lavabit.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=gmaxwell@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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