dannybuntu on Nostr: @Bitkey v2026.11.0 (Android, Play Store split APKs) reproduces exactly — zero ...
@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 Published at
2026-07-20 07:54:39 UTCEvent JSON
{
"id": "fa8ee8df5a57e7440b09f6e05edc2327f09df6c79f77ff06db3f734c2fc36b55",
"pubkey": "1f9e547c2f31942623b8ad1d07713282e8640fd8cf474e9f79f18ace8af216ed",
"created_at": 1784534079,
"kind": 1,
"tags": [
[
"client",
"WalletScrutiny.com",
"31990:168b7a2cd8bb9205c3f574de540606d6f4c46717c5164f47373fdcce2b9cd335:7703371760017",
"wss://relay.nostr.info/"
],
[
"c",
"walletscrutiny"
]
],
"content": "@Bitkey v2026.11.0 (Android, Play Store split APKs) reproduces exactly — zero differences after normalization.\n\nThis 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.\n\nAt 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.\n\nresources.arsc semantically identical across all resource-bearing splits. Remaining AndroidManifest.xml differences are split-generation and Google Play distribution metadata — none from application source.\n\nScope: Play Store split APK variant, arm64-v8a / xxhdpi / SDK 35.\n\nFull verification:\n\nhttps://walletscrutiny.com/verifier/?pubkey=1f9e547c2f31942623b8ad1d07713282e8640fd8cf474e9f79f18ace8af216ed#verificationId=4f3062ada69fe262184be9ef92b5f4ef39854e9afd0e822cdee640e00285543c ",
"sig": "32204bed7c66ba89a5e33791b197e19c19dbfd76c1ae84c6aa97e6c1ef9a54eeab2f69aa416d5ec646416e7977989e35241a62eaed02bc72a19fe190bce40384"
}
