You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here's a table of all the Rust repos we have in our org.
I think this surface area is too big. If we have active code, let's keep it in our active repos, where we can keep it current, tested, audited etc. Otherwise let's archive it.
e.g smt_utils, eth_trie_tools should actually just be (crates or modules) in the zk_evm repo, where there's already trie diffing stuff.
The plonky2-foo repos were initially part of the plonky2 workspace and then moved away into individual crates, though mostly outdated / unmaintained as of today.
CircleStark is unrelated to plonky2, could eventually be moved to Plonky3 github org (cc @dlubarov)
evm-tests should probably be kept. @praetoriansentry created a matrix of all tests and deployed them in a test chain, but we still use them for easy, reliable testing and easier debugging + make it a testing reference to anyone who wants to check completeness of the zkEVM (these tests are the standard for EVM implementations).
Here's a table of all the Rust repos we have in our org.
I think this surface area is too big. If we have active code, let's keep it in our active repos, where we can keep it current, tested, audited etc. Otherwise let's archive it.
e.g
smt_utils
,eth_trie_tools
should actually just be (crates or modules) in the zk_evm repo, where there's already trie diffing stuff.Here's a strawman proposal
eth_trie_utils
.Bootstrapping script
Clone all repos
The text was updated successfully, but these errors were encountered: