The World Cup provides a practical setting for observing how crypto wallets are changing. Questions that football fans discuss every day — whether a team can qualify, how championship odds move, and which match deserves attention — can become priced trading behavior in prediction markets such as Polymarket. When mainstream Web3 wallets integrate World Cup prediction activities, the result is not only a campaign around a sports event; over a longer timeline, it becomes a lightweight entry point for users to begin interacting on-chain.

World Cup prediction as an on-chain entry point
In this World Cup-related exploration, imToken has started to place AI Agents into real usage scenarios. The agents it introduced on the web and in Discord can help users complete prediction-related transactions around concrete needs. Instead of operating only inside a wallet app, users can participate in prediction markets through Discord or a web page, while the agent guides them back to on-chain interaction in a smoother way.

This is an early version of what an Agentic Wallet can look like. The future Web3 wallet is not limited to a standalone wallet application; it is closer to an “AI wallet form” that appears across many user contexts. Over the past decade, the wallet’s core problems were clear: where assets are stored, who controls the private key, and who signs the transaction. A user opened imToken mainly to check balances, transfer assets, interact with protocols and manage multi-chain holdings. At that stage, the wallet functioned as an asset entry point and a signing entry point. The user already knew what they wanted to do, and the wallet completed the final step.
From function menu to intent interpreter
The Agentic era changes that starting point. A user does not always begin by knowing which button to click. In a World Cup scenario, an ordinary user is less likely to start with: “I want to open Polymarket, find a specific market, judge the odds and complete a trade.” The more natural questions are: “What is interesting about tonight’s match?” “I favor Portugal qualifying; is there a related market?” “Is this price already too low?” “If I only want to participate with a small amount, what is the process?”

Previously, these questions were scattered across WeChat groups, social platforms, discussions and search engines. Users had to assemble the information themselves and then execute each step. Once an agent enters the process, the mode of interaction changes. The user only needs to express a broad intent; the agent breaks down the route, and the wallet turns that route into a series of on-chain actions. This is not simply adding a chat box to a wallet. The deeper change is that the wallet moves from being a “function menu” to an “intent interpreter.” In the old model, users decided whether they wanted to transfer, swap, stake or connect to a DApp. In the next model, they describe the outcome they want in natural language.
This is why a mass event such as the World Cup is suitable as an entry point for Agentic Wallets. It naturally provides context, gives users something to say, and requires judgment. The agent does not need to begin by managing a complex asset portfolio for the user, especially because complex asset management carries higher risk. It can first help users find an interaction route in a specific scenario, and then return the final control to the wallet and the user. imToken’s web agent and Discord agent are examples of bringing wallet capabilities into lighter entry points, without requiring users to open an app first or enter a traditional DApp browser first.

Wallet boundaries are moving outward
The boundary of the wallet is expanding. In the past, the wallet entry point was relatively clear: open the app, enter the asset page, click a function, and connect to a DApp. In the next phase, wallet entry points can be distributed across web pages, Discord, Telegram, AI chat boxes, campaign pages, developer tools, and even lightweight wallet interfaces generated by users themselves. From this angle, World Cup prediction is not the core point. The core point is that it places the wallet more naturally in front of user intent.
If viewed only from inside crypto, Agentic Wallets can be treated as a narrative: AI helps users read markets, find opportunities and trade. Mastercard’s launch of Agent Pay for Machines on June 10 makes the issue broader than Web3. Mastercard defines Agent Pay as a way for trusted AI agents to participate in payments under user authorization. It involves how the agent is identified, how it is authorized, how it is verified within the payment network, and how merchants, issuers and users know that a transaction was assisted by an agent.

This is highly similar to the question Web3 wallets face. When AI only helps write copy, the cost of an error is usually controllable. Once AI participates in asset interaction, the questions change: does it have permission, does it understand the user’s intent correctly, is the service it calls trustworthy, does the transaction exceed its boundary, and who handles the case when the result does not match the user’s expectation? Mastercard’s answer is to redesign the identity, tokens, authorization, risk controls and dispute handling for trusted agents inside the payment network.
Payment agents and the on-chain version of the same problem
Domestic payment companies are also moving in this direction. WeChat Pay is working with Tencent’s agent product WorkBuddy to test AI payment functions, including an “AI dedicated card” in WeChat Wallet. Based on disclosed information, the core of such products is not to let AI spend freely. Instead, they set boundaries for agent payments through top-up limits, payment authorization scopes and password confirmation. This follows the same logic as Mastercard Agent Pay: AI can participate in payment, but it must be identified, authorized, restricted and audited.

Web3 wallets face the on-chain version of the same issue. 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. In traditional payments, users can rely on banks, card networks, merchants, dispute handling and risk control systems. On-chain, once a transaction is recorded, there is often no undo button. The more efficiency AI agents bring, the more important the wallet’s role becomes as the final safety boundary. Future wallets must not only allow agents to act; they must also ensure agents act only within the scope users allow.
This is why Web3 is a fitting environment for discussing Agentic Wallets. Discussions about AI agents often move toward extreme automation: AI automatically trades, manages money, finds airdrops or conducts arbitrage. That direction is attractive, but for wallets the hardest problem is not automation; it is boundary awareness. A wallet is not an ordinary application. In a normal app, an AI recommendation of the wrong song, a mistaken paragraph or a wrong page click is mainly an experience issue. In a wallet, a misunderstood instruction, a wrong contract call or an excessive approval can become a real asset risk.

Therefore, the first-order question for Agentic Wallets is not “how much can AI do for the user,” but “how does the user know what AI is doing.” This is also why imToken has emphasized control over the past several years. From self-custodial wallets to multi-chain asset management, and now to AI co-creation and agent exploration, the continuous line is not simply more features. It is that users must be able to understand, confirm and control their digital world. In the Agentic era, that line becomes more specific: users need to understand who the agent is, what capabilities it can call, how long authorization lasts, whether it can operate across DApps, when confirmation is required again, and whether it can be paused or revoked with one action. The World Cup prediction activity is an event entry point; imToken’s web agent and Discord agent are community entry points where this shift has already begun in small, concrete scenarios.

