Trading app fomo said in a post on X that its multi-factor authentication feature is now available to all users. According to the company’s statement, the rollout includes support for Passkey, authenticator apps, and Face ID. The update was disclosed through fomo’s official X account. No additional implementation details were provided in the post.
TRON mainnet's committee proposal No. 107 has passed and taken effect, enabling the TVM Prague and Osaka compatibility features introduced in GreatVoyage-v4.8.2. The activated update lets contracts read historical block hashes directly from on-chain state. It also adds the CLZ instruction to the TVM, natively supports the secp256r1 precompile contract used for Passkey verification, and optimizes MODEXP energy consumption. According to ChainCatcher, the newly enabled capabilities improve alignment between TRON's TVM and Ethereum's Prague and Osaka upgrades. The proposal number and the upgrade's two named compatibility targets point to the same stated direction: making TRON's virtual machine a closer match for the latest Ethereum hard-fork specifications. For teams building smart contracts, migrating developer tools, or adapting EVM ecosystem applications, the changes deliver a more complete development environment. The proposal passed through TRON's mainnet committee process and took effect immediately after the vote. ChainCatcher's coverage identifies the update as part of the ongoing GreatVoyage release series.
Bankr developer deployer has again commented on the compromise of Bankr’s X account, arguing that the incident may indicate one of two possibilities: a serious undiscovered security flaw in X’s backend systems, or involvement by insiders. According to deployer, Bankr had already enabled Passkey protection, yet when the team tried to regain access, they were redirected to an appeal page for a suspended account. At the same time, the attacker was still able to log in and post malicious links even after the team had lost access. deployer also said the team began receiving 503 errors from the X API while the attacker continued posting normally. He questioned why the legitimate team was restricted while the attacker appeared to retain full permissions. The developer added that several other high-profile X accounts, including Robinhood CEO and the official SpaceX account, were reportedly taken over recently, with some of those accounts said to have had MFA enabled as well. He called on X to investigate the matter and explain what happened.
X has revoked previously associated Passkey and Yubikey credentials, advising users to re-set up on the new domain. The move highlights the fragility of domain-bound authentication methods.
Gemini released a self-custody smart wallet and onchain dashboard on Aug 14, 2025. It uses passkey login, sponsors gas fees with Arbitrum, Polygon, Optimism, and Base, and enables DeFi, DApp exploration, and cross-chain swaps.
Crypto exchange Gemini announced on Aug. 14 the release of Gemini Wallet, a self-custody smart wallet featuring passkey login, gas-free transactions via L2 partnerships, and full Web3 integration including the Gemini Onchain Dashboard.
Gemini introduces Gemini Wallet, a self-custody smart wallet with passkey login, gas-free transactions via L2 partnerships, and an onchain dashboard for DeFi, dapp exploration, and yield vaults.
As AI agents move from answering questions to taking real actions on behalf of users, authorization is becoming a critical security layer. In this article, imToken’s new “Sign” narrative is examined through Sigil, an early proof-of-concept product designed to sit between AI agents and wallets. The core issue is that many agents still rely on vague chat-based approvals such as “Yes” or “Confirm,” even when the underlying action may involve fund transfers, token approvals, contract calls, code execution, or access to sensitive services. That model creates three major risks: users often cannot see the exact parameters of what they are approving, a chat reply is not equivalent to a cryptographic signature by the account owner, and the approval interface itself can be manipulated by the same agent that initiates the request. Sigil’s answer is to rebind display, signing, and execution into a verifiable flow. Low-risk actions can proceed under predefined policies, while sensitive operations trigger a pause and generate a structured approval card sent through Telegram. The user must then confirm with Passkey and biometric authentication before the action can continue. The article also highlights Sigil’s three protection layers: clear presentation of real request parameters, proof that only the actual user can approve, and an isolated confirmation module anchored on-chain and rendered in a sandbox to prevent interface forgery. While the need is most obvious in crypto, the framework may extend to email, files, terminals, identity usage, payments, and broader agent permissions.
