From: waxwing/ AdamISZ <ekaggata@gmail•com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: [bitcoindev] On (in)ability to embed data into Schnorr
Date: Wed, 1 Oct 2025 07:24:50 -0700 (PDT) [thread overview]
Message-ID: <0f6c92cc-e922-4d9f-9fdf-69384dcc4086n@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1548 bytes --]
Hi all,
https://github.com/AdamISZ/schnorr-unembeddability/
Here I'm analyzing whether the following statement is true: "if you can
embed data into a (P, R, s) tuple (Schnorr pubkey and signature, BIP340
style), without grinding or using a sidechannel to "inform" the reader, you
must be leaking your private key".
See the abstract for a slightly more fleshed out context.
I'm curious about the case of P, R, s published in utxos to prevent usage
of utxos as data. I think this answers in the half-affirmative: you can
only embed data by leaking the privkey so that it (can) immediately fall
out of the utxo set.
(To emphasize, this is different to the earlier observations (including by
me!) that just say it is *possible* to leak data by leaking the private
key; here I'm trying to prove that there is *no other way*).
However I still am probably in the large majority that thinks it's
appalling to imagine a sig attached to every pubkey onchain.
Either way, I found it very interesting! Perhaps others will find the
analysis valuable.
Feedback (especially of the "that's wrong/that's not meaningful" variety)
appreciated.
Regards,
AdamISZ/waxwing
--
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/0f6c92cc-e922-4d9f-9fdf-69384dcc4086n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 2061 bytes --]
next reply other threads:[~2025-10-01 19:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-01 14:24 waxwing/ AdamISZ [this message]
2025-10-01 22:10 ` Greg Maxwell
2025-10-01 23:11 ` Andrew Poelstra
2025-10-02 0:25 ` waxwing/ AdamISZ
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=0f6c92cc-e922-4d9f-9fdf-69384dcc4086n@googlegroups.com \
--to=ekaggata@gmail$(echo .)com \
--cc=bitcoindev@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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