#dusk @Dusk
been circling around Hedger all week without actually stopping on one specific number that i think matters more then people give it credit for — proving time. specifically, fast in-browser proving, under 2 seconds, client side.
quick context for why this number even matters. privacy tech built on zero knowledge proofs has historically had a real usability problem generating a proof can be computationally heavy, and if that means waiting a long time (or needing a beefy server to do it for you) every single time you want to do something private, thats a dealbreaker for actual adoption, no matter how sound the cryptography underneath is. "technically private but practically unusable" has killed plenty of otherwise solid privacy systems.
Hedger specifically targets this with lightweight circuits that allow client side proof generation in under 2 seconds. client side here matters as much as the speed does — this isnt a proof getting generated on some server and sent back to you, its happening directly in your own browser. that has real implications for trust too, you arent handing off the underlying private inputs to a third party server just to get a proof computed.
why this actually connects to everything else ive covered this week — obfuscated order books, confidential transfers, all of it depends on proofs being generated fast enough that using the private version of a workflow doesnt feel meaningfully slower then the non private version. a 2 second (or less) browser side proof is what makes "privacy by default" feel realistic instead of "privacy as a slow, annoying opt in."
described plainly as enabling a seamless user experience at scale, which i think is the actual point being made here — the cryptography being sound is necessary but not sufficient, it also has to be fast enough that people dont route around it out of impatience.
$DUSK
been circling around Hedger all week without actually stopping on one specific number that i think matters more then people give it credit for — proving time. specifically, fast in-browser proving, under 2 seconds, client side.
quick context for why this number even matters. privacy tech built on zero knowledge proofs has historically had a real usability problem generating a proof can be computationally heavy, and if that means waiting a long time (or needing a beefy server to do it for you) every single time you want to do something private, thats a dealbreaker for actual adoption, no matter how sound the cryptography underneath is. "technically private but practically unusable" has killed plenty of otherwise solid privacy systems.
Hedger specifically targets this with lightweight circuits that allow client side proof generation in under 2 seconds. client side here matters as much as the speed does — this isnt a proof getting generated on some server and sent back to you, its happening directly in your own browser. that has real implications for trust too, you arent handing off the underlying private inputs to a third party server just to get a proof computed.
why this actually connects to everything else ive covered this week — obfuscated order books, confidential transfers, all of it depends on proofs being generated fast enough that using the private version of a workflow doesnt feel meaningfully slower then the non private version. a 2 second (or less) browser side proof is what makes "privacy by default" feel realistic instead of "privacy as a slow, annoying opt in."
described plainly as enabling a seamless user experience at scale, which i think is the actual point being made here — the cryptography being sound is necessary but not sufficient, it also has to be fast enough that people dont route around it out of impatience.
$DUSK
