DAML MODEL UPGRADE ISSUE in Splice 0.5.11 impacting PQS users

1. #1Wayne Collier27-02-2026source ↗
   The following DAML package versions were introduced by Splice 0.5.11, and are effective on DevNet as of this week.

   name version amulet 0.1.16 amuletNameService 0.1.17 dsoGovernance 0.1.22 validatorLifecycle 0.1.6 wallet 0.1.17 walletPayments 0.1.16

   
   
   These Daml model versions are currently scheduled to go live on TestNet (March 3rd) & MainNet (March 10th).
   
   However, Splice 0.5.11 deployments this week on TestNet have exposed an issue where in certain cases, "uploaded but not-yet vetted" packages break some assumptions in PQS. In order to avoid these issues, validator operators that use PQS are advised, as part of the 0.5.11 deployment, to make the following configuration changes:
   
   

   • in k8s, set the Helm value on the validator app maxVettingDelay to 0m
   • in docker-compose, add to the validator container an environment variable  ADDITIONAL_CONFIG_MAX_VETTING_DELAY with value canton.validator-apps.validator_backend.max-vetting-delay = 0m