From: "'conduition' via Bitcoin Development Mailing List" <bitcoindev@googlegroups.com>
To: Sergio Demian Lerner <sergio.d.lerner@gmail.com>
Cc: jeremy <jeremy.l.rubin@gmail.com>,
Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] Re: Knowledge Gathering: SPV Proof Applications In the Wild and Proposed
Date: Fri, 04 Sep 2026 15:18:01 +0000 [thread overview]
Message-ID: <6Zyn9YqvVDHYG5jKAif7_3P_V4elPH3YMm9qZ2Yz6Tt45dfqnTuAVzBpGo7WjRYBaaexd9YUSGzc9mvzspsUAb_HezPe8Kjye-ZR57f-qMU=@proton.me> (raw)
In-Reply-To: <CAKzdR-pSKPXjBnWJZMASDRZve5Y1ekeTo7eG_f=WV-vVn1xZPQ@mail.gmail.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 4959 bytes --]
Hey Jeremy,
Just wanted to include DropKick here. DropKick is a PQ rescue protocol that uses SPV-like proofs of block inclusion to prove that an honest user knew a secret before a quantum attacker did, i.e. a commit/reveal protocol.
Details here: https://conduition.io/bitcoin/dropkick/
and here: https://groups.google.com/g/bitcoindev/c/6SqWPfBf-p0
regards,
conduition
On Thursday, June 4th, 2026 at 10:26 PM, Sergio Demian Lerner <sergio.d.lerner@gmail.com> wrote:
> Rootstock uses SPV proofs to power its Bitcoin SPV node that runs in consensus inside the Bridge smart contract. The bridge uses SPV proofs to accept peg-ins and peg-outs change, after 100 Bitcoin confirmations.The system is decentralized: any user can submit Bitcoin headers to build the Bridge view of Bitcoin. The Bridge maintains the canonical chain and all potential forks. All forks can be extended with block headers having the right PoW.
> The codebase is based on Bitcoinj.
> The system has been running since 2018 without interruptions.
> The SPV proof verifier is protected from Merkle node type confusions (64-byte txs).
>
> Sergio
>
> On Mon, May 25, 2026 at 3:37 PM jeremy <jeremy.l.rubin@gmail.com> wrote:
>
> > I received the below as reply-one and am forwarding with permission:
> >
> > ------
> >
> >
> >
> > Hi Jeremy,
> >
> > This is a presentation I did in 2016 on SPV as "Satoshi's scaling solution".
> >
> > There are no new types of proofs, just old fashioned proofs-of-coin and proofs-of-spend. My approach was to try to envision what the whole network would need to look like.
> >
> > A common objection to SPV was that full nodes would be "overloaded", so I introduced spv-serving light nodes with different services.
> >
> > A key idea (which is not stated explicitly in the slides) is for a node to advertise interest in a set of tx hash stems for which it would provide proof services, and for which it wanted to be relayed transactions. The set would contain stems of varying lengths that could be as short as 1 hex character or as long as some max.
> >
> > Wallets would do this same registration to cause transactions to be routed to themselves. Nearly all of those stems would be randomly introduced for privacy.
> >
> > Bloom filters are mentioned as part of a transaction repeater service but that was for compatibility with existing SPV wallets of the time. The main idea was to achieve scaling and privacy by the registration scheme.
> >
> > Hope it's useful in some way!
> >
> >
> > Cheers,
> > Tom Harding
> >
> >
> >
> > On Thursday, May 14, 2026 at 10:47:59 AM UTC-4 jeremy wrote:
> >
> > > 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/9001a42f-b497-41c1-895d-3ec902f2413cn%40googlegroups.com.
>
> --
> 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/CAKzdR-pSKPXjBnWJZMASDRZve5Y1ekeTo7eG_f%3DWV-vVn1xZPQ%40mail.gmail.com.
--
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/6Zyn9YqvVDHYG5jKAif7_3P_V4elPH3YMm9qZ2Yz6Tt45dfqnTuAVzBpGo7WjRYBaaexd9YUSGzc9mvzspsUAb_HezPe8Kjye-ZR57f-qMU%3D%40proton.me.
[-- Attachment #1.1.2.1: Type: text/html, Size: 8594 bytes --]
[-- Attachment #1.2: publickey - conduition@proton.me - 0x474891AD.asc --]
[-- Type: application/pgp-keys, Size: 649 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 343 bytes --]
prev parent reply other threads:[~2026-09-04 15:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-14 14:46 [bitcoindev] Knowledge Gathering: SPV Proof Applications In the Wild and Proposed jeremy
2026-05-14 19:09 ` [bitcoindev] " Ekrem BAL
2026-05-23 2:39 ` [bitcoindev] " Olaoluwa Osuntokun
[not found] ` <9001a42f-b497-41c1-895d-3ec902f2413cn@googlegroups.com>
2026-06-05 3:52 ` [bitcoindev] " Sergio Demian Lerner
2026-09-04 15:18 ` 'conduition' via Bitcoin Development Mailing List [this message]
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='6Zyn9YqvVDHYG5jKAif7_3P_V4elPH3YMm9qZ2Yz6Tt45dfqnTuAVzBpGo7WjRYBaaexd9YUSGzc9mvzspsUAb_HezPe8Kjye-ZR57f-qMU=@proton.me' \
--to=bitcoindev@googlegroups.com \
--cc=conduition@proton.me \
--cc=jeremy.l.rubin@gmail.com \
--cc=sergio.d.lerner@gmail.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