-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature: Implement Secp Syscalls #279
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Quick review for early changes, I need to review the implementation in depth.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Realizing there's a lot of duplication coming from Blockifier. Why not call the Blockifier code directly?
Problem: when declaring contracts with the state builder, there is no easy way to find the declared contracts from the test state. Solution: reproduce what is done for deployed contracts, give the user the ability to define a name for each declared contract.
Problem: We currently only test specific transactions one at a time. Solution: Implement a comprehensive test case that covers all tx types. --------- Co-authored-by: Stephen Shelton <[email protected]> Co-authored-by: Olivier Desenfans <[email protected]>
Closed in favor of #286 |
This PR handles all the Secp syscalls for both
k1
andr1
curves. It includes:Issue Number: N/A
Type
Description
Breaking changes?