From mboxrd@z Thu Jan 1 00:00:00 1970 Delivery-date: Thu, 22 Jan 2026 06:54:45 -0800 Received: from mail-oa1-f62.google.com ([209.85.160.62]) by mail.fairlystable.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1viw56-00024U-GP for bitcoindev@gnusha.org; Thu, 22 Jan 2026 06:54:45 -0800 Received: by mail-oa1-f62.google.com with SMTP id 586e51a60fabf-40414b6f18dsf398578fac.3 for ; Thu, 22 Jan 2026 06:54:44 -0800 (PST) ARC-Seal: i=2; a=rsa-sha256; t=1769093678; cv=pass; d=google.com; s=arc-20240605; b=A7AGqZ6mb+g+aqGlBnZTl0uFk70aiJCsRJScU7s+Hyg3sBcpUqawajmG2r8482uq+y DowBuHBD6lUbi4o+o2lnA5ZflNynFv+dcX50DL82kruX3aTZrilSLc/SbJBF5XXzsr5s m8zaWMo7aeDzzztxPbVXfi9sV57YEBT0++BauQwm1UAn2qf0MI/btqJM/q3cNi26zI2u L4l+egv/KZCNu3+gXsT72yo9sYhJ5kfZSEs5BuvCRXWFJqUO1KUM/b2NtOMahnsV5RWM DyhoqB6rAbSn/6rbc6F6oRTnBV0+qcORwiXNG7rG53X4abBKgzXm7D9NfT88t0FGY/de ShyA== 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=4sZOI1WJ9v0/ega6kVQWVMZqmUePOevPLONElWvGuu0=; fh=J/0tDjsQBXnwyl0pR+8T/wljV1L2+WhwMqEymjGOtG0=; b=YdPlSkDLJO7t1OGxSB03CmCgEbE0NLBqv3EZnQxmVvA0tMGxEb3/0OOHGHVXJuEQo9 m3Qlx/54PVkzwrfcWqVKh1ClGEIfG6NX3DfiqszigPKxw42zzyJH/sLcBi039Qpd1lp+ Uo1qdAVR+xXmpliEF3K6+OafG+lmHcS/rntNBXHuvkzJoaU5QuP/TlMCPUFGtYcJ2LqF c/Mg63lEeP3wQcudgXWyZM7/J4UilJbcdX9rXtONPsKkyTHbi6r4wmRMFfkOdr7sU2Fn Q5RsCaax1snbCk/mPp5eXc0M4Jls5Nk+6YExWmA84sP2F9zY7YNkqTDjl4sz0968nOzQ nujA==; darn=gnusha.org ARC-Authentication-Results: i=2; gmr-mx.google.com; dkim=pass header.i=@proton.me header.s=protonmail header.b=Zk3JBTCv; 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=20230601; t=1769093678; x=1769698478; 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=4sZOI1WJ9v0/ega6kVQWVMZqmUePOevPLONElWvGuu0=; b=ckoxJpRjwN68T/t3oEsTKdVstI/dnJMg2WadrzIG5hMI5Ma+eMcnmB4IlPJh6y5/ZR oPcyzUjrkStQHZyecDuSpPLd/Fyp8GBce749D1XM1U8x+MkVjJEELkrkA+/9//CwWfWO DhaBoPTsTEXoMXOFgWLdtLhKAicy/zOKKbepfrRLqiPj8Bqkn7lgPNU67WAzGLjLyNbe GFiUVfnxROzYMhm6SinZEg0I2qhhFAl77FcCry2878uzmUJ1Nh65j0B6q8HHxGZvtAhu w94m5NbT7T2Q9WU5gCGVn5MTiPb+jf1bqhphHIsrekITi0gyn62ocQva1tDmeSCTKg/o 7Kag== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1769093678; x=1769698478; 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=4sZOI1WJ9v0/ega6kVQWVMZqmUePOevPLONElWvGuu0=; b=NpJ9YkLoJJOZR/QfJaov23Y61mE4ZTggnk7VAb7Eg4y3Ux4InGu88q3f9zbNQwvV+d az6KZ8BJZTuW+CpI2cR1avqk4ru4EwW93V09zAOvcLLgKYFyL0gC9PFU6T+kFfHJGThU mJgOUwHzdPIbRM7x8TYLQWNxAtOrF9th4ksKhTAOEfNkE/WAReOmRTfuumo1yYS52KxJ XAjp5jdxjAwDQZKrENDIEB8mYnMQ0lsEcwzo3C1nqHSsyJ5x36Q4JU6exy6vP7OF4oec J8YmtnfmEvsSONZsQVu0KNuKpwFpZGW4RBb52ZEof2S6h20eFfpoukzrFLN2PekmjU4n OSvA== X-Forwarded-Encrypted: i=2; AJvYcCUsYKUDzG+EeBpu+U9d+FsNdIf7R0VIi9+c49nROKp+q5gOKmutIHusCHS8Dr/wQfrlKjnu6pOvYrN6@gnusha.org X-Gm-Message-State: AOJu0YwrjqheJJDwWh5ILefYY+nxfwLO/egHFHHQB0yPthG2yaXHwjnZ ETd5KNFOOoV9uL3C8BGzgVaOrbRYAp0fAYBvVqBMMonAI81j5TKD8mfi X-Received: by 2002:a05:6870:c1d4:b0:3ec:4a8d:420b with SMTP id 586e51a60fabf-40846da119amr4171587fac.42.1769093677937; Thu, 22 Jan 2026 06:54:37 -0800 (PST) X-BeenThere: bitcoindev@googlegroups.com; h="AV1CL+EN+5f27WhGPhYNZwCxfFx1py26J4HrJ1bLC3b8z+jzFw==" Received: by 2002:a05:6870:6492:b0:408:8d90:8644 with SMTP id 586e51a60fabf-4088d90943els308107fac.0.-pod-prod-08-us; Thu, 22 Jan 2026 06:54:33 -0800 (PST) X-Received: by 2002:a05:6808:5391:b0:450:bc64:d159 with SMTP id 5614622812f47-45e8aa963b2mr4059716b6e.54.1769093673429; Thu, 22 Jan 2026 06:54:33 -0800 (PST) Received: by 2002:a05:600c:6c50:b0:477:b663:eee5 with SMTP id 5b1f17b1804b1-4801fd9b8f3ms5e9; Thu, 22 Jan 2026 06:35:32 -0800 (PST) X-Received: by 2002:a05:6000:2207:b0:435:6f0e:2e5e with SMTP id ffacd0b85a97d-4358ff3ea6fmr16141494f8f.62.1769092530598; Thu, 22 Jan 2026 06:35:30 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1769092530; cv=none; d=google.com; s=arc-20240605; b=K7dnIB0UCV2dDz4Js5+tQ3e5CYbAAnrhssLXFGGBp9ouIVQ09YGCYcw1gIe5kq56kg xlooojBtUlEVyBklWwyphWw7fNp628L9czoPfi+IXy9xVsXs9tSrs665wl1MDuDB0/f1 nm+IpVnqYijf/MyobcK+8dFgmtsUU3+uTPo999KgcaGZfyYNSvrX5nxfm+ObJAnF9zzM DOM6P489Nbo+9L3T/uuFR76pna2revOJwyuJojdFOpF+17mzj6tgr+N5wqvv4Hb7Ixcp S32wX4xC3YLxr69ryXlWT5TvOeHb7uJ1bQdXHFBpuHHkyNrnma/imncXrShh8/1BdSzu 5oxQ== 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=Llk/sXD9akTlkphTZTaPsz51qoUuoMOj5skCHfMSEJU=; fh=xlGXdwx/AOGpOY1BIwU4GAlWnzM8ndEKiseeCUWJ6As=; b=iDiYn21cD8RRfPHIr8qh0/oI25hoefwSqqHyvc8XNwg+BlPJ3KznLQXXsgXEQis3j1 XgWj3ppMztFzO2emMqihXCNFi6uYf1W/9xMY/U/zreyUuYpSt9I6iO0UPY4i91yFFQsA uVydYhvSUp59bcXJJDrf7LGnYopY3CbHKuanNrchOXge18Z4cQIiWczI67lxnpC6ZqAx NT+kXQrIkOAdGLHE4AFusAPcRxUoEzGGaQw5324hPOUkivr5R9UshVgFjx37kPOSAIky /++IoSStUgH8CidsnOoFL1NHfJKaGZLuGLe35ZeYO5vMHOqEw2lszHWg8JKTBdwlWKUy 4XHw==; dara=google.com ARC-Authentication-Results: i=1; gmr-mx.google.com; dkim=pass header.i=@proton.me header.s=protonmail header.b=Zk3JBTCv; 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 ffacd0b85a97d-435a8166321si59134f8f.5.2026.01.22.06.35.30 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 22 Jan 2026 06:35:30 -0800 (PST) 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: Thu, 22 Jan 2026 14:35:26 +0000 To: Giulio Golinelli From: "'conduition' via Bitcoin Development Mailing List" Cc: Bitcoin Development Mailing List Subject: Re: [bitcoindev] Falcon Post-Quantum Signature Scheme Proposal Message-ID: In-Reply-To: <16e01530-e9dd-481f-8c7f-ca9ccafcfcden@googlegroups.com> References: <16e01530-e9dd-481f-8c7f-ca9ccafcfcden@googlegroups.com> Feedback-ID: 72003692:user:proton X-Pm-Message-ID: b2704bd9a82839d57c7fb1301fa4a556e769c3fc MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha512; boundary="------21b1d6e9b2c81219b821460999adf42e9872bcf81585e2666796a46e4c1a0c5f"; 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=Zk3JBTCv; 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) --------21b1d6e9b2c81219b821460999adf42e9872bcf81585e2666796a46e4c1a0c5f Content-Type: multipart/mixed;boundary=---------------------8906fbf63b5b20b18ee74e281a393a31 -----------------------8906fbf63b5b20b18ee74e281a393a31 Content-Type: multipart/alternative;boundary=---------------------a83646daf9adbfee14b9a8d19203e6c0 -----------------------a83646daf9adbfee14b9a8d19203e6c0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" Falcon (FN-DSA) relies on discrete gaussian sampling using constant-time fl= oating point arithmetic for signers, which is very hard to implement quickl= y and in constant time (securely). Despite being significantly harder to im= plement than ML-DSA, it only provides a mild (factor of two or so) improvem= ent in signature + pubkey size. This is why we're probably not including FN= -DSA in our PQ signature opcode BIP following BIP360. https://blog.cloudflare.com/nist-post-quantum-surprise/#floating-points-fal= cons-achilles While I wouldn't rule out Falcon permanently, I personally feel more resear= ch is needed to explore Falcon, its weaknesses, and how flexibly it can be = adapted to schemes like CISA, BIP32, and multisignatures. Let it bake a lit= tle longer. If small signatures are your goal, then I'd look into SQIsign, which uses i= sogeny-based cryptography to produce very small sigs (148b) and pubkeys (65= b) using some convoluted mathematical tricks. However, much like Falcon, it= is still immature and needs more researchers to optimize its verification,= explore its strengths, and attack its weaknesses.=C2=A0 If you want a PQC scheme that's ready today=C2=A0and also provides small si= gnatures, I'll point you to XMSS, and Jonas Nick's SHRINCS proposal. You ca= n configure an unbalanced XMSS tree to get 272 byte signatures, potentially= smaller if you crank up the parameters. The catch is a dependence on state= fulness.=C2=A0 regards, conduition On Wednesday, January 21st, 2026 at 11:09 PM, Giulio Golinelli wrote: > Hi everyone, >=20 > I am to share a technical demonstration and benchmarking project that int= egrates the Falcon post-quantum signature scheme (Falcon-512) into Bitcoin = Core, implemented as a soft-fork within the classic P2WPKH mode. This work = aims to provide a practical reference for possible future Falcon adoption, = especially as it approaches FIPS standardization. > You can find details at this fork. >=20 > Why Falcon? > Falcon is a lattice-based, post-quantum digital signature scheme designed= to be secure against quantum attacks. Unlike other PQC candidates such as = SPHINCS+ and ML-DSA, Falcon offers significantly smaller signature and publ= ic key sizes, as well as efficient signing and verification times. It is im= plemented in pure C and does not require external dependencies. >=20 > Benchmarking & Results > Aspect Falcon ECDSA > Public Key Size (B) 897 33 > Signature Size (B) 655 71 > Verification Time (=CE=BCs) 57 120 >=20 > Verification time is more critical than signature creation time in Bitcoi= n, since signature creation is performed by clients (wallets), while nodes = focus on verification. > Integration >=20 > - Falcon was included into the codebase from the original GitHub reposi= tory. > - The build system (CMakeLists.txt) was updated to support Falcon. > - Falcon verification has been soft-fork enabled via a new script verif= ication flag. >=20 > Next Steps & Reference > This project serves as a practical demonstration of Falcon=E2=80=99s prom= ising performance, highlighting its advantages over currently selected post= -quantum signature algorithms such as SPHINCS+ and ML-DSA, which face signi= ficant time and space limitations. As Falcon approaches FIPS standardizatio= n, this work aims to provide a reference for future adoption and integratio= n in Bitcoin. >=20 > Let me know what you think and if this could be of interest for which cas= e I can complement the project by integrating Falcon into all the other spe= nding paths. I also look forward to development/integration corrections. >=20 > Best regards, > Giulio >=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/16e01530-e9dd-481f-8c7f-ca9ccafcfcden%40googlegroups.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/= qmJtMusWT649HfvfUWJJn8dIP7vcJ-xI4bLEXnb-1saPcgmC4as1sSSOpshVGrx2Aj-9X0McB97= slaYO286jS7-4N_ROqXtbNDdCrbcEnX0%3D%40proton.me. -----------------------a83646daf9adbfee14b9a8d19203e6c0 Content-Type: multipart/related;boundary=---------------------69dcf392cf1bcaeb35308291f9993d9e -----------------------69dcf392cf1bcaeb35308291f9993d9e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Falcon (FN-= DSA) relies on discrete gaussian sampling using constant-time floating poin= t arithmetic for signers, which is very hard to implement quickly and in co= nstant time (securely). Despite being significantly harder to implement tha= n ML-DSA, it only provides a mild (factor of two or so) improvement in sign= ature + pubkey size. This is why we're probably not including FN-DSA in our= PQ signature opcode BIP following BIP360.


=
While= I wouldn't rule out Falcon permanently, I personally feel more research is= needed to explore Falcon, its weaknesses, and how flexibly it can be adapt= ed to schemes like CISA, BIP32, and multisignatures. Let it bake a little l= onger.

= If small signatures are your goal, then I'd look into SQIsign, which uses isogeny-based cryptog= raphy to produce very small sigs (148b) and pubkeys (65b) using some convol= uted mathematical tricks. However, much like Falcon, it is still immature a= nd needs more researchers to optimize its verification, explore its strengt= hs, and attack its weaknesses. 

If you want a PQC scheme that's ready toda= y and also provides small signatures, I'll point you to XMSS, and = Jonas Nick's SHRINCS proposal. You can configure an unbalanced XM= SS tree to get 272 byte signatures, potentially smaller if you crank up the= parameters. The catch is a dependence on statefulness. 

regards,
conduition
<= div class=3D"protonmail_quote"> On Wednesday, January 21st, 2026 at 11:09 PM, Giulio Golinelli <= golinelli.giulio13@gmail.com> wrote:
Hi everyone,

I am to share a technical demonstration and= benchmarking project that integrates the Falcon post-quantum signature sch= eme (Falcon-512) into Bitcoin Core, implemented as a soft-fork within the c= lassic P2WPKH mode. This work aims to provide a practical reference for pos= sible future Falcon adoption, especially as it approaches FIPS standardizat= ion.
You can find details at th= is fork.

Why Falcon?
Falcon is a lat= tice-based, post-quantum digital signature scheme designed to be secure aga= inst quantum attacks. Unlike other PQC candidates such as SPHINCS+ and ML-D= SA, Falcon offers significantly smaller signature and public key sizes, as = well as efficient signing and verification times. It is implemented in pure= C and does not require external dependencies.

Benchmarking &= Results
Aspect Falcon ECDSA
Public = Key Size (B) 897 33Signature Size (B) 655 71
Verification Time (= =CE=BCs) 57 120

Verification time is more c= ritical than signature creation time in Bitcoin, since signature creation i= s performed by clients (wallets), while nodes focus on verification.
Integration
  • Falcon was included into the cod= ebase from the original GitHub repository.
  • The build system (CMakeL= ists.txt) was updated to support Falcon.
  • Falcon verification has be= en soft-fork enabled via a new script verification flag.
= Next Steps & Reference
This project serves as a practical demons= tration of Falcon=E2=80=99s promising performance, highlighting its advanta= ges over currently selected post-quantum signature algorithms such as SPHIN= CS+ and ML-DSA, which face significant time and space limitations. As Falco= n approaches FIPS standardization, this work aims to provide a reference fo= r future adoption and integration in Bitcoin.

Let me know what you t= hink and if this could be of interest for which case I can complement the p= roject by integrating Falcon into all the other spending paths. I also look= forward to development/integration corrections.

Best regards,
Gi= ulio

--
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/16e01530-e9dd-481f-8c7f-ca9ccafcfcden%40googlegroups.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/qmJtMu= sWT649HfvfUWJJn8dIP7vcJ-xI4bLEXnb-1saPcgmC4as1sSSOpshVGrx2Aj-9X0McB97slaYO2= 86jS7-4N_ROqXtbNDdCrbcEnX0%3D%40proton.me.
-----------------------69dcf392cf1bcaeb35308291f9993d9e-- -----------------------a83646daf9adbfee14b9a8d19203e6c0-- -----------------------8906fbf63b5b20b18ee74e281a393a31 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== -----------------------8906fbf63b5b20b18ee74e281a393a31-- --------21b1d6e9b2c81219b821460999adf42e9872bcf81585e2666796a46e4c1a0c5f Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: ProtonMail wrsEARYKAG0FgmlyNZ4JEHgpbO2E9rPFRRQAAAAAABwAIHNhbHRAbm90YXRp b25zLm9wZW5wZ3Bqcy5vcmdOEfgflE+bjJccFo8WcEKlNG2xwAxdaj4avS3k Zbdp6hYhBEdIka0CMtrLdg13a3gpbO2E9rPFAADK5AD/VcbEPsLLm/R5tueJ X+1ClbQCDq28PNTs43BVnb22sI8BAIn2/8Cre8KZAk5WgbCfKh+irT0BOKFi qDOzBRj3LfgK =FF9q -----END PGP SIGNATURE----- --------21b1d6e9b2c81219b821460999adf42e9872bcf81585e2666796a46e4c1a0c5f--