Skip to content

Refactor - Transaction Constructor Types #57

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

Open
wants to merge 11 commits into
base: develop
Choose a base branch
from

Conversation

DaMatrix
Copy link

@DaMatrix DaMatrix commented Aug 2, 2024

Description

This PR depends on #56 (tx-constructor), #44 (disable-p2sh), and #51 (no-address-version).

This removes the TxConstructor struct and replaces it with an enum containing all information necessary to construct each kind of transaction input.

This is advantageous not only because it forces API users to provide all necessary information upfront (and indirectly forces inputs to be valid, since), but also because it eliminates the need for intermediate TxIn values with invalid contents.

Changelog

  • Add an enum TxInConstructor with variants for each type of transaction input
  • Remove the TxConstructor struct and replace all usages of it with TxInConstructor
  • Remove the key_material BTreeMap which was used by many functions related to transaction creation; it's now redundant because all relevant information is present in TxInConstructor

Type of Change

Please mark the appropriate option by putting an "x" inside the brackets:

  • Bug fix
  • New feature
  • Enhancement or optimization
  • Documentation update
  • Other (please specify)

Checklist

Put an "x" in the boxes that apply. If you're unsure about any of these, don't hesitate to ask. We're here to help!

  • I have tested the changes locally and they work as expected.
  • I have added necessary documentation or updated existing documentation.
  • My code follows the project's coding standards and style guidelines.
  • I have added/updated relevant tests to ensure the changes are properly covered.
  • I have checked for and resolved any merge conflicts.
  • My commits have clear and descriptive messages.

Screenshots (if applicable)

If the changes affect the UI or have visual effects, please provide screenshots or GIFs showcasing the changes.

Additional Context (if applicable)

Add any additional context or information about the changes that may be helpful in understanding the pull request.

Related Issues (if applicable)

If this pull request is related to any existing issues, please list them here.

Requested Reviewers

Mention any specific individuals or teams you would like to request a review from.

@DaMatrix DaMatrix requested a review from a team as a code owner August 2, 2024 13:56
@DaMatrix DaMatrix mentioned this pull request Aug 2, 2024
11 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant