Skip to content

docs: add deployed contract addresses #36

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.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
0xrcinus wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs: add deployed contract addresses #36

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
47 changes: 47 additions & 0 deletions content/docs/smart-contracts/deployed-addresses.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,47 @@
---
title: Deployed Addresses
description: Contract addresses for OIF deployments across supported chains
---

# Deployed Addresses

This page lists the deployed contract addresses for OIF across all supported networks.

<Callout type="info">
OIF uses deterministic deployment (CREATE2) for settlement contracts, so addresses are consistent across chains.
</Callout>

## OIF Settlement Contracts

The core OIF settlement contracts are deployed on all supported mainnets at the same addresses:

| Contract | Address |
|---|---|
| **InputSettlerEscrow** | `0x15eA18EAcD9C35b454CF1456ed1bD05636B46147` |
| **OutputSettlerSimple** | `0x1DCE289d62C2068584C5D0CFb5C1fD538e832847` |

### Supported Mainnets

| Chain | InputSettlerEscrow | OutputSettlerSimple |
|---|---|---|
| Ethereum | `0x15eA18EAcD9C35b454CF1456ed1bD05636B46147` | `0x1DCE289d62C2068584C5D0CFb5C1fD538e832847` |
| Arbitrum | `0x15eA18EAcD9C35b454CF1456ed1bD05636B46147` | `0x1DCE289d62C2068584C5D0CFb5C1fD538e832847` |
| Base | `0x15eA18EAcD9C35b454CF1456ed1bD05636B46147` | `0x1DCE289d62C2068584C5D0CFb5C1fD538e832847` |
| Linea | `0x15eA18EAcD9C35b454CF1456ed1bD05636B46147` | `0x1DCE289d62C2068584C5D0CFb5C1fD538e832847` |
| Optimism | `0x15eA18EAcD9C35b454CF1456ed1bD05636B46147` | `0x1DCE289d62C2068584C5D0CFb5C1fD538e832847` |
| Scroll | `0x15eA18EAcD9C35b454CF1456ed1bD05636B46147` | `0x1DCE289d62C2068584C5D0CFb5C1fD538e832847` |
| zkSync | `0x15eA18EAcD9C35b454CF1456ed1bD05636B46147` | `0x1DCE289d62C2068584C5D0CFb5C1fD538e832847` |
Comment thread
coderabbitai[bot] marked this conversation as resolved.

<Callout type="info">
Settlement contracts are not yet deployed on testnets.
</Callout>

## Broadcaster Infrastructure

For broadcaster contract deployments (broadcaster, receiver, pusher, buffer, provers, and copies), see the [broadcaster deployments repository](https://github.com/openintentsframework/broadcaster/tree/main/deployments).

## Related Docs

- **Core Contracts**: Read about [InputSettlerEscrow and OutputSettler](/docs/smart-contracts/core-contracts) implementations

@coderabbitai coderabbitai Bot Apr 16, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

鈿狅笍 Potential issue | 馃煛 Minor

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

- **Deployment Guide**: See the [Deployment Guide](/docs/smart-contracts/deployment) for production deployment procedures
- **Supporting New Networks**: Learn about [adding new chain support](/docs/smart-contracts/supporting-new-networks)
1 change: 1 addition & 0 deletions content/docs/smart-contracts/meta.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,7 @@
"overview",
"quickstart",
"core-contracts",
"deployed-addresses",
"deployment",
"supporting-new-networks"
]
Expand Down