-
Notifications
You must be signed in to change notification settings - Fork 2
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
Prototype of best-chain abstractions #12
Conversation
6f87191
to
f534e21
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's at least one comment that is either a bug or naming/design-confusion. Most other comments are suggestions but not requirements for merge.
3009fdc
to
9e50b82
Compare
9e50b82
to
29831b6
Compare
29831b6
to
6899319
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One request to delete a CI step based on the guess that it's unnecessary (because I'm allergic to unnecessary code). If it is necessary, I request we add a comment as to why (for collaborators like me where it's not obvious; it may be obvious for anyone with more github CI experience).
6899319
to
eff29f8
Compare
Signed-off-by: Daira Emma Hopwood <daira@jacaranda.org>
Signed-off-by: Daira Emma Hopwood <daira@jacaranda.org>
Signed-off-by: Daira Emma Hopwood <daira@jacaranda.org>
…ually_valid`. Also assert that all transactions in a `BCBlock` are `BCTransaction`s. Signed-off-by: Daira Emma Hopwood <daira@jacaranda.org>
eff29f8
to
3f66d02
Compare
Signed-off-by: Daira Emma Hopwood <daira@jacaranda.org>
Signed-off-by: Daira Emma Hopwood <daira@jacaranda.org>
Definitions for transactions, TXOs, validation contexts, and blocks. Some basic consistency rules are implemented for transactions and blocks, assuming a Bitcoin-like UTXO protocol but with explicit fees. This should be sufficient to require us to take account of UTXO-related issues like missing inputs and double-spends. Both transparent and shielded abstractions are modelled.
Left for future work: it isn't clear whether this modelling of anchors is sufficient, and we might also need to model transaction expiry.
refs #7