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
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <tamas@bitsofproof.com>) id 1WYCSx-0003Ml-EE
for bitcoin-development@lists.sourceforge.net;
Thu, 10 Apr 2014 10:44:19 +0000
X-ACL-Warn:
Received: from wp059.webpack.hosteurope.de ([80.237.132.66])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
(Exim 4.76) id 1WYCSv-0005ZT-JK
for bitcoin-development@lists.sourceforge.net;
Thu, 10 Apr 2014 10:44:19 +0000
Received: from [37.143.74.116] (helo=[192.168.2.2]); authenticated
by wp059.webpack.hosteurope.de running ExIM with esmtpsa
(TLS1.0:RSA_AES_128_CBC_SHA1:16)
id 1WYCSo-0006Pm-U9; Thu, 10 Apr 2014 12:44:10 +0200
Content-Type: multipart/signed;
boundary="Apple-Mail=_E48B5024-ABCD-409E-BC99-911BB51CD00E";
protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Tamas Blummer <tamas@bitsofproof.com>
In-Reply-To: <CANEZrP3tBnikpE99bTvTshiVDpRNJE8zKM1skPua2k2E7J=gRw@mail.gmail.com>
Date: Thu, 10 Apr 2014 12:44:32 +0200
Message-Id: <3DB84423-BAEB-4290-B43C-7A3B07141844@bitsofproof.com>
References: <CA+s+GJCn9U2kmyMH6w3o+m99NCfO0ws=SccvGBYJv07WVuF=eA@mail.gmail.com>
<CAADm4BCEFCiOpNzUThPPHUamP2256izU8pwD3nerLCxks0wENA@mail.gmail.com>
<CAAS2fgTx40XSLhiygnJMrSbOC=iJ2YMVLNK7-AMt3ifvAHDZUA@mail.gmail.com>
<E9BAD633-3B6A-4A2C-AA06-DB591973DF66@bitsofproof.com>
<53456B99.9010207@monetize.io>
<B2FEC170-7214-4E46-8830-153995870B62@bitsofproof.com>
<00b77560-d7ed-4ed4-a4e5-eb1f00467a06@email.android.com>
<0509477C-89F9-47C7-8820-29ACAD4A4A8E@bitsofproof.com>
<CANEZrP2Q=TG+jejEVFFh5FhjzDDkySHNSTfwtKueLcHu=pB6Kw@mail.gmail.com>
<CA+s+GJBRvDFgktTgW2sCvAVahrjxcGqfgHw0BVNPvwUupotVrg@mail.gmail.com>
<534592E2.7040800@gmail.com>
<CAAS2fgS3q6N9go-NSKdjLwgU_5bFwa8YE88DcjNYHQTwzPCn3Q@mail.gmail.com>
<5345986C.3040901@gmail.com>
<CAAS2fgQyXHNnBDKoUMd_=-=1irGJ6cFKwi59enLJvFJiWBv50A@mail.gmail.com>
<CAJna-Hj1U5cQ22bSXoNB-4ck_urCuS9xCk+iEHsbh+yv17MP7A@mail.gmail.com>
<CANEZrP2w2b28qnYd7q=fo=VL0FzVE1R15s5Entuy+fK9x+V8Kg@mail.gmail.com>
<CA+s+GJDcGxa_ARPFAbsd54cFhgBn8WcqNrRs00TZJBrNmvq5jQ@mail.gmail.com>
<77889B25-03D6-4401-A5FE-432976951F55@bitsofproof.com>
<CANEZrP1ELraedzEpME6E8s7kXy57RKtr6667_Ke7cvhvcc9W0Q@mail.gmail.com>
<5EA7E1CA-2673-49D4-A1C4-015117E5133D@bitsofproof.com>
<CANEZrP3tBnikpE99bTvTshiVDpRNJE8zKM1skPua2k2E7J=gRw@mail.gmail.com>
To: Mike Hearn <mike@plan99.net>
X-Mailer: Apple Mail (2.1874)
X-bounce-key: webpack.hosteurope.de; tamas@bitsofproof.com; 1397126657;
3a5db896;
X-Spam-Score: 1.0 (+)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
1.0 HTML_MESSAGE BODY: HTML included in message
X-Headers-End: 1WYCSv-0005ZT-JK
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Bitcoind-in-background mode for SPV
wallets
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: Thu, 10 Apr 2014 10:44:19 -0000
--Apple-Mail=_E48B5024-ABCD-409E-BC99-911BB51CD00E
Content-Type: multipart/alternative;
boundary="Apple-Mail=_6C44A698-DEA9-4F83-A0D2-7EE12D916455"
--Apple-Mail=_6C44A698-DEA9-4F83-A0D2-7EE12D916455
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=windows-1252
Thanks, Peter and you convinced me. I run away with a thought.
It=92d be great to find a spot to deploy payment channels, but I agree =
this is not it.
Tamas Blummer
http://bitsofproof.com
On 10.04.2014, at 12:40, Mike Hearn <mike@plan99.net> wrote:
> 1) There is no catch 22 as there are plenty of ways getting bitcoin =
without bootstrapping a full node.
>=20
> I think I maybe wasn't clear. To spend coins you need transaction =
data. Today, the dominant model is that people get that data by scanning =
the block chain. If you can obtain the transaction data without doing =
that then, either:
>=20
> 1) Someone is doing chain scanning for free. See my point about "why =
pay if you can get it for free".
>=20
> 2) You got your tx data direct from the person you who sent you the =
funds, perhaps via the payment protocol. This would resolve the catch 22 =
by allowing you to spend bitcoins without actually having talked to the =
P2P network first, but we're a loooooong way from this world.
>=20
> And that's it. I don't think there are any other ways to get the tx =
data you need. Either someone gives it to you in the act of spending, or =
someone else gives it away for free, undermining the =
charge-for-the-p2p-network model.
--Apple-Mail=_6C44A698-DEA9-4F83-A0D2-7EE12D916455
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset=windows-1252
<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dwindows-1252"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space;"><div>Thanks, Peter and you convinced me. I run away =
with a thought.</div><div><br></div><div>It=92d be great to find a spot =
to deploy payment channels, but I agree this is not it.</div><br><div =
apple-content-edited=3D"true"><span style=3D"color: rgb(0, 0, 0); =
font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; text-align: -webkit-auto; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; orphans: 2; widows: 2; float: none; =
display: inline !important;">Tamas Blummer</span><br style=3D"color: =
rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; text-align: -webkit-auto; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; orphans: 2; widows: 2;"><span =
style=3D"color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant: normal; font-weight: normal; =
letter-spacing: normal; line-height: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><span =
style=3D"color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant: normal; font-weight: normal; =
letter-spacing: normal; line-height: normal; text-align: -webkit-auto; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; orphans: 2; widows: =
2; float: none; display: inline !important;"><a =
href=3D"http://bitsofproof.com">http://bitsofproof.com</a></span>
</span></div>
<br><div><div>On 10.04.2014, at 12:40, Mike Hearn <<a =
href=3D"mailto:mike@plan99.net">mike@plan99.net</a>> wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div =
dir=3D"ltr"><div class=3D"gmail_extra"><div =
class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0 =
0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div =
style=3D"word-wrap:break-word"><div>1) There is no catch 22 as there are =
plenty of ways getting bitcoin without bootstrapping a full node.</div>
</div></blockquote><div></div></div><br></div><div class=3D"gmail_extra">I=
think I maybe wasn't clear. To spend coins you need transaction data. =
Today, the dominant model is that people get that data by scanning the =
block chain. If you can obtain the transaction data without doing that =
then, either:</div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">1) =
Someone is doing chain scanning for free. See my point about "why pay if =
you can get it for free".</div><div class=3D"gmail_extra"><br></div><div =
class=3D"gmail_extra">
2) You got your tx data direct from the person you who sent you the =
funds, perhaps via the payment protocol. This would resolve the catch 22 =
by allowing you to spend bitcoins without actually having talked to the =
P2P network first, but we're a loooooong way from this world.</div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">And =
that's it. I don't think there are any other ways to get the tx data you =
need. Either someone gives it to you in the act of spending, or someone =
else gives it away for free, undermining the charge-for-the-p2p-network =
model.</div>
</div>
</blockquote></div><br></body></html>=
--Apple-Mail=_6C44A698-DEA9-4F83-A0D2-7EE12D916455--
--Apple-Mail=_E48B5024-ABCD-409E-BC99-911BB51CD00E
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename=signature.asc
Content-Type: application/pgp-signature;
name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org
iQEcBAEBAgAGBQJTRnYQAAoJEPZykcUXcTkcFqcIAMk1aNDQmWqFvMCr0IoO88Pv
aJLVLoNZM2NfahG85q1xi7NwWaVMFF5jHSJtR3tXvZF/6lwlXCU9DJROqQAeOWvT
KTG0zxjI47+J2yGyC6Tr/XuYaG/APca7ix+P3Kv5yTnuY28iloseYKykwM1O4weZ
V4qZ0KXrHTPmLIWNUJTo5Ut77zzK1f3o1tsGsYuUDBpoFXD1IQAlE94HOM6Jq9eO
No0I53Ejm1ua+FfGQTjOLt1OS/yUsJ1uvYibdT/Dt8fd6jrOms3aG8+L2KkqUCxg
kZk08h33DdfibYQ/APq7C2JBuqZgQ1VXx7XQ5iqHr5y7Q5JxH62V6v6BPIox+PU=
=Hj0A
-----END PGP SIGNATURE-----
--Apple-Mail=_E48B5024-ABCD-409E-BC99-911BB51CD00E--
|
