From: Chris Belcher <belcher@riseup.net>
To: ZmnSCPxj <ZmnSCPxj@protonmail.com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP proposal: Timelocked address fidelity bond for BIP39 seeds
Date: Sun, 1 May 2022 11:01:49 +0100 [thread overview]
Message-ID: <82948428-29a3-e50a-a54a-520a83f39bba@riseup.net> (raw)
In-Reply-To: <bsOJ-OnnA4FutVmPqtg1xY-k0notwX4OqqIpdMsymXR9-KnS2iXGUE8o7kDVeYBMCqAX0v3oEAmiVMhUIB25gupx6l_bLff2_CNsLK_sk-U=@protonmail.com>
Hello ZmnSCPxj,
This is an intended feature. I'm thinking that the same fidelity bond
can be used to running a JoinMarket maker as well as a Teleport
(Coinswap) maker.
I don't believe it's abusable. It would be a problem if the same
fidelity bond is used by two makers in the _same_ application, but
JoinMarket takers are already coded to check for this, and Teleport
takers will soon as well. Using the same bond across different
applications is fine.
Best,
CB
On 01/05/2022 10:43, ZmnSCPxj wrote:
> Good morning Chris,
>
> Excellent BIP!
>
>>From a quick read-over, it seems to me that the fidelity bond does not commit 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
next prev parent reply other threads:[~2022-05-01 10:02 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 [this message]
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
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=82948428-29a3-e50a-a54a-520a83f39bba@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