Redeploy EcoFacet

[ezynda3]

Which Jira task belongs to this PR?

Why did I implement it this way?

Checklist before requesting a review

• I have performed a self-review of my code
• This pull request is as small as possible and only tackles one problem
• I have added tests that cover the functionality / test the bug
• For new facets: I have checked all points from this list: https://www.notion.so/lifi/New-Facet-Contract-Checklist-157f0ff14ac78095a2b8f999d655622e
• I have updated any required documentation

Checklist for reviewer (DO NOT DEPLOY and contracts BEFORE CHECKING THIS!!!)

• I have checked that any arbitrary calls to external contracts are validated and or restricted
• I have checked that any privileged calls (i.e. storage modifications) are validated and or restricted
• I have ensured that any new contracts have had AT A MINIMUM 1 preliminary audit conducted on by <company/auditor>

[coderabbitai]

Walkthrough

Updated deployment JSONs: EcoFacet facet addresses replaced and version bumped to 1.1.0 across many networks, Periphery gained a new FeeForwarder field (empty string) in diamond manifests, and deployments/_deployments_log_file.json received numerous new additive deployment records and some source-mapping error messages.

Changes

Cohort / File(s)	Summary
Deployment logs deployments/_deployments_log_file.json	Many new additive deployment records appended (addresses, versions, optimizer runs, timestamps, constructor args, salts, verification status, occasional source-path errors). No deletions.
Diamond manifests (facet + periphery edits) deployments/*.diamond.json — deployments/arbitrum.diamond.json, deployments/base.diamond.json, deployments/celo.diamond.json, deployments/ink.diamond.json, deployments/mainnet.diamond.json, deployments/optimism.diamond.json, deployments/polygon.diamond.json, deployments/sonic.diamond.json, deployments/tron.diamond.json, deployments/unichain.diamond.json, deployments/worldchain.diamond.json	EcoFacet facet key/address replaced (old 1.0.0 entries → new addresses) and Version updated to 1.1.0; added Periphery.FeeForwarder field set to "".
Simple deployment mappings (address updates) deployments/*.json — deployments/arbitrum.json, deployments/base.json, deployments/celo.json, deployments/ink.json, deployments/mainnet.json, deployments/optimism.json, deployments/polygon.json, deployments/sonic.json, deployments/tron.json, deployments/unichain.json, deployments/worldchain.json	EcoFacet address values updated to new deployed addresses; no other structural changes.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Changes are data-only, repetitive across many files (address/version updates and a uniform periphery field addition) with one large JSON log append; review focuses on consistency and correctness of addresses/versions.

Possibly related PRs

• EcoFacet Updates [EcoFacet v1.1.0, IEcoPortal v1.1.0] #1421 — updates EcoFacet v1.1.0 deployments and adds Periphery FeeForwarder fields across deployment manifests.
• Implement EcoFacet [EcoFacet v1.0.0,IEcoPortal v1.0.0] #1324 — introduces EcoFacet and related deployment/configuration entries used across networks.
• Deploy GlacisFacet to Fraxtal, Vana, Bob, Sophon #1346 — edits to deployments/_deployments_log_file.json that also add deployment log entries (likely overlapping log changes).

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description Check	⚠️ Warning	The PR description is largely incomplete. While the template structure is present, two critical sections are entirely blank: "Which Jira task belongs to this PR?" and "Why did I implement it this way?" These sections are essential for providing context and traceability. The checklist sections are partially completed (some items marked done, others not), but without the foundational information in the main explanatory fields, reviewers lack crucial context about why this redeployment was necessary, which Jira ticket tracks this work, and what the specific rationale is for the changes made across all deployment configurations.	Please complete the PR description by filling in: (1) the related Jira task ID or ticket number in the "Which Jira task belongs to this PR?" section, and (2) a clear explanation in the "Why did I implement it this way?" section describing the rationale for redeploying EcoFacet, why the new address is being used, and any other relevant context about this configuration update. This information is essential for code review and project tracking purposes.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The PR title "Redeploy EcoFacet" directly and accurately reflects the primary change across the entire changeset. The raw summary shows that the EcoFacet contract address has been updated to a new address across all deployment files (arbitrum, base, celo, ink, mainnet, optimism, polygon, sonic, tron, unichain, worldchain), the version has been bumped from 1.0.0 to 1.1.0, and a new FeeForwarder field was added to periphery configurations. The title clearly communicates the main objective—redeploying EcoFacet with updated deployment details—in a concise and specific manner that would be immediately understood by someone scanning the commit history.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch redeploy-eco

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

Disabled knowledge base sources:

• Jira integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between cee7231 and f2de26b.

📒 Files selected for processing (1)

• deployments/worldchain.diamond.json (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• deployments/worldchain.diamond.json

⏰ 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: run-unit-tests

Warning

Review ran into problems

🔥 Problems

Errors were encountered while retrieving linked issues.

Errors (1)

• JIRA integration encountered authorization issues. Please disconnect and reconnect the integration in the CodeRabbit UI.

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}