chore(poseidon): add verification key json files

[sripwoud]

Generated with:

1. create options.json:

   {
      "path/to/zk-kit.circom/packages/poseidon-proof/circomkit.json": {
          "circuit": "poseidon-proof",
          "paramsList": [["1"],["2"],["3"],["4"],["5"],["6"],["7"],["8"],["9"],["10"],["11"],["12"],["13"],["14"],["15"],["16"]]
       }
    }

```commandline
pnpm add -g @zk-kit/artifacts-cli
cd $(mktemp -d)
snarkli gb path/to/options.json $(pwd)
circuit=poseidon
for i in {1..16};do mv -f "$circuit-proof-$i/$circuit-proof/groth16_vkey.json" "/path/to/snark-artifacts/packages/$circuit/circuit-$i.json";done
for i in {1..16};do mv -f "$circuit-proof-$i/$circuit-proof/groth16_pkey.zkey" "/path/to/snark-artifacts/packages/$circuit/$circuit-$i.zkey";done
for i in {1..16};do mv -f "$circuit-proof-$i/$circuit-proof/$circuit-proof_js/$circuit-proof.wasm" "/path/to/snark-artifacts/packages/$circuit/$circuit-$i.wasm";done
```

Test

See #143

git checkout test/poseidon-verifkey
pnpm --filter ./packages/poseidon t

[changeset-bot]

⚠️ No Changeset found

Latest commit: 4e8c557

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[sripwoud]

to trigger ci and match https://github.com/privacy-scaling-explorations/zk-kit/blob/687bddcb2a124b478af278729f44dc7632eb34d6/packages/poseidon-proof/package.json#L3

[cedoor]

Should we test them before merging?

[sripwoud]

Would be better
Yes
But I wasn't sure what was the easiest way.
A jest test, using snakjs CLI directly?

[cedoor]

Would be better Yes But I wasn't sure what was the easiest way. A jest test, using snakjs CLI directly?

Do we need the CLI? All the artifacts are ready to be used. So snarkjs can be used to generate the proof and then to verify it right?

[sripwoud]

@cedoor I added tests that cover all the wasm, zkey , json artifacts... see #127
and they are all failing.

Either my test suite itself is wrong (although it is very similar to what we do here)
or all the verification keys I generated are wrong...

[sripwoud]

@cedoor New artifacts generated and tests added in #143: should we merge #143 btw for reference (or even add it into the CI)?

[sripwoud]

The reason why my initial tests were failing (making me believe the CLI was buggy) was because I was using incompatible zkey and vkey artifacts to generate and verify the proofs.
If 2 different setups are run for a same circuit C, producing {v,z}key{A,B},
one cannot

• generate a proof P with zkeyA
• and then verify P with vkeyB

This will fail (which is what i was initially doing)

[cedoor]

@cedoor New artifacts generated and tests added in #143: should we merge #143 btw for reference (or even add it into the CI)?

Yea, I'd add it to the CI 👍🏽 We could open another issue/PR for it.

Do we need to rebase this branch?

[sripwoud]

@cedoor branch is rebased
#144 refactors the tests (the ci already picks them)

[cedoor]

@sripwoud kk, then this PR looks ok to me!