Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

how big would be the lookup table? #5

Open
jackzhp opened this issue Mar 22, 2021 · 1 comment
Open

how big would be the lookup table? #5

jackzhp opened this issue Mar 22, 2021 · 1 comment

Comments

@jackzhp
Copy link

jackzhp commented Mar 22, 2021

if my problem is to verify schnorr signature, i will have a sha256 in my constraint system.

after look at the 4bit xor table in the example, i am wondering how large would be for the loopup table for the sha256 circuit?

in fact, i feel that i understand the paper, but i just don't know how to apply it to a real problem. i feel there's a big gap between what the paper says and its application. or maybe my feelings indicate that I don't really understand the paper.

i have googled, but just still not able to close the gap by myself.

i am looking forward to a paper on how to apply plookup on a real example such as sha256.

Jack.

@kevaundray
Copy link
Owner

Hey,

You would not necessarily do a lookup table for SHA256, but more a lookup table for some component in sha256.

For example, In sha256 you may need to do an 8bit XOR, so you could use the 4bit XOR twice.

You are right in that the information is really sparse; a great repo which implements plookup with plonk is https://github.com/zcash/halo2

They also have a book with a lot of great details.

I hope that was somewhat helpful :)

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

No branches or pull requests

2 participants