Chronicle Versions Save

Public append-only ledger microservice built with Slim Framework

v1.3.1

2 years ago
  • Version 1.3.0 added a SQL table but did not include a mechanism to run the associated SQL file.
  • To address this, update to v1.3.1 and then run php bin/make-tables.php 02-v1.3.0 and the new table will be created.

v1.3.0

2 years ago
  • #43 - Support a public list of replica instances (optional)
  • Command line utility for changing the public key for a replication source (in replica instances)
  • Migrated from Travis CI to GitHub Actions
  • Requires PHP 7.1 or newer
  • Supports PHP 8.1

v1.2.0

4 years ago
  • Implemented #53 -- You will now be warned if a public key doesn't match what you input (or, if you omit a public key for setting up replication, it will ask you to confirm it before proceeding)
  • There is now a /replica/{unique_id} endpoint, just to index each replica's contents. (Before: it was a 404.)
  • Implemented #34 -- You can now configure your Chronicle to paginate the /export and /since endpoints.
  • Implemented #61 -- You can now configure your Chronicle to cache HTTP responses for a short period of time, to help mitigate extreme load (i.e. what we've been experiencing in our public instances).

v1.1.5

4 years ago
  • Fix double-quoting error with some SQL drivers
  • Update sodium_compat minimum to 1.11.0

v1.1.3

5 years ago
  • Fixes an issue with replication instances (#41).

v1.1.2

5 years ago

Fixed a bug that caused publishing new records to fail.

v1.1.1

5 years ago

Fixed an issue with the replication scripts not running due to the multi-instance feature breaking EasyDB.

v1.1.0

5 years ago
  • The first record in a Chronicle now has a prevhash of NULL. This allows foreign key constraints to be added to the database table definition.
  • When publishing files to the Chronicle, anything that cannot be safely encoded in JSON will cause the write to fail.
    • This is preferable to causing the export API to break forever.
    • We recommend base64url-encoding any binary blobs before sending them to Chronicle.
  • We now have documentation for Chronicle's internals.
  • New feature: concurrent instances
  • Several command line scripts return JSON messages if you pass the -j flag, to make them more useful in automation scripting (without forcing users to parse the standard CLI output messages manually).

v1.0.4

5 years ago

This is mostly a boyscouting release.

  • Updated the minimum version of dependencies (EasyDB, sodium_compat)
  • Removed duplicate code
  • Improved docblocks and comments
  • Chronicle is now 100% type-safe

v1.0.3

6 years ago
  • Fixed various typos and documentation warts
  • Fixed a minor bug in revocation returning an invalid JSON message