Splice 0.7.1
Upgrade Canton to 3.5.12. Duplicate wallet operations submitted with the same command id (e.g. tap, transfer, token standard transfers) now return the original result idempotently instead of HTTP 409. This aligns with…
- A newer release in the 0.7 line: Splice 0.7.5
- Newest Splice: Splice 0.9.4
Runs on Canton 3.5.12
Open the release notes (opens in a new tab)docs.canton.network
-
Upgrade Canton to
3.5.12. -
Wallet app
-
Duplicate wallet operations submitted with the same command id (e.g.
tap,transfer, token standard transfers) now return the original result idempotently instead ofHTTP 409. This aligns with standard idempotency-key semantics: a second request with a previously accepted command id receives a200response with the same result as the first. Concurrent duplicates, where no submission has completed yet, are still rejected. -
TransferPreapprovalProposals are now accepted if there is an existing one but it has expired.
-
Duplicate wallet operations submitted with the same command id (e.g.
-
CantonBft
- Increase the default segment length by 4x to reduce performance impact from epoch switches.
-
Validator App
-
Added a
typeparameter to validator config’sreward-sharing-config-by-partyoption. When this is set toexternal, it indicates that the assignment of reward coupons to beneficiaries is being managed by a process external to the validator app, and thus the validator app’s automation does not assign or mint the unassigned coupons. Thetypedefaults tobuilt-inpreserving the existing behavior where the validator app will either mint the unassigned rewards coupons, or assign them to beneficiaries if configured. See the reward-sharing documentation for details: https://docs.canton.network/global-synchronizer/splice-fundamentals/reward-sharing#reward-sharing Example enabling external sharing automation for a party::=
-
Added a