From: Alan Reiner <etotheipi@gmail•com>
To: Mike Hearn <mike@plan99•net>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] multisig, op_eval and lock_time/sequence...
Date: Sat, 12 Nov 2011 12:25:16 -0500 [thread overview]
Message-ID: <4EBEABFC.2080802@gmail.com> (raw)
In-Reply-To: <CANEZrP0LERYWrHmxzZYvzNauVF09YjLkHbPB=uty9v5p3Wck1g@mail.gmail.com>
Fair enough. I'm not expecting anyone to just suddenly adopt BIP 0010
just because I published it to the wiki. I put it there to get feedback
on what it might be missing, and maybe we can converge on a good
preliminary solution. Then update it as we start playing with it and
find more features/fixes to add to it.
Right now, I have actually implemented BIP 0010 in my own client
software (which is still a few weeks from even having an alpha version,
but nontheless I'm actually implementing it). I'm going to use TxDPs in
offline-wallet transactions, which is a nearly identical process (it's
just a 1-of-1 transaction). As such, I will be interested to test with
some other client developers, whether they can easily use the TxDPs I
produce.
I assume it doesn't bother you if I leave it the way it is, with the
acknowledgment that I know no one is adopting it yet (except for
myself). It's informational, until we get a couple different clients,
or at least test setup to play with it.
-Alan
On 11/12/2011 12:16 PM, Mike Hearn wrote:
> BIPs are either "standards track" (affects everyone, represents
> consensus), "informational" (ie basically just summarizing the authors
> viewpoints on things) or "process".
>
> My point is you can't have a credible standards track BIP until
> something has been implemented end to end. I don't think it's a good
> plan to design these things in isolation. You'll end up with bizarre
> user experiences because of technical decisions taken months earlier
> that are now hard to reverse. A working end to end implementation
> gives you the confidence to say, yes, this is how it should work,
> because here's the demo and you can see it works very well and the
> code is clean.
>
> If your BIP is informational then no problems, but I don't think
> there's much point in informational BIPs to be honest - it's easier to
> just write an email or forum post summarizing your views on things. If
> you find it a useful framework to write your thoughts in that's OK,
> but don't expect implementors to follow what's written there just
> because it's a BIP. It carries no more weight than any other document
> would.
>
>
next prev parent reply other threads:[~2011-11-12 17:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-09 10:22 Michael Grønager
2011-11-09 14:43 ` Alan Reiner
2011-11-09 15:22 ` Alan Reiner
2011-11-09 19:13 ` Gavin Andresen
2011-11-09 20:02 ` Gavin Andresen
2011-11-09 20:31 ` Michael Grønager
2011-11-09 21:18 ` Gavin Andresen
2011-11-09 21:32 ` Joel Joonatan Kaartinen
2011-11-09 22:13 ` theymos
2011-11-09 20:03 ` Michael Grønager
2011-11-10 3:00 ` Alan Reiner
2011-11-10 9:55 ` Michael Grønager
2011-11-10 12:56 ` Alan Reiner
2011-11-12 16:58 ` Mike Hearn
2011-11-12 17:10 ` Alan Reiner
2011-11-12 17:16 ` Mike Hearn
2011-11-12 17:25 ` Alan Reiner [this message]
2011-11-12 17:38 ` Mike Hearn
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=4EBEABFC.2080802@gmail.com \
--to=etotheipi@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=mike@plan99$(echo .)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