🌐 Exploring zk Solutions for Enhanced Scalability and Privacy in Polkadot

Tech Talk
1

:globe_with_meridians: Exploring zk Solutions for Enhanced Scalability and Privacy in Polkadot

Hello Polkadot Community,

As we continue to innovate within the Polkadot ecosystem, I would like to initiate a discussion on zero-knowledge (zk) solutions to enhance scalability and privacy across our network.

Discussion Points

  1. What zk technologies are currently being utilized within the Polkadot ecosystem, and how effective are they?
  2. In what ways can zkSNARKs and zkSTARKs be integrated into parachains to improve transaction throughput and reduce gas fees?
  3. How can we leverage zk solutions to ensure better privacy for users while maintaining compliance with regulatory standards?
  4. What challenges do we face in implementing zk solutions at scale, and how can we collaboratively address these issues?
  5. Are there existing projects or prototypes within Polkadot that successfully demonstrate zk technology, and what can we learn from them?

I invite insights, experiences, and suggestions from developers, researchers, and community members interested in advancing our understanding and implementation of zk solutions in Polkadot.

Looking forward to your thoughts!

Your GitHub or Contact Info

2

I think Calamari should be mentioned here, even though it took me 7 hours (!!!) to do my first private transfer and on the way I learned a few things that de-facto limit the privacy enhancements, scalability or UX which may serve as a learning. Let me share a few observations:

  • The Calamari browser extension took 75min to initially sync. This is a systematic scalability issue as the design requires the client to know all private txs to search for those involving oneself. (Do not mindlessly delegate this to a service provider because you’ll trade privacy for convenience - yet again)
  • I needed to obtain KMA although I just wanted to transfer KSM and XCMing my way through the network cost me quite some time and motivation
  • Once I was able to transfer KSM privately, I observed that the fee payment in KMA is transparently recorded on L1 and therefore linkable to wherever the KMA came from. Not very private.
  • the tx size is ~10kB (10x larger than usual balance transfer) and every private tx has to go through L1

Now to the positive: It worked! And I think we need to see more projects like these, learn and improve.