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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <adam.back@gmail.com>) id 1VQDRH-0001pI-Kf
for bitcoin-development@lists.sourceforge.net;
Sun, 29 Sep 2013 09:37:19 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 74.125.83.53 as permitted sender)
client-ip=74.125.83.53; envelope-from=adam.back@gmail.com;
helo=mail-ee0-f53.google.com;
Received: from mail-ee0-f53.google.com ([74.125.83.53])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1VQDRF-0002An-Oi
for bitcoin-development@lists.sourceforge.net;
Sun, 29 Sep 2013 09:37:19 +0000
Received: by mail-ee0-f53.google.com with SMTP id b15so2019619eek.26
for <bitcoin-development@lists.sourceforge.net>;
Sun, 29 Sep 2013 02:37:11 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=date:from:to:cc:subject:message-id:references:mime-version
:content-type:content-disposition:in-reply-to:user-agent;
bh=PG73tqCQqth7cMlwAvxVLpjvGCHVhDm3Mv6dsPUQiTE=;
b=P17HryW9NPLJCiz5L1DJdwDKFid3Lia7ksoSZj9iMKNFDJLQhwk1usmwtxmQZMBM9Y
F2VBjuSeR1FYm1esMNd7iPayiupmYSWi3gHq25m+bhv8BkRrsx1TWvLgQg5YVMyPNUUM
c81DpSCnSHV6Byr9JzWj1MwdC0+bbQXK6SqiXrbHlNopn3HgNZAF3jJjQLKC5FCCzVVl
pOvt+uJ9mu4Hp8A80TuL6iu8GwVcGfHrjgb+FfZjdRTGOl+JE2LTsShJUbqtJn2rg2YI
EYEOa8iYpa5wJQgqw1bG9PPZmIDSjI07DtzZGybFw2icHdVxV7C0nWaYIPHNG1V3EX4R
87Dw==
X-Received: by 10.15.98.9 with SMTP id bi9mr1035932eeb.67.1380447431366;
Sun, 29 Sep 2013 02:37:11 -0700 (PDT)
Received: from netbook (ip83-162-100-3.hotspotsvankpn.com. [83.162.100.3])
by mx.google.com with ESMTPSA id h45sm37500454eeg.5.1969.12.31.16.00.00
(version=TLSv1.1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
Sun, 29 Sep 2013 02:37:10 -0700 (PDT)
Received: by netbook (Postfix, from userid 1000)
id 727BB2E0AA9; Sun, 29 Sep 2013 11:37:10 +0200 (CEST)
Received: by flare (hashcash-sendmail, from uid 1000);
Sun, 29 Sep 2013 11:37:09 +0200
Date: Sun, 29 Sep 2013 11:37:08 +0200
From: Adam Back <adam@cypherspace.org>
To: Gavin Andresen <gavinandresen@gmail.com>
Message-ID: <20130929093708.GA16561@netbook.cypherspace.org>
References: <CAKaEYhLvqT6nkbupEEgR1d9dMP4-pA7xQbBqPDbREiDDV7c0rQ@mail.gmail.com>
<2c70dbfc173749cf4198c591f19a7d33@astutium.com>
<CAH+ZByHs00+Cpx5bwybgV3G9=CBfHaHKg7AV9ytywKNAjFVM6g@mail.gmail.com>
<CABsx9T29T+thSeF-xVk+prfeO7ZJQbX=n=tAURqEKQsVtcBpQg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Disposition: inline
In-Reply-To: <CABsx9T29T+thSeF-xVk+prfeO7ZJQbX=n=tAURqEKQsVtcBpQg@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Hashcash: 1:20:130929:gavinandresen@gmail.com::QT9kcz8TBCDWpTrV:00000000000000
0000000000000000000000000qtZ
X-Hashcash: 1:20:130929:neil@asdf.co.nz::UEknc/LTc6qBpzlD:002U9Y
X-Hashcash: 1:20:130929:bitcoin-development@lists.sourceforge.net::Cr+3SGJCrhsFn
nbA:0000000000000000000037nQ
X-Hashcash: 1:20:130929:adam@cypherspace.org::YQEOMKPX/W7yjhy7:00000000000000000
0000000000000000000000000RgM
X-Spam-Score: -1.5 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked.
See
http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
for more information. [URIs: doubleclick.net]
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(adam.back[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
0.0 T_FILL_THIS_FORM_SHORT Fill in a short form with personal
information
X-Headers-End: 1VQDRF-0002An-Oi
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] smart contracts -- possible use case? yes
or no?
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: Sun, 29 Sep 2013 09:37:19 -0000
There are some policy decision points in the protocol (and code) that may
become centralized risks or choke points that undermine the p2p nature. So
the extent that those can be argued to have in principle have a technical
fix, it could be quite interesting to research the necessary technology
(advanced crypto, byzantine networking argument etc) that could address
them. eg payee/payer blacklisting by a large group of miners and "committed
transaction" proposal to address it.
However even for that type of thing I think bitcoin-dev would probably
rather focus eg on something that has reached the stage of having a BIP. Eg
it might be better to discuss early stage or speculative ideas on
bitcointalk.org technical thread.
https://bitcointalk.org/index.php?board=6.0
taxation in particular there are examples where even the political sphere
accepts significantly anonymous taxation. eg for europeans with certain
types of investment in a swiss bank, the swiss bank sends however many
million as a single payment across all users per european country to their
passport home country (minus 25% cut for the swiss government). Perhaps
such things could be possible for bitcoin. Again I think bitcoin talk would
be a good place for such a discussion if that was the OP question
indirectly.
Adam
On Sun, Sep 29, 2013 at 06:32:10PM +1000, Gavin Andresen wrote:
> On Sun, Sep 29, 2013 at 12:28 PM, Neil Fincham <[1]neil@asdf.co.nz>
> wrote:
>
> I subscribe to this list so I can keep up-to date with bitcoin
> development, can we keep philosophy and tax evasion out of it?
>
> Yes, that's off-topic for this mailing list. Lets stick to technical
> issues that we can solve by writing code.
> --
> --
> Gavin Andresen
>
>References
>
> 1. mailto:neil@asdf.co.nz
>------------------------------------------------------------------------------
>October Webinars: Code for Performance
>Free Intel webinars can help you accelerate application performance.
>Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
>the latest Intel processors and coprocessors. See abstracts and register >
>http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk
>_______________________________________________
>Bitcoin-development mailing list
>Bitcoin-development@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/bitcoin-development
|
