From mboxrd@z Thu Jan 1 00:00:00 1970 Delivery-date: Tue, 11 Feb 2025 16:10:24 -0800 Received: from mail-yw1-f189.google.com ([209.85.128.189]) by mail.fairlystable.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1ti0Kd-000332-Ha for bitcoindev@gnusha.org; Tue, 11 Feb 2025 16:10:24 -0800 Received: by mail-yw1-f189.google.com with SMTP id 00721157ae682-6f774360029sf4532307b3.0 for ; Tue, 11 Feb 2025 16:10:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20230601; t=1739319018; x=1739923818; 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=cnpBdJjeKDkoMcR3qEvJnjpUPL6dmAXE4ACXheilRGw=; b=ktQ2rtZnr+9IRxdcvQ03gA3AJGtI3YRjiJSKL3RmBO86tGQSVUqnK66hXnu5nNaLaF 315kbgw03cC8Tap8rPf25maVVFGUKTxVOPECiRlxBec9K/yO6Kc+qsn5LBS+bqI7ta1H b7n3oL1XFh2JheqhRpxaGaCJXmJrpbekHboaV4cNMzklf4zLCw2VWmBTvo/O9be0GeNi s313Qo6tAzIWfK1t/qe2mV1RMUKjRaNMZOlz4aXLSXyc7JpGesGCuT951IY7QWH9OHRG ht4sDdwhjnDK6bKsD21RNEUr4zeQbnFUloe2bI3F+xDRKasqvudkTEreWE431M6qfO6p t2Gg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1739319018; x=1739923818; 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=cnpBdJjeKDkoMcR3qEvJnjpUPL6dmAXE4ACXheilRGw=; b=JOE8umWXYOm2wHw7/fvNg+Ma8VeAMjMFbAf93YnQABlNBeafkbSv4drn5gTvV+7tDN S17B/SuiKP9s80V7tqStHyg3uS9X/inN6aBSDkNZ2gEFPGgO+Kywzmv5OwJuaXU2QcVp tKCkoU3bZLzQQ3eSUEfNwPRDIcq3nIS5HWCmF8Tf6tD2+uzgGZ4T0As/hoLSUhZTeMD3 E24SlRm26hEg0kAB/jenG00YFHjhyo6v82XAWPKAg3752g28a3t9PbK0wLNwHzgvWyxR OnjfyEm+Mg1+cF/CAPFDV49Pc4pWdhMtbGWXoQ6YWS1ah3CiLuspOe6YrpfcT4fdQST4 9CAA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1739319018; x=1739923818; 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=cnpBdJjeKDkoMcR3qEvJnjpUPL6dmAXE4ACXheilRGw=; b=vugxr2olZRWeowooW0DhHaIv7X5gzdJRxMBL3uB59GrvszylBMU6Ielw7tPSJ9zupS aVnmdhzylRXzLltTQ64nEHl4SzKGD9TeoDXjz2RAXje81yDlBWvjKXHH+PikFalT9a+8 3AMAq9uFKA17nSsi6LnOw4uQ9TIF3v0CX2qZp2nATBa8AIEULNvX0DDQa4tANhf7juvf tMO+8B6S/c5eAOMK+DITZXHRIsKqP5q8jnCGc5Os33m7hpApzKWvuv5KZWQC7aWfV9M5 ORuqaLp9s1F29RGQp2j6No8ZJ2bkAX4D+2XViqb3/MgExWMPWlT5mQ5MYl9fOBysd6t2 6krw== Sender: bitcoindev@googlegroups.com X-Forwarded-Encrypted: i=1; AJvYcCXAhzL8E08ZUYLilPEAOz76T9YAfCxgGCd/l3lHAb1D/HeGTfzwN5O8B1P1THEb9aRHwhBtso1J/dEA@gnusha.org X-Gm-Message-State: AOJu0YywZik0eDTJxwiMCT8g9Ce7/HSSviCpTB45D0JQXuOEQgzssz5t a+seW6F2tPu7HU50FFu5q+RoClnmw/wqYhVCyZNFMNyVoxX+elPP X-Google-Smtp-Source: AGHT+IGfyDTyZauFdLTFuVFclwLJKWDbn1cSicukq84gy1PxanH6erssJAvrlVzM5bR7x8iPWYTI4w== X-Received: by 2002:a05:6902:2182:b0:e5b:53e4:8b8c with SMTP id 3f1490d57ef6-e5d9f7a710cmr1145775276.20.1739319017624; Tue, 11 Feb 2025 16:10:17 -0800 (PST) X-BeenThere: bitcoindev@googlegroups.com; h=Adn5yVEuENmf4V72MXoSO8XUKkf8tbzTZ/r7YXmayDqx9P8+uQ== Received: by 2002:a25:3f47:0:b0:e5d:9ca6:8e6e with SMTP id 3f1490d57ef6-e5d9ca6915dls142763276.2.-pod-prod-00-us; Tue, 11 Feb 2025 16:10:14 -0800 (PST) X-Received: by 2002:a05:690c:6f92:b0:6f9:d2ce:45e2 with SMTP id 00721157ae682-6fb0c461b9cmr53401187b3.8.1739319014278; Tue, 11 Feb 2025 16:10:14 -0800 (PST) Received: by 2002:a05:690c:4448:b0:6f9:a930:a709 with SMTP id 00721157ae682-6f9b1de8b9ams7b3; Tue, 11 Feb 2025 14:36:31 -0800 (PST) X-Received: by 2002:a05:690c:7246:b0:6f9:447d:d1a2 with SMTP id 00721157ae682-6fb1f24f99dmr17804707b3.29.1739313390458; Tue, 11 Feb 2025 14:36:30 -0800 (PST) Date: Tue, 11 Feb 2025 14:36:29 -0800 (PST) From: Agustin Cruz To: Bitcoin Development Mailing List Message-Id: <08a544fa-a29b-45c2-8303-8c5bde8598e7n@googlegroups.com> Subject: [bitcoindev] Proposal for Quantum-Resistant Address Migration Protocol (QRAMP) BIP MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_67190_1688409109.1739313389947" X-Original-Sender: agustin.cruz@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_67190_1688409109.1739313389947 Content-Type: multipart/alternative; boundary="----=_Part_67191_545060614.1739313389947" ------=_Part_67191_545060614.1739313389947 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Dear Bitcoin Developers, I am writing to share my proposal for a new Bitcoin Improvement Proposal=20 (BIP) titled *Quantum-Resistant Address Migration Protocol (QRAMP)*. The=20 goal of this proposal is to safeguard Bitcoin against potential future=20 quantum attacks by enforcing a mandatory migration period for funds held in= =20 legacy Bitcoin addresses (secured by ECDSA) to quantum-resistant addresses. The proposal outlines: - *Reducing Vulnerabilities:* Transitioning funds to quantum-resistant= =20 schemes preemptively to eliminate the risk posed by quantum attacks on= =20 exposed public keys. - *Enforcing Timelines:* A hard migration deadline that forces timely=20 action, rather than relying on a gradual, voluntary migration that might= =20 leave many users at risk. - *Balancing Risks:* Weighing the non-trivial risk of funds being=20 permanently locked against the potential catastrophic impact of a quantu= m=20 attack on Bitcoin=E2=80=99s security. Additionally, the proposal addresses common criticisms such as the risk of= =20 permanent fund loss, uncertain quantum timelines, and the potential for=20 chain splits. It also details backwards compatibility measures,=20 comprehensive security considerations, an extensive suite of test cases,=20 and a reference implementation plan that includes script interpreter=20 changes, wallet software updates, and network monitoring tools. For your convenience, I have published the full proposal on my GitHub=20 repository. You can review it at the following link: Quantum-Resistant Address Migration Protocol (QRAMP) Proposal on GitHub=20 I welcome your feedback and suggestions and look forward to engaging in a= =20 constructive discussion on how best to enhance the security and resilience= =20 of the Bitcoin network in the quantum computing era. Thank you for your time and consideration. Best regards, Agustin Cruz --=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/= 08a544fa-a29b-45c2-8303-8c5bde8598e7n%40googlegroups.com. ------=_Part_67191_545060614.1739313389947 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Dear Bitcoin Developers,

I= am writing to share my proposal for a new Bitcoin Improvement Proposal (BI= P) titled=C2=A0Quantum-Resistant Address Migration Protocol (QRAMP)= . The goal of this proposal is to safeguard Bitcoin against potent= ial future quantum attacks by enforcing a mandatory migration period for fu= nds held in legacy Bitcoin addresses (secured by ECDSA) to quantum-resistan= t addresses.

The proposal outlines:

  • Reducing Vulnerabil= ities:=C2=A0Transitioning funds to quantum-resistant schemes preem= ptively to eliminate the risk posed by quantum attacks on exposed public ke= ys.
  • Enforcing Timelines:=C2=A0A hard migration deadline that forces timely action, rather than r= elying on a gradual, voluntary migration that might leave many users at ris= k.
  • Balancing Risks:= =C2=A0Weighing the non-trivial risk of funds being permanently locked again= st the potential catastrophic impact of a quantum attack on Bitcoin=E2=80= =99s security.

Additionally, the proposal a= ddresses common criticisms such as the risk of permanent fund loss, uncerta= in quantum timelines, and the potential for chain splits. It also details b= ackwards compatibility measures, comprehensive security considerations, an = extensive suite of test cases, and a reference implementation plan that inc= ludes script interpreter changes, wallet software updates, and network moni= toring tools.

For your convenience, I have publis= hed the full proposal on my GitHub repository. You can review it at the fol= lowing link:

Quantum-Resistant Address Migration Protocol = (QRAMP) Proposal on GitHub

I welcome your fee= dback and suggestions and look forward to engaging in a constructive discus= sion on how best to enhance the security and resilience of the Bitcoin netw= ork in the quantum computing era.

Thank you for y= our time and consideration.

Best regards,

Agustin Cruz

--
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/08a544fa-a29b-45c2-8303-8c5bde8598e7n%40googlegroups.com.
------=_Part_67191_545060614.1739313389947-- ------=_Part_67190_1688409109.1739313389947--