Feat: Move ClarityRuntimeTxError into clarity and expose whether failed txs are included in block - #7486
Draft
jbencin-stacks wants to merge 1 commit into
Conversation
Move `ClarityRuntimeTxError` and `handle_clarity_runtime_error` from `stackslib` to `clarity`, and add `ClarityRuntimeTxError::is_included_in_block` plus `analysis_failure_is_included_in_block`. This will allow Clarinet to tell if a failed transaction was included in a block, and whether to charge the sender a fee and increment its nonce. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
jbencin-stacks
force-pushed
the
refactor/clarity-runtime-tx-error
branch
from
August 4, 2026 22:32
d3187e2 to
aa0fa92
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.
Description
This PR contains a couple more changes needed for Clarinet:
ClarityRuntimeTxErrorintoclarity, so it builds for WASMis_included_in_block()so Clarinet can tell if failed transaction was included in blockThis will expose information to Clarinet about why a transaction failed, which it needs to know if the transaction charges a fee and consumes a nonce
Applicable issues
Additional info (benefits, drawbacks, caveats)
Checklist
docs/property-testing.md)changelog.d/README.md)rpc/openapi.yamlfor RPC endpoints,event-dispatcher.mdfor new events)clarity-benchmarkingrepo