v2.34.0

Release date: February 02, 2026

Introducing synchronize anchor forwarding strategy

We've added a new synchronize forwarding strategy for anchors that provides enhanced data consistency between your ledger and bridge systems.

How it works

When using the synchronize strategy, anchor operations (create, update, sign) are:

1. Validated locally in your ledger to ensure they would succeed
2. Forwarded to the configured bridge for processing
3. The bridge's response is validated and synchronized back to your ledger
4. Both systems maintain consistent state

This strategy is ideal when you need:

• Strong consistency guarantees between ledger and bridge
• The bridge to be the source of truth for anchor data
• Automatic synchronization of bridge-side changes back to your ledger

Configuration

Set the forwarding strategy to synchronize in your processing policy configuration.

Check About Processing Policies for more details.

Supporting amount in anchors

Now it's possible to set amount to anchor records. The amount property is an optional integer field that must be greater than 0 when set. This allows anchors to carry quantitative information directly within the anchor record itself.

Adding source to anchors

Users can now set source to anchors. It can either be a string signifying an address, or an object with properties handle and custom.

Composite handle and custom reference:

{
  ...,
  source: {
    handle: 'tel:31988875664',
    custom: {
      prop: 'value'
    }
  }
}

Value being just an address:

{
  ...,
  handle: 'tel:31988875664'
}

Improvements

• Support multiple types for anchor symbol. It can either be a string signifying a handle, or an object with properties handle and custom.

{
  ...,
  symbol: {
    handle: 'usd',
    custom: {
      prop: 'value'
    }
  }
}

It remains backwards compatible with the value being just a handle.

{
  ...,
  symbol: 'usd'
}

• Support multiple types for anchor target. It can either be a string signifying a handle, or an object with properties handle and custom.

{
  ...,
  target: {
    handle: 'tel:319883388@bank',
    custom: {
      prop: 'value'
    }
  }
}

It remains backwards compatible with the value being just a handle.

{
  ...,
  target: 'tel:319883388@bank'
}