Skip to content
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.

Sign up for GitHub

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

Jump to bottom

dev: use local kakarot-ssj instead of remote release from archived repo #1596

Open
2 tasks
enitrat opened this issue Nov 9, 2024 · 2 comments
Open
2 tasks

dev: use local kakarot-ssj instead of remote release from archived repo #1596

enitrat opened this issue Nov 9, 2024 · 2 comments

Comments

@enitrat
Copy link
Collaborator

enitrat commented Nov 9, 2024

With the introduction of modexp and ecpairing, we need to stop using the old remote repo and start using the local version of kakarot-ssj

Changes since the version we're using right now:

  • modexp
  • ecpairing
  • some optimisation changes discussed internally

Once done

  • enable modexp as external_precompile
  • enable ecpairing as external_precompile
@github-project-automation github-project-automation bot moved this to 🆕 Backlog in Kakarot on Starknet Nov 9, 2024
@enitrat
Copy link
Collaborator Author

enitrat commented Nov 9, 2024

No, can you stop spamming please?

@enitrat enitrat mentioned this issue Nov 10, 2024
Open
@enitrat
Copy link
Collaborator Author

enitrat commented Nov 15, 2024

Unplanned: the deployments will keep using the audited code in kakarot-ssj repo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
No open projects
Kakarot on Starknet
Status: 🆕 Backlog
Milestone
No milestone
Development

No branches or pull requests
1 participant
@enitrat