Documentation

DevNet and TestNet get reset roughly every 3 months with the resets spread out such that they never happen at the same time on DevNet and TestNet. The exact time is announced in the #validator-operations channel run by the Canton Foundation . A reset requires a full redeployment of your node and

Upgrade To a New Release This section covers the processes to upgrade Canton participant nodes and synchronizers. Upgrading Daml applications is covered elsewhere. As elaborated in the versioning guide, new features, improvements and fixes are released regularly. To benefit from these changes, th

How to query contracts and transactions using SQL Query How to query contracts that are in Active Contract Set (ACS) To fetch contracts in the ACS use the active() table function 1 which is part of Participant Query Store’s (PQS) schema and can be used as any other PostgreSQL function.

This document describes in detail what rules govern package validation upon upload and how contracts, choice arguments and choice results are upgraded or downgraded at runtime. These topics are for a large part covered in Smart Contract Upgrade. This document acts as a thorough reference. Static C

You are not required to install the exact same Daml SDK versions used to build this Splice release. These versions are provided for reference only. .dar files built by older 3.x Daml SDKs are generally compatible with the Canton version used in this Splice release. For testing the interaction of

All the apps have an extended set of configuration options which might need tuning based on different scenarios. These configurations are accepted in the HOCON format. Adding ad-hoc configuration Every app accepts extra configuration through environment variables. All the environment variables p

The PQS SQL API is provisioned directly in the PostgreSQL database. Data consumers interact with it through SQL — not through the PQS process itself. PQS data can be joined across contract tables to build projections (for example, joining holdings with account templates). The temporal offset model

Performance degrades gradually, so it often goes unnoticed until transactions start timing out or the validator falls behind on event processing. This page covers the most common performance problems and their solutions. Slow Transactions If transaction latency has increased, check these areas i

The Daml Profiler allows you to to profile execution of your Daml code which can help spot bottlenecks and opportunities for optimization. Usage To test this out, we use the skeleton project included in the assistant. We first create the project and build the DAR. dpm new profile-tutorial -

Introduction In the Canton protocol, at the high level, there are three types of transactions that need to be signed: submissions, confirmations, and topology transactions. Submissions are a request to change on-ledger state, submitted by one or more parties. Confirmations are approvals by counter

The Splice repository contains the reference applications that power the Global Synchronizer infrastructure. These applications handle validator operations, network scanning, wallet management, and super validator coordination. They serve as both production infrastructure and reference implementatio

Templates template TransferPreapprovalProposal Signatory: receiver Field | Type | Description | receiver | Party | provider | Party | expectedDso | Optional Party | The DSO party that the receiver expects to bet set on the transfer preapproval. Must be set. It is only optional due to being

Templates template AcceptedTransferOffer Signatory: sender, receiver Field | Type | Description | sender | Party | receiver | Party | dso | Party | amount | PaymentAmount | expiresAt | Time | trackingId | Text | • Choice AcceptedTransferOffer_Abort Controller: sender Returns: A

Templates template AcceptedAppPayment Signatory: sender, provider, map (\ r -> (DA.Internal.Record.getField @“receiver” r)) amuletReceiverAmounts Field | Type | Description | sender | Party | amuletReceiverAmounts | [ReceiverAmuletAmount] | provider | Party | dso | Party | lockedAmulet

• Splice.ValidatorOnboarding

Templates template Subscription Main subscription object. Signatory: subscriptionSignatories subscriptionData Field | Type | Description | subscriptionData | SubscriptionData | reference | ContractId SubscriptionRequest | Reference to the subscription request, note that the contract will no

Deprecated (since splice-0.4.10): the modules below and their workflows are deprecated and should not be used in new applications. To implement a Canton Coin payment, use the Token Standard allocation workflow instead. Note that this immediately makes your application compatible with all Token Stand

Note that these are internal modules to implement the Canton Coin specific wallet funcationality in the Splice Wallet served by a Validator Node. Avoid referencing these models in your own Daml code, as no guarantees are made about their stability and upgrade cadence. For implementing a wallet of y

Templates template BuyTrafficRequest A request by an end-user to the wallet’s automation to buy traffic for a sequencer member Signatory: endUserParty Field | Type | Description | dso | Party | endUserParty | Party | expiresAt | Time | Buy the traffic before this time. | trackingId | Tex

Templates template UsedSecret Template used by a sponsoring SV node for enforcing that an onboarding secret is used only once. Signatory: sv Field | Type | Description | sv | Party | The SV node that sponsored the onboarding. | secret | Text | An onboarding secret. | validator | Party | The

Templates template MintingDelegation The right allowing the delegate to mint rewards on behalf of the beneficiary. Signatory: beneficiary, delegate Field | Type | Description | beneficiary | Party | The party on whose behalf minting is performed. | delegate | Party | The party authorized to

Templates template ValidatorTopUpState The state of a given top-up loop. Records the last time when this validator purchased traffic for this sequencer member in order to: • allow for crash fault tolerant deduplication of traffic purchases • allow enforcing a rate limit to prevent the validat

Templates template WalletAppInstall Signatory: endUserParty, validatorParty Field | Type | Description | dsoParty | Party | validatorParty | Party | endUserName | Text | endUserParty | Party | • Choice Archive Controller: endUserParty, validatorParty Returns: () (no fields) • Cho

An example of how to build an OTC trading app for multi-leg standard token trades. Used as part of the testing infrastructure to test the DvP workflows based on the token standard. Templates template OTCTrade Signatory: venue, tradingParties transferLegs Field | Type | Description | venue |

This module provides a BatchedMarkersProxy that can be used to create multiple markers in one view. Templates template BatchedMarkersProxy Signatory: provider Field | Type | Description | provider | Party | dso | Party | • Choice Archive Controller: provider Returns: () (no fields)

Utility template for proxying token standard choices so that featured app markers are created for a wallet app provider by their users when they are using token standard workflows. You can either use this template directly, or copy the code under a different package name and a different module name

Optional package implementing common workflows of wallets using the Token Standard. Not uploaded by default to a validator node. • Splice.Util.Token.Wallet.MergeDelegation See also the module-splice-util-featuredapp-walletuserproxy-40223 for code that simplifies integrating wallets with feature

This package provides the BatchedMarkersProxy contract which can be used to create a batch of FeaturedAppActivityMarkers in a transaction with a single view which is more efficient to process. To use it first create one long-lived BatchedMarkersProxy contract and then use BatchedMarkersProxy_

Utility template for proxying token standard choices so that featured app markers are created when using extra parties for operating an app. You can either use this template directly, or copy the code under a different package name and a different module name . Note: use the WalletUserProxy if y

Optional package simplifying the integration of featured apps with the token standard. Not uploaded by default to a validator node. • Splice.Util.FeaturedApp.DelegateProxy • Splice.Util.FeaturedApp.WalletUserProxy