Skip to content

Commit

Permalink
SCORU originator is not an operator (#351)
Browse files Browse the repository at this point in the history
* SCORU nodes in operator mode

* One or more users start Smart Rollup nodes.
  • Loading branch information
timothymcmackin authored Mar 12, 2024
1 parent ad19dda commit 2218ba4
Showing 1 changed file with 3 additions and 2 deletions.
5 changes: 3 additions & 2 deletions docs/architecture/smart-rollups.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
title: Smart Rollups
authors: 'Nomadic Labs, TriliTech, Tim McMackin'
last_update:
date: 18 January 2024
date: 11 March 2024
---

Smart Rollups play a crucial part in providing high scalability on Tezos.
Expand Down Expand Up @@ -91,7 +91,8 @@ 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. Origination: A user originates the Smart Rollup to layer 1.
1. One or more users start Smart Rollup nodes.
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 2218ba4

Please sign in to comment.