XRP Ledger has activated its fixCleanup3_2_0 amendment, making version 3.2.0 the minimum software release required for nodes to remain compatible with the mainnet.

XRP Ledger activates fix with 85.71% support

XRPScan data shows that fixCleanup3_2_0 is now active after securing support from 30 of the 35 trusted validators that participated in the vote. Five validators opposed the amendment.

XRPL amendments that change transaction processing must maintain at least 80% support among trusted validators for two consecutive weeks before activation. The latest proposal cleared that requirement with 85.71% consensus.

Activation immediately affects infrastructure operators running older software. Nodes on version 3.1.0 or below are now “amendment blocked,” meaning they cannot follow the updated rules governing validated ledgers.

“The fixCleanup3_2_0 amendment is now active. With this, all nodes running version 3.1.0 and below are amendment blocked until they upgrade to 3.2.0. Please take action to ensure service continuity,” XRPScan said.

The warning applies to exchanges, wallet providers, payment services, developers and other businesses that operate their own XRPL infrastructure. Users holding XRP in self-custody wallets do not need to change their tokens or move funds because of the amendment.

What fixCleanup3_2_0 changes

The amendment introduces a package of protocol corrections included in the XRP Ledger 3.2.0 release. It does not add a new user-facing product or alter XRP’s supply.

Among the changes are precision and rounding fixes for Single Asset Vaults and the Lending Protocol. The package also corrects an invariant affecting valid offer deletions on the Permissioned DEX.

Other changes validate non-canonical Multi-Purpose Token amounts, add a zero DomainID check for permissioned domains, and introduce an invariant that checks whether deleted accounts leave directly accessible ledger objects behind.

XRPL data cited after activation showed that 105 validators, or 70% of the network total, were running version 3.2.0. Another 35 validators, representing 23.33%, remained on version 3.1.3.

Among other nodes, 582, or 68.88%, had adopted version 3.2.0, while 228 nodes, or 26.98%, were still using version 3.1.3. Operators on 3.1.3 are above the version range identified in XRPScan’s amendment-block warning, although XRPL developers have urged all operators to complete the 3.2.0 migration.

Version 3.2.0 renames rippled to xrpld

Released in mid-June, version 3.2.0 also changed the name of XRPL’s reference server implementation from “rippled” to “xrpld.” The rename follows XLS-0095, a proposal designed to link the software’s identity more directly to the XRP Ledger.

The change extends beyond the server executable. Operators upgrading from version 3.1.3 must rename the configuration file from rippled.cfg to xrpld.cfg and revise related database paths, packages, scripts, deployment settings, service definitions, and metadata.

XRPL’s migration documentation provides steps intended to preserve existing node data while replacing the former naming conventions.

Developers describe version 3.2.0 primarily as a cleanup and maintenance release. It retires amendments that had remained active for more than two years and continues dividing the libxrpl codebase into smaller modules to support future maintenance.

XRPL upgrade follows $2.6B RWA increase

The activation comes as the ledger handles a growing amount of tokenized real-world assets. As crypto.news reported on July 26, XRPL added about $2.6 billion in RWA value over six months, excluding stablecoins.

That ranked the network second for net RWA inflows during the period, behind BNB Chain’s roughly $3 billion. Stellar followed with about $2.1 billion.

XRPL’s combined distributed and represented RWA value reached approximately $4.38 billion, while stablecoins added another $995.12 million. The wider total exceeded $5.37 billion.

For US businesses using XRPL for tokenized assets, payments, or exchange infrastructure, the amendment creates an operational requirement rather than a new regulatory rule. Operators must keep their server software compatible to avoid service interruptions as activity on the network expands.

Barclays analyst Benjamin Budish estimates Coinbase processed roughly $152 billion of trading volume during the quarter, well below the Street’s expectation of about $178 billion. He expects adjusted EBITDA to come in roughly 3% below consensus, pointing to weaker blockchain rewards and institutional trading revenue.

Clear Street’s Owen Lau also lowered estimates, projecting approximately $160 billion in trading volume and $301 million in adjusted EBITDA after weaker-than-expected retail activity.

Benchmark’s Mark Palmer similarly reduced his EBITDA forecast to $377 million, while Compass Point expects revenue to slightly miss consensus but believes EBITDA will be roughly in line with expectations.

Coinbase still rises and falls with crypto trading activity, a dependency that has become more apparent over the past year. The company has spent heavily to diversify revenue through stablecoins, derivatives, payments, tokenization and its Base blockchain. Those businesses continue to grow, but they remain relatively small compared with transaction revenue.

Subscription stability

One area where analysts are more constructive is subscription and services revenue.

This segment includes interest income from USDC, staking rewards, custody fees, Coinbase One subscriptions and institutional services. Because those businesses are less tied to daily trading volumes, analysts expect them to provide a cushion against weaker transaction revenue.

Trade certainty for curiosity

The Ethereum Foundation (EF) has appointed longtime ecosystem contributor pcaversaccio (known as “pc”) to its board, expanding the group’s leadership as it continues to refine the governance of the organization behind the world’s second-largest blockchain.

pc, a security researcher and co-founder of the emergency response initiative SEAL 911, joins the board for an initial one-year voluntary term. He has also served on the EF’s Silviculture Society, an advisory group that provides informal guidance on preserving the foundation’s core principles, including censorship resistance, open source development, privacy and security.

The appointment brings the Ethereum Foundation’s board to four members: President Aya Miyaguchi, Ethereum co-founder Vitalik Buterin, Swiss legal counsel Patrick Storchenegger and pcaversaccio.

The board is responsible for setting the EF’s strategic vision and ensuring management’s decisions remain aligned with the organization’s values, accordinfg to the Foundation. It also serves as a “security council” tasked with safeguarding the foundation’s mission and ensuring compliance with the laws of Switzerland, where it is currently based.

Hungary is easing part of its previously strict crypto framework, repealing a requirement that forced certain transactions to pass through an additional validator. The move comes as crypto services in the country restart under the European Union’s MiCA regime, with CoinCash preparing to resume operations after receiving MiCA authorization.

According to Hungarian tax and legal outlet Ado.hu, Parliament voted to remove the crypto validator obligation, eliminating mandatory third-party approval for specific crypto transaction flows. Finance Minister Kármán András said the government rolled back the rule because earlier regulations disrupted Hungary’s crypto market and led some providers to stop operating locally.

Key takeaways

• Hungary has repealed its crypto validator requirement, removing an extra transaction-level approval step for certain crypto conversions.
• The change is expected to reduce friction for compliant service providers while MiCA licensing and broader compliance duties remain in force.
• CoinCash is positioned to restart services after the National Bank of Hungary authorized its operator under MiCA on July 20.
• Hungary previously introduced a validator process via a 2024 crypto assets law, with requirements taking effect on July 1, 2025.

What Hungary’s validator rule required—and why it mattered

Hungary’s validator requirement was introduced through the country’s 2024 crypto assets law, creating a separate validation process alongside the EU framework. As described by the Hungarian legal database, the rule took effect on July 1, 2025 and required a licensed validator to verify details before issuing a compliance declaration for certain crypto conversions.

Those checks included information tied to the origin of crypto assets, wallet ownership, and customer data. In practical terms, the validator step added another hurdle for crypto service providers operating in Hungary—on top of MiCA obligations already covering authorization and ongoing compliance.

Industry implications were significant: the extra approval layer increased operational complexity and compliance costs, and some platforms chose to suspend services rather than continue under the combined set of rules.

MiCA still sets the baseline, but the approval step is being reduced

The validator repeal does not remove MiCA as the governing structure for crypto-asset service providers. Hungary’s broader approach has been to align its national rules with EU requirements while tightening implementation timelines.

Notably, earlier reporting highlighted that Hungary applied a shortened MiCA transition period for crypto asset service providers (CASPs), requiring compliance by July 1, 2025 rather than the EU’s maximum transition deadline of July 1, 2026. That accelerated schedule, combined with Hungary’s additional transaction-level validator process, left less room for gradual operational adjustment.

Minister Kármán framed the repeal as a response to market disruption. In a Tuesday Facebook post, he argued that “many players” had terminated Hungary-related crypto services due to the “negative and market-shaking regulations,” while he also suggested the market is now showing signs of recovery.

CoinCash gets MiCA authorization as it prepares to restart

While Hungary removed the validator requirement, MiCA authorization remains the key gateway for resuming compliant operations. CoinCash’s path illustrates how companies are adapting to the EU framework.

CoinCash’s operator, Tiwala Solutions, received authorization from the National Bank of Hungary under MiCA on July 20, according to a company announcement reviewed by Cointelegraph. CoinCash said it is the first and only Hungarian company authorized directly by the National Bank under the EU framework.

CoinCash co-founder Gábor Galántai stated this in a LinkedIn post on Friday. The authorization covers a broad set of regulated activities, including custody, crypto-to-fiat and crypto-to-crypto exchange, transfers, investment advice, and portfolio management.

The company also indicated it completed a months-long compliance review before obtaining approval. CoinCash had voluntarily paused operations in December 2025 while preparing to meet MiCA requirements, and it now plans to gradually resume services. The company added that it intends to expand beyond trading into additional MiCA-regulated offerings.

What changes now—and what investors should watch

From a market-structure perspective, Hungary’s validator repeal reduces an additional layer of friction for certain crypto transactions. For users, that can mean smoother processing by authorized providers; for operators, it can lower operational complexity by removing an extra transaction checkpoint.

However, the repeal leaves open the bigger question of how quickly the local market will normalize after a period of provider retrenchment. CoinCash’s restart plan is a tangible indicator of compliance momentum under MiCA, but other firms may move more slowly depending on their own licensing status and operational readiness.

Readers should watch for whether more Hungary-based or Hungary-serving platforms resume activity, and whether regulators continue to refine how MiCA transition and national requirements interact—especially as the removed validator step no longer offsets, or compensates for, the accelerated compliance expectations that previously shaped the market.

As Hungary continues recalibrating its crypto rulebook, the key uncertainty is speed: how quickly the compliance ecosystem can translate licensing into fully operational services, and whether additional rule adjustments follow the validator repeal once the market stabilizes under MiCA.

Trade.xyz, the operator of onchain perpetual markets on Hyperliquid, says it will reimburse eligible users for liquidation losses tied to a sudden “price anomaly” affecting its SK Hynix-linked contract. The announcement follows a sharp drop in the contract’s mark price after an off-chain trade was relayed through multiple independent data providers.

In a post on X, Trade.xyz stated that the SKHYNIX contract’s mark price fell to $917.25 from $1,127.90 at 23:01 UTC on Monday. It attributed the move to the way its oracle processes an external venue’s executed transaction, noting that eligibility requirements and details of the reimbursement are expected shortly.

Key takeaways

• Trade.xyz will cover eligible liquidation losses after a mark-price drop in its SK HynIX perpetual contract triggered liquidations.
• Trade.xyz said its oracle was “tracking” an external venue used as the primary South Korean pre-market and that it behaved according to specification.
• The affected contract is among Hyperliquid’s most active, with the platform reporting over $1.5 billion in 24-hour volume and nearly $600 million in open interest at the time of writing.
• Trade.xyz described reimbursement as a one-time discretionary decision and said it will review how prices are formed during extreme events.
• Hyperliquid/Trade.xyz is reportedly considering increasing the weight given to prices derived from its own order books during market stress.

Reimbursement after a mark-price break

The reimbursement plan centers on a specific event: Trade.xyz’s SKHYNIX contract mark price reportedly plunged within minutes, dropping from $1,127.90 to $917.25. According to Trade.xyz, the move was linked to an executed transaction on an external venue rather than a sudden distortion inside Hyperliquid’s own trading order book.

Trade.xyz did not disclose the number of users likely to qualify or the total amount it expects to distribute. It also said it would “announce soon” the eligibility requirements, with distributions expected “in the coming days.”

While the operator acknowledged the frustration traders can feel when liquidations occur during unusual market conditions, it framed the reimbursement as a “one-time discretionary decision.” It also signaled that the company plans to examine how its system handles price formation during extreme market events.

Why Hyperliquid’s mark price matters

On Hyperliquid, the mark price is not just a reference—it is a core input for risk controls. Trade.xyz said Hyperliquid uses mark prices to value positions for margin purposes and to determine when leveraged positions should be liquidated.

That design makes the accuracy and responsiveness of the mark-price mechanism critical. Even if the anomaly originates elsewhere, its impact can propagate quickly to trader margin calculations, particularly in highly leveraged perpetual markets.

Hyperliquid data cited by Trade.xyz indicates the SK Hynix contract is deeply liquid. On Wednesday, Hyperliquid’s interface showed the contract had produced over $1.5 billion in 24-hour volume and held nearly $600 million in open interest at the time of writing—figures that underscore why an oracle-driven disruption can quickly become a large-scale trader event.

How the anomaly appears to have transferred on-chain

Trade.xyz said the sharp move began with an executed transaction on an external market, not with trades on Hyperliquid itself. Its oracle tracks the US dollar value of one SKHX common share. The mechanism, according to Trade.xyz’s documentation, converts the underlying South Korean won price using the prevailing exchange rate.

In this case, Trade.xyz said the external print was processed by the oracle and contributed to the contract’s mark-price shift. It added that the oracle “worked as intended according to its specification,” a detail that helps clarify what the operator believes went wrong: not the system failing technically, but the market-data input producing a sudden reference-price dislocation.

The operator also suggested that Hyperliquid may adapt its approach for future stress periods. Trade.xyz said it is considering giving more weight to prices formed on Hyperliquid’s own order books, arguing that Hyperliquid’s internal liquidity and market signals may better reflect tradable conditions during volatility.

Perpetuals with external feeds under HIP-3

Trade.xyz’s SK Hynix market runs under Hyperliquid’s HIP-3 framework. HIP-3 enables perpetual contracts tied to assets with external price feeds, allowing builders to launch products when the primary pricing reference comes from venues outside the on-chain trading system.

Trade.xyz previously accounted for more than $22 billion of HIP-3’s first $25 billion in cumulative volume, according to coverage referenced in the source material. It has also launched an officially licensed S&P 500 perpetual using S&P Dow Jones Indices data, illustrating how HIP-3 has been used to bring traditional benchmark feeds into onchain perpetual trading.

This case highlights a central trade-off of external-feed perpetuals: while they expand asset coverage, they can also import volatility or idiosyncratic prints from other venues into margin and liquidation machinery. In moments when an off-chain venue’s execution data diverges sharply from the prevailing onchain trading picture, mark-price-based liquidation thresholds can behave abruptly.

What traders should watch next

For now, the key uncertainties are operational: how Trade.xyz will define eligibility for reimbursement and how it will adjust the balance between external feeds and Hyperliquid order-book prices going forward. Traders in external-feed perpetuals may want to pay close attention to any announced changes to oracle weighting and to monitoring around mark-price calculations during extreme events.

BNY, one of the world’s largest custodian banks, is taking a major step toward blockchain-based financial infrastructure by moving fund ownership records onchain.

The New York-based institution will launch a blockchain-based version of its transfer agency business, which manages fund ownership records and investor transactions, the Financial Times reported Wednesday.

“We think of BNY as modernizing a function that sits behind every single fund transaction by bringing the books and records on-chain,” Carolyn Weinberg, BNY’s chief product and innovation officer, reportedly said.

The move follows BNY’s broader digital asset expansion, including its European regulatory progress under the EU’s Markets in Crypto-Assets (MiCA) framework, as the bank positions itself for the next phase of institutional blockchain adoption.

What are transfer agency records?

Transfer agents are financial service providers that maintain official records of who owns shares in investment funds. They handle tasks such as processing investor transactions, issuing and redeeming fund shares, updating ownership records and supporting communication between funds and investors.

These records form part of the behind-the-scenes infrastructure that allows investment funds to operate. Traditionally, ownership information is stored across multiple systems used by fund managers, custodians and other market participants, requiring frequent reconciliation.

Related: USDC issuer Circle to acquire nearly 1,000 IBM blockchain patents

According to the report, BNY’s transfer agent services cover roughly $8.6 trillion in assets across 7.6 million accounts. The company, which oversees more than $59 trillion in assets under custody and administration, will reportedly maintain its traditional transfer agency operations alongside the new digital platform.

Baillie Gifford among early users for tokenized funds

By moving transfer agency records onchain, BNY aims to create a shared source of information for market participants, reducing reliance on separate databases and manual reconciliation processes.

Early users of BNY’s digital transfer agency reportedly include Edinburgh, Scotland-based asset manager Baillie Gifford, which plans to use the platform for what it described as the first “fully native” United Kingdom-regulated tokenized fund. BlackRock and BNY Dreyfus money market fund and cash management business are also expected to use the service for upcoming tokenized funds.

The firm has roughly $261 billion in assets under management, according to its website.

Related: Hong Kong prepares banks for quantum threats amid tokenization push

“What we have in the blockchain is a shared source of record-keeping between the participants,” Theo Golden, Baillie Gifford’s head of digital assets, said. “We agree that this is the source of truth when people are dealing with the asset that this is monitoring,” the executive said.

BNY has not disclosed which blockchain network will support the new platform. Cointelegraph approached the company for comment regarding the report but did not receive a response by the time of publication.

Magazine: The 5 types of real world assets being tokenized fastest onchain