In the deposit address model most ramps run, each new address takes two on-chain transactions before it returns anything. Here is what a ramp transaction costs end to end, and which part an operator can still change.
In the deposit address model most ramps run, each new address takes two on-chain transactions before it returns anything. Here is what a ramp transaction costs end to end, and which part an operator can still change.
Add a thousand customers and you add a thousand deposit addresses. In the standard model, each one takes two transactions before a cent of it reaches your hot wallet.
An engineer at a crypto exchange added his up. The answer came to roughly 270 million gas a month, at 50 deposits a day.
A fresh deposit address arrives empty. It holds the customer’s USDT but none of the native token needed to move it, so the platform funds the address first and sweeps it second. Both transactions are paid by the platform, on every deposit.
This is why volume does not rescue the number. Every extra customer brings an extra funding transaction with them, so the cost climbs at the same rate as the customer count while revenue per customer stays flat. That is one line on a longer bill.
Frax CEO Sam Kazemian quoted his JPMorgan banker word for word in 2024: “we have to close anyone’s account that we know their primary source of income/wealth is crypto. This is directly from the top from Jamie.”
n December 2025 JPMorgan froze accounts belonging to Blindpay and Kontigo over disputed transactions.
Licensing has not changed the pattern. 338 firms now hold full MiCA authorisation across 30 EEA markets, up from around 60 at the start of the year, and banks still decline them.
MiCA carries no provision requiring a bank to serve a licensed CASP, while the European Banking Authority continues to treat the sector as enhanced due diligence whatever an individual firm has cleared. Around 86 percent of European crypto companies report repeated account closures.
An operator carrying a 10 percent reserve has no lever to pull on any of this, which sends them back to the last row of the table.
TRON holds more than 51 percent of all USDT in circulation, so a ramp settling in USDT is almost certainly running there.
TRON charges by the address. One published comparison put a transfer to a brand new address at 27.25 TRX, against 13.4 TRX to one that had been received before, which puts every customer’s first transfer on the expensive path.
Justin Sun’s Proposal #104 post confirms the energy unit price was halved in August 2025, the largest cut in TRON’s history. The same post commits super representatives to quarterly fee reviews, so an operator’s per transaction cost gets decided at a governance vote they do not attend.
In the deposit address model most ramps run, each new address takes two on-chain transactions before it returns anything. Here is what a ramp transaction costs end to end, and which part an operator can still change.
Add a thousand customers and you add a thousand deposit addresses. In the standard model, each one takes two transactions before a cent of it reaches your hot wallet.
An engineer at a crypto exchange added his up. The answer came to roughly 270 million gas a month, at 50 deposits a day.
A fresh deposit address arrives empty. It holds the customer’s USDT but none of the native token needed to move it, so the platform funds the address first and sweeps it second. Both transactions are paid by the platform, on every deposit.
This is why volume does not rescue the number. Every extra customer brings an extra funding transaction with them, so the cost climbs at the same rate as the customer count while revenue per customer stays flat. That is one line on a longer bill.
Frax CEO Sam Kazemian quoted his JPMorgan banker word for word in 2024: “we have to close anyone’s account that we know their primary source of income/wealth is crypto. This is directly from the top from Jamie.”
In December 2025 JPMorgan froze accounts belonging to Blindpay and Kontigo over disputed transactions.
Licensing has not changed the pattern. 338 firms now hold full MiCA authorisation across 30 EEA markets, up from around 60 at the start of the year, and banks still decline them.
MiCA carries no provision requiring a bank to serve a licensed CASP, while the European Banking Authority continues to treat the sector as enhanced due diligence whatever an individual firm has cleared. Around 86 percent of European crypto companies report repeated account closures.
An operator carrying a 10 percent reserve has no lever to pull on any of this, which sends them back to the last row of the table.
TRON holds more than 51 percent of all USDT in circulation, so a ramp settling in USDT is almost certainly running there.
TRON charges by the address. One published comparison put a transfer to a brand new address at 27.25 TRX, against 13.4 TRX to one that had been received before, which puts every customer’s first transfer on the expensive path.
Justin Sun’s Proposal #104 post confirms the energy unit price was halved in August 2025, the largest cut in TRON’s history. The same post commits super representatives to quarterly fee reviews, so an operator’s per transaction cost gets decided at a governance vote they do not attend.
The engineer from the opening rebuilt his sweeping on CREATE2 with ERC-1167 minimal proxies and, in that one implementation, cut gas consumption by 84 percent
Small balances stay put until the amount clears the cost of moving it.
Fystack runs this as sweep tasks set on a USD value, with one task attached across many deposit wallets so a threshold change lands everywhere at once, and a gas tank keeping those wallets funded for the transfer.
// Create wallet with new sweep task
await sdk.createWallet({
name: 'User Payment Wallet',
walletType: WalletType.Standard,
sweepTaskParams: {
minTriggerValueUsd: '100.00',
destinationWalletId: '123e4567-e89b-12d3-a456-426614174001',
destinationType: 'internal_wallet'
}
})
Staking TRX or renting from an energy pool both avoid the burn. Guarda published a comparison of 11 USDT transfers costing $76.79 burned against $17.96 rented.
A TRON DAO ambassador puts the unit economics near 5.5 TRX per 100,000 energy, enough for two USDT transfers, with the deposit returned when the rental ends.
Rental turns the per transfer cost into a working capital decision:
A TRON withdrawal in Fystack with energy renting active: 2.97 TRX rented against 24.03 TRX burned, roughly $6.96 saved on one transfer.
Sweeping is the one cost line still open to a decision, and the spread between a naive build and a considered one runs wide enough to matter at ramp margins.
If deposit wallets are multiplying faster than revenue and nobody owns the sweeping bill, that number is worth pulling before the next volume step.
Fystack can help there: stablecoin custody and payment infra, self hosted, with threshold sweeping and TRON energy renting built in. The signing core, mpcium, is open source.
Crypto On Ramp Fees: Why More Volume Does Not Fix Your Margins was originally published in Coinmonks on Medium, where people are continuing the conversation by highlighting and responding to this story.
Crypto card monthly volume grew 106% annually from early 2023, driven almost entirely by programs that run on Visa. Mastercard is running two separate strategies at once: consumer card agents and a B2B settlement infrastructure acquisition. The card works as a bridge for existing merchants. For new ones with no entity and no processing history, protocols like x402 are the only option that works today
Crypto card monthly volume grew 106% annually from early 2023, driven almost entirely by programs that run on Visa. Mastercard is running two separate strategies at once: consumer card agents and a B2B settlement infrastructure acquisition. The card works as a bridge for existing merchants. For new ones with no entity and no processing history, protocols like x402 are the only option that works today
What Crypto Cards Reveal About the Future of Payments
Artemis Research reported in January 2026 that total crypto card monthly volume grew from $100 million in early 2023 to over $1.5 billion by late 2025, a 106% compound annual growth rate. Annualized, the market reached $18 billion — close to the $19 billion in peer-to-peer stablecoin transfers over the same period.
By July 2026, Paymentscan tracked $691.7 million in a single month from on-chain settled card programs alone, with $8.094 billion in cumulative volume across 128.7 million transactions and 467,000 wallet addresses.
The biggest program by monthly volume is RedotPay at roughly $380 million per month. KAST ranks third. Both run on Visa. Paymentscan’s July 2026 data shows Visa at 98.5% of on-chain crypto card volume. Mastercard at 1.5%.
Visa built its position by partnering early with infrastructure providers like Rain and Reap, which issue cards for many downstream programs at once. One Visa infrastructure deal covers many products. Mastercard built its crypto card presence through direct partnerships with centralized exchanges — Bybit, Revolut, Gemini — which ties its volume more closely to exchange trading cycles.
Both networks are extending card infrastructure to AI agents. Noah Levine at a16z noted in March 2026 that Mastercard Agent Pay is live for US cardholders and Visa’s Intelligent Commerce framework is in pilot. The Agentic Commerce Protocol, built by Stripe and OpenAI, has Etsy live with over one million Shopify merchants set to follow.
At the consumer layer, both networks are converging on the same approach. At the settlement layer, they are not. Mastercard announced in March 2026 that it would acquire BVNK for up to $1.8 billion, including $300 million in contingent payments. BVNK processes $30 billion annually for clients including Worldpay, Deel, and Rapyd. The stated goal: 24/7 stablecoin settlement for processors and acquirers, and stablecoin checkout within Mastercard’s payment gateway.
A crypto card does one job: it converts a wallet balance into what a merchant already accepts. The cardholder pays from USDC. The merchant receives a standard card transaction. Artemis confirmed that the vast majority of crypto card transactions today settle in fiat at transaction time, so the merchant sees only local currency regardless of which stablecoin the user holds.
That job has real reach. RedotPay users in Southeast Asia, LATAM, and Africa can pay at any Visa-accepting terminal without the merchant needing to know anything about crypto.
But the card cannot serve every merchant. Levine at a16z put it directly:
“Cards serve every merchant a processor can underwrite. Stablecoins serve every merchant a processor cannot.”
A developer who builds an API tool in a weekend has no legal entity, no website, and no chargeback history — a profile that is very difficult to underwrite. Levine’s conclusion: “These merchants will not be choosing stablecoins over cards. They will be choosing stablecoins over nothing.”
In March 2026, a marketplace at mpp.dev opened with over 60 services built for AI agents: SEC filing search charges per query, image generation at fractions of a cent, physical letters printed and mailed from a document and address. The protocol powering it is MPP (Machine Payments Protocol), built by Stripe and Tempo, which lets agents pay using cards, stablecoins, or Lightning in a single HTTP request.
In its first week, 894 agents made 31,000 transactions at prices from $0.003 to $35 per request, according to a16z. No checkout page. Pricing embedded in the HTTP response. The agent reads the schema, pays, receives output.
Two protocols now make this model possible at the infrastructure level. x402 embeds stablecoin payments directly in HTTP requests with no merchant account or processor onboarding. MPP supports cards, stablecoins, and Lightning in the same request, with the mpp.dev marketplace as its live implementation. As a16z noted, “x402 and MPP each take a different approach, but both embed payments directly into HTTP requests.”
MoonPay’s PayBox handles the full stack for agents — MPC key sharding in a trusted execution environment, policy limits before any transaction, virtual cards scoped per merchant for fiat rails when needed.
The card worked because neither side had to change anything. As Levine, a16z, wrote: “The next generation of merchants won’t have storefronts. They’ll have endpoints.” The card serves that well for the merchants that already exist. The infrastructure being built now is for the ones that do not.
Fystack is an enterprise-grade, self-hosted MPC custody platform for fintech teams and crypto businesses. The core signing infrastructure, mpcium, is open-source. Fystack supports multi-chain wallet operations across TRON, ETH, BNB, Solana, Polygon, and more, with a policy engine that enforces spend rules before any signing happens.
If you are building payment infrastructure that involves automated signing, wallet custody, or agent payment flows, Fystack has the full product overview. The policy engine source is on GitHub.
What Crypto Cards Reveal About the Future of Payments was originally published in Coinmonks on Medium, where people are continuing the conversation by highlighting and responding to this story.
Ripple has entered a partnership with Florida Athletics that will bring optional XRP and RLUSD payment choices into parts of the athletics program’s ticketing and merchandise experience.
It is a nice mainstream-facing win for Ripple, partly because sports partnerships are easy for normal people to understand. This is not some abstract infrastructure integration buried in a developer doc. It is payments, fans, tickets, concessions, and college athletics.
That said, the wording needs to stay careful.
XRP is not becoming a mandatory payment method for university purchases. This is not a blanket campus-wide crypto rollout. The partnership is tied to Florida Athletics, and the payment options are being introduced alongside existing fiat routes.
For more details, visit the official Ripple platform.
Crypto companies have used sports partnerships for years, with mixed results.
Some were splashy branding exercises that aged badly. Others helped put crypto products in front of large mainstream audiences. The difference usually comes down to whether the partnership has practical use beyond a logo.
This Ripple deal has a clearer payments angle.
If fans can use XRP or RLUSD for certain ticketing or merchandise purchases, the partnership becomes more than brand exposure. It gives Ripple a real-world setting to show how digital assets might work in consumer payments.
That is more interesting than a banner ad.
The inclusion of both XRP and RLUSD is notable.
XRP carries the long-running Ripple payments narrative. It is liquid, widely recognized, and central to Ripple’s public identity. RLUSD, as a dollar-linked stablecoin, gives users a less volatile option for actual spending.
That distinction matters.
Most consumers do not want to think about price volatility when buying a ticket or a hoodie. Stablecoins can make crypto payments feel more familiar because the unit of account stays closer to the dollar.
XRP gives the partnership the ecosystem hook. RLUSD may make the checkout experience more practical.
Ripple is also set to support Web3 education initiatives connected to the athletics program.
That part is easy to overlook, but it matters. Payments are one side of adoption. Understanding is the other. If students and staff are being introduced to digital assets through workshops or education programs, the partnership becomes a broader crypto literacy effort.
Of course, education does not automatically create adoption.
But it can make the integration feel less like a novelty and more like part of a longer-term relationship.
The strongest version of this story is also the most precise one.
Ripple has partnered with Florida Athletics. The deal introduces optional digital asset payment rails in selected athletics contexts. It also includes education support.
That is enough.
It does not need to be stretched into a claim that Florida as a whole is adopting XRP, or that every student will suddenly use RLUSD. Those claims would go beyond what the partnership supports.
For XRP holders, the partnership is useful because it gives the ecosystem another practical payments example.
It is not a price forecast. It is not a guarantee of transaction volume. It is not proof that XRP will become the default payment asset for sports.
But it does show Ripple continuing to push into public-facing payments relationships.
That is exactly the kind of story XRP’s community tends to care about: less courtroom drama, more actual usage narrative.
This article draws on Ripple’s Florida Athletics partnership materials and related public comments.
This article was written by the News Desk and edited by Samuel Rae.
This report is based on information released by Ripple. at Ripple
Europe is no longer building one digital-money system.
It is building several systems at once.
MiCA-native euro stablecoins are moving into mainstream fintech applications. The European Central Bank is preparing the infrastructure for tokenised transactions to settle in central bank money. And the digital euro is being designed as a public payment rail with pan-European reach.
These developments are often discussed separately.
That is a mistake.
The strategic question for founders is not whether stablecoins, tokenised finance or the digital euro will “win.” It is how these systems will work together and which companies will own the interoperability layer between them.
Revolut’s rollout of EURR provides the clearest live example.
A regulated issuer, a major fintech distribution platform, and public blockchain infrastructure are being combined to create a euro-denominated on-chain asset for customers who may never consider themselves crypto users.
That is the important shift.
Stablecoins are no longer asking for permission to sit beside payments. They are being designed into the payment experience itself.
The next competitive advantage in European payments will not be choosing one rail. It will be making several rails work as one experience.
On 7 August 2026, Revolut announced EURR, its first euro-denominated stablecoin, issued by Bridge and initially launched on Ethereum as part of a phased rollout. Revolut said testing would begin with eligible customers in Denmark, Poland and Portugal.
The rollout is deliberately limited. Bridge’s reserve dashboard showed EURR circulation of approximately €369 on 27 August, with reserves denominated in euros and held in the European Union. That figure should not be mistaken for a measure of Revolut’s broader customer reach. It is better understood as evidence of a controlled early-stage launch rather than a mass-market liquidity event.
The architecture is more important than the initial supply.
EURR is issued by Bridge Building S.A., which manages the issuance, reserves, and redemption process. Revolut provides the customer experience and distribution. Ethereum and Polygon provide public blockchain rails through which the token can move.
Revolut describes EURR as a way for eligible customers to move between euros, crypto, external wallets, and supported blockchain networks without first converting into a US-dollar stablecoin. Each EURR is designed to maintain a value of €1.00, and holders have the right to redeem against the issuer at par value, subject to applicable terms.
This is a meaningful product decision.
A euro user should not have to accept dollar exposure simply because the most liquid stablecoins happen to be dollar-denominated. A European fintech should not have to choose between the familiarity of bank money and the programmability of blockchain money.
EURR attempts to place those two experiences in the same product.
That does not make the product risk-free. It creates a new set of questions around reserve transparency, redemption capacity, chain liquidity, wallet controls and the responsibilities of the issuer, distributor and platform. But these are precisely the questions that arise when crypto becomes financial infrastructure rather than a speculative side product.
The stablecoin market is already large enough for the debate to move beyond whether the technology works. Circle reported USDC circulation of around $73.6 billion on 24 August 2026. Circle has also described stablecoin payments as a growing area of digital commerce, with stablecoin-enabled payment volume exceeding $390 billion during 2025.
These figures matter, but they do not tell the whole story.
A stablecoin can have deep liquidity and still fail to become a payment product. Payment adoption requires distribution, compliant onboarding, reliable redemption, merchant acceptance, treasury tools, FX conversion, and a clear answer when something goes wrong.
That is why the Revolut model is strategically important. It places the stablecoin inside an established customer relationship instead of asking users to discover a new wallet, acquire a new asset, and understand a new blockchain before they can make a payment.
The blockchain becomes part of the infrastructure.
The user experience remains recognisably fintech.
For founders, this is the distinction between technology adoption and product adoption. Customers do not necessarily want blockchain. They want faster settlement, lower friction, easier cross-border movement and better control over their money.
Stablecoins can provide those benefits, but only when the infrastructure disappears into a trusted experience.
The Bank for International Settlements has offered an important counterweight to the enthusiasm. Its 2026 Annual Economic Report argues that stablecoins show tokenisation’s potential to support faster and programmable payments, but that current designs fall short of important monetary properties, including singleness, redeemability and interoperability across ledgers.
That criticism should not be dismissed as opposition to innovation.
It identifies the commercial work still to be done.
A stablecoin payment system cannot be judged only by transaction speed. It must also be judged by the quality of its money, the reliability of redemption, the strength of its compliance model, and its ability to interoperate with other forms of money.
While EURR brings programmable euro liquidity closer to retail payments, the ECB is building the institutional layer underneath tokenised finance.
In his speech “From vision to delivery: building Europe’s tokenised financial market,” ECB Executive Board member Piero Cipollone described two complementary initiatives: Pontes and Appia.
His description of Pontes is direct:
“Pontes will turn our commitment to provide central bank money for settling tokenised transactions into an operational service.”
Pontes is designed to connect market-operated DLT platforms with the Eurosystem’s TARGET Services. The cash leg of tokenised transactions would settle in central-bank money, while synchronisation would support delivery-versus-payment and other transactions requiring all-or-nothing settlement.
That is an important distinction.
Many discussions about tokenisation focus on the asset being tokenised: a bond, fund, deposit or other financial instrument. The harder institutional question is what money settles the transaction and how participants can trust that settlement.
The ECB is attempting to answer that question by placing central-bank money at the centre of the system.
The ECB has stated that Pontes is scheduled to become an operational service in the third quarter of 2026. The planned roadmap includes an expansion of operating hours to 22.5 hours per business day and, by mid-2028, a 24/7 service with greater programmability, resilience and multi-currency capability.
Appia addresses the wider ecosystem.
It is intended to develop the architecture, standards and governance for an integrated European tokenised financial market. Its work covers asset interoperability, collateral management, cross-border connectivity, tokenised central-bank money and the legal and regulatory foundations of the ecosystem.
Cipollone summarised the relationship between the two initiatives in practical terms:
“Pontes builds bridges by offering digital finance a safe settlement asset and by making private settlement assets mutually convertible.”
That sentence deserves attention.
It means the ECB does not necessarily view stablecoins, tokenised deposits and other private settlement assets as irrelevant. Instead, the objective is to create a common anchor into which those assets can be converted and against which they can settle.
This is not a battle between public and private money in the simplistic sense.
It is a question of how private innovation can operate within a system that preserves settlement confidence, monetary sovereignty and market integration.
Tokenisation is often presented as a technology upgrade. In reality, it is a market-structure decision.
The benefits become meaningful only when tokenisation changes how assets are issued, transferred, financed, collateralised or settled. A tokenised bond that still relies on fragmented processes, manual reconciliation and limited operating hours may be digitally represented without being operationally transformed.
The ECB’s Pontes and Appia programmes are significant because they focus on the full chain rather than the token alone.
The question is not simply whether a security can exist on a DLT platform. It is whether the platform can connect to money, collateral, custody, legal ownership, liquidity and cross-border settlement.
That is where interoperability becomes decisive.
A closed tokenised market may create efficiency for one institution while increasing fragmentation across the wider system. An interoperable market can allow tokenised assets and settlement assets to move between platforms without forcing participants into one private ecosystem.
Europe has a particular reason to care about this. Its capital markets are already divided across jurisdictions, infrastructures and national systems. If tokenisation produces another generation of incompatible silos, it will reproduce the problem in digital form.
If it creates common standards and trusted settlement connections, it could help reduce that fragmentation.
For fintech and crypto infrastructure founders, this changes the strategic question. It is no longer enough to ask:
“Can we issue or transfer this asset on-chain?”
The better question is:
“What does this asset need to connect to to become commercially useful at scale?”
That may include a stablecoin, tokenised deposit, central-bank money, a securities settlement system, a collateral platform, an institutional custodian or a regulated payment provider.
The winning infrastructure will not be the one with the most impressive isolated technology. It will be the one that can connect the greatest number of trusted financial functions without creating additional operational risk.
The digital euro is often placed in direct competition with stablecoins.
That framing is too narrow.
The digital euro is being designed to solve a different problem: how to provide a sovereign, pan-European digital payment instrument that is widely accessible, interoperable and resilient.
The ECB’s digital-euro FAQs describe a system intended for physical shops, online commerce and person-to-person payments. The design includes both online and offline functionality. The ECB says merchants would be able to receive payments instantly without additional costs, including when there is no internet connection.
Basic use would be free for consumers, while the Eurosystem would not charge or benefit from digital-euro transaction fees. The proposed design also includes holding limits, intended to reduce the risk of excessive deposit outflows from banks during periods of stress.
These are not minor design details.
They reveal the policy priorities behind the project:
• Ubiquity rather than speculation.
• Resilience rather than maximum balance-sheet flexibility.
• Public access rather than dependence on one private issuer.
• Integration with existing payment providers rather than a separate consumer silo.
The digital euro is not yet a live retail payment product. The ECB states that if EU lawmakers adopt the necessary legislation during 2026, a first issuance could potentially take place in 2029. The ECB’s final decision on whether to issue it, and when, will come after the legislative process is completed.
That timeline does not make it irrelevant today.
Large payment products are designed years before they become widely available. Product architecture, merchant acceptance, compliance processes and customer journeys all require preparation.
The digital euro will also shape competitive expectations before it reaches full scale. If customers and merchants are promised instant, low-cost and widely accepted euro payments through a public rail, private providers will be judged against that baseline.
The digital euro is therefore more about sovereignty and ubiquity than programmability alone.
Stablecoins may be better suited to certain on-chain, cross-border and platform-native use cases. The digital euro may be better suited to public reach, monetary confidence and everyday euro payments.
Treating them as identical would obscure their respective strengths.
The three developments now fit together.
EURR represents the retail and crypto-native layer: a regulated euro token that can move on public chains and connect to a mainstream fintech interface.
Pontes represents the institutional settlement layer: tokenised transactions connecting to central-bank money and the Eurosystem’s existing infrastructure.
Appia represents the broader architecture: standards, governance, collateral, cross-border connectivity and a blueprint for an integrated tokenised financial ecosystem.
The digital euro represents the public payment layer: a potential pan-European instrument designed around access, acceptance, resilience and low-cost use.
These systems will compete in some areas.
They will also depend on one another.
A stablecoin may need bank rails for entry and exit. A tokenised security may need central-bank money for settlement. A digital-euro wallet may need private providers for distribution and user experience. An institutional platform may need multiple settlement assets to serve different markets and transaction types.
The architecture will be plural.
That creates a clear decision for founders.
Do you build a closed product around one rail and hope the market conforms to it? Or do you design a modular product that can route value across several rails while preserving one coherent customer experience?
The first option may be faster in the short term.
The second is more likely to survive changes in regulation, liquidity, infrastructure and user behaviour.
I have spent more than 25 years working at the intersection of marketing, strategy and regulation. That has included contributing to Malta’s pioneering DLT framework, launching Moneybase as Malta’s first neobank, and leading global marketing and strategy for a Layer-1 connecting banking infrastructure with Web3 across Europe, Asia and beyond.
Across regulated finance and Web3, I have seen a recurring pattern: single-rail thinking creates hard limits.
A company may have strong technology but weak distribution. A product may have liquidity but limited regulatory access. A platform may have community momentum but no clear path to institutional trust.
The limitations usually appear at the boundaries between systems.
That is why, if I were designing a European payments or digital-finance product today, I would make interoperability a board-level decision from the beginning.
I would treat MiCA-native euro stablecoins as the programmable euro layer for appropriate consumer, merchant, treasury and cross-border use cases.
I would design the product so that digital-euro functionality could eventually be embedded through existing wallets, accounts and payment channels.
I would map how tokenised assets, deposits and collateral could connect to Pontes and the wider Appia architecture as those initiatives develop.
And I would preserve the ability to connect all of this to cards, instant payments and legacy bank infrastructure.
Not because every product needs to use every rail immediately.
That would be inefficient and, in some cases, unnecessary.
The point is to avoid building a product that cannot connect to the rails your customers, partners, and regulators will eventually expect.
Interoperability should not be an integration backlog. It should be part of the original business model.
Europe’s digital-money future will not be defined by one winner replacing everything that came before.
It will be defined by the interaction between private innovation and public infrastructure.
MiCA-native euro stablecoins can provide programmability and on-chain flexibility. Tokenised central-bank money can provide institutional settlement confidence. The digital euro can provide public reach and a common European payment baseline.
The commercial opportunity lies between these layers.
Founders who understand this will build products that hide complexity from customers while managing it rigorously underneath. They will make compliance part of their market positioning, not merely a legal obligation.
They will treat trust, redemption, interoperability, and resilience as product features.
The market is moving beyond the question of whether crypto belongs in finance.
The more important question is whether finance can become interoperable enough to use crypto-native rails without sacrificing trust.
That is the opportunity in front of European fintech and Web3 leaders.
Not to choose one monetary regime. To build for the stack.
I’ve spent more than 25 years at the intersection of marketing, strategy, and regulation, helping design Malta’s pioneering DLT framework, launching Malta’s first neobank, and leading global marketing and strategy for a Layer‑1 that bridges traditional banking infrastructure with Web3 rails across Europe, Asia, and beyond.
My focus is simple: turn complex, high‑stakes environments like Europe’s evolving digital‑money stack into clear narratives and go‑to‑market strategies that boards, regulators, institutions, and communities can align behind.
If you are building on these rails, your biggest risk is not that you choose the “wrong” technology. It is that you design for too little of the stack.
EURR, Tokenised Finance and the Digital Euro: How Europe’s New Money Stack Will Reshape Payments was originally published in Coinmonks on Medium, where people are continuing the conversation by highlighting and responding to this story.
A market maker’s job looks simple from the outside: keep buy and sell orders in the book and update them as the market moves.
What is less visible is everything that has to happen before those orders can be updated correctly. The strategy needs to receive the latest market data, decide how its prices should change, send instructions to the exchange and learn what happened to its previous orders. All of that can happen through different connections with different speed, delivery and recovery characteristics.
So when a market maker evaluates an exchange, “Does it have an API?” — is only the starting point. The more useful question is whether the entire path from a market event to the next order is reliable enough to trade on.
A simplified market-making cycle looks like this:
market event → order-book update → pricing decision → order entry → execution → inventory update → next order
Every step depends on the one before it. If market data is late or incomplete, the pricing decision is based on the wrong market. If an order reaches the venue later than expected, the price may already be outdated. If a fill is not reflected quickly enough, the strategy can continue quoting without an accurate view of its inventory.
That is why connectivity is part of the trading system itself, not simply the technical work required to connect the system to an exchange.
The stack can be simplified into 3 main layers:
Different venues may expose these functions through WebSocket, FIX, REST, drop-copy feeds or other channels. What matters is not having the largest number of protocols, but using the right channel for each part of the trading cycle.
Raw latency gets most of the attention, but synchronization can be just as important.
Consider an incremental order-book feed. If one delta is dropped and the consumer misses the gap, later updates can continue arriving normally. The connection still looks healthy, but the local book is now being updated from the wrong state.
That creates one of the most dangerous situations for a market maker: the strategy keeps quoting, but the market it is quoting against is no longer the market the venue sees.
Recovery therefore has to be part of the design. The system needs to detect missing sequences, stop relying on corrupted state, retrieve a valid snapshot and rebuild the book before normal quoting resumes.
There is no single architecture used by every venue. Current institutional offerings show several ways to separate market data, order entry and account or execution events.
WhiteBIT Market Making Program
Bybit Market Maker Program
The comparison is therefore broader than the headline maker rebate. A market maker is also choosing the qualification model, available infrastructure and the operating conditions under which its strategy will have to maintain liquidity.
For a market maker choosing a venue, a basic API checklist does not go far enough. The better questions are:
How does market data reach us? What happens if an update is missed? How do we send and cancel orders? How do we learn that an order has been filled? How do sessions recover after a disconnect? How quickly can we rebuild a trustworthy state?
Those questions connect infrastructure directly to the job the market maker is trying to do: keep orders in the market while prices, executions and inventory are constantly changing.
A strong connectivity stack does not eliminate trading risk. It gives the market maker the information and execution channels needed to understand that risk fast enough to act on it.
Disclaimer: This is not financial or investment advice. DYOR before making any decisions. Use at your own risk.
From Market Data to Execution: How Market Making Works was originally published in Coinmonks on Medium, where people are continuing the conversation by highlighting and responding to this story.
AI agents initiated 3.3 million USDC in payments over x402 on Solana within a single week, highlighting a growing machine-to-machine payment use case for stablecoins.
The x402 protocol uses the HTTP 402 “Payment Required” status code to enable internet-native payments for APIs, data, and digital resources. According to protocol analytics, more than 99.99% of agentic transaction volume on x402 is denominated in USDC.
That makes this a very specific kind of adoption.
It is not mainstream retail usage. It is not proof that ordinary consumers are paying with Solana stablecoins at scale. It is a machine-to-machine micropayment story involving AI agents, APIs, and USDC settlement.
That may be even more interesting.
AI agents need ways to pay for resources.
If autonomous software requests data, uses APIs, accesses compute, or performs tasks across services, it may need to send small payments quickly. Traditional payment systems are not built for high-volume, low-value machine transactions.
Stablecoins fit naturally into that gap.
They can settle quickly, support programmable flows, and move across internet infrastructure without relying on card networks for every microtransaction.
Solana adds low fees and fast execution, which helps when payments are small and frequent.
HTTP 402 has existed for years as a “Payment Required” status code, but it was never widely used in mainstream web payments.
x402 attempts to make that idea practical for crypto-native payments.
A service can request payment, an agent can pay, and the transaction can unlock access to the requested resource. That creates a cleaner flow for machine-to-machine commerce.
If this works, agents could pay for data, APIs, storage, inference, and other digital services without human intervention for every transaction.
That is the broader idea behind agentic payments.
The fact that more than 99.99% of agentic x402 volume is denominated in USDC says a lot.
AI agents do not need volatile exposure for routine payments. They need a stable unit of account. USDC gives the system dollar-denominated settlement while still using blockchain rails.
That makes stablecoins more practical than SOL itself for many payment flows.
SOL provides the network environment. USDC provides the payment asset.
That separation is important for understanding Solana’s role.
The 3.3 million USDC figure is meaningful, but it should be framed properly.
This does not mean millions of consumers are using x402. It does not mean AI agents have become mainstream economic actors. It shows measurable activity in a specific protocol category.
The activity is still early.
But it points toward one of the more credible intersections between AI and crypto: autonomous software paying for digital resources.
That use case is more practical than many vague AI-token narratives.
The next thing to watch is whether x402 activity keeps growing.
If more services support the payment flow and more agents use it, Solana could become a meaningful settlement layer for machine payments. If activity remains concentrated in a small set of experiments, the story may stay niche.
For now, the signal is clear.
AI agents are already moving USDC over Solana through x402, and the payments are tied to actual internet resource access rather than pure speculation.
That gives Solana a useful role in the emerging agentic payment stack.
This article is based on x402 protocol analytics and public Solana payment data.
This article was written by the News Desk and edited by Samuel Rae.
This report is based on information released in disclosures at primary source documentation.
NEAR has launched a staking-based payment model for NEAR AI, giving users a way to lock NEAR tokens and receive monthly compute credits instead of paying through traditional cloud billing or credit-card rails.
According to the validated notes, the system gives users access to 43 hosted AI models, including models from OpenAI, Anthropic, and Google. The key detail is that tokens are not consumed. Users lock NEAR and receive compute credits proportional to their stake size.
That makes this more interesting than a simple payment integration.
NEAR is trying to tie token utility directly to AI usage. Instead of asking users to buy a token for speculative reasons, the model gives the token a role in accessing compute.
The question is whether users will actually adopt it at scale. But as a design direction, it is worth watching.
For more details, visit the official Near platform.
AI usage has a very real payment problem.
Users and developers often pay through cloud accounts, credit cards, subscriptions, invoices, or platform credits. That works fine in traditional software, but it does not map neatly to autonomous agents, crypto-native users, or applications that want programmable access without conventional billing.
NEAR’s model tries to solve that by using staking as the payment layer.
Instead of spending tokens directly, users lock them. The locked stake determines monthly compute credits. That creates a different relationship between token ownership and product access.
The user is not simply paying a fee. They are committing capital to the network and receiving AI compute access as a benefit.
That could make sense for developers, agent builders, or users who already hold NEAR and want a reason to use it beyond staking yield or governance.
The fact that tokens are not consumed is important.
If the model required users to spend NEAR every time they used an AI model, it would look more like a normal pay-per-use system. Locking tokens changes the economics because users retain ownership while receiving credits.
That may make the system feel less expensive for users, though there is still an opportunity cost. Locked tokens cannot be freely used elsewhere while committed, and their market value can move.
The model therefore resembles a membership or access system backed by staking.
That is a different kind of token utility, and crypto networks have spent years searching for utility models that do not rely only on speculation or inflationary rewards.
The autonomous-agent angle is where this gets more forward-looking.
If AI agents are going to operate independently, call models, use tools, pay for services, and make decisions in software environments, they need payment rails that are programmable. Traditional billing can work for human-managed accounts, but it becomes clunky when software agents are expected to act continuously.
Crypto rails may be useful there.
A staking-based compute model could let an agent or developer environment access AI resources based on locked capital rather than repeated card payments or centralized credentials.
That is still early. There are many open questions around permissions, safety, abuse controls, cost predictability, and user experience. But the direction fits NEAR’s broader focus on AI and agent infrastructure.
The caution is simple: launch is not the same as adoption.
NEAR may have a clever compute-credit model, but the market still needs to show whether users prefer it. Developers will compare it with direct API billing, cloud credits, open-source models, enterprise contracts, and other crypto-native compute markets.
The model also needs to be clear.
How many credits does a given stake generate?
Which models are available at what cost?
How predictable are credits over time?
Can teams build around it without worrying about token volatility?
Does the system attract users who were not already in the NEAR ecosystem?
Those questions will determine whether this becomes a real use case or a niche experiment.
What makes the NEAR AI payment model interesting is that it gives the token a practical role.
Crypto has often struggled to explain why a token needs to exist beyond governance, gas, staking, or incentives. Linking token staking to AI compute access gives NEAR a more concrete utility narrative.
That does not guarantee success. But it is more useful than vague AI branding.
If users can lock NEAR and receive compute credits for models they actually use, then the token becomes part of a product loop. That is exactly what many networks are trying to build: token demand connected to real usage rather than just market cycles.
NEAR’s staking-based compute payments are still early, but they point toward a crypto-AI model that is more practical than most of the hype around the sector.
This article is based on NEAR AI materials describing staking-based compute credits and model access.
This article was written by the News Desk and edited by Samuel Rae.
This report is based on information released by Near. at Near
Ripple has been named to CNBC and Statista’s World’s Top Fintech Companies list for the fourth consecutive year, giving the company another mainstream recognition point as it expands across payments, custody, tokenization, and digital asset infrastructure.
The recognition is tied to Ripple as a company, not to direct XRP token adoption. That distinction matters.
CNBC and Statista evaluate fintech firms across categories and performance indicators. Ripple appeared in the Digital Assets category, reflecting its enterprise business lines and broader role in blockchain-based financial infrastructure.
For XRP holders, the headline is positive for brand visibility, but it should not be turned into something it is not. This is not a bank adopting XRP. It is not a new payment corridor. It is not an endorsement of the token by CNBC or Statista.
It is a corporate fintech recognition story, and that still has value.
Crypto companies often live in two worlds.
Inside crypto, they are judged by token prices, regulatory battles, ecosystem activity, wallets, developers, and exchange liquidity. Outside crypto, they are judged more like fintech companies: revenue, customers, products, compliance, partnerships, and market position.
Ripple has always sat between those worlds.
It has the XRP Ledger connection and a large token community, but it also operates as an enterprise payments and digital asset infrastructure company. That means mainstream fintech recognition can matter for how banks, payment companies, investors, and partners view the business.
Being included on a CNBC and Statista list does not change Ripple’s fundamentals overnight, but it helps reinforce that the company is not viewed only through the lens of crypto speculation.
That is useful for a firm trying to sell services to institutions.
Ripple is often reduced to one story depending on who is talking.
For some, it is the XRP company. For others, it is a payments firm. For others, it is a regulatory case study. More recently, Ripple has been pushing further into custody, stablecoins, tokenization, and prime-brokerage-style digital asset services.
That broader footprint is likely part of why the company continues to appear in fintech rankings.
Enterprise customers do not usually care about crypto Twitter narratives. They care about whether a provider can deliver reliable infrastructure, handle compliance, support settlement, and operate across jurisdictions.
Ripple’s ability to remain visible in mainstream fintech circles may help it keep those conversations open.
Still, the market should keep the token connection in proportion.
Corporate recognition may improve Ripple’s brand, but XRP demand depends on actual network usage, liquidity, product design, and market conditions. A fintech list does not automatically create transaction volume.
The fact that CNBC and Statista have a Digital Assets category also says something about the market.
Crypto companies are no longer being treated only as speculative startups. The stronger firms are increasingly being evaluated alongside other fintech infrastructure providers. That means higher standards, more competition, and more focus on business durability.
Ripple appearing for a fourth straight year suggests continuity.
That matters because crypto businesses often rise and fall quickly. Exchanges, lenders, token projects, and infrastructure companies can go from market leaders to distressed names in a single cycle. Staying relevant across multiple years is harder than it looks.
For Ripple, the recognition supports the idea that it remains one of the more established digital asset firms.
This is the key caveat.
The list does not mean CNBC or Statista endorses XRP. It does not mean institutions on the list are using XRP. It does not mean Ripple’s enterprise progress automatically translates into token price appreciation.
That distinction is especially important because XRP headlines can move quickly through the market.
A corporate milestone can become a token narrative before the details are understood. Traders may treat any Ripple recognition as an XRP catalyst, but the actual connection is more indirect.
The realistic read is that Ripple’s corporate visibility remains strong, and that can support long-term business development. Whether that eventually benefits XRP depends on how Ripple’s products use the ledger, the token, or related infrastructure.
Ripple’s inclusion on the list is not the biggest story in crypto today, but it fits the company’s broader direction.
Ripple wants to be seen as a serious fintech infrastructure provider, not just a crypto brand. Payments, custody, tokenization, stablecoins, and institutional digital asset services all sit inside that strategy.
Mainstream recognition helps with that positioning.
It gives Ripple another credibility point when speaking to banks, payment providers, investors, and regulators. It also shows that digital asset companies can remain part of the fintech conversation even after years of market volatility and regulatory pressure.
For XRP holders, the takeaway is measured.
Ripple’s brand is still strong enough to appear in mainstream fintech rankings. That is positive. But token demand still has to be earned through real network activity and product usage.
The list helps the company’s institutional image. It does not settle the XRP adoption question by itself.
This article is based on CNBC and Statista’s World’s Top Fintech Companies list.
This article was written by the News Desk and edited by Samuel Rae.
This report is based on information released in disclosures at primary source documentation.
Ripple MiCA Authorization Opens A Wider European Payments Lane
Ripple has secured full MiCA authorization in Europe, giving the company a clearer regulatory path to expand crypto-enabled payment services across EU and EEA markets.
The authorization applies to Ripple’s corporate payment entity and allows compliant operations under the European Union’s Markets in Crypto-Assets framework. That is an important distinction. This is not a blanket regulatory endorsement of XRP trading itself. It is a licensing milestone for Ripple’s business activities under MiCA.
Still, the development matters for XRP watchers because Ripple’s payments business remains central to the token’s broader narrative.
If Ripple can operate more cleanly across Europe, it may strengthen the company’s ability to work with banks, payment firms, fintechs, and institutional clients in one of the world’s most important regulatory blocs.
MiCA has become one of the most important crypto regulatory frameworks in the world.
Instead of forcing firms to deal with fragmented rules across every European country, MiCA creates a more unified regime for crypto-asset service providers. That can make it easier for licensed firms to scale across member states while still meeting compliance obligations.
For Ripple, this is particularly relevant.
The company has spent years positioning itself as a payments and settlement infrastructure provider. Its core pitch has always depended on working with regulated institutions, not simply appealing to retail token traders.
A MiCA authorization can therefore make business conversations easier.
Banks and payment companies are more likely to work with a crypto firm when the regulatory status is clear. Compliance teams can point to a recognized framework. Legal departments can assess obligations more directly. Operational partners can understand the boundaries of what is permitted.
That is exactly the kind of clarity Ripple needs if it wants to expand deeper into European payment corridors.
The XRP market will naturally pay attention to the authorization, but the connection needs to be framed carefully.
Ripple’s regulatory progress can improve the environment around its payment business. That may support the broader XRP narrative if the company’s products continue to involve XRP-related liquidity or settlement tools.
But the authorization itself does not mean regulators have approved XRP as an investment product. It does not mean all XRP trading has received blanket clearance across Europe. It does not guarantee token demand.
The strongest read is more measured: Ripple has gained a clearer legal route for its European crypto-asset service operations.
That matters because institutional adoption depends on trust, licensing, and compliance. XRP’s long-term utility case is stronger when Ripple can operate in major markets without constant regulatory uncertainty.
Still, token price impact depends on actual usage, liquidity, and product adoption.
Ripple’s MiCA approval also fits into a wider industry trend.
Crypto companies are racing to secure European regulatory footing because MiCA offers something the US still lacks: a comprehensive digital asset rulebook. The framework is not light-touch, but it is relatively clear.
That makes Europe attractive for firms that want certainty.
Exchanges, custodians, stablecoin issuers, payment firms, and infrastructure providers all need to decide where to base operations and how to structure services. MiCA creates a pathway, but it also raises the bar.
Firms that secure authorization early may gain an advantage.
They can approach institutional clients with a stronger compliance story while rivals are still working through approvals. For Ripple, that could be meaningful given the company’s focus on cross-border payments.
Regulatory approval is useful, but it is not the finish line.
Ripple still needs to turn authorization into real payment volume, partnerships, and institutional usage. Licenses create permission. They do not automatically create demand.
The next thing to watch is whether Ripple uses the MiCA approval to announce new European clients, expanded corridors, or deeper integration with banks and payment providers.
That is where the story becomes more important for XRP holders.
If authorization leads to more payment activity, the market may view it as a practical step forward. If it remains mostly a compliance milestone, the immediate effect may be limited.
Either way, it is a positive development for Ripple’s European strategy.
Crypto markets have spent years asking for regulatory clarity. In Europe, that clarity is now becoming operational. Ripple’s MiCA authorization shows how larger crypto companies are beginning to use that framework to expand regulated services rather than wait for perfect global rules.
For Ripple, Europe just became a more navigable market.
This article is based on Ripple and ESMA materials.
This article was written by the News Desk and edited by Samuel Rae.
This report is based on information released in official primary source disclosures at primary source documentation.
Visa Stablecoin Treasury Engine Pushes Settlement Deeper Into Institutional Finance
Visa has launched a stablecoin treasury engine for financial institutions, marking another step in the shift from crypto payment experiments to real institutional settlement infrastructure.
The service is designed to let financial institutions settle merchant network balances using stablecoins such as USDC and EURC. That matters because Visa is not pitching this as a retail crypto wallet or a speculative trading product. It is a treasury and settlement tool for institutions already operating inside the payments system.
The difference is important.
Stablecoins have proven useful in crypto markets for years, but the more interesting development is their movement into traditional financial plumbing. If banks, payment firms, and merchants can settle balances using stablecoins behind the scenes, blockchain-based dollars and euros become less of a crypto-native novelty and more of an operational settlement layer.
Visa has been testing stablecoin settlement for years, but the market pays closer attention when those tests begin moving toward operational products.
The reason is simple: Visa sits at the centre of global payments. When it experiments with stablecoins, it does not need to convince the world that payments exist. It is trying to make settlement faster, more flexible, and more programmable inside an existing financial network.
That is very different from a startup trying to replace the card system.
A stablecoin treasury engine can help financial institutions manage balances in digital dollars or euros while still operating within a familiar settlement environment. For institutions, that can make stablecoin adoption feel less like a crypto bet and more like an infrastructure upgrade.
It also speaks to one of stablecoins’ strongest use cases: settlement speed.
Traditional payment settlement can involve multiple intermediaries, cut-off times, and currency-specific banking rails. Stablecoins can move continuously and settle directly on blockchain networks, depending on the setup.
Visa’s role is to make that capability usable by institutions that cannot simply plug into crypto rails casually.
Most retail users think about stablecoins as trading dollars.
Institutions think about them differently. They care about settlement, liquidity, reconciliation, counterparty exposure, balance management, compliance, and how money moves between entities.
That is why the word “treasury” matters here.
If stablecoins become part of treasury operations, they can sit behind payment flows without end users necessarily realizing a blockchain is involved. A merchant may care that settlement is faster or cheaper. It may not care whether the underlying balance moved through USDC, EURC, or a traditional banking transfer.
This is how crypto infrastructure often becomes mainstream: not by demanding attention, but by solving a back-office problem.
Visa’s stablecoin treasury engine points in that direction. It gives institutions a controlled way to use stablecoins where they make operational sense, while still keeping the product inside a professional financial framework.
The inclusion of both USDC and EURC is notable because stablecoin settlement is becoming more than a dollar-only story.
Dollar stablecoins dominate the market, but euro stablecoins are increasingly important for European payments, MiCA-era compliance, and multi-currency settlement use cases. If institutions want to use stablecoins for treasury management, they will eventually need access to more than one currency.
That is one reason Visa’s move matters.
Multi-stablecoin infrastructure can support more flexible settlement between regions, merchants, and financial institutions. It can also reduce the need for every transaction to route through dollar liquidity if another currency is more appropriate.
The stablecoin market is still heavily dollar-based, but institutional settlement may push more demand toward regulated non-dollar tokens over time.
That could become especially relevant in Europe, where MiCA has created a clearer framework for stablecoin issuers and service providers.
The product should be framed carefully.
Visa is not launching a consumer-facing app that lets everyday users speculate on stablecoins. This is an institutional treasury framework. It is designed for financial institutions and settlement operations, not retail trading.
That makes it less flashy, but more important.
The biggest stablecoin adoption may not come from people choosing to hold stablecoins in a wallet. It may come from stablecoins being used quietly inside payment networks, merchant settlement systems, institutional treasury desks, and cross-border liquidity management.
That is where Visa has influence.
For crypto markets, the signal is clear: stablecoins are moving deeper into mainstream financial infrastructure. The sector has spent years proving that tokenized dollars can move quickly on-chain. The next phase is about whether large financial networks can safely use that speed inside regulated systems.
Visa’s stablecoin treasury engine is another step in that direction.
This article is based on Visa newsroom materials.
This article was written by the News Desk and edited by Samuel Rae.
This report is based on information released in official primary source disclosures at primary source documentation.
Sui has launched gas-free stablecoin transfers, a move that goes directly at one of the most annoying pieces of crypto payments: needing the network’s native token just to move dollars.
For experienced crypto users, gas is normal. For everyone else, it is friction. A user may have USDC or another stablecoin in a wallet, but if they do not also hold the chain’s native token, they can get stuck. They cannot send funds, make a payment, or move assets without first acquiring gas.
That is a terrible experience for payments.
Sui’s new stablecoin transfer feature is designed to remove that issue by allowing users to send supported stablecoins without holding SUI for transaction fees. The available source material points to implementation through Sui’s Move API, with gas set at zero and the fee burden handled away from the end user.
That sounds technical, but the user-facing idea is simple: stablecoins should move more like money and less like a puzzle.
Reference: Sui
Stablecoins are one of crypto’s clearest product-market fits.
They are used for trading, settlement, payments, remittances, DeFi collateral, and dollar access in markets where banking rails are slow or unreliable. But even stablecoins can feel awkward when the user has to understand gas.
The problem is especially obvious for new users. Someone may receive stablecoins and assume they can send them immediately. Then the wallet tells them they need the native asset to pay fees. Now they have to find SUI, ETH, SOL, TRX, or another gas token before they can do anything.
That is not how normal payments work.
Nobody expects to hold a separate “fee token” to send pounds from a banking app or dollars from a payment wallet. Crypto users have learned to tolerate that because they understand blockchains. Mainstream users have not, and probably should not have to.
Gas-free stablecoin transfers are an attempt to hide that complexity.
If Sui can make stablecoin movement feel more like a normal payment action, the network becomes easier to use for wallets, apps, merchants, and everyday transfers.
Sui is not the first network to chase stablecoin payments, and it will not be the last.
Ethereum has the deepest liquidity and most established DeFi ecosystem. TRON has become a major stablecoin transfer network because of its low fees and wide USDT usage. Solana has pushed hard into fast, low-cost consumer payments. Base is trying to combine Ethereum alignment with cheaper transactions and app distribution.
That means Sui needs a real reason for users and developers to care.
Gas-free stablecoin movement is a practical answer. It does not rely on abstract network claims. It solves a visible user problem.
The supported stablecoin list is important as well. According to the cleaned pack, supported assets include USDC, USDsui, suiUSDe, AUSD, FDUSD, USDB, and USDY. That gives the feature a wider stablecoin base than a single-asset implementation.
For developers, the more interesting part may be the infrastructure model. If apps can build payment flows where the user never has to think about gas, Sui becomes easier to integrate into consumer-facing products.
That could matter for wallets, games, DeFi front ends, subscription tools, and cross-border payments.
The launch is promising, but the market will judge it by adoption.
Gas-free transfers sound useful, but the feature needs real volume. Users have to adopt it. Wallets and apps have to integrate it cleanly. Stablecoin liquidity has to remain deep enough that the experience feels reliable.
The competitive bar is high. Users already move stablecoins across other networks, and many do not care which chain wins as long as the transfer is cheap, fast, and easy. Sui has to prove that removing gas friction is enough to pull activity into its ecosystem.
There is also a sustainability question. If end users are not paying gas directly, someone else is absorbing or sponsoring those costs. That can work well, but the economics need to make sense over time, especially if volume scales.
Still, the direction is right.
Crypto payments will not become mainstream if every transaction requires users to understand the mechanics underneath. The winning experience probably looks boring: open app, send dollars, done.
Sui’s gas-free stablecoin feature moves in that direction. It is not a guarantee that Sui becomes a dominant payments chain, but it gives the network a cleaner user-experience argument at a time when stablecoin competition is becoming more serious.
This article is based on information from Sui Network.
This article was written by the News Desk and edited by Samuel Rae.
This report is based on information released by Sui. at Sui
Login