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
{{ message }}
This repository has been archived by the owner on Mar 15, 2024. It is now read-only.
On 32 bits archs these operations are around 40 times slower.
Since a few years ago most of the new mobile phones are 64 bit ARM architecture, so in theory only old devices would be affected.
This also could affect Android emulation: if x86 emulation is used, the performance of zk proof functionality will be very poor (we already experienced this in firebase where tests timed out when running on an x86 Android emulator).
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
zkProofs operations are slow on 32 bits architecture: iden3/go-circom-prover-verifier#23
This affects:
On 32 bits archs these operations are around 40 times slower.
Since a few years ago most of the new mobile phones are 64 bit ARM architecture, so in theory only old devices would be affected.
This also could affect Android emulation: if x86 emulation is used, the performance of zk proof functionality will be very poor (we already experienced this in firebase where tests timed out when running on an x86 Android emulator).
The text was updated successfully, but these errors were encountered: