RWA perpetual DEX trading volume has reached $365 billion in Q3 2026, rising 32% from the previous quarter as public equities generated nearly half of the activity.

CryptoRank reported the quarterly figures on Sept. 24, placing public-equity perpetual volume at approximately $175 billion, or close to 48% of the total. The quarter still produced growth despite monthly volumes declining during August and September.

The figures refer specifically to real-world asset perpetual contracts traded through decentralized venues. RWA perpetuals provide derivative exposure to assets such as stocks, commodities and indexes without requiring traders to own the referenced assets directly.

RWA perp DEX volume grew despite two monthly declines

Trading activity entered Q3 from a strong base. CryptoRank said July RWA perpetual volume reached a record $141 billion, following a rise from only $23.1 billion at the start of 2026.

August then became the first monthly contraction since January. Volume fell 13.5% to $122 billion, ending the uninterrupted expansion seen during the preceding months. CryptoRank attributed the pullback to renewed demand for crypto assets after Bitcoin and other major tokens posted stronger price moves during August.

September volume declined again, according to CryptoRank’s Sept. 24 update, yet the full quarterly total still reached $365 billion. The 32% quarter-over-quarter increase shows that July’s record activity was large enough to keep Q3 above the prior three-month period despite the later slowdown.

CryptoRank’s monthly series had already shown how quickly the market expanded during the first seven months of 2026. Its earlier research put July activity 513% above the level at the start of the year, with RWA contracts becoming a larger component of decentralized perpetual trading.

Public equities captured nearly half of Q3 volume

Stocks represented the largest RWA perpetual category during the quarter. CryptoRank placed public-equity volume at $175 billion, giving the category nearly 48% of the $365 billion Q3 total.

The concentration in equities follows a change already visible in August. CryptoRank’s monthly report said public equities had become the largest category in its RWA perpetual dataset. On Hyperliquid, stock-linked contracts accounted for 67% of HIP-3 volume during August, moving ahead of commodity contracts.

Available markets have expanded alongside trading activity. CryptoRank reported on Sept. 22 that decentralized perpetual venues now offer more than 1,000 RWA markets, with public equities representing roughly 75% of listings.

The same report placed tokenized stock market capitalization at $3.5 billion. BNB Chain hosted around $1 billion, while Ethereum and Solana followed. Combined, the three networks represented roughly 70% of the market measured by CryptoRank.

RWA perpetuals differ from tokenized stocks themselves. Perpetual contracts generally track the price of an underlying asset through derivatives and do not give holders ownership rights, dividends or voting claims attached to the referenced stock. Crypto.news explained the distinction in its guide to RWA perpetuals covering stocks and commodities.

Perpetual DEX open interest has reached a record

Trading volume has grown alongside outstanding positions. CryptoRank’s Sept. 22 research put total perpetual DEX open interest at a record $19 billion, with overall perpetual open interest across the measured market near $25 billion.

RWA contracts represented roughly 24% of total open interest, up from around 6% at the beginning of 2026. CryptoRank calculated an 18-percentage-point increase during the year as exchanges introduced more markets tied to stocks, commodities and indexes.

Hyperliquid has remained a major venue in the decentralized derivatives market. Current CryptoRank rankings place Hyperliquid Futures at the top of the DEX table by open interest, with billions of dollars in outstanding perpetual positions and hundreds of listed markets.

One day before CryptoRank published the Q3 RWA figures, Hyperliquid’s open interest reached a reported record of $18 billion. As crypto.news reported in its Hyperliquid open-interest record coverage, BTC, ETH and HYPE accounted for roughly $9.33 billion, while HIP-3 continued hosting contracts linked to stocks, commodities and indexes.

Equity markets are expanding through HIP-3 and tokenization

Hyperliquid’s HIP-3 infrastructure has contributed to stock-linked perpetual activity by letting independent teams deploy perpetual markets. Crypto.news previously reported that TradeXYZ processed $202.36 billion during Q2, based on an independent Hyperliquid Research Collective report.

Equity perpetuals generated $58.9 billion across 55 markets on TradeXYZ during Q2, a 377% quarter-over-quarter increase, according to that report. TradeXYZ’s share of HIP-3 volume increased from 84.5% to 95.1% during the quarter.

On-chain stock activity is developing outside perpetual contracts as well. In June, Ondo Finance extended tokenized U.S. stocks to Hyperliquid’s HyperEVM, initially supporting 35 names including Nvidia, Tesla, Alphabet and several ETFs, as crypto.news reported in its HyperEVM coverage.

Base has recorded another source of tokenized-equity activity. Token Terminal data cited by crypto.news put 30-day tokenized-stock DEX volume on Base at $730.9 million by Sept. 12, after daily volume reached $100 million. Aerodrome processed $557.1 million of the measured monthly activity.

U.S. access to many tokenized equity products remains restricted. Crypto.news reported Sept. 21 that TD Cowen expects limited domestic demand even as the regulatory framework develops, noting that U.S. investors already have established access to conventional listed equities.

Separately, Coinbase’s Base-native stock tokens remain unavailable to U.S. persons under the company’s current Regulation S structure. Coinbase expanded its lineup in September after its first group of tokenized equities produced $227.7 million in decentralized exchange volume over roughly 30 days, according to Token Terminal data cited by crypto.news.

Pudgy Penguins (PENGU) has fallen nearly 10% in 24 hours to around $0.0098 on Sept. 24, even as the token remains roughly 38% higher over the past seven days.

CoinGecko data shows PENGU trading around $0.0098 during the latest check, with a 24-hour range between $0.009478 and $0.01111. Its market capitalization stood near $619 million, while 24-hour trading volume was approximately $376 million.

The token had climbed from $0.00685 on Sept. 15 to above $0.010 earlier this week, CoinGecko historical data shows. PENGU reached the $0.011 area before sellers pushed the price back under the psychologically watched $0.010 level.

PENGU price has slipped below $0.01 after its rally

The latest decline follows several days of strong gains. CoinGecko recorded PENGU at $0.00726 on Sept. 17 and $0.01003 by Sept. 22, showing how quickly the token advanced before the latest pullback.

CoinGecko still placed PENGU’s seven-day return near 38.2% during the Sept. 24 check. The token remained approximately 85% below its $0.06845 all-time high despite the weekly recovery, while its circulating supply stood at roughly 62.86 billion tokens.

No single verified project-specific event reviewed for this report established the cause of Thursday’s drop. Market data instead shows the decline occurring after PENGU reached its highest price in several months and after derivatives participation began cooling.

PENGU open interest has fallen as traders reduce exposure

A Sept. 24 CoinGlass snapshot showed derivatives volume down 12.68% at approximately $536.67 million, while open interest declined 11.66% to roughly $154.03 million. A later live reading placed open interest near $156.47 million and 24-hour futures volume around $576.31 million, showing how quickly the figures can change intraday.

CoinGlass recorded nearly $1.94 million in PENGU futures liquidations over 24 hours during that later reading. Falling open interest means fewer futures positions remain outstanding, although CoinGlass notes that position closures can result from voluntary exits or forced liquidations and do not identify a single directional cause.

Spot flows looked less decisive. The Sept. 24 CoinGlass netflow reading supplied with the market data stood near +$88,550, meaning exchange inflows were only slightly above outflows at that point. The recent flow series contained both positive and negative readings without a sustained run of large positive inflows.

Technical indicators remain positive but momentum is stretched

PENGU’s 14-period RSI stood at 67.15 in the chart data provided for Sept. 24. The reading remains above the neutral 50 level and below the conventional 70 overbought threshold, showing strong momentum without formally entering the usual overbought zone. The RSI moving average sat near 50.56.

The Aroon Oscillator was approximately +57.14, indicating that recent highs have occurred more prominently than recent lows over its 14-period window. Both measures remained positive despite the price rejection above $0.010.

The $0.0095 region therefore sits close to the token’s Sept. 24 intraday low of $0.009478 recorded by CoinGecko. A loss of that area would place PENGU below the short-term support identified by CoinLore, while a recovery above $0.0105 would move price back toward its recent highs.

Analysts are watching $0.011 before higher PENGU targets

Crypto analyst Ali Charts has pointed to several weekly indicators that he views as constructive. His Sept. 22 analysis identified contracting Bollinger Bands, consecutive Tom DeMark Sequential buy signals, a bullish Parabolic SAR flip and a SuperTrend buy signal.

Ali wrote “PENGU BULL RUN IS ABOUT TO START” while placing the midpoint of a parallel channel around $0.025 and its upper boundary close to $0.045. Both levels are analyst projections, not confirmed price outcomes. Independent coverage of his chart documented the same Bollinger Band, TD Sequential, Parabolic SAR and SuperTrend readings.

Two days later, Ali compared PENGU’s structure with an earlier PEPE cycle and wrote “PENGU ABOUT TO EXPLODE.” His comparison relies on a historical price fractal, so a similar past pattern does not establish that PENGU will follow PEPE’s previous trajectory.

The Senate stopped short of debating a federal crypto market structure bill. A week later, the CFTC chair was still laying out plans for tokenized collateral and round-the-clock markets. The agencies can act under existing law, but their records show how far each action actually reaches.

The Commodity Futures Trading Commission wants markets ready for tokenized collateral and 24-hour trading. Its chair, Michael Selig, said as much at a Treasury market conference on Sept. 22, one week after the Senate blocked debate on the CLARITY Act. He described work on stablecoins as derivatives collateral and said some products, including crypto, may suit continuous trading. The agency had already sent a crypto market measure to White House review. Selig’s remarks were a statement of direction, not the publication of that measure.

The order of events matters. The Securities and Exchange Commission had proposed crypto offering rules before the Senate vote. It issued a limited exemption for tokenized stock trading two days afterward. The CFTC filed a separate measure for preliminary review the same day, as crypto.news reported when the CFTC submission appeared. Washington is writing parts of a rulebook while the bill that would set its statutory foundation remains stalled.

How much of a market can those parts govern? The public documents give a more useful answer than the shorthand that regulators have replaced Congress. One action interprets existing securities law. Another proposes exemptions for raising money. A third permits a specific way to trade tokenized stocks. The CFTC’s next rule has not yet been released for public inspection. None is the spot digital commodity market law contemplated by CLARITY.

The Senate rejected debate, not a final crypto law

On Sept. 15, the Senate voted on cloture on a motion to proceed to H.R. 3633. The official roll call records 49 votes for cloture, 50 against and one senator not voting. Sixty votes were required. Senators did not vote on final passage or settle the bill’s provisions through floor amendments.

Some accounts inverted the numbers, describing 50 votes in favor and 49 against. The Senate record says the reverse. Either count falls short of 60, but a feature about who can write law should get the legislature’s own vote right. The 49 supporting senators were 11 votes short of the threshold. Four Republicans voted against the motion, including Thom Tillis, whose procedural switch left a route to seek reconsideration. The bill remained available for further negotiation; its Sept. 15 path to debate was blocked.

CLARITY aimed to divide oversight of digital assets and their markets between the SEC and CFTC, including a registration structure for digital commodity intermediaries. Congress had been considering a more complete answer to questions that agencies now confront through rules, interpretations and orders. The House passed its version in July 2025. Its later Senate text changed during negotiations, so an account of a disputed September provision must specify which version it describes. The Senate-reported version remains a public reference, but it should not be mistaken for every late negotiating draft.

The disagreement was political and substantive. Senate Banking Chair Tim Scott said after the vote that the SEC and CFTC should set rules until Congress legislates. Democratic Senator Mark Warner said he wanted digital asset legislation, but would not advance this version without stronger restrictions on senior officials profiting from policies affecting their crypto holdings. Banking organizations separately pressed for tighter restrictions on rewards associated with holding stablecoins, saying deposit competition could affect lending. Those groups made a policy argument; no projected deposit loss should be treated as an observed outcome.

Seven Democratic senators who opposed the motion said the following day that they remained committed to bipartisan legislation. Calling the bill law would be false. Calling it permanently dead would go beyond the vote.

The SEC can interpret a transaction without licensing its market

The regulatory work did not begin on Sept. 15. On March 11, the SEC and CFTC signed a coordination agreement covering shared definitions, examinations and enforcement. Six days later, the SEC issued interpretive release Nos. 33-11412 and 34-105020, with accompanying CFTC guidance. It described digital commodities, collectibles, tools, stablecoins and digital securities. It addressed staking, mining, airdrops and wrapping, as well as when a nonsecurity crypto asset can be sold as part of an investment contract. The agencies’ March interpretation was an exercise of their existing authority.

The distinction between an asset and a transaction is central. A token need not itself be a security for a promoter’s offer of it to involve an investment contract. The SEC’s description of an asset does not remove the securities laws from every transaction in that asset. Nor does calling an asset a digital commodity hand the CFTC full supervision of every spot exchange that lists it. An earlier crypto.news examination of the SEC’s classification of XRP addresses the separate question of how long an agency interpretation may last.

Consider a platform that lists a digital commodity for ordinary purchase and another platform that offers leveraged positions in the same asset. The asset label may be the same. The activity and applicable jurisdiction are different. The CFTC regulates derivatives and certain leveraged retail commodity transactions under existing law. For ordinary spot digital commodities, it has described its federal role principally as enforcement against fraud and manipulation, without general day-to-day supervision of spot exchanges. Its own account of the distinction is unusually clear.

That is the gap CLARITY was designed to address. The SEC and CFTC can coordinate their interpretations. They cannot create an unrestricted federal spot market mandate merely by agreeing which tokens count as commodities. An agency can regulate conduct within the perimeter Congress gave it. It cannot vote itself the rest of the perimeter.

There is still practical value in the interpretation. An issuer deciding whether a proposed token sale needs securities registration now has a published view from the SEC. A derivatives venue knows the CFTC says it will administer the Commodity Exchange Act consistently with that view. The treatment could shape business decisions immediately. It is still different from a new statute governing intermediaries across the spot market. A court or later commission can test or revisit an agency’s reading of existing law.

Four records show why the ‘new rulebook’ is still uneven

The primary documents can be sorted by two questions: has the action taken effect, and does it govern ordinary crypto spot trading? The answer changes in every row.

One of these measures is an effective exemption. One remains a proposal. Another is a public interpretation, and the fourth is a filing title and review status. Describing all four as ‘rules now in force’ would turn a process into a result. More tellingly, the effective exemption concerns shares, which remain securities, while the largest proposed jurisdictional change in CLARITY concerned digital commodity markets. The most visible new trading permission sits on a different side of the SEC-CFTC divide.

The CFTC review record names ‘Regulation Crypto Asset Transactions and Regulation Crypto Asset Markets,’ identifies the agency, and labels its stage ‘Prerule.’ It gives a Sept. 17 receipt date. It does not disclose draft provisions or show a commission vote on a proposed or final rule. That small entry proves that a measure entered review. It does not prove what legal powers the eventual text will claim.

Selig offered a possible route in August. He said staff were examining whether existing registrants and unregistered crypto exchanges could be designated as a type of CFTC designated contract market, with leveraged or margined crypto trading under tailored rules. His remarks also described working with onchain software developers. They are evidence of his intended approach, not a substitute for the unreleased CFTC text. Whether the agency’s eventual proposal fits its existing authority depends on its actual provisions.

The narrower route may still change a great deal for firms that want to offer margined crypto trading in the United States. It would not automatically cover every app where a customer buys and withdraws an unleveraged token. That missing customer, venue and transaction sit at the center of the congressional question.

The SEC’s $75 million route is a proposal with an expiry problem

The SEC’s Aug. 18 proposal would give eligible projects two tailored ways to offer investment contracts involving crypto assets without registering the offering. One would allow up to $5 million over a four-year period. Another would permit up to $75 million in each 12-month period, with financial statements and ongoing reporting alongside required disclosures. It proposes a conditional safe harbor concerning when the related investment contract no longer applies. The published proposal sets an Oct. 20 comment deadline. A crypto.news account of the offering proposal examines those routes in more detail.

The proposal does not say that every token becomes exempt from securities law after four years. Its application depends on the facts of an issuer’s commitments and compliance with its conditions. It does not license an exchange to ignore laws governing securities activity. Antifraud provisions remain relevant. And none of the proposed fundraising routes can be used merely because the SEC has announced them; a final rule would have to follow the comment process.

The policy choice is significant. Projects often raise money while a team is still promising to build the network on which a token’s value might depend. The SEC is trying to specify how that fundraising stage might be conducted and, under stated conditions, how the associated investment contract could end. The proposal answers a question about capital raising. It does not supply a federal registration system for the entire digital commodity spot market.

That distinction has an institutional consequence. A company can plan a token offering around a published proposal only provisionally. It can plan around an effective rule more confidently, while still accounting for future changes and court review. A national law fixing the agencies’ mandates would require another institution to change it. Industry advocates want the agency work to advance precisely because waiting for that institution has not produced a bill. The staged process creates rules sooner in some corners and leaves others open.

A five-year stock exemption has a narrower address

The SEC’s Sept. 17 order, release No. 34-106402, is the most concrete post-vote action. It temporarily exempts qualifying Tokenized Securities Venues from the Exchange Act definition of ‘exchange’ for a particular model of permissioned automated market maker trading in tokenized National Market System stocks. It grants separate conditional relief to certain liquidity providers from the definition of ‘dealer.’ The 60-page order states that the exemptions run until Sept. 17, 2031, unless the commission changes them under its authority.

Stockholders must have the same rights and privileges as holders of an equivalent traditional share. The venue faces limits on symbols and trading volume, must stop trading when the underlying stock is halted, and must allow an issuer to object when an unaffiliated third party tokenizes its shares. The smart contracts used for the trading model must be public and auditable on a public, permissionless ledger, while access to the venue is restricted to approved participants. The order does not exempt fraud or manipulation.

Those conditions illustrate both the potential and the boundary of agency action. An SEC exemption can open a defined route for trading securities without waiting for Congress to rewrite every exchange rule. It does not make all decentralized trading lawful or designate the CFTC as supervisor of every crypto asset. SEC Chair Paul Atkins called the measure a bridge and said durable rulemaking would need to follow. A crypto.news report on the tokenized stock exemption looks at the possible commercial users. A bridge is useful. It is not the destination.

The order deserves scrutiny on its own merits, too. Its volume caps are meant to limit disruptions if prices in an automated pool diverge from shares trading in conventional markets. Disclosure and records conditions give the SEC a way to see how the model operates. Whether actual venues satisfy the conditions, attract activity and preserve shareholder rights is an observable question, not an assumption to be filled in by the agency announcement.

Supporters of agency action have a strong practical case

Scott’s call for regulators to act did not require the claim that legislation was unnecessary. Selig himself said in August that a statute was the strongest way to fix the SEC-CFTC jurisdictional line and set principles for spot crypto markets. He nonetheless directed CFTC staff to examine rules under current authority. Those positions can coexist: a firm needs to know what rules apply to a proposed product now, even when Congress might later change the governing law.

Atkins made a related case for using a temporary SEC exemption while the commission studies tokenized stock trading. The Sept. 17 order imposes participant screening, trading limits, disclosure, records, issuer rights and the ordinary securities law bans on fraud and manipulation. It is an intervention with conditions, not an unregulated free pass. His argument is that an observed market can inform permanent rules better than a market that cannot start.

Coin Center, a crypto policy organization, made a different case within the same debate. Its March submission urged broad prospective rulemaking over individual relief, arguing that selective exemptions can favor applicants with the resources to seek them and leave decentralized projects outside. That criticism does not show the SEC order is improper. It identifies a question the order cannot settle: whether other workable models get an equivalent path.

Warner’s opposition to the Senate bill is another constraint on a simple ‘Congress failed, agencies solved it’ account. He said the dispute over ethics requirements involving elected officials prevented his support despite progress on national security issues. Rules from financial regulators about trading venues do not resolve the elected-official ethics issue that helped stop the vote. Banking groups’ concerns about rewards tied to stablecoin balances likewise involve a separate dispute over the boundary between payments and deposit competition. The missing legislation is missing for reasons the agencies’ crypto rulemaking cannot erase.

The decisive test is an ordinary spot trade

Take a customer who deposits dollars on an exchange, buys an unleveraged digital commodity and withdraws it to a wallet. The March interpretation helps describe the asset and the legal treatment of a particular sale. The SEC’s offering proposal could matter to an earlier fundraising transaction involving that asset. The tokenized stock order is irrelevant to this trade. The CFTC’s unpublished measure cannot yet be applied to it, and Selig’s public example centers on leveraged or margined trading.

What federally supervises that ordinary spot exchange’s routine operations? Existing anti-fraud powers, applicable state regimes and other federal obligations do not amount to the dedicated CFTC spot-market registration and supervision framework CLARITY sought to create. This is the part of the rulebook agencies cannot simply announce into existence. The difference is more than durability: it is the scope of the legal authority available in the first place.

That customer example is also a way to judge the feature’s claim. If Congress passes a law assigning broad spot digital commodity oversight, the gap narrows by statute. A crypto.news look at Bitcoin after the Senate vote addresses the asset’s current classification. If the CFTC publishes a measure that identifies an existing legal basis covering more of the ordinary spot transaction than Selig’s August remarks suggested, its precise terms will need to be examined. The Sept. 17 review listing alone does not answer either point.

The limits run in both directions. The failure of CLARITY did not repeal securities or commodities law, undo the SEC’s March interpretation, or stop agencies from proposing and issuing measures within their authority. The SEC stock exemption is real. So are its boundaries. The CFTC may yet publish a consequential proposal. Until it does, a filed title should not be asked to carry the weight of a completed rule.

What to watch

The CFTC proposal: Watch for publication of the text tied to RIN 3038-AF80 after executive review. Its treatment of unleveraged spot trading is the most direct test of its reach.

The SEC comment deadline: Comments on Regulation Crypto Assets are due Oct. 20, 2026, under the published proposal. Any subsequent final text could change the $5 million and $75 million routes.

The tokenized stock venues: Public venue notices, trading volume and issuer objections will show whether the SEC’s five-year exemption becomes a used market or remains an available permission.

The Senate’s next motion: A renewed effort to proceed to H.R. 3633, revised bill text or a new bipartisan agreement would change the legislative outlook. The Sept. 15 cloture vote did not decide final passage.

The spot exchange question: Any proposed CFTC registration requirements should be read for the products and transactions they cover, not only the number of exchanges that might apply.

FAQ

Disclaimer: This article is for information and educational purposes only and does not constitute financial or investment advice. Figures reflect regulatory filings and reporting available at the time of writing and change with each disclosure. Nothing here is a recommendation to buy, sell, or hold any security or asset. Always do your own research. Information is accurate as of September 24, 2025.

NYSE and Blockchain.com have agreed to explore distributing tokenized U.S. shares to a global crypto audience. The deal leaves the harder questions for the platform’s launch: whose record proves ownership, who decides who can trade, and how the new market stays tied to the shares beneath it.

The New York Stock Exchange and Blockchain.com signed a memorandum of understanding on Sept. 23 to explore giving Blockchain.com customers access to tokenized U.S. stocks and exchange-traded funds. The route would run through NYSE’s planned digital alternative trading system, subject to required regulatory approvals. It is a plan for distribution, not a launch of stock trading to the company’s more than 44 million confirmed accounts.

NYSE is building a market that could operate at all hours and settle trades onchain. Blockchain.com brings a customer network already accustomed to digital assets. The announcement does not identify the final custody chain for each share, say which customers will qualify, or publish the terms under which a token could be converted back into a conventional holding. Those details decide what a buyer owns.

The answer will differ by product. A token can be the security recorded on a company’s shareholder file. It can represent an entitlement to a share held through an intermediary. It can instead be a contract that tracks a share’s price. All three can display a ticker on a phone. Only the first two can potentially carry the underlying shareholder interest, and even there the legal path to voting or dividends needs to be specified. The Securities and Exchange Commission drew those distinctions in a January staff statement on tokenized securities.

The new agreement makes an old stock market question visible in a new format. A blockchain can record a transfer. It does not, on its own, determine which entity owes the holder a dividend, who can correct a mistaken transfer, or whose ledger a company treats as its shareholder record.

The Sept. 23 deal is a distribution agreement, not an open market

The parties called their agreement a memorandum of understanding. Their joint announcement says Blockchain.com’s user base would gain access to tokenized listed equities and ETFs through NYSE’s previously announced digital ATS after necessary approvals. The agreement covers a second business line: ICE Data Services plans to distribute Blockchain.com’s crypto data, while Blockchain.com plans to bring ICE and NYSE exchange data into its app.

That data arrangement could start informing users before they can buy any tokenized stock through the proposed venue. The announcement offers no launch date, approved securities list, country-by-country access rules or account-level eligibility figures. Forty-four million confirmed accounts measure an existing customer base. They do not measure approved brokerage accounts, funded investors, stock orders or future onchain volume.

The distinction matters because earlier ICE announcements already described several pieces of the same developing platform. In January, NYSE parent Intercontinental Exchange outlined a digital trading platform combining its Pillar matching engine with blockchain-based systems for custody and settlement. In March, NYSE named Securitize as its first prospective digital transfer agent able to mint blockchain-native securities for corporate and ETF issuers. The Sept. 23 deal adds a distributor and market data connection to that proposed structure. It does not say Blockchain.com becomes the transfer agent, the securities issuer or the operator of NYSE’s ATS.

NYSE Group President Lynn Martin told lawmakers on Sept. 2 that the planned platform would link digital equities directly to underlying shares and preserve voting rights, dividends and corporate actions. That is NYSE’s stated design. The signed customer terms, transfer records and regulatory approvals would show how it operates for a buyer. It is too early to treat the design statement as evidence that a particular token or distribution channel has gone live.

A crypto.news report on the new NYSE agreement covered the announcement and noted that the companies had not said their arrangement was approved under the SEC’s separate innovation exemption. The useful question now sits underneath the partnership: which existing institutions will keep authority over the shares when trading moves across a blockchain?

Crypto exchange Bitget says it has detected an unauthorized transfer event that affected approximately $351.6 million worth of assets, and it has temporarily suspended withdrawals while it investigates. The incident was identified after Bitget’s security systems flagged suspicious activity involving a limited set of hot wallets around 18:31 UTC on Thursday.

In a live Q&A, Bitget CEO Gracy Chen said the breach was contained to a portion of the exchange’s hot and warm wallet infrastructure, while its cold wallets remained secure. She also indicated that withdrawals are expected to restart within hours to days, and that the exchange is working with law enforcement and onchain security firms.

Key takeaways

• Bitget reported unauthorized transfers totaling about $351.6 million and temporarily halted withdrawals.
• The company says only a limited number of hot wallets were involved, with cold wallets remaining secure.
• Chen cited exposure across multiple networks, with Ethereum representing the largest concentration of the observed stolen funds.
• Bitget said customer balances remain accurate and deposits and trading continue.
• Bitget claims the losses are more than covered by its User Protection Fund, which it says holds over $464 million.

What Bitget says happened

According to Bitget’s public statement, its security monitoring systems identified unauthorized transfers linked to a small number of hot wallets at 18:31 UTC on Thursday. The exchange then initiated emergency response procedures.

Chen said the incident was confined to certain hot and warm wallet layers. She emphasized that Bitget’s cold wallet setup—typically used to hold the majority of assets offline—was not compromised. This distinction matters because it suggests the attack vector likely targeted operational wallet components rather than Bitget’s offline reserves.

Scope of affected assets and networks

Chen said affected assets included Ether (ETH), XRP (XRP), USDt (USDT), USDC (USDC), Avalanche (AVAX), BNB (BNB), and USDT0 (USDT0) on Arbitrum. She also identified the networks involved as Ethereum, the XRP Ledger, Avalanche, BNB Smart Chain, and Arbitrum.

While Bitget disclosed multiple tokens and multiple networks, Chen pointed to Ethereum as accounting for the main concentration of the observed stolen funds. That detail is important for market participants and onchain analysts because it indicates where investigators may find the clearest trail of movement first—particularly when early reporting is based on initial onchain sightings.

Bitget also addressed a discrepancy between early onchain reporting and its later figure. Chen said the initial estimate appeared lower because the unauthorized activity extended beyond the Ethereum-focused activity captured in early onchain analysis.

Withdrawal suspension and ongoing operations

Bitget temporarily suspended withdrawals during its security review. Chen said the exchange expects withdrawals to resume within a matter of hours or days, implying a staged restoration process rather than an immediate return to full throughput.

At the same time, Bitget stated that user account balances remain accurate and that deposits and trading are continuing normally. For users, that combination—trading functionality intact but withdrawals paused—signals that Bitget likely prioritized liquidity protection and operational controls while it determines how funds moved and what portion can be recovered or compensated.

Bitget said it flagged addresses associated with the transfers and that it had contacted law enforcement and onchain security firms. Those steps typically aim to both support forensic tracing and reduce the likelihood of further movement through blacklisted or monitored pathways.

Compensation stance and promised reporting

Chen said the affected funds are more than covered by Bitget’s User Protection Fund, which she said currently holds more than $464 million. The claim is meant to reassure users that the exchange has a buffer to compensate for losses, even though the final outcome—such as whether any portion is recovered—still depends on the investigation.

Bitget also said it will provide hourly updates and publish a full incident report within 24 hours. The report is expected to include a root-cause analysis and corrective actions, which investors and system auditors will likely focus on to understand how the breach reached hot and warm wallet layers and what controls will be revised to prevent recurrence.

The exchange’s approach—rapid operational containment, public disclosure of token and network scope, and a defined timeline for deeper technical reporting—will be closely watched by users at other exchanges as well. Security incidents often lead to heightened scrutiny of wallet architecture, signing workflows, and monitoring thresholds, particularly when hot wallet access is implicated.

For now, traders and users should watch whether Bitget meets its withdrawal-resumption timeframe and whether the promised incident report clarifies the precise entry point and the corrective measures for hot and warm wallet handling—especially since early onchain estimates differed from the exchange’s later, broader figure.

Bitcoin climbed past $87,000 after a rate increase that should have made risk harder to own. The public record identifies several sources of demand, but it cannot put a name to every buyer or turn fund inflows into a complete account of the rally.

Bitcoin’s rally after the Federal Reserve raised interest rates has an answer that can be measured, though not a single buyer who can be named. Money returned to US spot Bitcoin exchange traded funds. A public company resumed purchases. Traders caught on the wrong side of the rise had to close positions. By September 21, Bitcoin had moved above $87,000, then surrendered part of the gain two days later.

The timing matters. The Federal Open Market Committee raised its target range by a quarter point to 3.75% to 4.00% on September 16. Its September projections put the median year end policy rate at 4.1% in both 2026 and 2027. In June, those medians were 3.8% and 3.6%. The Fed did not promise a cut.

A hike had been expected by many traders. Expectations alone, however, cannot account for the subsequent purchases. The useful question is narrower: which observable channels brought demand into Bitcoin after the decision, and which claims about the buyers go beyond the evidence?

The funds first lost $746 million

Farside Investors’ daily fund table records $450.4 million of net withdrawals from US spot Bitcoin ETFs on September 15 and another $295.9 million on the day of the Fed decision. Add them: $746.3 million left over two trading sessions. The decision was hardly greeted by an immediate flood into the funds.

The direction changed on September 17. Funds took in $159.5 million, followed by $433.0 million on September 18, $999.0 million on September 21 and $714.7 million on September 22. SoSoValue’s September 23 figures, reported by crypto.news, add $346.98 million for a fifth consecutive positive session.

Together, the five figures total $2,653.18 million. Subtract the $746.3 million of withdrawals from September 15 and 16 and the eight trading days show a net $1,906.88 million entering the funds. The latter is an accounting window, not a measure of money that bought Bitcoin at the rally’s exact hour. It is the net of two sharply different periods, and reporting only the five positive sessions would conceal the withdrawals immediately before the turn.

There is a data trap here. An earlier snapshot of Farside’s September 23 table showed only $32.4 million, with several issuers’ entries still blank. The later SoSoValue reading included $166.29 million for BlackRock’s IBIT and $143.24 million for Fidelity’s FBTC, among other reported fund flows. Treating a blank as zero would understate that day’s total by more than $300 million. These are dated snapshots, and totals can change when issuers report.

The apparent buyers changed between Monday and Wednesday

Monday’s $999.0 million was spread among several funds. Farside recorded $381.4 million for BlackRock’s IBIT, $289.1 million for ARK 21Shares’ ARKB and $238.8 million for Fidelity’s FBTC. Combined, those three accounted for $909.3 million, or about 91% of that day’s total. This identifies fund vehicles, not the institutions or people placing orders through them.

Tuesday’s flow was $714.7 million in Farside’s later table. IBIT received $350.3 million and FBTC $257.4 million. Those two accounted for about 85% of the daily total. By Wednesday, Bitcoin had retreated toward $84,000 even as SoSoValue reported another $346.98 million into the funds.

That final pairing is as important as the Monday surge. A positive ETF print does not guarantee a positive Bitcoin session. Fund subscriptions are one channel of net demand; sellers on exchanges, derivatives positions and the timing of fund hedging all affect the price. The five day fund streak establishes persistent subscriptions. It cannot prove those subscriptions alone pushed Bitcoin through $87,000.

The concentration figures matter for the same reason. On Monday, IBIT, ARKB and FBTC supplied more than nine tenths of net additions; that does not mean three asset managers independently decided to buy Bitcoin with their own balance sheets. A fund can receive orders from brokerage customers, registered advisers and institutions. The issuer reports the fund level flow. Its table does not sort the orders by investor type. Calling all $999 million institutional buying would add a claim the data do not contain.

Monday and Wednesday also illustrate why two kinds of accounting should stay separate. A fund flow is a net change in assets associated with subscriptions and redemptions. A traded fund share can change hands repeatedly between investors in the secondary market without producing the same amount of new fund creation. Price, exchange turnover and ETF net flow are different measurements. A headline can be accurate on one and misleading on another.

ETF inflows are net creations or subscriptions valued in dollars, not a public register of every underlying investor or a second by second ledger of coins bought. Market makers and authorized participants can bridge a fund trade and its underlying hedge at different times. Nor does a dollar flow translate into an exact Bitcoin quantity without choosing a price and knowing when the exposure was acquired. Converting $999 million into BTC at the day’s closing quote would produce an illustration, not an audited purchase count.

A corporate purchase is real, but its clock is different

Strategy provides a named buyer. Its September 21 Form 8-K reports the purchase of 950 BTC for $75.7 million, including fees and expenses, at an average $79,670 per coin. The transactions occurred between September 14 and September 20. The filing gives the period, not the individual trades’ timestamps.

That distinction rules out an easy claim. Strategy’s announcement landed on September 21, when Bitcoin rallied, but the filing does not show that Strategy bought Bitcoin during Monday’s surge. Its purchase may have happened before, after or across the September 16 rate decision. It used existing USD Cash and said it issued no shares through its at the market program during the period.

Strive’s September 21 filing identifies another corporate buyer: 1,355 BTC at an average price of roughly $79,475 during September 14 to 18. Its disclosure has the same dating problem for anyone trying to explain a particular candle. The combined reported 2,305 BTC shows corporate accumulation over overlapping periods; it does not measure corporate buying on September 21.

Strategy’s 950 BTC can be compared with its own past and future disclosures. It cannot simply be added to $2.65 billion of ETF inflows and called total market demand. The windows overlap, the units differ and other buyers and sellers are missing.

Some buyers were closing losing bets

The other identifiable class of buyer did not necessarily want to own Bitcoin for months. A trader short a Bitcoin perpetual or futures contract must buy back exposure to exit. If price rises quickly, liquidation can force that purchase. Those buy orders can add fuel to the move that made the short untenable.

Nansen senior research analyst Nicolai Sondergaard described the rally as a combination of ETF demand and short covering. A September 23 crypto.news account quoted CoinMarketCap research lead Alice Liu saying covering, rather than new buying, drove much of the rise. These are analysts’ interpretations, not a trader by trader audit.

One check comes after the peak. A CryptoQuant analyst’s exchange data, cited by crypto.news, showed Binance Bitcoin open interest falling from about $5.4 billion to $4.9 billion between September 21 and 23. Bitcoin had declined by then. Falling open interest shows positions closed, but it does not, on its own, separate shorts closed during the rally from longs unwound during the retreat. The $500 million change is a change in the dollar value of outstanding positions, not $500 million of confirmed short buying.

No comprehensive public tape identifies the beneficial owner behind each ETF order and each derivatives close. A forced short buy and a patient fund subscription may both lift demand, but they imply different things about what happens when price stops climbing.

The strongest case for lasting demand has a limit

There is a serious argument that the inflows represent more than a squeeze. Five consecutive positive fund sessions, worth $2.65 billion, spanned the climb and continued on September 23 after the pullback. The purchases were not confined to one fund. IBIT, FBTC and ARKB all drew substantial cash on September 21. Corporate filings show at least two companies buying during the surrounding week. Those are observable commitments, regardless of the Fed’s posture.

The opposing interpretation has a different strength. Bitcoin’s move to about $87,300 did not hold; price was back near $84,000 by September 23. The ETF print records subscriptions during a day, while the price reflects all orders at their execution times. If new fund cash keeps arriving as Bitcoin falls, it means sellers are meeting it. That does not make the fund demand imaginary. It means its price impact cannot be read directly off its dollar total.

Recent crypto.news coverage of the ETF streak reported the pullback alongside continuing inflows and falling Binance open interest. Those facts support a mixed account: underlying fund demand was present, while leverage amplified and then retreated from the move. The public numbers do not tell us the exact share attributable to each.

For a cleaner test, compare the next complete fund reports with the path of open interest after the rally. If subscriptions remain large while open interest stops contracting, the evidence for demand beyond traders closing shorts strengthens. If subscriptions dry up and the price keeps slipping, Monday’s surge looks more dependent on temporary buying. Neither pattern proves causation on its own, because the public series are aggregated across markets and reported at different frequencies.

There is a second timing problem. Bitcoin trades around the clock; US listed fund shares trade during US market hours. The biggest crypto move can happen before an ETF session opens or after it closes. A daily ETF total cannot be laid over a 24 hour Bitcoin candle as though both cover identical hours. Any precise account of Monday would require intraday spot order flow, fund creation timing and derivatives transactions on a common clock. The available public daily series fall short of that standard.

The Fed did not become a buyer’s signal

The Fed’s September statement said inflation remained elevated and economic activity was expanding at a solid pace. Its 2026 and 2027 median rate projections of 4.1% are each higher than in June. The September projection table is a set of participants’ assessments of appropriate policy, not a binding schedule of decisions, but it offers little support for a claim that a near term rate cut drove the immediate rally.

A risk asset can rise after a hawkish decision if the surprise was already priced, other yields fall, or buyers in its own market outweigh macro pressure. Those are possible mechanisms, not proof that one explains this week. The observed fund reversal begins September 17, one day after the announcement. By September 21 it was large enough to see without a macro theory: $999 million in reported net subscriptions.

The more revealing development came when price and subscriptions parted ways on September 23. That is where the original question becomes testable. If fund creations keep coming while short positioning stays less crowded and Bitcoin holds its gains, the evidence for sustained cash demand improves. If creations turn negative and the price loses the levels recovered after the decision, the short squeeze explanation gains weight. Neither result can assign every past trade to an individual investor.

What the public record can actually name

The records identify funds, companies and position types. They do not name the ultimate owner of IBIT shares purchased on September 21. They do not date Strategy’s 950 BTC to Monday. They do not show that every liquidation produced a spot Bitcoin purchase on an exchange.

What they do show is enough to reject two simple versions of the story. Bitcoin did not rally because investors immediately celebrated the September 16 hike: ETF funds lost a combined $746.3 million on September 15 and 16. Nor was the rebound just a chart artifact with no recorded cash demand: about $2.65 billion entered spot funds over the next five sessions, on the figures available September 24.

A public filing adds 950 BTC of Strategy purchases during September 14 to 20, while Strive reports another 1,355 BTC during September 14 to 18. Short covering plausibly accelerated the price move, but no audited decomposition of its contribution has been published. The answer is a set of buyers, operating on different clocks.

What to watch

Daily ETF creations: Check the complete issuer table after every fund has reported; a blank cell is not a zero.

Fund concentration: A positive total spread across IBIT, FBTC and ARKB differs from one driven by a single product.

Open interest with price: Rising price and falling open interest can fit short covering; falling price and falling open interest can reflect long unwinds.

Corporate filings: Read transaction windows in each 8-K before assigning a purchase to a specific trading day.

Price against flows: Compare Bitcoin’s daily close with that day’s fund subscriptions. The September 23 divergence deserves more attention than an inflow headline alone.

FAQ

Disclaimer: This article is for information and educational purposes only and does not constitute financial or investment advice. Figures reflect regulatory filings and reporting available at the time of writing and change with each disclosure. Nothing here is a recommendation to buy, sell, or hold any security or asset. Always do your own research. Information is accurate as of September 24, 2026.

European financial watchdogs have warned on Sept. 23 that sufficiently advanced quantum computers could undermine cryptography securing blockchains, while CryptoQuant founder Ki Young Ju estimates 6.89 million BTC may have public-key exposure relevant to a future quantum attack.

The Joint Committee of the European Supervisory Authorities, comprising the European Banking Authority, European Insurance and Occupational Pensions Authority and European Securities and Markets Authority, warned that quantum computing could create major risks for cryptographic systems protecting transactions, communications, databases and blockchains.

The Sept. 23 Autumn 2026 risk update did not say a machine capable of breaking Bitcoin cryptography exists today. Its warning focused on preparation, noting that quantum-related security risks could emerge before commercially useful quantum applications become practical.

EU watchdogs say cryptographic risks could emerge early

In its risk update, the Joint Committee said quantum computing could improve financial processes, pricing, fraud detection and compliance monitoring. The same technology could eventually weaken cryptography used throughout financial infrastructure. The authorities wrote that “risks posed could also materialise faster than any commercially viable application.”

A separate ESMA technical analysis published in May examined the mechanics in more detail. It said sufficiently advanced quantum computers could use Shor’s algorithm against public-key schemes including RSA and elliptic-curve cryptography, or ECC. Bitcoin relies on elliptic-curve signatures for ownership and transaction authorization.

ESMA stressed that such attacks remain beyond current noisy intermediate-scale quantum, or NISQ, machines. Its report said systems capable of threatening existing cryptography are not expected immediately, but long migration periods make early preparation necessary.

IBM has taken a similar position on timing. The company said in April that fault-tolerant quantum systems could begin approaching cryptographic relevance by the end of the decade. IBM has not said a Bitcoin-breaking quantum computer exists now.

Bitcoin quantum exposure estimates depend on methodology

The amount of Bitcoin potentially exposed to a future quantum attacker remains disputed because researchers count address types and reused keys differently.

CryptoQuant founder Ki Young Ju estimated in February that approximately 6.89 million BTC could face quantum exposure under his methodology. His figure included roughly 1.91 million BTC associated with directly visible public keys and other coins whose keys may have been revealed through previous spending behavior. The estimate included dormant holdings attributed to early Bitcoin users.

IBM has connected Digital Asset Haven to Swift’s blockchain-based shared ledger while opening an on-premises beta that lets regulated institutions keep digital asset operations inside their own data centers.

IBM said on Sept. 24 that Digital Asset Haven clients can access permissioned blockchain networks, including Swift’s ledger, through a beta ISO 20022 Messaging Adapter. The company said institutions can use familiar ISO 20022 messages to instruct tokenized deposit transactions instead of creating separate blockchain-specific payment workflows.

The release expands a platform IBM introduced in October 2025 for banks, governments and regulated companies managing digital assets. IBM originally built Digital Asset Haven to cover wallets, transaction orchestration, governance and key management across public and private blockchain networks.

IBM connects tokenized deposits to existing bank messaging

Through the new adapter, participating institutions can initiate tokenized deposit activity on Swift’s blockchain ledger using payment formats already embedded in bank systems. IBM said digital assets can move around the clock through the ledger before final settlement occurs through existing banking infrastructure.

Swift’s architecture separates payment execution from final settlement. Its ledger records and coordinates interbank payment commitments, while banks retain control of their assets, funding and keys. Settlement can continue through real-time gross settlement systems, correspondent banking arrangements or other agreed mechanisms.

The ledger uses an Ethereum Virtual Machine-compatible architecture based on Hyperledger Besu. Swift operates the shared orchestration layer, while participating banks continue using their existing compliance processes and payment applications.

IBM’s integration relies on ISO 20022, the financial messaging standard Swift completed migrating its cross-border payment network to in November 2025. The adapter is intended to let banks connect digital transactions with existing operational processes instead of replacing their payment messaging stack.

Swift ledger has 17 banks preparing tokenized payments

Swift declared its blockchain ledger ready for initial use in July after nine months of development work involving more than 40 financial institutions. Seventeen banks from six continents entered its first group preparing live tokenized deposit transactions.

Participants include ANZ, BNP Paribas, BNY, Citi, DBS, First Abu Dhabi Bank, FirstRand, HSBC, Itaú Unibanco, Lloyds Bank, Mashreq, MUFG, OCBC, Standard Chartered, UBS, UOB and Wells Fargo. Swift said the initial use case centers on 24/7 cross-border payments using bank-issued tokenized deposits.

In related coverage, crypto.news reported on the Swift ledger rollout involving 17 global banks after the infrastructure entered its first deployment phase in July.

Crypto.news later reported that HSBC and Standard Chartered completed a live interbank transaction through the ledger in August. The transaction connected the banks’ separate tokenized deposit systems while final settlement remained on existing banking rails.

Digital asset infrastructure provider Taurus has connected its custody and tokenization products to the same Swift infrastructure. Crypto.news reported in August that Taurus integrated with Swift’s tokenized deposit ledger, giving banks another route into the network.

IBM on-premises beta removes the public-cloud dependency

Alongside the Swift connection, IBM has opened Digital Asset Haven to an on-premises beta designed for IBM Z and IBM LinuxONE systems. The deployment keeps the software layer and key-management infrastructure inside the client’s own data center, without requiring public-cloud infrastructure.

Banks can use the deployment for assets including stablecoins and tokenized deposits. IBM said clients can install the platform on compatible IBM hardware already in their environments or add capacity based on operational requirements. The same architecture, APIs and workflows used in its SaaS and Hybrid SaaS products remain available in the on-premises version.

For key protection, IBM uses Crypto Express hardware security modules embedded within its infrastructure. Confidential computing and environment partitioning can separate production, testing and development systems, while IBM Offline Signing Orchestrator supports cold-storage processes.

Structured key ceremonies form another part of the beta. IBM said organizations can use formal processes for generating root certificate authority keys and produce audit documentation for regulators.

IBM said qualifying configurations can achieve 99.999999% availability, but the company specifies that the figure comes from internal measurements and projections using a defined hardware and software configuration. IBM states that other configurations may produce different availability results.

Digital Asset Haven originally launched with support for more than 40 connected public and private blockchains. Its existing services include programmable transaction approvals, wallet controls, HSM and multiparty-computation key management, compliance integrations and transaction monitoring.

IBM and Swift move from testing toward bank deployment

Demand for payment modernization remains part of the companies’ case for the new infrastructure. J.P. Morgan Payments reported that 93% of financial institutions are modernizing their payments infrastructure, citing investment in core systems and new payment products among current priorities.

Tom McPherson, general manager of IBM Z and LinuxONE, said financial institutions increasingly need traditional and tokenized assets to operate alongside one another. He said IBM’s Swift connection and on-premises deployment are intended to give regulated institutions more control over digital asset operations. IBM cautioned that statements concerning future product direction “are subject to change or withdrawal without notice.”

Institutions interested in the on-premises beta can currently join IBM’s waitlist. IBM’s product page describes SaaS, Hybrid SaaS and on-premises deployment as options for financial institutions operating wallet, transaction, governance and key-management services.

Swift is scheduled to discuss the ledger’s implementation during Sibos 2026, running from Sept. 28 through Oct. 1. Its agenda includes sessions on interoperable tokenized money, transaction capabilities and the ledger’s implementation roadmap.

Raiffeisen Bank International has built a group agreement with Bitpanda for its Central and Eastern European network. Its Austrian model is real. The 18 million customer figure measures the size of a possible rollout, not customers newly able to place a crypto order.

Raiffeisen Bank International announced a crypto deal for a network of around 18 million customers on September 23. The number is real as a measure of the bank group’s reach. It is not a count of people who gained crypto trading that day.

The bank’s release, published at 16:00 on September 23, calls its arrangement with Bitpanda Enterprise a group framework. Individual network banks will roll out services progressively to reflect local market needs. No list of launch dates or newly live subsidiaries appears in the announcement. The bank’s June 30 group snapshot counts 18.8 million customers, a more precise figure than the rounded 18 million in the headline.

That leaves a question the customer total cannot answer. How many of those people could open their banking app on September 24 and buy bitcoin through this new agreement? The published release provides no number. It does not identify a newly launched country service.

The deal covers a network, not 18 million accounts switched on

RBI says it has subsidiary banks in 11 Central and Eastern European markets. Bitpanda will supply infrastructure for those banks to offer digital assets. The operative words are will supply and can offer. Each bank’s customer rollout is a later decision, according to the announcement.

RBI’s international network directory identifies the markets as Albania, Bosnia and Herzegovina, Croatia, the Czech Republic, Hungary, Kosovo, Romania, Russia, Serbia, Slovakia and Ukraine. Five are EU members: Croatia, the Czech Republic, Hungary, Romania and Slovakia. The others are outside the EU. The distinction matters for licences and product availability. An authorization to provide a crypto service across EU member states is not an authorization for every jurisdiction in the banking network.

The release does not assign a go live date to any of the 11. Nor does a bank customer count show how many customers are adults, use a compatible app, pass a new crypto onboarding check, live in a jurisdiction where the product is offered, or choose to trade. Every one of those steps reduces the path from total customers to actual users. None can be quantified from the agreement alone.

A useful audit starts with the named market, then demands a local bank product page, a dated launch notice, terms identifying the provider and evidence that the customer can complete onboarding. A press release about a group agreement satisfies the first step only. It would be false precision to turn the 18 million ceiling into a live access estimate without the later steps.

A market-by-market status check produces a narrower finding than the headline. The network directory verifies the banks, while the partnership release verifies a shared plan. It does not connect any one of those banks to a live Bitpanda consumer product under the new agreement. These are distinct evidence states, not an assertion that a bank can never introduce one or that a local service has been ruled out.

That table is deliberately about disclosure in the announcement. It does not certify the absence of any unrelated crypto product at each bank, and it does not show that Bitpanda lacks a local licence. Its point is auditable: the company placed 11 banking markets next to an 18 million customer number without publishing an 11 market activation list. A subsequent country notice could change a row immediately.

The arithmetic of reach is therefore bounded on one side but not measured on the other. The upper number is the rounded group customer figure. The lower bound of customers newly enabled by the September announcement cannot be determined from public information, because the company did not disclose first day activation. Reporting the lower bound as zero would be just as unjustified as reporting all 18 million as active. A framework can exist before a customer sees anything new in an app.

There is a less obvious classification issue. A customer can belong to a bank group without being a retail mobile app customer eligible to open an investment account. The published total combines the group’s customer relationships across its network; the release does not provide the subset with a compatible mobile product, nor does it split corporate customers from retail customers for this partnership. Those missing pieces prevent even a reliable potential-user estimate.

The Austrian model exists outside the new CEE count

Bitpanda and RBI point to a working precedent. Raiffeisen Landesbank Niederoesterreich-Wien began offering access to Bitpanda in its banking environment in 2024. Its current customer page describes a route through the Mein ELBA app, trading from EUR 1 and recurring plans from EUR 10. The app asks a bank account holder to register for a personal Bitpanda account.

A second Austrian regional institution, Raiffeisen Salzburg, said on September 21 that its Bitpanda access had been available since August 2026. It described more than 650 crypto coins and tokens reachable from Mein ELBA. The local release says the banking app provides the route to an external provider and that Bitpanda performs the trades.

These are live product examples, not proof that an RBI subsidiary in Croatia, Romania or another CEE market is live under the September 23 framework. The corporate distinction is easy to miss because both sides use the Raiffeisen name. RBI’s own ownership diagram shows regional Austrian Raiffeisen banks owning around 61.17% of RBI, while the 11 CEE banks are its regional subsidiaries. The Austrian partnerships demonstrate a model that might be copied. They cannot be counted as launches inside the new 11 market program.

The two agreements should not be silently added together to produce a bigger customer pool. Even the 18.8 million figure is a group customer total, not 18.8 million distinct prospective crypto accounts. No customer conversion rate is supplied. Crypto.news’ initial report on the RBI deal described the reach as potential, which is the right qualification for the announced arrangement.

The app hands the customer to Bitpanda

The Austrian bank’s own terms show what a customer gets. On the Niederoesterreich-Wien product FAQ, a customer needs both a Raiffeisen account and an active Mein ELBA app. They then register for Bitpanda. The bank requires customers to be at least 18, hold a valid photo ID and reside in Austria.

The contractual split is more important than the app’s appearance. The page says customers become Bitpanda customers through the app’s Bitpanda access. It says purchases and sales take place exclusively with Bitpanda and assets are held inside Bitpanda’s structure. The bank receives a fee from Bitpanda for its access services. Austria previously fined Bitpanda EUR 70,000 under MiCA, another reason to identify the regulated provider accurately rather than describing the banking app as the trading venue. It says it is not itself providing the crypto or securities service and is not liable for Bitpanda’s performance.

That is a distribution model. The bank supplies the familiar entrance and payment account; Bitpanda provides the specialist transaction and asset service. Raiffeisen Salzburg states an equivalent limit in plain terms: it offers access, while Bitpanda handles the trading. Its product disclosure identifies Bitpanda GmbH as the provider authorized by the Austrian Financial Market Authority under MiCA.

The economics run in both directions. A bank can add an investment function without building its own full trading infrastructure. Bitpanda can reach banking customers through a channel that already has their attention. Under the Austrian arrangement, the bank is compensated by Bitpanda. The parties have not disclosed the fee formula or said whether the new group arrangement uses identical commercial terms. A separate Bitpanda infrastructure agreement with IG Europe illustrates that distribution partnerships can differ in the type of partner and customer service offered. A statement about revenue for the CEE banks would therefore go further than the public record permits.

The phrase inside the banking environment can imply a seamless handoff, but even the mature Austrian offering requires a separate Bitpanda identity. Raiffeisen’s page directs the user to the app’s Discover section, then to an individual Bitpanda registration. A registered banking customer is not automatically an approved crypto customer. Bitpanda can apply its own onboarding criteria in addition to the bank’s age, identification and residency requirements.

That is not an incidental footnote. If the bank reaches millions of users but only a fraction of them complete crypto onboarding, the actual product population will be smaller than the bank’s customer base. The difference cannot be computed by treating installation of Mein ELBA as a proxy: having the app, finding the offer, applying, being accepted and placing a first order are separate events. The September release reports none of those figures for the new partnership.

The fee disclosure supplies another reason to keep roles straight. The Niederoesterreich-Wien page explicitly says Bitpanda pays Raiffeisen for access services. It does not publish the amount or say that the bank takes a percentage of each trade. Customers are told that trading fees will be displayed before they place an order. There may be a commercial benefit to the bank if customers adopt the product, but the terms alone do not let a reporter calculate that benefit. A projected revenue figure made by multiplying 18 million by a guessed trading fee would conflate account holders, traders, volumes and a confidential commercial arrangement.

For a customer, the legal boundary matters when something goes wrong. The Austrian FAQ says the bank does not take responsibility for Bitpanda’s service. That language is not a finding that a customer has no protection, and it cannot be copied into the terms of a not yet launched RBI subsidiary. It does show that bank branding and legal responsibility can sit in different places. A country launch should be read from its own contracts before a reporter tells customers whom to contact about execution or assets.

A bank app does not mean a bank holds the coins

The distinction affects what users can do after buying. The Austrian product page says transfers of assets from another crypto exchange into the app’s Bitpanda service are not possible. It advertises immediate movement of funds through the linked Raiffeisen account, but that does not imply an unrestricted crypto wallet integrated into the bank account. Trading fees appear before an order is confirmed.

The bank’s page places Bitpanda branded stock and commodity offerings next to crypto, then notes that those branded products are derivatives, not direct ownership of the shares or commodities. The point is not that every product has the same legal form. It is that the menu inside a bank app can contain several distinct agreements, issuers and risk exposures. The app’s single interface does not turn them into bank deposits.

This is the detail to seek when the first CEE subsidiary announces its own launch. Which legal entity contracts with the customer? Who has custody of the crypto asset? Does the app permit transfers to an outside wallet? How are trading fees shown? Will the customer have to open a separate Bitpanda account? The Austrian answer is documented. The CEE answer has not been announced market by market.

The existing arrangement gives a workable reporting test because an advertised service leaves traces: a product page, onboarding criteria, provider identity and terms. Counting those traces is more informative than counting a bank’s total customers. It can be repeated when each local RBI subsidiary makes an announcement.

A good rollout count needs a consistent definition. A bank announcing that its app has a Bitpanda tile is a narrower milestone than customers being able to complete an order. A registration path open to a small pilot group is narrower than availability to all eligible retail customers. A countrywide statement is narrower again than a reported active customer count. If RBI eventually reports a single group adoption figure, the methodology will matter: users who clicked through, accounts opened at Bitpanda and customers who actually purchased an asset are different populations.

The Austrian pages show why the last step is not assured by the first. A person can see Bitpanda inside Mein ELBA but be ineligible for the service because of residence or age, or decide against registering. A completed registration need not lead to a trade. A successful trade need not imply a customer moved assets outside Bitpanda. Each funnel stage has a different question attached. Bank announcements tend to state the broadest one because it makes the partnership legible. Financial reporting needs the narrowest verifiable one.

Two public figures illustrate the scale of the gap without estimating it. RBI’s 18.8 million describes existing group customers on June 30. Bitpanda’s reported 7.4 million users in 2025 describes the platform’s own base at a different date and under its own definition. Adding the two counts, or assuming their populations do not overlap, would be meaningless. Neither company has published the number of RBI customers with Bitpanda accounts through this new CEE agreement.

A disclosure by a subsidiary would supply the missing numerator. If a bank said 400,000 eligible customers could open the feature, that would show a live addressable group in that country, subject to its stated conditions. If it said 20,000 customers had registered with Bitpanda and 8,000 had traded, those would be adoption figures. Nothing in the September 23 release permits either number to be inferred. The absence is a reporting limit, not a reason to assume the commercial plan will fail.

Five EU markets do not make one regulatory market for the whole group

MiCA’s cross border service provision rule governs how an authorized provider expands to another EU member state after the required notification. RBI says just five of its 11 CEE subsidiary markets are in the EU. The remaining six include Albania, Bosnia and Herzegovina, Kosovo, Russia, Serbia and Ukraine. They do not become part of an EU crypto licence by virtue of their parent’s headquarters in Vienna.

That does not prove Bitpanda cannot serve customers in those countries. It means separate local analysis is required, and the September 23 release has not published a common licence covering all 11. A group technology agreement can be signed in one place while the consumer product requires authorization, banking integration and customer terms in another.