Splice 0.7.5
Upgrade Canton to 3.5.15. Updated Docker base image to 1.0.13, which updates gRPC health probe to v0.4.55. The client IP used for per-client-IP HTTP rate limiting is now extracted based on a configurable, ordered list…
- The latest release in the 0.7 line.
- Newest Splice: Splice 0.9.4
Runs on Canton 3.5.15
Open the release notes (opens in a new tab)docs.canton.network
-
Upgrade Canton to
3.5.15. -
Docker
- Updated Docker base image to 1.0.13, which updates gRPC health probe to v0.4.55.
-
Scan & SV App
-
The client IP used for per-client-IP HTTP rate limiting is now extracted based on a
configurable, ordered list of headers,
rate-limiting.client-ip-headers, which defaults to["x-forwarded-for", "x-real-ip"]. The first configured header that is present and whose value parses as an IP literal is used; for comma separated values (as inX-Forwarded-For) the first entry is taken. Configuring an empty list disables the extraction, in which case no per-client-IP rate limit is enforced. This replaces therate-limiting.trusted-client-ip-headerandrate-limiting.enable-client-provided-ip-headersoptions, which have been removed.
-
The client IP used for per-client-IP HTTP rate limiting is now extracted based on a
configurable, ordered list of headers,
-
Scan App
- The endpoints
/v1/state/acsand/v1/holdings/stateare now deprecated, please use the new counterparts,/v2/state/acsand/v2/holdings/state. The only change between v1 and v2 is the type of the pagination token (afterin request,next_page_tokenin response), which is now a String instead of a number. The deprecated V1 endpoints are planned to be removed in Splice 0.9.0.
- The endpoints
-
SV App
- The SV app OpenAPI specification now annotates endpoints
(
x-jvm-package: sv_public) with anx-external-audienceextension, which is one ofvalidators(endpoints that validator operators need to reach),svs(endpoints that only other SVs need to reach) ornone(endpoints that do not need to be reachable from outside of the SV node’s own deployment, e.g. the CometBFT endpoints). SV operators can use this annotation to restrict the external exposure of their SV app: only the endpoints of a given audience need to be reachable from the corresponding networks, and endpoints with an audience ofnone, as well as endpoints without anx-external-audience, do not need to be exposed to external traffic at all. Note that endpoints currently marked for exposure to validators will be phased out in the foreseeable future, and replaced by a new limited number of endpoints which should be made available only on DevNet.
- The SV app OpenAPI specification now annotates endpoints
(