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
Right now it's not quite possible to load poseidon, the prover and verifier within a browser.
msgHash requires a Buffer type despite uInt8Array being the native buffer-like for browsers (can be worked around using Buffer.from, but might not provide the same results).
To properly load their respective .wasm libraries, we need fs, which is exposed only to nodejs runtimes.
Poseidon (and maybe MembershipProver and MembershipVerifier) are not serializable, so even if we are able to load their .wasm libraries through our server, they can't be shared through a client, forcing computing (i.e., the evaluation of the verifier and the generation of the proofs) can only be done in a server.
FWIW the limitation is documented in the README but for anyone looking to support this library client side, these challenges would need to be tackled. Also, these are only the ones I've faced, there might be even some more one these first ones had been cleared out.
The text was updated successfully, but these errors were encountered:
Right now it's not quite possible to load poseidon, the prover and verifier within a browser.
msgHash
requires aBuffer
type despiteuInt8Array
being the native buffer-like for browsers (can be worked around usingBuffer.from
, but might not provide the same results)..wasm
libraries, we needfs
, which is exposed only tonodejs
runtimes.Poseidon
(and maybeMembershipProver
andMembershipVerifier
) are not serializable, so even if we are able to load their.wasm
libraries through our server, they can't be shared through a client, forcing computing (i.e., the evaluation of the verifier and the generation of the proofs) can only be done in a server.FWIW the limitation is documented in the README but for anyone looking to support this library client side, these challenges would need to be tackled. Also, these are only the ones I've faced, there might be even some more one these first ones had been cleared out.
The text was updated successfully, but these errors were encountered: