Alter Ego (pipsandbills)

Alter Ego

web3 is my alter ego. https://x.com/pipsandbills https://zora.co/@pipsandbills

16 Followers

Recent casts

Top casts

going over miden's zk-based privacy architecture and realized something important: miden will launch with a centralized sequencer, and with zk alone, that means the sequencer can still see your data. it's like sending a whatsapp message where the encryption only hides how the message was typed but whatsapp hq can still read the actual message that means the “privacy” tagline isn’t end-to-end yet. what you have is a computation privacy not data privacy but that could be improved with @zama 's fhe integration let's break that down 🧵

  • 0 replies
  • 1 recast
  • 3 reactions

miden is one of the strongest zero-knowledge VMs being built today. It gives you: • private computation (your execution trace stays hidden) • STARK-based cryptography method • verifiable correctness • a scalable zk-first architecture this is huge. but there’s one thing miden cannot give: a guarantee of end-to-end encryption. why? because zk proves correctness, it does not hide data but when you combine that with fhe, you can have computation on a hidden data that has been proved correct! meaning: • storage = encrypted • mempool = encrypted • execution = encrypted • state = encrypted • node visibility = zero this is the actual end-to-end encryption. so with zama inside miden, you could have an end-end encrypted chain that works even if the sequencer operator are malicious tldr miden gives private computation. zama gives private data. put them together and you get something better: a verifiable, encrypted, adversary-proof L2.

  • 0 replies
  • 0 recasts
  • 1 reaction

you might want to pay attention to this, seeing that privacy has been a mainstream narrative web3 throughout its history has had 4 privacy model: • mixers: hide linkage, not data. Breakable with metadata - @zachxbt has done this many times • zk: prove correctness, but doesn't hide execution state. • tee: rely on hardware, broken by @danielgenkin and the TEE.fail team. • mpc: requires large validator sets, expensive for smart contracts. all the above works and might be useful in a niche case but none of them survives malicious operators + malicious hardware + malicious networks. 🧵

  • 0 replies
  • 0 recasts
  • 1 reaction

Onchain profile

Ethereum addresses