Skip to content

epic: applicative recursion #1350

@ClementWalter

Description

@ClementWalter

Why

Cairo EVM traces range from 100 to 1000M steps, while stwo-cairo currently hash a hard coded maximum size of 2**27 ~ 135M steps.

What

Create a commitment on the function's signature arguments (i.e. a commitment of the parameters of the call to _apply_body_inner)

Split the single main.cairo program at the _apply_body_inner interface into 3 programs

  1. everything up to the first call to _apply_body_inner => init.cairo
  2. _apply_body_inner alone => body.cairo
  3. everything from the last return of _apply_body_inner => teardown.cairo
  • init.cairo should put in the output_ptr the commitment
  • body.cairo should put in the output_ptr initial and final commitment
  • teardown.cairo should put in the output_ptr the commitment

Sub-issues

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Projects

Status

Backlog

Relationships

None yet

Development

No branches or pull requests

Issue actions