EBA | Enabling Standardized Executions Through Modular Accounts - Eugenio Reggianini | ETHDam III

Welcome to East to E to E. Yeah. Amazing. Let's welcome our next speaker. Uh this talk is enabling standardized executions through modular accounts.

Thank you very much. Well, nice to meet you everyone. My name is January Janini. I'm going to go through this uh uh definitely less technical speech and more let's say product and business and inspirational speech about research that I was honored to lead with uh another group of very smart and interesting people about how to merge usability and privacy in a standardized way for onchain services. Um so let's start from a little bit from uh from market market perspective right so we we we see a couple of trends coming from users users want to do more things and more complicated things on chain essentially at the same time we are um we are embracing with features which allow us to aggregate signature doing more things on chain and we see the need for embracing cryptographic primitives to reduce the amount of data which is posted on chain and for some cases also um ensuring that some some level of uh computation is executed in a private environment.

This is to ensure compliance and to provide an a more efficient user experience. So how we can achieve this on one side in terms on from UX perspective we can enable contractbased account services uh which can be plugged with different model functions. This is a good combination which combines flexibility and usability. We have seen the adoption of contract accounts based services enabling for batching transaction enabling for such social recovering for uh meaningful purpose of doing things on chain which were not possible uh before. On the other side, privacy is actually addressed by different uh uh cryptographic techniques which allow us to reduce the amount of data which is posted on chain to run cryptographically in private environment in trusted execution environment but also in in on let's private computations uh a list of se of selected action that the users request us to do uh on chain.

So we what we what we envision for coming features that a blockchain based account should having um an identity contract why uh I need to be able to prove that I'm requesting the these action by myself and so for essentially anti-cill protection I need a contract account which can be flexible to execute different functionality which the user are requesting uh to me as a service provider. And a third one a privacy feature which enable to essentially uh provide um scalability to solve scalability issues in reducing the data which is posted on chain but also in addressing full cover initiality of certain action especially when we are applying um specific uh use cases in a competitive environment which is uh probably the case for per public permissionless network when everybody can propose new things. Um so what we are giving really as a user into this concept we are giving a an identity which can coexist with privacy and can coexist with uh I would say flexibility provided by contract accounts and their own capability signature aggregation modularity batching and so on. Why the user need this? Because at the same time we can enable an an improved user experience.

We we can support multiple target of markets from retail users to enterprise users and also we take care of uh privacy from data management perspective. uh this project has started um a few months ago started as a research which which was results I'm I'm actually showing here today with the support of a couple of uh communities and grouped which grouped a list of professional which I am honored to represent here and we are slowly uh going to uh a development environment where we are going to test essentially this new set of features for a blockchain account and we are always open to if you're interested to collaborate with us. Um our general user flow would look like um that's actually where I think we we can spend a little bit of more time. Um essentially these three product features they are combined together. Uh the first one is an identity contract as I was mentioned before which is um used by user to create a test station uh which uh are proven on claims that they request to execute action on chain and this can be taken by uh smart contract on chain atestation by NFT minting or sobound token mintings.

So essentially I am creating my onchain identifier state for enabling me to expressing what I want to execute on chain as a user operation. That user operation then it is relayed on a meool and which is assembled by a bundler and interact with the smart contract account capability. The smart contract account capability validates the user operations, generate a known for the extended transaction and then communicate with a set of modules that are essentially having the goal of minimizing and uh the data sharing which will be authorized on the network and manage the executions on a private computation using uh using by that. So a ZK validation model which verify the proof of the onchain identifier state generated by the identity contract and a fullomorphic virtual machine which actually execute on a privately basis the the gener the user operation generated by the user authorized by the signature verified all this transaction payload is transmitted to the contact point that then at the end execute uh for the users on blockchain networks. Which kind of use case we can empower with this setup?

First of all, fully confidential voting. We we have seen that so far we have been developing onchain governance systems. uh but let's say sometimes the the level of engagement in uh the onchain government has been lacking. Why? Because of lack of uh harmonization and fully privacy on uh operating and casting voting operations.

Why this concept could uh reduce the gaps and we think that can support the engagement on onchain governance voting procedures because on the identity contract side the members can actually provide a system that uh establish anti-se mechanism to prove that they are authorized member to cast their vote on the with um uh fully omorphic environment they can actually execute uh confidential their confidential voting power that is encapsulated in their token holding position. In that way, the contract account will you have to think that will generate a sort of ballot in which an accumulated power of token holders who voted to support one decision will uh be able to match the threshold for a specific proposal or not without uh fearing of uh being traced back in terms of uh if I'm without omorphic encryption if uh I would if my voting capability my voting power would be able to um posted uh after the execution of a proposal potentially because we are in a blockchain environment which is fully permissionless. We would be able to see who actually voted by associating the voting power with the nullifier. The changing environment uh from voting to trading with different logic. This kind of setup can enable uh a broader audience of traders which uh not only focus on uh business dynamics but also on regulatory requirement to access trading venue.

In this context, the identity contracts takes care of the on boarding but also of the compliance requirement which are enabler for investors not members anymore to access trading accounts and at the same time the uh fullyomorphic encryption um make sure that the trading APIs which are requested by the user operation are matched in a private environment by the trading account without disclosing the internal trading uh operation that has been executed in order to achieve that results and uh thirdly um is what I described here a supply chain/ NFT distribution environment reframing there is an environment where myself as a buyer account I'm going to a procurement process for a grant for a program for different reasons I need to make uh sure that my supplier meets the the procurement requirement that can be verified with zero knowledge cryptography in order to get access to this procurement process and at the same time for a matter of competitiveness. uh if I get selected and awarded with the for the project with the money, I want to make sure that my award selection gets run privately without providing public knowledge also to competitors that I was selected and keep my competitive advantage. So to conclude what this um this research I think uh match to discovered the by combining user experience and compliance and privacy we into an account set of features which combine contract accounts and different cryptographic techniques. We managed to aggregate messages willing willingness of the users users operations. We are able to verify in a granular way the signatures of each uh each of the aggregated signatures of the users and we are able to execute those requests on chain on a private environment keeping the the keeping the permissionless network in a competitive space but taking care of the compliance requirements.

I think that's all and I thank you. Thank you. Any questions? If not, that's all right. Thank you very much.

That was really good.