Raw tx: how to configure change address with exact calculation

[python-cardano]

Raw tx: how to configure change address with exact calculation

[cffls]

Unfortunately, the library doesn't have a function to calculate the change from an unbalanced transaction. There is a private function under txbuilder, _add_change_and_fee, but it relies on private fields in the txbuilder, so it is hard to use it without txbuilder.

[34r7h]

Yea I saw the source code in builder but didn't fully follow. I'll study a bit more. Tell me if I'm off.. I should add up all Lovelace going out, calculate tx fee (help me here: based on byte size of all inputs, outputs, metadata, signatures, and min tx fee?) Then make sure some output exists to take the leftover Lovelace and tokens as change from used inputs. Is that correct or what's missing? I think a change and fee helper would be an awesome feature to consider exposing as a standalone method.

…

On Thu, Jun 30, 2022 at 11:55 PM Jerry ***@***.***> wrote: Unfortunately, the library doesn't have a function to calculate the change from an unbalanced transaction. There is a private function under txbuilder, _add_change_and_fee, but it relies on private fields in the txbuilder, so it is hard to use it without txbuilder. — Reply to this email directly, view it on GitHub <https://github.com/cffls/pycardano/issues/57#issuecomment-1171539492>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AATSTIFZHXGHKMYH5WR3E63VRXRABANCNFSM52KGCWZQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[cffls]

txbuilder is the ultimate interface that helps you to automatically compute change and tx fee. I don't think there is a more straightforward way than using txbuilder itself to provide change and fee computation.

[34r7h]

Hey I started to roll my own transaction builder to address edge cases that kept coming up. It has a lot to do with utxos with low balances that I'm wrestling with, including a problem of blockfrost sending multiple utxos for the same transaction id if a token was minted, no doubt reflecting the lovelace dumped in a token but still creating code complexities of what's available and what to return. I'm deep in this rabbit hole now.. i've kept my original createtx function that uses your builder so will respond with the code to reproduce in some time.