docs: add deployed contract addresses#36
Open
0xrcinus wants to merge 1 commit into
Open
Conversation
Lists InputSettlerEscrow and OutputSettlerSimple addresses across all supported mainnets, with a link to the broadcaster deployments repository for broadcaster infrastructure contracts. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
❌ Deploy Preview for oif-docs-wip failed.
|
📝 WalkthroughWalkthroughTwo documentation assets were added: a new page describing deterministic settlement contract deployment with address tables across supported mainnets, and a corresponding metadata entry registering the page in the documentation navigation structure. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@content/docs/smart-contracts/deployed-addresses.mdx`:
- Line 45: The page uses the inconsistent contract name "OutputSettler" on line
45; update that occurrence to the exact contract name "OutputSettlerSimple" so
it matches the rest of the document and the documented contract identifiers
(e.g., InputSettlerEscrow and OutputSettlerSimple).
- Around line 18-33: The deployed-addresses.mdx page lists InputSettlerEscrow
and OutputSettlerSimple as deployed on multiple EVM mainnets but the addresses
shown (0x15eA18... and 0x1DCE28...) are actually Katana deployments; update the
document to reflect true deployments by replacing the "Supported Mainnets" table
with the actual chains and addresses (e.g., mark Katana as the chain for
0x15eA18EAcD9C35b454CF1456ed1bD05636B46147 and
0x1DCE289d62C2068584C5D0CFb5C1fD538e832847, add the correct Ethereum mainnet
address for InputSettlerEscrow 0x000025c3226C00B2Cdc200005a1600509f4e00C0 where
applicable, and indicate that OutputSettlerSimple has no Ethereum mainnet
deployment), and remove or reword the CREATE2 claim so it no longer asserts
consistent addresses across unrelated chains; edit the tables and the text
referring to InputSettlerEscrow, OutputSettlerSimple, and the CREATE2 statement
accordingly.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 84030b72-a732-49ec-ab22-e9951396cfe3
📒 Files selected for processing (2)
content/docs/smart-contracts/deployed-addresses.mdxcontent/docs/smart-contracts/meta.json
|
|
||
| ## Related Docs | ||
|
|
||
| - **Core Contracts**: Read about [InputSettlerEscrow and OutputSettler](/docs/smart-contracts/core-contracts) implementations |
There was a problem hiding this comment.
Use the exact contract name consistently (OutputSettlerSimple).
Line 45 says OutputSettler, but this page documents OutputSettlerSimple everywhere else. Please align the name to avoid ambiguity.
Suggested fix
-- **Core Contracts**: Read about [InputSettlerEscrow and OutputSettler](/docs/smart-contracts/core-contracts) implementations
+- **Core Contracts**: Read about [InputSettlerEscrow and OutputSettlerSimple](/docs/smart-contracts/core-contracts) implementations📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| - **Core Contracts**: Read about [InputSettlerEscrow and OutputSettler](/docs/smart-contracts/core-contracts) implementations | |
| - **Core Contracts**: Read about [InputSettlerEscrow and OutputSettlerSimple](/docs/smart-contracts/core-contracts) implementations |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@content/docs/smart-contracts/deployed-addresses.mdx` at line 45, The page
uses the inconsistent contract name "OutputSettler" on line 45; update that
occurrence to the exact contract name "OutputSettlerSimple" so it matches the
rest of the document and the documented contract identifiers (e.g.,
InputSettlerEscrow and OutputSettlerSimple).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Test plan
next buildpasses/docs/smart-contracts/deployed-addresses🤖 Generated with Claude Code
Summary by CodeRabbit
Release Notes