fix(lez-core): preserve generic transaction envelope - #26
Draft
3esmit wants to merge 1 commit into
Draft
Conversation
3esmit
force-pushed
the
fix/generic-response-envelope
branch
from
August 2, 2026 04:10
574c02e to
606622f
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
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.
Summary
Return the generic transaction envelope on every
send_generic_public_transactionerror path.Root cause
Validation and FFI failures used the transfer-only response shape, so callers of the generic API could not classify a legitimate rejection.
Verification
nix build --no-link .#unit-tests -Lnix build --no-link .#default -Lon restacked head606622fCloses #25.
Dependency and ABI gate
Remain draft. This PR is stacked on #24. Do not update a source pin or merge until #24 reconciles its source-#45 ABI expectation and source logos-blockchain#37's logos-blockchain#43-coordinated Testnet ProgramId migration gate is resolved.
After the combined parent and source stack is integrated, rerun module validation before promotion.