Content
@
0 reply
4 recasts
4 reactions
Dan Romero
@dwr.eth
For someone who understands ZKPs: is there an easy way to make the EdDSA signatures compatible with ZK stuff for /frames?
7 replies
1 recast
13 reactions
EmpiricalLagrange
@eulerlagrange.eth
You could use this as a basis for private identity instead of fid: https://github.com/zk-passport/proof-of-passport Requires nfc scan of passport. You can hash the passport image or something to prevent replay attempts.
0 reply
1 recast
5 reactions
EmpiricalLagrange
@eulerlagrange.eth
What could make zkFrame dev easier is to make a new contract that uses this: https://semaphore.pse.dev Being gated by having a fid or w/e, and then the semaphore identity is used instead of an eddsa signer.
0 reply
0 recast
4 reactions
Alok Vasudev
@alok
cc @yisun @lsankar.eth
1 reply
0 recast
1 reaction
EmpiricalLagrange
@eulerlagrange.eth
It really depends what you’re trying to do. Verifying an eddsa signature in zk isn’t the hard part. Do you also have to verify the key is a valid signer for some fid? What about fid replay protection?
1 reply
0 recast
1 reaction
EmpiricalLagrange
@eulerlagrange.eth
I figured out the easiest way to a v1 for this, cc @dev Use SGX to output valid signers for a FID, this output would be signed with secpr1 ecdsa. For privacy you can request multiple fid signers to hide the real one. Requires an eddsa + ecdsa + intel certificate authority check in ZK. Can be done in WASM
0 reply
0 recast
0 reaction
Alana Levin
@alanadlevin
@dev
1 reply
0 recast
0 reaction
Idan Levin 🎩
@idanlevin
@kobi
0 reply
0 recast
0 reaction
