v2.17.0
Ledger release v2.17.0
Release date STG: November 20, 2024
Release date PRD: November 28, 2024
OAuth support for bridges
As mentioned in About Bridges , the secure
property for a bridge describes the mechanism used for accessing the bridge from ledger. This functionality was not implemented until now.
It was not possible to secure the communication between ledger and bridge and the only options available to guarantee security were JWT tokens and verifying in the bridge that the messages for each endpoint are signed by ledger.
Now, we implemented the option to define secrets directly in the bridge record by using a new secret
field.
Detailed documentation is still pending and will be added as soon as possible.
Settlement and scheduling
In the previous release we added support for scheduling and in this release it is improved and extended with support for scheduling settlement reports.
As part of the settlement process, we added support for filters in bridge traits.
Detailed documentation is still pending and will be added as soon as possible.
Intent statuses management
Each intent status is calculated by the ledger from the present proofs, where, for example, an intent becomes prepared
once both source and target sign a proof saying they are prepared, and then ledger creates a final proof. This requirement for everyone to prepare was basically hardcoded into the DTC logic of 2-phase-commit (2PC) for intents even though it is not explicitly expressed.
We made a change so it is expressed through a policy. This means that ledger user with proper permissions can now configure status policies for shaping the intents’ processing flow.
Layouts documentation
We added documentation for the layouts, new ledger functionality that defines templates for creating or updating ledger records.
Documents added:
- About Layouts
- How to read a layout
- How to apply a layout
- How to sync a layout to a ledger
- How to display differences between a layout and a ledger
Improvements & Fixes
- fixed security issues in lib dependencies
- added support for
$nin
operator in actions, records and filters - updated RTP layouts to support settlement
- improved filtering to allow partial matches for circles
- refactored access builder and access service
- implemented caching records in access builder
- this is a temporary solution until we use a distributed cache in our architecture
- fixed bug when status was set to
created
when updating record from CLI - improved rtp-e2e-tests with adding new tests and descriptions
- fixed bug where ledger was throwing
core.unexpected-error
instead of a valid error for the case when target wallet was not specified correctly - added testing of our published libs in CI
- improved CLI server conection, i.e. usage of command
minka server connect
- purpose of this was to enable connection to ledger using a proxy URL
- changed
Executed effect action message
in dispatcher service toscheduled effect action message
- enabled setting record status based on proofs with
custom.status
field in create requests
Studio release v2.17.0
Release date STG: November 20, 2024
Release date PRD: November 28, 2024
Studio localization
Studio is the tool for administrators and participants in a payment system based on Ledger to interact in an easy and friendly manner with ledger configuration, onboarding, and operating process.
Currently, most customers are clearinghouses from Republica Dominicana and Colombia. Their operations and security teams sometimes struggle to understand systems that are not localized to Spanish language.
We introduced to option for localization and localized the Studio to Spanish language. Users can now (in Settings section) choose between English and Spanish.
Settlement and scheduling
In the previous release we added support for scheduling and in this release it is improved and extended with support for scheduling settlement reports.
Detailed documentation is still pending and will be added as soon as possible.
Improvements & Fixes
- improved filtering of records in Studio by removing lag
- added search option for drop downs with long lists