Skip to content

Compliance module design doc#367

Draft
tynes wants to merge 2 commits into
mainfrom
compliance-module
Draft

Compliance module design doc#367
tynes wants to merge 2 commits into
mainfrom
compliance-module

Conversation

@tynes

@tynes tynes commented Feb 26, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Introduce an optional compliance screening layer for cross-chain transactions in the OP Stack bridge
  • Design covers L1 deposit screening (OptimismPortal2), L2 withdrawal screening (L2ToL1MessagePasser), configurable IRule-based checks, and owner-controlled approve/reject/settle flows with ETH custody and refunds
  • Includes full failure mode analysis

Documents

  • protocol/compliance-module.md — design doc
  • security/fma-compliance.md — failure mode analysis

🤖 Generated with Claude Code

tynes and others added 2 commits May 5, 2026 15:34
Introduce an optional compliance screening layer for cross-chain
transactions in the OP Stack bridge. The design covers L1 deposit
screening via OptimismPortal2, L2 withdrawal screening via
L2ToL1MessagePasser, configurable IRule-based checks, and owner-
controlled approve/reject/settle flows with ETH custody and refunds.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
The L1 deposit and L2 withdrawal flow diagrams had several inaccuracies
compared to the detailed design: missing donateETH() on the happy path,
incorrect owner/settle flow, wrong labels ("Deposit" instead of
"Withdrawal"), and missing nonce reservation step. Updated both diagrams
to accurately reflect the contract interactions described in the doc.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@tynes
tynes force-pushed the compliance-module branch from da27548 to 4ae1c71 Compare May 5, 2026 19:34
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