txlib endorse - #229
Open
robknight wants to merge 2 commits into
Open
Conversation
Move object helpers, state-header types, replay construction, test support, and transaction tests out of lib.rs. Re-export the public API so callers remain unchanged.
Require every spent object's nullifier to be accompanied by an EndorseSpend proof over {state_header, tx_final}, preventing reuse across transactions or grounding states.
Allow TxBuilder to consume states supplied through proven openings and endorsements, and add Rekey paths that split proof work between key holders.
robknight
force-pushed
the
txlib-endorse
branch
from
August 26, 2026 16:42
46340ae to
089de71
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds an extra "endorse" statement to spends in transactions. This ensures that every spend/nullification has a statement from the object owner (someone who knows the full object state), attesting to this and to the transaction context (which includes the transaction hash chain). For single-user transactions this is trivial, and has a small overhead of one extra custom statement per nullification. However, this unlocks joint transactions, in which any event - insert, mutate, or delete - can be endorsed by an object owner, with that endorsement handed to someone else who submits the transaction. This means that an endorsement requires the owner's participation, and the owner can ensure that the transaction being committed to really is the transaction described to them.
Stack created with GitHub Stacks CLI • Give Feedback 💬