Exchange Ranking
Top Exchanges
24h Volume Ranking
Popularity Ranking
Exchange BTC Balance
Proof of Reserves
Decentralized Exchanges
Funding Rate
Funding Heatmap
Liquidation Data
Max Pain
Long/Short Ratio
Whale L/S Ratio
Binance/Okex/Huobi L/S
Bitfinex Margin L/S
ETF Tracker
Solana ETF
XRP ETF
Hong Kong ETF
Bitcoin Treasuries
Crypto Reversal
Ethereum Reserves
HyperLiquid Wallet Analysis
Hyperliquid Whale Watch
Large Transactions
On-chain Movement
Bitcoin ROI
Stablecoin Market Cap
Options Analysis
News
Articles
Economic Calendar
Features
Wallet
Contract Calculator
Security
Collections
Watchlist
Following
XRP XRP Healthcare announced that it will stop operations and initiate the delisting process for XRPH and XRPHAI tokens.
XRP Healthcare recently announced the closure of its business and immediately initiated the delisting process for its XRPH and XRPHAI tokens. The decision follows a series of setbacks for the blockchain-based health care startup, including a failed initial public offering and intense pressure from a long period of bear market conditions.
Technical failures and security vulnerabilities
Serious technical vulnerabilities played a central role in the company's collapse. On September 3, attackers exploited flaws in the underlying code of XRPH Wallet, damaging 4,011 user wallets and causing approximately $452,000 in damage. The stolen funds included 267,664 XRPs and tokens native to the project. Detailed analysis pointed out that the leak originated from a flaw in the random number generation process when the application generated mnemonic words, and this problem had been marked as a risk point by independent developers early in the project.
Investigators later found that the application further amplified security risks by transmitting users 'mnemonics across the network. It should be emphasized that this vulnerability has nothing to do with XRP Ledger itself, but only involves XRP Healthcare's proprietary code and its wallet design choices.
Term interpretation: Entropy in cryptography refers to the randomness of system collection and is used in algorithms that require unpredictability (such as generating a secure private key). If the entropy value in the wallet algorithm is too low, it may cause the private key to become predictable and make it vulnerable to attack.
Well-known developer Vet Goose said he himself refused to accept XRP Healthcare's funding application due to misleading information about the so-called partnership in the project document. He described the platform's technical architecture as inadequate and questioned the need for proprietary tokens, pointing out that this model was unnecessary for the proposed medical solution.
Vet Goose highlighted his concerns: "In this healthcare ecosystem, separate tokens are never needed, and technical documentation contains inaccurate statements about collaboration."
Management Response and Project Liquidation
XRP Healthcare's leadership responded that they relied entirely on external developers to secure wallets, and said they only realized the problem of mnemonic transmission after the hack became public. Management refuted criticism from senior members of the Ripple community, but failed to provide a strong technical rebuttal to address underlying code issues.
A recent announcement confirmed that the project has entered the liquidation stage and will cease all operations. As a result, the XRPH Wallet application is now permanently disconnected from the network and users can no longer access related services.
Currently, the company is discussing a deadline for withdrawing tokens with cryptocurrency exchanges. It is expected that each trading platform will determine its own specific delisting procedures and schedule for XRPH and XRPHAI assets.
XRP Healthcare was founded three years ago to use blockchain technology to create a decentralized medical ecosystem. Its closure marks the end of its goal of integrating digital assets with medical services.
Technical Review pointed out that the project's fatal mistakes were poor security practices, excessive reliance on external teams, and failure to address key warnings raised by developers since the platform's inception.
