Dmytro Kozhevin

Probably some simple heuristics could distinguish most of the batch transactions from the atomic sequence (that would be fair to count as 1 tx): - If all the ops in...

> The secret key SBG...API belongs to the additional signer of the GB3...7LB account, IIUC the CLI currently doesn't know of existence of multisig and simply maps this secret key...

No, this is not a constant, which is the reason for the issue. You need to fetch the `stateArchivalSettings` ledger entry and use `maxEntryTTL` from it. I'm not sure if...

It's been a while since this has been filed and we've released Soroban with 30 days. However, the semantics is not as simple: - When balance is created, it will...

Besides the points that @jayz22 has mentioned, there are important high-level issues: - Modifying the env is a protocol change and I'm not sure we have a proper mechanism for...

This issue got lost and the change didn't make it in protocol 20. We could make the change in protocol 21, but I'm not sure if maintenance cost is worth...

Sorry, I've misinterpreted your thumbs up as agreement with my proposal to close this. The maintenance cost is that since this has made it into protocol 20, we'll need to...

> Tx malformed - tx encoder/sender did something wrong > Soroban invalid - tx encoder/sender did something wrong (I'm not sure what hte full scope of errors exist here) FWIW...

This has been fixed a long time ago.

> Does https://github.com/stellar/rs-soroban-env/pull/1112 fix this for all insufficient footprints? or just nonce footprint? This issue is intended to be more general than the nonce case. It fixes only the nonce...