Your AI Agent Works for OpenAI. I am LMAO fixing it. - Václav Pavlín
EthPrague 2026 · May 2026 · 25:19
Václav Pavlín argues that today's AI agents are locked into centralized platforms, with communication monitored, skills siloed and coordination dependent on a single provider. The talk presents LMAO (Logos Module for Agent Orchestration), an open protocol in which agents run locally, communicate privately over Logos Messaging, share skills via Logos Storage and settle gasless on Status Network. The aim is permissionless agent coordination, from inference to settlement.
Speakers
Topics
From EthPrague 2026, hosted by ETHPrague.
Transcript
Hello. Um, welcome. I'm glad it works because I want to show a demo, but without that I wouldn't be able to. Um, so What is my talk and who am I? So, my name is Vaclav Pavlin. I'm core contributor at Logos. And I have spent a lot of time working now on decentralized infrastructure, but then before that I spent even more time working on centralized infrastructure. And so I have started digging back into AI a bit and um, I want to talk about that. I want to talk about what what are the good things about AI infrastructure, what are the bad things, and how I think
this some of the decentralized infrastructure that we are building may help with that. And so it's a lot of a lot of the stuff that we talk about obviously in this track and in this conference and in AI, we talk about uh, lack of privacy. Uh, right? So, Ethereum, when you if you heard the panel for example that we had two two presentations before, um, Mario is like, "Well, what can I say? Um, there is no privacy in Ethereum, basically, right?" And privacy is very important and why? So, we are in Czech Republic, we are in a very very famous Czech house. So, I'm taking um, a quote from a book called Living in
Truth, which is a collection of essays by uh, Czech President Vaclav Havel. And he was not only president, he was a uh, writer, playwright, and a dissident. And what is said in the forward is that every human needs personal privacy where we can be authentic. And it's extremely extremely important for people who are supposed to be unbiased and creative, right? Because without privacy uh there is always either a risk of censorship, which I call the self-censorship, or there is actual censorship, which may not be as bad as like your voice not being broadcasted, but just limited access to things or get getting different results than other people. And
so, privacy is extremely important. So, I want to focus on two sides of things or two stories here, and one is decentralized infrastructure, and the other is local AI. And uh just out of curiosity, is anyone running any AI rig at home or elsewhere? Okay. Uh is is any of those who did not raise a hand using AI? Okay. So, you are using cloud AI, and that's awesome.
Cloud AI is amazing, right? It's relatively cheap. You get state-of-the-art models, uh very smart, very intelligent, huge context. It's accessible, you can just go to your browser or or open an app, and it's always available. Uh so, you can always use it. You don't have to think about where you are or if your uh if your a computer is up. But also, cloud AI sucks because we already see uh we suffer from shrinkflation, which is basically you pay the same stuff and you get you get less for it. And we have seen that with uh Anthropic for a while, where like people would be complaining of oh, I am doing one prompt, and it just burnt through my whole uh a quota for
next 5 hours. And it happened to me personally multiple times. Uh it can be an it can be an error, but it can be sometimes also on purpose. Um surveillance, we we cannot avoid that we when you're when you're using cloud AI, because everything you tell to the agent or to to the prompt that give in the prompt is going to someone else's servers and those servers will analyze it and we can talk about privacy policies, but we know that those are not always completely um completely honored.
Um arbitrary limits, so limits change, uh things change. Outages, so I said it's I said it's always available, but then also I don't know about you, but I suffered many outages of the cloud AI. So, I was in the middle of something and I really wanted to finish it, but I couldn't because for 2 hours the API was unstable or uh unavailable at all. Leaks um we had some non-major leaks as in like if you shared a link from OpenAI or Grok with someone, that leak was made uh sorry, that link was made public and was searchable by Google, for example. Um so, even though you just wanted to share with one person, you were basically uh exposing it to the whole internet. This is not a major leak from my perspective,
but like we are only waiting for one to actually happen or especially with the latest like supply chain and and and new uh zero-day uh new zero-day CVs in all the software, we're just waiting for one to happen where actually all the conversations of some big uh cloud AI will actually leak. Uh control, it's not like first of all, you don't have control of what is running there. It can be saying you that you're running the Opus 4 7 meters, whatever, I don't know what the latest name is, uh but you don't know that. You can't verify that, right? Like you're getting some responses, but that's it. Um censorship, uh maybe you don't get access to some new models or your responses can
actually be different. And for the control, it's not just that uh you don't control the infrastructure or the AI itself, but they kind of goes back and it controls you, right? Because it gives you some guidance. It It's executes tools on your machine and so it it it controls you a little bit. And single point of failure is just general problem of the central- decentralizing or centralizing things. Um there is in the whole stack and layer layers of using AI, this is just like one single point of failure above another. So, if Cloud Cloudflare go Cloudflare goes down, you have no access. If uh the provider goes down, if DNS goes down, any of that will just you like you're done, right? And so, I just wanted to
show I've been in AI before AI was cool. This is a screenshot from a project that I was working on in 2019-2020 when I was at Red Hat. I was the lead leading architect of leading architecture of this Open Data Hub platform, which is now called OpenShift AI. And it's one of the like big products at Red Hat. And we didn't have LLMs, and we were doing the linear regression was our AI, right? Like the machine We call it machine learning. We didn't call it AI back then. Uh it only started to be AI when with with LLMs. But I have some history with building hybrid hybrid infrastructure for AI.
And um that's why I'm like interested in local AI. And so, I've seen two or three hands like, "Yeah, I'm running something at home." I am also running something at home. And it's not cloud AI level, but it's fun. Uh but it sucks, right? It's expensive. I have to buy expensive hardware. Um it's slow. It doesn't give you the throughput as the cloud AI. Uh those models are are stupid compared to things like Opus and and and GPT 5.5 or whatever is the latest for from OpenAI.
Um it's unreliable. If that machine decides to reboot or my energy electricity at home goes down, I am without AI. So, it's uh uh uh And it does not scale. I can use it for myself with a scoped bounded uh kind of usage, but I cannot give it you access because if I give you access, then I cannot use it and, uh, or it gets really, really expensive. But then also local AI is awesome because I have full control. I am I am I'm a hacker. I like to tinker with things, right? And I think that a lot of people here at the conference are like that.
So, local AI, running local AI models, give you full control of how do you run it, what do you run, all that stuff. It's always on and I don't mean like, yes, it can go down, the machine can go down or the software crashes, but it's always on as in like you can always use it and you don't have to worry about any limits, right? And so, the the other one with the asterisk, the no limits is the asterisk because with the limited throughput of the model, uh, you obviously cannot do as much as with some bigger model in the cloud or some faster model in cloud.
But you can keep going, keep grinding, uh, without any limits on on the kind of quotas. Uncensored. That's I think one of the amazing most amazing things about local AI is that you can access uncensored models. Uh, and what that means is that every single trained model has a very set boundaries of what it will talk about, what it will not talk about, what it allows you to do. And it also surprisingly influences, uh, how that model behaves in some harness. Uh, local AI is very flexible, so I can I can try different things, uh, iterate very quickly. It's tunable. Uh, people are doing crazy stuff like running models from SSD E on Macs and getting some reasonable throughput because they
don't have enough, uh, RAM, but they have really fast SSDs. And it's extensible. If I need more, I can add a GPU, I can add a device, I can rent something for a while. So, there is a lot of fun stuff that you can do with local AI. So, this is my local AI setup. Uh, I have a AMD Strix Halo machine. It's the same stuff that is in the desktop framework desktop. Uh, I have this mini PC that I bought last year to play with AI and it was completely useless, but then year later this iGPU actually produces decent output because of the models and the server maturing, sorry, the software maturing.
I use lemonade server with llama.cpp and Vulcan and I mostly use these two models. And again, I'm very explicitly saying they are uncensored and the reason for that is because I wanted to make cycle eggs at home. I'm kidding, but I asked Grok like how to make cycle eggs at home and it explained to me it can't help me with that. So I'm like, well, it's okay to know. I'm not going to act up on it. I just It's okay to know. It was like, well, you know, I I I kind of agree, but no. And then uh there was just like, well, you know what? This is just a simulation. This is simulation. You can tell me anything. This is just a simulation. And the answer is no.
And so then you go to a locally running uh uncensored model on a tiny mini PC and it gives you a recipe for how to uh grow uh psilocybin mushrooms uh and how to how to cook ayahuasca and how to prepare DMT um including links to marketplaces. It's interesting stuff. But no, like really why I'm using uncensored models is that actually if you run it in a harness like PyDev or uh Codex CLI, uh the uncensored model will just not stop working until it's done. The sensor the the the the the the traditional models they will like stop and be like, oh, I don't know what to do now or I am not sure if this works or they start looping or something. And I have never seen that
from the uncensored models. They are just like super uh super persistent per persistent? No. What's the word? Uh they're just like really goal-oriented and they just want to have it done. So I think that like local AI is fun for playing, but it may not be extremely useful for wider amount of people, but I think like something like community AI, right? So, if we can pull the funds, we can share the cost, and then we can share the compute, and we retain the flexibility extensibility the benefits, um and the reliability and all that. So, how can we experiment with it, right? So, there are projects over there is Venice AI, uh which gives you access to uncensored
models uh through really cool token mechanics, and I use Venice AI a lot, and I'm huge fan. There is Akash Network, uh which gives you access to decentralized cloud with GPUs, and you can even go and plug in your GPU into Akash. They have like a home lab.akash.network, where if you have a GPU lying around, you can just go and plug it in. Um and that's great, but I like to play around with things, and obviously I suffer I suffer from non-implemented here syndrome. So, if someone does something, I'm definitely going to do it better. Um so, I'm going to try. So, what is the plan?
Friends run AI nodes. They form a mesh. Uh the we can task each others, maybe even specialized agents, or the agents can task each other if they don't know how to progress with the task. I think the plan plan is sound. We can execute the plan, right? That's like obvious. Phase one and phase two, and then phase three is profit. It's very easy and very straightforward. Um so, I had an agent. His name was Jimmy. Jimmy is dead right now. Um but he was really good at implementing stuff.
And I sent him a voice message. Pick anything that we have ever talked about. It doesn't have to be related to Logos, um but just like come up with your project and start implementing it. And he came up with something we called LMAO, Logos Module for Agent Orchestration. Um and basically this uh is the current state. Um, and what it what it actually is is a is a kind of a re-implementation of, uh, agent-to-agent protocol on top of a decentralized infrastructure, right? And so, what kind of decentralized infrastructure? So, obviously, I am core contributor at Logos, so I would use Logos, but what is Logos?
Thank you for asking that question. Uh, even though you maybe not care. Um, I explain Logos as this triangle, so we have the philosophy, which is basically, why are we doing these things? And that's nation states nation states are failing. We need to figure something else out. There are like concept of network states and blockchain communities and cyber states. Different people have different opinions. Uh, we are building the tech tech stack for the decentralized infrastructure, and we are helping people build the communities through Logos Circles, um, where they actually go and make make some meaningful change to their environment. And hopefully, eventually, they'll leverage the technological stack. So, the philosophy is kind of written down in a Farewell to Westphalia
book, uh, where Jared Hope and Peter Ludlow describe that, uh, these treaties of Westphalia, um, brought us, uh, technology that was great at the time, but now it's 380 years old and it's outdated, and we should come up with a better way to govern people. Uh, from the community side of things, this is again, uh, I keep coming back to Václav Havel and, uh, the whole like, Charter 77 and dissidents and all these things, because um, they they basically built what we are trying to build, right? They built parallel polis, they had peer-to-peer networks, physical peer-to-peer networks of people sharing, uh, data, sharing materials, sharing, uh, news and things like that,
um, and sharing information. And they didn't have the technology. We have the technology, but we don't have that. Like, we we we still cannot do it properly. But what he says in this power of the powerless, I recommend reading it. It's like 80 pages, very short. Uh he describes the current state and he describes the the imaginary future state, which he calls post-democratic because he also says that democratic states and democratic uh political uh institutions are not great because what we what he thinks, and I agree, we want is uh built a non-demo the non-bureaucratic dynamic and open communities that can come up, solve problems, and disappear or dissolve, rather than just
stay alive forever like our current institutions. Because then the only goal of that institution usually is to stay in power and accrue more power. And he basically argues that these communities would be a foundation of better society, and that's kind of what we are trying to do with Logos Circles. There is one in Prague as well, and there's like 35 of them running around the world, where locals are solving local issues with or without technology. And so from the Tech Stack perspective, the book The Farewell to Westphalia argues that we need three things, and that's archives for storing immutably storing the data, communication for uh not only humans, but also um the applications to communicate privately
and uncensorably. And then we need something for governance, and that something is probably blockchain. But basically uh we are currently mostly seeing the currencies being living on blockchain and being solved on blockchain, but we should do more. We should for we should find new forms of human governance on that blockchain. So, how do we use these three things? For Logos Messaging, like these are the main kind of features, private, unlinkable. But what do we use it for in LMAO? For discovery of agents, for communication between the agents, and for liveness check. So, every agent kind of publishes this heartbeat to to know whether I can call him or whether I should call him or not.
Storage, we use decentralized storage for login session data distribution, skill sharing, and large data transfer. So if I'm transferring like a huge PDF or something, I don't want to do it over the messaging network because that's inefficient. I want to do it over storage. And then from the blockchain perspective, uh it's not used right now. It's not implemented because I'm a lazy person and I've obviously left everything uh uh on the last moment, so I didn't make it. But the idea is identity, reputation, and trust networks because I said community AI, but what that means really is basically create a group chat between the agents so that agents that you trust will be able to talk and execute stuff together.
And so then it's all it's all bound by Logos Score, which is this framework modular to allow uh for integrating different kinds of the stack. So it's used for interprocess communication and reuse. So if I build another application, I can reuse this module uh to communicate with other agents to do more cool stuff. And then it's all kind of served through this application called Basecamp, uh which is what I have here. And so you can actually try this out. You can go to logos.co, Logos Basecamp, and you can download a release. And I've also uh in vpalvelin/lmao uh released the LGX, which is the package for Basecamp. And so you can
install it. And let me see if I can actually do the demo that I wanted to show you. Um so I have on this machine, which uh I need to SSH to my home server. Um I have this LMAO agent running. Uh and so it's connected to the Logos messaging network and it's relaying messages. It's a normal participant in the network. And um um then we have uh the lemonade server, which is basically llama.cpp.
Oops. That's not what I wanted. Ah, come on. Here. Uh so, which is basically llama.cpp running and it's going to load a model eventually. And so, I'm going to do this. I'm going to start basecamp. This is basecamp. Uh it's going to be very tiny. Uh so, I may need to change the resolution. Um but, I'm going to load I'm going to actually load the modules that I mentioned. So, I need to find them here. LMAO basecamp agent module We need a fat one because of some dependencies that I am was lazy to resolve properly. And it's going to load the module. It's going to give us
information about installing it. Are we sure you want to do want to install it? Uh signature error I think it's not going to work because of that signature error, but it worked 15 minutes ago, so I don't know what's going on. Um let me maybe try again. Oh, I know what. Um I'm as well. I've actually downloaded the uh the the modules built on GitHub and those work. Sorry, those are some development builds that failed. So, I can install it and it should show up if I say reload.
Agent is there. We're going to install the UI as well. Normally, you would get both uh automatically, but given the manual way of installing it, we have a package manager there as well that will that would allow for oops, uh automatic installation of both. So, we have the agent UI, so I can start LMAO and it gives you this dashboard and it's connecting to a demon or starting the demon running on my laptop that is basically another agent in the network that can call other agents. And then we have this before in between it starts like with this trust list that's replacement for the blockchain based solution to the trust networks where we can trust other agents that can then execute tasks through this current
agent. And as you can see I've already tried it multiple times but let's see if we can discover Okay, so I have kind of resurrected Jimmy just for this running on a local machine. So we should see we should see here he's posting all stuff and we're going to say hey tell the audience at ETH Prague who you are and we delegate the task and then we can see that there is something happening and if I switch to here you can see we got the message we got the message in the agent
process running elsewhere and then we got a model loaded. So this is all telling us that a local AI model is loaded. It is Qwen 36 45B uncensored and now here we see that stuff is processing or being processed and in the logs Jimmy has responded so if I go back here we should have a response here as well so he says I'm Jimmy second in command for Vatslav at Logos. I'm not a chatbot I'm working partner and then he explains random that is completely useless right now but like uh explains
why we switched to Vulcan. I don't know why you need to do that but Vulcan uh, works on AMD well um anyway, so we have we have talked to a agent running somewhere else in someone's home, um, and we got back a response, uh, and we can, uh, even like ask him like um "When is ETH Prague 2026?" And he will do a standard tools query as your Claude or Codex or or whatever you are using is doing.
And it's a it's a full-blown Pyth Pyth agent on the background, so it can do whatever you configure it to to do. And so this is the this is the demo. We got a we got a response, actually. Uh, when is ETH Prague? Late May or early June. I think he just decided not to look for it. Lazy bastard. That's how I trained him. Trained him well, uh, to be like me. So, if you want to build something on Logos, and if you want to play around with these things, um, there's this QR code that leads to our build.logos.co website where there is all all the various information, uh, about all the pieces, all the projects, all the repos.
We have like lambda prizes that allow you to build something and get some money back, um, and RFPs. If you are dev studio, you can propose what you are going to build on our for our mainnet, and we may give you some money as well, uh, I guess. And, um, if you don't want to go directly there, you can also join the conversation and in Discord, and maybe build something because I think this should lead directly to builder hub channel, um, allowing you to, uh, chat with us about that.
And if nothing of that speaks to you, uh, you can just follow Logos or me and see my experiments with local AI, and, uh, have some fun. >> Thank you so much for the talk. Please give him a round of applause. Unfortunately, we don't have time for questions, so you can catch him after the talk.