Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: enhance readability of page #30

Merged
merged 6 commits into from
Jun 15, 2022
Merged
Changes from 4 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/Blocks/transaction-life-cycle.md
Original file line number Diff line number Diff line change
@@ -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

Expand Down Expand Up @@ -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 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.

Expand Down