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

Do magic with the modelling wand #9

Merged
merged 16 commits into from
Nov 19, 2020

Conversation

thomaseizinger
Copy link
Contributor

We swing the magic modelling wand and produce two constructors on TxOut that make it a lot easier to produce valid transactions!

The whole commitment is 33 bytes long with the last 32 bytes being
the x-coordinate of the public key.
The original asset commitment can always be retrieved from the
ConfidentalTxOut.
That is, most important to least important with increasing level
of detail based on the order you encounter the structs as you
read through the existing type definitions.

Order of `impl` blocks for traits are at the bottom but unsorted.
By providing two constructors for a ConfidentialTxOut, we can make
it easier for users to properly construct a valid transaction that
follows all the invariants that need to be upheld.
This also simplifies the calling site massively because we don't
have to iterate over the inputs several times.
We always pass random bytes in here, I think this is just used for
entropy.
We try to hide the actual wally APIs from the user by providing
meaningfully named functions on the actual types that we want to
construct.
@thomaseizinger thomaseizinger merged commit 1ae5d93 into comit-network:master Nov 19, 2020
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.

2 participants