1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <jeremy@taplink.co>) id 1W6olq-0004b0-Ek
for bitcoin-development@lists.sourceforge.net;
Fri, 24 Jan 2014 21:58:38 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of taplink.co
designates 50.117.27.232 as permitted sender)
client-ip=50.117.27.232; envelope-from=jeremy@taplink.co;
helo=mail.taplink.co;
Received: from mail.taplink.co ([50.117.27.232])
by sog-mx-1.v43.ch3.sourceforge.com with smtp (Exim 4.76)
id 1W6olp-0000fU-O2 for bitcoin-development@lists.sourceforge.net;
Fri, 24 Jan 2014 21:58:38 +0000
Received: from [10.15.209.154] ([166.137.186.205]) by mail.taplink.co ;
Fri, 24 Jan 2014 14:12:13 -0800
References: <CAAS2fgQmsxjkQFSiCdeMoVMaqq5720KpUpdkKZOE+XytHsWw0w@mail.gmail.com>
<20140124090218.GA15398@savin>
<CANEZrP0MnXr4xjaMPg7v7vTiDQr-y7esvEBE=xk=Y0BUGXak9A@mail.gmail.com>
<20140124152617.GA31017@petertodd.org>
Mime-Version: 1.0 (1.0)
In-Reply-To: <20140124152617.GA31017@petertodd.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <9C11B575-1C43-44BB-B5C2-52F892E5A35A@taplink.co>
X-Mailer: iPhone Mail (10B146)
From: Jeremy Spilman <jeremy@taplink.co>
Date: Fri, 24 Jan 2014 13:58:28 -0800
To: Peter Todd <pete@petertodd.org>
oclient: 166.137.186.205#jeremy@taplink.co#465
X-Spam-Score: -2.2 (--)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
-0.0 SPF_PASS SPF: sender matches SPF record
-0.6 RP_MATCHES_RCVD Envelope sender domain matches handover relay
domain
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1W6olp-0000fU-O2
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Bait for reusable addresses
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Fri, 24 Jan 2014 21:58:38 -0000
>=20
>=20
>=20
> I think we need to provide users with better options than that.
>=20
Perfect privacy without extraordinary computational overhead today means dow=
nloading everything. But we could provide better tools to *shift* bandwidth r=
equirements rather than try to reduce them.=20
I've been thinking about a setup where user runs a UTXO only, and maybe even=
outbound-connect only (like bitcoinj), full node at home. Then using Tor, m=
ostly for tunneling, they host a hidden service they can connect back to fro=
m their smartphone to see balances, manage receive addresses, send funds, et=
c.
The smartphone is not doing SPV, it's like a web client for the wallet runni=
ng at home. The initial connection between the smartphone and home wallet ha=
s the phone learn two codes, one is the hidden service name, another is an a=
ccess token which is revocable. You may require further authentication from t=
hat point.=20
With fast bootstrapping / checkpointing of the UTXO I think usability could b=
e as good as SPV, and you would get push-notification of relevant transactio=
ns with zero privacy trade-off.
I wonder if people would want to run such an app, if they would run it on th=
eir desktop, a dedicated machine, or an old smartphone or other cheap ARM de=
vice.=
|
