You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Cardano blocks and transactions signing configuration is not deployed #3499
On deployed environments, the aggregator silently ignores the AGGREGATOR_CARDANO_BLOCKS_TRANSACTIONS_SIGNING_CONFIG_SECURITY_PARAMETER and AGGREGATOR_CARDANO_BLOCKS_TRANSACTIONS_SIGNING_CONFIG_STEP repository variables and always falls back to the Terraform default (100 / 30). The /protocol-configuration/{epoch} route then advertises a signing configuration that was never chosen, and the signers use it to compute the block numbers to sign for CardanoBlocksTransactions.
What
Fix the deployment of the aggregator to use the correct signing configuration for the CardanoBlocksTransactions.
How
Fix the deployment of the aggregator to use the correct signing configuration for the CardanoBlocksTransactions
For an external release-preprod observation before the fix: on 25 August 2026 at approximately 17:19 UTC, we fetched the newest CardanoBlocksTransactions artifacts twice, verified the newest certificate chain, and inspected its certificate-signed protocol message.
Separately, metadata.parameters.k = 5; we treated this as the Mithril protocol parameter, not the CBT block-number offset.
This matches the deployment fallback described in this issue. After the next deployment, we can repeat the same read-only check against the newest signed certificate and report whether the intended configuration is active.
Activity
alba-press commentedon Aug 26, 2026
Thanks for documenting and fixing this.
For an external release-preprod observation before the fix: on 25 August 2026 at approximately 17:19 UTC, we fetched the newest CardanoBlocksTransactions artifacts twice, verified the newest certificate chain, and inspected its certificate-signed protocol message.
The newest certificate reported:
cardano_blocks_transactions_block_number_offset = 100latest_block_number = 5098770Separately,
metadata.parameters.k = 5; we treated this as the Mithril protocol parameter, not the CBT block-number offset.This matches the deployment fallback described in this issue. After the next deployment, we can repeat the same read-only check against the newest signed certificate and report whether the intended configuration is active.