From mboxrd@z Thu Jan 1 00:00:00 1970 Delivery-date: Sat, 18 Jul 2026 11:50:42 -0700 Received: from mail-oa1-f64.google.com ([209.85.160.64]) by mail.fairlystable.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1wlA7V-0006EK-JB for bitcoindev@gnusha.org; Sat, 18 Jul 2026 11:50:42 -0700 Received: by mail-oa1-f64.google.com with SMTP id 586e51a60fabf-451d80641efsf9274652fac.2 for ; Sat, 18 Jul 2026 11:50:41 -0700 (PDT) ARC-Seal: i=2; a=rsa-sha256; t=1784400635; cv=pass; d=google.com; s=arc-20260327; b=T3zJRPLYvwOHJr7LeKOeVnm4EQ6qb9xGs/HSaPSOZtsVYWP5k6s+X3JkV0hpVxQIl1 ysH6d5q0weRrxPrYe2Bt6WfelE/oulW81epJfdO7BsrV9fm6DVXAB6TyjX2j/oJwBLGg QIVhpj8vBoFD7hxNI1D0oCPlxMam9ssevAiNCMnh229gjF9HyqmpvXFsdJVbkdw/wVDu T6uiRI8PsBDSQ5Yu9OZnHS/kzq5pIifNOCtntg4BG1W7rcHed99Z79f3Rhd526I7kREw GrwTNApKtyvUNHO0IlA+ZeARNG+fDvT+yokRjPoUUvLjgqmY1ZHWjRSeq+sVedSHS8HI 4F8g== ARC-Message-Signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20260327; 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=VfXYE9N6t1P/pM+FdjUK+CKa1fioH4/pIPttwka0yxs=; fh=0Ar+pE2zbqULbs+GVcP8liL73XkEO+TJHRYZbKTv9i0=; b=DOnUGkFrMM0c6xVstiPZ+ulrriQHK4g8U1nNfXh+11jut8hBaCWmoPy/nVVoZpEw7M MeHFe3LWjOz2Z3jXNdjEOsjiu2IcPztRFZyxHd6fNKf9ndFiEh4kOucVoOlHhTpEd+CP 2PCbHspkljXyZrgXqs1gRC0HvOWyaOCROqfTPWsmkyp3UFQlRszD8sGFH75y1BmQe6Zu +de10KMWzuU9wRb91KCgGoAGPCy0w8feyGLsGoh4nWZIMX90SqJEH0uvCJ5bpB84VAkI IdsJoGiWXVdWQjt1KhiphoRRqR242Y3fC/89O44OgDf92e3EF6Wwb6U15JlTQD+FN6WO eSKw==; darn=gnusha.org ARC-Authentication-Results: i=2; gmr-mx.google.com; dkim=pass header.i=@proton.me header.s=protonmail header.b=ayXHBa8o; spf=pass (google.com: domain of conduition@proton.me designates 185.70.43.25 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=20251104; t=1784400635; x=1785005435; 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:content-type :mime-version:feedback-id:references:in-reply-to:message-id:subject :cc:from:to:date:from:to:cc:subject:date:message-id:reply-to :content-type; bh=VfXYE9N6t1P/pM+FdjUK+CKa1fioH4/pIPttwka0yxs=; b=C+1+C56W1nfuCeOnLr+gNXvV7qNj5Clau17XH8JzdX46sWDElcYySZGRdUr05MOwfq x1ZGvFIB1be1wNHoHF5X5gIDjw+iqSqTwjIDFuCUYyGmC8L8ebobTIWSDu2Lq3hR8ksv dr0n1tlYOT1ZQ1FQM9w6pZ9uwAW0rPIufr9d8ayY2MePIajj6hHAnPHEJws/ipWM+Zqp KIQT1ncUNtX20eVog587/5c7C9uunWaMuBzbAh62tj06oN4k5qb2SRRYqqQT1tVQMHjU fPg749FFIh4rqhY8SWn8bdeyvpBP6za0SDUrWtG/sZ07Oen/kr91C/Oj6PAuzXNJZTZu mC9A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1784400635; x=1785005435; 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:content-type :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:content-type; bh=VfXYE9N6t1P/pM+FdjUK+CKa1fioH4/pIPttwka0yxs=; b=K+k1SLuGYgUiOgmBMjqoHclPYzeguFLe3lelALijsiHwMGt0kqgYFY7qpHRBVhkola Y9VxiOClvBauitA5SbBOZeD0WOzIhIna3C7fMCkpOHADnSpZtfSexj08b7RBw9IWBeJi mgGQkBE5yThFNHwAzlVV0gYxTP+I+TCSs9sTpxxN1/xspYMKSWtEk5Na5Q/4oJ4kOZS9 lVDdFh8JIJdvJUfielfYAbrWqXqc+BXJWSg1hAv0lYd3UqsEFCQlxHs366OThHot/QcC HdM3mG3G7r0pCr2JJf0N0g0Kx3S6kzj2ZoHZKd9VxFzFsL1r9bF2BnFi8nCp3o+A6TXA z50A== X-Forwarded-Encrypted: i=2; AHgh+RqliqzZnTFBc22CthdNxcK7Qq5eTuqWV3r8dgQB5idAk5ArAoK3QO51O8M20nB/s1a6XKL2Ta9y7MEj@gnusha.org X-Gm-Message-State: AOJu0Yw2+GR1Wu0+zoJR6/m3kLUHjQdvNrwoT1Jtt3oV/Vhu1lL/dGtq SF4Eo8nS9n+kQalNFJvI8RutKrcaYDHdMWoJ29ABBRW2rOpjSXH8YYCP X-Received: by 2002:a05:6870:648f:b0:44a:e523:aff2 with SMTP id 586e51a60fabf-45690c8022bmr3716027fac.23.1784400634941; Sat, 18 Jul 2026 11:50:34 -0700 (PDT) X-BeenThere: bitcoindev@googlegroups.com; h="Aa7YSPTofUUxVFD4Uz4T0wRwbHpEv8kvVpyLppQFR2gNGKLnug==" Received: by 2002:a05:6870:761b:b0:456:d5f3:3538 with SMTP id 586e51a60fabf-456d5f52a47ls59567fac.0.-pod-prod-03-us; Sat, 18 Jul 2026 11:50:30 -0700 (PDT) X-Received: by 2002:a05:6808:23c3:b0:495:e677:1332 with SMTP id 5614622812f47-4a4d0394900mr4804775b6e.36.1784400630489; Sat, 18 Jul 2026 11:50:30 -0700 (PDT) Received: by 2002:a05:600c:620e:b0:495:453b:241b with SMTP id 5b1f17b1804b1-495453b24d9ms5e9; Sat, 18 Jul 2026 11:45:15 -0700 (PDT) X-Received: by 2002:a05:600c:c84:b0:495:4491:b8c2 with SMTP id 5b1f17b1804b1-4954a3e6ed0mr79576255e9.3.1784400313325; Sat, 18 Jul 2026 11:45:13 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1784400313; cv=none; d=google.com; s=arc-20260327; b=qqC1qG7nD2T7sGcFVy8sZfquF+qPsfXYXRMk23z+WPRvtWRnlrB4bO672IoqjVFL9V pL3e4zHTqSCpB9CCLYiNYkARsMhKmBqR7lVjQ3CtI83FVz303v9n06KuaBUcpiiF0xym jInK2r5eZ96zOvshr02mg0XwLKlncQQ3029eHkUTEuyTPWRCoqOYfnKgOVK++/UqRdNX HcHl+GDN+g34FxaYeO8rVDMS00UnUKFtjEs8wE0LnE/VXQDqsfDAu9PXw5p7mMtql5uO MfspkYsiotlVBeBsVRvRHhSfxxIkrq4chkm/1mk1G4Gk3LLwWpmz/HqNgKlSebn0Y9aG MFFg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20260327; h=mime-version:feedback-id:references:in-reply-to:message-id:subject :cc:from:to:date:dkim-signature; bh=hyVV0t8vmUSUla4+FRLn9RnAmfuby3V+PtUx7KYc1mQ=; fh=ZoFN/wAJsc7YujXIAOohNqslPO0XeXRGfI/gbLftL6I=; b=acPUlujfvzf+oVMOdk4eJlrAoY6PppsBaJ+9haq/LzEc6DK5OXHNrHEMccGRFUOAfi xAyBk8J4GYAFWJSjwnijDKPb6WYZv6RGINKZm4YYr3JttcWbKDdQS9MRB5yfhIKhGt5/ 9s9eSt9i8aGYYi5mU+TjJTn4lgDx0cpQiUpEh3VPvzUDGaium5/r8LW8H2Tips1ERzXx RdJ4tIknp/B+G8PHPYtPJ/cuQsuoCNT1FV+nHvzfgn5giBA52lNDwU/+Ig/QWPnrhpg7 dhI43xzR9rgS1eVETkWmQSMgcMepTvaQvaWtxVS/XLp6Bymgl2lFauu7aBWir0ph5Z4T 7kww==; dara=google.com ARC-Authentication-Results: i=1; gmr-mx.google.com; dkim=pass header.i=@proton.me header.s=protonmail header.b=ayXHBa8o; spf=pass (google.com: domain of conduition@proton.me designates 185.70.43.25 as permitted sender) smtp.mailfrom=conduition@proton.me; dmarc=pass (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=proton.me Received: from mail-4325.protonmail.ch (mail-4325.protonmail.ch. [185.70.43.25]) by gmr-mx.google.com with ESMTPS id 5b1f17b1804b1-495483509c4si722445e9.0.2026.07.18.11.45.13 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 18 Jul 2026 11:45:13 -0700 (PDT) Received-SPF: pass (google.com: domain of conduition@proton.me designates 185.70.43.25 as permitted sender) client-ip=185.70.43.25; Date: Sat, 18 Jul 2026 18:45:06 +0000 To: Fabian From: "'conduition' via Bitcoin Development Mailing List" Cc: Bitcoin Development Mailing List Subject: Re: [bitcoindev] BIP draft: CISA for Taproot Key Path Spends Message-ID: In-Reply-To: References: Feedback-ID: 72003692:user:proton X-Pm-Message-ID: b2da35fbe29e2228662ddcfa2e79c47809c76053 MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha512; boundary="------cfc8427514a0fa3c85b46e79c0b0d8ed83b73ec232d8853effa1978761c1b2ed"; 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=protonmail header.b=ayXHBa8o; spf=pass (google.com: domain of conduition@proton.me designates 185.70.43.25 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) --------cfc8427514a0fa3c85b46e79c0b0d8ed83b73ec232d8853effa1978761c1b2ed Content-Type: multipart/mixed;boundary=---------------------4aef08d7aa5ccb56d7d1abca2590315f -----------------------4aef08d7aa5ccb56d7d1abca2590315f Content-Type: multipart/alternative;boundary=---------------------186dcdf77adbd25f4921166a35885d57 -----------------------186dcdf77adbd25f4921166a35885d57 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" Sending this again because I think the first time didn't work. Thanks Fabian, this is very cool. I haven't read the entire BIP in detail y= et, but first thing I notice on a quick skim is that reserving segwit versi= on 2 conflicts with BIP-360 which proposes to use the same. I'm particularly interested in how to dovetail this proposal with PQ migrat= ion efforts. I have two questions: 1. Can the framework you use for verifying aggregated sigs be generalized = to support future aggregated PQ signatures in the future? (assuming we some= day have a PQ sig algorithm that admits aggregation)=C2=A0 2. How do you see this proposal mixing with BIP360? The major hurdle I see= is that your proposed output type puts a bare EC pubkey on-chain in the sc= ript-pubkey. Unfortunately Boris' EC recovery trick=C2=A0does not seem to w= ork in this context: Because signatures are aggregated we can't recover pub= keys, so we can't hide them behind a hash. We either have to put them in th= e SPK, or the witness. So at face value, it seems there are two options: 1. Couple CISA tightly with P2TRv2. On one hand this would be good because= it would provide a concrete incentive for users to migrate to a wallet tha= t supports PQC. This also seems like the easier option from an engineering = perspective. However it comes with all the baggage of P2TRv2 (not actually = quantum-safe by default, need to solve the Q-day timing problem). 2. Hide the EC pubkeys behind a hash in the SPK (e.g. P2MR or P2TRH), and = attach the EC pubkey in the witness of every aggregated TX input, so that t= he verifier can run the aggregated sig-verify algorithms. This would be mor= e secure and relaxes the Q-day timing constraints, but we don't get as much= relative savings.=C2=A0 Napkin math of the witness weight of an aggregated input, assuming full-agg= regation is used: - with P2TRv2: - 1 byte for the marker - total: 1 byte - with P2TRH: - 1 byte for the marker - 32 bytes for the EC pubkey - total: 33 weight units - with P2MR: - 1 byte for the marker (witness) - 32 bytes for the merkle sibling node (witness) - 32 bytes for the EC pubkey (witness) - total: 65 weight units regards, conduition On Saturday, July 18th, 2026 at 7:44 AM, 'Fabian' via Bitcoin Development M= ailing List wrote: > Hi list, > I would like to share a BIP draft for transaction-wide cross-input > signature=C2=A0aggregation (CISA). It introduces=C2=A0a new=C2=A0witness= =C2=A0version, > which enables Taproot-style key path spending where=C2=A0inputs can > aggregate their signatures. >=20 > Each input chooses between half-aggregation, full-aggregation, or an > explicit opt-out via a marker byte in its witness. > The aggregation schemes themselves are specified in the previously > shared BIP 458 (half-aggregation) and BIP 459 (full-aggregation) > drafts. Script path spending follows BIP 341/342 unchanged. >=20 > The BIP draft text can be found here: > https://github.com/fjahr/bips/blob/cf0d4f2142cd0504b16e86739167b1f7ab9a3a= 06/bip-XXXX.mediawiki >=20 > For inline comments, I have opened a mock pull request on my BIPs > repo fork: > https://github.com/fjahr/bips/pull/6 >=20 > Feedback of any kind is much appreciated. >=20 > Best, > Fabian >=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/Qc_VmkfXgE8KHBfUnUB-hdWF1QOYv6zshzI7WEv_hvqJ6O_4zssJ4X2T2Di79I3TqHQvRDXsF= tD8os5M44wrbB61M1LD_-GDRGYEagoHsV4%3D%40protonmail.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/= IrJGniZYNo7x0fr4wABg7SsdqJoJWs5yozmiFLGzJkxOwtHU01_O8swpJMKVi_uEkdqAfFUTELp= OTja53HCrgmBgQBFYup1NQ4LCZHMRcFQ%3D%40proton.me. -----------------------186dcdf77adbd25f4921166a35885d57 Content-Type: multipart/related;boundary=---------------------199e81fdcc8f8c2272a16eac29477703 -----------------------199e81fdcc8f8c2272a16eac29477703 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Sending this again because= I think the first time didn't work.

Thanks Fabian, this is very cool. I haven't read the entire BI= P in detail yet, but first thing I notice on a quick skim is that reserving= segwit version 2 conflicts with BIP-360 which proposes to use the same.

I'm particularly interested in how to dovetai= l this proposal with PQ migration efforts. I have two questions:
=
  1. Can the framework you use for verifying aggregated sigs be gen= eralized to support future aggregated PQ signatures in the future? (assumin= g we someday have a PQ sig algorithm that admits aggregation) 

    <= li style=3D"list-style-type:"2. "">How do you see this prop= osal mixing with BIP360? The major hurdle I see is that your proposed outpu= t type puts a bare EC pubkey on-chain in the script-pubkey. Unfortunately <= a href=3D"https://delvingbitcoin.org/t/public-key-recovery-for-ec-leaves-in= -p2mr-bip-360/2603" title=3D"Boris' P2TRH trick" target=3D"_blank" rel=3D"n= oreferrer nofollow noopener">Boris' EC recovery trick does not see= m to work in this context: Because signatures are aggregated we can't recov= er pubkeys, so we can't hide them behind a hash. We either have to put them= in the SPK, or the witness. So at face value, it seems there are two optio= ns:

    =
      =
    1. Couple CISA tightly with P2TRv2. On one hand this would be good b= ecause it would provide a concrete incentive for users to migrate to a wall= et that supports PQC. This also seems like the easier option from an engine= ering perspective. However it comes with all the baggage of P2TRv2 (not act= ually quantum-safe by default, need to solve the Q-day timing problem).
    2. Hide the EC pubkeys behind a hash in the SPK (e.g. P2MR o= r P2TRH), and attach the EC pubkey in the witness of every aggregated TX in= put, so that the verifier can run the aggregated sig-verify algorithms. Thi= s would be more secure and relaxes the Q-day timing constraints, but we don= 't get as much relative savings. 

=
Napkin math of the witness weight of an aggre= gated input, assuming full-aggregation is used:

=
  • with P2TRv2:
    • 1 byte for= the marker
    • total: 1 byte
  • with P2TRH:
    • 1 byte for the marker
    • 32 bytes for the = EC pubkey
    • total: 33 weight units
  • with P2MR:
    • 1 byte for the marker (witness)
    • 32 bytes for the merkle sibling node (witness)
    • 32 bytes for the EC pubkey (witness)
    • total: 65 weight= units

regards,
conduiti= on

On Saturday, July 18th, 2026 at 7:44 AM, 'Fabian' via Bitcoin Devel= opment Mailing List <bitcoindev@googlegroups.com> wrote:
Hi list,

I would like to share a BIP draft for transaction-wide cross-input
signature a new witness&nb= sp;version,
which enables Taproot-style key path spe= nding where inputs can
aggregate their signatur= es.

Each input chooses between half-a= ggregation, full-aggregation, or an
explicit opt-out= via a marker byte in its witnesshttps://github.com/fjahr/bips/blob/cf0= d4f2142cd0504b16e86739167b1f7ab9a3a06/bip-XXXX.mediawiki

For inline comments, I have opened a mock pull = request on my BIPs
repo fork:

Fee= dback of any kind is much appreciated.

Best,
Fabian

--
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+u= nsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/Qc_VmkfXgE8KHBfUnUB-hdWF1Q= OYv6zshzI7WEv_hvqJ6O_4zssJ4X2T2Di79I3TqHQvRDXsFtD8os5M44wrbB61M1LD_-GDRGYEa= goHsV4%3D%40protonmail.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/IrJGni= ZYNo7x0fr4wABg7SsdqJoJWs5yozmiFLGzJkxOwtHU01_O8swpJMKVi_uEkdqAfFUTELpOTja53= HCrgmBgQBFYup1NQ4LCZHMRcFQ%3D%40proton.me.
-----------------------199e81fdcc8f8c2272a16eac29477703-- -----------------------186dcdf77adbd25f4921166a35885d57-- -----------------------4aef08d7aa5ccb56d7d1abca2590315f 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== -----------------------4aef08d7aa5ccb56d7d1abca2590315f-- --------cfc8427514a0fa3c85b46e79c0b0d8ed83b73ec232d8853effa1978761c1b2ed Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: ProtonMail wrsEARYKAG0FgmpbyaEJEHgpbO2E9rPFRRQAAAAAABwAIHNhbHRAbm90YXRp b25zLm9wZW5wZ3Bqcy5vcmfdzg7f124MUPC7g6PARumUFm3K0ufK6KQH/CYq iwrQnBYhBEdIka0CMtrLdg13a3gpbO2E9rPFAACmtgEAgD/gCTkvvZcZ7OtU NMozIjTNkm08RL4c0zmV2RRSi4UBANYSrtu5z27bq9FU4+wHp59bSJLuLU0P /VI15oCwiN4N =9Z7k -----END PGP SIGNATURE----- --------cfc8427514a0fa3c85b46e79c0b0d8ed83b73ec232d8853effa1978761c1b2ed--