Skip to content

Commit

Permalink
state at the end of the period., called a commitment
Browse files Browse the repository at this point in the history
Co-authored-by: NicNomadic <[email protected]>
  • Loading branch information
timothymcmackin and NicNomadic authored Jan 17, 2024
1 parent 7966236 commit dcff70d
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/architecture/smart-rollups.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -91,7 +91,7 @@ Eventually include:
The general flow of a Smart Rollup goes through these phases:

1. Origination: A user called the _rollup operator_ originates the Smart Rollup to layer 1 and one or more users start nodes based on that Smart Rollup to independently verify its operation.
1. Commitment periods: The Smart Rollup nodes receive the messages in the Smart Rollup inbox, run processing based on those messages, generate but do not run outbox messages, and publish a hash of their state at the end of the period.
1. Commitment periods: The Smart Rollup nodes receive the messages in the Smart Rollup inbox, run processing based on those messages, generate but do not run outbox messages, and publish a hash of their state at the end of the period., called a commitment
1. Refutation periods: Nodes can publish a concurrent commitment to refute a published commitment.
1. Triggering outbox messages: When the commitment can no longer be refuted, any client can trigger outbox messages, which create transactions.

Expand Down

0 comments on commit dcff70d

Please sign in to comment.