Sign security parameter offset by turmelclem · Pull Request #3168 · IntersectMBO/mithril

feature(common): introduce a new BlockNumberOffset structure, and improve arithmetic operations between BlockNumber and BlockNumberOffset

turmelclem

committed

refactor(common): make CardanoTransactionsBuilder use dedicated BlockNumberOffset type

turmelclem

committed

refactor(common, aggregator): add BlockNumberOffset in CardanoBlocksTransactions SignedEntityType

turmelclem

committed

feature(common, persistence, aggregator): use BlockNumberOffset in CardanoBlocksTransactions SignedEntityType

turmelclem

committed

refactor(common, aggregator, signer): make git CardanoTransactionsSigningConfig using new the new BlockNumberOffset type

turmelclem

committed

refactor(aggregagor, common): update signable builder beacon with tuple containing BlockNumber and BlockNumberOffset, remove usage of mithril_network_configuration_provider

turmelclem

committed

feature(common): sign the blockNumberOffset for CardanoBlockTransactions

turmelclem

committed

refactor(aggregator): use BlockNumberOffset type in CardanoBlocksTransactionsSnapshot constructor

turmelclem

committed

refactor(common): move arithemic operation between blockNumber and blockNumberOffset in blockNumber

turmelclem

committed

feature(aggregator, common, internal, openAPI): add security parameter in Proof v2 routes results

turmelclem

committed

feature(client-library): verify that the computing of cardano blocks/transactionV2 proof message contain security parameter

turmelclem

committed

feature(client-CLI): show depth of the certification (security parameter) in certify table result for blocks and transactionsV2

turmelclem

committed

feature(examples): add block depth (security parameter) in result of certify command for blocks and transactionsV2

turmelclem

committed

tests(aggregator-fake): update default data with blockNumberOffset for CardanoBlocksTransactions signed entity type

turmelclem

committed

feature(aggregator): Delete blocks and transactions and related records

turmelclem

committed

refactor(chore): change CardanoBlocksTransactionsSigningConfig security_parameter from BlockNumber to BlockNumberOffset

turmelclem

committed

tests(aggregator): implemment SignedEntityType CardanoBlocksTransactions

turmelclem

committed

refactor(common): remove test case with CardanoTransactions and CardanoBlocksTransactions since beacon are different now

turmelclem

committed

chore: upgrade crate versions and `openapi.yaml` version

turmelclem

committed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Sign security parameter offset - #3168

Sign security parameter offset#3168
turmelclem merged 19 commits into
mainfrom
ctl/3098-sign-security-parameter-offset

Commits on Apr 8, 2026

feature(common): introduce a new BlockNumberOffset structure, and improve arithmetic operations between BlockNumber and BlockNumberOffset

refactor(common): make CardanoTransactionsBuilder use dedicated BlockNumberOffset type

refactor(common, aggregator): add BlockNumberOffset in CardanoBlocksTransactions SignedEntityType

feature(common, persistence, aggregator): use BlockNumberOffset in CardanoBlocksTransactions SignedEntityType

refactor(common, aggregator, signer): make git CardanoTransactionsSigningConfig using new the new BlockNumberOffset type

refactor(aggregagor, common): update signable builder beacon with tuple containing BlockNumber and BlockNumberOffset, remove usage of mithril_network_configuration_provider

feature(common): sign the blockNumberOffset for CardanoBlockTransactions

refactor(aggregator): use BlockNumberOffset type in CardanoBlocksTransactionsSnapshot constructor

refactor(common): move arithemic operation between blockNumber and blockNumberOffset in blockNumber

feature(aggregator, common, internal, openAPI): add security parameter in Proof v2 routes results

feature(client-library): verify that the computing of cardano blocks/transactionV2 proof message contain security parameter

feature(client-CLI): show depth of the certification (security parameter) in certify table result for blocks and transactionsV2

feature(examples): add block depth (security parameter) in result of certify command for blocks and transactionsV2

tests(aggregator-fake): update default data with blockNumberOffset for CardanoBlocksTransactions signed entity type

feature(aggregator): Delete blocks and transactions and related records

refactor(chore): change CardanoBlocksTransactionsSigningConfig security_parameter from BlockNumber to BlockNumberOffset

tests(aggregator): implemment SignedEntityType CardanoBlocksTransactions

refactor(common): remove test case with CardanoTransactions and CardanoBlocksTransactions since beacon are different now

chore: upgrade crate versions and `openapi.yaml` version