๐Ÿ“

Preliminary Research Template

(1) Brief Description of Rollup Solution
Simply describe what sort of rollup it is:
  • Does it use fraud proofs vs validity proofs?
  • Is all the data available on L1 or is it stored off-chain (validium/optimistic chain)
  • Is it specific purpose or general-purpose?
(2) System Actors
Explore the architecture and identify the different actors in the system. An actor an entity with well-defined role/s. Software implementations may bundle actors together in a monolithic manner, in this case refer to the architecture echoed by the development teams of the system for clarity about actors.
(3) Actor Relationships
This describes the interactions that different actors have with each other. These many interactions between different actors will effectively describe the lifecycle of various tasks performed in the system such as:
  • Processing deposits and withdrawals
  • Gossiping data
  • Executing transactions
  • Publishing data to data availability layer.
  • L2 consensus
ย 
In this section you can also dive deeper into the practical implementations of system actors and additional sorts of tasks carried out by individual actors. You can also use this section to describe the current security assumptions around actors.
(4) Rollup Characteristics
TitleDescription
SettlementHow are L2 state changes trustlessly verified? Is arbitration necessary or do cryptographic guarantees ensure validity?
Execution EnvironmentWhat software performs of the off-chain state transition computation on the L2 state?
Sequencing RulesWho is responsible for transaction ordering? Are there any rules to transaction ordering? Any MEV strategy (including a planning for one)?
EconomicsNative token? Are their any additional incentives introduced to compel different actor behaviour? (e.g. incentives to sync from L1 instead of trustful sync with L2 nodes)
(5) Data Publication
State Validation
Does the system currently have a mechanism to prevent invalid state roots from being posted to the DA layer?
Data Availability
Where is L2 transaction data posted to?
Where are L2 state roots posted to?
Sequencer failure
What is the current situation regarding sequencing on the L2?
If there is a sequencer failure, what can a user do?
Validator failure
If there are no validators (e.g. nodes that process state transitions and gossip state roots and transactions), what can a user do? (can they withdraw assets? etc)
ย 
Using the above forum post, use your findings to rank the rollup milestone status. If it does not satisfy any of the stages, then you should explicitly clarify that the solution does not meet the criteria to be labelled a rollup.
๐Ÿ“

Preliminary Research Template

(1) Brief Description of Rollup Solution
Simply describe what sort of rollup it is:
  • Does it use fraud proofs vs validity proofs?
  • Is all the data available on L1 or is it stored off-chain (validium/optimistic chain)
  • Is it specific purpose or general-purpose?
(2) System Actors
Explore the architecture and identify the different actors in the system. An actor an entity with well-defined role/s. Software implementations may bundle actors together in a monolithic manner, in this case refer to the architecture echoed by the development teams of the system for clarity about actors.
(3) Actor Relationships
This describes the interactions that different actors have with each other. These many interactions between different actors will effectively describe the lifecycle of various tasks performed in the system such as:
  • Processing deposits and withdrawals
  • Gossiping data
  • Executing transactions
  • Publishing data to data availability layer.
  • L2 consensus
ย 
In this section you can also dive deeper into the practical implementations of system actors and additional sorts of tasks carried out by individual actors. You can also use this section to describe the current security assumptions around actors.
(4) Rollup Characteristics
TitleDescription
SettlementHow are L2 state changes trustlessly verified? Is arbitration necessary or do cryptographic guarantees ensure validity?
Execution EnvironmentWhat software performs of the off-chain state transition computation on the L2 state?
Sequencing RulesWho is responsible for transaction ordering? Are there any rules to transaction ordering? Any MEV strategy (including a planning for one)?
EconomicsNative token? Are their any additional incentives introduced to compel different actor behaviour? (e.g. incentives to sync from L1 instead of trustful sync with L2 nodes)
(5) Data Publication
State Validation
Does the system currently have a mechanism to prevent invalid state roots from being posted to the DA layer?
Data Availability
Where is L2 transaction data posted to?
Where are L2 state roots posted to?
Sequencer failure
What is the current situation regarding sequencing on the L2?
If there is a sequencer failure, what can a user do?
Validator failure
If there are no validators (e.g. nodes that process state transitions and gossip state roots and transactions), what can a user do? (can they withdraw assets? etc)
ย 
Using the above forum post, use your findings to rank the rollup milestone status. If it does not satisfy any of the stages, then you should explicitly clarify that the solution does not meet the criteria to be labelled a rollup.