From: Sriram Karra <karra.etc@gmail•com>
To: Mike Hearn <hearn@vinumeris•com>
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Future Of Bitcoin-Cores Wallet
Date: Tue, 11 Aug 2015 16:51:31 +0530 [thread overview]
Message-ID: <CAFkt3UPaEu5uxeLD0kUDK9xDhA8szy29F1U7HaSzj0ScOt1LsQ@mail.gmail.com> (raw)
In-Reply-To: <CA+w+GKR1BNpVk4SAKExrkGDMzb+BQfinpmWGbNiMyM89DnzOFA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 913 bytes --]
On Tue, Aug 11, 2015 at 4:33 PM, Mike Hearn via bitcoin-dev <
bitcoin-dev@lists•linuxfoundation.org> wrote:
> Hey Jonas,
>
> I think your analysis of what (some) users need is a good one.
>
> We've discussed this before so I know you prefer your current approach,
> but I personally would take a slightly different path to reach the same end:
>
> 1. Support serving of SPV wallets from pruned storage. This means some
> protocol upgrades, BIPs, etc. It helps all SPV wallets, including on phones.
> 2. Then make a bitcoinj based desktop wallet app, that contains a
> bundled bitcoind.
>
> It makes a lot of sense to have single set of reference implementations
for the different components. So unless you also support something you have
not explicitly stated - get rid of bitcoin-qt in its current form, the
above does not meet the spirit of Jonas' original post - which makes a load
of sense to me.
[-- Attachment #2: Type: text/html, Size: 1319 bytes --]
next prev parent reply other threads:[~2015-08-11 11:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-11 9:02 Jonas Schnelli
2015-08-11 11:03 ` Mike Hearn
2015-08-11 11:21 ` Sriram Karra [this message]
2015-08-11 15:46 ` Jeff Garzik
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=CAFkt3UPaEu5uxeLD0kUDK9xDhA8szy29F1U7HaSzj0ScOt1LsQ@mail.gmail.com \
--to=karra.etc@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=hearn@vinumeris$(echo .)com \
/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