You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be very cool if there was a function to return the TasmConstraintEvaluationMemoryLayout used by the STARK prover/verifier. I think all values can be known at compile time. The values free_mem_page_ptr and challenges_ptr can be fixed by a convention. But the values curr_base_row_ptr, curr_ext_row_ptr, next_base_row_ptr, next_ext_row_ptr might be derivable somehow from a macro or maybe just hardcoded and then verified through a test?
The text was updated successfully, but these errors were encountered:
Sword-Smith
changed the title
Derive TasmConstraintEvaluationMemoryLayout used by STARK prover
Derive TasmConstraintEvaluationMemoryLayout used by STARK prover?
Mar 9, 2024
It would be very cool if there was a function to return the
TasmConstraintEvaluationMemoryLayout
used by the STARK prover/verifier. I think all values can be known at compile time. The valuesfree_mem_page_ptr
andchallenges_ptr
can be fixed by a convention. But the valuescurr_base_row_ptr
,curr_ext_row_ptr
,next_base_row_ptr
,next_ext_row_ptr
might be derivable somehow from a macro or maybe just hardcoded and then verified through a test?The text was updated successfully, but these errors were encountered: