← back to the index
VT-011 Crypto exchange · Ireland 2019

Bitsane — 246,000 Users, One Overnight Vanish, No Answers

Platform
Bitsane
Est. Losses
Undisclosed aggregate (individual losses $5,000–$150,000+)
Users Affected
246,000 registered users
Status
At-Large

Summary

Bitsane, a Dublin-registered cryptocurrency exchange that had been operating since 2016, vanished on June 17, 2019. Its website went offline, its Twitter and Facebook accounts were deleted, and emails to support addresses began bouncing as undeliverable. The platform had counted 246,000 registered users and a daily trading volume of approximately $7 million as recently as March 31, 2019. Neither the named CEO, Aidas Rupsys, nor the named CTO, Dmitry Prudnikov, responded to press inquiries, appeared before any regulatory authority, or made any public statement explaining the closure. The operators have not been publicly located, charged, or identified through any confirmed legal proceeding as of the date of this report.

The disappearance followed a pattern that had become familiar in the 2019 period of exchange failures: withdrawal failures that began weeks before the final closure, support communications that cited unspecified technical reasons, and a terminal event in which all public-facing infrastructure was simultaneously deleted. Users who had held cryptocurrency on the platform — primarily XRP, Bitcoin, and other digital assets — found their balances inaccessible with no recourse pathway. The exchange had gained particular prominence as an early trading venue for XRP (Ripple), having at one point been listed as one of Ripple's approved exchanges, and a significant portion of the affected user base held XRP positions.

Individual losses documented in reporting ranged from several thousand dollars to a single documented case of $150,000 in XRP and Bitcoin held by one US-resident user. The aggregate dollar loss is not established in any public regulatory or court filing; estimates reported at the time ranged widely. The case remains unresolved: no criminal charges have been filed, no assets have been frozen by Irish or European regulators, and no recovery mechanism has been established for affected users.

Timeline

2016
Bitsane launched
Bitsane LP is registered in Dublin, Ireland. The exchange launches, initially attracting users with its early XRP trading pairs and relatively low trading fees.
2017–2018
Growth and Ripple listing
Bitsane is listed as one of Ripple's approved exchanges for XRP trading, lending the platform significant credibility and driving user acquisition among the XRP community.
March 31, 2019
Peak reported activity
Bitsane reports a daily trading volume of approximately $7 million, with 246,000 registered users as of May 30, 2019.
May 2019
Withdrawals begin failing
Users report that withdrawal requests are rejected or indefinitely pending. Bitsane support emails respond citing "temporarily disabled due to technical reasons."
June 17, 2019
Platform deleted
The Bitsane website goes offline. Twitter and Facebook accounts are simultaneously deleted. Support email addresses begin returning bounce responses. No explanation is provided to users.
Late June 2019
Press investigation
Forbes investigates the disappearance; both Rupsys and Prudnikov are unreachable for comment. Rupsys, through a Lithuanian law firm, Baltesco, later denies accessing funds and claims not to be connected to the platform — a statement that contradicts his named role as CEO.
June–July 2019
User complaints filed
US-based users file complaints with the FBI. Victims in the US and Europe organise in Telegram groups to document losses and coordinate legal and regulatory approaches.
July 2019
Internal investigation claimed
Reports indicate Bitsane's legal representation stated an internal investigation had been launched, but no findings were published and no further communications were made by the platform or its principals.
2019–2026
No resolution
No Irish or European regulatory authority initiates public enforcement proceedings. No operator is arrested or charged. No assets are recovered for users. Rupsys and Prudnikov remain unlocated by any public authority.

An XRP Gateway That Made Itself Indispensable

Bitsane's positioning as an early XRP trading venue distinguished it from the crowded field of Bitcoin-and-Ethereum-only exchanges. When Ripple's payment network began attracting significant retail interest in 2017 and into 2018's bull market, exchanges that listed XRP pairs gained disproportionate user inflows from the XRP community.

The most effective growth mechanism was inclusion on Ripple's approved exchange list. Ripple's approval carried the implicit weight of the company's brand, suggesting the exchange had met some threshold of operational legitimacy. In fact, these listings were commercial partnerships rather than audit-based certifications; the endorsement conferred association without substantiation.

By March 2019 the exchange was processing approximately $7 million in daily volume with 246,000 registered users. Many held XRP as their primary position. The exchange's functional performance gave no outward indication that the May 2019 withdrawal freeze represented anything other than a technical issue. The deletion six weeks later resolved that ambiguity definitively.

The Withdrawal Freeze and the Six-Week Window

The period between the onset of withdrawal failures in May 2019 and the platform's deletion on June 17 is the most operationally significant interval in the Bitsane case. It is the window during which users who sought explanations received them — plausibly worded technical excuses — while the platform continued to operate its trading interface and, presumably, continued to receive new deposits and trading activity from users who were not yet aware of the withdrawal problem.

This six-week interval is characteristic of exchange exit preparations. An operator who intends to close a platform and cannot or will not return customer funds has an incentive to delay the visible collapse for as long as possible: each day of apparent normal operation reduces the alarm level of users who are monitoring, gives operators time to move or consolidate assets, and extends the window before regulatory or law enforcement attention is triggered. The support emails citing "technical reasons" for withdrawal suspension served this function, whatever their origin.

When the deletion finally occurred on June 17, it was simultaneous and complete: website, Twitter, Facebook, and email, all removed at once. This coordination — a single-event removal of all public-facing infrastructure — is inconsistent with a business that experienced an unexpected technical failure. It is consistent with a deliberate decision, executed at a chosen moment, to sever all user-facing contact simultaneously. The named operators — Rupsys and Prudnikov — have never provided any account of what occurred.

The Identity Opacity Problem

The Bitsane case is instructive as an example of the minimum viable identity footprint that an operator could maintain and still attract hundreds of thousands of users. Aidas Rupsys was named as CEO and Dmitry Prudnikov as CTO, but both individuals had minimal verifiable public profiles outside the exchange itself. LinkedIn accounts were deleted at the time of the platform's disappearance. No regulatory filings in Ireland or the UK established substantive corporate details about the operation of the exchange's custodial infrastructure.

After the collapse, Rupsys engaged a Lithuanian law firm — Baltesco — to communicate through legal counsel rather than directly. The statement issued through that firm — that Rupsys had not accessed any funds and was not connected to the bitsane.com platform — was facially inconsistent with his named position as CEO of Bitsane LP, the registered entity. No further clarification was offered. Prudnikov's LinkedIn profile was deleted and he did not engage with any public or official inquiry.

A third figure, Maksim Zmitrovich, was identified as founder of a separate entity also named Bitsane Limited, which he denied was connected to the exchange. The corporate naming overlap added a layer of confusion that, intentionally or otherwise, further complicated the identification of individuals with operational control.

The result is a case with 246,000 documented victims, a named corporate entity, and two named individuals in operational roles — none of whom have faced any legal consequence. The Irish regulatory environment in 2019 did not require cryptocurrency exchanges to hold licenses, maintain customer fund segregation, or report to any financial regulatory authority. Bitsane LP was, from a regulatory compliance standpoint, an ordinary limited partnership that happened to hold cryptocurrency on behalf of a quarter-million people.

The Five Factors

01
Regulatory non-registration as operational cover
Ireland in 2019 did not require cryptocurrency exchanges to register with the Central Bank of Ireland or hold any financial services authorization. Bitsane LP was registered as an ordinary limited partnership with no obligation to meet capital adequacy requirements, maintain segregated customer accounts, or submit to any supervisory examination. The absence of registration meant no regulator had authority or visibility to intervene before the collapse — and no authority had records sufficient to support an investigation after it.
02
Third-party endorsement as trust transfer
Inclusion on Ripple's approved exchange listing transferred institutional credibility from Ripple's brand to Bitsane without any corresponding transfer of accountability. Users who found the exchange through Ripple's materials reasonably treated the listing as an implied endorsement of custodial safety. Endorsement lists of this kind — commercial in nature, not audit-based — systematically mislead retail users about the safety of listed platforms.
03
Operator identity asymmetry
The two named operators, Rupsys and Prudnikov, had a public-facing identity sufficient to attract users but a footprint too thin to support regulatory tracking when they disappeared. The threshold of identity disclosure required to open an exchange in Ireland in 2019 — essentially company registration — was far lower than the threshold required to trace and prosecute a disappearing operator. This gap between entry-level identity disclosure and accountability-level identity disclosure is a structural feature of pre-licensing crypto exchange regulation.
04
The withdrawal freeze as early warning signal
Withdrawal disablement in May 2019, six weeks before the platform deleted itself, was the definitive actionable signal. No functioning solvent exchange routinely disables withdrawals for multi-week periods citing unspecified technical reasons; the combination of withdrawal suspension and escalating support delays is the characteristic precursor pattern of an imminent exit. Users who acted on that signal in May 2019 and initiated alternative custody arrangements avoided the losses that fell on those who waited.
05
Simultaneous infrastructure deletion as irreversibility mechanism
The deletion of website, social accounts, and email infrastructure in a single coordinated action on June 17 was not merely a closure — it was a deliberate destruction of the communication channels through which users might have received information, organised, or made contact with the operators. The simultaneous deletion maximised the informational gap at the moment of maximum user distress, and it has meant that no contemporaneous communication from the operators about what happened has ever been preserved for regulatory or legal use.

Aftermath

As of the date of this report, no criminal or civil proceedings have been filed against any individual in connection with the Bitsane disappearance. No assets related to Bitsane have been frozen or recovered by any regulatory authority. The Irish Central Bank, which did not regulate cryptocurrency exchanges in 2019, did not open a public enforcement inquiry into the matter. US users who filed FBI complaints have received no documented outcome from those filings.

Aidas Rupsys and Dmitry Prudnikov remain unlocated by any public authority. The statement issued through Baltesco — Rupsys's Lithuanian legal representative — that he was "not connected to" the platform is the last publicly documented communication from anyone associated with the exchange's operation. No liquidation proceedings have been commenced in Ireland to administer the exchange's corporate estate or distribute any recovered assets.

The European Union's Markets in Crypto-Assets regulation (MiCA), which entered into force in stages from 2023, imposes mandatory authorization requirements on crypto-asset service providers operating in EU member states, including Ireland. Under MiCA, an exchange operating as Bitsane did would be required to hold authorization from the national competent authority, maintain minimum capital, and segregate client assets. The regulatory architecture that permitted the overnight vanish of a 246,000-user exchange no longer legally exists within the EU — though effective enforcement against operators who have already disappeared remains a distinct practical challenge.

Lessons

  1. Withdrawal failures that persist beyond 48 hours with only technical explanations from exchange support are a structural warning sign, not a routine service interruption; any custodial position held on an exchange that cannot process withdrawals should be treated as at risk until the position is confirmed cleared.
  2. Third-party endorsement listings — by token issuers, industry associations, or other market participants — should be understood as commercial associations rather than safety certifications; the due diligence performed for an endorsement listing is not equivalent to an independent custody audit.
  3. An exchange that holds cryptocurrency for hundreds of thousands of users should be subject to the same identity verification, capital adequacy, and custody segregation requirements as any other financial institution holding client assets; the absence of these requirements in pre-licensing jurisdictions does not reflect a considered safety judgment — it reflects regulatory inaction.
  4. The coordinated deletion of all public-facing infrastructure in a single action is an irreversibility mechanism: it destroys evidence, cuts communication, and maximises the time before affected users can coordinate; platforms in a withdrawal freeze that delete support channels should be reported to financial crime authorities immediately, not after confirmation of the fraud.
  5. Regulators in jurisdictions where crypto exchanges operate without licensing should establish a minimum-notice closure requirement, analogous to those applicable to deposit-taking institutions, so that users have time to withdraw funds before a platform ceases operations; Bitsane's six-week withdrawal freeze was a window that properly empowered regulators could have used.

References