Discrepancy between Poseidon hashes in circom vs circomlibjs about circomlibjs HOT 4 CLOSED

Thanks. For reference, I figured out that the following yields the same results as the current circom version (no need to downgrade circomlibjs).

let hashBytes = poseidon([4, 9]);
let hash = poseidon.F.toString(hashBytes);

from circomlibjs.

It seems the newer versions of circomlibjs have a different implementation of the Poseidon hash. This error was fixed when I downgraded to [email protected] (perhaps some versions in between will work too; I haven't tried).

from circomlibjs.

Suggestion: If there was a github repository test that forced an equality comparison between the poseidon_wasm.js code and a poseidon circuit, it would be really helpful. Took me weeks to pull this all together myself.

from circomlibjs.

Thanks. For reference, I figured out that the following yields the same results as the current circom version (no need to downgrade circomlibjs).

let hashBytes = poseidon([4, 9]);
let hash = poseidon.F.toString(hashBytes);

Thank you so much for this!! I was using ffjavascript's utils.stringifyBigInts instead of F.toString(). Not sure what that method is doing, but it was returning other numbers.

js is such a pain to code with.. because we don't get suggestions. Really wishing this had been coded in ts, since vscode would have suggested poseidon.F.toString most likely.

from circomlibjs.