SNOS has been maintaining several forks of its dependencies for some time now. Many of our changes have been included in upstream, but there remain some minor ones which force us to continue to use our own forks.
This becomes very problematic for projects which use SNOS as a dependency (e.g. the prove_block lib) because it creates duplicated and conflicting dependencies which are difficult to work around, resulting in compile errors like:
note: `blockifier::Foo` and `Foo` have similar names, but are actually distinct types
Upstream PRs
As of now, each of these "customizations" has an upstream PR, listed below. However, these still point to main branches and would need to be backported for immediate relief (TODO).
SNOS has been maintaining several forks of its dependencies for some time now. Many of our changes have been included in upstream, but there remain some minor ones which force us to continue to use our own forks.
This becomes very problematic for projects which use SNOS as a dependency (e.g. the
prove_blocklib) because it creates duplicated and conflicting dependencies which are difficult to work around, resulting in compile errors like:Upstream PRs
As of now, each of these "customizations" has an upstream PR, listed below. However, these still point to
mainbranches and would need to be backported for immediate relief (TODO).cairo-vm: https://github.com/lambdaclass/cairo-vm/pull/1845sequencer: dev: Minor SNOS changes starkware-libs/sequencer#3098pathfinder: feat: Expose private class hashing functionality equilibriumco/pathfinder#2465