@WAWoloszyn TEEs provide cryptographic proof of something, but not necessarily the right thing. You need reproducible builds to independently verify the hash of the code that generated the output, otherwise it's worthless
Proud to present our technical explainer for the SAVE framework (Structured Attestation & Verification Engine) that @MidasRWA relies upon for its Attestation Engine. We're confident frameworks like SAVE will help make DeFi safer.
https://t.co/iGZO0rDT5H
ZK proofs were first conceived in 1985 and remained largely theoretical for ~25 years — the math worked, but the compute didn't follow.
Faster hardware, cloud computing, and blockchain applications triggered a Cambrian explosion of ZK protocols in the 2010s.
@MilkRoad Separate execution and consensus clients are a security and reliability benefit, we shouldn't merge them but wrap them with a deployment helper
Massive implications. 13-second finality under normal network conditions (~99% of the time) unlocks real-world payment and settlement use cases. Also dramatically reduces reorg risk for bridges, L2s, and offchain systems
Um...did the EF just roll out a way to drop Ethereum finality from 13 mins to...13 second??
Bullish if true.
Fast confirmation rule.
https://t.co/kY9cN8OSOz
1/6 This is our first deep dive on privacy preserving tech on Ethereum. We present the @umbracash stealth address protocol, enabling private payments on all EVM chains. Senders can generate one-time addresses controlled by recipients, where only sender & recipient know the link.
6/6 Umbra UI hosted here -> https://t.co/nlLYytCiFH
Built by @ScopeLift and open-source -> https://t.co/ol7IBA7Egg
Stay tuned for more deep dives into privacy preserving techs (ZK tech next)
5/6
Key advantages: No mixer/tumbler required (legal risks). Identity of receiver can be revealed selectively if needed. Gas efficient.
Drawbacks: Sender's identity, amount/token types are visible. secp256k1 is not quantum resistant. Limited programmability/composability in DeFi.