Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of lavabit.com
	designates 72.249.41.33 as permitted sender)
	client-ip=72.249.41.33; envelope-from=bgroff@lavabit.com;
	helo=karen.lavabit.com; 
Message-ID: <42430.77.247.181.163.1312762908.squirrel@lavabit.com>
In-Reply-To: <CAAS2fgQ6GXfebUV8_PLVpLJ9jvPF8FXiBqwquhGFNZ+Vt3uCtg@mail.gmail.com>
References: <CAAS2fgQ-L-1K2Oi40tqnhxpnnWQHqgbd4BmqedhA3WcevYiCzg@mail.gmail.com>
	<43351.137.56.163.46.1312351847.squirrel@lavabit.com>
	<CAAS2fgQ6GXfebUV8_PLVpLJ9jvPF8FXiBqwquhGFNZ+Vt3uCtg@mail.gmail.com>
Date: Sun, 7 Aug 2011 20:21:48 -0400 (EDT)
From: bgroff@lavabit.com
To: "Gregory Maxwell" <gmaxwell@gmail.com>
User-Agent: SquirrelMail/1.4.13
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Discussion related to pull 349 and pull
 319 (escrow transactions)
Precedence: list

> On Wed, Aug 3, 2011 at 2:10 AM,  <bgroff@lavabit.com> wrote:
>> Thank you! =C2=A0(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 ti=
me
>> 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 whol=
e
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