Hi Leo,<br /><br />I think it is possible to provide privacy for Satoshi and also reduce the size of a weak announcement (strong announcements can already be small: just a txid or a Merkle root of many txids).<br /><div><br /></div><div>Importantly, we cannot include the whole signed transaction in the weak announcement. Doing so would leak the EC public key immediately, allowing an attacker to create their own valid weak announcement. We must avoid revealing the public key until the actual spending transaction is broadcast.</div><div><br /></div>We need a scheme where the EC public key is not leaked in a weak announcement, but the legitimate owner can verify it, while no one else can. Also, once the EC public key is revealed, anyone should be able to verify a past weak announcement (to validate the transaction when it is broadcast). This reduces to the following requirement: we need a proof of knowledge of the EC public key that can be verified if the public key is known and provides no information otherwise.<br /><br />I think this is called a zero-knowledge proof. One simple approach could be to apply a tagged hash function to the concatenation of the EC public key and the future wTXID, and include this in the weak announcement. The structure would be:<br /><ul><li>    UTXO (previous TXID and output index)</li><li>    future spending wTXID</li><li>    proof := tagged_hash(EC public key || wTXID)</li></ul>The wTXID is included in the concatenation to bind the proof to a particular future transaction. Otherwise, someone could copy a weak announcement and substitute their own wTXID.<br /><br />Satoshi could publish a strong announcement now and then monitor all weak announcements involving his UTXOs. If someone publishes a weak announcement for one of his coins, he could verify the "proof" field. If it is valid, it would mean someone has cracked his key with a quantum computer, and he would need to use his strong announcement immediately to reclaim the funds before the attacker does.<br /><br />Best,<br />Boris<br /><br /><div><div dir="auto">On Wednesday, June 4, 2025 at 2:40:53 PM UTC-3 Leo Wandersleb wrote:<br /></div><blockquote style="margin: 0px 0px 0px 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Hi Boris,<div><br /></div><div>the announcements, weak and strong would have to not be transactions yet to be compatible with legacy nodes and thus keep it a soft-fork. They could be OP_RETURN data. Only after the 144 blocks, the upgraded full nodes would allow the inclusion of the actual transaction. This would mean the transaction would be both in full in the OP_RETURN strong announcement and without the witness part later, so it would be a bit expensive this way but maybe we can do better?</div><div><br /></div><div>A node that gets updated would have to re-index all the blockchain to find announcements if we don't introduce a time frame for actually using the announcements. We could also say that any announcement has to be used within another 1000 blocks. Then the upgrading node would have to re-index the last 1000 blocks.</div><div><br /></div><div>The legitimate owner of a UTXO might wait for an attack for privacy reasons. My proposal would allow Satoshi himself to make all his UTXOs quantum safe without any of us learning about him being active. He could add one 64B OP_RETURN in 2027 and when QC becomes an issue, we would learn about him having been active in 2027 in 2040 when actually somebody tried to attack and not in 2027 when people started to panic because of imminent quantum breakthroughs.</div><div>Hmm ... a problem is the weak announcement doesn't require keys, so anybody could provoke Satoshi to come forward. Maybe we have to add key ownership as a requirement for the "weak" announcement, too. So it should also contain a serialized transaction.<br /></div><div><br /></div><div>Best,</div><div><br /></div><div>Leo</div><div><br /></div><div><div dir="auto">On Wednesday, 4 June 2025 at 04:15:59 UTC+2 Nagaev Boris wrote:<br /></div><blockquote style="margin: 0px 0px 0px 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Hi Leo,
<br />
<br />Thanks for the clarifications, much appreciated!
<br />I have a couple of questions:
<br />
<br />1. How is a weak announcement stored in the blockchain and in the UTXO set?
<br />I assume it must be a transaction, correct? And it should somehow mark
<br />the UTXO as planned to be spent for 144 blocks?
<br />How would older (non-upgraded) nodes interpret a transaction
<br />containing a weak announcement? Would they just skip over it without
<br />any special processing?
<br />If so, is there a problem for nodes that upgrade after the fork: would
<br />they have to reprocess all blocks since the fork to find and index all
<br />missed weak announcements?
<br />
<br />2. In the case of reclaiming a UTXO after a weak announcement by an
<br />attacker: why would the legitimate owner wait for a weak announcement
<br />at all?
<br />If the EC public key was already leaked, it seems they should publish
<br />a strong announcement themselves rather than wait. If the EC public
<br />key wasn't leaked, there's nothing to worry about even if someone
<br />publishes a weak announcement: they are most likely bluffing, since
<br />they wouldn't have the actual public key.
<br />
<br />Best,
<br />Boris
<br />
<br />On Tue, Jun 3, 2025 at 3:29 PM Leo Wandersleb &lt;<a rel="nofollow">lwand...@gmail.com</a>&gt; wrote:
<br />&gt;
<br />&gt; Hi conduition,
<br />&gt;
<br />&gt; Thanks for your careful analysis - excellent catches.
<br />&gt;
<br />&gt; You're absolutely right about the txid vulnerability. The commitment must be to the complete transaction including witness data (wTXID or equivalent) to prevent an attacker from pre-committing to unsigned transactions. This is essential - otherwise an attacker could indeed enumerate the UTXO set and create commitments without knowing the private keys.
<br />&gt;
<br />&gt; Regarding updates: You're correct that frequent updates would be needed as wallets receive new UTXOs. However, I don't see this as a major issue - users could batch their commitments periodically (say, monthly) rather than after every transaction. The scheme is particularly important for existing UTXOs that already have exposed pubkeys (old P2PK, reused addresses, etc.). For new UTXOs, wallets should ideally migrate to quantum-safe addresses once available. OpenTimestamps aggregation would indeed help with scaling and provide plausible deniability about the number of UTXOs being protected.
<br />&gt;
<br />&gt; The time delay serves a different purpose than you might expect. It's not about preventing commitment forgery after pubkey exposure, but rather about allowing priority based on commitment age when multiple parties claim the same UTXO:
<br />&gt;
<br />&gt; 1. Weak announcement starts the 144-block window
<br />&gt; 2. During this window, anyone with a strong commitment can reveal it
<br />&gt; 3. The oldest valid commitment wins
<br />&gt;
<br />&gt; This creates the "poison pill" effect: an attacker might crack a key and try to spend a UTXO, but if the original owner has an older commitment, they can reclaim it during the window. The uncertainty about which UTXOs have poison pills makes attacking large "lost" UTXOs risky - hence less disruptive to the network.
<br />&gt;
<br />&gt; The delay essentially allows a "commitment priority contest" where age determines the winner, protecting users who prepared early while still allowing these users to not move their funds.
<br />&gt;
<br />&gt; Best,
<br />&gt;
<br />&gt; Leo
<br />&gt;
<br />&gt; --
<br />&gt; You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group.
<br />&gt; To unsubscribe from this group and stop receiving emails from it, send an email to <a rel="nofollow">bitcoindev+...@googlegroups.com</a>.
<br />&gt; To view this discussion visit <a href="https://groups.google.com/d/msgid/bitcoindev/5e393f57-ac87-40fd-93ef-e1006accdb55n%40googlegroups.com" rel="nofollow" target="_blank">https://groups.google.com/d/msgid/bitcoindev/5e393f57-ac87-40fd-93ef-e1006accdb55n%40googlegroups.com</a>.
<br />
<br />
<br />
<br />-- 
<br />Best regards,
<br />Boris Nagaev
<br /></blockquote></div></blockquote></div>

<p></p>

-- <br />
You received this message because you are subscribed to the Google Groups &quot;Bitcoin Development Mailing List&quot; group.<br />
To unsubscribe from this group and stop receiving emails from it, send an email to <a href="mailto:bitcoindev+unsubscribe@googlegroups.com">bitcoindev+unsubscribe@googlegroups.com</a>.<br />
To view this discussion visit <a href="https://groups.google.com/d/msgid/bitcoindev/44b5aa4c-a71b-49ed-beee-071140b16aacn%40googlegroups.com?utm_medium=email&utm_source=footer">https://groups.google.com/d/msgid/bitcoindev/44b5aa4c-a71b-49ed-beee-071140b16aacn%40googlegroups.com</a>.<br />