From: Alan Reiner <etotheipi@gmail•com>
To: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] Multi-sig tx execution ideas
Date: Fri, 28 Oct 2011 18:28:30 -0400 [thread overview]
Message-ID: <4EAB2C8E.6040103@gmail.com> (raw)
I just posted BIP 0010 to gist : https://gist.github.com/1321518
The goal is to provide a standard method for proposing how to spend
multi-sig TxOuts, and collect signatures without actually having to
understand BTC under-the-hood. I envision, even without any program
installed, moderately-interested users could figure out this process
without a third-party. The addition of an installed program that
automatically detects .txdp files and intelligently presents the
information to the users, could bring this functionality to even more
users. Perhaps I'm too optimistic, though...
This is, of course, open for discussion/improvement. I've talked
briefly with Gavin about this, and he suggested Base64 instead of hex
for the block-encoding. I'd lean towards Base58 because developers
already have it in their codebase. Also, the separation of fields by
underscore characters could be changed. Spaces would make it easier for
C++ to read them in using stream operators "<<" and ">>".
-Alan
reply other threads:[~2011-10-28 22:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4EAB2C8E.6040103@gmail.com \
--to=etotheipi@gmail$(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