Ariutokintumi & Jistro - Meet the Ethereum Virtual Virtual Machine: EVVM

Thank you everyone for being here. I'm with Kistro is the CTO also the EVVM and both of us are the architects. He's also the core developer. So uh we are presenting the EVVM theum virtual virtual machine. It's a virtualizer layer.

It's a new concept that we are going to show you. Um I don't know we can can we start? It's fine. Okay. So the time uh well first of all uh you can go to evvm.

org to check documentation to check another presentation we made and we are going to be inc France on July 2nd also presenting and doing a live demo. Through the slides you are going to see QR codes. Each QR code will drive you to a special part of the repo of the documentation that will let you get more information about what are we talking about. So first of all the state of Ethereum now in 2025 is L1 and there is many L2s there is L3s or other mainets is the same there is subnets there is app chains and all these new infra that is added to other scalability with new functionalities we think that this is solving so how the problem by approaching by different technologies But what happened historically in the in the internet space for scalability and for have more availability is to go in example from dedicated servers to virtual preate servers to the cloud. So what we are approaching is something like that.

So we are solving chain fragmentation and scalability with an infral solution. What this means we are we are pushing for vertical scalability. This means that with the EVVM that is a set of smart contracts that is about 60k lines of solidity you will be able to deploy a virtualized layer a virtualized EVM in this case into an existing EVM. So this is a virtualized blockchain where you don't need to add infra you will have an abstracted layer where you will see well please check the docs this will be available online also you will have a the possibility to create a lot of new functionalities there as it is a app chain a layer 2 a layer three attached to this L1 or you can deploy also in an L2 so what is already implemented in the EVVM that is very interesting is dispersed transactions. You can put hundreds of transactions inside one that will be executed for for that transaction specifically as one uh you can have executors that you will see in the demo that we are going to show you where you can give a voucher to someone else to execute your transactions but in your behalf.

So this is very good for for paying expenses to use AAI agents or or other functionalities that you want just to to have someone else to execute it in place of yourself. Erh you have tokens whitelisting so you can choose which tokens can interact inside this environment on the EVVM that is deployed on an EVM as a contract. You have also a natively named service that is full working that works with names that resolves on the EVVM if you want to use it in place of addresses and also uh we are working on the capability that is almost there to have phones and emails also working natively on the EVVM. It's important to tell at this point that the EVVM is an open source project that you can use uh for free for personal use and educational purposes not for commercial use but you are you are free to to install it to fork it to deploy it and and to do your modifications under the the license. So we also you also can have native tokens uh that are different from the native tokens of the EVM that you are deployed and will be respected as native tokens in the EVVM and we behave like that.

You have staking rewards. You also have a sync nons. This is very interesting. You can have syn synchronic synchronous noses that happens usually in the blockchains and also a synchron accounts and you have trusted execution environments relayers also implemented there that is very interesting for for D5 functionalities. So security your own execution environment rules.

You can make it permissionless or permissionless. As you see there is the EVVM and the EVVM is deital dealarized into the EVM or not. You you create these zones as happens with the routters and the and these kind of of implementations and you also you can tell who can interact with the EVVM and who cannot interact in the EVM. So you can make it open or you can make it closed. Uh there is abstraction.

Everything is abstracted inside the EVVM. So you abstract transactions that are into the payload of the intent that goes into the EVVM. This works in a everywhere intent structure unless you want to go permissionless to the EVVM as a user and you can go or you go with intent through a fisher or relayer. We call them fishers because uh on the conception we were using all the memp pools of all the blockchains for doing transactions into the EVVMs. How we configure very low has gas fees on the transactions.

So never going to be processed on the blockchains that we were using leeching the meool and there was fishers like fishing these transactions because they recognize it take it and relay to the EVVM uh environment. So uh we also have abstraction nonsense native tokens up codes. So this is more or less how how is the structure this the EVM the EVVM deployed inside a user can go permissionless or can go through a relayer that also can be a a T. So uh there is also a gel generation protocol inside that is working with a and what it does is uh every time you want to interact with the the mata protocol that is the EVVM that we made like the model but this doesn't matter could be your own EVVM uh you will synthetize the tokens that are deposited as collateral. So if you want to have USDC into your own EVVM, you will request the user to send this USDC to the EVVM through a contact address in a in any destination chain and make there a bridge.

You can use hyperlink IP acceler anyone or you can go uh maybe directly transfer this USDC to the EVVM if you code what is needed for the adapter but it's very easily and uh you will synthetize this USDC inside but what are you going to do with this USDC with this it bitcoin whatever you can use it on the five protocols while is being used inside the AVVM and generate jield with the gild build. You can earn money if you if it's your propose and inside is a game or something or you can uh reward all the actors that are making the EVVM work like in example relayers and you will give rewards to the relayers by doing good actions like executing transactions from the users for free and you will reward them with tokens that they need to stake and with the stake you will estimate how much is for each relayer every month and you will give them yield from what was deposited there. This is already coded and is already available. So uh this h now we can talk about service. What is a service?

A service is something that is working around the EVVM. In example we have peer-to-peer swaps. We have a loans from a uh we have the name service. These are services that are all around the EVVM as a smart contracts. With these services, you can interact with the EVVM.

You can give more extended functionality to the users and the services get rewards for using the EVVM. You can see also in the cure code and uh well, it's great to use as a sandbox. If you have an EIP, you can just code it into the EVVM, deploy it and ask all the devs and the users to start using it and and you will get a lot of feedback. You can do the iteration of of disable, deploy again, upgrade, whatever until you are sat you are satisfied with the results and then you can upgrade the AVM of your preference like an example I know mainet uh well uh so what we see maybe can the h the future of blockchain can happen in just one mainet uh the security is enough So what we are pushing is uh having like an EVVM for art maybe EVVM for defi unis swap can deploy their EVVM in place of deploying a new chain and like this and this is a question is have you ever seen a web3 hyper structure this is a reading it's an article very interesting that you can check for later web3 is for a hipper structures this means well there is all the explanations a lot of con uh con concepts And I invite you to read it and please join our Telegram devs group on the left and mint the official POP on the right. And well I now Kevin will show you a demo how is this is very easy to use.

So um let me load the demo. Okay, perfect. Uh I'm going to be uh a little bit quick just for the time. So uh we begin the the transaction. So we we have the central construction example is uh we can stop for this part.

Erh this part you use arc 191 erh to construct all the all the signatures inside avmn because all the executions are inside uh well try to configurate and well for the single payment for this example uh we're going to use can continue h connected wallet and So uh for this uh we're going to implement the address to send it and this part the single payment is signature structure. We can stop here. Perfect. Uh we had a concat of uh what type of execution we want. It want synchronous or asynchronous uh nons.

We had the receiver address, the the token address, the amount, the priority fee. We're going to talk about later, the nons and the priority boolean and executor also we're going to talk about later. So uh with this I can continue h we can we can form h that signature. So using our template we can find on the depths telegram group we can form the address or even a username. So if we remember the username can be a uh just a username email address or even a phone number.

We're going to generate the nons and token address and an amount and a priority fee. And for the execution erh it's very very easy. It's like a voucher. So uh maybe for an AI agent maybe you want to execute inside the EVBM uh you can select the address of that AI agent and send the transaction to be executed inside the EVBM. So after that we had all the data all the data we need to execute but uh because it's a test net uh we need to get token.

So uh inside the contract we had the add balance h function. So uh that uh add balance function uh you can add all the tokens as you want because all the tokens are um well I don't remember the name but uh because we had that abstract of the of the token of the token we can set any token we want in the test net obviously when the mainet goes uh you need to pass all the tokens from the bridge to the ABBN and for just forget the that token amount. So when you have the the files are ready, we're going to execute the pay no staking because we are not staking. The only difference the staking and nonstaking is the staking receive all the rewards and priority fee and the nonstaking doesn't receive anything. So we're gonna out all the data the from uh the address to send the amount h we're gonna get the identity uh clean because we're going to use the identity the token the amount the priority fee and the nonsh we use uh one 91 because uh it's untampered that means that any value or if you want to do twice the the nonsh obviously the transaction fails and you can h do nothing with this.

So you you need to get the equal data from the signatures and the transaction. So uh right now we executed the transaction and we're gonna see the balance for that address obviously with the token in this case is ether is a address zero and the m the token is address one and we get the amount I'll transfer for this h account but h maybe you can say okay it's good it's good but I want to get certain amount of tokens to certain amount of h addresses. We can do that with disperse pay just maybe you're gonna send a UDC to all your friends or maybe a default protocol or various default protocols. You can do that or even uh with pay erh with pay data er can go back to the last one.

Yeah, perfect. uh with uh pay multiple we can send various uh various uh pay transactions inside the ABBN all at once. That means if maybe you want to send some transactions to the D5 protocol or maybe uh various agents or maybe uh you want to execute uh because you are a fisher, you can do that all at once. Well, thank you. Uh, that's our presentation about the EVVM.

Uh, we have some minutes left for questions. Yes, that was a powerful introduction of everything. No, keep it. Uh, so yes, we're actually a little bit ahead of time. So, please do scan so we can ask the questions for are you talking to me and Jitsu?

So, will the EVM native tokens be public? available or strictly related on the to the EVVM's nameace.

Well, h the EVVM is a concept itself. So, this depends on the configuration of the deployer. So, in our case for the mata protocol that is what you can read in documentation because it's is the first example is not separated yet. uh we will make them available only within the space of the EVVM. So there will not be a contract outside the EVVM for the native token that is mate but you can make it there is no problem or or any restrictions to do that.

uh it's just about configurations is part of of the novelty and and gratefulness of of virtualizing and abstracted everything is that with just a few solidity code uh lines uh you can code op codes emulated you can code any configuration you might want and h the next question will be about optimization of course and if this is is more heavy processing than than do it natively on the client. Sometimes yes, sometimes not. But this is the first approach of virtualized layers. So of course there is a lot more to do. But uh the thing is that in practice is possible and a good part of the EVVM is that as everything is abstracted uh if you are the deployer and you set up the rules and in example you have only three layers you can fork it disable depreciate it from one chain deploy it in another chain the fork and will continue being used without notice by the users the banks or the institutions whatever and you can migrate it from the best option always.

So are the rate limits tied to the EV EVM the EVM's deployers on from in from master?

Okay. uh uh no uh the finalization time yes because you are attached to that and that's why in the in the previous question I I also told about the fork and move the EVVM within the ecosystem because if you are not convinced about the the rate that of finalization rate that is most important that block I think in this question because blocks are are happening very often now uh you can move it away. But remember that you can encode or or incept more than one transaction like 20, 100, 200 transactions in one transaction. So you will be multiplying the capacity of any chain that you are deploying on. So I see there's a little bit hallucination in everything.

This is questions that came in from the beginning. But my personal question to you is how did you actually come up with a concept of a EVVM inside a EVM? Well uh the thing is that back in time 2023 in Waterloo we were at at it global hackathon and we invented something that is called Rolamate in roamate.io io you can check it there is the live demo that was h a gasless payment solution for ethereum mainet and how we did it is uh we starting using the main poolool of ethereum mainet to configure transactions reducing nons and use it as a communication protocol with validation of signatures and we were listening to this mempool with relayers that we coded and executed the mnosis and innosis we had only an order book. So after winning the hackathon, we were requested by by some h enterprises to make this happen and be something real.

So we started to figure out the architecture to make this scalable, usable, secure and all these things and we realized that we need something like the EVVM to make this robust enough and secure enough. And well so the EVVM was not the product but was needed for the product. So at the end of the day we finish it with the product that is the EVVM and the payment protocol is a secondary product that is mounted on the EVVM. So this happens just because wasn't our objective. I mean it's a way to to form the startups and also to to build a company is try to go with the needs and not just following your own idea.

Well, personally that's why I love hack advance because you find the most amazing things. Do we have any questions directly from the audience? If you don't want to use the app, we can always come down to you with a microphone. Nobody have a burning question. Ah, there we go.

So I have a question. Um how is it how easy is it to add new up codes which are added to EVM or pre-ompiles or other you know native uh support?

Okay for that uh testing of out codes is just a proxy I like to call charter because um they they try to figure it out how to solve this. So with that pro uh proxy uh we call it as it is h you can hardcode it all the all the proposals to make that is the well that the up code I don't know if this solves your question or maybe

um I'm not sure I completely understood that um so you said you can you can hardcode the specific object you coded coded not hardcoded but you can implement that op code and simulate it inside the AVBM just for testing out the the input and output of that up code.

Okay. So for example if I need to use a new up code do I need to use for uh your protocol upgrade or can I uh implement it myself? How would that work? Okay, first uh we implement that kind of proxy. So you need to first uh upload uh you up code inside the blockchain they want to use the EBVM and after that you link that uh op code with the EVBM and you can execute that function related to that op code.

Okay. Or if you don't want to give that deep uh as Kevin said, you can just code it in solidity as an emulation and check how it behaves. And that's that's a good part because in the AVVM h the interface is the interface of the smart contracts. It's like acting like the RPC. In the AVM, the RPC is the interface to interact to the EVM because it's where you enter with the transactions.

In the AVVM, you enter through the interface directly. You are already on chain. So there you can emulate a lot of things as well, a lot of functionalities. You can call like simulated op codes and as you have all these EVM environments that is emulated is more easy to you to connect things and and try to to have a normal behavior than having just a smart contract with your op code alone there floating like that. So perfect.

So let's get the last question. We have just one that came in from gasla 87. Could EVM simplify even replace rollup architectures in the future given its ability to abstract gas tokens?

Okay, this question is a little bit spicy. So, uh when we talk about roll-ups, uh most of the roll-ups apps like uh unis swap or maybe warcoin etc etc. uh they have that community can implement nodes inside. But when when we try to use for enterprise solutions like banks or maybe uh import and export for certain areas uh they want to make that nodes h private as possible or even doesn't use any nodes for for that. So uh with this kind of solution of the ABVM you can make your own infrastructure without uh using any node system or or take care of that uh protocol.

So you can implement the EBBN inside of the blockchain of of you wish maybe a public chain or maybe a L2 or L3 and yeah you can simplify that rollup without any problem.

Perfect. I hope everybody got their questions answered.

Okay. So next up we got gonna have a little bit panel coming up and I want to thank you. Um are you talking to me and it was nice to sorry

thank you for your presentation and and be here.

It was lovely to have you.

So meet them outside and have a good talk with them. Let's give them a hand.