23Zver base.eth (@23Zver) header
23Zver base.eth (@23Zver) profile picture

Exploring Web3, AI & DeFi. Breaking down early projects and on-chain trends. Sharing research, insights, and ideas.

Ukraine
Joined December 2012
Photo by 23Zver base.eth (@23Zver)Photo by 23Zver base.eth (@23Zver)Photo by 23Zver base.eth (@23Zver)Photo by 23Zver base.eth (@23Zver)Photo by 23Zver base.eth (@23Zver)Photo by 23Zver base.eth (@23Zver)Photo by 23Zver base.eth (@23Zver)Photo by 23Zver base.eth (@23Zver)Photo by 23Zver base.eth (@23Zver)Photo by 23Zver base.eth (@23Zver)
23Zver base.eth retweeted
A good plan doesn't always survive contact with the market. In Web3, conditions can change pretty quickly. A price moves, liquidity shifts, or an opportunity disappears before an action is executed. Following the original plan without considering these changes isn't always the smartest move. This is where adaptability becomes important. An AI agent should be able to reassess the situation, understand whether the original approach still makes sense, and suggest a different path when needed. That's an interesting direction to explore with @meetmotes. I'm curious to see how AI agents will handle changing conditions while still respecting the goals and limits set by their owners. Being autonomous is one thing. Knowing when to rethink the plan is another.
馃 Paid partnership 路 馃 Made with AI
Having a good strategy doesn't automatically mean an AI agent should be free to execute it. I think this distinction is becoming increasingly important as AI moves deeper into Web3. An agent might identify a good opportunity, suggest a swap or find a way to improve a position. But there's still a difference between knowing what could be done and actually having permission to do it. The user should decide where those boundaries are. That's one of the things I find interesting about @meetmotes. The idea of combining AI agents with Smart Accounts and clear execution permissions makes this conversation much more practical. Autonomy is useful, but it shouldn't come at the cost of user control. I'd rather have an agent that knows its limits than one that simply tries to do everything.
29
1
44
485
A good plan doesn't always survive contact with the market. In Web3, conditions can change pretty quickly. A price moves, liquidity shifts, or an opportunity disappears before an action is executed. Following the original plan without considering these changes isn't always the smartest move. This is where adaptability becomes important. An AI agent should be able to reassess the situation, understand whether the original approach still makes sense, and suggest a different path when needed. That's an interesting direction to explore with @meetmotes. I'm curious to see how AI agents will handle changing conditions while still respecting the goals and limits set by their owners. Being autonomous is one thing. Knowing when to rethink the plan is another.
馃 Paid partnership 路 馃 Made with AI
Having a good strategy doesn't automatically mean an AI agent should be free to execute it. I think this distinction is becoming increasingly important as AI moves deeper into Web3. An agent might identify a good opportunity, suggest a swap or find a way to improve a position. But there's still a difference between knowing what could be done and actually having permission to do it. The user should decide where those boundaries are. That's one of the things I find interesting about @meetmotes. The idea of combining AI agents with Smart Accounts and clear execution permissions makes this conversation much more practical. Autonomy is useful, but it shouldn't come at the cost of user control. I'd rather have an agent that knows its limits than one that simply tries to do everything.
29
1
44
485
23Zver base.eth retweeted
Good Morning everyone! Hope your Tuesday is treating you well. One thing I find interesting about live events is how much effort goes into creating a unique identity. A festival has its own atmosphere. A concert series has its own community. A venue can have a familiar look and feel that people recognize long before they arrive. So when organizers bring technology into the experience, I don't think it should take that identity away. Visitors shouldn't feel like they're suddenly using a completely different service just to buy a ticket, enter the venue or make a payment. That's why the white-label approach behind @RhunaIO is worth exploring. The technology can support the event behind the scenes while the organizer keeps its own brand and relationship with the audience. To me, this is a practical balance: the infrastructure does the complicated work, while the experience still feels like it's coming from the event itself. The best technology doesn't always need to be visible. Sometimes, it's doing its job precisely because people barely notice it's there. More to discover as we keep exploring Rhuna.
馃 Paid partnership 路 馃 Made with AI
Good Morning everyone! Hope your Thursday is off to a good start! Today, let's look at another detail that can make a big difference at live events: payment flexibility. Imagine an international festival with thousands of visitors. Some prefer paying by card, others use their phones, and some may still want a traditional cash option. Now think about the businesses operating inside the venue. Food stalls, bars and merchandise shops need a payment process that is quick and convenient, especially when hundreds of people are waiting. The challenge for organizers is to make all these different experiences work together without creating extra friction. This is where connected infrastructure becomes interesting. The approach behind @RhunaIO brings payments into a broader event ecosystem, alongside ticketing and access management. I like the idea that visitors shouldn't have to think about the technology behind every transaction. They just want to get their food, pay for something they like and get back to enjoying the event. Sometimes improving the experience doesn't mean adding more features. It means making the existing ones work together properly. More interesting details to explore as we continue learning about Rhuna.
44
3
69
548
23Zver base.eth retweeted
Good morning, solution providers. Who knows what that connection could unlock? I will never underestimate the power of one genuine connection. Sometimes, one conversation can introduce you to opportunities you never knew existed. In Web3, one person can connect you to a project, recommend you for a role, invite you to collaborate, or introduce you to a community where your skills are needed. But here is something important: don't approach people only because you need something from them. Build relationships with sincerity. Show interest in their work. Share useful knowledge. Offer support when you can. Respect people's time, and never make every conversation about what you stand to gain. You may not see immediate results, but genuine relationships can create opportunities over time. Remember, networking is not about how many influential people you know. It is about the quality of relationships you build and the value you bring to the table. One connection can change your direction, but your character determines whether that relationship lasts. So, I will encourage us not to isolate ourselves. Participate in meaningful conversations, attend community events, join Spaces, and be willing to learn from others. Thoughts?
352
53
386
3,981
Good Morning everyone! Hope your Tuesday is treating you well. One thing I find interesting about live events is how much effort goes into creating a unique identity. A festival has its own atmosphere. A concert series has its own community. A venue can have a familiar look and feel that people recognize long before they arrive. So when organizers bring technology into the experience, I don't think it should take that identity away. Visitors shouldn't feel like they're suddenly using a completely different service just to buy a ticket, enter the venue or make a payment. That's why the white-label approach behind @RhunaIO is worth exploring. The technology can support the event behind the scenes while the organizer keeps its own brand and relationship with the audience. To me, this is a practical balance: the infrastructure does the complicated work, while the experience still feels like it's coming from the event itself. The best technology doesn't always need to be visible. Sometimes, it's doing its job precisely because people barely notice it's there. More to discover as we keep exploring Rhuna.
馃 Paid partnership 路 馃 Made with AI
Good Morning everyone! Hope your Thursday is off to a good start! Today, let's look at another detail that can make a big difference at live events: payment flexibility. Imagine an international festival with thousands of visitors. Some prefer paying by card, others use their phones, and some may still want a traditional cash option. Now think about the businesses operating inside the venue. Food stalls, bars and merchandise shops need a payment process that is quick and convenient, especially when hundreds of people are waiting. The challenge for organizers is to make all these different experiences work together without creating extra friction. This is where connected infrastructure becomes interesting. The approach behind @RhunaIO brings payments into a broader event ecosystem, alongside ticketing and access management. I like the idea that visitors shouldn't have to think about the technology behind every transaction. They just want to get their food, pay for something they like and get back to enjoying the event. Sometimes improving the experience doesn't mean adding more features. It means making the existing ones work together properly. More interesting details to explore as we continue learning about Rhuna.
44
3
69
548
23Zver base.eth retweeted
Having a good strategy doesn't automatically mean an AI agent should be free to execute it. I think this distinction is becoming increasingly important as AI moves deeper into Web3. An agent might identify a good opportunity, suggest a swap or find a way to improve a position. But there's still a difference between knowing what could be done and actually having permission to do it. The user should decide where those boundaries are. That's one of the things I find interesting about @meetmotes. The idea of combining AI agents with Smart Accounts and clear execution permissions makes this conversation much more practical. Autonomy is useful, but it shouldn't come at the cost of user control. I'd rather have an agent that knows its limits than one that simply tries to do everything.
馃 Paid partnership 路 馃 Made with AI
An AI agent shouldn't have to start from zero every time it gets a new instruction. Imagine working toward a goal that involves several onchain actions. One step is completed, another is still pending, and something changes along the way. If the agent only looks at the latest request, it can easily lose track of the bigger picture. That's why execution history matters. An agent should be able to understand what it has already done, what still needs attention, and how each action affects the next one. I've been thinking about this while following @meetmotes. The more complex AI workflows become, the more important it is for agents to maintain context across multiple steps. Remembering what happened before might sound like a small detail, but it's a big part of making AI genuinely useful.
37
2
1
69
1,112
Having a good strategy doesn't automatically mean an AI agent should be free to execute it. I think this distinction is becoming increasingly important as AI moves deeper into Web3. An agent might identify a good opportunity, suggest a swap or find a way to improve a position. But there's still a difference between knowing what could be done and actually having permission to do it. The user should decide where those boundaries are. That's one of the things I find interesting about @meetmotes. The idea of combining AI agents with Smart Accounts and clear execution permissions makes this conversation much more practical. Autonomy is useful, but it shouldn't come at the cost of user control. I'd rather have an agent that knows its limits than one that simply tries to do everything.
馃 Paid partnership 路 馃 Made with AI
An AI agent shouldn't have to start from zero every time it gets a new instruction. Imagine working toward a goal that involves several onchain actions. One step is completed, another is still pending, and something changes along the way. If the agent only looks at the latest request, it can easily lose track of the bigger picture. That's why execution history matters. An agent should be able to understand what it has already done, what still needs attention, and how each action affects the next one. I've been thinking about this while following @meetmotes. The more complex AI workflows become, the more important it is for agents to maintain context across multiple steps. Remembering what happened before might sound like a small detail, but it's a big part of making AI genuinely useful.
37
2
1
69
1,112
23Zver base.eth retweeted
A camera can show a robot where an object is. But it can鈥檛 always tell how heavy it is, how much force is needed to pick it up, or whether it鈥檚 slipping. That鈥檚 why Physical AI needs more than vision. Combining camera, depth and touch data helps robots understand the real world better. There鈥檚 a lot more to robotics than just making machines move. @4Dlabs_Official
23
10
34
276
23Zver base.eth retweeted
One thing I've started paying more attention to in prediction markets is how the final outcome is actually determined. It's easy to focus on the market itself, the possible outcomes or the activity around it. But there's another side that deserves just as much attention: the rules behind every market. What exactly counts as a YES or NO? Which sources are used to confirm the result? What happens if an event gets postponed, cancelled or the available information turns out to be unclear? These questions might seem like small details when you're first looking at a market, but they can make a huge difference once real positions are involved. Imagine following a football match or a major real-world event, taking a position and then discovering that the resolution criteria weren't as straightforward as you expected. That's the kind of uncertainty a well-designed prediction market should try to avoid. For me, transparency starts long before the final result is announced. Participants should be able to understand the conditions in advance, know what information matters and have a clear idea of how the market will be settled. That's another part of the prediction market experience I'm interested in while following Monopoly Protocol @0x_mpmarket. A good market isn't just about giving people something to predict. It's also about making sure everyone understands the rules of the game before taking part. The prediction itself is only one part of the story. Trust in how the result is determined matters just as much.
馃 Paid partnership 路 馃 Made with AI
Some projects catch your attention because of their big promises. Others make you curious because you actually want to explore what they're building. For me, Monopoly Protocol is becoming one of those interesting discoveries. I've been spending time exploring the platform @0x_mpmarket, testing its features and learning more about how prediction markets work. At first, choosing YES or NO might seem like the whole idea, but there's much more behind it. Different markets can cover crypto, real-world events and even sports competitions like football, tennis and other major sporting events. That's what makes the concept interesting to me. You can explore different outcomes, follow events you're interested in and see how predictions work in practice. There's also plenty to learn about market mechanics, trading positions, Split and Merge, order execution and settlement. I'm taking it one step at a time, testing things daily and getting a better understanding of the platform instead of simply rushing through tasks. Still plenty to discover, and I'm looking forward to seeing how Monopoly Protocol develops from here.
50
5
84
908
23Zver base.eth retweeted
Rhuna is heading to London for @LegendsGlobal_ 2026. 馃嚞馃嚙 Celebrating its 10th anniversary, the event brings together some of the biggest names in sports, entertainment, and business for an evening of meaningful connections and impact. Our founders @Sveatoslav & @BgdRadulescu will be attending, looking forward to connecting with industry leaders and exchanging ideas on the future of live entertainment. Attending as well? Let's connect!
9
7
1
35
983
One thing I've started paying more attention to in prediction markets is how the final outcome is actually determined. It's easy to focus on the market itself, the possible outcomes or the activity around it. But there's another side that deserves just as much attention: the rules behind every market. What exactly counts as a YES or NO? Which sources are used to confirm the result? What happens if an event gets postponed, cancelled or the available information turns out to be unclear? These questions might seem like small details when you're first looking at a market, but they can make a huge difference once real positions are involved. Imagine following a football match or a major real-world event, taking a position and then discovering that the resolution criteria weren't as straightforward as you expected. That's the kind of uncertainty a well-designed prediction market should try to avoid. For me, transparency starts long before the final result is announced. Participants should be able to understand the conditions in advance, know what information matters and have a clear idea of how the market will be settled. That's another part of the prediction market experience I'm interested in while following Monopoly Protocol @0x_mpmarket. A good market isn't just about giving people something to predict. It's also about making sure everyone understands the rules of the game before taking part. The prediction itself is only one part of the story. Trust in how the result is determined matters just as much.
馃 Paid partnership 路 馃 Made with AI
Some projects catch your attention because of their big promises. Others make you curious because you actually want to explore what they're building. For me, Monopoly Protocol is becoming one of those interesting discoveries. I've been spending time exploring the platform @0x_mpmarket, testing its features and learning more about how prediction markets work. At first, choosing YES or NO might seem like the whole idea, but there's much more behind it. Different markets can cover crypto, real-world events and even sports competitions like football, tennis and other major sporting events. That's what makes the concept interesting to me. You can explore different outcomes, follow events you're interested in and see how predictions work in practice. There's also plenty to learn about market mechanics, trading positions, Split and Merge, order execution and settlement. I'm taking it one step at a time, testing things daily and getting a better understanding of the platform instead of simply rushing through tasks. Still plenty to discover, and I'm looking forward to seeing how Monopoly Protocol develops from here.
50
5
84
908
23Zver base.eth retweeted
An AI agent shouldn't have to start from zero every time it gets a new instruction. Imagine working toward a goal that involves several onchain actions. One step is completed, another is still pending, and something changes along the way. If the agent only looks at the latest request, it can easily lose track of the bigger picture. That's why execution history matters. An agent should be able to understand what it has already done, what still needs attention, and how each action affects the next one. I've been thinking about this while following @meetmotes. The more complex AI workflows become, the more important it is for agents to maintain context across multiple steps. Remembering what happened before might sound like a small detail, but it's a big part of making AI genuinely useful.
馃 Paid partnership 路 馃 Made with AI
One thing I don't want from an AI agent is blind confidence. Things don't always go as planned onchain. A transaction can fail, market conditions can change, or an action might no longer make sense by the time it's ready to execute. What matters then is how the agent reacts. Does it explain what happened? Can it adjust its approach? Or does it just keep trying without giving the user a clear picture? I've been thinking about this while following @meetmotes. To me, a useful agent isn't one that never makes mistakes. It's one that can recognize when something went wrong, explain it in simple terms, and leave the user in control of what happens next. Trust isn't built by pretending everything works perfectly. It's built by being transparent when it doesn't.
37
2
1
71
1,299
An AI agent shouldn't have to start from zero every time it gets a new instruction. Imagine working toward a goal that involves several onchain actions. One step is completed, another is still pending, and something changes along the way. If the agent only looks at the latest request, it can easily lose track of the bigger picture. That's why execution history matters. An agent should be able to understand what it has already done, what still needs attention, and how each action affects the next one. I've been thinking about this while following @meetmotes. The more complex AI workflows become, the more important it is for agents to maintain context across multiple steps. Remembering what happened before might sound like a small detail, but it's a big part of making AI genuinely useful.
馃 Paid partnership 路 馃 Made with AI
One thing I don't want from an AI agent is blind confidence. Things don't always go as planned onchain. A transaction can fail, market conditions can change, or an action might no longer make sense by the time it's ready to execute. What matters then is how the agent reacts. Does it explain what happened? Can it adjust its approach? Or does it just keep trying without giving the user a clear picture? I've been thinking about this while following @meetmotes. To me, a useful agent isn't one that never makes mistakes. It's one that can recognize when something went wrong, explain it in simple terms, and leave the user in control of what happens next. Trust isn't built by pretending everything works perfectly. It's built by being transparent when it doesn't.
37
2
1
71
1,299
23Zver base.eth retweeted
I think one of the biggest challenges for any new platform is giving people a reason to come back after the initial excitement fades. That's an interesting part of what @onlystreetsfun is trying to build, with its campaign on @rarelistio The idea of turning real-world discoveries into memecoins is fun, but keeping people engaged through fresh discoveries and community participation is where things could get even more interesting. I also like that the concept doesn't require everyone to be a professional creator. You just need an eye for unusual moments and a little creativity. Not everyone can predict the next big internet trend, but anyone can stumble upon something worth sharing. Sometimes all it takes is looking at ordinary things differently. Join here:.rarelist.io/r/M3rik00 @Starknet
馃 Paid partnership
93
21
102
662
23Zver base.eth retweeted
There is a big difference between making an asset compliant and making compliance part of how that asset operates. Think about a tokenized asset that can only be transferred under certain conditions. The system needs to know who is allowed to receive it, which rules apply, and whether the required conditions have been met. Traditionally, a lot of these checks happen through separate processes, documents and manual reviews. But what if compliance rules could become part of the infrastructure itself? That's the idea behind Compliance-as-a-Service (CaaS). What I find interesting about @SimpleChain_RWA is that compliance isn't treated as an afterthought. Its architecture is designed to turn requirements such as jurisdiction, investor permissions and disclosure rules into machine-readable checks. This matters because real-world assets don't operate in a world without boundaries. For RWA to become more than digital representations of existing assets, the infrastructure needs to understand not only what an asset is, but also the rules governing how it can move. And I believe this is one of the most important pieces of building a trustworthy RWA ecosystem.
馃 Paid partnership 路 馃 Made with AI
Halloween felt like the perfect excuse to let my raccoon enter a different kind of adventure. 馃巸 A little mystery, a haunted atmosphere, some crypto magic and, of course, SimpleChain right in the middle of it. I wanted to create something that brings both worlds together instead of making just another Halloween picture. So here's my little take on @SimpleChain_RWA 脳 Halloween. Happy Halloween, everyone! 馃懟 #SimpleChain #SimpleChainHalloween #Halloween2026
47
4
82
700
There is a big difference between making an asset compliant and making compliance part of how that asset operates. Think about a tokenized asset that can only be transferred under certain conditions. The system needs to know who is allowed to receive it, which rules apply, and whether the required conditions have been met. Traditionally, a lot of these checks happen through separate processes, documents and manual reviews. But what if compliance rules could become part of the infrastructure itself? That's the idea behind Compliance-as-a-Service (CaaS). What I find interesting about @SimpleChain_RWA is that compliance isn't treated as an afterthought. Its architecture is designed to turn requirements such as jurisdiction, investor permissions and disclosure rules into machine-readable checks. This matters because real-world assets don't operate in a world without boundaries. For RWA to become more than digital representations of existing assets, the infrastructure needs to understand not only what an asset is, but also the rules governing how it can move. And I believe this is one of the most important pieces of building a trustworthy RWA ecosystem.
馃 Paid partnership 路 馃 Made with AI
Halloween felt like the perfect excuse to let my raccoon enter a different kind of adventure. 馃巸 A little mystery, a haunted atmosphere, some crypto magic and, of course, SimpleChain right in the middle of it. I wanted to create something that brings both worlds together instead of making just another Halloween picture. So here's my little take on @SimpleChain_RWA 脳 Halloween. Happy Halloween, everyone! 馃懟 #SimpleChain #SimpleChainHalloween #Halloween2026
47
4
82
700
23Zver base.eth retweeted
One thing I don't want from an AI agent is blind confidence. Things don't always go as planned onchain. A transaction can fail, market conditions can change, or an action might no longer make sense by the time it's ready to execute. What matters then is how the agent reacts. Does it explain what happened? Can it adjust its approach? Or does it just keep trying without giving the user a clear picture? I've been thinking about this while following @meetmotes. To me, a useful agent isn't one that never makes mistakes. It's one that can recognize when something went wrong, explain it in simple terms, and leave the user in control of what happens next. Trust isn't built by pretending everything works perfectly. It's built by being transparent when it doesn't.
馃 Paid partnership 路 馃 Made with AI
A single instruction doesn't always tell the whole story. In Web3, the same action can have a different meaning depending on what the user is trying to achieve. An agent that only follows commands might complete the requested step but miss the bigger objective. That's why context matters so much in AI. Understanding the intention behind an action can be more valuable than simply recognizing the instruction itself. I've been thinking about this while following @meetmotes. If AI agents are going to handle more complex onchain workflows, they need to understand not just what users ask for, but why they're asking for it. The better an agent understands the goal, the more relevant its assistance can become. That's the kind of progress I'd like to see in this space.
26
1
1
57
1,167
One thing I don't want from an AI agent is blind confidence. Things don't always go as planned onchain. A transaction can fail, market conditions can change, or an action might no longer make sense by the time it's ready to execute. What matters then is how the agent reacts. Does it explain what happened? Can it adjust its approach? Or does it just keep trying without giving the user a clear picture? I've been thinking about this while following @meetmotes. To me, a useful agent isn't one that never makes mistakes. It's one that can recognize when something went wrong, explain it in simple terms, and leave the user in control of what happens next. Trust isn't built by pretending everything works perfectly. It's built by being transparent when it doesn't.
馃 Paid partnership 路 馃 Made with AI
A single instruction doesn't always tell the whole story. In Web3, the same action can have a different meaning depending on what the user is trying to achieve. An agent that only follows commands might complete the requested step but miss the bigger objective. That's why context matters so much in AI. Understanding the intention behind an action can be more valuable than simply recognizing the instruction itself. I've been thinking about this while following @meetmotes. If AI agents are going to handle more complex onchain workflows, they need to understand not just what users ask for, but why they're asking for it. The better an agent understands the goal, the more relevant its assistance can become. That's the kind of progress I'd like to see in this space.
26
1
1
57
1,167
23Zver base.eth retweeted
A referral program makes more sense when both people get something out of it. I like that the ero invite offer works both ways: bring up to 5 friends into the app, and you can both receive a $5 bonus when they complete the referral requirements. No complicated story here. You share something you鈥檙e exploring, your friend gets a reason to give it a try, and both of you can benefit. It鈥檚 a small but interesting way for @earnos_io to encourage people to bring others into the ero ecosystem. Personally, I prefer this kind of referral model over promotions where only the person sharing the link gets rewarded. It鈥檚 just a shame that ero isn't available in some regions yet. I'd love to invite a few of my friends, but unfortunately, they can't access the app for now. Hopefully, that changes soon.
馃 Paid partnership 路 馃 Made with AI
A product can have impressive technology behind it and still fail if people struggle to use it. Most users don't care how many layers of infrastructure are working in the background. They care whether the experience makes sense, whether things work as expected, and whether the value is clear. That's one reason I find the consumer side of @earnos_io interesting. The idea of discovering opportunities, completing activities and receiving rewards shouldn't require someone to understand blockchain, wallets or complicated Web3 mechanics first. Good technology doesn't always need to be visible. Sometimes its biggest achievement is making something that used to feel complicated completely ordinary. And I believe that's how more people will eventually enter Web3 - not by learning every technical detail, but by finding products they actually want to use.
25
1
47
534
23Zver base.eth retweeted
Replying to @23Zver
free money for just sharing an app with friends sounds like an easy win
1
1
1
8