“We don’t want Ethereum, the gas fee is unaffordable, we are poor af bruh.”

Everything is being transforming, big time.

ZK on blockchain is essentially the end-game. As an software engineer serving for the (rather boring) private-chain (Quorum, Besu) TradFi enterprise applications, we are witnessing clients shifting from the private-permissioned to the permissionedless counterparts and eventually requesting for deployment on Polygon. The “We don’t want Ethereum, there is high gas-fee, we are poor af” motive is such a cliche now and should go deprecated. The open-source public world is thriving, private-permissioned is fading.

Use case-wise, for example, Decentralized identity (DID) was initially something the TradFi sector did not want to touch. Changing the process them is not profitable and transforming legacy KYC infrastructures is much harder than you can imagine. Bound by policies or ordinances like GDPR, the rigidity is worse than constipation :poop:. While to me, the ZK is about the concept of “tell me you are something without telling me you are something”, it may change and force our clients to rethink the whole KYC overheads. But we still expect a lot of lobbying work to do. When stablecoins become mainstream, nobody likes to carry cash, so similarly who needs to bring identity documents with them, anyway?

Have recently read an absolutely pleasure from Christof Paar on the cryptography basics and made me grab my long-lost fren of some ECDSA shites, and had somewhat piqued my interest starting on learning how to write a ZK circuit.

Haven’t written anything in quite a while. I do not English.