-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 This is 5atoshiNakamoto's most recent Warrant Canary. This file version can be accessed at https://5atoshiNakamoto.github.io/canary.txt An archive of former canaries can be found at https://5atoshiNakamoto.github.io/canaries *********** STATEMENTS *********** * The issue date of this canary is today: Sun. 20, April, 2025. (See DEADLINE UPDATE and PROOF OF DATE below.) * 5atoshiNakamoto's main signing key is used to sign this canary: ID: 0x926025C3 Fingerprint: 51AE 7F50 3F5F 6404 FBEC 93CB F57A C7F1 9260 25C3 Comment: 5atoshiNakamoto.labbe@simplelogin.co (Public Key may be found at https://5atoshiNakamoto.github.io/public-key, forwarding to https://keys.openpgp.org/search?q=5atoshiNakamoto.labbe@simplelogin.co, as well as at https://github.com/5atoshiNakamoto, and even at https://keybase.io/5atoshiNakamoto) * 5atoshiNakamoto is the account administrator of https://5atoshiNakamoto.github.io and the associated Github account, https://github.com/5atoshiNakamoto. *************** LIBERTY CANARY *************** 5atoshiNakamoto is in 100% control of all of his or her own hardware. 5atoshiNakamoto will shut down before becoming complicit in crimes against his or her own userbase under duress of any government or organization. 5atoshiNakamoto is not under duress of any government or organization. *************** WARRANT CANARY *************** No warrants have ever been served to me, 5atoshiNakamoto, by this pseudonym or by my real given name and legal government ID (e.g. to hand out private signing keys, or to introduce backdoors to any project in which I'm involved, in so far as I know), nor have any searches or seizures taken place of my own space. 5atoshiNakamoto has not received: * A gag order preventing the disclosure of a broad order for user metadata * A gag order preventing the disclosure of a broad order for user data * A gag order preventing the disclosure of a targeted order for user data * A gag order preventing the disclosure of a targeted order for user metadata 5atoshiNakamoto has never received a legal order enforceable in his or her jurisdiction for user data. 5atoshiNakamoto has never received a legal order enforceable in his or her jurisdiction for any broad class of users. 5atoshiNakamoto has never received a gag order preventing disclosure of any broad order. A gag order refers to any legal order enforceable in 5atoshiNakamoto's jurisdiction preventing disclosure of: * A request or order for user information * A request or order for investigative assistance * A request or order for technical assistance * Any other request, order, demand, or information of any type **************** DEADLINE UPDATE **************** The next canary statement is planned to be published within 3 months, before 20, July, 2025. *Special note should be taken if no new canary gets published by that time, or if the list of statements change without plausible explanation.* Once again, an archive of former canaries can be found at https://5atoshiNakamoto.github.io/canaries ************** PROOF OF DATE ************** PROOF OF DATE is currently best demonstrated utilizing a combination of two(2) tools: (1) Printing a very recent Bitcoin block hash demonstrates that this canary could not have been created PRIOR to the date and time of the Bitcoin block height stated (3 blocks back [~30 minutes] to protect against the (un)likelihood of block reorganization), and (2) Verifying the hash of this canary.txt file timestamped on https://OpenTimestamps.org and included in the Bitcoin blockchain demonstrates that this canary could not have been created AFTER the date and time stated. Thus, a narrow window between these two results is the only plausible date and time for the creation and timestamped signature of this canary. (1) A very recent Bitcoin block hash: 000000000000000000017ff517d14639709f164097af4d1ee6b45362ff97e45f Block: 893229 (You can easily view evidence of this Bitcoin block hash at a website like: https://mempool.space/block/000000000000000000017ff517d14639709f164097af4d1ee6b45362ff97e45f) (2) Next, verify the matching hashes of the following files on https://OpenTimestamps.org and that it is included in a Bitcoin block sufficiently close in date and time to Block 893229 from Step 1. Download the two files at: * https://5atoshiNakamoto.github.io/canary.txt.ots * https://5atoshiNakamoto.github.io/canary.txt Then at https://OpenTimestamps.org, first drag (or otherwise, 'upload') the .txt.ots proof file into the STAMP & VERIFY box, followed by the .txt stamped file into the box below it. If all checks out, the files will both display a matching hash and the Bitcoin block height and time in which this hash was included. Compare this Bitcoin block height and time to Block 893229. Each difference in block height represents the passage of ~10 minutes. ******************** DISCLAIMERS & NOTES ******************** (1) No data within any files are actually uploaded to the servers at https://OpenTimestamps.org in the process of creating or verifying this timestamp. Only a SHA256 hash function occurs within the privacy of one's browser. In the timestamp creation process, only the hash of the file is included among many others in a Merkle tree of a subsequent Bitcoin block. (2) This scheme is not infallible. Although signing this declaration makes it difficult for a third party to produce arbitrary declarations, it does not prevent them from using force—or other means like blackmail or compromise of the signer's laptop(s), for example—to coerce one to produce false declarations. (3) This declaration is merely a best effort and provided without any guarantees, warranty, and is not legally binding in any way to anyone. No signer should ever be held legally responsible for any of the statements made here. (4) Failure to update this canary does not necessarily mean 5atoshiNakamoto has received a gag order; nor is not updating it—or omitting anything—an attempt to communicate anything to anyone. Frankly, it's also entirely plausible that 5atoshiNakamoto could have become otherwise incapacitated or lazy with his or her systems management of this website, leaving this canary to expire, but let's hope not. Have you asked him or her? This canary serves only to periodically confirm certain facts as long as they are presently true. (5) Compromise of the associated Github account, 5atoshiNakamoto, or PGP private key remains always a remote possibility. (6) Doing the best we can. -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEUa5/UD9fZAT77JPL9XrH8ZJgJcMFAmgEtHIACgkQ9XrH8ZJg JcMKqQ/+OsKAkHKm+3RZbSTs0iy230Cpxxo4kpbAeFenadW9qmeFtgrDz1CSgZmy mhEw4UftlvDWuerMMQkwhPZwT2DvXW4coQasCG1+JSTJTSqcQkr04FXNc+Ichcyy wFMaR4JUfdtRhus7noJVcbVwbxfEynNtr+tWipONpeyGF2odJwLBkim0gBWeQl+1 7pIByIrV98xpdYgctLL8myNIHOuWhF6uuTj02YH/yodv2snwyNDzT+sL5dnG4mkC YhUJRktS552Uuq31QwRvZTENzx/0bv3oHTu1Wczvk+K9gc20xTB2AOa5c1szDp0a vl2os8uwdbAslmSVgODMYeHO36zZvxWWItkVEz6ZOKMAVr3xkGTHZvvy/X290EBc ZIxJ6oB7zE1Mil+UMkZ2lVJRoATP7syaWb/Re2RUH3HmKPl4UdBq+qAQbB5rFNRa Xp2799DmD0ZgSrPSot0ovp5N/JgUwEpOtFqU+2C8d0ubxrC64nDBrhvDkgQuOjWm mWmN6CLTdVbqWUpl+CmPanUkfSAJYg6cOnFxLyBO58S0KeEU7RvV83IwQQ1jfkfq Z61M8EHuXNIhdvSuY0s5b/WwBDEqeUjMBy2pEe+LLnhanUblWynPiwP9dYNZEOUj gxMo00sexibWlcKGRts819HJm6osIEI/zkjvQRnuaP+GQkZZ5gI= =7yHh -----END PGP SIGNATURE-----