Futures
Access hundreds of perpetual contracts
CFD
Gold
One platform for global traditional assets
Options
Hot
Trade European-style vanilla options
Unified Account
Maximize your capital efficiency
Demo Trading
Introduction to Futures Trading
Learn the basics of futures trading
Futures Events
Join events to earn rewards
Demo Trading
Use virtual funds to practice risk-free trading
Launch
CandyDrop
Collect candies to earn airdrops
Launchpool
Quick staking, earn potential new tokens
HODLer Airdrop
Hold GT and get massive airdrops for free
Pre-IPOs
Unlock full access to global stock IPOs
Alpha Points
Trade on-chain assets and earn airdrops
Futures Points
Earn futures points and claim airdrop rewards
Promotions
AI
Gate AI
Your all-in-one conversational AI partner
Gate AI Bot
Use Gate AI directly in your social App
GateClaw
Gate Blue Lobster, ready to go
Gate for AI Agent
AI infrastructure, Gate MCP, Skills, and CLI
Gate Skills Hub
10K+ Skills
From office tasks to trading, the all-in-one skill hub makes AI even more useful.
GateRouter
Smartly choose from 40+ AI models, with 0% extra fees
Google Chrome's automatic background download of the local AI model Gemini Nano has raised concerns about browser security within the crypto community.
BlockBeats News, May 9 — Chrome will download a several-gigabyte AI model file without user awareness, used for local anti-fraud, webpage summarization, and AI feature support. Although Google states that running AI locally can enhance privacy and security, many encrypted users question the lack of transparency and explicit authorization.
Analysis suggests that as browsers gradually become the core entry point for encrypted wallets, on-chain transactions, and DApps, the browser itself has become an important part of the encryption security system. Industry experts worry that deep AI integration, while potentially improving phishing website detection, will also expand the attack surface of browsers, including risks such as malicious plugins, fake transaction pages, and wallet hijacking.
The article points out that in the future, encrypted users may need to manage their browser environment as carefully as they do hardware wallets, including isolating browser configurations, restricting extension permissions, and using hardware wallets to store large assets.