Stablecoins Handle Trillions as ETH and SOL Demand Shifts

Visa’s Onchain Analytics dashboard showed about $1.3 trillion in adjusted stablecoin volume and 230.3 million adjusted transactions over a 30-day window ending Aug. 27. The raw counts for that window were about $6.8 trillion and 1.75 billion transactions before adjustments. The adjusted dataset filters and labels addresses, counts only the largest stablecoin transfer within a transaction and excludes some high-activity unlabeled addresses. The data still includes exchanges, decentralized exchanges, lending, mint-and-burn and ramp activity. A retail-sized bucket in the dataset recorded about $7.6 billion across 158.8 million adjusted transactions under $250.

Some wallets and apps present stablecoin transfers without showing any ETH or SOL balance to the user. On-chain execution still requires native tokens: validators are paid in the chain’s native asset and some protocol fees are burned. Fee abstraction separates three roles that conventional wallets often combine: the user authorizes an action, an intermediary funds transaction execution, and the network charges a native fee. When an intermediary covers the fee, the visible need for users to hold a native token can disappear while the network-level requirement remains.

On Ethereum, the ERC-4337 account abstraction standard lets users submit operations that a bundler assembles into a transaction. A paymaster can cover an operation’s cost but must maintain a native-currency deposit at the EntryPoint contract. EntryPoint checks whether the deposit can cover the operation’s maximum cost and then charges the actual cost against it. The required deposit varies with gas limits, maximum fee settings, transaction volume and the buffer an operator maintains; there is no fixed balance that covers all cases. Some services present fees in USDC while actually fronting ETH for on-chain costs; examples include certain exchange and infrastructure payment flows that quote a token-denominated fee while an operator supplies the native gas.

Solana requires SOL for every transaction. The base fee is 5,000 lamports per signature, split between burning and the validator, and an optional priority fee can go to the validator. By default the fee payer is the first signer, but an application can designate a sponsor to sign and cover the SOL fee. Service providers have packaged that sponsorship primitive into offerings that either fully sponsor transaction fees or accept payment in SPL tokens such as USDC. In these flows the user sees an all-dollar transaction while SOL is paid on-chain by the sponsoring account.

Sponsorship concentrates native-token funding into managed payer accounts run by a smaller set of operators. Those operators must fund fee-payer balances, set pricing and recovery rules, and put in place abuse controls. They maintain native-currency buffers that vary with transaction volume and fee volatility. Operators recover costs through token billing, fiat billing, monthly charges or service margins.

Aggregate stablecoin volume alone does not equal native-token demand. On Solana, the number of signatures and any priority fees affect the SOL bill as much as raw transaction counts. On Ethereum, the protocol burns the base fee and pays the priority fee to validators; a high volume of stablecoin transfers can coexist with limited base-chain revenue capture if most fees are burned or if activity moves to cheaper execution environments. Determining which accounts actually supply native-fee liquidity requires payer-level on-chain analysis rather than high-level stablecoin volume figures.

End users can remain economically inside stablecoins while sponsors and service providers hold native-token exposure and keep funded fee-payer accounts. Public datasets currently do not measure the full impact of sponsorship and fee abstraction on aggregate ETH and SOL demand at the payer level.