We will be hosting our first AMA featuring the following PSE Projects (https://pse.dev/en/projects). Send in your questions as a reply to this case and the teams will try to answer them on Wednesday Feb 21st.

A list of the projects attending can be found below 👇

Working on building zkTLS infra/products. A ruthless empiricist and meme connoisseur.

/opacity

and

/eulerlagrange

@vitalik.eth I’m sure you have some questions for these guys.

I wanna answer this so bad… will let the team handle it though.

How long until we can make TLS Notary stateless, where we don't rely on notaries, but users can create proofs of their TLS sessions complete client side?

Anon Adhaar
Bandada
MACI
QFI
Semaphore
Email Wallet/ zkEmail
TLS Notary
WAX (formerly BLS Wallet)
ETHSim / Semaphore network
NxBn Collab
Trusted Setup - P0tion - Definitely Setup
Summa

I've only talked with him over telegram, but hes nice, super technical, loves diving right into the deep end.

You guys ever interact with Vitalik in your work? What’s he like to collab with?

https://hackmd.io/FJBcmQCoREiPKlE9r0rw2A?view=

I feel like I thought of a way to significantly speed up client side zk

Basically you use a custom lookup table for each proof (the parts you can make public)

Anyone working on ZK wanna give me feedback on this 👀

Anyone working on ZK wanna give me feedback on this 👀

https://warpcast.com/eulerlagrange.eth/0xa9fe2acb

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

Const generics are mid, why do people use them?


cc @sinu

Computer Scientist • Building at PSE - EF • Web3 • ZKP • She/her

small brain (TEEs) crypto ✨find me on #tee-s

I'm guessing @vivianplasencia is going to respond to a lot of the questions heh

Interested in ZK, FHE, PUFs, hardware, system design, ai safety, and smart contact security.

Nice, I've only spent a little time with noir and risc zero, I feel like I'm still stuck in the stone age whenever I write a circuit in circom but it's what I've become comfortable with

It really depends on what you need. I need speed to deliver a good UX, so I use a DSL (Noir). A lot harder, and recursive proofs are a bad UX.

If you can do it in a backend, id just use a zkVM at this point

For anybody writing circuits, what's your preferred method?

Devrel @aztecnetwork | ex Aave | Posting about blockchain privacy 

Seconded. People hear ZK and immediately think using it makes everything magically private 😂

Not a PSE member, but wanted to chime in.

I just started a company that uses zk, and our tg market includes web2. Those people automatically associate zk with things like Tornado cash.

I just say verifiable compute now 😅

What misconceptions do you keep hearing about ZK?

A Jaf of all trades (🦍, 🚴‍♂️)

Post your Q under the announcement cast.

They will go through the questions there :)

what existing in-prod tools do we have to combat spam on farcaster?

what is possible today vs 1yr from now?

❤️⚙️🧪R&D @PSE opinions are my own and subject to change. 

Mass scale polling with participation filters based on private identity information. I want people to be able to signal preferences privately while being robust to sybil shenanigans.

What do you want to see built? What are your needs? Not as ZK devs, just as users, what do you want to exist that currently doesn't?

TLSNotary only really makes sense for cases where there is some privacy requirement, such as hiding an access token in a request. There may be some usecases where an Attestor doesn't have access to some offchain data but some other party does. TLSN could facilitate proving that data to an Attestor so they can sign it.

what are ways in which TLSNotary and other PSE projects can augment non-privacy preserving, onchain, somewhat trusted attestation projects and standards (using that term loosely here) such as /eas

We helped organize the progcrypto event with 0xPARC at devconnect. There are also sometimes collaborative projects like with audits/security or zk email.

me and @cedoor collaborated on Zupass / PCD before DevConnect IST w/ some core developments & boilerplates / examples

https://github.com/cedoor/zuauth
https://github.com/proofcarryingdata

We helped organize the progcrypto event with 0xPARC at devconnect. There are also sometimes collaborative projects like with audits/security or zk email. https://github.com/privacy-scaling-explorations/security

how closely (or not) do y’all work with 0xPARC?

I can bring significant perf gains to zkML, stay tuned 👀

I don't think right now, we have looked into that, but EZKL is pretty awesome for proving training and inference cc: @jasonmorton

@atheartengineer - is PSE doing any zkml work, particularly around small models?

Building @megapot, advising @zkp2p, ex-Set Protocol

/lab

Soon? Maybe? We're finishing up one chunk of work on the client (you'll see the results soon!) and then we may tackle mobile though that's not written in stone quite yet

We (zkp2p) would also be interested in taking any questions too!

Software engineer at the Privacy and Scaling Explorations team (EF)

It's a good idea. Only drawback is that it needs extra work for observers to prove validity. And that introduces technical debt for the membership data and proving artifacts. We often want the ceremony to be provably secure to an observer many years in the future.

what’s wrong with using a burner address and using TLSNotary to attest to / prove certain things about yourself to reinforce sybil resistance

i suppose like zupass or gitcoin passport(ish)

do you think ceremony participants should be public?

E.g.: if I contribute to the 4484 ceremony. Would I want my address to be public or would I prefer to keep it private?

Public pros: people can see who participated and trust they deleted the secret

Anonymous pros: my support to specific projects remain private

## 😎 P0tion allows you to set up your own VMs (AWS EC2 or Google cloud functions) to run the coordination process. Every participant can sign in with GitHub and Bandada (Anonymous groups). We are in the process of implementing Sign-In With Ethereum. These mechanisms allow us to protect the ceremony queue from bots

P0tion (I work with @geoffl, @ctrlc03, @0xjei and more people)

## 🥺 P0tion is a developer tool to make it easy to run a ceremony for your circuit. Every time you write a Groth16 ZK circuit you need to run a ceremony with different participants so a secret does not get revealed

/// Simple Q to start with from me 👇


# Can one person from each team explain what they work on in two ways, one for each persona below?


## 🥺reasonably intelligent, non-technical normie

## 😎the most giga-chad, galactic big-brain, “doesn’t know the price of milk” cryptographer you know

working on blockchain privacy

https://joshcrites.com

We've been working on a Mercado Pago implementation! Ran into some issues with it not having a signed timestamp. Have some workarounds but they introduce us as a trusted party (we sign on the timestamp)

zkp2p is extremely promising for me:

Transfer Venmo USD to on-chain USD in a moment with no intermediaries 🤯

 (we need a non-venmo version in Latam because there is not much support for it)

@bad-wisdom can tell you more

What ZK projects (other than your own) are you most excited about? Why?

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

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.

how do you folks make proving system decisions?

what are some low hanging fruits that devs should focus on right now to make privacy tools easier to use for end users?