-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FR] - Balance existing transaction #867
Comments
BTW I could contribute this directly and this feature request is also to test waters whether this would be appreciated? |
@ch1bo This is a very interesting use case and is very much appreciated. If you can submit the PR it would be awesome, if not, just let us know and we will find it a place on the TODO list. |
This would enable a more standalone operation of some of hydra tools, |
If we were to do this, it would be useful for https://github.com/tweag/cooked-validators too, right @mmontin? |
Adding example files I got from https://github.com/v0d1ch |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 120 days. |
Internal (anyone could benefit though)
Area
Transaction building
Describe the feature you'd like
I would like to use the
cardano-cli
to balance a transaction that was drafted by another application. Assuming we have a transaction already built with body and witnesses (redeemers) by a DApp in a transaction envelopetx.json
and some signing keywallet.sk
which owns ADA to pay fees:Would connect to the
cardano-node
as usual to fetch various information (utxo owned by user, protocol parameters, system start and era history) and balance the transaction. That is:Alternative with slightly smaller scope: Take only an input to use for paying fees and change address, very much like
transaction build
.Describe alternatives you've considered
Obvious alternative is to do all this in the DApp itself, but balancing a transaction is a generic process and not application-specific. Also, this would tie the transaction creating code very much to the "source" of where UTxO, protocol parameters etc. are fetched from. Having it in the
cardano-cli
, a dedicated client to thecardano-node
, would keep it separated from e.g. an alternative workflow that usesblockfrost
.Additional context / screenshots
We encountered this while designing a command line tool to create certain smart contract transactions in the Hydra protocol. More details here: cardano-scaling/hydra#1574
The text was updated successfully, but these errors were encountered: