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.

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

Make curve25519 and bn128 out into their own crates #983

Open
2 tasks
samkim-crypto opened this issue Apr 22, 2024 · 0 comments
Open
2 tasks

Make curve25519 and bn128 out into their own crates #983

samkim-crypto opened this issue Apr 22, 2024 · 0 comments

Comments

@samkim-crypto
Copy link

Problem

The curve25519 code contains logic related to curve25519 syscalls. It is currently contained in zk-token-sdk create, but is mostly independent of the rest of the (token) logic in the crate. There are some downstream projects that only require the curve25519 logic, but unnecessarily need to depend on the entire set of dependencies in zk-token-sdk.

This is also the case with bn128 logic in the solana-program crate as it is independent of the rest of the logic there.

Proposed Solution

Separate out these crates into their own separate crates:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant