From: waxwing/ AdamISZ <ekaggata@gmail•com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] On (in)ability to embed data into Schnorr
Date: Fri, 3 Oct 2025 19:39:04 -0700 (PDT) [thread overview]
Message-ID: <7b4296ca-50ed-4a8b-b853-0accff46abfbn@googlegroups.com> (raw)
In-Reply-To: <aN_OlgvB-Co1BL19@petertodd.org>
[-- Attachment #1.1: Type: text/plain, Size: 1252 bytes --]
Hi Peter,
> You can probably use timelock encryption to ensure that the leak of the
private
key only happens in the future, after the funds are recovered by the owner
in a
subsequent transaction.
Another very interesting point, there, to get around the issue of key
leakage ... albeit I don't see a usecase, maybe I'm just not imaginative
enough, very possible.
If someone wants to keep something in the utxo set "forever", it doesn't
help. If they want the property of "immediately accessible in the utxo set"
(like "deposit into some fancy system with a blob of data"; I emphasize
"deposit" because that would explain why not "just put it in the witness",
your current outputs don't support that; correct me if my reasoning is
wrong here), then I guess they don't get that, either: the data is
accessible "intermediate term" instead.
Cheers,
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/7b4296ca-50ed-4a8b-b853-0accff46abfbn%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1627 bytes --]
prev parent reply other threads:[~2025-10-04 6:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-01 14:24 waxwing/ AdamISZ
2025-10-01 22:10 ` Greg Maxwell
2025-10-01 23:11 ` Andrew Poelstra
2025-10-02 0:25 ` waxwing/ AdamISZ
2025-10-02 15:56 ` waxwing/ AdamISZ
2025-10-02 19:49 ` Greg Maxwell
2025-10-03 13:24 ` Peter Todd
2025-10-04 2:39 ` waxwing/ AdamISZ [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=7b4296ca-50ed-4a8b-b853-0accff46abfbn@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