◎ Radar

### Context As part of #4665 we changed the Daml code for the existing `AmuletAllocation` and `AmuletTransferInstruction` to also compute an early expiry time for them, which is by default 90 days after their creation time. We did however not adjust the triggers to make use of that early expiry, a

# Release of Canton 3.5.1 Canton 3.5.1 has been released on May 27, 2026. ## What’s New ### Contract Keys #### Overview Canton 3.5 introduces contract keys. Compared to a similar feature available in Canton 2.x, there are two notable differences: - The keys are not unique, meaning multiple contracts may share the same key. - Negative lookups are not validated. As a consequence, application developers must ensure key uniqueness through external enforcement mechanisms. Contract keys are avai

Alternative to #5683 — same bug, different design. Posting both so maintainers can pick. PR #5545 set `automaticSilentRenew={false}` on the `react-oidc-context` provider and removed `offline_access` from the scope request. Either change on its own would have been fine; together they leave the UIs w

PR #5545 set `automaticSilentRenew={false}` on the `react-oidc-context` provider and removed `offline_access` from the scope request. With both in place the UIs no longer use any refresh token, so users get bounced to the IdP every time the access token expires, which is every 5 minutes on a default

## Development Fund Proposal Submission **Proposal file:** [`/proposals/daml-upgrade-compatibility-linter.md`](https://github.com/ayushsingh82/canton-dev/blob/proposal/daml-upgrade-compatibility-linter/proposals/daml-upgrade-compatibility-linter.md) --- ## Summary An open-source static analysis t

I would like to ask, if this is approved, for the CC lock mechanism, is it mandatory to use the application owner's party ID, or can we collaborate with a liquidity provider to provide a party ID that locks the CV in the name of my application, for example?