From: "Luke-Jr" <luke@dashjr•org>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Project status
Date: Tue, 13 Sep 2011 12:40:23 -0400 [thread overview]
Message-ID: <201109131240.26029.luke@dashjr.org> (raw)
In-Reply-To: <CABsx9T1SeEFkZkTfB_3Cy=iSms_2burxAo4bRdO-YJwHY7B8Ow@mail.gmail.com>
On Tuesday, September 13, 2011 10:43:27 AM Gavin Andresen wrote:
> 3) I'd really like to come to consensus on one or more
> 'multi-signature' standard transactions to enable much better wallet
> backup and security.
More important in this area, IMO, is support for deterministic keychains in
wallets. Type 2, according to gmaxwell's original spec, seems pretty ideal,
and significantly improves security for many use cases. Since it allows a
wallet to contain a public keychain without the matching private keychain,
webservers, POS, and other services can be provisioned only with the keychain
required to generate/access infinite public keys, and without the private
keyroot needed to spend them.
The ideal scenario in this regard, as I see it, is this:
- Webserver wallets are provisioned with multiple public keychains (one per
webserver), and configured to use a specific one for getnewaddress/etc. By
provisioning them with *all* the public keychains, their listtransactions/etc
can see the transactions sent to other webservers, necessary to show
confirmations to the end user and such.
- Business keeps a locked-down *offline* wallet with the private keychains for
all the forementioned public keychains. Only this wallet has the information
required to spend the income. The wallet is encrypted, and can only be
accessed by staff with the proper position/authority to authorize expenses.
- A third wallet is used by staff to prepare expense transactions. It keeps
track of locking coins it knows are in the process of being spent, and any
staff member can create new ones. Once created, they must submit the
transaction to a staff member with the proper authority to bring it to the
offline transaction-signing wallet (on a USB key), where it is signed, and
returned to this third wallet.
Another feature that needs some attention is signmessage. It can be used to
send a transaction id/summary to a specified email address signed by the
sending key of the same transaction (these can be added to the send-money
GUI). This would allow merchants to publish a single payment address and still
be able to verify which customers sent payment.
next prev parent reply other threads:[~2011-09-13 16:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-13 14:43 Gavin Andresen
2011-09-13 16:40 ` Luke-Jr [this message]
2011-09-13 16:48 ` Douglas Huff
2011-09-13 16:53 ` Luke-Jr
-- strict thread matches above, loose matches on Subject: below --
2011-08-29 20:10 Gavin Andresen
2011-08-29 20:15 ` Luke-Jr
2011-08-30 1:09 ` Matt Corallo
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=201109131240.26029.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--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