Liana v15.0 (Linux) verified reproducible. Rebuilt from source at tag v15.0 (4684d5cb) with upstream's pinned Guix build. All 3 shipped executables — lianad, liana-cli, liana-gui — are byte-for-byte identical to the official .tar.gz and .deb. https://walletscrutiny.com/verifier/?pubkey=1f9e547c2f31942623b8ad1d07713282e8640fd8cf474e9f79f18ace8af216ed#verificationId=7a57b4e1a6e216ee225bf59e871da70cefb70675a2faca3534ee9121ada905c1

"Whether you believe in God or not - religions, these are institutions that have had several thousands of years of practice to get it right - what do they all have? Prayer - words of affirmation and the practice of gratitude." https://www.youtube.com/watch?v=JOh-9iaPcGU

@Bitkey v2026.11.0 (Android, Play Store split APKs) reproduces exactly — zero differences after normalization. This one is a fix landing. Our v2026.8.0 and v2026.10.0 verifications both returned not_reproducible for the same reason: BUILD_DATE was compiled in from git log -1 --date=short, so a rebuild stamped the date of the published-source commit rather than the date of the internal build commit. In v2026.10.0 the entire difference was one content byte — 2026-05-21 vs 2026-05-22. At v2026.11.0 upstream ships verifiable-build/android/release-build-date.txt and reads it in preference to git. It's load-bearing here: the tag commit is dated 2026-07-09, the shipped build date is 2026-07-02. Under the old logic this release would have failed by a seven-day margin. classes.dex now matches byte for byte. resources.arsc semantically identical across all resource-bearing splits. Remaining AndroidManifest.xml differences are split-generation and Google Play distribution metadata — none from application source. Scope: Play Store split APK variant, arm64-v8a / xxhdpi / SDK 35. Full verification: https://walletscrutiny.com/verifier/?pubkey=1f9e547c2f31942623b8ad1d07713282e8640fd8cf474e9f79f18ace8af216ed#verificationId=4f3062ada69fe262184be9ef92b5f4ef39854e9afd0e822cdee640e00285543c

@BitcoinSafeOrg Desktop v2.1.0 — Linux AppImage (x86_64) reproduces exactly. Built from tag 2.1.0 (commit c208831) in a containerized environment. The resulting archive is byte-identical to the file published on the release page: Bitcoin-Safe-2.1.0-x86_64.AppImage.tar.gz sha256 8568fe64eac2935786b59c2e8e9161f7eecbcf8f80c4c93f5b8f605bbec980f6 No stripping or normalization — the artifact users download is the artifact compared. That download also carries a valid PGP signature from the release key 2759AA71…F612D, whose fingerprint is published on bitcoin-safe.org independently of the GitHub assets it signs https://walletscrutiny.com/verifier/?pubkey=1f9e547c2f31942623b8ad1d07713282e8640fd8cf474e9f79f18ace8af216ed#verificationId=d7e409662c93455842f21e90f50e8f2757fbead0bb9568ce6afa2c220e0fbc15

Thanks Johnny, maybe as we get more experience and knowledge, we can go deeper than hashes next time!

Binge-watched "Little House on the Prairie" on Netflix, about living life in the American Frontier. There are things common and different with the Filipinos "living life in the Philippine Islands" maybe a book about it deserves to be written. But I can't time-travel. Somebody should have written about it. Maybe some of the Spasnish have. I know the Americans missionaries have, but I want a different perspective. Filipinos by the way, back then is the term used to describe the Spanish who migrated to the Philippines. They hold a higher distinction when compared to us brown-skins - we were called indios. Which kinda sounds like "Indians"

Update 2026-07-17. In the process of improving the mycelium script, we've found some interesting observations. > Update — alternate Google Play hash for Mycelium 3.22.0.2. Google Play now serves a byte-distinct APK for the same version: - Previous: bfcd317bd2bae081d5d4d9cd0f80619e69fe9b5f4f7853a1f06510be75f45603 - Current: 335de275ff03e5dd4bab5f5b7bf31ba42af0bb68fa751dd092e6fb03c0a22d98 - Both APKs are exactly 53,772,157 bytes, and all 2,891 ZIP entries are byte-for-byte identical. Both verify with APK Signature Schemes v2/v3 and the same Mycelium signing certificate. The hash change is confined to the APK Signing Block: the current APK adds Google Play “Frosting” security metadata (0x2146444e) while reducing its padding by the same amount. No application code or resources changed. The reproducible verdict therefore remains unchanged. We did not upload the new report as it would overlap the previous one. Verdict unchanged: reproducible. https://walletscrutiny.com/mobile/com.mycelium.wallet/#verificationId=7ef3b0891841d2a9c8c0aa5707e944e1164617c0e583f9e0c1a2e72c258ba6bb

諦めないで - Akiramenaide https://www.facebook.com/share/p/18xqxjxenA/

Thank you !