-
Notifications
You must be signed in to change notification settings - Fork 72
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
Separate tx build from simulate/sign/send #1265
Comments
What if instead of |
That's a good point. I've updated the issue above and example to reflect that it only builds a tx, no simulation, signing, or sending. |
This makes a lot of sense. There is already |
We have non-fee txn args in the config::Args already, for example the network option which impacts which network passphrase to use, and the Maybe both of these needs merging together, or maybe fees should be kept fees since fees is a reasonably complex-on-its-own set of options that benefit from bucketing together. |
I'm splitting this component of #1180 into its own issue, because I think it needs to be prioritised separately.
What
Add support for the ability to not sign and send transactions to the network and instead output their transaction XDR as base64 to stdout.
Why
The CLI signs every transactions it submits to the network. It also has the option to simulate only.
Users who wish to build a transaction and submit it at a later date or sign it on another machine need a way to perform all the operations that the CLI supports today without doing those final two steps of signing and sending. These users need the CLI to output the transaction XDR rather than performing those steps.
How
Add a
--build-only
option wherever the--source
option exists.When
--build-only
is present, commands do not simulate, sign, or send the transaction to the network. Instead the base64 encoded transaction XDR is outputted to stdout.Stdout is intentional so that the output can be piped to other programs.
Example
For example, today the following command will simulate a deploy, then build a transaction that performs the deploy, the sign the transaction with the source, then send it to the network.
For example, with this change it will be possible to build the tx without signing and submitting:
For example, after #1180 is also complete we'd have a composable set of commands:
Related
This issue is similar and related to #1264.
The text was updated successfully, but these errors were encountered: