Skip to content
This repository has been archived by the owner on Jan 19, 2024. It is now read-only.

Question about field size #9

Open
pememoni opened this issue Jul 27, 2023 · 1 comment
Open

Question about field size #9

pememoni opened this issue Jul 27, 2023 · 1 comment

Comments

@pememoni
Copy link

pememoni commented Jul 27, 2023

Hey hey, I recently found this Valida and really excited about all of the smart choices and innovations that you are doing! I was curious about the 32-bit field size, as far as I know, most of the other similar projects e.g. Boojum , Polygon are using Goldilocks. Is there an interesting theoretical or engineering reason behind this decision?

@dlubarov
Copy link
Collaborator

Hey! We think 32-bit fields are a good long-term direction since they let us get much better throughput (like field operations per unit time) on CPUs and GPUs. (Even though modern CPUs support 64-bit integer arithmetic, it's scalar-only, whereas most CPUs have vectorized 32-bit multiplication.)

I think the optimal field choice is somewhat application-specific, but for applications that generally use less than 32 bits of space in each witness element anyway (e.g. lookup heavy applications), 32-bit seems like a good fit.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants