we have finally launched hub.sealcred.xyz!

remember the old days of having to grind through 1.5m constraints to create a zk proof of eth address ownership?

forget it

12k constraints is all you need to generate eth ownership zk proof

i'm going to explain how it works in the article sometime soon

🥳

cto @ bwl.gg (lunchbreak.com), 80M+ users (bdut.ch) 🙏 built @remindme, @mintit, @gpt, @healthbot, farcantasy.xyz

completely decentralized, permissionless and open source: github.com/BigWhaleLabs

we use github.com/personaelabs/efficient-zk-ecdsa to generate commitment for an address once

and then this address can enjoy insanely fast zk applications from them on!

Discover the best new web3 projects /launchcaster · https://nf.td/launchcaster

web3 / crypto ethusiast | CTO | former spy agency directory | nf.td/jay

building /creddd @personaexyz

previously researcher @ethereum

🕺 you guys rock, excited to see what's next!

wait till you see our next set of improvements :)

take a look at the circuits :) we ended up verifying precomputes for T in the same circuit where we verify ecdsa sig (bit.ly/3wTVzww) and we verify precomputes for U in the second circuit (bit.ly/3WWwEDa)

the check you linked to checks that the values of U are the same for both zkp's

but i'm sure you couldn't miss it

reading the code, it's not totally clear how you're verifying the precomputes in a way that's secure

specifically, I don't believe this is a sufficient check: https://github.com/BigWhaleLabs/seal-hub-ecdsa-verifier-contract/blob/main/contracts/CompleteECDSACheckerVerifier.sol#L100-L103