From: Mike Hearn <mike@plan99•net>
To: bgroff@lavabit•com
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] [PULL] Add scriptPubKey enforced sendescrow and redeemescrow API calls
Date: Wed, 22 Jun 2011 15:24:36 +0200 [thread overview]
Message-ID: <BANLkTi=FTLnU-riNVYssnR9FLdcEeZX7gOS6Zdv1f_XDcJoSSg@mail.gmail.com> (raw)
In-Reply-To: <18440.87.106.138.84.1308200020.squirrel@lavabit.com>
[-- Attachment #1: Type: text/plain, Size: 1759 bytes --]
Thanks for writing this. It's great to see somebody run with the contracts
protocol.
Your proposed protocol is simpler than the one I suggested, so I updated the
Contracts wiki page to use it. However your implementation, as pointed out
by Gavin, is too complicated. See my proposal on the wiki here:
https://en.bitcoin.it/wiki/Contracts
I think you can just use an output script of
2 <K1> <K2> <K3> 3 CHECKMULTISIGVERIFY
On Thu, Jun 16, 2011 at 6:53 AM, <bgroff@lavabit•com> wrote:
> I have a pull request here:
>
> https://github.com/bitcoin/bitcoin/pull/319
>
> >From the README:
>
> Bitcoin "escrow" are coins that are under the control of multiple
> parties. The initial implementation allows n parties to vote, with
> k good signatures needed (k <= n).
>
> This eliminates single points of failure and reduces the trust required
> in many transaction use cases.
>
> Use cases include Escrow (without trusting the escrow agent with the
> coins), immediate payment and funds locked with multi-party signatures.
>
> This was inspired by https://forum.bitcoin.org/index.php?topic=8821.0 and
> https://forum.bitcoin.org/index.php?topic=4723.msg68804 .
>
> Feedback on the pull is very much appreciated.
>
>
>
>
>
> ------------------------------------------------------------------------------
> EditLive Enterprise is the world's most technically advanced content
> authoring tool. Experience the power of Track Changes, Inline Image
> Editing and ensure content is compliant with Accessibility Checking.
> http://p.sf.net/sfu/ephox-dev2dev
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
[-- Attachment #2: Type: text/html, Size: 2803 bytes --]
next prev parent reply other threads:[~2011-06-22 13:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-16 4:53 bgroff
2011-06-22 13:24 ` Mike Hearn [this message]
2011-06-22 13:42 ` Mike Hearn
2011-06-22 16:01 ` bgroff
2011-06-22 14:08 ` Gavin Andresen
2011-06-22 14:49 ` Mike Hearn
2011-06-22 15:32 ` Gavin Andresen
2011-06-22 16:02 ` Mike Hearn
2011-06-22 16:23 ` bgroff
2011-06-22 19:33 ` bgroff
2011-06-22 20:44 ` bgroff
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='BANLkTi=FTLnU-riNVYssnR9FLdcEeZX7gOS6Zdv1f_XDcJoSSg@mail.gmail.com' \
--to=mike@plan99$(echo .)net \
--cc=bgroff@lavabit$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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