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
|
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 <pete@petertodd.org>) id 1Uzm9x-0007WX-VD
for bitcoin-development@lists.sourceforge.net;
Thu, 18 Jul 2013 11:14:09 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of petertodd.org
designates 62.13.149.78 as permitted sender)
client-ip=62.13.149.78; envelope-from=pete@petertodd.org;
helo=outmail149078.authsmtp.net;
Received: from outmail149078.authsmtp.net ([62.13.149.78])
by sog-mx-4.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
id 1Uzm9w-00034W-3k for bitcoin-development@lists.sourceforge.net;
Thu, 18 Jul 2013 11:14:09 +0000
Received: from mail-c233.authsmtp.com (mail-c233.authsmtp.com [62.13.128.233])
by punt8.authsmtp.com (8.14.2/8.14.2/Kp) with ESMTP id
r6IBE0Fp063326; Thu, 18 Jul 2013 12:14:00 +0100 (BST)
Received: from savin (76-10-178-109.dsl.teksavvy.com [76.10.178.109])
(authenticated bits=128)
by mail.authsmtp.com (8.14.2/8.14.2/) with ESMTP id r6IBDrmw004794
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO);
Thu, 18 Jul 2013 12:13:56 +0100 (BST)
Date: Thu, 18 Jul 2013 07:13:53 -0400
From: Peter Todd <pete@petertodd.org>
To: Jeremy Spilman <jeremy.spilman@gmail.com>
Message-ID: <20130718111353.GA11385@savin>
References: <CA+CODZEQX_xiaJE7WtFZC2qfVfDqZAgg-ydU5Q73O-QTkXJpPw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
protocol="application/pgp-signature"; boundary="G4iJoqBmSsgzjUCe"
Content-Disposition: inline
In-Reply-To: <CA+CODZEQX_xiaJE7WtFZC2qfVfDqZAgg-ydU5Q73O-QTkXJpPw@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Server-Quench: 2381fb56-ef9b-11e2-a49c-0025907707a1
X-AuthReport-Spam: If SPAM / abuse - report it at:
http://www.authsmtp.com/abuse
X-AuthRoute: OCd2Yg0TA1ZNQRgX IjsJECJaVQIpKltL GxAVKBZePFsRUQkR
aAdMdwoUEkAYAgsB AmUbWlZeUV57XGU7 bAxPbAVDY01GQQRq
WVdMSlVNFUsqB2Vz clxDFRlycwJPfDB3 YERmEHJYVEUsJ0N7
XxsCHD8bZGY1an1O VEkLagNUcgZDfhhC alcuVT1vNG8XDQg5
AwQ0PjZ0MThBJSBS WgQAK04nCW8NAj90 axc5VTsoBwUZV20p
IgQiI1URGUsXLi0A
X-Authentic-SMTP: 61633532353630.1021:706
X-AuthFastPath: 0 (Was 255)
X-AuthSMTP-Origin: 76.10.178.109/587
X-AuthVirus-Status: No virus detected - but ensure you scan with your own
anti-virus system.
X-Spam-Score: -1.5 (-)
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
X-Headers-End: 1Uzm9w-00034W-3k
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Anti DoS for tx replacement
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, 18 Jul 2013 11:14:10 -0000
--G4iJoqBmSsgzjUCe
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Fri, Apr 19, 2013 at 06:48:11PM -0700, Jeremy Spilman wrote:
> 0. User and AP negotiate how much to escrow, who pays the fees, and how
> far in the future nLockTime will be set (how long user=E2=80=99s funds wi=
ll be tied
> if AP doesn=E2=80=99t close the channel)
>=20
> 1. User creates an unsigned TX1 with 1 or more inputs from user=E2=80=99s
> =E2=80=98listunspent=E2=80=99, change going back to user (if any), and a =
single output of
> =E2=80=98FundAmount=E2=80=99 with scriptPubKey of =E2=80=982 PK1 OP_0 CHE=
CKMULTISIG=E2=80=99, and sends to
> the AP
Note that with OP_DEPTH we can remove the small chance of the payee
vanishing and putting the funds in limbo:
<height + n> OP_DEPTH OP_LESSTHAN
IF 2 PK1 PK2 CHECKMULTISIG
ELSE PK1 CHECKSIG
ENDIF
Though that shows how to implement OP_DEPTH as a true soft-fork we're
probably best off doing it as part of a script v2 using the soft-fork
mechanism I outlined before when talking about fidelity-bonded ledgers.
(best to do MAST (merklized abstract syntax tree) support at the same
time)
--=20
'peter'[:-1]@petertodd.org
--G4iJoqBmSsgzjUCe
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iQEcBAEBCAAGBQJR583wAAoJECSBQD2l8JH7q2AIAJGAfEAS1rnS3H/SLIxcXRaG
UtkPGyQRfAKc5qUuS+WoyPRSTRjb+F/F3broopoRBF6yhGC/EBkfq0mY/fzKB4Cd
bKX75v3VqC2u14mr6YApw8/HLrpttjxM+EiYNX7TNZDVhvQwHxwFmqHZeclVJmsM
KQO0yfw7yM16Ezq7vguqpsmZhDLGgoBknK/Afqvmr6HlmAMcGXMZYlbVaCOF68gG
fdgdC92HtTlkqYjz0pyT1BoPO2kJdAn0YZAdekA8s35t7DXyZliAyzr1+LEEsSct
3tvcw+x6/jTt8YsdYse9820g780fsnNt0BDInIc5Fd4tvsBXsq/syzytuCWEBAc=
=rOdq
-----END PGP SIGNATURE-----
--G4iJoqBmSsgzjUCe--
|
