Delivery-date: Fri, 03 May 2024 16:55:12 -0700 Received: from mail-yb1-f190.google.com ([209.85.219.190]) by mail.fairlystable.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1s32kB-0007sb-VJ for bitcoindev@gnusha.org; Fri, 03 May 2024 16:55:12 -0700 Received: by mail-yb1-f190.google.com with SMTP id 3f1490d57ef6-de604d35ec0sf430552276.3 for ; Fri, 03 May 2024 16:55:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20230601; t=1714780506; x=1715385306; darn=gnusha.org; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-sender:mime-version :subject:message-id:to:from:date:sender:from:to:cc:subject:date :message-id:reply-to; bh=6KXCccm+DT3WYPts+5uF8fITy6CLyAjnKjn+9iyseMw=; b=PpSLgTuebzmtvjIIDhF7xcToS7RpmHRKtd5c7FGtYz7kj8azdvRnywzzNeHuKobMwY 7dLxYKFjRDiAZ9lNe/BT7GhcFpI2io9NwXvNj1Cbpk1hBH6GUc1Mt9TIvlNa2v/D1iKs oGeLIqVlk1KdzOHcQP5biiTLk0ueJwQ116uVQSR0bXBCBNYUHUQEFB28F2mdgPKH+d0Y yhS8Zjyuf8KIDpCOQTbeQl7LaUMMGNyu/S+t2Oq3EXd5NNL3pgUnY4/TSV2O3RmckDCK gurIM4iHOEJ30ZftsmZUMbwAr0amZR1xBJvwi/n+Rz2YibriC4ZTYWKkDZogHSWmrxXi ZkkA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1714780506; x=1715385306; darn=gnusha.org; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-sender:mime-version :subject:message-id:to:from:date:from:to:cc:subject:date:message-id :reply-to; bh=6KXCccm+DT3WYPts+5uF8fITy6CLyAjnKjn+9iyseMw=; b=Zp/N7wbiXQlbkbbGHspKxqmD3s3YvfQVzVtUem/mDjExBamJnQG5Y2gaHRCVVS8a82 ILoGZzyeNUd91yyanrW/rNTxODKiSuxSH6SdX2s2pwPCQzbU2r+eLJQQgpzgscR6b63O YmPREUkAjrQg/vST5Kti8Rdj2LVVXBHCpOLQMddqEp4KIl87TKZ+UgU6VMI6UWincL48 bg13cPvOeOhaXPTpr+VbbZAMc6BVUiwgpKNo8QgjKH4LmkvUjcJTECUfzKurbHl1Aqki +A16tJiIdNhVqPNRPRPtp0n/2ANNaZNRuXIG8zjd0xXZiVeuDrsdtfZIXYHTOaniOlsh 04+A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1714780506; x=1715385306; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-sender:mime-version :subject:message-id:to:from:date:x-beenthere:x-gm-message-state :sender:from:to:cc:subject:date:message-id:reply-to; bh=6KXCccm+DT3WYPts+5uF8fITy6CLyAjnKjn+9iyseMw=; b=MhhpXgFkOrADtuUTNGu/ZF5COwYR1rYxXA4KQy6xVsOZrhcZqpNNy+WAY7QnRHqPdn sO+rTYL4QXgIThp8zGl8YBh7Ul9zLOd68VfthLhFzBLUU33Fg6Peq9G+mqR07NtF8djn 1txPdDTtErZxkf8YuGamN+vVWb/TxEOq5NGUdFBVBct+5ZJR9qxf8tCzaqDDMQ1WtptD Qe7C+IKZGUdoFbzWOqB2otR8lo6vtoes/xlKRvEGw+gywDEeXtDV1pBDIg0S64Z5b0cx /Ql570YDgAoQZYsWwsB/ANVv+Djihl7+X1dafTybLFHscFSBbx9h3mXApHKvyUAS6BcV UvlQ== Sender: bitcoindev@googlegroups.com X-Forwarded-Encrypted: i=1; AJvYcCWKuZY/jC6xfz3bw0OUJ/yD+vFf7jYk/dYbHIGPtj4wmR7gatoro+G3UuGkE9n6KCpJp0ewa9VxvOJc8HbmvSA5ZN5ASqo= X-Gm-Message-State: AOJu0YyF7Tz2TSA0vSjD+1oDSEB9H4vnI7bDYY4PXp4zY65JH2J3Nble CLkE5VmjWCE0ibeVWIm1hPRn2bl7yCMs5QeQgSLft6rULx2nBvFW X-Google-Smtp-Source: AGHT+IFjdmSYIEtqMknMb4uvqIFDOB0Df/MGUZAUHXBhOhw+Hw41JRefF1DNTMSv/Mm7Ejn/5QAmwQ== X-Received: by 2002:a25:aa49:0:b0:de5:558c:e9b9 with SMTP id s67-20020a25aa49000000b00de5558ce9b9mr4544337ybi.11.1714780505803; Fri, 03 May 2024 16:55:05 -0700 (PDT) X-BeenThere: bitcoindev@googlegroups.com Received: by 2002:a25:ab67:0:b0:de5:ae90:1e0d with SMTP id 3f1490d57ef6-de8b54abab0ls647526276.1.-pod-prod-09-us; Fri, 03 May 2024 16:55:04 -0700 (PDT) X-Received: by 2002:a0d:e614:0:b0:61d:4701:5e66 with SMTP id p20-20020a0de614000000b0061d47015e66mr997564ywe.2.1714780504108; Fri, 03 May 2024 16:55:04 -0700 (PDT) Received: by 2002:a05:690c:fd1:b0:611:9f18:9d1 with SMTP id 00721157ae682-6201f57ad17ms7b3; Fri, 3 May 2024 16:53:32 -0700 (PDT) X-Received: by 2002:a05:6902:709:b0:dd9:1702:4837 with SMTP id k9-20020a056902070900b00dd917024837mr1298780ybt.3.1714780411454; Fri, 03 May 2024 16:53:31 -0700 (PDT) Date: Fri, 3 May 2024 16:53:31 -0700 (PDT) From: ProfEduStream To: Bitcoin Development Mailing List Message-Id: <9004c5d4-6b9d-4ac1-834c-902ba4901e05n@googlegroups.com> Subject: [bitcoindev] BIP 322 use case MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_92478_235978478.1714780411045" X-Original-Sender: profedustream@gmail.com Precedence: list Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com List-ID: X-Google-Group-Id: 786775582512 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , X-Spam-Score: -0.5 (/) ------=_Part_92478_235978478.1714780411045 Content-Type: multipart/alternative; boundary="----=_Part_92479_1744345166.1714780411045" ------=_Part_92479_1744345166.1714780411045 Content-Type: text/plain; charset="UTF-8" Hey, As a Bitcoin association, we're currently facing an issue because we're unable to sign an address with our multi-sig wallet. After conducting some research, I came across BIP322 in these threads: https://bitcointalk.org/index.php?topic=5408898.0 & https://github.com/bitcoin/bips/pull/1347 *Explanation*: As a Bitcoin association, we offer membership to everyone for a few thousand sats per year. To facilitate this process, we utilize "Swiss Bitcoin Pay". It's an application that allows us to easily manage our accounting. Additionally, we onboard merchants with this app because of its user-friendly interface and self-custodial capabilities, making it very convenient. The accounting features are also highly beneficial. To utilize this application in a self-custodial manner, users need to paste a Bitcoin address on the "Swiss Bitcoin Pay" dashboard and then sign a message with this address. This serves as a "Proof-of-Ownership" and is a legal requirement in some regulated countries. "Swiss Bitcoin Pay" is not the only application that requires signing a message as a "Proof-of-Ownership". Peach, a non-KYC P2P Bitcoin application, is another example. Given our goal to decentralize our treasury, we naturally opt for a multi-sig wallet, similar to many companies. However, as you know, BIP 322 hasn't been pushed and it's currently impossible to sign a message with a multi-sig wallet. *Conclusion*: I'm unsure why BIP322 hasn't been pushed or addressed in the past few months/years, but I want to highlight its necessity. Additionally, I hope that this comment sheds light on a deficiency in our Bitcoin ecosystem, and I trust that further improvements will be made to enable people to sign a message with a multi-sig wallet. I'm available to assist if needed. @ProfEduStream -- You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group. To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/bitcoindev/9004c5d4-6b9d-4ac1-834c-902ba4901e05n%40googlegroups.com. ------=_Part_92479_1744345166.1714780411045 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Hey,

As a= Bitcoin association, we're currently facing an issue because we're unable = to sign an address with our multi-sig wallet.
After conducting some research, I came across BIP322 in these thr= eads: https://bitcointalk.org/index.php?topic=3D5408898.0 & https://github.com/bitcoin= /bips/pull/1347

Explanation:

As a Bitcoin association, w= e offer membership to everyone for a few thousand sats per year. To facilit= ate this process, we utilize "Swiss Bitcoin Pay". It's an application that = allows us to easily manage our accounting. Additionally, we onboard merchan= ts with this app because of its user-friendly interface and self-custodial = capabilities, making it very convenient. The accounting features are also h= ighly beneficial.

To utilize this application in a self-custodial manner, user= s need to paste a Bitcoin address on the "Swiss Bitcoin Pay" dashboard and = then sign a message with this address. This serves as a "Proof-of-Ownership= " and is a legal requirement in some regulated countries. "Swiss Bitcoin Pa= y" is not the only application that requires signing a message as a "Proof-= of-Ownership". Peach, a non-KYC P2P Bitcoin application, is another example= .

G= iven our goal to decentralize our treasury, we naturally opt for a multi-si= g wallet, similar to many companies. However, as you know, BIP 322 hasn't b= een pushed and it's currently impossible to sign a message with a multi-sig= wallet.


Conclusion:

I'm unsure why BIP322 hasn't been pushed or addre= ssed in the past few months/years, but I want to highlight its necessity.Additionally, I hope that this commen= t sheds light on a deficiency in our Bitcoin ecosystem, and I trust that fu= rther improvements will be made to enable people to sign a message with a m= ulti-sig wallet.


I'm available to assist if needed.

@ProfEd= uStream

--
You received this message because you are subscribed to the Google Groups &= quot;Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to bitcoind= ev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msg= id/bitcoindev/9004c5d4-6b9d-4ac1-834c-902ba4901e05n%40googlegroups.com.=
------=_Part_92479_1744345166.1714780411045-- ------=_Part_92478_235978478.1714780411045--