v1.0.4

Notable changes

1. Added support for IPFS v0.11+
2. Fixed an integer precision bug that can cause transaction number to clash (DB upgrade required)
3. Fixed bug on commit-reveal chain that can lead to infinite loop in resolution
4. Fixed bug where Bitcoin Core does not load the wallet previously loaded upon restart
5. Populated the controller field in DID Document resolved
6. Added more logging to MongoDB activities
7. Fixed deactivate operation and added deactivated property in resolution metadata
8. Other miscellaneous stability improvements

WARNING: Backend data model is changed in this release, both ION Core and ION Bitcoin services will auto-upgrade (re-sync) the existing DB on startup.

MAKE SURE you don't have ION Core running the latest build (v1.0.4) while ION Bitcoin is running an older version, this will corrupt ION Core's DB. Stop BOTH services and upgrade ION Bitcoin build first.

v1.0.3

1. Bitcoin Core v0.21.x support.
2. ION Core can now start without ION Bitcoin service being up.
3. Added "API mode" to allow node to serve requests using just the backend DB.
4. Fixed a bug in processing deactivate operations.
5. Fixed a couple of bugs in retry logic.

v1.0.2

	Soft-Fork	DB Change (Auto-Upgrade)	Configuration Change
Core service	No	Yes	No

1. Many reliability improvements/fixes.
2. Emitted a number of events for monitoring purposes.
3. Introduced database versioning.

v1.0.1

v1.0.1	Soft-Fork	DB Change (Auto-Upgrade)	Configuration Change
Core service	Yes	Yes	No

Core Service

1. Bug fix - Fix overwriting a partial operation to MongoDB silently fails

v1.0.0

NOTE: please use release v1.0.1 as it contains important bug fixes.

v0.11.0

v0.11.0	Soft-Fork	DB Change (Auto-Upgrade)	Configuration Change
Core service	Yes	Yes	Yes
Bitcoin microservice	Yes	Yes	Yes

Core service

1. SIP1 - Revamped file structure to improve support for light nodes in the future.
2. SIP2 - Replaced Base64URL encoding with JCS (Json Canonicalization Scheme).
3. Feature - Ability to turn on Observer and Batch Writer independently.
4. Feature - Auto DB upgrade support.
5. Feature - Relaxed CAS URL validation to allow IPFS v1 CID.
6. Bug - Fixed deactivation operation.
7. Bug - Fixed duplicate service ID being allowed.
8. Various terminology and property renames.

Bitcoin service

1. Feature - Ability to turn on/off value locking and bitcoin chain observing independently.
2. Feature - New normalized-fee algorithm.

IPFS CAS Implementation

1. Bug - Fixed incorrect IPFS pin API endpoint.

v0.10.0

v0.10.0	Fork	Persistent Store Breaking	Configuration Change
Core service	Yes	No	Yes
Bitcoin microservice	No	No	No

Core service

1. Feature - Changed IPFS CAS adaptor to use IPFS HTTP API directly.
2. Feature - Added published field in method metadata.
3. Feature - Add support for bitcoin regtest network.
4. Feature - Added new long form DID format support.
5. Feature - Implemented hashing of public key as reveal value
6. Bug Fix - Fixed long-form resolution not verifying delta size.
7. Bug Fix - Added size limit for writer_lock_id field in anchor file.

Bitcoin service

1. Fixed initialization failure when restart bitcoin service after if it has processed all the blocks.

IPFS service

1. Deprecated this service.

v0.9.0

v0.9.0	Softfork	Persistent Store Breaking	Configuration Change
Core service	Yes	No	No
Bitcoin microservice	Yes	No	Yes
IPFS microservice	No	No	No

Core service

1. Add type to DIDs.
2. Added code to abort decompression once a limit is reached.
3. Added error message for DID not found.
4. Added more colored console logs.
5. Other bug fixes.

Bitcoin service

1. Improved initialization time by 10 times.
2. Avoided unnecessary DB deletion upon start.
3. Implement relative locking to avoid hard dependency on a specific unlock block number.
4. Added code to handle database upgrade automatically with each new release.
5. Simplified normalized fee calculation.
6. Simplified bitcoin processor revert logic.
7. Other bug fixes.

IPFS service

1. Upgraded js-IPFS dependency to v0.46.0.

v0.8.2

Fork status: Not a fork*

v0.8.2	Code change	Persistent Store Breaking	Configuration Change
Core service	Yes	No*	No
Bitcoin microservice	No	No	No
IPFS microservice	No	No	No

*This release technically is a soft fork, but since we anticipate minimal impact, we release this version as a patch.

Core service

1. Handled the initial case where no general/auth keys are present in a Document.

v0.8.0

Fork status: Hard fork

v0.8.0	Code change	Persistent Store Breaking	Configuration Change
Core service	Yes	Yes	No
Bitcoin microservice	No	No	No
IPFS microservice	No	No	No

This release breaks backwards compatibility for Core service. Requires DB reset for Core service.

Core service

1. Renamed usage to purpose for public keys.
2. Update commit-reveal scheme aligns with recovery commit-reveal scheme.