diff options
| author | Chris Belcher <belcher@riseup.net> | 2022-05-01 11:01:49 +0100 |
|---|---|---|
| committer | bitcoindev <bitcoindev@gnusha.org> | 2022-05-01 10:02:03 +0000 |
| commit | 84ad3a1d4527ee0b6561b47beadab5a94bc0e547 (patch) | |
| tree | 79e7fb22224b6a1b2f435fb817e79bc63e4ae2d5 | |
| parent | cd5b868bb9d454ecf8353e540651311532fec214 (diff) | |
| download | pi-bitcoindev-84ad3a1d4527ee0b6561b47beadab5a94bc0e547.tar.gz pi-bitcoindev-84ad3a1d4527ee0b6561b47beadab5a94bc0e547.zip | |
Re: [bitcoin-dev] BIP proposal: Timelocked address fidelity bond for BIP39 seeds
| -rw-r--r-- | 39/2f8ebfcc0bef8bc957196c5e3c57bb51c774ea | 103 |
1 files changed, 103 insertions, 0 deletions
diff --git a/39/2f8ebfcc0bef8bc957196c5e3c57bb51c774ea b/39/2f8ebfcc0bef8bc957196c5e3c57bb51c774ea new file mode 100644 index 000000000..369f30f4a --- /dev/null +++ b/39/2f8ebfcc0bef8bc957196c5e3c57bb51c774ea @@ -0,0 +1,103 @@ +Return-Path: <belcher@riseup.net> +Received: from smtp3.osuosl.org (smtp3.osuosl.org [140.211.166.136]) + by lists.linuxfoundation.org (Postfix) with ESMTP id 62ED0C002D + for <bitcoin-dev@lists.linuxfoundation.org>; + Sun, 1 May 2022 10:02:03 +0000 (UTC) +Received: from localhost (localhost [127.0.0.1]) + by smtp3.osuosl.org (Postfix) with ESMTP id 3B53260D55 + for <bitcoin-dev@lists.linuxfoundation.org>; + Sun, 1 May 2022 10:02:03 +0000 (UTC) +X-Virus-Scanned: amavisd-new at osuosl.org +X-Spam-Flag: NO +X-Spam-Score: -2.8 +X-Spam-Level: +X-Spam-Status: No, score=-2.8 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, RCVD_IN_DNSWL_LOW=-0.7, + RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, + SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] + autolearn=ham autolearn_force=no +Authentication-Results: smtp3.osuosl.org (amavisd-new); + dkim=pass (1024-bit key) header.d=riseup.net +Received: from smtp3.osuosl.org ([127.0.0.1]) + by localhost (smtp3.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) + with ESMTP id m-NWobdU-Q-s + for <bitcoin-dev@lists.linuxfoundation.org>; + Sun, 1 May 2022 10:02:01 +0000 (UTC) +X-Greylist: domain auto-whitelisted by SQLgrey-1.8.0 +Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129]) + by smtp3.osuosl.org (Postfix) with ESMTPS id 481A160BE8 + for <bitcoin-dev@lists.linuxfoundation.org>; + Sun, 1 May 2022 10:02:01 +0000 (UTC) +Received: from fews2.riseup.net (fews2-pn.riseup.net [10.0.1.84]) + (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) + key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256 + client-signature RSA-PSS (2048 bits) client-digest SHA256) + (Client CN "mail.riseup.net", Issuer "R3" (not verified)) + by mx1.riseup.net (Postfix) with ESMTPS id 4KrhbD4vwDzDsRK; + Sun, 1 May 2022 03:02:00 -0700 (PDT) +DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; + t=1651399320; bh=ELh/K7jkYArywOCDA6Vnta2/2o0R8F1s+q579Y63cCI=; + h=Date:Subject:To:References:From:In-Reply-To:From; + b=PK5QXoNejzzVGbnto3B10oafFr5f5Udv4NIwjLSEMm119nO28X9wgRgZs1IvswmX6 + 3CoWpGIB/D/MDKoi0Piu1pT+4MPtX5O6N3FqbBZzKkg9GfdFninnJaGraJQPWuU/Oo + ULpTUusI3YD9gMnCcoTVFd26b5GpqIRnqBnIXAWc= +X-Riseup-User-ID: E78F7E8CDAF64C8CAAA0F09A50062D978766042E540862EC1EF88CD47B9E0B8E +Received: from [127.0.0.1] (localhost [127.0.0.1]) + by fews2.riseup.net (Postfix) with ESMTPSA id 4KrhbC75Rdz20Wk; + Sun, 1 May 2022 03:01:59 -0700 (PDT) +Message-ID: <82948428-29a3-e50a-a54a-520a83f39bba@riseup.net> +Date: Sun, 1 May 2022 11:01:49 +0100 +MIME-Version: 1.0 +Content-Language: en-US +To: ZmnSCPxj <ZmnSCPxj@protonmail.com>, + Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org> +References: <22c80504-e648-e021-866e-ca5a5db3b247@riseup.net> + <bsOJ-OnnA4FutVmPqtg1xY-k0notwX4OqqIpdMsymXR9-KnS2iXGUE8o7kDVeYBMCqAX0v3oEAmiVMhUIB25gupx6l_bLff2_CNsLK_sk-U=@protonmail.com> +From: Chris Belcher <belcher@riseup.net> +In-Reply-To: <bsOJ-OnnA4FutVmPqtg1xY-k0notwX4OqqIpdMsymXR9-KnS2iXGUE8o7kDVeYBMCqAX0v3oEAmiVMhUIB25gupx6l_bLff2_CNsLK_sk-U=@protonmail.com> +Content-Type: text/plain; charset=UTF-8; format=flowed +Content-Transfer-Encoding: 7bit +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 10:02:04 -0000 + +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 + |