Self-Sequencing Specs

Describes current self-sequencing method available for end-user on applications leveraging the Multichain Sequencer. Self-sequencing allows users to exit or interact with the protocol trustlessly.

One of the key components of current Coprocessor based solutions is the ability for users to exit the protocols in a trustless manner. The main security considerations for enabling self-sequencing are reliant on the following aspects

• Finalize state to prevent leveraging a direct attack on a rollup as an attack vector to access liquidity

• Generate a correct proof on the finalized state

In this architecture the following example walks through how a trustless exit can be designed into the applications logic:

• Rollup A contains the global ledger

• User A initiates a withdrawal transaction via self-sequencing in case of liveness issues with the sequencer

• Rollup A achieves finality in two ways with current solutions:

  • Optimistic design → Once the challenge period expired a self-sequenced proof can be generated

  • zk-based design → L1 verification of the submitted zk-proof on the rollup state is sufficient to generate the self-sequenced proof

• On the applications side its key to enable a selector for end-users to decide when they want to self-sequence, and when the end-user will submit the proof instead of the sequencer