CBOR in Byron transactions

[mkazlauskas]

What is your idea? Provide a use case.

Either always include cbor in Byron transactions, or compute and set the fee

Why is it a good idea?

fee is not part of a Byron transaction body and we used cbor it to compute it.

What is the current alternative and why is it not good enough?

c7b6869 changed the behavior that was there before 6.0

[KtorZ]

I like the idea but it is going to be challenging to know what were the protocol parameters needed to compute fees at the moment of the serialization.

Perhaps instead including a size in bytes would solve your issue?

[KtorZ]

Mainnet

https://github.com/input-output-hk/cardano-configurations/blob/8a403bb2fdb23d17a25fcc14141395918b0e5be0/network/mainnet/genesis/byron.json#L14523-L14525

PreProd
https://github.com/input-output-hk/cardano-configurations/blob/8a403bb2fdb23d17a25fcc14141395918b0e5be0/network/preprod/genesis/byron.json#L111-L112

Preview

N/A (there's no Byron era on Preview)

[KtorZ]

It is tempting.

[mkazlauskas]

Probably best to leave it up to applications to compute 😅

[KtorZ]

Actually, nevermind. It's not even computable for Byron without knowing the inputs! One can compute the minimum required fee from the size, but it isn't necessarily equal to the actual transaction fee. Often, wallets would leave more.

[mkazlauskas]

Good point 😔 It means that we wouldn't actually benefit from knowing transaction size, inputs and outputs is enough. We'll have to update our application to resolve the inputs during the mapping...