News
15 May 2026, 14:11
Gemini Stock Jumps on Revenue Rise, $100M Bitcoin Investment From Winklevoss Capital

Crypto exchange Gemini secured a $100 million Bitcoin investment from its founders’ fund, and revealed a 42% YOY Q1 revenue bump.
15 May 2026, 14:00
Kraken API Unlocked: running multi-strategy operations on Kraken — subaccounts, API keys, and the two layers of separation that matter

TL;DR Most multi-strategy operations need two layers of separation: process isolation (one API key per process) and strategy isolation (subaccounts with their own balances, P&L, and risk surface). Kraken supports both natively. Multiple API keys solve process problems inside one account: separate nonce sequences, scoped permissions, clean blast radius if a single key is compromised. Subaccounts isolate each strategy across linked accounts: separate balances, separate margin calculations, separate per-account rate limits, while still consolidating into one volume tier for fees. Subaccounts on Kraken Derivatives are open to any eligible client (set up via support ticket); on Kraken Spot they are gated to institutional clients via the Kraken institutional team. Run one API key per process . Most “invalid nonce” errors in production are one key shared across multiple processes, not a clock-skew problem. Two layers of separation: process isolation vs. strategy isolation The core architectural question for systematic traders is how to separate strategies, permissions, and balances across accounts and processes. Kraken provides two distinct answers, operating at different layers. Multiple API keys isolate processes and permissions within one account. Each key carries its own nonce sequence, can be scoped to specific permissions, and creates clean process boundaries. Balances, volume tier, and per-pair rate limits remain shared across keys. Subaccounts isolate what API keys cannot. Each subaccount on Kraken has its own balances, its own P&L, its own API keys, and its own rate limits. Margin is calculated at the subaccount level. A master account links all subaccounts — and crucially, trading volume across linked accounts is consolidated for fee schedule tier purposes. What each layer isolates Dimension Multiple API keys (one account) Subaccounts (linked accounts) Balances Shared across keys Separate per subaccount Volume tier (fees) Shared Consolidated across linked accounts Rate limits Shared per-pair Separate per account Margin and risk surface Shared Separate per subaccount API keys Multiple per account Generated and controlled per subaccount Layer one: API key management for multi-strategy operations One API key per process A momentum bot and a market-making bot pointed at the same key will collide on nonces. The most common nonce error in production isn’t clock skew, it’s one key shared across multiple processes, each incrementing the nonce independently and racing each other to the API. Split the key, don’t raise the nonce window. The same rule applies to every process that is not the primary trading bot: monitoring dashboards, P&L reconcilers, position-flattening scripts, and backtests replaying live data against the REST API each need a dedicated key. When a key throws an error or hits a rate limit, you immediately know which process to investigate. Minimum permissions per role Kraken API keys are fully scoped. A read-only dashboard does not need order placement permissions. A reconciliation job pulling trade history does not need withdrawal permissions, ever. Scope each key to exactly what its process requires and nothing more. The cost is one minute during key creation. For the full set of best practices (including permission scopes, key 2FA, expiration, rotation, and per-key controls) see Kraken’s API Key Security guide and How to create an API key documentation. Layer two: subaccounts on Kraken Subaccounts deliver two structural advantages for multi-strategy operations: Trading volume across linked accounts is grouped for the Fee Schedule Volumes tier. Funds move instantly and fee-free between the master account and subaccounts. The canonical use case is running a market-making book and a directional book in parallel without commingling exposure. Separate mandates, separate volatility profiles, or a hedging book against a directional position; each operates within its own risk surface, preventing one strategy’s drawdown from affecting another’s margin or liquidation threshold. A master Owner manages each Subaccount User. Each Subaccount User has its own KYC and its own Account, while staying linked to the Owner for transfers and consolidated volume tiers. How to create a Kraken subaccount (Derivatives and Spot) Kraken Derivatives is open to any eligible client. Subaccount creation goes through the Kraken support team: Create a new Kraken account for the subaccount and verify it. Unlock Derivatives trading from the subaccount. Submit a Kraken Derivatives support ticket from the master account email address requesting that the accounts be linked. Once linked, subaccount management (listing, balance retrieval, and transfers between master and subaccounts or between margin accounts sharing a collateral currency) runs through the Futures REST API. Kraken Spot is institutional-only. The REST API documents a CreateSubaccount endpoint, but availability is gated. CreateSubaccount must be called using an API key from the master account, and the endpoint requires the Withdraw Funds permission on that master key. Spot subaccounts are restricted to institutional clients. Reach this surface through your Kraken relationship manager. Kraken subaccount operational caveats Withdrawals from subaccounts are blocked. Funds have to be moved back to the master account before they can leave Kraken Derivatives. Build that into reconciliation and treasury workflows from the start. API keys are generated and controlled separately on each subaccount. The master account does not own subaccount keys. API rate limits are managed separately per account. Sign-ins are separate for each subaccount. Temporary lockouts last about 15 minutes. They trigger after too many failed API calls, invalid nonce errors, or invalid signatures in a short period. A misconfigured key in a tight retry loop can keep a strategy offline for the better part of an hour. Getting started: API keys and subaccounts Audit current keys. What each one is used for, what permissions it has, whether IP restriction is on. Split keys by process. One key per process, minimum permissions. Apply IP allowlists to every production key. Test in UAT before promoting any new key configuration to production. Decide on subaccounts. Multiple keys are enough if strategies share capital. Subaccounts are needed when strategies need separate capital, P&L, or risk. Derivatives via support ticket, Spot through your Kraken relationship manager. Create an API key , or for institutional subaccount setups and FIX access, contact the Kraken Institutional team . Contact the Kraken Institutional team FAQ Who can use subaccounts on Kraken? Subaccounts on Kraken Derivatives are available to any eligible client and are set up via a support ticket. Subaccounts on Kraken Spot are currently available to institutional clients through the Kraken institutional onboarding team. What is the difference between API keys and subaccounts on Kraken? API keys isolate processes and permissions within a single Kraken account. Each key has its own nonce sequence and scoped permissions, but shares balances and rate limits. Subaccounts are separate linked accounts, each with independent balances, margin, rate limits, and API keys, while still consolidating trading volume into one fee tier. Can I withdraw directly from a Kraken Derivatives subaccount? No. Funds have to be moved back to the master account before they can leave Kraken Derivatives. Do subaccounts on Kraken share trading fees across linked accounts? Yes. Trading volume across all linked subaccounts is consolidated into a single fee schedule volume tier, meaning your combined activity across strategies contributes to lower fee rates. The post Kraken API Unlocked: running multi-strategy operations on Kraken — subaccounts, API keys, and the two layers of separation that matter appeared first on Kraken Blog .
15 May 2026, 13:40
Binance Wallet Blocks Search for Luo Yonghao Memecoin After Founder’s Complaint

BitcoinWorld Binance Wallet Blocks Search for Luo Yonghao Memecoin After Founder’s Complaint Binance Wallet has blocked search results for a memecoin that used the name and likeness of Chinese entrepreneur Luo Yonghao, following a direct complaint from Luo to Binance founder Changpeng Zhao (CZ). The token is no longer discoverable through the wallet’s built-in search function, according to a report from BlockBeats. Background of the Complaint Luo Yonghao, a well-known figure in China’s tech and business circles, publicly stated on social media that a cryptocurrency token using his name and profile picture was being traded on Binance. He expressed concern that the token could mislead users and cause financial harm. In his social media post, Luo called for the token to be delisted from the platform or, at minimum, for Binance to establish a formal reporting mechanism to address such unauthorized use of personal identities. Binance Wallet’s Response Following Luo’s appeal to CZ, Binance Wallet removed the token from its search index. As of now, users attempting to search for the memecoin by name within the wallet interface will not find it. This action appears to be a direct response to the complaint, though Binance has not yet issued a formal public statement regarding the delisting or any broader policy changes related to unauthorized celebrity memecoins. Implications for Memecoin Listings and User Protection The incident highlights ongoing tensions between decentralized token creation and the responsibility of centralized platforms like Binance to protect users from potentially deceptive assets. While memecoins often rely on viral appeal and celebrity association, this case demonstrates that platforms can and do respond to complaints when a token uses a person’s identity without consent. For traders, the event serves as a reminder to verify the legitimacy of tokens, especially those tied to public figures. For the broader crypto industry, it raises questions about how exchanges and wallets should handle tokens that may infringe on personal rights. Conclusion Binance Wallet’s removal of the Luo Yonghao memecoin from search results marks a notable instance of a major crypto platform acting on a personality rights complaint. While the token itself remains on-chain, its reduced visibility within Binance’s ecosystem limits its accessibility to new buyers. The incident underscores the evolving regulatory and ethical landscape for memecoins and the increasing pressure on exchanges to implement clearer policies for user protection. FAQs Q1: Is the Luo Yonghao memecoin completely removed from Binance? The token has been removed from search results in Binance Wallet, meaning users cannot find it through the wallet’s search function. However, it may still be accessible via direct contract address or on other decentralized platforms. Q2: Can other celebrities request removal of unauthorized memecoins? While Binance has not published a formal policy, this case suggests that the platform may respond to direct complaints from individuals whose identity is used without permission. Establishing a formal reporting mechanism is one of the steps Luo requested. Q3: Does this affect the token’s trading volume or price? Reduced discoverability on Binance Wallet likely limits new buyer access, which could impact trading volume and price. However, the token may still trade on other platforms or through direct peer-to-peer transactions. This post Binance Wallet Blocks Search for Luo Yonghao Memecoin After Founder’s Complaint first appeared on BitcoinWorld .
15 May 2026, 13:26
Donald Trump-Linked Crypto Bet? Trusts Bought MARA, COIN, MSTR, HOOD, SOFI and SQ in Q1

U.S. Office of Government Ethics disclosure documents have shown that trusts linked to President Donald Trump’s family bought shares of several crypto-related companies during the first quarter of 2026, adding digital asset exposure during a period of heavy securities trading. The filings , released Thursday, cover transactions from January through March and show total reported transaction values ranging from at least $220 million to roughly $750 million. The disclosures list values in broad ranges and do not provide exact trade prices, dates, profits, or the accounts used for each transaction. Among the crypto-linked purchases were securities tied to Bitcoin miner MARA Holdings, crypto exchange Coinbase Global, Bitcoin treasury firm Strategy, Robinhood Markets, SoFi Technologies, and Block Inc. The documents state that Trump’s assets are held in a trust controlled by his children, while some transactions indicate that a broker acted as an agent. The filings do not specify whether each trade involved common stock, corporate bonds or another type of security. The White House referred questions to the Trump Organization, while an attorney for the company did not immediately respond to requests for comment, according to the reports. Donald Trump Trusts Add Crypto-Linked Equities The reported purchase of MARA shares placed one of the largest publicly traded Bitcoin mining firms among the crypto-related names listed in the disclosures. MARA’s business is closely tied to Bitcoin mining economics, power costs, treasury strategy and digital asset market conditions. Coinbase, another reported purchase, gives exposure to U.S. crypto trading, custody and institutional market infrastructure. The company has also been active in policy debates around digital asset regulation. Strategy, formerly known as MicroStrategy, is one of the largest public corporate holders of Bitcoin. Its stock often trades as a proxy for Bitcoin exposure because of its large BTC treasury. Robinhood and SoFi offer consumer-facing financial products, including crypto trading in certain markets. Block, led by Jack Dorsey, has long been tied to Bitcoin through payments, wallet development and digital asset-related services. Together, the listed names show exposure across several parts of the crypto equity market, including mining, exchange infrastructure, Bitcoin treasury holdings, brokerage platforms and payments. Filings Show Broad Trading Activity The crypto-related purchases were part of a larger set of reported trades involving major U.S. companies. The disclosures included securities linked to Microsoft, Meta Platforms, Oracle, Broadcom, Bank of America, and Goldman Sachs, along with municipal bonds. Some individual purchases were valued between $1 million and $5 million each, including an S&P 500 index fund, Nvidia, and Apple. The filings also listed large sales ranging from $5 million to $25 million each in companies such as Microsoft, Amazon and Meta. Federal ethics rules require public officials to disclose transactions above $1,000, but the forms use broad value bands. That means the filings do not show exact amounts, execution prices, timing within the quarter, or whether trades were made directly by a trust manager, broker, or managed account. The president’s annual financial disclosure, expected later, is set to provide a wider view of business assets and income. That filing may include details on other areas such as real estate, golf properties and crypto-related ventures. Crypto Policy Debate Adds Context The disclosures arrive as Washington continues debating federal rules for digital assets. The Senate Banking Committee recently advanced the CLARITY Act, a crypto market structure bill aimed at dividing oversight between the Securities and Exchange Commission and the Commodity Futures Trading Commission. Some Democratic lawmakers have called for ethics language covering elected officials and their families who hold or promote digital assets. The issue became part of the wider debate around crypto legislation after reports that Trump and his family had exposure to several crypto-related projects. Eric Trump has also discussed digital assets at the Consensus conference, saying his family had faced restrictions from traditional banks. He described crypto as a way to reduce intermediary fees and support decentralized access to financial services.
15 May 2026, 13:11
Bitcoin exchange supply falls to an 8-year low

The supply of Bitcoin ( BTC ) on all cryptocurrency exchanges has declined to an 8-year low, amid notable demand from conviction investors. As of May 15, Bitcoin’s supply on all crypto exchanges hovered around 5.623% of the asset’s total supply, according to analytics from Santiment , analyzed by Finbold. Consequently, approximately 1,180,830 BTC, valued at about $95.2 billion at press time, sits on exchanges. Bitcoin supply change on all exchanges. Source: Santiment The notable decline in BTC supply on all crypto exchanges can be attributed to significant demand from conviction buyers. Furthermore, this group of investors has added BTC worth $243 billion year-to-date, bringing their total to nearly 4 million coins, as Finbold reported . The low supply of the flagship coin on exchanges could imply a rising demand for self-custodial services. Furthermore, crypto exchanges are prone to several risks, including attacks and insolvency. Bitcoin price faces a historical supply shock impact As the United States leads other jurisdictions in crypto regulatory certainty, as evidenced by the traction of the Clarity Act , a proposed U.S. federal law to legalize crypto assets, the ongoing supply shock could escalate. Moreover, more institutional investors have been seeking exposure in Bitcoin to diversify their portfolios. With BTC supply on crypto exchanges at a multi-year low, the expected increase in demand could trigger a historic supply shock. The growing demand for Bitcoin from institutional investors may not be quenched by the dwindling supply on cryptocurrency exchanges. As a result, Bitcoin price is well positioned to rebound towards its all-time high (ATH) and kickstart a fresh parabolic rally. Besides, VanEck expects BTC price to rally beyond $160,000, fueled by capital rotation from Gold, as Finbold explained . However, if the supply of Bitcoin on crypto exchanges increases in the near term, it could signal weakening conviction among holders, potentially exposing BTC to renewed selling pressure and delaying any parabolic price recovery. The post Bitcoin exchange supply falls to an 8-year low appeared first on Finbold .
15 May 2026, 12:11
How to Send USDC Without Holding ETH for Gas Fees

USDC sits in millions of wallets across Ethereum without ever moving because the holder doesn't have ETH for gas. The friction has been a known problem since Ethereum's earliest days. In 2025 and 2026, that problem will finally have a real fix at the protocol level, and a small group of wallets now lets users send USDC without holding ETH at any point. What Changed in 2025 With Pectra and EIP-7702 Ethereum's Pectra upgrade went live on mainnet on May 7, 2025. The upgrade activated EIP-7702 , a proposal that lets standard wallet addresses temporarily behave like smart contract accounts during a single transaction. The shift is technical, but the user-facing effect is direct: a wallet with only USDC can now send that USDC, with the network fee paid in USDC instead of in ETH. Before Pectra, sending USDC required ETH for gas. The wallet checked for an ETH balance, used it to pay the validator, then transferred the USDC. If the wallet had USDC but no ETH, the transfer failed with an "insufficient funds for gas" error. This blocked stablecoin-only users from any on-chain activity, which was a major barrier to broader stablecoin adoption. EIP-7702 removes the barrier by letting an externally owned account delegate to a smart contract for one transaction. The delegation enables a paymaster system to pay the gas fee in ETH on the user's behalf, then deduct the equivalent value in USDC from the transaction itself. The Paymaster Architecture A paymaster is a smart contract that pays gas on behalf of users. The user signs an authorization that grants the paymaster permission to deduct a small amount of USDC from their balance. The paymaster pays the gas in ETH at the moment of execution. The user never holds ETH at any step. This approach lets users pay gas in USDC without ever touching the native token. Circle, the issuer of USDC, runs an official Circle Paymaster service available across Ethereum, Arbitrum, Avalanche, Base, OP Mainnet, Polygon PoS, and Unichain. Wallet providers integrate the paymaster directly into their send flow, so users see a single confirm screen with the gasless USDC option already selected. Three components handle the gasless USDC transfer: EIP-2612 permit: the user signs a message authorizing the paymaster to spend a small amount of USDC EIP-7702 delegation: the wallet temporarily acts as a smart contract for the transaction Paymaster contract: pays the ETH gas fee and deducts the equivalent in USDC The whole process happens in one click from the user's perspective. The technical layer runs in the background. Wallets Supporting Gasless USDC in 2026 The question of how to send USDC without ETH has multiple working answers in 2026, depending on which wallet a user chooses. Several wallets now ship send USDC without ETH support, with EIP-7702 wallet integration becoming standard across major providers: IronWallet integrates gasless USDC transfers on Ethereum, with the fee deducted directly from the USDC balance. The wallet handles routing automatically when the user has no ETH balance. Trust Wallet rolled out gas sponsorship in November 2025, covering up to four swaps per day on Ethereum, BNB Chain, and Solana. Ethereum swaps require a $50 minimum per transaction. MetaMask offers a Gas Station feature that lets users pay swap fees in approved tokens, including USDC on Ethereum. The wallet charges a 0.875% in-wallet swap fee. Bitget Wallet uses EIP-7702 to let users pay gas in stablecoins, including USDC on Ethereum. Each wallet has trade-offs on chain coverage, fee structure, and supported transaction types. Sending USDC Without ETH Through IronWallet The six steps below walk through a complete gasless USDC transfer using IronWallet. Download IronWallet from the App Store or Google Play. The app runs on iOS and Android. Create or import a wallet. No email, no phone number, no KYC, no verification step. The app generates a 12-word seed phrase locally on your device. Back up your seed phrase securely. Write it down offline. IronWallet uses double-key encryption on the device, and the seed phrase is the recovery method if the device is lost. Add or select the Ethereum network inside the app. Copy your ERC-20 address and use it to receive USDC. Open the send screen, enter the recipient address and the USDC amount. IronWallet routes the transfer through the gasless flow automatically when the wallet has no ETH balance. Confirm with PIN or biometric login. The fee is deducted directly in USDC, not in ETH. No separate gas token balance is required at any step. The same flow applies to gasless USDT on Tron. Add the Tron network in the app, copy your TRC-20 address, and send USDT without holding TRX. Layer 2 as an Alternative for Lower Costs For users open to switching networks, Layer 2 chains like Base, Arbitrum, and Optimism offer USDC transfers at fees well below Ethereum mainnet even before gasless features apply. Base gas runs at 0.006 gwei as of May 2026, which translates to fractions of a cent per USDC transfer. Gasless USDC works on Layer 2 chains too. Circle Paymaster supports Arbitrum, Base, OP Mainnet, and Polygon PoS, so users can combine the lower L2 base cost with the paymaster mechanism for the cleanest experience. Conclusion How to send USDC without ETH is no longer a workaround in 2026. Ethereum's Pectra upgrade and EIP-7702 turned gasless USDC transfers into a default option across multiple wallets, with Circle Paymaster providing the protocol-level infrastructure. IronWallet, Trust Wallet, MetaMask, and Bitget Wallet all offer different implementations of the same idea: users send USDC with no ETH balance at any point. The shift turns gasless stablecoin transfers from a niche feature into a default capability across the self-custody category, with no ETH for gas required at any step. The gas token barrier that blocked stablecoin-only users for years is mostly gone. What replaced it is a small fee paid in USDC and a one-click signing flow that handles the technical layer in the background. FAQ Which wallets let me send USDC without ETH? In 2026, several wallets offer gasless USDC transfers on Ethereum. IronWallet deducts the fee directly from the USDC balance. Trust Wallet provides gas sponsorship for swaps with a $50 minimum. MetaMask offers a Gas Station feature with USDC as a supported gas token. Bitget Wallet uses EIP-7702 to pay gas in USDC across eight chains. Each implementation has different trade-offs on chain coverage and fee structure. How much does a gasless USDC transfer actually cost in 2026? A typical gasless USDC transfer through a paymaster costs slightly more than underlying ETH gas, since the paymaster takes a small premium. With Ethereum gas at 0.4 gwei in May 2026, a standard transfer costs $0.05 to $0.10 in ETH. A gasless version typically runs $0.20 to $0.50 in USDC. Can I use gasless USDC on Layer 2 networks like Base or Arbitrum? Yes. Circle Paymaster supports Arbitrum, Base, OP Mainnet, and Polygon PoS in addition to the Ethereum mainnet. Layer 2 fees are already low enough that gasless USDC on L2 is mostly a user-experience improvement, not a cost-saving measure. Users moving USDC frequently on L2 may find the convenience worth the small paymaster premium. Do I need to hold any ETH at all when using gasless USDC? No. A wallet with only USDC and zero ETH can complete gasless USDC transfers through any paymaster-supporting wallet. The paymaster covers all gas costs in the background. This makes USDC-only wallets fully functional for the first time in Ethereum's history, which removes the longstanding requirement to acquire ETH just to participate in on-chain activity. Disclaimer: This article is provided for informational purposes only. It is not offered or intended to be used as legal, tax, investment, financial, or other advice.











































