Splice 0.4.13
Increase the CPU limits assigned to the sequencer from 4 CPUs to 8 CPUs. This should avoid any throttling during periods of high load and during catch-up after downtime. State sync is disabled by default. State sync…
- A newer release in the 0.4 line: Splice 0.4.25
- Newest Splice: Splice 0.9.4
Open the release notes (opens in a new tab)docs.canton.network
- Deployment
- SV
- Increase the CPU limits assigned to the sequencer from 4 CPUs to 8 CPUs. This should avoid any throttling during periods of high load and during catch-up after downtime.
- Cometbft
- State sync is disabled by default. State sync introduces a dependency on the sponsoring node for fetching the state snapshot on startup and therefore a single point of failure. It should only be enabled when joining a new node to a chain that has already been running for a while. In all other cases, including for a new node after it has completed initialization and after network resets, state sync should be disabled.
- Observability
- Global Synchronizer Utilization dashboard now includes an average over an hour of the transaction rate.
- Canton/Sequencer Messages dashboard now includes hourly totals, and a pie chart of the distribution of message types over the last 24 hours.
- SV
- Validator Compose Deployment
- Expose Canton ledger API by default. Reference the docs for details.
- Daml
-
Fix a bug where activity record expiration had a reference to the
AmuletRulescontract which resulted in transactions failing when trying to expire an activity record for a party that has not upgraded to the latest version of the Daml models. This caused an issue on DevNet where transactions submitted by the SV app failed repeatedly which resulted in the circuit breaker getting triggered and blocking all submissions.These Daml changes requires an upgrade to the following Daml versions:
-
Fix a bug where activity record expiration had a reference to the