diff options
| author | Nicholas Johnson <mail@nicholasjohnson.ch> | 2024-11-23 00:00:00 +0000 |
|---|---|---|
| committer | Nicholas Johnson <mail@nicholasjohnson.ch> | 2024-11-23 00:00:00 +0000 |
| commit | 52d5e9267a1fdadd5e91d8e096753f2b39b1abee61c733346078d510ce619645 (patch) | |
| tree | 942ae08cfc44b1b882467bc888d6e95dff28bd99b3f9517ed7cb61b7aee35f50 /content/entry/future-proof-digital-timestamping.md | |
| parent | c78a77591ed7344cec4305b3e3238b1d15b9b1d55cf27139168c08d1ad78cffd (diff) | |
| download | journal-52d5e9267a1fdadd5e91d8e096753f2b39b1abee61c733346078d510ce619645.tar.gz journal-52d5e9267a1fdadd5e91d8e096753f2b39b1abee61c733346078d510ce619645.zip | |
Convert angle brackets to square brackets
Hugo was rendering the angle brackets as raw HTML and omitting them.
Diffstat (limited to 'content/entry/future-proof-digital-timestamping.md')
| -rw-r--r-- | content/entry/future-proof-digital-timestamping.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/content/entry/future-proof-digital-timestamping.md b/content/entry/future-proof-digital-timestamping.md index 653c1f6..fa83e55 100644 --- a/content/entry/future-proof-digital-timestamping.md +++ b/content/entry/future-proof-digital-timestamping.md @@ -27,7 +27,7 @@ Also, OpenTimestamps has an extremely efficient design compared to other Bitcoin So anyway, I created a timestamped Git commit and tagged it [timestamp-1](https://archive.softwareheritage.org/swh:1:rel:e4726ec79a43e28c616e4d5f3db0efe2237b23f9;origin=https://git.nicholasjohnson.ch/nicksphere-gmi;visit=swh:1:snp:fb9bef300f9b939382f5656232d95377c8630a10). I wrote the concatenated commit data of the timestamped commit to [a file](/timestamp-1.txt) in case you're interested to see what it looks like. The software works in a very elegant fashion. It even maintains compatibility with non-OpenTimestamps Git clients, so GnuPG can still verify the commit signature. -The base64-encoded timestamp appended to the commit data includes all the necessary hashes to build the Merkle path from the tagged commit to the merkle root included in the Bitcoin transaction. Using './ots --git-extract <filename>' on any file in the nicksphere-gmi repo present at the timestamped commit, you can extract an ots proof file which you can then verify with './ots --verify <filename>'. +The base64-encoded timestamp appended to the commit data includes all the necessary hashes to build the Merkle path from the tagged commit to the merkle root included in the Bitcoin transaction. Using './ots --git-extract [filename]' on any file in the nicksphere-gmi repo present at the timestamped commit, you can extract an ots proof file which you can then verify with './ots --verify [filename]'. Thus future readers of my journal and historians will be able to verify that each entry was written by a human with no major external dependency other than the widely witnessed Bitcoin ledger. There are caveats to that, but luckily I thought up ways around all of them. |