Enabling standardized onchain executions through zk validation modules

Transcript

[Music] okay hello everybody thanks for being here my name is Antony and well we will change for a very Broad and inspirational talk to something very very concrete okay here the question is that as maybe you already know with Jordy and David we created different Solution on zero knowledge proof like the ZK rollup of polygon at the Iden 3 Foundation and and Privado that is the tooling of the protocol of Iden 3 that is more used in in identity and privacy and today we will we will address this problem this problem and this is one analysis that aeno has done has

performed about how enable these standardized executions through modular accounts something very very specific and very concrete and basically as an introduction here we have this tradeoff between the complexity of the executions that the time are bigger are more complex are more heavy we can say and at the same time uh we need to be compliant to address all the all the problems that Regulators are are scrutinizing how The Regulators are scrutinizing us how we ensure privacy in the transactions and H at the end how we find a balance between these two forces that they are trying to move in an opposite way no then one one

way to do it is through this um modular contract account which by one side they allow us scalability because they have this composability H aspect which allow us to to to perform Super transactions for example in the same block which is something very very concrete and at the same time this is adding this complexity of this Lego of this puzzle how you you are able to ensure that everything is performing in the in the right in the right way and basically uh here is is where zero knowledge can help a lot because as maybe you already know all the data can be a stored of chain only the hash that is H somehow um is is ensuring that all the data is correct is

what it's stored in the in the blockchain and at the same time this is giving us the the the trust that execution has been done in a proper way okay then with this introduction I pass to to hen thank you so welcome everyone uh what is this ZK validation model for contract account I try to summarize here uh some ethereum reference standards uh under three main pillar let's say the first one are two main core reference standards for contract accounts so the standard ERC 437 which of course perform uh bunders to the mols the entry point contract singl ton the verification Loop and the execution Loop and we combine

this with the modular setup which is a minimal modular setup we know there are two different way of doing modular contract accounts ERC 79 and ERC 7579 in this minimal setup uh we try to um reduce at best the performance that we can achieve by aggregating the ZK sign the ZK proof the signature to the ZK proof and do the batching essentially the second pillar is essentially needed to enable the two smart contracts the contract entry point which is a single tone contract and the ZK validation model to talk to each other and the third one is the magic Source within the ZK validation model which is ERC 1271

which allows essentially to have a standardized Logic for verified zkc um so from product perspective what kind of value we bring to the table we I wanted to use this slide to show that this actually product solution is quite balanced between um compliant uh which is given from data perspective in terms of offering onchain data minimization and offering a standardized way to verify Sig and adoption and user experience by providing of course uh the batching capability through signature aggregation and providing also a way to validate with different authentication authentication rules uh

one set of execution uh so why user may need this because we improve ux we enable let's say more complex use case we enable user to ask many things that needs to be uh done on chain we can support Enterprise adoption because Enterprise care about compliance because it's a risk for them and general source of Truth data minimization because for not only for compliance but also for Network efficiency is very very important um this is a project started a few months ago with the support of uh many different communities the centralized identity Foundation idry eum Enterprise Alliance European blockchain

Association and and companies from the industries like Privado ID rhinestone and and others um I wanted to give you a general idea on how a user for may look like so everything starts from the user the user create a verifiable credential which essentially attest the ownership of of a specific data to um to a specific signator and then um it generate a user operation as a message that wants to be executed on chain and uh essentially generate a ZK proof Associated to that then the user operations fall into the M poool that through a bundler calls uh rely on chain the entry point contract the entry point

contract execute the verification Loop so generate a know and um uh may make the gas a fee estimation and then called the ZK validation model to verify the ZK proof which are generated to the user operation and upon the verification of this execute all the user operations on chain um a potential use case that we are actually um testing at the moment because this project started as a research and then is slowly evolving as a as a testing and development and testing environment is uh let's say belongs the Dio environment because we by interviewing different Dows safe Aragon we understood that there was an

issue in terms of Engagement within the da and um essentially this led to the fact that proposals that were made public on the Dows are either were either approved or were not rejected because of people fearing expressing purely their vote on chain because there is any way a a degree of transparency between the public address and the voting power so so this is where ZK can come in and establishing the eligibility to have this voting power without revealing the public address and of course we can combine this because we use contract accounts with batching and essentially if the proposal meet the threshold and get passed he essentially

use contract entry point to efficiently execute funding allocation or whatever is needed by the by what is described in The Proposal that has been vote so we think that here for instance we create two big core value impact for the for the community firstly we increase the engagement on DS on members on DS and we reduce the risk that um there is a vote manipulation because of extreme transparency and so we we believe that we can enhance a better trust governance on chain um so the the real clear message that I want to share here is that in my mind uh dkp and contract

accounts have a natural fit together with this setup uh where zkp offer data minimization and compliance for a client side perspective and contract account make the magic ex aggregating signature and aggregating items that needs to be executed on chain um so with this I think that I can close for a moment and ask for a question okay yes yes well we for generally our analysis so far is that uh the cost of this solution it's still relevant in

terms of use case which requires multiple layers of aggregation but considering the evolution of the the technology and the amount of uh effort that the industry is putting in decrease the cost of verification we think that in a reasonable time frame this solution will be very much viable from a cost efficiency perspective and and also sorry and also there will be there is this component of okay maybe for certain Dow it's almost subsidized or it's free but let's say if if you want to vote in a government as we're speaking with different governments in in in the world then maybe they are more eager to pay because they need more security no then

here you can create like different like a different cost layer because also it's not the same if you vote for a dow for mem coins whatever but if you vote for for a country yes to choose a president no then according to that H we are thinking on on a different H price Model or cost model in terms of in terms of testing I can't really now give you an estimation in terms of of cost concretely but also have a strictly r implic implication of where you are doing the proving layer two layer three or on a layer one native so we are doing the development right now and we are gathering uh actually those kind of metrics I like

that um so my question is you you showed the example with Dows but can it also be used for um hooks in Unis swap for example to um make permissioned uh pools or anything related to defi yes yes yes actually for like uh a question of time I just disclose one one use case but we are actually thinking on additional use case one is the one that you you have been thinking essentially from for trading perspective you can have users interacting with different trading platform and they a sort of creating their own portfolio environment and essentially aggregating

different zkp according to the trading strategies that they want to execute and then let the contract at point to do the magic or additionally I can tell you we are working on something which is more Enterprise oriented so for instance you we have a lot of use case in the blockchain where you want to track and Trace things and then you want to sell these things uh and use blockchain for traceability yes so you can combine this use case and having different suppliers providing zkp of their Milestone on the supply chain and then potentially use the contract entry point to main nft at the moment of the sales where the contraen point is managed by the distributor the buyer and and essentially mint the nft to the user

after the verification of the zkps so yeah the the the the this solution is uh is quite flexible and can be adapted for to many many Industries uh really am I thanks for the um presentation but I I'm still in that um um which um part of the context of information um can be the projected in in your your modu and uh is the casur in your modu customizable or customizable by the users because because you know different users have uh have different um um Tech or context to

to to to be protected maybe someone may want to protect Identity or some some other maybe asset or balance so I wonder that um how how keep circuit um I mean how CC formed and is and is that and Custom isable or not well sorry how about the C ciruits I mean the c c is customizable by users or not yes yes totally I mean we have created for ZK circuits you have all

these uh program language that is named thcom that was developed by by Jordi and his team and and then yes it's totally modular and you can create the conditions that you want then yes you you can adapt it as you want this is open source at the ID three repositories then yeah so you build user interface based on circum based on circum ciruit Lang langage basically c will be your your base the the idea here is really to create a standardized authorization framework to have the user operation executed upon the ZK verification so what may happen is that the client which is probably in the case of the da hosting the the the da

environment with the modular smart contract can have a specific custom ZK circuit built upon uh identified use cases that he wants to apply this product Oh I got yeah now I I know it's customiz work great do we have any other questions from the audience today all right thank you so much for your presentation we will begin our next presentation at 12:10 thank you thank [Music]