Splice 0.3.5
Added new metrics for the Scan app to monitor the ingestion of transactions and contract reassignments into the update history. The setting spliceDomainNames.nameServiceDomain must now be supplied for the…
- A newer release in the 0.3 line: Splice 0.3.21
- Newest Splice: Splice 0.9.4
Open the release notes (opens in a new tab)docs.canton.network
- Scan
- Added new metrics for the Scan app to monitor the ingestion of transactions and contract reassignments into the update history.
- Deployment
- The setting
spliceDomainNames.nameServiceDomainmust now be supplied for thesplice-cluster-ingress-runbookhelm chart. See thesv-helmexample. - Added a new Grafana dashboard for monitoring utilization of the Global Synchronizer, currently estimated by comparing the total number of transactions processed to those visible to the DSO party. The larger this delta is, the more likely it is that the Global Synchronizer is used for private transactions beyond those needed for operating the synchronizer itself.
- The docs image expects a new environment variable
SPLICE_CLUSTER. In production, that would be one ofdev,testormain. The cn-docs Helm chart takes this value from thenetworkNameHelm value.
- The setting
- Metrics
- All metrics named starting with
cn_now start withsplice_instead. Example Grafana configuration has been updated to match, but any custom consumers of these metrics must be updated manually.
- All metrics named starting with
- Daml
-
Restructured the Daml code of AmuletRules_BuyMemberTraffic to avoid an intermediate transfer to the DSO party before the amulets were burned. There is no change in the amount that gets burned or the rewards are issued, just a slight change in the transaction structure to accomplish this.
This requires an upgrade to the following Daml versions:
-
Restructured the Daml code of AmuletRules_BuyMemberTraffic to avoid an intermediate transfer to the DSO party before the amulets were burned. There is no change in the amount that gets burned or the rewards are issued, just a slight change in the transaction structure to accomplish this.
This requires an upgrade to the following Daml versions: