Update validation to include the validation step on the sequencer (#773)

* Add block time to limits and triggers (#770) * Add block time to limits and triggers * Remove max * docs: Add special address section (#726) * Add special address section * Update starknet-state.adoc * Update starknet-state.adoc * Update special addresses based on Evyatar feedback * Update starknet-state.adoc * Reword 0x0 address * Update starknet-state.adoc * Update starknet-state.adoc * Update starknet-state.adoc * Feedback actioned * Update transaction-life-cycle.adoc (#764) * Update transaction-life-cycle.adoc In step 2 we need to write that there are to validation steps, one occurs in the gateways and again in the sequencer. I added this comment: // There is a step missing that the sequencer runs the validation again before _execute_ * Update components/Starknet/modules/architecture_and_concepts/pages/Network_Architecture/Blocks/transaction-life-cycle.adoc * Update components/Starknet/modules/architecture_and_concepts/pages/Network_Architecture/Blocks/transaction-life-cycle.adoc * Update transaction-life-cycle.adoc --------- Co-authored-by: Steve Goodman <[email protected]> Co-authored-by: JameStark <[email protected]> Co-authored-by: JameStark <[email protected]> --------- Co-authored-by: adishildan <[email protected]> Co-authored-by: Steve Goodman <[email protected]>
starknet-io · Aug 24, 2023 · 781d9d1 · 781d9d1
1 parent d9d7e32
commit 781d9d1
Showing 1 changed file with 6 additions and 3 deletions.
diff --git a/...ture_and_concepts/pages/Network_Architecture/Blocks/transaction-life-cycle.adoc b/...ture_and_concepts/pages/Network_Architecture/Blocks/transaction-life-cycle.adoc
@@ -13,16 +13,19 @@ The transaction lifecycle in Starknet involves the following high level steps:
 A transaction is submitted to one of the gateways, functioning as the Mempool and marks the transaction status as `RECEIVED`.
 
 === 2. Validation
+
+==== 2.1 Mempool validation
 The Mempool performs validation on the transaction to check for its validity. If the transaction is invalid, it will not proceed to the next stages.
 
+==== 2.2 Sequencer validation
+The sequencer performs validation on the transaction prior to execution to ensure that the transaction is still valid. If the transaction is invalid, it will not proceed to the next stages.
+
 === 3. Execution
 The sequencer operation sequentially applies the validated transactions to the state. If a transaction fails during execution, it will be included in the block with the status `REVERTED`.
 
 === 4. Proof Generation
 The Prover stage executes the operating system on the new block, computes the proof, and transmits it to L1.
 
-
-
 [id="transaction_status"]
 
 == Transaction status
@@ -141,4 +144,4 @@ The following is an example of a receipt:
   }
 }
 
-----
+----