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
rapidsnark, a C++ tool previously incompatible with macOS ARM64, has been updated to support this architecture. We had switched to a WASM verifier(snarkjs) due to this limitation.
Proposal
Given rapidsnark's recent update, I propose we revert to using rapidsnark for macOS ARM64. This change would enhance performance and maintain consistency across platforms.
The text was updated successfully, but these errors were encountered:
Seems like rapidsnark is available for ARM chips, though it's not possible yet to compile the c witness on arm chips (or I guess I'm missing something)
Seems like rapidsnark is available for ARM chips, though it's not possible yet to compile the c witness on arm chips (or I guess I'm missing something)
hmm at least it seems possible to verify with rapidsnark on ARM tho
Seems like rapidsnark is available for ARM chips, though it's not possible yet to compile the c witness on arm chips (or I guess I'm missing something)
hmm at least it seems possible to verify with rapidsnark on ARM tho
yup, but we only use rapidsnark for proof generation atm. Probably best to wait until circom releases support so that we can generate proof using rapidsnark on both arm and intel
Context
rapidsnark, a C++ tool previously incompatible with macOS ARM64, has been updated to support this architecture. We had switched to a WASM verifier(snarkjs) due to this limitation.
Proposal
Given rapidsnark's recent update, I propose we revert to using rapidsnark for macOS ARM64. This change would enhance performance and maintain consistency across platforms.
The text was updated successfully, but these errors were encountered: