The World Cup offers a concrete setting for watching how Web3 wallets are changing. Whether a team advances, how championship odds move, and what fans debate every day can all become priced trading behavior in prediction markets such as Polymarket. When mainstream Web3 wallets integrate World Cup prediction activities, the result is more than a seasonal campaign. Over a longer timeline, it becomes a lightweight entry point for users to step into on-chain interaction, and it pushes wallets beyond the familiar roles of balance display and transaction signing.
World Cup predictions become an entry point for AI-assisted wallets
In this round of World Cup-related exploration, imToken has started placing AI Agents into actual use cases. The agents it launched on the web and in Discord are designed around specific prediction needs and can help users complete betting transactions in a more natural way. Users no longer have to complete every action only inside a wallet app. They can participate in prediction markets from Discord, web pages, and other contexts, while being guided by an Agent back to the on-chain process.
This can be read as an early form of the Agentic Wallet. The Web3 wallet of the future does not have to remain limited to a standalone wallet application, but it will increasingly resemble an AI wallet form that is present wherever users express intent. Over the past decade, the core questions for wallets were comparatively clear: where assets are stored, who controls the private key, and who signs the transaction. When users open imToken, they usually do so to check balances, send assets, interact with protocols, or manage multi-chain holdings. At that stage, the wallet is mainly an asset entrance and a signing entrance. The user already knows what to do, and the wallet completes the final step.
The Agentic shift changes that sequence. Users do not always begin by knowing which button to click. In a World Cup scenario, an ordinary user may not start with the thought, “I need to open Polymarket, find a specific market, assess the odds, and finish the trade.” The more natural questions are: “What is interesting about tonight’s match?”, “I think Portugal will advance; is there a related market?”, “Are these odds already too low?”, or “If I only want to participate with a small amount, what is the process?” In the past, these questions were scattered across WeChat groups, social platforms, or search engines. Each user had to piece the information together and then execute step by step. Once an Agent is introduced, the interaction model changes: the user expresses a rough intent, the Agent breaks down the path, and the wallet turns that path into a series of on-chain actions.
The wallet shifts from a function menu to an intent interpreter
This is not simply a matter of adding a chat box to a wallet. The deeper change is that the wallet begins moving from a “function menu” toward an “intent interpreter.” Earlier wallets asked users to decide whether they wanted to transfer, swap, stake, or connect to a DApp. A wallet in the Agentic era can move closer to natural language: users describe what they want to accomplish, and the system helps locate the route. A mass event like the World Cup is well suited to this role because it already carries context, gives users something to express, and requires judgment. The Agent does not need to begin by managing complex asset portfolios. It can first help users find an interaction path inside a specific scenario, then return final control to the wallet and the user.
The web-based and Discord-based agents mentioned in imToken’s exploration are a clear example. They bring wallet capabilities into lighter entry points. A user does not necessarily need to open the app first, nor enter a traditional DApp browser first. Instead, the user can start from an event page or a World Cup context, then use the Agent to find the path into an on-chain interaction. That also shows that the boundary of the wallet is expanding outward. In the past, the wallet entrance was relatively clear: open the app, enter the asset page, click a function, and connect to a DApp. In the next stage, wallet entrances can be distributed across web pages, Discord, Telegram, AI chat boxes, activity pages, developer tools, and even lightweight wallet interfaces generated by users themselves.
From this angle, the prediction activity itself is not the only point. The more important change is that it allows the wallet to stand in front of user intent in a more natural way. If viewed only from inside Crypto, Agentic Wallet may look like a narrative concept: AI helps users watch markets, find opportunities, and place trades, which sounds similar to an extension of the last AI Agent wave. But Mastercard’s launch of Agent Pay for Machines on June 10 makes the subject no longer exclusive to Web3.
Mastercard and WeChat Pay show the same payment boundary problem
Mastercard defines Agent Pay as a way for trusted AI Agents to participate in payments under user authorization. Its design concerns include how an Agent is identified, how it is authorized, how it is verified within a payment network, and how merchants, issuers, and users can know that a transaction was completed with assistance from an Agent. These are highly similar to the issues now facing Web3 wallets. When AI only helps write copy, the cost of an error is usually limited. Once AI starts participating in asset interactions, the questions become very different: does it have permission, has it understood the user’s intent correctly, is the service it calls trustworthy, has the transaction exceeded its boundary, and who is responsible if the result does not match the user’s expectation?
Mastercard’s answer is to redesign the identity, token, authorization, risk control, and dispute handling of trusted Agents within payment networks. Domestic payment giants are also moving in the same direction. WeChat Pay is testing AI payment functions together with Tencent’s agent product WorkBuddy, including the launch of an “AI dedicated card” inside WeChat Wallet. Based on disclosed information, the core of this product is not to let AI spend money freely. It is to set boundaries for agent payments through prepaid balances, payment authorization scopes, password verification, and confirmation procedures. In other words, AI can participate in payments, but it has to be identified, authorized, restricted, and audited.
Web3 wallets are facing the on-chain version of the same problem. The difference is that traditional payment systems emphasize networks, merchants, issuers, and compliance responsibilities, while on-chain wallets emphasize private keys, signatures, authorizations, contract calls, and user self-custody. For that reason, an Agentic Wallet cannot simply copy the traditional payment path. In traditional payments, users can rely on banks, card networks, merchants, dispute resolution, and risk-control systems. In the on-chain world, once a transaction is recorded, there is often no undo button. The higher the efficiency brought by an AI Agent, the more important the wallet becomes as the final security boundary.
Control remains the foundation of the Agentic Wallet
When people discuss AI Agents, they often drift toward an extreme version of the idea: AI automatically trades, automatically manages funds, automatically finds airdrops, and automatically arbitrages. That direction has appeal, but for a wallet, the hardest part is not automation. It is the sense of boundary. A wallet is not an ordinary app. If AI recommends the wrong song, writes the wrong paragraph, or clicks the wrong page, the problem is usually an experience issue. In a wallet, if AI misunderstands an instruction, calls the wrong contract, or grants excessive authorization, the result can become a real asset risk. The first principle question for an Agentic Wallet is therefore not how much AI can do for the user, but how the user knows what the AI is doing.
This also explains why imToken has continued to emphasize control over the past few years. From self-custodial wallets to multi-chain asset management, and now to AI co-creation and Agent exploration, the continuous thread is not simply that more functions are being added. The thread is that users must be able to understand, confirm, and control their digital world. In the Agentic era, this principle becomes more concrete. A wallet has to help users understand who the Agent is, which capabilities it can call, how long the authorization lasts, whether it can operate across DApps, when the user needs to confirm again, and whether the user can pause or revoke it with one action.
The strength of an AI Agent comes from its ability to simplify complicated processes. A user can say one sentence, and the Agent can break it into more than a dozen execution steps. That improves the experience, but it also creates a security challenge. The longer the path and the more intermediate steps it contains, the more the wallet has to bring key nodes back in front of the user. A strong wallet interaction does not mean showing users more technical detail. It means translating complex transactions into language that users can understand. The World Cup prediction activity is an event entrance, while imToken’s web Agent and Discord Agent are community entrances. Agentic Wallets have already begun entering real usage flows through these small scenarios.