Range checking is a way of verifying that a number is between zero and two to the 63 or whatever, so you don't overflow. Em: I think we want to optomlize this range yagging. There should be a right up a with pretty exciting ideas where you can batch range checks. This is a sort of unexplored territory that writes heither just like ideas at this point. Or am, i mean, the amazing thingis that does tis so much low hanging fruit. You know, in two thousand 19 how much, how many papers were published on the continuous basis. And now we're point where the people with both kinds of engineering and research hat on are here
In this episode, we catch up with Justin Drake and Vitalik Buterin from the Ethereum Foundation to chat about how zero knowledge proof systems are being used throughout the Eth1x and Eth2.0 stacks. We look at their applications for privacy and scalability throughout layer 1, layer 1.5 and layer 2, as well as explore some other emerging applications.
Here were some of the articles and ideas discussed:
5 ways to optimise zkps:
- Remove the need for FFTs
- Sparseness
- Recursion
- Custom gates
- Hardware
Jacobian groups https://eprint.iacr.org/2020/196.pdf
Trilinear maps https://arxiv.org/abs/2002.07923
Give the Zero Knowledge Podcast some feedback. Whether you are a long-time listener or new to the show, we would love to hear from you!
Please share your feedback with us here: https://forms.gle/LtQQyKJV6r7LrSND7
If you like what we do:
Follow us on Twitter - @zeroknowledgefm
Join us on Telegram
Catch up with us on Youtube
Support our Gitcoin Grant
Support us on the ZKP Patreon
Or directly here:
ETH: 0xC0FFEE1B5083230a5154F55f253B6b6ae8F29B1a
BTC: 1cafekGa3podM4fBxPSQc6RCEXQNTK8Zz
ZEC: t1R2bujRF3Hzte9ALHpMJvY8t5kb9ut9SpQ