From mboxrd@z Thu Jan 1 00:00:00 1970 Delivery-date: Mon, 06 Apr 2026 13:32:36 -0700 Received: from mail-oo1-f55.google.com ([209.85.161.55]) by mail.fairlystable.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1w9qce-0004OC-D4 for bitcoindev@gnusha.org; Mon, 06 Apr 2026 13:32:36 -0700 Received: by mail-oo1-f55.google.com with SMTP id 006d021491bc7-679c51b2d6csf9918031eaf.2 for ; Mon, 06 Apr 2026 13:32:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20251104; t=1775507550; x=1776112350; 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:message-id:to:from:date:sender:from:to:cc:subject:date :message-id:reply-to; bh=4bQcP46n06A0oSw3sWUFly8dF5HjYawVLuZ+ZYjD+fI=; b=RlleWhXivtSIArWEtbx2rSLzp1zqdjvWqgMz5CWobXXJCz4LV0KvDKP/RLbdfka6DN NE5bV5n+Q5VeRTd0rPm+nQvqCuMKWekJzg0M8ZgYIpc+gku2xItAdhnHAftdNKqnVwaL XQMC15iToxVi7fHFTOuHI3C7Fufc1VJFiP7Q1WvD0W92y0cE8SwyJwefA3y2Mjo/WbCm w7wA/kbd+e73DH+ULOW22G/aif5x+fzbYM+3wrdwVIR3fnrtjuycQYK7btCIPj4hdC0W SwM2VW0JsBB5UAj+6mP2pVNFY85ukSpM5qVpzvX7fiHt1XJfsx9NNYr90XWOP6vrN4hq Gymw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20251104; t=1775507550; x=1776112350; 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:message-id:to:from:date:from:to:cc:subject:date:message-id :reply-to; bh=4bQcP46n06A0oSw3sWUFly8dF5HjYawVLuZ+ZYjD+fI=; b=SJT0dKlQLo3nE0KELz0sj+DuKZR/GXfSQlUV/rgxmNjml5tROfykIfLVy+4YFpUB2r pjrUnDu8OCAJy7kfBA2YOv7kykBsxUwwtbTLBqK8Qn+QGJESjoItmqqdZKOfUCv/T2zt Y0R8C11tJG2Sm+9Hk6nVsT2y3BOJ6+l3J37CJ3+63ggs/AUbc2ntM3dg32GtowzsnNVO 73rGE3DtrY/V99Zuef/1EROb5syp/LO+YbMhHq8SP9QyFRgNv5gwoxSjMV31kQB1/0ve fqu/aEg8NqnczUxcVQ6dTYiVImE+6c+ZqqF4f1E3z1mykxvvy89ynx+Dz8413Rcf9mGL zEKA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1775507550; x=1776112350; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-sender:mime-version :subject:message-id:to:from:date:x-beenthere:x-gm-message-state :sender:from:to:cc:subject:date:message-id:reply-to; bh=4bQcP46n06A0oSw3sWUFly8dF5HjYawVLuZ+ZYjD+fI=; b=BPJ6vIuABsfMVTo+prnLJMG98JmT2qmiUIPgHlgjf9vKMvYkn+p2OaL6Z4sY7Wy6DG iDQhcUTOPTacv/xDUXLTR013BZxz+rqsCOmkRngo66yNw/FfciUfteZQh+hjdY5UY9K7 B3rfMyYIzn1yghON6TyTyq029zjdhL36KaDe+/pTPUk10vrDCA1vM2aY8s9iNMEk9K+C xCu/8q8k0yH+K9QrxHGAzWR6ronZTV0PlggYjIkFOm6mkJyFVoCD0l8fayiLRIIkbx33 WIkXJF2v0xAaHarDkpx5H3ospC5KfngiD7t+UXo29TaQ6grELDBa6ARo3pnboXueyk9d SUFA== Sender: bitcoindev@googlegroups.com X-Forwarded-Encrypted: i=1; AJvYcCX4F0+B8C4rQo6y918AlrkHq5fzahZaHpXCLJ1pcLtR7G7901HlrSkQnpYbDO7QKuio37O011OlPp+g@gnusha.org X-Gm-Message-State: AOJu0Ywqs9G0bIp5+wiXEXnOY0xUBxDS4lQj0vf/KSdBdc2yhdo7IAJF tBnlxrIKvS8AIhQ7Nn0x1OAqpd00L7Q9y4k/CwlIRjnotAeuE55jQ2ER X-Received: by 2002:a4a:ee0e:0:b0:685:97f6:c2a5 with SMTP id 006d021491bc7-68597f6ca47mr2947947eaf.52.1775507550233; Mon, 06 Apr 2026 13:32:30 -0700 (PDT) X-BeenThere: bitcoindev@googlegroups.com; h="AYAyTiJ+mfFF3i2A3X16yMA+HwpHhuhYp5I0fPhq62JQpi6/4w==" Received: by 2002:a05:6870:301:b0:41c:64c3:46be with SMTP id 586e51a60fabf-422ee5df2c3ls1378259fac.1.-pod-prod-07-us; Mon, 06 Apr 2026 13:32:24 -0700 (PDT) X-Received: by 2002:a05:6808:5088:b0:467:15dc:b32a with SMTP id 5614622812f47-46ef8218edcmr7227220b6e.42.1775507544147; Mon, 06 Apr 2026 13:32:24 -0700 (PDT) Received: by 2002:a05:690c:a088:10b0:79a:e1a5:fe7e with SMTP id 00721157ae682-7a252b9cfe2ms7b3; Mon, 6 Apr 2026 13:30:34 -0700 (PDT) X-Received: by 2002:a05:690c:e3cd:b0:79c:875c:c914 with SMTP id 00721157ae682-7a4d556dcb3mr145978897b3.37.1775507433820; Mon, 06 Apr 2026 13:30:33 -0700 (PDT) Date: Mon, 6 Apr 2026 13:30:33 -0700 (PDT) From: PYM To: Bitcoin Development Mailing List Message-Id: <4303fca1-81a8-4655-ac53-33f566daebc2n@googlegroups.com> Subject: [bitcoindev] A slight change proposed on Committing to quantum resistance: a slow defence for Bitcoin against a fast quantum computing attack MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_798200_2129909403.1775507433382" X-Original-Sender: pywebdesign@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_798200_2129909403.1775507433382 Content-Type: multipart/alternative; boundary="----=_Part_798201_1254642628.1775507433382" ------=_Part_798201_1254642628.1775507433382 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hello, here's a small idea to combine merkel tree with timestamped message= =20 signature to bind p2pkh adress to quantum resistant scheme so user do not= =20 need to rush to move bitcoin before qday, in a space efficient form. - *Universal P2PKH freeze* =E2=80=94 At a defined block height, all P2PKH o= utputs=20 become unspendable via classical ECDSA.=20 - *Pre-freeze claim* =E2=80=94 Before the freeze, owners sign a claim conta= ining=20 their Bitcoin address and a new post-quantum public key of their choice.=20 The claim is ECDSA-signed, proving classical ownership while quantum=20 computers don't yet exist.=20 - *Merkle-batched publication* =E2=80=94 Claims are batched into Merkle tre= es. Only=20 the 32-byte root goes on-chain via OP_RETURN. One transaction covers large= =20 amount of claims.=20 - *Post-freeze spending* =E2=80=94 To spend a frozen output, provide: the o= riginal=20 claim, a Merkle inclusion proof linking it to a pre-freeze root, and a=20 signature from the post-quantum key committed in the claim. =20 - *No claim, no spend* =E2=80=94 Any P2PKH output with no registered claim = before=20 the freeze height is permanently frozen until a future recovery mechanism= =20 is defined by the community. I do not have enough knowledge to find the ideal scheme or implementation= =20 that fulfill those requirements sadly.=20 1 - Stewart I, Ilie D, Zamyatin A, Werner S, Torshizi MF, Knottenbelt WJ.= =20 Committing to quantum resistance: a slow defence for Bitcoin against a fast= =20 quantum computing attack. R Soc Open Sci. 2018 Jun 20;5(6):180410. doi:=20 10.1098/rsos.180410. PMID: 30110420; PMCID: PMC6030263. https://pmc.ncbi.nlm.nih.gov/articles/PMC6030263/ --=20 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 e= mail to bitcoindev+unsubscribe@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/= 4303fca1-81a8-4655-ac53-33f566daebc2n%40googlegroups.com. ------=_Part_798201_1254642628.1775507433382 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hello, here's a small idea to combine merkel tree with timestamped messa= ge signature to bind p2pkh adress to quantum resistant scheme so user do no= t need to rush to move bitcoin before qday, in a space efficient form.

  • Universal P2PKH freez= e =E2=80=94 At a defined block height, all P2PKH outputs become un= spendable via classical ECDSA.
  • Pre-freeze claim =E2=80=94 Before= the freeze, owners sign a claim containing their Bitcoin address and a new= post-quantum public key of their choice. The claim is ECDSA-signed, provin= g classical ownership while quantum computers don't yet exist.
  • Merkle-batched publication =E2=80= =94 Claims are batched into Merkle trees. Only the 32-byte root goes on-cha= in via OP_RETURN. One transaction covers large amount of claims.
  • Post-freeze spending =E2=80=94 To= spend a frozen output, provide: the original claim, a Merkle inclusion pro= of linking it to a pre-freeze root, and a signature from the post-quantum k= ey committed in the claim.=C2=A0
  • No claim, no spend =E2=80=94 Any = P2PKH output with no registered claim before the freeze height is permanent= ly frozen until a future recovery mechanism is defined by the community.

    • I do not have enough knowledge to find the ideal scheme o= r implementation that fulfill those requirements sadly.=C2=A0

    1 = - Stewart I, Ilie D, Zamyatin A, Werner S, Torshizi MF, Knottenbelt WJ. Com= mitting to quantum resistance: a slow defence for Bitcoin against a fast qu= antum computing attack. R Soc Open Sci. 2018 Jun 20;5(6):180410. doi: 10.10= 98/rsos.180410. PMID: 30110420; PMCID: PMC6030263.
    https= ://pmc.ncbi.nlm.nih.gov/articles/PMC6030263/

    --
    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/4303fca1-81a8-4655-ac53-33f566daebc2n%40googlegroups.com.
    ------=_Part_798201_1254642628.1775507433382-- ------=_Part_798200_2129909403.1775507433382--