MonsieurNicolas

I see @ThomasBrady . Yeah we definitely need some idea of potential saving for each part (like: is skipping crypto high impact) of this as it potentially creates a bunch...

Couple questions on the xdr structure. In ``` typedef TransactionEnvelope DependentTxCluster; typedef DependentTxCluster TxExecutionThread; typedef TxExecutionThread ParallelTxExecutionStage; ``` Why do we need each thread to have a "DependentTxCluster"? I would...

> We don't really want to set different base fees per stage I am pretty sure we will need this fairly rapidly in follow up versions. As soon as the...

I guess you have a couple scenarios to keep in mind: * can we get "ultra realistic benchmarks"? For this, we may want to expand on https://github.com/stellar/supercluster/blob/main/src/FSLibrary/MissionHistoryPubnetPerformance.fs -> picking "interesting"...

> That is not very useful for Soroban given that historical traffic won't have much volume for a while. It's also not very interesting to know that we could close...

Yeah I thought from the title and description of the issue that you were trying to come up with a way to answer questions like: * did build X introduce...

@leighmcculloch I imagine that we're consistently using "C" strings with tooling outside of core?

good -- we want people to use strkeys to avoid sad typos, so only this issue should be left then

I think I found more occurences of this. When decoding `TransactionMeta` using the `print-xdr` command, I get `contractID` in hex: ```json "sorobanMeta": { "ext": { "v": 0 }, "events": [...

mmm that would be a breaking change as contractID is type 1 not 0. This is annoying: it is plausible that we would want accounts to emit events at some...