Skip to content

BIP85: fix datetime string typo to align with UNIX Epoch time #1967

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jonatack merged 8 commits into from
Oct 15, 2025
Merged

BIP85: fix datetime string typo to align with UNIX Epoch time #1967

Changes from 1 commit
Commits
Show all changes
8 commits
Select commit Hold shift + click to select a range
ee69fc6
Fix BIP85 Timestamp Typo
3rdIteration Sep 15, 2025
1887780
Update bip-0085.mediawiki
3rdIteration Sep 19, 2025
3dab73a
Update bip-0085.mediawiki
3rdIteration Oct 6, 2025
53a0084
Update bip-0085.mediawiki
3rdIteration Oct 6, 2025
71e0d81
Update bip-0085.mediawiki
3rdIteration Oct 6, 2025
3fa9d10
Update bip-0085.mediawiki
3rdIteration Oct 7, 2025
903ab6e
Update bip-0085.mediawiki
3rdIteration Oct 14, 2025
eb7ad53
Update bip-0085.mediawiki
3rdIteration Oct 14, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion bip-0085.mediawiki
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -382,7 +382,7 @@ Keys allocated for RSA-GPG purposes use the following scheme:

Note on timestamps:

The resulting RSA key can be used to create a GPG key where the creation date MUST be fixed to unix Epoch timestamp 1231006505 (the Bitcoin genesis block time <code>'2009-01-03 18:05:05'</code> UTC) because the key fingerprint is affected by the creation date (Epoch timestamp 0 was not chosen because of legacy behavior in GNUPG implementations for older keys). Additionally, when importing sub-keys under a key in GNUPG, the system time must be frozen to the same timestamp before importing (e.g. by use of <code>faketime</code>).
The resulting RSA key can be used to create a GPG key where the creation date MUST be fixed to unix Epoch timestamp 1231006505 (the Bitcoin genesis block time <code>'2009-01-03 18:15:05'</code> UTC) because the key fingerprint is affected by the creation date (Epoch timestamp 0 was not chosen because of legacy behavior in GNUPG implementations for older keys). Additionally, when importing sub-keys under a key in GNUPG, the system time must be frozen to the same timestamp before importing (e.g. by use of <code>faketime</code>).
Comment thread
jonatack marked this conversation as resolved.
Outdated

Note on GPG key capabilities on smartcard/hardware devices:

Expand Down