Radar

<!-- I confirm that, if this is a feature request that has security implications, I already contacted security@digitalasset.com and followed the [responsible disclosure policy](https://digitalasset.com/security/). I confirm that this is not a question or a request for technical support by the commu

Kraken bumped into this. We need to exclude `sv_user` and `sv_party_id` from the comparison AND ADD A TEST. Surface symptom: ``` 2026-10-20T15:35:47.781Z [⋮] DEBUG - o.l.s.a.a.HttpRequestLogger:validator=validator_backend (22c996af9e9fa52ad0113badfae0f1ef-no_w3c_trace_context--adef65533abe26e9) -

## Problem Statement As of PQS 3.6.0, password is now mandatory, but has to be specified in two places when using the helm chart Align it so that password can be specified in one place and used by both the pqs feeder process and the pqs pruner cronjob (if pruning is turned on) https://github.com/

We should avoid breaking changes by deprecating any `logger: Logger` arguments exposed in publicly exported functions. Should also include an example in the docs on how to configure logtape at the application-level

- **Scope:** Enable bulk storage on every SV. - Ask the SVs to enable bulk storage (`scan.bulkStorage.enabled`), with the docs from #7753. - Make the S3 config mandatory once every SV has it. - Before enabling on MainNet: review the Pulumi operator service account permissions on the buckets, s

Bulk storage objects don't carry a migration id, but the update segments and the progress cursors (staging and committed, updates and snapshots) are `TimestampWithMigrationId`, ordered by migration id first. Migration ids no longer change, so they only add confusion (see the discussion on #7599, whe

Canton changes: - [5a0fb8f46d](https://github.com/DACH-NY/canton/commit/5a0fb8f46da7cf518632c156ca373cc76c7b3c48) rgugliel-da: Follow up for: Throw when trying to serialize a message to an unknown… ([#36445](https://github.com/DACH-NY/canton/pull/36445)) - [9efeaf4e3a](https://github.com/DACH-NY/ca

Bumps [axios](https://github.com/axios/axios) from 1.18.1 to 1.20.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/axios/axios/releases">axios's releases</a>.</em></p> <blockquote> <h2>v1.20.0 — August 19, 2026</h2> <p>This release hardens runtime option

## Development Fund Proposal Submission **Proposal file:** proposals/2026-10-PixelPlex-token-publication-standard.md ### Applicant **Organization:** PixelPlex **Author / Primary Contact:** Yury Korzun, yury.korzun@pixelplex.io **Champion:** Name and organization of the Dev

Canton changes: - [cf35c18dbd](https://github.com/DACH-NY/canton/commit/cf35c18dbd9e8d1f89e085cef685b8339d0b6f69) fabiotudone-da: [main forward port] CantonBFT, benchmark: support recently added sequencing parameters ([#36200](https://github.com/DACH-NY/canton/pull/36200)) ([#36269](https://github.

Canton changes: - [cf35c18dbd](https://github.com/DACH-NY/canton/commit/cf35c18dbd9e8d1f89e085cef685b8339d0b6f69) fabiotudone-da: [main forward port] CantonBFT, benchmark: support recently added sequencing parameters ([#36200](https://github.com/DACH-NY/canton/pull/36200)) ([#36269](https://github.

Towards ChainSafe/canton-extending-mainnet#129. This is the Daml half, so it can make the 0.10.0 cut; the operator app's advance and take-back, the top-up change and the LocalNet test follow on the 0.10.3 train. Summary: `GovernanceParameters` gains `outageAdvance : Int`, the traffic in bytes the o

Closes ChainSafe/canton-extending-mainnet#121 Summary: the SV governance UI can now display and propose a `SRARC_RegisterSynchronizer` vote. Three commits, because the first is a defect fix on its own. **Displaying a vote (c43f50f).** The UI's action list is a closed union, so a registration vote