# A Hitchhiker’s Guide to a Trustless Automation Protocol | Łukasz Stoczyński | ETHWarsaw [4]

- Channel: [ETH Warsaw](https://streameth.org/eth-warsaw)
- Date: 2025-11-09
- Duration: 13:40
- Watch: https://streameth.org/watch/yt-JuU6QnfGUh4
- YouTube: https://www.youtube.com/watch?v=JuU6QnfGUh4

## Description

Łukasz Stoczyński from Mimic Protocol talks about how trustless automation can work end-to-end and the next generation of automation infrastructure should look like.

🎥 Recorded at ETHWarsaw 2025

Follow ETHWarsaw on social media for the latest updates!
X (Twitter): https://x.com/ETHWarsaw  
LinkedIn: https://www.linkedin.com/company/ethwarsaw
Telegram chat: https://t.me/joinethwarsaw

## Transcript

everyone. Uh so my name is Lucas. Uh and I'll will do a hitchhiker's guide to a trustless automation protocol right now. Um uh so yeah, my name is Lucas. I'm head of go to market at Mimik. Uh I have been with the company for over 18 months right now and we have been focused on building onchain automation for the past four years. Um so we can call ourselves experts in the in this area. Um so to put the context to start like you know um set the floor here. So like what do we mean by automation? So uh as a user we mean it you know to interact with blockchain with uh without any uh manual uh intervention but as a developer you think of it as okay I want to execute code in a blockchain when specific conditions are met. So uh we're going to go through the journey where I'm going to tell you a little bit more about the protocol that we've built uh and what sort of a features we have built in uh to it and how developers can use it. Um and I'm going to have a little helper uh that's Marvin. Uh if anyone of you uh read the book or uh seen the movie the hitchhik hitchhiker's guide to the galaxy uh you probably know Marvin. If you haven't uh you should catch up. It's a really uh classic book and movie. Um, so we're going to go through the automation protocol, but like let's not forget about trustless and decentralization because like you know that's one of the reasons why we're we're here in web 3 is because we want things not to be centralized and um that something that we don't need to trust uh because it's trusts. Um so uh we're going to start with a simple um simple interactions like schedule transaction. So, uh, let's think of a simple transfer that you want to automate. Alice wants to send funds to Bob. Um, and you know, you need to do this. Um, you need to trigger this on a specific time. Uh, you could use a chron job to do this. Uh, and you could potentially use some centralized tools like gelato or or or open zeppelin defender um to do this. It's a simple thing. Uh, that's why we're starting with simple features. Um so we have got schedulers in the in the protocol that you can use. If we want to go a little bit more uh uh further into this, you want to check the balance thresholds. So you want to do the transfer but only if there is more than x you know tokens or or um in the uh in the account in the address. Um so u you need to query query uh balances beforehand before you um automate this transaction. Uh and again you could use potentially gelato or or or defender for this. Um um yeah so so we we've added thresholds so you can check that. Next thing is uh token prices. So um okay you want to make this transfer automated but only if there is a more than a thousand US worth of value of a token. So in order to do so you need to check the rates between the two tokens. You could use some onchain oracles if you want to build it yourself. You could use unis swap t- wops for that. Um but you know why build it yourself? Uh we have token rates embedded into the into the protocol. Um if you want to go a little bit more you know deeper in into this like you won't have any token prices. So a lot of tokens especially if you want to trade you know memecoin to memecoin or like go into some exotic tokens you're not going to have those tokens those token prices on chain. Not all oracles provide those. So um uh yeah for any any weird uh token prices you need to have offchain sources um because you know onchain sources are not always an option. You need some off-chain data for that and it has to be trustless. That's that's important. So we've added off-chain data sources into the protocol that you can use for your automation. Going further, okay, we've discussed transfers. It's pretty trivial I would say like you know you don't want to automate transfers only you want to go definitely more deeper deep uh than that so DeFi is probably one of the most important aspects that you would want to automate um so stuff like tokenized operations swaps bridging lending investing you know you could yourself integrate some taxes you could use aggregators you could spend hours on integrating different D5 protocols but why would you do so uh we've covered you for that and we have added DeFi integrations uh where you can automate any tokenized operations basically. Uh but again this is DeFi. We want to be more generic. We don't want just swaps. We don't want just transfers. Uh we want to do anything basically. Uh you want to execute any function on the protocol that you know a smart contract can support. So um things like arbitrary calls um you know you if you wanted to do it yourself you would have to program each of these audit again a lot of time spent a lot of resources required this is not scalable so we've added generic calls to the protocol custom triggers that's another uh cool feature that that we've covered uh so if A occurs on chain X perform on chain Y so you can have you know different different triggers that you check you know some onchain events on one chain and then you execute on another chain. So um arbitrary event triggers um you could use crushing oracles for that but you know we're getting like super complex in terms of uh developing these um and you know you could rely on some trustless data sources but again why would you uh we've added those custom triggers into the protocol as well. Um going even more important execution trustless execution. So storing the keys to execute these operations are risky. We don't want to store our users keys. We don't want to to do this. This is like a common uh security um risk right now if you're trying to automate something because you have to have those keys stored somewhere and and you have to give the access to a relayer or or you know um to a third party to do so. Um so uh we want to avoid storing critical keys. Uh we have to validate the conditions on chain uh and anyone could uh execute our code uh in a trustless way. So we've added a trustless execution that I'll explain how it works um uh when we get to the protocol infrastructure uh architecture sorry. Um and lastly, we want this to be easily updatable because you know today in today's world when you create an automation it's often fixed like making changes is super complex. So we want to allow you developers to change the rule. Uh so changes the rule not the exception. So uh we want to be able to update triggers, we want to be able to update conditions. uh we want to be able to update operations, stop executions and and scale executions uh in a matter of you know changing few lines of codes and not the the whole infrastructure. So uh the code is updatable in the protocol. So uh now what people usually think automating a simple thing uh but those who hasn't actually gone into deep automation uh don't know how complex it is like writing smart custom smart contracts scripts re you know deploying relayers making sure they have gas uh have giving access to private keys and you know if you want to do something new you have to kind of go all over the the process again. Um so um we've added all those features to uh um you know so basically all those features show you that you know it's not a simple thing. Uh and u that's what we call uh mimic protocol that's that's the features that we have built in into into the protocol that we're building. So what is mimic protocol? Mimic protocol is a three layer solution to simplify how you interact with the blockchain. Um layer one is a planning planning layer. So uh a user a developer um implements their own tasks. Today the tasks can be written in Typescript. So you don't need to know solidity. You don't need to know um any um you know um smart contract uh knowledge. Um the the TypeScript code is getting transpar and and other languages. Um you decide you know you you write your own logic basically you decide how you want to trigger them um and then you get the access access curated data from oracles and uh the execution is delegated to relayers. So in a simple manner, you write the task, you define all your logic, you sign it with your wallet um and then it goes into the protocol. The protocol does all the monitoring, checks the oracles, checks the prices, make sure that your conditions are are met and uh when they are, the protocol creates an intent on your behalf and that's how we get to uh execution. So there is no user intervention required. We're leveraging intents uh to do so. So whenever your tasks task conditions or triggers are met, the protocol creates an intent. The intent is uh being auctioned in the protocol to multiple solvers that are competing uh to to fill it. Um and obviously to to give you uh the best price, the best execution, the cheapest one, the the most efficient. you as a user don't have to, you know, care about like if you're going to be using unis swap or or one inch or if you know you're going to be uh getting the if you want, you know, define a yield percentage and you know, you don't want you don't care if it's morpho, if it's compound or a you can like kind of abstract all of this. Um so yeah, so so the intents are uh again execute based on the best proposals. Um and then um we go to the third layer which is the settlement layer. So basically the settlement layer makes sure um makes sure that um the um solving from from the solver um is matching the intent that you the task that you've created. So we have got some onchain safeguards that will make sure that um the the solution from solver is matching your request in the task. So um yeah we have settler contracts we have some safeguard engine. You can also add custom safeguards where you say okay I don't want any transaction above this amount to happen or I don't want to withdraw this funds or transfer this funds to any other address than X for example. Um so you can do a lot of those onchain safeguards to ensure that um your you know your tasks don't go um as uh as not intended basically. Um and yeah it's it's all checked on blockchain. Uh so um you get this like per uh enforcement the solver when they solve uh the um uh the transaction for you the intent for you um they have to um provide a proof uh to the protocol that you know uh there is a match between the intent and the uh and the execution and then the protocol checks it on your behalf. If for any reason it would not match uh then the the execution would fail and and basically the the task will kind of keep going. Um so yeah our main goal here is to push for standard. As I've mentioned we've been building onchain automation for four years. Um we've processed over $7 billion in automated manner for our customers. We have like a large B2B suite of customers that we're building custom automations for. Everything is built, you know, in kind of semi uh efficient way where we're utilizing smart accounts, we're writing scripts, we're we're like writing tasks ourselves. And um we've had a lot of customers coming to us for very custom uh solutions like very custom use cases. And even though we can automate anything, it was like you know it's taking too much time, it's not efficient, it you know will cost our customers of you know the developers time to do so. So um that's how we come up with mimic protocol because we want a standard that we can use ourselves. But then we also want to open it for everyone uh in this space to to uh use it and to make it easier for developers basically to um automate onchain tasks. So uh mimic protocol alpha version is live now. You can access it um on uh yeah live it's working on four EVM networks. Important to mention we're EVM right now. We're also working on the Solana deployment. So currently uh the protocol is deployed on arbitrum base optimism and Gnosis chain. Um, so you can basically go into the docs and uh through the docs uh you'll be able to generate your API key um and um create your own task uh define the task and get it running to to to have it tested. Um yeah, thank you very much for for listening and uh yeah uh let me know if you have any questions.