Skip to main content
The amulet namespace is used for Canton coin specific operations.

Availability and extensibility

The amulet namespace is an extended namespace that requires configuration. You can initialize it either during SDK creation or later using the extend() method. Option 1: Initialize during SDK creation
Option 2: Add amulet namespace later using extend()

Configuration

The AmuletConfig type defines the configuration for the amulet namespace:
  • auth: Authentication configuration for accessing the validator and scan services
  • validatorUrl: URL of the validator service
  • scanApiUrl: URL of the scan API
  • registryUrl: URL of the amulet registry

Key changes from v0 to v1

v0 used the tokenStandard controller with implicit party context set via sdk.setPartyId() and the instrumentId and instrumentAdmin were passed in explicitly to each function. v1 uses the amulet namespace where you:
  • Pass partyId explicitly to each operation
  • Initialize the namespace with configuration, which determines the instrumentAdmin and instrumentId
  • Access operations through logical groupings (traffic and preapproval)
Creating preapprovals

The below example demonstrates the full process of renewing and cancelling preapprovals:
Full example: create, renew, and cancel preapprovals
Buy Member Traffic

Check Traffic Status

Refer to the following example for more information:
Full example: buy member traffic
Tap The is useful for testing against LocalNet or Devnet.

Migration reference

See also