-
Notifications
You must be signed in to change notification settings - Fork 219
feat: Add ezeth plasma #1189
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: Add ezeth plasma #1189
Conversation
🦋 Changeset detectedLatest commit: be20488 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
📝 WalkthroughWalkthroughAdds plasma support across EZETH prod and staging warp routes: inserts plasma token connections and a new plasma EZETH entry in configs; expands deploy files with plasma interchainSecurityModule/ISM blocks and hooks across many domains; tweaks swell protocolFee. Purely declarative YAML additions and one value change. Changes
Sequence Diagram(s)sequenceDiagram
autonumber
participant Sender as Sender Router
participant Hook as Plasma Hook
participant Routing as Plasma Routing ISM
participant Domain as Domain ISM(s)
participant Val as Validators
participant Receiver as Receiver Router
rect #f8fbf2
Note over Sender,Hook: New plasma path added
end
Sender->>Hook: Submit message (gas, protocolFee)
Hook->>Routing: Submit for verification
Routing->>Domain: Route to domain-specific ISM or fallback
par Multisig verifications
Domain->>Val: merkleRootMultisig check
Domain->>Val: messageIdMultisig check
end
Domain-->>Routing: Aggregated decision (threshold)
Routing-->>Hook: Verification result
alt verified
Hook-->>Receiver: Deliver message
Receiver-->>Receiver: Execute action
else rejected
Hook-->>Sender: Reject / no delivery
end
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes Possibly related PRs
Suggested reviewers
Poem
Pre-merge checks and finishing touches❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✨ Finishing touches🧪 Generate unit tests (beta)
📜 Recent review detailsConfiguration used: CodeRabbit UI Review profile: CHILL Plan: Pro 📒 Files selected for processing (1)
✅ Files skipped from review due to trivial changes (1)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
🧹 Nitpick comments (1)
deployments/warp_routes/EZETHSTAGE/renzo-stage-config.yaml (1)
144-147
: Keep the token symbol consistentThe metadata swamp’s got mixed signage: this entry spells the symbol
EZETH-STAGE
while every other chain still saysEZETHSTAGE
. That mismatch can trip up anyone reading configs side‑by‑side. Let’s keep the labels uniform.- symbol: EZETH-STAGE + symbol: EZETHSTAGE
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (4)
deployments/warp_routes/EZETH/renzo-prod-config.yaml
(16 hunks)deployments/warp_routes/EZETH/renzo-prod-deploy.yaml
(18 hunks)deployments/warp_routes/EZETHSTAGE/renzo-stage-config.yaml
(1 hunks)deployments/warp_routes/EZETHSTAGE/renzo-stage-deploy.yaml
(18 hunks)
🧰 Additional context used
🪛 Gitleaks (8.28.0)
deployments/warp_routes/EZETHSTAGE/renzo-stage-deploy.yaml
[high] 2516-2516: Detected a Generic API Key, potentially exposing access to various services and sensitive operations.
(generic-api-key)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
- GitHub Check: check-warp-deploy
🔇 Additional comments (1)
deployments/warp_routes/EZETHSTAGE/renzo-stage-config.yaml (1)
191-193
: Double-check the stage labelOne quick sanity check: this block still calls the asset “Stage 7” while the surrounding routes all moved to “Stage 9”. If that isn’t intentional, please bump the name so the crew isn’t scratching their heads later.
Check Warp Deploy Summary
Last updated: 2025-10-10 14:38:04 UTC |
Description
This PR adds Plasma to EZETH production and staging configs
Backward compatibility
Testing
Summary by CodeRabbit
New Features
Chores
Documentation