You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/multichain/README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -77,7 +77,7 @@ The protocol proceeds in the following process:
77
77
1. AVS deploys `AVSRegistrar` , configures metadata in EL, and gets operator registration
78
78
1. AVS registers for generation/transport calling `CrossChainRegistry.makeGenerationReservation`
79
79
2. The AVS deploys an `OperatorTableCalculator`
80
-
2. At some cadence, the `Generator`` process gets all active generations from the `CrossChainRegistry` against the latest `finalizedBlock`
80
+
2. At some cadence, the `Generator` process gets all active generations from the `CrossChainRegistry` against the latest `finalizedBlock`
81
81
1. It then creates and signs a `globalTableRoot` of all operator table commitments
82
82
3. The transporter will generate a Certificate to validate that the Eigen Labs Operator signed off on the `globalTableRoot`. The root is then transported to ALL destination chains
83
83
4. Lastly, the transporter will update all Operator Tables with a certificate. The sidecar will generate the proof data to then update tables via the `OperatorTableUpdater`
0 commit comments