Gemini Set Litecoin Trading and Delayed Bitcoin Cash Over Fork Risk

Gemini announced on October 12, 2018 that it would add Litecoin custody and trading, making LTC the fourth digital asset supported by the New York trust company after bitcoin, ether and zcash. Litecoin deposits were scheduled to open on October 13 at 9:30 a.m. Eastern Daylight Time, with trading due to start on October 16 at 9:30 a.m. EDT.

The same notice said Gemini had intended to announce Bitcoin Cash support but postponed it because one or more possible mid-November forks created unresolved operational risk. The paired decisions mattered because they showed two sides of institutional crypto access in 2018: regulatory authorization could widen a supervised exchange’s asset menu, while protocol uncertainty could still stop a launch.

Authorization preceded the listing

The New York State Department of Financial Services had authorized Gemini on May 14, 2018 to offer custody and trading for Litecoin and Bitcoin Cash as potential future offerings. That earlier authorization is important to the chronology. October 12 was Gemini’s product announcement and launch schedule for Litecoin, not the date on which the regulator first approved the asset.

Gemini said it would open four markets: LTC/USD, LTC/BTC, LTC/ETH and LTC/ZEC. That gave customers routes between litecoin and dollars as well as the three crypto assets already available on the platform. It also placed custody and execution inside a limited-purpose trust company subject to continuing New York supervision.

The regulatory record did not certify Litecoin’s price, investment merit or technical security. DFS authorization concerned Gemini’s provision of custody and trading services. The department said virtual-currency applicants were reviewed for anti-money-laundering, capitalization, consumer-protection and cybersecurity standards. Those controls addressed the regulated intermediary; they did not remove the market and protocol risks of the asset itself.

Bitcoin Cash exposed the protocol boundary

Gemini’s Bitcoin Cash delay made that distinction concrete. The exchange said uncertainty around possible hard forks in mid-November included forks that might lack the replay protection it required for safe support. In a chain split, replay protection is intended to prevent a transaction valid on one resulting chain from being repeated unintentionally on another.

Without adequate safeguards, an exchange handling deposits and withdrawals across a disputed split could face ambiguity over which chain it supported and whether customer transactions might be reproduced. Gemini therefore said it would wait until late November, after the possible forks, to evaluate the ecosystem’s health.

That was a company risk assessment, not proof on October 12 that a particular fork would occur or that every proposed implementation lacked protection. It also did not revoke the earlier DFS authorization for a potential Bitcoin Cash offering. The announcement established only that Gemini was unwilling to activate the service on its original timetable.

What the October 12 record establishes

The verified development was a scheduled expansion, not completed trading. Litecoin deposits had not opened when Gemini published the notice, and the first trades were set for four calendar days later. CoinDesk contemporaneously confirmed the timetable, four trading pairs, regulatory approval and Bitcoin Cash postponement.

No event-day price, return, volume or market-share claim is made here. The available primary records document authorization and an exchange launch plan, but they do not establish a causal Litecoin market reaction or quantify expected customer demand.

For institutions and retail customers seeking a supervised venue, the announcement broadened prospective access to a long-established crypto asset. Its larger significance was procedural: asset support depended on both permission from the exchange’s regulator and the operator’s judgment that the underlying network could be handled safely. On October 12, Litecoin cleared that combined gate; Bitcoin Cash did not.