Skip to content

Pin dependencies #61

@mmagician

Description

@mmagician

Since arkworks/algebra, poly-commit etc. are moving targets, let's not have our code break because of upstream changes.

This issue is about pinning the dependencies to some specific fork & revision/branch/tag, whatever makes more sense (but should be consistent). Probably revision is best, since we don't have tags that update on a frequent basis, and branches will come from different forks/repos and thus not be consistent.

@DimitrisPapac & @Cesar199999 can you take care of this together please?

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions