You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, (at-block) can emit CheckErrors which cause the transaction to be invalid, as well as the block that includes it. In Stacks 2.1, we should make it so that any error emitted by (at-block) is a RuntimeError, so at least the transaction will be mineable and fees will be collected.
The text was updated successfully, but these errors were encountered:
jcnelson
changed the title
[clarity] (at-block) errors must all be runtime errors
[clarity] All check errors must be handled as runtime errors
Jul 25, 2022
N.B. this applies to all check errors. We should not merely re-cast all check errors as runtime errors, but instead treat check errors the way we do for runtime errors -- i.e. they don't invalidate the block; they only debit the sender the tx fee (but the tx receipt should contain the original check error).
Right now,
(at-block)
can emitCheckError
s which cause the transaction to be invalid, as well as the block that includes it. In Stacks 2.1, we should make it so that any error emitted by(at-block)
is aRuntimeError
, so at least the transaction will be mineable and fees will be collected.The text was updated successfully, but these errors were encountered: