v2.24.0
Release date: June 4, 2025
New features
Two-Factor Authentication
We've introduced two-factor authentication (2FA) to enhance the security of Studio accounts. This feature adds an extra layer of protection by requiring both your password and a time-based one-time password (TOTP) generated by an authenticator app. Users can set up 2FA by scanning a QR code with their preferred authenticator app, and the system will require this additional verification step during login. This feature helps protect your account from unauthorized access, even if your password is compromised.
BigQuery Reporting Bridge
There is now a new bridge component that integrates with Google BigQuery to provide advanced reporting capabilities out of Ledger. Report requests are created by users from Studio or CLI. BigQuery Reporting Bridge processes the report request, and once the report is generated by Big Query service, it gets automatically and securely stored in a Google Cloud Storage (GCS) bucket. The resulting report can be previewed and downloaded from Ledger by users from inside Studio or CLI.
CLI Layout Export and Apply Local
The new layout export
command supports exporting layouts to a file. This feature allows users to save their
layout configurations for reuse in future sessions or across different machines. The exported layout can be imported
back into Ledger using the layout apply --local
command. You can read more about the commands in the How To guides
on exporting and applying layouts.
Improvements
-
[ledger] Using aggregated limits (e.g.
dailyCount
) is now configurable per ledger (disabled by default), whilemin
andmax
limits are still always enabled -
[ledger] Introduced Redis as a distributed cache store for faster and reliable responses
-
[ledger] Significantly improved performance for RTP solution reliably reaching more then 100 intents per second regardless of the number of RTP participants
-
[ledger] Added support for filtering anchors by
data.custom.documentType
anddata.custom.documentNumber
-
[ledger] Introduced ability to forward HTTP headers that ledger received from a client, to connecting bridges configured to use the forwarding feature
-
[ledger] Made
access
propery optional on entities (other thanledger
) -
[studio] Removed ability to export signer keys from Studio, making the secret key more secure
-
[cli] Added support for Delete requests for
server proxy
service -
[cli] Added option to print request details in the command prompt when request is sent through
server proxy
service
Fixes
-
[ledger] Restrict access to create new ledgers
-
[studio] Fixed a bug with
Create Bridge
button not showing in some cases -
[studio] Fixed a bug with a component that displays custom data field resulting in a failed action to show record details in some cases
-
[studio] Fixed a bug with homepage returning a 500 error when there are no symbols created in the ledger
-
[studio] Studio sidebar and top bar are now fixed preserving the layout when scrolling