Skip to content

feat: use warn_log_format for discarded messages (backport #21053)#21545

Closed
AztecBot wants to merge 6 commits intobackport-to-v4-next-stagingfrom
claudebox/backport-21053-warn-log-format
Closed

feat: use warn_log_format for discarded messages (backport #21053)#21545
AztecBot wants to merge 6 commits intobackport-to-v4-next-stagingfrom
claudebox/backport-21053-warn-log-format

Conversation

@AztecBot
Copy link
Collaborator

Summary

Backport of #21053 to v4-next.

Replaces debug_log_format with warn_log_format for messages that are discarded during processing (undecryptable ciphertext, unrecognized message type IDs). These are situations users should be aware of, so warn-level logging is more appropriate than debug.

Conflict Resolution

The cherry-pick conflicted because v4-next has a simpler process_message.nr without custom message handling. Resolution kept v4-next's structure while applying the warn_log_format change:

  • debug_log_formatwarn_log_format for invalid message from tx (line 42)
  • debug_log_formatwarn_log_format for unknown msg type id (line 94)
  • Import updated accordingly

Original author: @nchamo

ClaudeBox log: https://claudebox.work/s/d7859f91b737f065?run=1

aminsammara and others added 6 commits March 13, 2026 11:45
## Summary
- Lower `SLASH_INACTIVITY_TARGET_PERCENTAGE` from 0.8 to 0.7
- Disable `SLASH_DUPLICATE_PROPOSAL_PENALTY` and
`SLASH_DUPLICATE_ATTESTATION_PENALTY` (set to 0)
- Increase `SLASH_GRACE_PERIOD_L2_SLOTS` from 1200 to 8400
- Reduce `perBlockAllocationMultiplier` from 2 to 1.2

## Test plan
- Verify generated config files are updated after running `yarn
generate` in relevant packages
- Deploy to devnet/testnet and confirm slasher behavior matches new
parameters

---------

Co-authored-by: Aztec Bot <49558828+AztecBot@users.noreply.github.com>
This PR was created because merging `v4` into `v4-next` resulted in
conflicts.

Please resolve the conflicts and merge this PR to keep `v4-next` up to
date.

This PR was auto-generated by the `pull-v4-into-v4-next` workflow.
Keep v4-next's simpler structure (no custom message handling) while applying
warn_log_format change from the original PR.
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.

4 participants