Alexey Kuleshevich

> It seems like a long time ago it was agreed we'd follow a "push-based" dependency upgrade system. > I personally don't agree with it, because it leads to problems...

> Can we then add a requirement to bump to the latest Plutus release before making a ledger release? Ledger team rarely if ever makes releases. Again, it is the...

> I think we do care that this is the case (since it ensures each node release has the latest possible Plutus library versions). In other if you really care...

That is also what I am trying to say, is that Ledger has nothing to do with this. This message should be explicitly added to `cardano-api`! If there are no...

> in order to bump plutus version in cardano-api and still have it compile, the ledger must have bumped the plutus version first. You are totally missing my point when...

> There is a link to conway formal spec? Yes, the full spec is implemented in Agda: https://github.com/IntersectMBO/formal-ledger-specifications There are links in the readme to PDF version as well.

My notes that came out of the audit with @WhatisRT and the final outcomes: * > ExUnits do not have an upper bound. Enforce to maxBound :: Word64 with well...

Closing this ticket as duplicate of #4078

I've learned recently from Duncan that the reason why segregated witness serialization was implemented on Cardano. It was only because ["Bitcoin did it this way" with BIP-141](https://github.com/bitcoin/bips/blob/master/bip-0141.mediawiki), which I'd argue...

As part of this task we should also reach out to other core team leads to confirm that this is something that we can indeed change and no other team...