public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Nagaev Boris <bnagaev@gmail.com>
To: opus lux <opusluxofficial@proton.me>
Cc: "bitcoindev@googlegroups.com" <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] [BIP] P2WOTS: 64 Slot Winternitz UTXO's (witness version three)
Date: Mon, 8 Jun 2026 17:20:18 -0500	[thread overview]
Message-ID: <CAFC_Vt6x=wM61NTFyn00JntRFJPWUt8_x9yxPcrGgPfpDCo_+Q@mail.gmail.com> (raw)
In-Reply-To: <LB_O7FqGG5kTYN96-MClXIl7retn-UyDlPQbVhVOnxlMO5i-h1Oq1NDhAkaZUqx--yeNW38X8p90IulPeSDLJzhJd5UwHYvFEzc8YhVWvtU=@proton.me>

Hi Opus Lux,

Thanks for working on this!

What do you think about SHRINCS signature scheme?
https://github.com/BlockstreamResearch/shrincs-specification
https://github.com/BlockstreamResearch/shrincs-cpp/ - C++ implementation
https://delvingbitcoin.org/t/shrincs-324-byte-stateful-post-quantum-signatures-with-static-backups/2158/

It uses an asymmetric tree, saving signature size for lower indices,
putting the leaves closer to the Merkle root. Also it includes a
stateless fallback to SPHINCS+ in case a signer lost the state (the
slot counter). Also it utilizes a constant sum optimization in WOTS to
save some space on shrinking the sum digest.

Best,
Boris


On Mon, Jun 8, 2026 at 5:12 PM 'opus lux' via Bitcoin Development
Mailing List <bitcoindev@googlegroups.com> wrote:
>
> Hi all,
>
> I's like to officially propose P2WOTS (Pay-to-Winternitz-One-Time-Signature), a new native Bitcoin output type using witness version three. It provides post quantum security using only SHA-256 and contains no elliptic curve key material anywhere.
>
> The 34 byte scriptPubKey commits to a Merkle Key Tree over 64 independent WOTS+ one time key pairs.
> This construction directly solves the WOTS+ one time signing limitation, each spend consumes a fresh independent slot key, making address reuse safe without ever violating the one time property.
>
> BIP draft PR:
> https://github.com/bitcoin/bips/pull/2194
>
> Looking forward to technical feedback from the community.
>
> Regards,
> Opus Lux
>
> --
> 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/LB_O7FqGG5kTYN96-MClXIl7retn-UyDlPQbVhVOnxlMO5i-h1Oq1NDhAkaZUqx--yeNW38X8p90IulPeSDLJzhJd5UwHYvFEzc8YhVWvtU%3D%40proton.me.



-- 
Best regards,
Boris Nagaev

-- 
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/CAFC_Vt6x%3DwM61NTFyn00JntRFJPWUt8_x9yxPcrGgPfpDCo_%2BQ%40mail.gmail.com.


  reply	other threads:[~2026-06-08 22:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-08 22:07 [bitcoindev] [BIP] P2WOTS: 64 Slot Winternitz UTXO's (witness version three) 'opus lux' via Bitcoin Development Mailing List
2026-06-08 22:20 ` Nagaev Boris [this message]
2026-06-08 23:01 ` [bitcoindev] " 'opus lux' via Bitcoin Development Mailing List
2026-06-09  0:41   ` 'conduition' via Bitcoin Development Mailing List

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='CAFC_Vt6x=wM61NTFyn00JntRFJPWUt8_x9yxPcrGgPfpDCo_+Q@mail.gmail.com' \
    --to=bnagaev@gmail.com \
    --cc=bitcoindev@googlegroups.com \
    --cc=opusluxofficial@proton.me \
    /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