v1.7.0-rc.3: Multichain

v1.7.0-rc.3: Multichain

The below release notes cover the updated version release candidate for multichain

Note: v1.7.0-rc.1 is the final redistribution release on top of multichain. v1.7.0-rc.2 is the final MOOCOW release on top of multichain.

Release Manager

@ypatil12 @eigenmikem

Highlights

🚀 New Features

• The ECDSACertificateVerifier and BN254CertficateVerifier have new storage/introspection for checking a reference timestamp: isReferenceTimestampSet

⛔ Breaking Changes

• The preprod/testnet contracts have been redeployed with fresh addresses since this upgrade is not upgrade safe from v1.7.0-rc.0
• CrossChainRegistry: All references to AVSs setting transport destinations have been removed. OperatorSets will be transported to all supported chains. See PR #1512
  • createGenerationReservation no longer takes in a list of chainIDs
  • addTransportDestinations and removeTransportDestinations have been removed
  • getActiveTransportReservations and getTransportDestinations(operatorSet) have been removed
• ECDSACertificateVerifier
  • getTotalStakes has been renamed to getTotalStakeWeights
  • signedStakes has been renamed to totalSignedStakeWeights
• KeyRegistrar
  • checkKey has been deprecated in favor of isRegistered

🛠️ Security Fixes

• In the OperatorTableCalculator, we now hard-code the Generator's table root and reference timestamp. See PR #1537

🔧 Improvements

• The ECDSACertificateVerifier now has a calculateCertificateDigestBytes, which returns the non-hashed bytes of the digest. See PR #1542
• Clarify stakes are stake weights and update natspec for clarity. See PR #1541
• Add getTotalStakeWeights and getTotalStakeWeights to BN254CertificateVerifier. See PR #1552

🐛 Bug Fixes

• Allow 0 staleness periods for the ECDSACertificateVerifier. See PR #1540
• Allow ECDSA certificates to be valid even if not on the latest reference timestamp to match BN254 certificates. See PR #1540
• Added a new parameter: TableUpdateCadence to the CrossChainRegistry. We now enforce that maxStalenessPeriod is >= TableUpdateCadence to prevent bricking Certificate Verification. See PR #1536
• Prevent replay of past certificates on new environments. See PR #1547

What's Changed

• feat: invalid staleness period prevention by @ypatil12 in #1536
• feat: cleaner generator updates by @ypatil12 in #1537
• chore: symmetric BN254 and ECDSA checks by @ypatil12 in #1540
• feat: add calculateCertificateDigestBytes to ECDSA cert verifier (#1532) by @ypatil12 in #1542
• refactor: remove transport interface by @ypatil12 in #1512
• chore: clean up natspec round 1 by @ypatil12 in #1541
• fix: storage gap in CrossChainRegistry by @ypatil12 in #1541
• test: more integration test scenarios and checks file by @eigenmikem in #1548
• fix: prevent globalTableRoot certificate replay upon newly instantiated CertificateVerifiers/OperatorTables by @ypatil12 in #1547
• fix: Multichain (Pt 2) fixes by @nadir-akhtar in #1549
• chore: KeyRegistrar clarifications by @ypatil12 in #1551
• chore: CertificateVerifier clarifications by @ypatil12 in #1552
• chore: CrossChainRegistry clarifications by @ypatil12 in #1553

Full Changelog: v1.7.0-rc.0...v1.7.0-rc.3