Version 1.0.2

• Fixed a bug in revocation identified by @lookyman in #17 caused by NULLs
• Added bin/fix-nulls.php which will clean up the NULLs in the existing database (setting them to FALSE or 0, depending on the database driver).

Version 1.0.1

• Fixed typos
• Changed VERSION constant for API responses to reflect the API's 1.0 release status.
• Typo fixes (mostly pull requests #14 and #16)
• Began listing (chronicling, even) client-side implementations in the README file.
• Made it easier to find the Chronicle API URL:
  • Added a hyperlink on the index page to the API.
  • If you send a Client ID header to the index page, you get redirected to the API.

Version 1.0.0

This is mostly a bugfix release from v0.5.1, thanks to our public testing server.

• Fixed SQL definition inconsistencies.
• Verified that replication works.
• Verified that cross-signing works.
• More unit tests.
• Fixed documentation warts.

Version 0.5.1

This just fixes an annoying routing issue, and adds a page of documentation for setting up Chronicle on Ubuntu 16.04.

Version 0.5.0

Two new optional features:

1. Publish metadata when clients are added or removed.
2. Request timeouts (to defeat replay attacks). This changes the
   register/revoke APIs to require a request-time parameter in the
   JSON body, which will be required to fall within a time interval.

Version 0.4.0

• Lots of whitespace/docblock improvements
• Fixed typos that were causing SQL errors
• Reworked our exceptions; we now don't throw any base Error or Exception objects
• Chronicle now has a logo (an SVG image created with a text editor)

This is probably the last pre-1.0.0 release.

Version 0.3.0

• We now have some basic end user Documentation for installing and running a Chronicle
• Replication improvements:
  • Chronicle now verifies the Ed25519 signature of each message when pulling from the source
  • Replication data is now publicly accessible via the new /chronicle/replica URI
  • On a regular time interval, Chronicle can publish the latest hashes for all of its replicas (we call this scheduled attestation)
• Added a CLI testing apparatus for testing locally

Version 0.2.0

• Changed what goes into each link in the Blakechain
  • Old : H(data)
  • New: H(time || publickey || signature || data)
• Implemented cross-signing
  • Publish your summary hash at a point in time to another Chronicle
• Implemented replication
  • Mirror one (or more) other Chronicles to a separate database table, validating every new hash along the way.

Version 0.1.0

This is the first unstable release of Chronicle, a Sapient-secured microservice that stores messages in a cryptographically verifiable append-only data structure.

The goal of the first release was to get a rough HTTP API exposed. In the near future, we'll add features (including cross-signing; see #2) and support for various database backends.