Splice 0.3.3
Added the openid scope to their authorization requests to comply with the OpenID Connect specification. Scan instances will now run a background process that replicates the history of the network from before their SV…
- 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
- All UIs (except the experimental app manager and splitwell UIs)
- Added the
openidscope to their authorization requests to comply with the OpenID Connect specification.
- Added the
- Scan
- Scan instances will now run a background process that replicates the history of the network from before their SV node joined. This affects data returned by the
/v1/updatesendpoints, missing data for other API endpoints (such as/v0/transactions) will be backfilled in a future update. This one-time process is expected to take up to a few days to complete, depending on the size of the missing history. During this time, scan instances will consume slightly more compute and networking resources than usual, and the/v1/updatesendpoint will return an error until the replication has finished on that particular instance. Progress on your own scan instance can be monitored through thecn_history_backfilling_*metrics. - The
/v1/updatesendpoint now excludes updates resulting from ACS imports. This change was already mentioned in the 0.2.5 release notes, but due to a bug was not actually implemented until now.
- Scan instances will now run a background process that replicates the history of the network from before their SV node joined. This affects data returned by the