From: Eric Lombrozo <elombrozo@gmail.com>
To: Gregory Maxwell <gmaxwell@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Multiwallet support
Date: Fri, 21 Dec 2012 10:11:21 -0800 [thread overview]
Message-ID: <2F31D463-26FA-4EC1-8571-4BAF1C4EE941@gmail.com> (raw)
In-Reply-To: <CAAS2fgRG6kY8ke4hTdUjVBB1dmCppmzwo7qmOM-ytKS1299Z1w@mail.gmail.com>
I like that idea. I'm close to having something working along those lines. Hopefully I'll be able to push something by tonight.
>
> How about a rpc like "usewallet <foo> <normal RPC>" that simply
> generalizes all the rpcs?
>
> And instead of explicitly deactivating rpcs that don't make sense,
> simply have them return an error. Or, for example, sendtoaddress on
> a watching wallet should actually return an unsigned raw transaction
> and a wallet specific message that tells you where to find the private
> key.
>
> I think it's desirable to not break compatibility but for this kind of
> feature compatibility should not get in the way of doing it right.
prev parent reply other threads:[~2012-12-21 18:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-21 8:53 [Bitcoin-development] Multiwallet support Eric Lombrozo
2012-12-21 13:20 ` Gregory Maxwell
2012-12-21 18:11 ` Eric Lombrozo [this message]
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=2F31D463-26FA-4EC1-8571-4BAF1C4EE941@gmail.com \
--to=elombrozo@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=gmaxwell@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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