public inbox for
 help / color / mirror / Atom feed
From: ProfEduStream <profedustream@gmail•com>
To: Bitcoin Development Mailing List <>
Subject: [bitcoindev] BIP 322 use case
Date: Fri, 3 May 2024 16:53:31 -0700 (PDT)	[thread overview]
Message-ID: <> (raw)

[-- Attachment #1.1: Type: text/plain, Size: 2216 bytes --]



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: &


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 

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.


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.


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

[-- Attachment #1.2: Type: text/html, Size: 10743 bytes --]

             reply	other threads:[~2024-05-03 23:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-03 23:53 ProfEduStream [this message]
2024-05-04  0:11 ` Luke Dashjr
2024-05-05 12:09   ` Ali Sherief
2024-05-05 14:50     ` Luke Dashjr
2024-05-10 17:47       ` Prof EduStream

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \
    --to=profedustream@gmail$(echo .)com \ \
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