Skip to content
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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs(dependency-set): specify that dependency is bidirectional #480

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
+2 −3
Open

docs(dependency-set): specify that dependency is bidirectional #480

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
5 changes: 2 additions & 3 deletions specs/interop/dependency-set.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,9 +21,8 @@ social consensus MUST be used to determine the chain that represents the canonic
particularly impacts the block builder as they SHOULD use the chain id to assist in validation
of executing messages.

The dependency set is configured on a per chain basis and is a unidirectional relationship. This means
that it is possible to depend on a chain without it depending back. This means that it is possible
to send assets to a chain where they cannot be sent back.
Dependency is a bidirectional relationship.
If two chains use the same `op-supervisor`, they should be able to pass messages between them.

The chain id of the local chain MUST be considered as part of its own dependency set. This allows a chain
to consume logs that it has produced much more cheaply than providing a block hash proof.
Expand Down