sinu.eth (sinu)

I think the main roadblock would be the incentives. For public data, there is nothing in the way of doing this right now (Internet Archive!). For data gated behind access control, TLSNotary could be part of that picture. The main limitation there is scaling, but somewhat approachable near-term for at least text content

• 0 replies
• 1 recast
• 3 reactions

Right now we use garbled circuits for our in-protocol ZKPs ala JKO13. We have plans to switch to using Quicksilver this year. Protocols like QS provide impressive proving and verification performance (comparable to evaluating a statement in the clear). They can work over any field, and recently I learned over Z_2^k too

• 1 reply
• 0 recasts
• 4 reactions

TLSNotary is an interactive "designated verifier" protocol, so we are operating under a different set of constraints than what is common in other apps of ZK in this space. Namely, we do not require sub-linear proof sizes or sub-linear verification costs. In other words: SNARKs are overkill for us in many cases.

• 1 reply
• 0 recasts
• 4 reactions

Go interact with GenericArray a couple times and report back how it makes you feel

• 0 replies
• 0 recasts
• 3 reactions