chore(deploy): add ReceiverAcrossV4 v1.0.0 on robinhood (EXSC-682)

[0xDEnYO]

Which Linear task belongs to this PR?

Fixes EXSC-682

Why did I implement it this way?

ReceiverAcrossV4 was never deployed on Robinhood chain (the diamond log carried an empty entry), which is why Across destination calls / 1-step routes are disabled there. This PR records the production deployment of ReceiverAcrossV4 v1.0.0 to robinhood at 0x90dd81bD07763f39dF31D0089B61520461557D71 (CREATE3, standard pipeline via deployContractToNetworks.sh). Registration in the diamond was proposed via diamondUpdatePeriphery as a timelock-wrapped Safe proposal.

Production rollout status:

Chain	Contract address	Safe nonce
robinhood	0x90dd81bD07763f39dF31D0089B61520461557D71	19

Notes:

• deployments/robinhood.diamond.json (production registry) updates only when the timelock-wrapped cut executes — intentionally not part of this PR.
• Contract is verified on Blockscout (via the v2 standard-input API — the instance's etherscan-compat /api route rejects valid submissions) and verified:true is set in the MongoDB deployment log.

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

The Robinhood deployment manifests add and populate a deployed ReceiverAcrossV4 address while preserving the existing GasZipPeriphery entry.

Changes

Robinhood deployment configuration

Layer / File(s)	Summary
Add ReceiverAcrossV4 address mapping deployments/robinhood.json, deployments/robinhood.diamond.json	Adds the deployed ReceiverAcrossV4 address to both Robinhood deployment configurations; the existing GasZipPeriphery entry remains unchanged.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

• lifinance/contracts#2086: Updates the deployed ReceiverAcrossV4 address in deployment mappings for another network.

Suggested labels: waitForBackend

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title clearly names the deployment change and target chain, matching the main update in the PR.
Description check	✅ Passed	The description follows the template and covers the task, rationale, and checklists, with only minor checkbox items left incomplete.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch exsc-682-deploy-receiver-across-v4-robinhood

---

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.}