From d978b33510e23851ecfb7a471aed282478ab66b2 Mon Sep 17 00:00:00 2001 From: Ori Pomerantz Date: Wed, 11 Dec 2024 20:39:53 -0600 Subject: [PATCH] docs(dependency-set): specify that dependency is bidirectional As discussed by @zainbacchus in our call today. --- specs/interop/dependency-set.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/specs/interop/dependency-set.md b/specs/interop/dependency-set.md index 8c6351237..e789de8d2 100644 --- a/specs/interop/dependency-set.md +++ b/specs/interop/dependency-set.md @@ -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.