The World Cup provides a useful lens for looking at how Web3 wallets are changing. Topics that football fans discuss every day, such as whether a team will qualify or how championship odds shift, become priced trading behavior in prediction markets such as Polymarket. When mainstream Web3 wallets integrate World Cup prediction activities, those integrations function as a lightweight entry point into on-chain interaction rather than a standalone campaign.

In this World Cup-related exploration, imToken has begun placing AI Agents into practical user environments. Its agents on the web and in Discord are designed around specific prediction needs, helping users complete betting-related transactions in a more natural flow. Users no longer have to operate only inside a wallet app. They can enter through Discord or a web page, participate in prediction-market activity, and be guided back on-chain by an Agent. This is an early form of what an Agentic Wallet can look like: the future Web3 wallet does not have to be confined to a wallet application, but can appear as an AI wallet form that is present across the scenarios where users already spend time.
From asset gateway to intent interpreter
For the past decade, the core wallet questions were relatively clear: where assets are stored, who controls the private key, and who signs the transaction. A user opening imToken has typically done so to check balances, send assets, interact on-chain, or manage multi-chain holdings. In that phase, the wallet acted as an asset gateway and a signing gateway. The user already knew what they planned to do, and the wallet handled the final critical step.

The Agentic era changes that sequence because the user may not know at the beginning which button to press. In a World Cup scenario, an ordinary user may not first think: open Polymarket, find a market, judge the odds, and execute a trade. The user is more likely to ask: what is interesting about tonight’s match, is there a market related to Portugal qualifying, are these odds already too low, and how does the process work if I only want to participate with a small amount. In the past, these questions were scattered across WeChat groups, social platforms, or search engines. Each user had to piece together the information and then carry out the steps manually.
Once an Agent enters the process, the interaction changes. The user only needs to express a broad intention. The Agent breaks that intention into a path, and the wallet turns the path into a sequence of on-chain actions. This is therefore not simply a matter of adding a chat box to a wallet. The real shift is that the wallet moves from being a functional menu to being an intent interpreter. Earlier wallets mainly asked the user whether they wanted to transfer, swap, stake, or connect to a DApp. A wallet designed for the Agentic Wallet phase allows the user to describe the desired outcome in natural language.

Why the World Cup works as an entry point
A mass event like the World Cup is suitable as an entry point for Agentic Wallets because it already contains context, gives users something to say, and requires judgment. An Agent does not need to begin by managing a complex asset portfolio for the user, especially when complex asset management carries higher risk. It can first help the user find an interaction path inside a specific scenario, while leaving final control with the wallet and the user.
The web and Discord agents that imToken has tested are representative of this direction. They move wallet capability into lighter entry points. A user does not necessarily have to open the app first or enter a traditional DApp browser first. The user can arrive through an event page or a World Cup context and use an Agent to find the path to interaction. This means the boundary of the wallet is spreading outward. Previously, the wallet entry point was easy to define: open the app, go to the asset page, click a function, and connect to a DApp. In the future, wallet entry points 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 that angle, the World Cup prediction activity is not the main point by itself. Its significance lies in allowing the wallet to stand in front of user intent in a more natural way. If viewed only from within crypto, Agentic Wallet can be reduced to a narrative in which AI helps users watch markets, find opportunities, and trade. That sounds like an extension of the previous AI Agent wave. But Mastercard’s launch of Agent Pay for Machines on June 10 moved the discussion outside Web3 as well.
Agentic commerce enters the payment network
Mastercard defines Agent Pay around enabling trusted AI Agents to participate in payments under user authorization. The framework addresses 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 assisted by an Agent. These are highly similar to the problems faced by Web3 wallets.
When AI is only helping write copy, the cost of an error is usually limited. Once AI begins to participate in asset interaction, the issue changes. Does the Agent have permission. Has it correctly understood the user’s intent. Is the service it calls trustworthy. Does the transaction it initiates exceed the allowed boundary. If the result does not match the user’s expectation, who handles the consequence. Mastercard’s answer is to redesign trusted Agent identity, tokens, authorization, risk control, and dispute handling inside the payment network. This signal matters because it places Agentic Commerce inside a concrete commercial context rather than leaving it only as a crypto-native technical imagination.

Domestic payment giants are also moving in this direction. WeChat Pay is testing AI payment functions together with Tencent’s agent product WorkBuddy. One disclosed example is the launch of an AI Exclusive Card inside WeChat Wallet. Based on the disclosed information, the core of such products is not to let AI spend money freely, but to set boundaries for agent payments through recharge limits, payment authorization scope, and password verification confirmation. This follows the same line as Mastercard Agent Pay: AI can participate in payment, but it must be identified, authorized, limited, and audited.
The on-chain version of the same boundary problem
Web3 wallets face the on-chain version of the same question. The difference is that traditional payment systems emphasize networks, merchants, issuers, and compliance responsibilities, while on-chain wallets emphasize private keys, signatures, authorization, contract calls, and user self-custody. For that reason, Agentic Wallets cannot simply copy the traditional payment route. In traditional payments, users can rely on banks, card networks, merchants, dispute processes, and risk-control systems. In the on-chain world, once a transaction is submitted to the chain, there is often no undo button.

The more efficiency an AI Agent brings, the more important the wallet becomes as the last safety boundary. A future wallet should not merely allow an Agent to do things; it should ensure that the Agent can act only within the scope permitted by the user. This is also why Web3 is a particularly direct place to discuss Agentic Wallets. Discussions about AI Agents often move toward an extreme image in which AI automatically trades, manages assets, finds airdrops, and arbitrages. That direction is attractive, but for wallets the hardest problem is not automation. It is boundary design.
A wallet is not an ordinary application. If AI recommends the wrong song, writes the wrong paragraph, or clicks the wrong page in a normal app, the result is mostly an experience problem. If AI misunderstands an instruction inside a wallet, calls the wrong contract, or grants excessive authorization, the result can become a real asset risk. The first-order question for an Agentic Wallet is therefore not how many tasks AI can perform for the user, but how the user knows what the AI is doing.

This is why imToken has emphasized 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 the addition of more functions. It is that users must be able to understand, confirm, and control their digital world. In the Agentic era, that principle becomes more specific. The wallet needs to show the user who the Agent is, which capabilities it can call, how long authorization lasts, whether it can operate across DApps, when the user must confirm again, and whether the user can pause or revoke it with one action.
The power of an AI Agent comes from simplifying complex processes. A single user sentence can be broken into a path of more than ten execution steps. That improves the experience, but it also creates a security challenge. The longer the path and the more intermediate links it contains, the more the wallet must bring key checkpoints back in front of the user. Good wallet interaction in the future is not necessarily about showing more technical details. It is about translating complex transactions into language users can understand. The World Cup prediction activity is an event entry point, while imToken’s web Agent and Discord Agent are community entry points. The Agentic Wallet is beginning from these small, concrete scenarios.

