From: "David A. Harding" <dave@dtrt•org>
To: Tadge Dryja <rx@awsomnet•org>
Cc: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] Trivial QC signatures with clean upgrade path
Date: Tue, 31 Dec 2024 22:38:00 -1000 [thread overview]
Message-ID: <56e0005eb75e4f1720a5aabbcdb0535c@dtrt.org> (raw)
In-Reply-To: <374d6201-fb43-48df-abbc-f01ef1944a7dn@googlegroups.com>
On 2024-12-16 12:20, Tadge Dryja wrote:
> An on-chain proof of quantum computer (PoQC I guess :) ) would be a
> way to reduce the damage of activation forks. One way to build it:
> Create a NUMS point pubkey - something like described in BIP341. Send
> some coins to that address, then watch if it gets spent. [...]
> Nodes can then have code which
> watches for such a proof and changes consensus rules based on it.
I think this could be even more useful if combined with a previous idea
far creating a NUMS[1][3] (or trust minimized[2]) pubkey compatible with
Bitcoin but with a security strength less than 128 bits. That way
someone might claim the bounty of the key with (say) 96 bits security
potentially months or years before QC advances made regular keys
insecure and tempted operators of QCs into stealing from regular user
addresses.
-Dave
[1]
https://gnusha.org/pi/bitcoindev/CAH5Bsr20n2T7KRTYqycSUx0iEuEApC8NGtPCfN8rYhRyHLE4gA@mail.gmail.com/
[2]
https://gnusha.org/pi/bitcoindev/aRiFFJKz5wyHFDi2dXcGbNEHZD2nIwDRk7gaXIte-N1BoOEOQ-ySYRnk0P70S5igANSr2iqF2ZKV1dWvipaQHK4fJSv9A61-uH7w4pzxKRE=@protonmail.com/
[3]
https://gnusha.org/pi/bitcoindev/CAH5Bsr39kw08ki76aezJ1EM9e7mdLFLUmtKwJJNYcyuMpR_Cuw@mail.gmail.com/
--
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/56e0005eb75e4f1720a5aabbcdb0535c%40dtrt.org.
next prev parent reply other threads:[~2025-01-01 12:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-15 21:42 Matt Corallo
2024-12-15 23:54 ` Luke Dashjr
2024-12-16 1:30 ` Weikeng Chen
2024-12-16 1:40 ` Matt Corallo
2024-12-16 11:14 ` Anthony Towns
2024-12-16 15:57 ` Matt Corallo
2024-12-16 22:20 ` Tadge Dryja
2024-12-17 5:31 ` 'conduition' via Bitcoin Development Mailing List
2024-12-18 3:29 ` Antoine Riard
2025-01-01 8:38 ` David A. Harding [this message]
2025-01-02 0:43 ` Ian Quantum
2025-01-01 8:37 ` David A. Harding
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=56e0005eb75e4f1720a5aabbcdb0535c@dtrt.org \
--to=dave@dtrt$(echo .)org \
--cc=bitcoindev@googlegroups.com \
--cc=rx@awsomnet$(echo .)org \
/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