v2.33.0

Release date: January 22, 2026

New features

Anchor Insights dashboard (currently available in dev environment)

Studio now includes an Anchor Insights dashboard on the Anchors page, providing visualizations of anchor metrics:

Total anchors: All-time count with breakdown by type (email, phone, etc.)
New anchors: Daily creation trend over the selected period
Updated anchors: Daily update activity over the selected period
Anchors by participant: Distribution across participants
Creation by participant: Stacked bar chart showing daily anchor creation grouped by participant

The dashboard includes date range filtering with preset periods (7d, 30d, 90d) and custom date pickers.

This feature is currently in technical preview and is not yet available in production environments.

Ledger drop

Ledgers can now be dropped using the API, CLI, or SDK. This is a critical, irreversible operation: when a ledger is dropped, all data that belongs to that ledger is permanently removed.

Scoped deletion: Only the targeted ledger and its associated data are removed.
Access control: Only signers with explicit drop permissions on Ledger can perform this operation, ensuring that destructive actions are tightly controlled.

You can drop a ledger using:

API: DELETE /ledger or POST /ledger/drop (with a signed drop record payload and x-ledger header)
CLI: ledger drop <handle>
SDK: await sdk.ledger.drop().init().hash().sign([{ keyPair }]).send() (requires setting active ledger with sdk.setActiveLedger(handle))

This feature is currently in technical preview and is not yet available in production environments.

Ensure your ledger is not configured with open permissions (e.g. broad any rights or overly permissive policies). If a malicious or mistaken signer can gain drop access on an open ledger, they can permanently delete all of its data. See About Authorization for more details about authorization.

Improvements

[studio] Properly show error in studio homepage to users that don't have any permission.

Navigation menu sections are now automatically hidden when users lack access to all child items within that section. Previously, empty menu sections could appear even when all children were inaccessible.

Added support for using intent on wallet routing filters

Wallet routing filters now support accessing intent-level data through the ctx.intent and ctx.claim context objects. Previously, filters could only target claim data directly. This enhancement allows you to create more sophisticated routing rules based on intent properties.

For example, you can now filter routes based on the intent's schema:

{
  "handle": "hpb",
  "bridge": "hpb",
  "routes": [{
    "filter": {
      "ctx.intent.data.schema": "p2p"
    },
		"action": "accept"
  }],
	"access": [ ... ]
}

Improved `changes list` output for CLI

The <record> changes list command in the CLI now provides a more detailed and user-friendly output. These changes includes:

[cli] Introduced 'signers' and 'moment' columns for changes list output table.
[cli] Reversed order of rows (from desc to asc) in the changes list output table. Latest changes now appear at the bottom of the list.
[cli] Replaced data columns (e.g 'custom', 'bridge') in changes list output table with a single 'differences' column. This column summarizes changes made to the record in a color coded diff format.

Fixes

[ledger] Fixed an issue where pagination query parameters were not parsed correctly while using anchor bridge forwarding. The pagination decorator now properly handles both nested and flat query parameter formats.
[ledger] Improve performance of list queries for all records on API