Skip to content

fix(messaging): log malformed settlement messages - #650

Open
zakazaka95 wants to merge 1 commit into
dojoengine:mainfrom
zakazaka95:fix/621-log-malformed-messages
Open

zakazaka95 wants to merge 1 commit into
dojoengine:mainfrom
zakazaka95:fix/621-log-malformed-messages

Conversation

@zakazaka95

Copy link
Copy Markdown

Closes #621.

Both settlement collectors now emit an operator-visible warning with block, transaction index, transaction hash, and conversion reason before skipping a malformed event or log. Focused regressions cover the Starknet and Ethereum paths and assert both the skip behavior and required diagnostic context.

Validation: git diff --check and rustfmt content checks pass; Windows test/check attempts are blocked before katana-messaging by existing Linux-only sp1-jit and reth-mdbx/libclang dependencies, so GitHub CI is the authoritative runtime check.

Make both settlement collectors emit an operator-visible warning with block, transaction index, transaction hash, and conversion reason before skipping malformed messages.
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.

messaging: collector silently drops malformed L1-handler messages

1 participant