Patch release

Patch release solving two issues: 1. solved the incoming authentication message not matching with known tokens by skipping erroneous tokens (#40); and 2. added retries with delays for initial blockchain connections to solve cases where the API tries to connect before the blockchain node is up, e.g. after a reboot.

Release w/ Fennel implementation

This release adds native support for the Fennel blockchain (#30). It also contains general improvements to the REST interface, which now provides an endpoint the endpoint /blockchains/{blockchain}/scan to scan a blockchain for Whiteflag messages in specific blocks (#31). The transceive direction of (transmitted) messages is now preserved when the same message is later received or retrieved from the blockchain (#32). A custom JWS implementation for Fennel ensures Whiteflag authentication signatures use the native signature algorithm of the blockchain, even if the algorithm is not specified for JWS in RFC 7518 (#33); Bitcoin and Ethereum still use a workaround (#28). Last but not least, this release also has updated dependencies, some small bug fixes and general code improvements.

Main release

This version drops the beta status of the software. All required features to use the Whiteflag Protocol have been implemented and use throughout the years for the development and test of the protocol. The Whiteflag API now also has a lightweight embedded datastore. Skipped v1.0.0 to avoid confusion with all the v1.0.0-alpha and v1.0.0-beta versions. This version will be used for further Whiteflag interoperability testing, expanding the global ecosystem, and follow-on development of the protocol.

Beta version w/ Bitcoin implementation

This version contains updated dependencies, some code improvements and one major feature:
#1 - added a module to interface with the Bitcoin blockchain

Beta version w/ bug fixes and minor improvements

This version contains updated dependencies, some minor code improvements and solutions for two issues:
#19 - a bug preventing the state to be saved to a files
#20 - reverting back to v1.x of the web3.js Ethereum JavaScript API for maintainability

Beta version w/ all plannend features

Completed all features and documentation.

Alpha version w/ last issues before beta

Implemented the following issues:
#9 - originators can be updated and deleted through the REST API originators/{address} endpoint
#11 - upgraded the MongoDB client to version 3 and updated the datastore modules accordingly
#13 - the subject code and object type of signs/signals messages are now validated against the Whiteflag specification

Alpha version w/ implementation of WF test messages

Implemented Whiteflag test messages (#4) and updated test scripts, message schema and documentation accordingly. Furthermore, the REST API has been improved: 1. all endpoints are now tested against the OpenAPI definition, 2. disabled endpoint operations now return 403 instead of 404. Also improved startup and shutdown and made several minor code and logging improvements.

Note:

• the config/whiteflag.toml configuration file now has a testMessagesOnly option in the [tx] section, which, if set to true, only allows test message to be sent to prevent the accidental transmission of real messages, e.g. when testing on main blockchain networks.

Alpha version w/ bug fix and minor improvements

Fixed issue #12 which caused incorrect block number tracking when node is resyncing from scratch, with additional code refactoring in the ethereum.js module. Refactored and renamed the whiteflag.js main module. Added a manual page, and updated documentation. The package has been updated to register the man pages and the executable with the host system with npm install and npm link. Also includes updated package dependencies.

Alpha version w/ implementation of WF authentication method 2

Implemented Whiteflag authentication method 2: pre-shared token authentication (issue #3). For this, the API has been extended with endpoints to store and delete pre-shared secret authentication tokens (/originators/tokens) and to generate the related non-secret validation token to be used as validation data in A2 messages (/token/create). Please refer to the "Authentication" operations section in the Whiteflag OpenAPI description, which has been updated accordingly.

NOTE:

• the config/api.toml configuration file now includes two additional parameters to enable/disable endpoint operations: storeAuthToken and deleteAuthToken.
• the API now internally emits the messageUpdated event when an earlier received message is updated later; this event should be added to the rxStoreEvent and txStoreEvent arrays in config/datastores.toml for datastores to upsert updated messages.