Skip to content

Commit

Permalink
Apply suggestions from code review
Browse files Browse the repository at this point in the history
Co-authored-by: Blessing Krofegha <[email protected]>
  • Loading branch information
cpengilly and krofax authored Oct 31, 2024
1 parent fdb6866 commit 337f95e
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions pages/stack/interop/op-supervisor.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -12,15 +12,15 @@ import { Callout, Tabs, Steps } from 'nextra/components'
Interop is currently in active development and not yet ready for production use. The information provided here may change. Check back regularly for the most up-to-date information.
</Callout>

OP Supervisor is a critical service designed to verify cross-chain messages and manage the safety of interoperability between different chains in the OP Stack. It acts as a hub for indexing data that every `op-node` needs to cross-verify with other chains.
OP Supervisor is a service that verifies cross-chain messages and manages interoperability between chains in the OP Stack. It serves as a hub where each `op-node` can index the data needed for cross-chain verification.
Some features and benefits include:

* Enables secure cross-chain message passing on the Superchain
* Provides a centralized point for managing interoperability data
* Provides a unified point for managing interoperability data
* Supports multiple networks simultaneously
* Offers potential for public endpoints to aid in node synchronization

## Cross-chain message verification
## How cross-chain message verification works

OP Supervisor verifies messages between different chains in the OP Stack, reducing the risk of invalid or malicious cross-chain interactions.⁠ It centralizes the verification process, which reduces the complexity of operating individual nodes⁠.⁠

Expand Down Expand Up @@ -61,7 +61,7 @@ For a full listing of API names, see the [`op-supervisor` client](https://github

OP Supervisor requires RPC access to all chains in the dependency set. This allows `op-supervisor` to verify cross-chain messages and sync data across multiple networks simultaneously, such as OP Mainnet and Base nodes using the same instance.

Benefits of this approach:
Benefits:

* Scalability: As the number of chains in the Superchain grows, `op-supervisor` can handle the increasing complexity of cross-chain interactions.
* Improved reliability: It enables a more redundant setup, which is good for stability in the growing ecosystem.
Expand Down

0 comments on commit 337f95e

Please sign in to comment.