v2.13.0

• Ledger
• Studio (N/A)

Ledger release v2.13.0

Release date STG: July 23, 2024

Release date PRD: August 7, 2024

Labels

We introduced a new concept in the Ledger called label - a property of records that allows users to attach a label or tag anything in ledger with a descriptive name.

• find more info in the documentation: About Labels
• and here: How to manage anchor labels

Statuses

We also introduced a new, similar concept in the Ledger called status - a property of records that describe its current state on the system.

• find more info in the documentation: About Statuses
• and here: About Status Policies

Domains

We introduced a concept of domains: a namespace in ledger. They are used to separate or group all other ledger records.

Domains are optional: if domain record is not defined, users can use any domain values without restrictions. Once a first domain record is created, ledger starts enforcing domain rules which means that valid domains are only the ones defined as domain records.

• documentation for domains is still in progress and will be included in the next release

Query language

We improved the possibilities for filtering records by implementing a query language based on MongoDB syntax and implemented through query parameters.

• find more info in the documentation: About Queries
• updated docs: Lists and pagination

CLI improvements

We continued to work on improving CLI:

• allowed import and export of .pem files
• not printing access rules unless verbose is used
• verbose now prints HTTP headers
• User-Agent with CLI version included in the header
• allowed to add proofs to records
• fixed the bridge update command

Improvements & Fixes

• implemented usage of @minka/scheduler in libs/bridge-sdk
• added overrideToken field to JwtConfig so we can use ledger-sdk when sending requests from the backend
• removed LedgerSignatureStatus.Stored
• fixed handling of ledger subdomains
• fixed certificate errors that were happening for some requests
• fixed issue with wallet balances race condition for non-funded wallets
• fixed issue when ledger is created with inconsistent hash

Studio

N/A