From mboxrd@z Thu Jan 1 00:00:00 1970 Delivery-date: Fri, 03 Oct 2025 23:40:50 -0700 Received: from mail-oa1-f63.google.com ([209.85.160.63]) by mail.fairlystable.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1v4vwn-0007AW-O4 for bitcoindev@gnusha.org; Fri, 03 Oct 2025 23:40:50 -0700 Received: by mail-oa1-f63.google.com with SMTP id 586e51a60fabf-30cce8e3ceasf5328297fac.1 for ; Fri, 03 Oct 2025 23:40:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20230601; t=1759560043; x=1760164843; darn=gnusha.org; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-sender:mime-version :subject:references:in-reply-to:message-id:to:from:date:sender:from :to:cc:subject:date:message-id:reply-to; bh=EHH/iWqAyGPv2B8jrO72WdYEbxjfJS0uoW+/P0ZQDS0=; b=W9nz8CK2/G3WkViHitb3QYDKwcF/YKthu3vyRjhrYLaVxNAVywDoxnrg9quA0sGF8V zk71LPzGuuXTLCh2b1K6YbBAc+qUoTBmSeRkfMciJFgN8Hm7HK210ludTiSvC/inugYx 4rOt1kQGUAr5SYo1m+pDx2uj8qO6knD3o5KlgW9bNy/SAs0fLbK9BMo4XgOSxlReP7xR 8M0kGeg0i63l4uQrGQ1r4WLohOQOZM30OV/Yapt8KDL5lGCn6auSoLu8ke/TfOeUf5jy ZW3klaWa4Ob+NFcn/944ler0iL+8cbmGc1oApI5vJXM72PvAbmO9opPywndKMZsZfFyM eHOg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1759560043; x=1760164843; darn=gnusha.org; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-sender:mime-version :subject:references:in-reply-to:message-id:to:from:date:from:to:cc :subject:date:message-id:reply-to; bh=EHH/iWqAyGPv2B8jrO72WdYEbxjfJS0uoW+/P0ZQDS0=; b=dyLw+4/lD4K1JfJ6O6QkgyO1Ti5yu7uftGVphDkdAxSBHBrCH/M1CAJHNlhCX4IMLD Xbc1HsJhQUnK8V4VGvXeOLlfqBAlbRs1OT3CzieMfhXQPe3adhKMlLMzY/gSSZKGlF1D baS8W1I4QWNpWg6y8C3FRIj8ognNuaTju6ehyJ10zgaCJdgzSFkYKeUpK1A7ohDSfZha DB0UbETZ3NnWnG0TjlmQ/WEKp+RHdXyyjO7qo2trRriic2R5kviT6mHEx1UzmI20Rqe7 im653hraeVFTW75yNfgjxgBq3e7AOMyIYN9p8ocxvmG4DYvargTFnc6P49/4B6GbJ/Yp LOVw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1759560043; x=1760164843; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-sender:mime-version :subject:references:in-reply-to:message-id:to:from:date:x-beenthere :x-gm-message-state:sender:from:to:cc:subject:date:message-id :reply-to; bh=EHH/iWqAyGPv2B8jrO72WdYEbxjfJS0uoW+/P0ZQDS0=; b=Ce+Z0cy4eMy9YyUb59eYcsY1fQTLXJihWYP7aofD/3mYkLP//jigDC/0HaGI1JDdRN V5VJxl/Qpv9JtIw8P9f10GssNrySdVwtRxvHhTwQh1FAkK3+Qn55lH2unLnO6bJr0Ojb p6DK/VVN6a67xG5jYyBqahVDVRp6GWHNLdWki0dkgeERm9bgQkxt6M+N7Du71lcw2ioq E9U/WXOz0KjoB3Wab43e/SS5wQ2WJ/QmvhsHEm/Eb+oYj8ixYOLXgfbShuF/cRgMmVOg V7D1tPNuyK4I3qpH9qDCeKASuqxW8q1IHfuIdhaQOCdCA7d4YTd5zdPwZvfhEWBISb7z 1WIQ== Sender: bitcoindev@googlegroups.com X-Forwarded-Encrypted: i=1; AJvYcCWNCIeMVqY7P02tcmRlnwQ6mpGXeQJLVYAw6mxCmgSG6AGFmJXgJhCr+Zkjl5pNlvHQyFfynbgj5nvo@gnusha.org X-Gm-Message-State: AOJu0Yws4CSsIk6o+nklgzyTBlt+Y1cRURnhtApeGWwSgwlU5aC3xM99 BjmhMCPZn3rKSAPsfv3MVZTAZaGfozILLDYRjDZklotpcLE1YiD1Ek+x X-Google-Smtp-Source: AGHT+IHebpXI4rQcRwCXIsW40nBOiyMxTK+HXaifbp7xKe0TjwLUSl/CHmxIv5d+uh9AgX111WEknA== X-Received: by 2002:a05:6870:3907:b0:322:2712:c89d with SMTP id 586e51a60fabf-3b0f49f9761mr3120059fac.11.1759560043331; Fri, 03 Oct 2025 23:40:43 -0700 (PDT) X-BeenThere: bitcoindev@googlegroups.com; h="ARHlJd6lb71X32JDlJj8y7CEBLVD2um61koRWqrf6DRewxWNKw==" Received: by 2002:a05:6870:264:b0:344:f218:403d with SMTP id 586e51a60fabf-3abe79b33c2ls1904646fac.0.-pod-prod-03-us; Fri, 03 Oct 2025 23:40:38 -0700 (PDT) X-Received: by 2002:a05:6808:d46:b0:43f:2464:ee55 with SMTP id 5614622812f47-43fc17dbf8dmr3207776b6e.20.1759560038348; Fri, 03 Oct 2025 23:40:38 -0700 (PDT) Received: by 2002:a05:690c:ed6:b0:725:2535:e36 with SMTP id 00721157ae682-77f93fd870bms7b3; Fri, 3 Oct 2025 19:39:05 -0700 (PDT) X-Received: by 2002:a05:690c:4b88:b0:76b:1fd1:adb with SMTP id 00721157ae682-77f946766c5mr71281787b3.37.1759545544896; Fri, 03 Oct 2025 19:39:04 -0700 (PDT) Date: Fri, 3 Oct 2025 19:39:04 -0700 (PDT) From: waxwing/ AdamISZ To: Bitcoin Development Mailing List Message-Id: <7b4296ca-50ed-4a8b-b853-0accff46abfbn@googlegroups.com> In-Reply-To: References: <0f6c92cc-e922-4d9f-9fdf-69384dcc4086n@googlegroups.com> Subject: Re: [bitcoindev] On (in)ability to embed data into Schnorr MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_83546_608227345.1759545544548" X-Original-Sender: ekaggata@gmail.com Precedence: list Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com List-ID: X-Google-Group-Id: 786775582512 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , X-Spam-Score: -0.5 (/) ------=_Part_83546_608227345.1759545544548 Content-Type: multipart/alternative; boundary="----=_Part_83547_99062592.1759545544548" ------=_Part_83547_99062592.1759545544548 Content-Type: text/plain; charset="UTF-8" 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. ------=_Part_83547_99062592.1759545544548 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Peter,

> You can probably use timelock encryptio= n to ensure that the leak of the private
key only happens in the futur= e, after the funds are recovered by the owner in a
subsequent transact= ion.

Another very interesting point, there, to g= et 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 he= lp. 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 "dep= osit" 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 he= re), then I guess they don't get that, either: the data is accessible "inte= rmediate term" instead.

Cheers,
AdamISZ/wax= wing

--
You received this message because you are subscribed to the Google Groups &= quot;Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to bitcoind= ev+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoind= ev/7b4296ca-50ed-4a8b-b853-0accff46abfbn%40googlegroups.com.
------=_Part_83547_99062592.1759545544548-- ------=_Part_83546_608227345.1759545544548--