Skip to content

Michelson NAC usage: a failing %call_evm is not included in a block - #466

Open
Migl992 wants to merge 3 commits into
etherlinkcom:mainfrom
Migl992:docs/call-evm-failures-not-included
Open

Migl992 wants to merge 3 commits into
etherlinkcom:mainfrom
Migl992:docs/call-evm-failures-not-included

Conversation

@Migl992

@Migl992 Migl992 commented Oct 16, 2026 •

Copy link
Copy Markdown

The page explains that a %call_evm whose EVM leg fails makes the whole operation fail, but not that such an operation never appears on chain.

Observed on Previewnet (2026-09-26): five raw-injected operations calling %call_evm towards reverting EVM targets (plain revert("boom"), a custom error, a missing function, a revert after a nested crossing, a nested Michelson failure) were accepted by injection/operation but never included: opL8Uf…, onogc3…, ooZv1d…, opFyT2…, oohegN…. Control experiments on the same code path: a plain failing Michelson operation (%decrement at zero, ooY5Aihm9QBkvC92ZD6Ex2pcoDHJBSw6xpzDftHULELWQKk1br8) was included with status failed, and a raw-injected succeeding %call_evm (onmRggbbEU7kiQEXVGzCGBPJKEF4cPjDpLWSM31isFXowo3Zoym) was included.

The failure is only visible when the operation is simulated (for example by Taquito's fee estimation), as a tezlink_error whose error_message is Transfer(GatewayError("Cross-runtime call failed with status 400 Bad Request: <raw revert bytes>")). Tools that wait for an on-chain receipt or confirmation never see it. This PR adds that note. Found while building nactrace.

@vercel

vercel Bot commented Oct 16, 2026

Copy link
Copy Markdown

@Migl992 is attempting to deploy a commit to the Trili Tech Team on Vercel.

A member of the Team first needs to authorize it.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant