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

transactions #8

Open
lyndsysimon opened this issue Jun 2, 2015 · 1 comment
Open

transactions #8

lyndsysimon opened this issue Jun 2, 2015 · 1 comment

Comments

@lyndsysimon
Copy link
Owner

Define how transactions will be built and signed.

@lyndsysimon
Copy link
Owner Author

Note that this may include several objects. First pass at an architecture:

TransactionInput - a Key, plus an amount to send
TransactionOutput - a Key, plus an amount to receive
Transaction - a collection of inputs and outputs. Includes validation that inputs are equal to outputs and that the transaction is syntactically valid.

For complex transactions, a TransactionScriptNode abstract object would have a number of subclasses, each of which represented a single script operation to be included.

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