summaryrefslogtreecommitdiff
path: root/86/d352075c5e35063ec56c91bc27829d0305a05e
blob: 88125bd5e5ab6a8a88de0ed92c015a0eeaaf8875 (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
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
Return-Path: <ZmnSCPxj@protonmail.com>
Received: from smtp2.osuosl.org (smtp2.osuosl.org [140.211.166.133])
 by lists.linuxfoundation.org (Postfix) with ESMTP id 9FA18C002D
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue,  3 May 2022 05:26:59 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by smtp2.osuosl.org (Postfix) with ESMTP id 7EF124010D
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue,  3 May 2022 05:26:59 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -1.601
X-Spam-Level: 
X-Spam-Status: No, score=-1.601 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, 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: smtp2.osuosl.org (amavisd-new);
 dkim=pass (2048-bit key) header.d=protonmail.com
Received: from smtp2.osuosl.org ([127.0.0.1])
 by localhost (smtp2.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id CFjy14NS8jNn
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue,  3 May 2022 05:26:58 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.8.0
Received: from mail-40135.protonmail.ch (mail-40135.protonmail.ch
 [185.70.40.135])
 by smtp2.osuosl.org (Postfix) with ESMTPS id 4B7C340120
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue,  3 May 2022 05:26:58 +0000 (UTC)
Date: Tue, 03 May 2022 05:26:46 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com;
 s=protonmail2; t=1651555615;
 bh=NYiN/UR9enuMPBi+4I4G0N6oBcwIUPdTKaxz6IDab/U=;
 h=Date:To:From:Cc:Reply-To:Subject:Message-ID:In-Reply-To:
 References:Feedback-ID:From:To:Cc:Date:Subject:Reply-To:
 Feedback-ID:Message-ID;
 b=Tkt724r8lNHiKth9xszdXV7v2jmJVC5I+vTDl13WeUfLnZoLTqIW7FqrQezEtEL1f
 iXsuHP5nFTGxrxTidp38j/MpxS02J4B8jP3Qag2imB5/4uxhVZttK2VAeeV+cFNvVM
 Zprn1U3lpLS4i2XiHHyfL99s27S/fmjKCywUEvPl85T+XhN/lnMc5xCXGoJJUb57ZE
 nFWRtfVdvutAPR8Z9jk0hxLVi50SHt1M7A+ycMb6cHL7gPMfxerWy0lQVqe8KIJg9a
 O1L9r3vUUs7rKSxMMOrGUZ9FclQSYeroDo3fvoo7oxsoW7Pw5ss+YrDmOzJFFNxoP/
 spoJhtboR/zEg==
To: Chris Belcher <belcher@riseup.net>
From: ZmnSCPxj <ZmnSCPxj@protonmail.com>
Reply-To: ZmnSCPxj <ZmnSCPxj@protonmail.com>
Message-ID: <dff38JBEJOVZezg16f-wUv3Mcxew_4g3F4_SzE78DBW3UUi87zKh5nz17U0KWnUs1KSC6OEPZsIcxboz86M6-VgJX4cJXY4PnNLvWDRc0RE=@protonmail.com>
In-Reply-To: <4a6ef305-cf67-dce3-aed3-ab0a28aa758f@riseup.net>
References: <22c80504-e648-e021-866e-ca5a5db3b247@riseup.net>
 <bsOJ-OnnA4FutVmPqtg1xY-k0notwX4OqqIpdMsymXR9-KnS2iXGUE8o7kDVeYBMCqAX0v3oEAmiVMhUIB25gupx6l_bLff2_CNsLK_sk-U=@protonmail.com>
 <82948428-29a3-e50a-a54a-520a83f39bba@riseup.net>
 <gp_6EV3OP368tCH4wMFnprOi6AJyQyzK2vZUsm1hIbTKUmfbqh-UaZ4qW_oAAHDgMYdlqGREFgTtdfkPGyzjxdzOiu_R26_rq_phnC1kAi8=@protonmail.com>
 <4a6ef305-cf67-dce3-aed3-ab0a28aa758f@riseup.net>
Feedback-ID: 2872618:user:proton
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
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: Tue, 03 May 2022 05:26:59 -0000

Good morning Chris,

> Hello ZmnSCPxj,
>
> Renting out fidelity bonds is an interesting idea. It might happen in
> the situation where a hodler wants to generate yield but doesn't want
> the hassle of running a full node and yield generator. A big downside of
> it is that the yield generator income is random while the rent paid is a
> fixed cost, so there's a chance that the income won't cover the rent.

The fact that *renting* is at all possible suggests to me that the followin=
g situation *could* arise:

* A market of lessors arises.
* A surveillor creates multiple identities.
* Each fake identity rents separately from multiple lessors.
* Surveillor gets privacy data by paying out rent money to the lessor marke=
t.

In defiads, I and Tamas pretty much concluded that rental would happen inev=
itably.
One could say that defiads was a kind of fidelity bond system.
Our solution for defiads was to prioritize propagating advertisements (roug=
hly equivalent to the certificates in your system, I think) with larger bon=
ded values * min(bonded_time, 1 year).
However, do note that we did not intend defiads to be used for privacy-sens=
itive applications like JoinMarket/Teleport.


Regards,
ZmnSCPxj