From: Tamas Blummer <tamas@bitsofproof.com>
To: "Jorge Timón" <jtimon@monetize.io>
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Plans to separate wallet from core
Date: Tue, 24 Jun 2014 13:48:05 +0200 [thread overview]
Message-ID: <F8592D15-B751-4DD9-A573-6373934C8D44@bitsofproof.com> (raw)
In-Reply-To: <CAC1+kJMn3p5H6A8GGiuF56d411zC4qsTomuy7A5e0+OQT78FGQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 373 bytes --]
I think there are three typical uses:
1. Building consensus on the block chain. This is what the core is for.
2. Single user wallets. This is where SPV alone is good.
3. Services e.g. exchange, payment processor .... This is where core + indexing server talking SPV to core is the right choice
Regards,
Tamás Blummer
Founder, CEO
http://bitsofproof.com
[-- Attachment #1.2.1: Type: text/html, Size: 4899 bytes --]
[-- Attachment #1.2.2: email.png --]
[-- Type: image/png, Size: 7120 bytes --]
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
next prev parent reply other threads:[~2014-06-24 12:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-23 9:50 [Bitcoin-development] Plans to separate wallet from core Jorge Timón
2014-06-23 10:32 ` Wladimir
2014-06-23 20:15 ` Jorge Timón
2014-06-24 9:07 ` Wladimir
2014-06-24 9:44 ` Wladimir
2014-06-24 13:24 ` Thomas Voegtlin
2014-06-24 15:33 ` Justus Ranvier
2014-06-24 16:40 ` Jorge Timón
2014-06-25 5:43 ` Wladimir
2014-06-24 9:11 ` Mike Hearn
2014-06-24 9:40 ` Wladimir
2014-06-24 10:12 ` Mike Hearn
2014-06-24 11:29 ` Jorge Timón
2014-06-24 11:48 ` Tamas Blummer [this message]
2014-06-24 13:26 ` Jorge Timón
2014-06-24 13:37 ` Pieter Wuille
2014-06-24 11:58 ` Wladimir
2014-06-24 12:16 ` Mike Hearn
2014-06-24 12:41 ` Wladimir
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=F8592D15-B751-4DD9-A573-6373934C8D44@bitsofproof.com \
--to=tamas@bitsofproof.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=jtimon@monetize.io \
/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