Release 0.5

[mmagician]

• fully deprecate circom1, and thus remove make circom-2 feature the default,
• simplify the traits, we no longer need CricomBase vs. Circom1 & Circom2. Directly implement all the methods on the Wasm struct,
• update the dependencies to 0.5.0-alpha
• adapt version numbering for org consistency

[mmagician]

This code works now after arkworks-rs/groth16#61 has been merged and groth 0.5.0-alpha.1 released. Let's keep it as a branch for now till we upgrade all other repos

[anudit]

@mmagician Just tried the 0.5.0-alpha.1 release, proof verification seems to work 🚀

[Pratyush]

Thanks @mmagician; could you also update the README to change the line about adding ark-circom as a dependency to use the crates version instead?

Also, @tyshko-rostyslav, could you please authorize the crates-io team within the arkworks organization to make releases for the ark-circom crate?

[tyshko-rostyslav]

Thanks @mmagician; could you also update the README to change the line about adding ark-circom as a dependency to use the crates version instead?

Also, @tyshko-rostyslav, could you please authorize the crates-io team within the arkworks organization to make releases for the ark-circom crate?

Sure, but as far as I understand from docs you need to have a team in arkworks-rs created. Otherwise I could add people one by one, whatever is easier for you

[mmagician]

@tyshko-rostyslav There is a crates.io team in the arkworks-rs organization: https://crates.io/teams/github:arkworks-rs:crates-io

[tyshko-rostyslav]

@tyshko-rostyslav There is a crates.io team in the arkworks-rs organization: https://crates.io/teams/github:arkworks-rs:crates-io

As per docs I have to be a member of your team to be able to give the team access. Could you please (temporarily) add me to that team?

[mmagician]

@Pratyush

[tyshko-rostyslav]

@Pratyush

Thanks! Added the team

[mmagician]

Thanks @tyshko-rostyslav! https://crates.io/crates/ark-circom/0.5.0-alpha

[mmagician]

@CPerezz I ended up upgrading the dependencies for wasmer. I added CI for this as well, but could you still confirm the new alpha release works on your setup please?

[CPerezz]

@CPerezz I ended up upgrading the dependencies for wasmer. I added CI for this as well, but could you still confirm the new alpha release works on your setup please?

Hey, this target and setup work for the build and check. Also, couple things to at least mention.

• Target wasm32-wasi also works. So maybe worth to test for a matrix{{}} of targets instead in the CI?
• I've found sometimes that check or build won't compile the lib as if it was a dependency. Resulting sometimes in unexpected errors when used downstream.
  I usually have this script running in the CI to asses that indeed no errors happen even when the lib is a dependency of another crate: https://github.com/privacy-scaling-explorations/sonobe/blob/main/.github/scripts/wasm-target-test-build.sh
  And I call it like: https://github.com/privacy-scaling-explorations/sonobe/blob/0ad54576ec6462d63313ebde18bb0a24669fd00e/.github/workflows/ci.yml#L104

In any case, definitely looks well! Nice work!