Releases: digital-asset/canton
Releases · digital-asset/canton
canton v0.8.3
- Participant nodes will automatically configure the ledger-api to share the same database as canton (instead of being fixed to an in-memory store).
This change allows the ledger-api to persist data between restarts of canton.
Postgres and H2 are supported. - Upgraded to DAML 0.13.51
- Azure deployment templates
canton v0.8.2
- Updated documentation and demo.
canton v0.8.1
- Upgraded to DAML SDK 0.13.46
canton v0.8.0
- Added an admin command
transfer_search
to search in-flight transfers - Upgraded to DAML SDK 0.13.43
canton v0.7.0
- Upgrade to DAML 0.13.39.
- Binding all server endpoints to localhost only by default.
- Add admin command for manual migration of databases.
- Using Scala types in the admin console instead of protobufs.
- Transfer messages are encrypted and contract contents remain hidden from the mediator and sequencer.
- Added extensive documentation to Canton configuration options.
canton v0.6.0
- Added a flag to restrict the capabilities of a namespace delegation and thereby preventing
the delegated key to be able to revoke the root certificate.
canton v0.5.2
- Ability to dynamically change log level on canton console
- Reconciliation: compute, exchange and verify real ACS commitments
- Updated documentation on how to configure persistence and apis.
- Changed domain api configuration structure
(using domains.name.public-api instead of domains.name.server.public)
canton v0.5.1
- Use slick config for database config
- Support for DAML models with non-stakeholder actors
canton v0.5.0
- Support for persisting single dimension event logs in a database
- Upgrade to DAML 0.13.38
- Fixed bug that prevented the demo to run on Windows
- Upgraded Ammonite dependency to 1.8.2 (from 1.6.5), fixing demo issues
with Java13
canton v0.4.3
- Fixed race condition in identity manager which lead to disfunctional
domains.