Skip to content
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

Create new commands for input/output encode/decode. #299

Open
evoskuil opened this issue Oct 3, 2015 · 0 comments
Open

Create new commands for input/output encode/decode. #299

evoskuil opened this issue Oct 3, 2015 · 0 comments

Comments

@evoskuil
Copy link
Member

evoskuil commented Oct 3, 2015

The tx-encode command is overly complex due to the overloading of the --output option, supporting three distinct 2/3 tuple modes. The --input option is simpler, but requires an encoded script and index tuple. The input-set command constructs an input and sets it, but doesn't use the input construction model that is used by tx-encode.

To resolve, create commands:

  • input-encode
  • input-decode
  • output-encode
  • output-decode

and modify input-set and tx-encode to accept opaque/base16-encoded input and output parameters.

@evoskuil evoskuil added this to the 3.0 milestone Oct 3, 2015
@evoskuil evoskuil modified the milestones: 4.0, 3.0 May 12, 2016
@evoskuil evoskuil removed this from the 4.0 milestone Jan 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant