forked from bitcoin/bitcoin
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Make dash-tx
easier to use.
#5754
Comments
@eloyesp, the Dash tools that AJ has built might help with some of what you're asking for. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
dash-tx
is a great command to write raw transactions, but it is missing some important functionality that makes it not suitable on many contexts:Proposed solution
Add a
outmemo
option, similar tooutdata
but using ascii instead of hexa... that will simplify usage a lot.Add a
outchange
output type, that calculate a fee for the transaction (see example for more info).Add support for interactive or secure signing, as currently it requires private keys on the command line, that is really insecure. This functionality could be implemented in several ways, allowing usage of an encrypted file with private keys, adding interoperability with
pass
or just reading fromstdin
.Fee calculation
Fee calculation is important, as it is rather complex (requires knowing the size of the signed transaction) and a bad calculation risks loosing funds, so implementing this in a easy to use way will help a lot. But it requires an extra data that is currently missing, that is the input values.
Sample usage
That will create a transaction to send 0.2 to Xfa and the rest (~0.29990) to Xfb and will sign it using the privatekey that is encrypted on the file.
Context
All those functionality together would make it pretty straightforward to use MAYA without any UI, but I think that it could also help other developers play with dash transactions.
Hope that it makes sense...
The text was updated successfully, but these errors were encountered: