Minka Ledger Docs
Release Notes

v2.1.0

Ledger release v2.1.0

Release date: March 8, 2023

Multitenancy

We’ve implemented support for multitenancy. This means that now Ledger is able to support multiple clients/tenants (ledgers) on one Ledger instance. Active ledger will be resolved by looking at a subdomain. For example: https://ledger.ldg-stg.one will resolve ledger with handle ledger and https://minka.ldg-stg.one will resolve ledger with handle minka.

CLI is update to support new command for selecting a ledger:

$ minka ledger select
? Ledger: sandbox

For existing clients/instances there will be no change, unless explicitly communicated.

Improved bridge support

We have aligned Bank integration tutorial with all the latest changes from this version with focus on API schema changes.

Other important changes

  • API schema changes to improve API consistency
    • changed signer schema to format
    • changed meta.signatures to meta.proofs
    • changed proofs (formerly signatures) schema to method
  • changed bridge payload schemas
    • to be future-proof, we have changed source, target and symbol parameters from strings to objects to enable us to include additional metadata in those parameters
  • updated 2-phase commit payload
    • commit Actions are sent to POST /credits/:handle/commit and POST /debits/:handle/commit
    • abort Actions are sent to POST /credits/:handle/abort and POST /debits/:handle/abort
  • implemented API versioning: changed base URL to v2
    • all API call will now have additional v2 part. For example, instead of calling /signers/{handle}/changes/{change} ****you should call /v2/signers/{handle}/changes/{change}
  • supported proofs verification in SDK
  • updated error codes. See more here: Error reference
  • updated documentation
    • updated access object example in API reference documentation
    • updated API spec for intent processing
    • updated existing docs with multitenancy support
  • enabled security: enforcing signature checks for some Ledger operations
    • validate record access - GET by handle and PUT

Improvements & Fixes

  • additional proofs created by ledger. All responses from ledger are now signed by the ledger
  • show warning in CLI if the version is not up to date
  • /status API endpoint returns the deployed ledger version
  • changed access rules format to object
  • simplified record updates via SDK
  • added handle to event payloads
  • improved error messages on the SDK
    • added custom.moment which is is ISO format "2023-02-20T21:42:10.279Z" to each proof
    • print the error in the minka *** show commands (if there was an error regarding specified record)
  • improved CLI error message - now it contains more information about the error that occurred
  • record events are now dispatched via shared base service
  • changed the security so that the bearer only has read permissions for now

Studio

N/A

On this page