From 7caa50a9f201b2eb1bf9e5d4d2d7b8c8e561d5e9 Mon Sep 17 00:00:00 2001 From: emanuel-sol Date: Fri, 13 May 2022 05:33:35 -0300 Subject: [PATCH 1/2] =?UTF-8?q?=F0=9F=93=9D=20Update=20page?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- docs/Blocks/transaction-life-cycle.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/Blocks/transaction-life-cycle.md b/docs/Blocks/transaction-life-cycle.md index 031c044846..2325e6eff8 100644 --- a/docs/Blocks/transaction-life-cycle.md +++ b/docs/Blocks/transaction-life-cycle.md @@ -1,6 +1,6 @@ # Transaction Lifecycle -The following are the possible statuses of transaction from the moment it the moment it is included in a proof validated by L1. +The following are the possible statuses of a transaction from the moment it's included in a proof to the moment it's validated by L1. ## Transaction status @@ -35,7 +35,7 @@ Transaction was accepted on-chain. ## The pending block -Today, StarkNet supports querying the new block before its construction is complete. This feature improves the liveness of the system prior to the decentralization phase, but will probably become obsolete once the system is decentralized, as full nodes will only propagate finalized blocks through the network. +Today, StarkNet supports querying the new block before its construction is complete. This feature improves the uptime of the system prior to the decentralization phase, but will probably become obsolete once the system is decentralized, as full nodes will only propagate finalized blocks through the network. During the construction of the block, as it is accumulating new transactions, the block’s status is PENDING. While PENDING, new transactions are dynamically added to the block. Once the sequencer decides to “close” the block, it becomes `ACCEPTED_ON_L2` and its hash is computed. From 4fb8ff6ff74d9b07edca8286b4411d5dba77ab7e Mon Sep 17 00:00:00 2001 From: Emanuel <34749913+emanuel-sol@users.noreply.github.com> Date: Fri, 20 May 2022 12:09:53 -0400 Subject: [PATCH 2/2] Update transaction-life-cycle.md --- docs/Blocks/transaction-life-cycle.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/Blocks/transaction-life-cycle.md b/docs/Blocks/transaction-life-cycle.md index 2325e6eff8..df7135c930 100644 --- a/docs/Blocks/transaction-life-cycle.md +++ b/docs/Blocks/transaction-life-cycle.md @@ -35,7 +35,7 @@ Transaction was accepted on-chain. ## The pending block -Today, StarkNet supports querying the new block before its construction is complete. This feature improves the uptime of the system prior to the decentralization phase, but will probably become obsolete once the system is decentralized, as full nodes will only propagate finalized blocks through the network. +Today, StarkNet supports querying the new block before its construction is complete. This feature improves the responsiveness of the system prior to the decentralization phase, but will probably become obsolete once the system is decentralized, as full nodes will only propagate finalized blocks through the network. During the construction of the block, as it is accumulating new transactions, the block’s status is PENDING. While PENDING, new transactions are dynamically added to the block. Once the sequencer decides to “close” the block, it becomes `ACCEPTED_ON_L2` and its hash is computed.