1.35.7

• tag link - <https://github.com/IntersectMBO/cardano-node/releases/tag/1.35.7>

• tag PR -

• tag commits - <https://github.com/IntersectMBO/cardano-node/compare/1.35.6…1.35.7>

Changelogs

• cardano-api: https://github.com/IntersectMBO/cardano-node/blob/1.35.7/cardano-api/ChangeLog.md

• cardano-cli: https://github.com/IntersectMBO/cardano-node/blob/1.35.7/cardano-cli/ChangeLog.md

• cardano-node: https://github.com/IntersectMBO/cardano-node/blob/1.35.7/cardano-node/ChangeLog.md

• submit-api: https://github.com/IntersectMBO/cardano-node/blob/1.35.7/cardano-submit-api/CHANGELOG.md

Regression testing on a local cluster

protocol version 8 and SECP256K1 cost model

P2P ON - Babbage with Babbage TX	✔️
P2P OFF - Babbage with default (Babbage) TX	✔️
Mix P2P and Legacy - Babbage with default (Babbage) TX	✔️
P2P ON - Babbage with Alonzo TX	✔️
Mix P2P and Legacy - Babbage with Mary TX	✔️
P2P ON - Babbage with Shelley TX	✔️

other testing

upgrade job (1.35.6 to 1.35.7-rc1)	✔️
block production testing on network with 10 pools, 5 of them P2P, 5 of them Legacy - results (sqlite db)	✔️
sanity check submit-api REST service	✔️

Release testing checklist

1.35.7-rc1 pushed to shelley-qa	⏳
Grafana metrics OK	⏳
Regression testing against shelley-qa - results	⏳
Regression testing against preview	⏳
Sync testing ran against shelley_qa & Preview & Preprod & Mainnet (Windows, Linux, macOS)	❌*
DB re-validation testing (ledger snapshots compatibility)	✔️
Backward compatibility testing (Node with version N-1)	✔️
Check build instructions changes	✔️
Benchmarking - Report	⏳
sanity check release notes	✔️

* RAM usage for 1.35.7-rc1 is between 3 to 4GB higher than for 1.35.5.

Warning

There is a clearly visible pattern of significantly higher cardano-node RAM usage since release 1.35.5.

RAM usage for 1.35.6 was on average 2GB bigger than for 1.35.5. Now with release 1.35.7 difference grew to values between 3 to 4GB higher than for 1.35.5.

Release 1.35.7 (legacy topology) requires more than 20GB of RAM which is much more than officially recommended RAM amount (16GB).

New functionalities in this tag

New issues

Breaking changes

Component Level Test Tracking

Test Definition and Status

Quality Control	Owner	Status	Link to tests	Comments
Component level tests	Jared Corduan Damian Nadales Marcin Szamotulski Iñigo Querejeta Azurmendi Andrew Sutherland Alexey Kuleshevich	✔️	Ledger Consensus Network Crypto Plutus Core Base	Each component version that is integrated in Cardano Node is tested separately, as detailed in the component repository.
Integration level tests (cardano-node)	Jordan Millar	✔️	Cardano Node	The quality control performed when any component is integrated into the cardano-node is described in the cardano-node repository.
System level tests (cardano-node-tests)	Martin Kourim	✔️	link to tests	The System-level tests executed for any node version can be found on the cardano-node-tests webpage (this page)
UAT (community)	Samuel Leathers	⏳		We encourage our early adopters to look into the below scenarios as part of the UAT for the current tag: scenarios with different node versions, different P2P settings (only with Legacy/P2P relays, with a mix of relays) tests confirming that stake pools with P2P Single Relay does not have a competitive (dis)advantage tests with stake pools having different node versions and P2P settings (1 relay with 1.35.4 and another one with 1.35.7 + P2P Single Relay) renewal of certificates and restart of the nodes
Audits	Kevin Hammond	✔️		All reviewed audits for this release were successfully finalized.
Mixed settings/versions tests	Moritz Angermann, Jean-Baptiste Giraudeau			Not planned (complex/insufficient tooling)