Ledger and execution

DAML.

DAML smart contracts execute under the DamlExecutor. Canton integration covers domains, parties, and contracts.

STATUS: Testnet
CRATE: tenzro-vm
STABILITY: Stable
REFERENCE: Canton 3.5+

Types

DamlContractId, DamlTemplateId, DamlParty, DamlValue, DamlCommand, DamlEvent, DamlTransaction are first-class types in tenzro-types.

CIP-56 token template

Two-step transfer flow: create → accept or reject. Party-to-address mapping with DAML Decimal string formatting.

Submit a command

Create a contract:

tenzro canton submit \
  --command-type create \
  --template Iou:Iou \
  --create-arguments '{"issuer":"Alice","owner":"Bob","amount":"100.0"}'

Exercise a choice on an existing contract:

tenzro canton submit \
  --command-type exercise \
  --template Iou:Iou \
  --contract-id <CID> \
  --choice Transfer \
  --choice-argument '{"newOwner":"Carol"}'

Canton MCP

Direct DAML interaction through the Canton MCP server at https://canton-mcp.tenzro.network/mcp. 15 tools — Canton 3.5+ JSON Ledger API: submit command (submit-and-wait), list contracts (with live ledger-end offset and FQ party id resolved via CIP-26 User Management), allocate party, list parties, list domains, list packages, get events, get transaction, get my user, health (livez + readyz + version), version (CIP feature flags), CIP-56 Canton Coin balance, AmuletRules fee schedule, connected synchronizers, DAR upload (single Content-Type at /v2/packages), DvP settle, transfer, asset creation, reconnect synchronizer.

← All docs