From: jeremy <jeremy.l.rubin@gmail.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: [bitcoindev] Knowledge Gathering: SPV Proof Applications In the Wild and Proposed
Date: Thu, 14 May 2026 07:46:05 -0700 (PDT) [thread overview]
Message-ID: <a3049fd5-e001-4d3a-9c99-d5629f47dfd8n@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1281 bytes --]
Dear Bitcoin Developers,
SPV proofs are an important part of Bitcoin's Design, after all Satoshi
thought they were worth including in the whitepaper!
As far as I'm aware, they have somewhat limited usage in the wild, mainly
in Electrum and in Layer 2 Bridges, but it is important that they work
correctly.
I'd like to gather a bit more detailed information on where and how SPV
proofs are currently used, as well as any other proposed uses of SPV proofs.
In this Knowledge Gathering, I'd also like to glean a better understanding
of what types of commitment structures might work "better" than others for
SPV -- e.g., ability to cheaply verify if a block pays a particular
address, spends a particular coin, and the exclusion forms (does not pay an
address, does not spend a coin) etc, especially in the context of Layer 2
Bridging.
Happy International Chihuahua Appreciation Day,
Jeremy
--
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 visit https://groups.google.com/d/msgid/bitcoindev/a3049fd5-e001-4d3a-9c99-d5629f47dfd8n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1686 bytes --]
next reply other threads:[~2026-05-14 14:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-14 14:46 jeremy [this message]
2026-05-14 19:09 ` [bitcoindev] Re: Knowledge Gathering: SPV Proof Applications In the Wild and Proposed Ekrem BAL
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=a3049fd5-e001-4d3a-9c99-d5629f47dfd8n@googlegroups.com \
--to=jeremy.l.rubin@gmail.com \
--cc=bitcoindev@googlegroups.com \
/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