Skip to content

Commit 7abef3f

Browse files
committed
Update Learn - AggLayer doc
1 parent ce44d26 commit 7abef3f

File tree

1 file changed

+10
-9
lines changed

1 file changed

+10
-9
lines changed

docs/learn/agglayer.md

Lines changed: 10 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -106,16 +106,16 @@ The solution that enables validium users to circumvent 'data withholding' attack
106106

107107
#### Proof aggregation interface
108108

109-
The `submitBatch` data interface is used to transmit proofs between chains and the AggLayer, involves the following data elements. The below table records the interface data elements, their types and brief descriptions.
109+
The `submitBatch` data interface, used to transmit proofs between chains and the AggLayer, involves the following data elements. The below table records the interface data elements, their types and brief descriptions.
110110

111111
| Field | Type | Description |
112112
| :----------------------: | :-------------: | ------------------------------------------------------------------------- |
113113
| Chain ID | Int | Identifier for chain submitting a batch and proof |
114114
| New State Root | u256 | Commitment to the updated chain state |
115115
| Batch Proof | Plonky2/3 Proof | Proof guaranteeing validity of batch of tx |
116116
| Consensus Proof | Plonky2/3 Proof | Proof of consensus for decentralized sequencers/signature for centralized |
117-
| Message Queue | Vec<Message> | LxLy message queue resulting from batch |
118-
| Calldata | Vec<Calldata> | Calldata that must be posted to Ethereum |
117+
| Message Queue | Vec&lt;Message&gt; | LxLy message queue resulting from batch |
118+
| Calldata | Vec&lt;Calldata&gt; | Calldata that must be posted to Ethereum |
119119
| Cross-Chain Dependencies | Vec<*> | Cross-chain state root dependencies and bundles that the batch builds on. |
120120

121121

@@ -127,9 +127,10 @@ The problem with the aggregation layer, as described, is that it suffers from hi
127127

128128
Currently, proving time for a batch is a few minutes, and batches are posted to Ethereum every 30-60 minutes, which prohibits fast cross-chain messaging and interoperability.
129129

130-
In order to reduce latency to levels that make cross-chain interactions feel like using a single chain, we need to safely confirm batches before:
131-
1. A proof is generated (validity).
132-
2. A batch is posted to Ethereum (finality).
130+
In order to reduce latency to levels that make cross-chain interactions feel like using a single chain, we need to safely confirm batches before:
131+
132+
1. A proof is generated (validity).
133+
2. A batch is posted to Ethereum (finality).
133134

134135

135136
#### Finality
@@ -164,9 +165,9 @@ The `SubmitBatchWithoutProof` data interface is used to post batches to the Aggl
164165
| :------------------------: | :------------: | :-------------------------------------------------------------------------- |
165166
| Chain ID | Int | Identifier for chain submitting a batch and proof |
166167
| New State Root | u256 | Commitment to the updated chain state |
167-
| Consensus Witness | Vec<Signature> | Witness required to verify consensus for a chain |
168-
| Message Queue | Vec<Message> | LxLy message queue resulting from batch |
169-
| Calldata | Vec<Calldata> | Calldata that must be posted to Ethereum |
168+
| Consensus Witness | Vec&lt;Signature&gt; | Witness required to verify consensus for a chain |
169+
| Message Queue | Vec&lt;Message&gt; | LxLy message queue resulting from batch |
170+
| Calldata | Vec&lt;Calldata&gt; | Calldata that must be posted to Ethereum |
170171
| *Cross-Chain Dependencies* | Vec<*> | *Cross-chain state root dependencies and bundles that the batch builds on.* |
171172

172173

0 commit comments

Comments
 (0)