From: Chris Belcher <belcher@riseup.net>
To: ZmnSCPxj <ZmnSCPxj@protonmail.com>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP proposal: Timelocked address fidelity bond for BIP39 seeds
Date: Tue, 3 May 2022 19:03:12 +0100 [thread overview]
Message-ID: <f3892570-6c45-47ee-2804-9988ff18bdf5@riseup.net> (raw)
In-Reply-To: <dff38JBEJOVZezg16f-wUv3Mcxew_4g3F4_SzE78DBW3UUi87zKh5nz17U0KWnUs1KSC6OEPZsIcxboz86M6-VgJX4cJXY4PnNLvWDRc0RE=@protonmail.com>
Hello ZmnSCPxj,
Such a system will have to be publicly advertised, in the same way we
see centralized cryptocurrency staking shops buying ads all over the
place. That's how they'll make retail hodlers aware that renting out
your coins in this way is possible. If JoinMarket/Teleport users notice
such ads appearing then we could change the taker code to remove the
intermediate certificate keypair, and have the fidelity bond UTXO key
sign the endpoint (IRC nickname or onion hostname) directly. This
removes the possibility of fidelity bonds in cold storage. It would have
to be done for privacy, and it wouldn't be too bad. Right now there's no
cold storage solution for fidelity bonds yet JoinMarket has about 600
bitcoins locked up and advertised, which must be all on hot wallets.
Best,
CB
On 03/05/2022 06:26, ZmnSCPxj wrote:
> 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 following 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 market.
>
> In defiads, I and Tamas pretty much concluded that rental would happen inevitably.
> One could say that defiads was a kind of fidelity bond system.
> Our solution for defiads was to prioritize propagating advertisements (roughly equivalent to the certificates in your system, I think) with larger bonded values * min(bonded_time, 1 year).
> However, do note that we did not intend defiads to be used for privacy-sensitive applications like JoinMarket/Teleport.
>
>
> Regards,
> ZmnSCPxj
next prev parent reply other threads:[~2022-05-03 18:03 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-01 8:57 [bitcoin-dev] BIP proposal: Timelocked address fidelity bond for BIP39 seeds Chris Belcher
2022-05-01 9:43 ` ZmnSCPxj
2022-05-01 10:01 ` Chris Belcher
2022-05-01 11:41 ` ZmnSCPxj
2022-05-02 9:23 ` Chris Belcher
2022-05-03 5:26 ` ZmnSCPxj
2022-05-03 18:03 ` Chris Belcher [this message]
2022-05-03 18:26 ` Eric Voskuil
2022-05-04 2:37 ` ZmnSCPxj
2022-05-04 4:04 ` eric
2022-05-04 4:19 ` ZmnSCPxj
[not found] ` <01c401d86a5c$956ddbd0$c0499370$@voskuil.org>
2022-05-18 3:06 ` eric
2022-05-18 6:29 ` ZmnSCPxj
2022-05-21 21:36 ` AdamISZ
2022-05-10 12:31 ` AdamISZ
2022-05-10 16:54 ` ZmnSCPxj
2022-05-10 19:03 ` AdamISZ
2022-05-10 19:28 ` AdamISZ
2022-05-13 10:02 ` Chris Belcher
2022-05-13 12:44 ` ZmnSCPxj
2022-05-15 9:13 ` Chris Belcher
2022-05-16 0:00 ` ZmnSCPxj
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f3892570-6c45-47ee-2804-9988ff18bdf5@riseup.net \
--to=belcher@riseup.net \
--cc=ZmnSCPxj@protonmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox