From mboxrd@z Thu Jan 1 00:00:00 1970 Delivery-date: Mon, 16 Feb 2026 20:23:06 -0800 Received: from mail-oo1-f61.google.com ([209.85.161.61]) by mail.fairlystable.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1vsCc5-0006XK-Ez for bitcoindev@gnusha.org; Mon, 16 Feb 2026 20:23:06 -0800 Received: by mail-oo1-f61.google.com with SMTP id 006d021491bc7-6795b040001sf29252892eaf.0 for ; Mon, 16 Feb 2026 20:23:04 -0800 (PST) ARC-Seal: i=2; a=rsa-sha256; t=1771302179; cv=pass; d=google.com; s=arc-20240605; b=H++EbsyG2zpV5zDgpsBffWo+HdqfdVWSV9oY3ym6w0OhyuvlDHQHeg+Jn5bvQu2t11 yyXopcN2gLlNVPr7MFwIFnxmOYvBzn45OG1NeroZwwwqky+9ZpAXCcRFtoluAQQheFSD UVDvYf2XAiTFFs+foIE/Vw7fC2qPzkz1AndKzgi2MlHvz4VeCJqRm0pyqDUrBaSInMiG NQk1yNMO5+GeDXjIbjjpnVePRSXVCYQWFCs7gMW5GAXxkBQBKOOhG3kXYhdQJ4lRInv6 QdzUdyrdr6sEBzRya1Ww+RGE2idkKyeA9i8SLM3D6Eoaydb2zeQ44yVMBVh+lBzRLtfF p/Vw== ARC-Message-Signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20240605; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:reply-to:mime-version:feedback-id :references:in-reply-to:message-id:subject:cc:from:to:date :dkim-signature; bh=U7Kv/jjRK9qhgXvPhwZ7GP/xh3MaeoLvv4q9NGLlYcg=; fh=Boff9FjDvi5ooJsXCa5eDjOIlmEoIB4r3uE8C1KCVFI=; b=Rl1q0R9q6y3iOHqhl/X0qhH4dE3MV2vhS2s86Tw/zCuZjdgWp2swYQ/fR1flgIB/bU 5RZjhNbO+c7opAF3iEvhyHjydsJdflKswZG1lv5z8T5ou43W8YcJkNnEMfQJDHjE5YZd gZbNww9ruTMgwcAkQJ2RZWjy4r/OTgrujMe6XN4yynCq1NeQsFAVzP5Tjip1qVbekfIt AiD3MFIQCWRZFzwQWqZx3RP3+s8QqMZQY6cFNT++2ifEuhy3xcyCoHejwNqauIRHGNkA X55NzVRru+UIb6QOo6Kd66y3+0u5Chel+R4U9fu93vUbNTOK7kVbVHWjizbAQCG6/gdm EQTQ==; darn=gnusha.org ARC-Authentication-Results: i=2; gmr-mx.google.com; dkim=pass header.i=@proton.me header.s=z2pm4ntgjbejvo6nsgtpkxx3cm.protonmail header.b=cdhVSHzD; spf=pass (google.com: domain of conduition@proton.me designates 109.224.244.28 as permitted sender) smtp.mailfrom=conduition@proton.me; dmarc=pass (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=proton.me DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20230601; t=1771302179; x=1771906979; darn=gnusha.org; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:reply-to :x-original-authentication-results:x-original-sender:mime-version :feedback-id:references:in-reply-to:message-id:subject:cc:from:to :date:from:to:cc:subject:date:message-id:reply-to; bh=U7Kv/jjRK9qhgXvPhwZ7GP/xh3MaeoLvv4q9NGLlYcg=; b=fxyhC4PFz6F7jPU56u34k9h3cbms9Tq4xza3aZ6+WcoCtIiEHm2j9rGS1qscTdu/ua wrdb+4XfYVc+2gUng2oLswbpIH02RJ96iCHO/zW06OrIzG3Y8T3dCpv5xgqwcMOiBjYa EETYpSpXA+PMOIzeunvO/fcjbJHmCf2m42jbYG4Qq7XyiCE2woMV6r722D/G88SLJVZA 0RA6l/xdq3mObFBf7VCXCYQF5VB7mUkZf0CwTB+afZGiON7vBAWRqC7qgzqkNSa3361z py0ApwowkO4P05TdKWn43+iFdnYhdl0mAagtz79VC1vJxqj16l5ay6Z8N5S0G3/vak8c WDxw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1771302179; x=1771906979; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:reply-to :x-original-authentication-results:x-original-sender:mime-version :feedback-id:references:in-reply-to:message-id:subject:cc:from:to :date:x-beenthere:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=U7Kv/jjRK9qhgXvPhwZ7GP/xh3MaeoLvv4q9NGLlYcg=; b=okvfv9rOR6QmPGBYmAkhgwB0T7DjCUiiZUiSZSMM9LX5CRNvJxogDqDvAOC1GkW8WS oO+4NthOTGKj3PSRGSZeGDPkyYIhQo4iXvhocIAlgFvzPkgwY9nvc3DZdUo3wgumsB5w yC7I/IWc76KFTuZD2bux0B1/co17s0JqLAOykkVnAQzrF7Gxo2zCD/9duHTAtloX637N PgPxaSrGnLo2Z8uZ8OHJM7tH4VBENHTEskV7fWdRI+zGKwKpNkcNo9oxiePqUuD6Gb2P k3ro727RdA/teqSPv6FeGj2zcVEzFWbFfJ/2EJqTmuqK/PN/ir3WAFmH+WoqFrg5ghly f24Q== X-Forwarded-Encrypted: i=2; AJvYcCUMQkFbhbADUJpIl6ZWZCJ9E5P1TL2WRVB0d7a9w3whOs/FQ78sfBH19ichgBj2wO88wnomQLm6r7ZY@gnusha.org X-Gm-Message-State: AOJu0Ywa6aBM30ggxHOHPM8OeQsbByrdP9vx1MA+P7lE74Mr0syHaHlN bxJfeXjC7gKAyktM5V+5VTDepuz+fjaEjrt+v8M3k8gExZBz2WDXZJDy X-Received: by 2002:a05:6820:80f:b0:66a:84f9:1d2 with SMTP id 006d021491bc7-67767294bdbmr6591778eaf.32.1771302178880; Mon, 16 Feb 2026 20:22:58 -0800 (PST) X-BeenThere: bitcoindev@googlegroups.com; h="AV1CL+EvlYUsnaci3vtEq6e11LxCEs1Q5jAQEqCmQlK5JWXo2g==" Received: by 2002:a05:6820:1c9a:b0:662:f738:c2f0 with SMTP id 006d021491bc7-67986c18e3bls1532050eaf.0.-pod-prod-09-us; Mon, 16 Feb 2026 20:22:53 -0800 (PST) X-Forwarded-Encrypted: i=2; AJvYcCUuZ3fwPcZZV9oQwMpU7dfFjIV6WogVuBHq9p+2lqmiXoJ19Fw88zCXfs8Co/OuuBjystSdAtKBlDY9@googlegroups.com X-Received: by 2002:a05:6808:1829:b0:45c:8f03:1e19 with SMTP id 5614622812f47-4639f264cf6mr6618583b6e.55.1771302173540; Mon, 16 Feb 2026 20:22:53 -0800 (PST) Received: by 2002:a05:620a:51d8:b0:80d:5a8b:a44e with SMTP id af79cd13be357-8cb3f827295ms85a; Mon, 16 Feb 2026 20:13:51 -0800 (PST) X-Forwarded-Encrypted: i=2; AJvYcCVi1QexJCeKY5kbMeqnBicHHyjNUuKIFyijM1Aj02xncGVTUzsuNSsDSHBG2RfjvGRyhKAKgdnXNoZp@googlegroups.com X-Received: by 2002:ac8:7fc7:0:b0:501:4b10:aa9e with SMTP id d75a77b69052e-506a8270c3fmr165078041cf.13.1771301630795; Mon, 16 Feb 2026 20:13:50 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1771301630; cv=none; d=google.com; s=arc-20240605; b=j4Nug71S1DzLzed5ULYNFvNcWJXhQA780QeyeVtuDMGDIWgRvw5TtSssm/s2pimrW+ E7e/PSr8++PYnL3aj4L6CZEOD9bfSPIyCtZ/rNTUfUqIuTJBcOBJ/UAf/9PoJ0jXLjDR p7WNfXYIsVq7B67eaWyuSYdFC3BKRwwo8ND+oOwtl79hRybm5A2/9uQMzmC/hVp0hMh2 SkOFK27+S1SusNVvyyJ78Sq+MftsBl340YwES5eNj9mggUrdYgl+XPArYN8HV0QPqdhJ 4mHy4lLQzlI9bv7cEL7j53JJBzWJ357x0elO8mG0fDcYrFDcdjtpUn9AdJwiw0VetnMM zEIA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20240605; h=mime-version:feedback-id:references:in-reply-to:message-id:subject :cc:from:to:date:dkim-signature; bh=fYNqkAhXuYn7RXA2hj1U/BLWOTyzF5VlTr4pBygiQI0=; fh=efdtEjWZtjF0jo7Pit+GWbwJkTkQSbMhw0j+8ufEw84=; b=BAbBa1s+dp8oyDWysUF2qLY77pvG83t774mqJVqCI1ZLoN//V3jLioSq27+DMxPUs4 U7m+BbklZKZfoFmnYeFoR23jUzFcv8vN0y601YV8bkOCGhw0yljyZAlVVfIVxHqjEOQM ZDjIPYgqid4W0o4yHKwdTWHppAkfqNg7bMc8cvas2wck5PNbwp612yoaUIQFXz3yBZ61 75mkC+bIWAqzcKI7IPuOSsauLzb59SL4aLRS7NXhldUzmWFaCQkOMT2ykZrmVeXrUon0 0DekI4EtoeG4Qw7z1W6k7tqd6xHJfJaiOn275nDkBdV1KdA1BMsRoE6uY5XJicgFOI7e Fkbg==; dara=google.com ARC-Authentication-Results: i=1; gmr-mx.google.com; dkim=pass header.i=@proton.me header.s=z2pm4ntgjbejvo6nsgtpkxx3cm.protonmail header.b=cdhVSHzD; spf=pass (google.com: domain of conduition@proton.me designates 109.224.244.28 as permitted sender) smtp.mailfrom=conduition@proton.me; dmarc=pass (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=proton.me Received: from mail-24428.protonmail.ch (mail-24428.protonmail.ch. [109.224.244.28]) by gmr-mx.google.com with ESMTPS id d75a77b69052e-50684afc050si4796241cf.6.2026.02.16.20.13.50 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 16 Feb 2026 20:13:50 -0800 (PST) Received-SPF: pass (google.com: domain of conduition@proton.me designates 109.224.244.28 as permitted sender) client-ip=109.224.244.28; Date: Tue, 17 Feb 2026 04:13:44 +0000 To: Erik Aronesty From: "'conduition' via Bitcoin Development Mailing List" Cc: Ethan Heilman , Jonas Nick , bitcoindev@googlegroups.com Subject: Re: [bitcoindev] Algorithm Agility for Bitcoin to maintain security in the face of quantum and classic breaks in the signature algorithms Message-ID: In-Reply-To: References: Feedback-ID: 72003692:user:proton X-Pm-Message-ID: 7cc6f453bf65c634e4c378a76754e89fd6c05339 MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha512; boundary="------0c98e6ae9a424bb517377fddbc5b0871cfb9b0441de1c0f21ad653a52ec35195"; charset=utf-8 X-Original-Sender: conduition@proton.me X-Original-Authentication-Results: gmr-mx.google.com; dkim=pass header.i=@proton.me header.s=z2pm4ntgjbejvo6nsgtpkxx3cm.protonmail header.b=cdhVSHzD; spf=pass (google.com: domain of conduition@proton.me designates 109.224.244.28 as permitted sender) smtp.mailfrom=conduition@proton.me; dmarc=pass (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=proton.me X-Original-From: conduition Reply-To: conduition 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: -1.0 (-) This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --------0c98e6ae9a424bb517377fddbc5b0871cfb9b0441de1c0f21ad653a52ec35195 Content-Type: multipart/mixed;boundary=---------------------4f7adc118ee88faa149ceeb0274649be -----------------------4f7adc118ee88faa149ceeb0274649be Content-Type: multipart/alternative;boundary=---------------------ff0c1c086c9bf673a15aaadbab33e7ad -----------------------ff0c1c086c9bf673a15aaadbab33e7ad Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" Hi list, just wanted to pipe in on the subject of commit/reveal using OP_TX= HASH. I don't think it is possible. The protocol link Erik posted ( https:/= /delvingbitcoin.org/t/a-quantum-resistance-script-only-using-op-ctv-op-txha= sh-and-no-new-signatures/2168 ) seems to contradict itself. On one hand the= author says phase zero doesn't commit to final CTV templates E & T. Howeve= r it also says T & E are committed to via the P_anchor tapscript tree, whic= h must be pinned by phase 0. So unless I'm misunderstanding, this technique= seems to require a priori knowledge of template hashes T and E when creati= ng the funding address and UTXO in phase 0, so this would not be viable as = a PQ fallback spending path. Happy to be proven wrong. regards, conduition On Wednesday, February 11th, 2026 at 1:06 AM, Erik Aronesty = wrote: > >=20 > >=20 > > You'd still need BIP 360 P2MR (or P2TRD) since OP_TXHASH needs tapscrip= t, and the only available tapscript supporting output type, P2TR, isn't qua= ntum safe. >=20 >=20 > false, covenant based multistep secret-reveal spending paths don't rely o= n signatures at all >=20 > >=20 > > I'm going to assume: > > - you mean to use this commit-reveal for migrating between signature al= gorithms, not for everyday use, >=20 >=20 > it can be used if "q day" happens. otherwise ignored. >=20 > > - TXHASH is being used because you are waiting for the commitment to be= confirmed on-chain rather than lifeboat's out-of-band commitment system >=20 >=20 > it's used so you can commit to a spending constraint without committing t= o the final "as yet to be determined" quantum-safe destination: https://del= vingbitcoin.org/t/a-quantum-resistance-script-only-using-op-ctv-op-txhash-a= nd-no-new-signatures/2168 >=20 > > Once you post your commit-txn, but before it confirms, other parties ca= n post competing commit-txns that double spend your output. If one of malic= ious transactions confirm, you must now wait for a timelock to expire and t= hen try to post your transaction. >=20 >=20 > agreed. they have to spend resources to attack your private key and the o= nly thing they can do is "grief" using a timing attack with the results, ra= ther than steal outright. a massive incentive difference. >=20 > > They can block you again. Each time they burn some of you coins in fees= . Miners get the fees, so they might be incentivized to do this. Thus, we m= ust trust miners not to do this. Lifeboat doesn't have this issue since it = uses out-of-band commitments, but out-of-band commitments have their own is= sues. >=20 >=20 > each time you use the reset-path, they have to re-attack a new key. very = expensive just to grief a small amount of fees spread across all miners. so= unds like science-fiction levels of compute. >=20 > plus.... TX_HASH is simple and generally useful and there is no guarantee= that q-day will even come >=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= email to bitcoindev+unsubscribe@googlegroups.com. > To view this discussion visit https://groups.google.com/d/msgid/bitcoinde= v/CAJowKgL5okUA%3DDHSyUJfzdb6p_z5a6H_hN6NuhZo6R9ZYbJFUQ%40mail.gmail.com. --=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/= ByJc1I7sSQAMLnAzSHPi8KSSscU0qakPM2YI0qC6VBBOwzmYtQEW5NY6d80eLUCf7fmKxbdFlSu= xm4RCoT5rtKT68Khdi2xjwYIu4B5e6BQ%3D%40proton.me. -----------------------ff0c1c086c9bf673a15aaadbab33e7ad Content-Type: multipart/related;boundary=---------------------e1e160c95d1528a323840bfb430a3d24 -----------------------e1e160c95d1528a323840bfb430a3d24 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi list, just wanted to pip= e in on the subject of commit/reveal using OP_TXHASH. I don't think it is p= ossible. The protocol link Erik posted ( https://delvingbitcoin.org/t/a-quantum-resistance-script-only-using-op-ctv= -op-txhash-and-no-new-signatures/2168 ) seems to contradict itse= lf. On one hand the author says phase zero doesn't commit to final CTV temp= lates E & T. However it also says T & E are committed to via the P_= anchor tapscript tree, which must be pinned by phase 0. So unless I'm misun= derstanding, this technique seems to require a priori knowledge of template= hashes T and E when creating the funding address and UTXO in phase 0, so t= his would not be viable as a PQ fallback spending path. Happy to be proven = wrong.

<= div style=3D"font-family: Arial, sans-serif; font-size: 14px; color: rgb(0,= 0, 0); background-color: rgb(255, 255, 255);">regards,
conduition



On Wednesday, February 11th, 2026 at 1:06 AM, Erik Aronesty <eri= k@q32.com> wrote:

<= br>You'd still need=20 BIP 360 P2MR (or P2TRD) since OP_TXHASH needs tapscript, and the only avail= able tapscript supporting output type, P2TR, isn't quantum safe.
<= /blockquote>

false, covenant based multistep secret-reve= al spending paths don't rely on signatures at all

I'm going to assume= :
- you mean to use this commit-reveal for migrating between signature = algorithms, not for everyday use,

it can be used if "q day" happens. otherwise ignored.
- TXHASH is being= used because you are waiting for the commitment to be confirmed on-chain r= ather than lifeboat's out-of-band commitment system
<= div>
it's used so you can commit to a spending constraint wit= hout committing to the final "as yet to be determined" quantum-safe destina= tion: https://delvingbitcoin.org/t/a-quantum-= resistance-script-only-using-op-ctv-op-txhash-and-no-new-signatures/2168
<= div dir=3D"ltr">
Once you post your commit-txn, but before it confirms,= other parties can post competing commit-txns that double spend your output= . If one of malicious transactions confirm, you must now wait for a timeloc= k to expire and then try to post your transaction.

agreed. they have to spend resources to attack your private key a= nd the only thing they can do is "grief" using a timing attack with the res= ults, rather than steal outright. a massive incentive difference.
They can b= lock you again. Each time they burn some of you coins in fees. Miners get t= he fees, so they might be incentivized to do this. Thus, we must trust mine= rs not to do this. Lifeboat doesn't have this issue since it uses out-of-ba= nd commitments, but out-of-band commitments have their own issues.

--
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://grou= ps.google.com/d/msgid/bitcoindev/CAJowKgL5okUA%3DDHSyUJfzdb6p_z5a6H_hN6NuhZ= o6R9ZYbJFUQ%40mail.gmail.com.

--
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/bitcoindev/ByJc1I= 7sSQAMLnAzSHPi8KSSscU0qakPM2YI0qC6VBBOwzmYtQEW5NY6d80eLUCf7fmKxbdFlSuxm4RCo= T5rtKT68Khdi2xjwYIu4B5e6BQ%3D%40proton.me.
-----------------------e1e160c95d1528a323840bfb430a3d24-- -----------------------ff0c1c086c9bf673a15aaadbab33e7ad-- -----------------------4f7adc118ee88faa149ceeb0274649be Content-Type: application/pgp-keys; filename="publickey - conduition@proton.me - 0x474891AD.asc"; name="publickey - conduition@proton.me - 0x474891AD.asc" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="publickey - conduition@proton.me - 0x474891AD.asc"; name="publickey - conduition@proton.me - 0x474891AD.asc" LS0tLS1CRUdJTiBQR1AgUFVCTElDIEtFWSBCTE9DSy0tLS0tCgp4ak1FWkRub0tSWUpLd1lCQkFI YVJ3OEJBUWRBcnBZYWFjZDgwcXdocmNaQW9VbW9NSHNWS21iZWlPZUEKcFhXbk1ybFdPZkxOSzJO dmJtUjFhWFJwYjI1QWNISnZkRzl1TG0xbElEeGpiMjVrZFdsMGFXOXVRSEJ5CmIzUnZiaTV0WlQ3 Q2pBUVFGZ29BUGdXQ1pEbm9LUVFMQ1FjSUNaQjRLV3p0aFBhenhRTVZDQW9FRmdBQwpBUUlaQVFL YkF3SWVBUlloQkVkSWthMENNdHJMZGcxM2EzZ3BiTzJFOXJQRkFBQTZhQUVBM1RmNHdqSVoKYnox K0diS0h4K09WQytNUXlVdi84RStoWUpjTE5QZnA0NEFBLzNiak5OTXN4WHdJTGZEM0xManNVVWFo CitBV2JyblVjVUFqQ2R1d3hUT01LempnRVpEbm9LUklLS3dZQkJBR1hWUUVGQVFFSFFDSXYxZW5J MU5MbAo3Zm55RzlVWk1wQ3ZsdG5vc0JrTmhQUVZxT3BXL3RKSkF3RUlCOEo0QkJnV0NBQXFCWUpr T2VncENaQjQKS1d6dGhQYXp4UUtiREJZaEJFZElrYTBDTXRyTGRnMTNhM2dwYk8yRTlyUEZBQUFR TFFEL2NCR2kwUDdwCkZTTkl2N1B6OVpkeUNVQjhzTy90dWZkV3NjQkNZK2ZMYTV3QkFNK0hTL3Jp S014RGt0TkhLakRGc2EvUgpEVDFxUGNBYXZCaXc2dDZ4Ti9jRgo9Y3d5eAotLS0tLUVORCBQR1Ag UFVCTElDIEtFWSBCTE9DSy0tLS0tCg== -----------------------4f7adc118ee88faa149ceeb0274649be-- --------0c98e6ae9a424bb517377fddbc5b0871cfb9b0441de1c0f21ad653a52ec35195 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: ProtonMail wrsEARYKAG0FgmmT6ucJEHgpbO2E9rPFRRQAAAAAABwAIHNhbHRAbm90YXRp b25zLm9wZW5wZ3Bqcy5vcmcZgXsgcYrkyaZYvQ1drXuuVDE3pgOEBTJU+NY/ vQo6tRYhBEdIka0CMtrLdg13a3gpbO2E9rPFAADTbQEAqh9lZEnOLwOIUYrP jkAnQsTf0w29gb/0XGyrdm1HdikBAMakTethuFTuD3HQiVzbXkFYwRPiH1C4 0W2xFLR0XXcP =bvjk -----END PGP SIGNATURE----- --------0c98e6ae9a424bb517377fddbc5b0871cfb9b0441de1c0f21ad653a52ec35195--