Protocol: Protocol Statements

[iAmMichaelConnor]

The statements of the protocol are split across many circuits and smart contracts.

Protocol Statements

Preview Give feedback

1. Protocol: High-level circuits topology #3154
   A-documentation A-protocol +2
   
2. Protocol: Private Circuit ABI #3155
   A-documentation A-protocol +2
   
3. Protocol: Public VM Circuit #3156
   A-documentation A-protocol C-avm +3
   
4. Protocol: Initial Private Kernel Circuit #3143
   A-documentation A-protocol +2
   
5. Protocol: Inner Private Kernel Circuit #3144
   A-documentation A-protocol +2
   
6. Protocol: Ordering Private Kernel Circuit #3145
   A-documentation A-protocol +2
   
7. Protocol: Public Kernel Circuit with Private Previous #3146
   A-documentation A-protocol +2
   
8. Protocol: Public Kernel Circuit with Public Previous #3147
   A-documentation A-protocol +2
   
9. Protocol: Base Rollup Circuit #3148
   A-documentation A-protocol +2
   
10. Protocol: Merge Rollup Circuit #3149
    A-documentation A-protocol +2
    
11. Protocol: Root Rollup Circuit #3150
    A-documentation A-protocol +2
    
12. Protocol: Squisher circuit: Honk -> UltraPlonk
13. Protocol: Squisher circuit: UltraPlonk -> Standard Plonk
14. Protocol: EIP4844 commitment equivalence circuit #3153
    A-documentation A-protocol +2
    
15. Protocol: VM Bytecode Commitment circuit #3152
    A-documentation A-protocol +2
    
16. Protocol: Smart contracts #3151
    A-documentation A-protocol +2
    
17. Protocol: Sequencer VRF circuit #3615
    A-documentation A-protocol +2
    

• Protocol Statements
  • Describe the logic of the protocol.
  • Describe the assertions that must be in place.
    • The constraints (assertions) of the system are spread across many circuits and L1 contracts, but they should be described as a whole, in one place. Where the assertions are located (i.e. in which circuit/contract) is a matter of optimisation, which might change over time. This can then serve as a checklist, to ensure those assertions are included in at least one of the circuits/contracts.
    • In particular, exhaustively explain what shouldn't be possible.
  • Sub-protocols
    • It might help to describe certain sub-protocols, which need to be sound in their own right.
    • E.g.:
      • Contract Deployment
      • (Account abstraction)
      • A private function call
        • Nested private function calls
      • A public function call
        • Nested public function calls
      • Private -> Public function calls
      • Enqueueing many public function calls
      • Private -> Internal Public function calls
      • Side-effect ordering
      • Note/Nullifier squashing optimisations
      • Upgrading contract bytecode
      • Upgrading keys
      • Gas metering
      • Fee payments
      • Sequencer Selection
      • Prover Selection
      • Initiating an upgrade
  • Circuits
    • For each: Explain / justify the requirements. Describe the Public Inputs ABI & the Bus ABI. Explain the statements logic and assertions.
    • High-level topology [David/Leila?]
    • Private Circuits [David/Leila?]
      • General features a private circuit must adhere-to.
      • Why not a private VM?
    • Public VM Cicuit [David] <-- big section
    • Kernel Circuits
      • Private [David/Leila?]
        • Initial Private Kernel Circuit
        • Inner Private Kernel Circuit
        • Ordering Private Kernel Circuit
      • Public [David/Leila?]
        • Initial Public Kernel Circuit
        • Inner Public Kernel Circuit
        • (Ordering Public Kernel Circuit???)
      • Future Kernel Optimisations
        • Delegating chunks of compute to 'gadget' circuits
        • A Merkle Tree of Private Kernel iterations
    • Rollup Circuits [Lasse/Leila?]
      • Base Rollup Circuit
      • Merge Rollup Circuit
      • Root Rollup Circuit
    • Squisher Circuits [???]
      • Honk -> UltraPlonk
      • UltraPlonk -> Standard Plonk / Fflonk
    • Circuits for sequencer/prover selection? [Palla]
    • EIP-4844 circuit [???]
    • Bytecode commitment circuit [???]
  • Smart Contracts [Lasse]
    • ...