summaryrefslogtreecommitdiff
path: root/3e/bcbbb3defbf55e6b04b526ffad71776ec27c4f
blob: 6a84d7a5165dfbb59c0365e12266434181a10951 (plain)
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
Return-Path: <ZmnSCPxj@protonmail.com>
Received: from smtp4.osuosl.org (smtp4.osuosl.org [IPv6:2605:bc80:3010::137])
 by lists.linuxfoundation.org (Postfix) with ESMTP id 0B620C002D
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sun,  1 May 2022 09:43:48 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by smtp4.osuosl.org (Postfix) with ESMTP id DA171410BE
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sun,  1 May 2022 09:43:47 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: 0.298
X-Spam-Level: 
X-Spam-Status: No, score=0.298 tagged_above=-999 required=5
 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
 DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001,
 FROM_LOCAL_NOVOWEL=0.5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001]
 autolearn=ham autolearn_force=no
Authentication-Results: smtp4.osuosl.org (amavisd-new);
 dkim=pass (2048-bit key) header.d=protonmail.com
Received: from smtp4.osuosl.org ([127.0.0.1])
 by localhost (smtp4.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id Rn2Kxo5YREDm
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sun,  1 May 2022 09:43:47 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.8.0
Received: from mail-40141.protonmail.ch (mail-40141.protonmail.ch
 [185.70.40.141])
 by smtp4.osuosl.org (Postfix) with ESMTPS id 286F1410BC
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sun,  1 May 2022 09:43:46 +0000 (UTC)
Date: Sun, 01 May 2022 09:43:39 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com;
 s=protonmail2; t=1651398224;
 bh=Hy2uEY4W0uo1PEWvMb6eV0k99sdhcqthnNtV25R8zTg=;
 h=Date:To:From:Reply-To:Subject:Message-ID:In-Reply-To:References:
 Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID:
 Message-ID;
 b=d05rNQMYZTix3jgt3TmNwtsSfG0ylhmgTY6pMzcjBMAEMp7MoGrTZ/89TR270D6br
 fpJDkEVJ8lqlLHB+6Wr2jSLJfdkdzmceQC5E9oEeNupaSLoYrbdD+dT3YAIe0Gx83M
 fyVu0rklOIF3pj+dHbFGTxANtX7xB5CLqWXpONVNPcTj7a3t80GOXE7/K95z7418Gj
 OqPXiQinrrJQz4Bi3r0t4tgYbjW91QqiUPv7UuVDg7QTHRPqUxNXOLHM7eEqPdYcID
 L+MPFjQghvfClIVdt4e7mocSjbA34y9rFLtPnxyjRhXj6avokZ8AtPFLOGTdJNHy/j
 Yc8LRNvG9PkkA==
To: Chris Belcher <belcher@riseup.net>,
 Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
From: ZmnSCPxj <ZmnSCPxj@protonmail.com>
Reply-To: ZmnSCPxj <ZmnSCPxj@protonmail.com>
Message-ID: <bsOJ-OnnA4FutVmPqtg1xY-k0notwX4OqqIpdMsymXR9-KnS2iXGUE8o7kDVeYBMCqAX0v3oEAmiVMhUIB25gupx6l_bLff2_CNsLK_sk-U=@protonmail.com>
In-Reply-To: <22c80504-e648-e021-866e-ca5a5db3b247@riseup.net>
References: <22c80504-e648-e021-866e-ca5a5db3b247@riseup.net>
Feedback-ID: 2872618:user:proton
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [bitcoin-dev] BIP proposal: Timelocked address fidelity bond
	for BIP39 seeds
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.15
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: Sun, 01 May 2022 09:43:48 -0000

Good morning Chris,

Excellent BIP!

From a quick read-over, it seems to me that the fidelity bond does not comm=
it to any particular scheme or application.
This means (as I understand it) that the same fidelity bond can be used to =
prove existence across multiple applications.
I am uncertain whether this is potentially abusable or not.


Regards,
ZmnSCPxj