Skip to content

Cardano blocks and transactions signing configuration is not deployed #3499

Closed

Description

@jpraynaud

Why

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

Activity

  1. self-assigned this
    on Aug 26, 2026
  2. alba-press commented on Aug 26, 2026

    @alba-press

    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 = 100
    • latest_block_number = 5098770

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bug ⚠️Something isn't working

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions