diff options
| author | Nicholas Johnson <nick@nicholasjohnson.ch> | 2023-10-20 00:00:00 +0000 |
|---|---|---|
| committer | Nicholas Johnson <nick@nicholasjohnson.ch> | 2023-10-20 00:00:00 +0000 |
| commit | d25b7743fb26bbe4f1648048214d17da621d070beb202630c31ae044906b3ed7 (patch) | |
| tree | 027fd6c53f7fd949df4c7a22e87a90dea96cb0e88dd3dfb8dc988b43213bac1a /content/entry/future-proof-digital-timestamping.md | |
| parent | b42f03332f305b08390e71ee498135e46ab6d1fe67ebcf85d9a37a666901d464 (diff) | |
| download | journal-91ce27ae3422bf470ca72073625692a4346cd2cf594c990a18f3f8b8d7c7ebc3.tar.gz journal-91ce27ae3422bf470ca72073625692a4346cd2cf594c990a18f3f8b8d7c7ebc3.zip | |
Use SWHIDs in Software Heritage linkssignify-signature-7
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 10db49c..d09eb2a 100644 --- a/content/entry/future-proof-digital-timestamping.md +++ b/content/entry/future-proof-digital-timestamping.md @@ -25,7 +25,7 @@ Then I found [OpenTimestamps](https://opentimestamps.org/). It's based on Bitcoi Also, OpenTimestamps has an extremely efficient design compared to other Bitcoin timestamping schemes. Thanks to OpenTimestamps' clever use of [Merkle trees](https://petertodd.org/2016/opentimestamps-announcement#merkle-trees), it can timestamp unlimited data using only 1 transaction. Other Bitcoin timestamping software uses 1 transaction per timestamp, an extremely wasteful, inefficient design. At least OpenTimestamps isn't that bad. -So anyway, I created a timestamped Git commit and tagged it [timestamp-1](https://archive.softwareheritage.org/browse/release/e4726ec79a43e28c616e4d5f3db0efe2237b23f9/?origin_url=https://git.nicholasjohnson.ch/nicksphere-gmi&release=timestamp-1&snapshot=fb9bef300f9b939382f5656232d95377c8630a10). I wrote the concatenated commit data of the timestamped commit to [a file](/resource/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. +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](/resource/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>'. |