The One Question bounty closes Thursday 10 December.

Join in
We Them Media logo We Them Media Support us

From ChatGPT to ChainGPT: Shipping Autonomous Agents on Ethereum - Opeyemi Stephen

The picture loads from YouTube. The player loads only when you press Play. Turn on captions in the player if you need them.

Okwuyemi Stephen of Gaia AI talks at Web3 Lagos about building autonomous AI agents that act on Ethereum. The talk sets out five layers: an agent app that plans, an inference node, a signer that enforces spending rules, an RPC provider and a contract. Stephen shares a starter repository and urges listeners to own their intelligence.

Not by We Them Media Channel: Web3Bridge. Published Tuesday 9 September 2025.

Titles are the owner’s. It plays from their channel.

Transcript

This transcript may contain errors. This video belongs to Web3Bridge. Letters mark each change of speaker.

These are the speakers’ own words. We have not checked their claims.

0:00 A: be calling our next speaker in person, Okwuyemi Stephen from Gaia AI, to speak to us on From ChatGPT to ChainGPT: Shipping Autonomous Agents on Ethereum. Please, a round of applause for him as he comes on stage. Thank you very much.

0:16 B: My name is Okwuyemi Stephen. Um, in the eyes and mouth of some people, Okwuyemi Bangkok. Um, for some, just Bangkok. For others, Egbo Adugo, right? Nice to meet you. Say nice to meet you too. Okay, now we, we, we do have, we do have the crowd. And today I'm going to be talking to you guys, um, from ChatGPT to ChainGPT, shipping autonomous agents on Ethereum, right? But before that, let's- I wanted to say let's get straight into the video, but you know. Not TikTok. How does this move? Cool. Um, a little about me. Um, obviously, my name is Steven, Bangkok, whatever. I'm Global Ecosystems Lead at Gaia. Um, Gaia is a decentralized artificial intelligence network infrastructure that enables you to ship your own code, to ship your own AI agents, um, to spin nodes, and to be able to inference your GPUs at any time and anywhere in the world. Before that, I was Dev Innovation Lead or Developer Innovation Lead at Fuel Labs. Previously, I was TCM at ConsenSys as well, worked on projects with MetaMask and Linear. Sorry, can I get water? My voice is a little hoarse. And yeah, I'm also CTO for Danezo Trade Africa. Um, it's our startup here in Nigeria. We're a loan and remittance platform, and we provide loan and remittance services to small-scale enterprises and small businesses. I'm going to need that water, please. All right. Um, yeah, at the end of the day, I'm a friendly neighborhood guy. If you see me anywhere, feel free to say hello. Feel free to walk up to me. Yeah, that's that about that. Okay. Um, so why decentralized artificial intelligence? Because we can't just go from or, um, ChatGPT to ChainGPT without understanding whatever it is that we're doing, right? Um, I'll say it in a few words, right? Chatbots talk, right? And agents act. And what I mean by acting in this case is it's not just reasoning, right? But holding a wallet and transacting on-chain. If we're talking about autonomous AI agents, um, or shipping Ethereum agents, right? I'll show you the minimal architecture, or the aim of this is to show you the minimal architecture that makes this real and the exact steps that you can follow after this session to be able to build your own. We'll have a little starter code which you can scan and then build off on. I built like a template for you guys as well. So just a precise reproducible playbook. So Why decentralized artificial intelligence? First of all, builders need control, right? You don't want to build stuff and then you have no control over what you're building. Everybody complains these days about Google. Everybody complains these days even about OpenAI, you know, as a platform. You know, I think there was something in the news the other time of, oh, all the secrets you tell ChatGPT, the please and the thank you. that it could be used, you know, in a legal case. True or false? True or false? Am I talking to a crowd here? Guys, true or false? Cool. So there was all of that talk and builders need control in essence, right? They need clarity and they need the ability to be able to act on-chain. So first, ownership and portability is one of the reasons why you need decentralized AI. You should be able to run your inference You know, where it makes sense, either on your own personal node or even if it's a rented one, and you should be able to move without rewriting your app, right? Secondly, trust and privacy. We've mentioned the legal case with all the, the legal precedents Sam was talking about. Thank you very much. Sorry, just a second. All right, cool. Yeah, it's better now. Let's get back to it. So like I was saying, right, trust and privacy. You need to be able to audit the path from prompt to action and to keep sensitive data as a builder. without or with, actually with the explicit allow list that you have. That's the second reason why you need decentralized AI. Now, third, on-chain actionability. That's just big grammar for you should be able to do things on-chain, right? You should be able to give your agents, whatever AI agents that you're creating, a bounded wallet and policies so that it can sign and it can call contracts safely. Control Transparency, and action. If you're looking for 3 words of why you need decentralized, um, artificial intelligence: control, transparency, and action. Please, what did I say? Are we hungry? Please, now you should have eaten before you came out. How you come to party and you're not going to eat? So control, transparency, and action. What did I say, please? That is what decentralized artificial intelligence unlocks. Now let's see the minimal architecture that makes this practical. So we're going to slow it down. I don't know if you can see this. I think it's visible enough. We're going to slow it down now and define what runs where, right? How actions are gated. And we'll give like a plain English version because a lot of the time people talk a lot about, you know, oh, the jargon is too much. Oh, I don't understand it. Oh, it's not clear what we aim to do here. And what I've taken, you know, the personal mission, my personal mission is to simplify everything as much as possible for you guys. Right. So let's start with the first thing there. You see agent runtime, right? Agent runtime is simply your app or your service. So this is like the minimal architecture of what, you know, your Ethereum agent should look like. You understand? Now your agent runtime is your app or your service. Now what does it do? It plans a step and chooses a tool. Think, oh, if you want to say something like, um, the contract or whatever, or the agent should read the price, you understand? Or, oh, if the delta is more than 1%, then update. All those your if and else statements, all those your conditionals and everything, that's where your agent runtime and your app or your service lives. Right. What does it do at the end of the day? It outputs a structured intent. So if I'm explaining to you like you're 5, what your agent runtime simply means, this is just the planner that is saying, oh, I think that we should do X. Here's why. Now, how many of you have gone through like your normal ChatGPT, especially with GPT-5, for instance? You see those thinking stages, right? Where it's telling you it's thinking. And if you click it, You can see those different stages that is taken. That is what your agent runtime is. Is it understandable? Is it understandable? Please make my work easier. Show you understand. Please, is it understandable? Thank you very much. Now let's now go to the second path, which is where I'm going to be shilling, right? Which is like your inferencing layer, your Gaia nodes. You understand? This is the inference-only node. And what does it do? You can see there, right? It converts prompts, these prompts that you have put there, to structured outputs. It does not hold your keys. It does not touch your chain. You can self-host or you can rent. So I was with Hyperbolic at some time too. Hyperbolic is also a decentralized artificial intelligence network. You know, we inference GPUs. People could rent GPUs as against paying for this really, really, you know, $20. Not everybody has $20. to float a project, or if you're like a big company that wants to scale. But people could rent GPUs, right? So that is where your Gaia node comes in, or your inference layer comes in. It doesn't hold the keys, right? It doesn't touch your chain. You can self-host it, or you can rent it. The endpoint is also portable. The endpoint is portable. Now, if I was to explain this to you like you're 5, right? What your Gaia node or your inference layer simply is, It is the calculator or the translator that helps you, the planner, think. But it cannot spend your money. It cannot do anything outside of what it is that you want it to do. Understandable? Capisce? Cool. Let's go to the 3rd part now, right? Which is your signer or your policy layer. So we've listed 2 parts already. Your agent runtime, which I said is the app or the service. Your inference layer, which you can plug in something like GAIA too, right? I'm going to just say plug in GAIA because I mean, that's what pays the bills, right? And then the third one is the signer or the policy layer. Now this is what we call the safety gates. You understand? Separate process or microservice, right? It holds your private key. You can enforce whatever policy that you need before signing. You can also allow a list of API methods. You can allow spend caps. If you say, oh, um, um, when the price hits so-so and so, ask my agent, help me invest $20, or help me invest $10, or help me invest $5,000. Let's assume you are building like a trading agent or something. So this is where all of those instructions are going to live. You understand? All the safety gates that you need, even your rate limits as well, it lives on your signer or policy layer, you understand? If the intent violates the policy that you have set, what is going to happen? It's going to reject, you know, that task and ask that, oh, let a human come and review this particular action. Is that clear? So if I'm explaining to you like, like, like, like you're 5, this model would not sign anything unless you ask it to, or unless the signer itself does that, you understand? This is the adult with the wallet, if I'm explaining to you like you're 5. So we've talked about the planner saying, oh, I think we should do this and this, right? We've also talked about the calculator or translator that will help the planner think. Now this signer or policy layer, it is the adult with the actual wallet, money spending. This is what you have here. Do you get me? Now the planner can ask, but it's the adults that will now say, oh, okay, yeah, this applies, let us spend so-and-so, or let us sign so-and-so transaction. Is it clear? Is it clear? Now the 4th thing you have is your RPC provider. Um, if you've- I mean, if you're an alumni of Web3 Bridge or you work with Web3 or you are a builder, you would know what RPC means, right? Who is a builder here? Who's a builder here? Who's a builder here? So for, for ₦10,000, right, let's do quick giveaway. I like my talks to be interactive. What does RPC mean? Who knows? Oh, now all of you are raising up your hands, are we? But no, let's, let's do it. Who knows what RPC means? Yeah, big man. Sorry, can you guys hear him? What did he say? Right or wrong? Right or wrong? RPC means right or wrong. You just won yourself ₦10,000. Please see me after the talk. Yeah, this is why you clap, by the way. Even Tinubu does not give you money for free now. All right, let's get back to it, right? So for your, your, for the number 4 part, you have your RPC provider, right? Could be standard HTTPS. So when you send that signed transaction, you know, to maybe Sepolia, right, you can configure your primary and your fallback RPCs. Nothing should really be custom, you know, on this layer. So again, putting it like your 5, right? This is the road or the post office, you understand, that carries out- is the road or the post office that carries out your already signed envelope. So let's assume you're sending a letter now. You've written your letter, you've said I love you to that baby. For those that went to boarding school in my time, Right? You've said I love you to that babe, right? And you said, oh, let's help you deliver the letter. Obviously there was no social media then. I'm not that old, please, right? But this is the one that now carries it. All of the things that you need, and now you are putting your transaction on the blockchain, whether it's signing, whether it's making investments, whether it's sending tokens, right? Now after that, the, the 5th layer is now the contract or the minimal rights method. Now you can call things like maybe you write a method like your update value method, right? This is going to emit an event, and then when you emit that event, you can verify by reading storage or listening for that event. I mean, everybody who has run one or two integrations before knows what it means to call an endpoint. If you're like a front-end guy, I think even backend guys, backend guys know it, right? So this particular contract layer is like the vending machine, you understand? It's the right signed coin and the button will give a predictable result because you've written the rules and you've told it what to do. So when you call the endpoint, you expect something, either success 200 or what? Error 404, abi? Or a 500 or whatever, whatever. 404. I forget those codes now, but you know what you expect at the end of the day. It's either successful or it rejects and tells you the reason why with your error message. So if you're going to put this flow in 6 bits, right? You have your user triggers and then from there it goes to your agent plans. From there it goes, Gaia would return the intent via the inference layer, right? Your policy would validate, right? Your signer will build. or it will sign, or it will send whatever you needed to send, right? And from there, you can now log your transaction hash, and then you can confirm the block, you know, on your explorer. That's how that is supposed to work. So from idea to action, all you are going to need to do in these 5 stages, all of, all of what this encompasses, right? Number 1 is to think. That is what the runtime would do, right? And then you decide. That is what the node would do, the inference layer is going to do. And then you check your rules. That is what your signer or policy layer is going to do, check the rules. And then you pay or you sign or you do whatever it is that you need to do, and then your machine would update. And then you keep the receipts and you can check it on whatever, um, explorer that you are, that you are using, right? So, um, there's something that you need to also know, which is observability. You have to- the observability will happen on the explorer side of things. You have to keep that paper trail, which is what essentially the blockchain helps you to do. So you make sure that you keep that paper trail and maybe log like what we call the correlation ID, right? You log that ID, you log probably the transaction hash, you log the policy decision so that should you need to check, you know, um, later for discrepancies, you can be able to do that without any problems. Um, I think I've bored you guys a little bit. So let's go to the next slide. So this is the agent lifecycle. This is how it works, right? So from trigger to plan to think to check to sign and send to verify, right? So trigger is your user action, your cron or your webhook. The plan, the agent to propose the intent. What are we doing? Why are we doing what we're doing, right? And then you think your Gaia or your inference layer, it could be I'm not going to shill others, so it has to be Gaia. So your Gaia node is going to return, um, that structured output, and then you check, you know, with your policies and your safety measures that you have put in place, you understand? Your allow list, your spend caps, your rate limits, you sign and send, wallet signs, RPC broadcast, and then you verify. You can log your transaction hash, and then you can check whatever it is that you, that you want to check. Please, is this clear? Do I have the crowd or have I lost the crowd? Is this clear? Yes. Thank you very much. So now, so a quick path to shipping. Yeah, because we do not have a lot of time, I made a starter repo and you can use this QR code if you want to experiment on this actual project, right? You open the repo, you scan the repo, you set your environment keys, right? And then you can run locally. I also put scripts Right? I also put some demo scripts and some safety scripts for you so that you don't end up going the wrong way. So obviously you open the repo and that just means that you're picking the toolbox, right? Oh, sorry, my bad. So obviously open the repo, right? Sorry about that. You open the repo Um, and then you set your 3 environment keys so that the script would know that you're on the test network, right? It's a throwaway wallet, you know, and the contract address, right? You label the jars so that nothing gets mixed up. And then now you now install. You install by running locally, um, obviously npm install. If you're a builder, you should know this by now, right? npm install. And then you, you also install the demo agent scripts that I put there for you. This would give give you that environment for you to be able to play around, right? Um, for the sake of time, we're not going to be able to go into like the code code, but that was why I took the time to explain how these things work so that when you are on your local machine, when you're looking at the repo, and then it also has a comprehensive README that will take you step by step through all of the things that you need to do as well, right? Um, you can leave a GitHub star if you are, if you are impressed with it. And also You can also contact me on Twitter or whatever if you have problems or office hours. I'm down, totally down for office hours at any time of the day. I think my voice is going again. So yeah, you load this up, shows you what you need to do, your Chainstarter. So let me explain some of the things that are there real quick, then I close, right? So your Chainstarter agent, what you see there is your Chainstarter agent, which is the folder, right? This is just the blockchain agent starter kit that I have created. It demonstrates how AI agents can safely interact with Ethereum smart contracts, right, through a policy layer. That's what the, that's what the, um, the thing is. Um, also, what does it do? It takes you from AI agents to policy gates to Ethereum transaction, right? It will show you the complete flow from AI decision-making to on-chain execution. So when you get into that particular repo, I have listed all of those things. Right? I don't- I think I should have pulled it up anyways, my bad. But if you get into that repo, you would see all of it. Your Chain Starter Kit is there. You check what it does for you and you'd see the complete flow from like AI decision-making to like your on-chain execution. Now the key components of what you are going to find there on in that particular folder, the key contents you are going to find there is your agent oracle, your agent oracle contract. This is a simple oracle that would store a single value for you. It has an update value method, right? Or a function, you can call it a function as well, that AI agents can call. And it will emit events for transparency as well because you're working with the blockchain, right? Another key component that is there is your AI integration, which is the demoagents.js that you see there. The second one that you have to- the script that you have to install. This is going to connect your AI endpoints like Gaia for decision-making. It can also fall back to mock data if you don't have any AI service configured or integrated. That's what the demo-agent.js script is for. It will also demonstrate how AI agents can propose blockchain actions for you, right? Policy layer as well, which is the third one. It contains your function allow list that is going to only permit specific contract functions. Right? It also gives you like your gas price caps in case you are, you're trying to, um, um, spend, spend gas on stuff. And then you also have like your blockchain execution layer, which is going to sign and send transactions to Sepolia testnet. Sepolia money is not real money, please. So you need to keep that in mind, right? Um, it uses ethers.js as well, uh, for modern Ethereum interaction, and it also provides the transaction verification and status reporting if you need to, um, log incident reports and all of that. So, um, you might ask yourself like, why does all of this matter, right? First things first is safety, right? Policy layer would prevent your AI from making dangerous transactions, you understand? Um, scalability as well, right? If there are no patterns, you cannot have real DeFi protocol or smart contract, um, doing things autonomously for you. So you have to have that policy layer. If you, if you are familiar with, um, Liquid- I don't know, who knows Njoku here? I know. If you're familiar with Njoku's products, Liquid, right, it has that, that policy layer if you go into like the nitty-gritty, or if you have spoken to him about the products. So this is important because you need those policies to be able to put safety gates so that your AI does not, um, run riot and do, you know, what it is not supposed to do for you, or then start hallucinating and stuff like that. Also, transparency is another reason why this matters, right? All AI decisions that you are going to make with this particular project is obviously going to be stored on-chain, so it is transparent for all to see, and it maintains that blockchain ethos- decentralization and transparency. All right, um, dynamic parameters adjustments too for DeFi protocols. You should be able to change things as things go. You should not just have a point A to point B AI agent whereby you cannot stop in the middle and say, oh, let's do this, or let's do this, or let's add this. You understand? Your AI rails should, as much as it can run autonomously, it should also be able to say, oh, I hand over the reins to a human. You should also be able to take control, you know, at any point in that particular user journey. Right? Understood or not? Yes. Cool. Um, so this is not just a demo, it's something that can help you. Um, if you use this, um, starter agent kit, it can help you go to production-ready patterns for building your own artificial intelligence agents that can safely interact with blockchain protocols. So from this, you can spin up an agent that can interact with Solana, you can spin up an agent that can interact with Cosmos, You can spin up an agent that can interact with- I mean, there's like a billion and one protocols these days, right? So, um, you could use this to, I mean, get started and get building. All right, um, so this, this would position you also. It's going to give you that nice journey. It's going to give you that nice experience of getting your hands in the weeds with artificial intelligence, right? So you should use this. The README is going to explain it to you properly. Anyways, um, so at the end of the day, right, um, this is the ethos of decentralized artificial intelligence. I cannot finish my talk without letting you know that you should own your intelligence, right? It should start today. You should start today. Own your intelligence. People shouldn't be the ones in control of whatever you do with your data. It is very, very important that you do so, right? Um, and in the words I mean, thank you. You can follow me here, right? Let's build autonomous on-chain agents. Uh, my handle on Twitter is devvgbg, but if you just run a quick search, Okoyemi Bangkok, um, is the name. Don't ask me why Bangkok anyways. And, um, in the words- I'll leave you with the words of a great philosopher. Um, so you know that we have a lot of philosophers, right? And, um, to encourage people, it's also- it's always nice to leave motivational quotes. True or false? True or false? So in the words of the great philosopher, right? Um, what's this? What happened? Oh my days, I don't see it. But let me, let me leave you with the words of this great philosopher, right? Um, his name is Crown Usama. How many of you guys know Crown Usama? He's also popularly known as Charlie Poppy. So in the words of the great philosopher Crown Usama, AKA Charlie Poppy. All these my Web3

25:23 A: boys.

25:23 B: Start today, keep building. You know, pass like that. Thank you very much.

More from this hub

Something wrong, or a video you want off this page? Write to wethem.xyz@gmail.com and it is fixed or taken down within 48 hours.