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
|
Return-Path: <vv01f@c3d2.de>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 4427CBA0
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 5 Jul 2018 08:25:04 +0000 (UTC)
X-Greylist: delayed 00:06:13 by SQLgrey-1.7.6
Received: from mail.c3d2.de (c3d2-50.in-berlin.de [217.197.84.50])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id B4B16124
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 5 Jul 2018 08:25:03 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by mail.c3d2.de (Postfix) with ESMTP id 479B923F12;
Thu, 5 Jul 2018 10:18:48 +0200 (CEST)
Received: from mail.c3d2.de ([127.0.0.1])
by localhost (mail.c3d2.de [127.0.0.1]) (amavisd-new, port 10026)
with ESMTP id IRrPJSsRT6k3; Thu, 5 Jul 2018 10:18:48 +0200 (CEST)
Date: Thu, 05 Jul 2018 08:18:44 +0000
In-Reply-To: <DB6PR1001MB1302B5C6237A8A4DBE0CB6A4DE410@DB6PR1001MB1302.EURPRD10.PROD.OUTLOOK.COM>
References: <871sewirni.fsf@gmail.com>
<CAAS2fgS-_D7aBcDf_nAbuREBxv65zYMr60-1YqCnx-esvRVfEg@mail.gmail.com>,
<201807031213.51127.luke@dashjr.org>
<DB6PR1001MB1302B5C6237A8A4DBE0CB6A4DE410@DB6PR1001MB1302.EURPRD10.PROD.OUTLOOK.COM>
Mime-Version: 1.0
Content-Type: text/plain;
charset=utf-8
Content-Transfer-Encoding: quoted-printable
To: fred savage <fred_savage2003@hotmail.co.uk>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
From: vv01f <vv01f@c3d2.de>
Message-ID: <D8724D8B-59D0-4E13-B491-0BFF47FED8B9@c3d2.de>
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE
autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
X-Mailman-Approved-At: Fri, 06 Jul 2018 18:31:30 +0000
Subject: Re: [bitcoin-dev] [Lightning-dev] BIP sighash_noinput
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Jul 2018 08:25:04 -0000
You can provide a reusable payment code (BIP-47) instead of an actual addre=
ss=2E Unfortunately that not yet supported by the clients/apps most people =
use=2E Just that would be less a hurdle than providing a service that e=2Eg=
=2E generates addresses from xpub=2E
Am July 4, 2018 6:08:43 PM UTC schrieb fred savage via bitcoin-dev <bitcoi=
n-dev@lists=2Elinuxfoundation=2Eorg>:
>you cannot specifically NOT support addrss reuse=2E on a blockchain where
>people can send you funds without your permission required to send you
>funds=2E so ALWAYS expect multiple payments to the same address
--=20
Diese Nachricht wurde von meinem Android-Ger=C3=A4t mit K-9 Mail gesendet=
=2E
|
