The MOR-DIEM Synergy | Hermes Overtakes OpenClaw

Alright everybody, it is another week of the Morpheus Town Hall. This week, a handful of things to talk about. The kind of headlining story out of the Morpheus ecosystem though is from the brain of Ryan Condren, we are gifted mordium.com. Ryan is actually, I believe he's in flight right now, so we were unable to get him to jump on this week, but we'll definitely have him on in a subsequent week to hear from the horse's mouth, if you will, some of the things that he's working on with this. But I definitely wanted to touch on it because it's very timely. Over the last 10 days or so, there has been a massive run-up in terms of more token price, DVV token price, and more focus shifting into DAI. And what's awesome about this is, as the meta is shifting to DAI, this is, at least from my perspective, the first time that DAI is getting a lot of attention from the crypto markets, but not through the scope of meme agents. In 2024, or I guess it was spring 2025, there was that moment of decentralized AI mania, quote unquote, in the markets. But it was really, I mean, I'm always one to kind of poke some fun. But at the time, I won't pick on any specific protocols or anything like that. But at the time, most of what was being called DAI was really just, you know, telegram bots with tokens attached to them. Now, we're at this moment where proper decentralized AI tools, things like Morpheus, things like Venice, things like Dolphin, some of these others are getting recognition, both on the timeline, and then also, obviously, through investors and token price. And through this, Ryan shipped more DM.com. That's M-O-R-D-I-E-M.com, which is a new way for people who are DM holders from Venice's project to actually, if they have DM and it's unused inference, meaning that they hold the asset, but they're not actually consuming the $1 a day of inference per DM, they can stake it to more DM.com, which is ultimately offering it up as compute to the Morpheus network ecosystem, and earn more proceeds for doing so. So they're kind of pseudo acting as a compute provider in doing that, which increases the amount of total available inference on Morpheus. The other two things that you can do with this website are buy inference. And by buy, I mean stake for inference. So if you want to stake your existing Morpheus tokens, similar to the API gateway, you have the ability to do that, stake your Morpheus inference as a user, and then also the ability to stake to the Morpheus builder pool, which is the subnet, and you'll earn 20% APY more on more for doing so. But the real flagship thing that this is doing that's most different from everything else is giving you a way to put your unused DM to work, providing more compute to the Morpheus network ecosystem, but also providing an economic opportunity for you as the DM holder. Kyle, Tomás, do you guys have any notes on this? I mean, this is, of course, pretty big. It's another connection point between Venice and the Morpheus ecosystem. And I think there will be a lot of participation in this, probably. I mean, there's already 400, it looks like 471 DM staked to this, and it's only been live for a couple of days. Yeah, so I can speak to it a little bit. Definitely. I think when Ryan is on here, it would be, he can explain it in much more detail. But yeah, overall, it's really an amazing opportunity, right? It allows people to, how do I frame this, utilize some of that access capacity that they have, monetize it, while also creating much broader access within the Morpheus network. So it's kind of a win-win everywhere, right? It's a win for DM holders, right, to get commentated. It's a win for Morpheus token holders that the system's going to be more broadly utilized and have much larger scale. It's a win for consumers within the Morpheus marketplace that now have access to, again, deeper scale and larger amounts of capacity. And then it's also a win for Venice, right, where they're getting more utilization of their system. So it's really a great application of what the Morpheus infrastructure is kind of built around, right? Let people provide into the marketplace in whatever way that they choose to and work as more of this decentralized, permissionless consolidator of inference and help people monetize some of that, excuse me, excess capacity, right? It's just one great avenue, right? We see people with AI credits, right? We see other larger opportunities of, you know, when we work up the scale, it's like individuals with capacity, people with API excess credits or capacity, people with data centers who are running, who aren't getting full utilization. So it's kind of, we're checking, we're trying to check each box within that. And this Mordium product fits perfectly kind of right in the middle where it's way better and way stronger than a simple consumer scale running through Venice. And then we hope over time we get to the larger scale data center level access as well, providing. So it's really great. I think it shows, you know, the strength of the system that's built. And we encourage people to build similar things like this on top of it for other platforms as well. And, you know, hopefully they have a good opportunity to monetize through their products, through the Builders Protocol, which Mordium is using. And I think it's a great opportunity overall. Yeah. So this is a really good example of how Morpheus as a project, like this really highlights how Morpheus as a project is an aggregator of decentralized AI tooling, or like in this case, decentralized AI inference. And I've used this example before on other spaces, probably even this specific space of how if you compare what's happening in DAI right now to what's happened in DeFi in the past, you have in DeFi, you have decentralized exchanges that ultimately have their own liquidity pools. So for example, you have Uniswap, you have Compound, you have some of these other places where on Uniswap, Uniswap has its own liquidity pool of tokens that people are providing token pairs into and they're earning yield for doing so. But then you have this next layer of something like OneInch and CowSwap and other aggregators where those aggregators are allowing you to tap into those liquidity pools across different exchanges. And so what I mean by that is Morpheus is Morpheus, and Morpheus is a really good example of this, is providing that same type of additional layer to the inference market as something like a OneInch would be providing to the capital markets. And so what I mean by that is now that people can use their DM and ultimately stake it to provide compute to the Morpheus ecosystem, that means that every Morpheus staked from a user's perspective is effectively getting you access to DM. As other people come online, it'll be the same thing. So I said this on Monday that all DM is not Morpheus, but all Morpheus is DM from this perspective. And I'm not saying they're one-to-one in terms of value, but what I'm saying is staking more as a user now inherently gets you access to DM, or at least the same compute that you would otherwise have if you were staking DM. And as more and more inference sources come online and things like this become more robust, Morpheus can become a central place where you can access all of them permissionlessly without needing to go to any one individual inference provider. And so this is kind of just like the next step in that evolution, but it's an important one because it highlights that that's like the direction that things can and will ultimately head in. And hopefully eventually Morpheus will be like the singular or one of the singular places to stop for all decentralized inference because you'll just be able to access all of it in one place as opposed to having to go to, again, like any one individual provider. But yeah, it's really cool to see. We will definitely have Ryan on stage with us at some point soon to talk about it in depth. But for now, if you are a DM holder or a Morpheus token holder and you want to engage with MorpheusDM.com, definitely go check it out, especially if you're a DM holder and you're looking for a way to have that DM token be productive for you beyond providing you the dollar a day of inference that, you know, as an investor, you may or may not be actually chewing through on any given day. Of course, if you're a developer, that's probably a little bit different. But yeah, I wanted to definitely kick off with that this week. The second thing that I wanted to talk about this week, and it is changing gears here a little bit more, focusing now on the agentic side of things, is that over the last four days, Hermes Agent has now become the number one most used global open source agent platform, overtaking OpenClaw and Clawed code, which is pretty amazing. So the figures that I'm seeing in terms of token throughput, let me just make sure I have this correctly. It looks like Hermes has done, is it 224 billion tokens? Which is wild and beyond, you know, what OpenClaw has done at about 186. Thomas, I know that you are a huge proponent of Hermes and have made the switch from OpenClaw. Why is that? Are you surprised, I guess, to see them jump OpenClaw? And why did you make the jump yourself? No, I'm not really surprised because, you know, when you look at the evolution of the tools, every time, you know, there's a new tool, it builds upon, like it's built on the shoulders of the ones before, and improve some of the key limitations that they had, or add some capabilities, or things like that, right? And I think it's particularly at the stage we're at of agentic AI, it's not a big surprise to see Hermes surpassing the consumption of OpenClaw. And, you know, it's likely going to happen, like there's likely going to be another framework coming up in, you know, a quarter, two quarters, three quarters, that's going to surpass what Hermes is doing today. So it's just, I think it's just the nature of those tools evolving, the profile of the users adopting those tools changing as well. And, you know, for me, the switch from OpenClaw to Hermes was driven predominantly by memory, and some of the challenges I was having with memory using OpenClaw. But I can see, like some people I've spoken to have made the switch because OpenClaw was still required a certain, like a high degree of technical understanding to set up and maintain on an ongoing basis. Hermes has managed to lower that barrier. So, yeah, I mean, I started using ClaudeBot, MoldBot, OpenClaw, and over the last sort of month or so, transitioned over to Hermes. So it went, like I went from 100% OpenClaw, 0% Hermes to 90% OpenClaw, 10% Hermes, and then there was a switch. And what triggered that switch was interaction that I had with both platforms. OpenClaw was a bit of a frustrating one. You know, like I had one of those agents that builds company profile, like when I do research on particular companies, and I want that output to be very specific, like I have this form basically that I want the agent to fill. And a few times I had OpenClaw come back with the output, and the output was completely different from the template. And so the last time I asked OpenClaw, like why are you not using the template? How can we work better together so you always use the template? And the answer was, it's not a memory problem because it is in my memory MD that I have to use this template. I just didn't consult the memory. So that was obviously quite disappointing. I have what might be a dumb question, Thomas, but, and this is just, I mean, I'm a retail user myself. Is, what about the framework of the actual agent is different in that regard? Like, couldn't OpenClaw just have a specific memory skill set up? It does. It has one. No, no, I know, but I guess what I'm trying to understand is, what about the memory skills that exist within OpenClaw, like can't match what Hermes is doing? Like, are there specific skills on Hermes that I just can't access on OpenClaw? So Hermes has this self-improving loop that is quite powerful and it's really built into the system. I try to do something like that with OpenClaw. So I had a, like, look at all the logs, look at all the errors, like every day at two in the morning, three in the morning, look at all the logs, look at all the errors, identify issues that you see in those logs and then propose a way to fix them. So, you know, there was already sort of this self-improvement loop that was, like, I had already added that self-improvement loop to OpenClaw and every morning I'd get the message saying, hey, these are the issues that I found. This is how I think we can resolve it. What do you think? If you agree, I'll implement it. So I'd review this, agree, and then it would get implemented. With Hermes, I don't even need to do that. It happens completely behind the scenes. And, you know, there's a lot of discussion around, like, what are the implications? What's the impact on token consumption? Hermes has a high degree of token consumption, that OpenClaw, you know, things like that. The way I look at this is if I can get a one-shot answer and that one-shot answer consumes more token than one answer from OpenClaw, that I'm going to have to go back and ask for more, then it's worth it. Because at the end of the day, to get the output that I wanted, I would probably have used the same or even more tokens than Hermes. And what it cuts is the frustration and my time interacting with the system to get the output that I want. Even the memory management, right? Like, I spent quite a bit of time digging into memory management for OpenClaw and implementing different strategies from, like, using a vector database, implementing QMD, looking at main panelists, different approaches to memory. And I could never really get it right. With Hermes, the experience that I had was the complete opposite, where I was doing some research on a particular topic. And then maybe a week later, I went back to that topic and wanted to drill a little bit more on it. And when I went to Hermes and say, so, I want to do research on this topic and have some specific questions, you know, these are the questions. Hermes immediately responded with, yeah, we looked at that last week. Let me look at where we left it last week and then we can go from there. So that right there told me that the way memory is managed across both systems is fundamentally different. And I was getting a much, much better output from Hermes than I was from OpenClaw. Got it. Okay. I have another kind of dumb question, potentially. If I'm currently a user of OpenClaw and I want to switch over to Hermes or give it a try, what are the things that I need to do to capture as much of the existing context and tooling as I can to package it up and bring it over? So obviously, I could go in and just download Hermes onto my machine. But is it just the sole MD file? Is it more than that, that I would need to transfer over? So as part of the install wizard, if you will, of Hermes, it asks you for a pointer to your OpenClaw install. And it goes and gets all the files that it needs. Oh, so it'll just do it itself? Yeah, it just does it itself. Oh, that's interesting. Can I have it wipe itself too? Like, could I literally download the Hermes wizard, say, hey, go grab everything you need and then wipe OpenClaw? I don't know. I didn't try that. And the permissions that I have on Hermes would not allow it to do that. Because giving an agentic framework the ability to wipe the machine that it's running on isn't really a best practice. Right? Because if it can't delete OpenClaw, what else can it delete? Yeah. Yeah. And removing it, removing OpenClaw from your system, you go to like, you know, tilde slash, which is your home directory. And then in there, there's a .openclaw folder. So you just delete the .openclaw folder and that's it. That makes sense. Okay. Yeah. And I'm not necessarily saying people should do this. It was more so I was just curious if you did want to make the switch. I mean, I know for myself, even just getting my OpenClaw set up the way that I wanted it to on a hardened machine and all of those things was like, it was like a challenge for me. I had to learn, you know, more about code than I ever have in the past. Somebody that does not have a software background. And so any point of friction to change it up is like, it's kind of like, oh, do I really want to do it? Even though it might be the better tool. And ideally, you know, if there is some type of like one shot solution, that's always the thing that I'll tend towards just because, you know, not having the technical background of many others. It would just take longer, so I'm trying to say. There is a migrate tool, by the way. Yeah, this is a migrate tool. From Hermes. Okay, cool. I'll have to give that a try and walk through it and see if I can't figure it out. Because, yeah, now I'm tempted to change. I have had a couple interesting quirks with my OpenClaw. Like there was a point in time where it was pinging the Morpheus API gateway continually, but not. It kept claiming that it wasn't, but I could see my daily credits going down. And then I had to do a bunch of digging to figure out why it was only for it to be like, oh, yeah, actually, I have been doing that. Like, okay, please stop. That's interesting. That's interesting you say that because last week, so I wiped OpenClaw completely from my machine this last weekend. But I had basically stopped using it, but it was still running on sort of a segregated machine. But last week when I was away, I got alerts that I was basically running out of credit. So the amount of inference that I was getting access to through Morpheus was basically running low, which made no sense to me because, you know, I was traveling, I wasn't using Hermes at all. So why was it running out? And looking at the logs, it was all OpenClaw consuming all that inference, even though I was not interacting with it at all. Yeah, that's what this was like. It was giving input without requesting, like without output and just pinging it for some reason. But it was chewing through inference by doing that. Yeah, so I had exactly that. So I ended up having to remote into the Mac mini that I have to run Hermes and OpenClaw and shut down the gateway so I would not have access to anything. And then all of a sudden my consumption went back to what I expected. And that was the nail in the coffin there for OpenClaw. I didn't mind having it running in the background. And, you know, at times I would sort of look at what the output was and what the performance was and are both for the same type of request. But, no, like I was not going to let OpenClaw just chew through all the inference credit that I have just because it feels like it. I actually needed to do some real work. So you're not going to steal it from Hermes. Yeah, no, that's funny. That's exactly that same issue. I think I was able to fix it, but I'm glad to hear that you were not having that issue with Hermes. It's, yeah, I really, I guess the only thing that surprises me about Hermes popping up and nothing should surprise me really in terms of things moving quickly. And also people's like, I don't know if brand loyalty is the right word, but kind of like brand loyalty sticking around with any one place. But because OpenClaw was so prolific and basically became, at least initially, like the retail standard for running your own agent, I really thought that was maybe going to be like the Kleenex moment for this, for like personal agents. Like that was going to be everything gets referred to as an OpenClaw or ClaudeBot or, you know, they went through a couple of branding changes, but it happened much more quickly than I thought it was going to that someone else stepped in. And now it makes me feel like there won't be a time where there's going to be like one exact agent framework. And it'll be just a ubiquitous thing that everyone carries their context and souls and things with them from platform to platform to platform until they ultimately find the one that they want to stick with for a while. Yeah, I think it's going to take a while before we get to this. And if you look at, you know, the differences between both platforms, it also speaks to a different user. Like on OpenClaw, you can curate the instructions, you can curate the skills.md. And that's how you improve them. You have to do it yourself, which is great, right? It's going to speak to people that are really ready to put their hands into the heart of the system and tinker with it to see measurable improvements. With Hermes, the agent writes its own skills. And as you ask sort of the same questions, so I'll take the example of the company profiles, right? So the first time I asked for a company profile, indicated the format that I wanted, etc. Hermes created a skill. And every time I asked for a company profile, it reuses that skill. But if I ask for a clarification on something, it goes back and updates the skills. And next time I asked for a company profile, I don't run into the same issue I did the last time I used it. So that's part of this self-improving loop that you have. And so if you're a less technical user, if you're intimidated by opening a skill.md and making changes to the skill.md, which is something you would have to do with OpenClaw, it is not something that you have to do with Hermes. Hermes will do that itself. Without you even asking. My favorite type of work. No, that is awesome though. Yeah. Kyle, do you have anything on this changeup in frameworks? Or popularity, I guess otherwise, between these two? Not necessarily. I think that each of the frameworks are good in different ways. I think the memory management, like Thomas has been talking about in Hermes, is much better. I think that there are some better aspects of OpenClaw from the way that it handles the heartbeat and the way that it handles the reasoning. But overall, I think it's... I don't think that we're in the final place right now of what a good agent harness is. I think that we're going to keep seeing new ones of these. We're going to keep seeing forks of these that continue to improve on it. So I'm just excited that everyone's using them, honestly. And we're kind of collecting this global knowledge on them for what's next. Yeah, I was going to say the best part about this is that on this ranking sheet, I'm looking at Claude Code is fourth. Yeah, I mean, Claude Code is great as well, right? This is all based on some of the infrastructure that Claude Code created with... Oh, I just mean, though, that the open source options are more popular. That's what I meant. Oh, yeah. No, I wasn't talking necessarily about Claude's open source, but just more generally on the structure of the harness, right? Like Claude Code, I guess you could kind of call Claude Code open source now after the leak. But regardless, I think Anthropic kind of figured out the structure of the skills files. And then OpenClaw kind of iterated on that and created the full platform. And then Hermes iterated on that. And now we kind of know what this basic infrastructure looks like in how to handle agents and what is an agent, right? It's kind of just like a skill file and an agent, you know, a handful of files together. But I love all of it, right? Every time I knew one of these forks come out that kind of optimize for a specific niche, I think it helps add towards what's next. Yeah, totally agreed. I'm changing gears here a little bit. I'm going to do some little halftime self-promo here. We put out the latest episode of the Brainpower podcast yesterday, and it was with Ahmad, who is the founder of Intelligent Internet and was also the founder of, oh my gosh, Stability AI. Holy smokes. Sorry, people. Stability AI. It was a fantastic interview. The guy is a genius. I mean, like, without a doubt, had some really, really interesting insights and takes. And if you haven't checked that out yet, I definitely recommend that you do. And also check out Intelligent Internet. It's ii.inc. They are doing some really heavy, deep research with AI. One of the recent topics that they covered in papers that they published was, and he explains this better than I'm going to right now in the podcast. But basically, they did, I believe, what he called the 1911 test, which is they took information that only would have been available from 1911, the year 1911 and earlier, and tried to see if a large language model could prove relativity just with that information. So basically simulating Einstein in a way. And spoiler alert, the answer was yes. But also, interestingly, they did what was called the single or one postulate and were able to prove it with just one calculation. Basically taking special relativity from two postulates down to one, which was very, very interesting. He explains this again so much better than I ever could or will pretend to be able to. But yeah, it really was interesting. We also cover a handful of other things ranging from the fact that he is he sets our P doom likelihood at 50%, which is kind of kind of wild. And then we also talk about like humanoid robots and some other things. He was one of the only people I've ever talked to who actually currently has a humanoid robot. I think he even has a couple of them. So we talked about that and kind of what that's likely to look like in the future, which is also why I'm so glad for things like Morpheus and decentralized AI, because if and when all of us have these types of robots in our life or doing things, whether it's literally in our home or in our workplace or even out in public, having versions that we can have sovereign intelligence tied to. So it is acting on your best interest, not the best interest of XYZ entity that allows you to use it. I think that that would be best case for humanity and certainly for all of us as individuals. The only other topic I had here, if you guys do want to touch on this really quickly, and Thomas, this is definitely one that I'll need a little bit of help with, certainly from a technical perspective, but was the TanStack, Mistral and UAI path supply chain attack that happened over the last couple of days. Can you tell us, Thomas, what is a supply chain attack and why should we care about this? Like what is going on here? Yeah. So a supply chain attack, when you look at open source software, open source software is built on, typically built on other open source software through what's referred to as dependencies. So when I launch an application, it pulls those dependencies from the creators of those dependencies that are open source developers. And so a supply chain attack is when you manage to compromise one of those dependencies to effectively compromise the software that you're trying to run. Okay. So in the case of the attack that we've seen on TanStack and Mistral and so on, this is the mini Shai Vood attack, which is not a new one. The first time it was seen was in September of 25, so September last year. It affected about 180 NPM packages. So NPM being the node package manager, the package manager for node.js. There's over a million packages in node. So you'd think that 180 isn't that much. But the strength of Shai Vood is that it is a fully replicating war. So what it does is it steals credentials from a CICD pipeline. So continuous integration, continuous development. And then once it compromises a software, it tries to compromise other software that call upon it. So the second wave was in November, and this time it affected 25,000 repositories. The third wave was the trust wallet hack. That one drained about $8 million of crypto. That was in December of last year. And so what we see now with TanStack and Mistral is sort of the latest embodiment of this worm called Shai Vood that effectively compromises software by, so it basically stages a malicious payload and then injects it into published NPM tarpauls. So basically applications. And then once it's done that, it hijacks the project's own CICD pipeline to publish the compromised version of this software. And so now everyone that uses this compromised software is at risk of being compromised through the self-replication of the worm. So I don't know if I helped clarify or if I made it blurrier or more complex than I should have. Well, it made sense to me, Thomas. It was a great expert. All right. Yeah. There are certain topics or aspects that were definitely above my head, but I trust Kyle's opinion of this. This is like a sliding scale of comprehension in terms of software knowledge. And I'm the bottom of the scale. So just because I understand. Let me TLDR. TLDR, when you run programs, they have requirements for them to run, which automatically get installed. So instead of hackers now targeting you, they're targeting the programs that you didn't realize you were installed. Got it. And they're finding their way onto your game. Got it. And in a lot of cases, it's agents who actually install these things without you realizing it. Not necessarily, honestly. Like, yeah, certainly yes. Right. But there's even some major packages. Like, OpenAI-based infrastructure in their company. Like, uses many commonly used open source packages like everyone does. And the latest one, I think, found their way into their system. Like, OpenAI sent out an alert, I think, today or yesterday about it. So it's not just agent-specific stuff. These are code packages that are used in millions and millions of pieces of software, you know, across the world. So it's the recommendation for everyone, right, is to go and look at your code base. Check your requirements files and your lock files. See what versions of software are being installed as part of your NPM. And check if any of these malicious, not malicious packages, but the packages that were impacted maliciously are installed. And then, you know, you could search online, take the required steps. Like, uninstalling the package and cleaning some stuff out and making sure you don't hit these pill switches that they have. Like, it's kind of the first step is figure out if you're impacted. And then if you are, then it's going to take a little bit more research to find the steps on what do I need to do. But people have written many, many pages on what to do if you're impacted. So I would leverage those. I really hope at some point here someone builds some type of agent or tool that can just be like the Spider-Man of security. That can basically watch it for you and then flag it and fix it. That's probably, I don't know if David's on here yet, but I'm sure David is already doing that in his Evercoach. I'm sorry, I'm forgetting the new name of it. Morpheus skill. Come on. Doing that. But it's really as simple as telling whatever coding ID you're using. Am I impacted by the security hacks that went up yesterday? Search the internet to see what security hacks I'm talking about. And it'll search. It'll be like, oh, this NPM package is big in the news. You're not using it. Okay. I'm good. That actually is something I'm doing with my agent is I have it run a daily cybersecurity check and then compare it against my own configuration. And then I sort of have a broader catch-all where there's something in Morpheus skill called Bagman, which has a bunch of best practices around how to handle keys and wallets and things like that. But there's also a skill around looking for prompt injection, which is called, I think, prompt check. And then there's also one around sort of scanning the space. So, yeah, if you're using the Morpheus skill, there's a lot of that built in. But, yeah, more suggestions. Always welcome. Awesome. I'm going to, once I have that through Morpheus skill, I'm just going to picture, David, you looking over my shoulder, making sure everything I'm doing is not malicious going forward. It's a great visual. There you go. Well, David, thanks for hopping on, by the way. Do you have any, we did cover more DM and we covered Morpheus just as like the inference aggregation layer earlier. Do you have anything you want to add to that or anything specific you want to say on that? Well, you know, it's interesting. I was just in a meeting and I was previewing that to folks and they're like, wow, that makes a lot of sense. There's all this unused, you know, inference where people already have the credits. You know, that's how Morpheus is always cheaper. That's how you guys are able to do this. And I think it sort of clicked in, in place for folks in a way that they didn't understand the arbitrage that was going on before. So big credit to Ryan for pushing that out. I think it's a real breakthrough to sort of simplify the way people understand, you know, that Morpheus can be this, this marketplace reference and just put it in very practical terms. Like if you're holding DM, go to moredm.com, you know, and put them to work, right? If you're not using all those credits, you might as well, you know, put them to work. So I think, I think that's really great. Yeah, absolutely. Totally agree. That was kind of a similar message to what we were saying before is that it highlights the way in which Morpheus as a decentralized permissionless sandbox essentially can be connected to all of these other things and then provide opportunities for people. In this case, DM holders who want their DM to be productive and ultimately want the compute to be productive, but aren't necessarily chewing through the inference themselves. One other thing, guys. So this was big. This actually broke just now while we were talking was, and it's not directly related to AI, but is indirectly related to us. It looks like the Clarity Act has passed the U.S. Senate Banking Committee and now will be moving to the full Senate. So that is a huge win for decentralized assets. And I don't know if you guys have any specific stances on this. We, of course, don't have to go too down the rabbit hole of the Clarity Act. But it looks like we're going to be getting some legitimate legal framework here in the U.S. for crypto assets. That's great. That's the one's got to look. Yeah. Well, it's a good signal that the bankers were all in up in arms at the last second trying to scuttle. Because I think the biggest fight was something that was already settled in the Genius Act, which is that it was okay for Coinbase, let's say, to pass along the yield to users. And I think the bank sort of blatantly realized, wait a minute, why would people use a bank account if I can get yield from my USDC? Right. And sort of, you know, tried to re-litigate all this in the Clarity Act, trying to prevent their own users, their own savers from, you know, having that yield that is created, you know, from stable coins. Because most of the stable coins are holding them in treasuries. They're collecting 4% or 5% annually. And most of the stable coin issuers like USDC and Coinbase are passing that along, right? Which you'd think the banks would, you know, want to see. But, you know, it really doesn't fit their model. And so, yeah, it'll be interesting to read what actually gets into the final version, you know, and I can say, you know, more definitively whether this is good, whether this is bad and, you know, how it all plays out. But, yeah, I mean, at least the way it looks from the outside, it seems like a big milestone for the industry. Yeah, totally agreed. And certainly long overdue in terms of just having this framework in place. So, that's excellent. That was all I had on the official things we must cover this week. I know Economic Junkie has jumped up on stage. What's going on, man? How are you? Hey. Yeah. Hi. I had nothing specific. You know, I just wanted to say hi. I was just listening to your podcast with Imad. I thought it was amazing. Super fascinating topics you covered there. And also, you know, when David just explained, I don't know who just explained the whole more DM thing. It just now clicked with me that we can do something that, you know, open AI, as far as I know, can't do. You know, you have people paying for inference, but can they easily share that inference amongst one another? Not that I'm aware. So, another win. Yeah. Not only can they not, but OpenAI likely wouldn't even allow them to. Because from their perspective, unused inference is like, that's basically more revenue coming to them with less overhead. Yeah. It's free money. Yeah. Yeah. It's literally free money. I mean, it's like the gym membership that no one uses, right? Yeah. It's like a gift card. You know, Walmart makes like, I don't know how much millions every year just from unused gift cards. Yeah. I think I saw one time that Starbucks with their like Starbucks dollars in their app. Was it like they were, they would be like in the top 40 banks or something in the US if they were a bank. It was something crazy like that. Like the amount of money that's just sitting in these Starbucks dollar accounts is massive. But yeah, no, that's exactly right. It allows you to actually get some productive benefit as a user for the inference that you're ultimately paying for. Now, in this case, you'd be paying for it through the ownership of DM. But you're entitled to that dollar a day. I mean, that's, that's the, you know, with Venice ultimately. I have a buddy of mine who, he just, you know, invests, he holds in Venice because I do. And, you know, I tell him, okay, I believe in this, but I'm not telling you what to do, but he does it. And he, but he doesn't use the inference. So then I told him here, you can just, you know, you can stake your DM here and yeah, he's happy to do that. So you can earn some extra yield. So he's just interested in basically some speculation, but at the same time, somebody else can benefit from that. Yeah, exactly right. And from a user perspective, this is why more the asset is so powerful because it gets you access to any available inference across the whole network. And so like DM in this case would just be one compute provider that's allowing you to access the inference that you need to run your agent. But they could be any number of providers. And so it's, yeah, it's, it's quite amazing. And it's awesome to see it start to play out in real time. Guys, we definitely should keep the conversation going here. I unfortunately do have to drop. I have a call. I absolutely have to be on in six minutes. I'm at two, but I definitely like keep the space open and let's keep it rolling. Yeah. Awesome. Thanks, Bo. Good. And good to see you on stage. Economics. I know you've been in the discord for a long time. Oh, yeah. Yeah. Your story and what brought you into Morpheus. Yeah. Yeah. And I saw you in Miami recently. I was so mad that I couldn't make it. But it was just, I wasn't paying attention. I didn't know that the consensus thing was going on. I wish I, but next time, whatever, you know, whatever's going on around here, I definitely want to show up and, you know, meet up in person to talk some more because I always love talking to, to, to you all. That's great. Yeah. No, I think consensus is in Miami the next two years in a row. So, so definitely more opportunities for that, but it's always cool to see people in the community come out to all the events, you know, and I think the big thing that's changed in the last six months is now we're all using agents. Now we're all accessing the inference from Morpheus. Like I use it every day. Right. Yeah. I don't have to sort of explain in theoretical terms anymore. It's like, here, here's my agent. I'm powering it with Morpheus. You know, it's routing to this privacy layer on Venice. It's great. It's a great point that Bo made on this recent podcast episode, or I don't know who made the point, but he was, somebody was saying that the challenge with. Cryptocurrency and decentralized money has been that there has been this, there's this super old entrenched centralized system that we're competing with, but with AI, that's not the case. The decentralized and decentralized systems are growing together. And I think that's such a huge plus for us in decentralized AI right now. Sure. Every time a new open source model gets released, you know, decentralized AI becomes more compelling, more powerful, more useful. So, yeah, it's amazing to see, you know, Google released all their Gemma models. Great. You know, a bunch of Asian groups release, you know, GLM five or 5.1 that makes it better on coding. And so sort of all the work that's happening on the AI side is just making it more and more exciting. I mean, it seems like basically the closed source AI model is completely dead. Yeah. Well, I mean, their walled gardens become a lot less compelling as the open source models start to saturate the benchmarks and can do a lot of the same things. Yeah. And so, yeah, it's going to be interesting. But I think Morpheus community has done the hard work the last three years building out all these primitives, right? The inference marketplace, all the technology. And yeah, now we get to put it to work. And do you think that, so because I've been doing, I have not gotten into agents yet. I've been doing client work, consulting work and all that stuff. I can't wait to get into that. And I ordered my Apple, I think it's a mini M2 or something like that. It's just sitting there. And I can't wait to fire that up and connect to, I think it's Everclaw that you recommend, Everclaw.xyz. And then from what I understand, it should be pretty easy to get it set up from there. That's great. Yeah. No, I'm glad that you're going to get an agent. You know, I started using Openclaw back in January, you know, and I wanted to connect it into Morpheus. And so I started rolling and open sourcing these different skills. And I've branded them now the Morpheus skill, right? So initially I called it Everclaw, but I think people thought it was an agent as opposed to a skill set that you could use with any agent, right? And since then, to their credit, Hermes has really taken off. I see that they're using now more usage for Hermes agent than there is for Openclaw, which is what I've seen among my own friends. You know, a lot of the people that started with Openclaw ended up using Hermes because it had better memory and better defaults and sort of was configured more powerfully. And so, you know, I really recommend when you set up your agent, I would go to Hermes. I would use that. And then just tell your Hermes agent to use the Morpheus skill. I've recently actually rolled a Hermes skill specifically for Morpheus and put in a pull request. Hopefully they'll accept that pull request. Regardless, I've published all the code. So yeah, you'll be able to connect to your Hermes agent with Morpheus hopefully pretty easily. So you recommend that when I get started, instead of doing that curl get.evercloud.xyz that I do something else with Hermes. Well, it works with both Openclaw and Hermes. So depending on which agent you want to use, you can import the Morpheus skill either way. And I'm going to post Hermes specific install instructions. Okay, cool, cool. Yeah, yeah, I'll look out for that then. Yeah, but for me, it's been a game changer. You know, I've been able to, you know, execute more coding the last four or five months than I have the last 20 years. I mean, it's been totally night and day, right? I know you were saying on the podcast, all your projects you've been tabling, you're able to tackle now. Yep. I had quite the backlog of ideas and concepts. And all of a sudden, I could just tell my agent what I want to build. And it'll access that model on Morpheus and code it up. You know, now it moves at the speed of which I can articulate to my agent what I want to do next. So yeah, it's pretty refreshing, right? It's like having a coworker that is online 24-7, always executes what you want. Yeah, yeah. I was wondering, would you feel, let's say, because for example, I have a client who I do consulting work for and I work in their QuickBooks system. I do stupid little tasks occasionally for them where I have to just work through line by line. And would you say you're comfortable enough with your setup to unleash it on somebody's billing system to do menial tasks? I'm kind of terrified of that because I don't know what if it makes a mistake, then that would be a huge disaster for the company. So the way I think about it is I tend to put the agent in its own isolated environment, treat it like an employee, right? Give it its own email, give it its own phone number, give it its own GitHub account. If I were going to give it access to one of those systems, I would treat it like an employee, right? You can only read these files. You can only have access to these levels of permissions, right? You don't want to give it access to the admin and it makes a bunch of mistakes. But I feel pretty comfortable at this point. Let's say you give it read access to those systems and then it's giving you all of its work products, right? And you have the edit power, you have the admin power. You can then take that information and output that it gives you and use your expertise and wisdom to execute faster, right? And that's, I think, where I'm comfortable doing is treat it like an employee, isolate it, give it permissions like you would with an employee. And then it's in a pretty good position. Like if you make a mistake, well, it's only in its workspace. It's only in the things that it read and the output. Oh, it needed to be tweaked. That's fine, right? And so I'll have it always come back to me before it pushes anything to production. I built that into... I actually open sourced this last week. If you look at my X profile, you can see the standard operating procedure that I published for developing code and deploying code. And it has all those steps and checks and audits built into the process. So that's the way I would think about it is give it the permissions you would a junior employee so that it can execute, but not make mistakes into other workspaces. Right. Okay. So that's the tricky part, I guess, because let's say I give it the access that I have to my client's QuickBooks account because it's not just read access, it's write access because there has to be a transaction to be classified and stuff like that. But again, there should be a way that you can do that locally. You may be able to dig into the permissions and see if there's some more advanced permissioning. There's MCP tooling. Yeah, go ahead, Scott. I'm sorry. There's MCP tooling that you can use with QuickBooks. So there's entry built into QuickBooks that you can tap into. Okay. Yeah. Okay. Yeah. A lot of these programs are starting to give you an agentic method of interacting. So it doesn't have to go through the GUI. It doesn't have to go through the software. For example, Google recently released all their CLI tools. So if you gave it access to Gmail, you can now do that through the CLI, the command line interface, which is more native to the agents, right? As opposed to having it take screenshots and kind of try to poke around the GUI makes a lot more sense for the agent to be using the CLI or like Scott's saying, MCP connection. Gotcha. Yeah. Yeah. I'll try to get that. I'll start small and I'll try to work my way. To that competence level. Well, and what I would suggest is, you know, more and more people are popping into the Discord and posting about what they're building. And that's where sort of we get this flywheel of people see what each other are building. Yeah. Right. And what they're connecting to Morpheus and which models they're using and where they're hitting problems, where they're being successful. You know, so I just encourage you. There's a whole builder section in Morpheus Discord to really put what you're doing. To the point that, you know, of what information you feel comfortable being public. You know, I think that kind of those best practices are really, really useful. Yeah. Yeah. Yeah. Great. Yeah. I mean, I don't want to monopolize. Oh, sorry. I didn't want to monopolize the space here. Yeah. I just wanted to say hi. Sure. Sure. No, this is great. Appreciate the questions, the suggestions. I think we're just getting to the top of the hour so we can wrap it up. But yeah, this has been a really exciting week. It's great to see all the traction and the usage increasing. You know, I think one of the suggestions by the community, Thomas, was to, you know, look at and just share with people every week, like what are the most popular models people are using on Morpheus. I looked at the analysis before this. It looks like right now the two top models are GLM 5.1, GLM 5, and then the Gem models have really picked up a lot of usage. So that's another one to highlight. So, you know, touching on those kind of, you know, metrics, I think is really interesting as people use the tech. Great. Well, why don't we go ahead and wrap it there? Appreciate everybody jumping on. Another great week. And I hope everybody has a good one. And everybody keep being awesome.