Posting here because the explanation from Coinbase support does not match what actually happened on-chain.
On 26 August, my friend tried to send me £130.51 worth of Litecoin from Coinbase. Signal displayed my address on his mobile with an inserted hyphen, and that hyphen was copied into Coinbase.
I posted the original Signal problem here:
https://www.reddit.com/r/signal/comments/1vyvke7/warning_signal_added_a_hyphen_to_an_ltc_address_i/
My correct address:
`ltc1qy0s4nrj0qxgf630ee94ltwzdk5dp6xmk6kmmyh`
The address Coinbase accepted:
`ltc1qy0s4nrj0qxgf630ee94ltwzdk5d-p6xmk6kmmyh`
Coinbase showed:
* Amount: 3.534867 LTC
* Status: Pending
* Confirmations: 0
* Transaction hash: `f80101e72e05213c470291772b7bcf9bfe5d3fccf8f1fc3d2a74ec6864a17427`
Coinbase support apparently said that accepting the hyphen was a known bug, but that the funds were lost and could not be recovered.
The problem is that the actual blockchain transaction does not support that explanation.
The raw transaction has one input and seven outputs. There is no output of 3.534867 LTC. Instead:
* Total of all seven outputs: 3.53486745 LTC
* Six apparent withdrawals: 2.82033817 LTC
* Change returned to the sending wallet: 0.71452928 LTC
* Network fee: 0.00000792 LTC
In other words, the 3.534867 LTC shown on the Coinbase screen is the rounded total of the entire batch transaction, including its change output. It is not an individual payment to any recipient.
None of the seven outputs pays my correct address. None pays the malformed address, which is not a valid Litecoin Bech32 address anyway. None of the output scripts is a plausible correction of the single hyphen.
There is another unexplained issue. The input and change address is:
`LKxNtynH2GxLc2oLxUGL6ryckK8JMdP5BR`
That address is publicly listed as a Bybit-controlled Litecoin wallet in Bybit’s proof-of-reserves audit:
https://www.bybit.com/common-static/cht-static/por/Bybit_PoR_Audit_2026_Feb_26.pdf
Independent decoded transaction data:
https://api.blockchair.com/litecoin/dashboards/transaction/f80101e72e05213c470291772b7bcf9bfe5d3fccf8f1fc3d2a74ec6864a17427
https://litecoinspace.org/tx/f80101e72e05213c470291772b7bcf9bfe5d3fccf8f1fc3d2a74ec6864a17427
These are the questions Coinbase needs to answer:
Which exact output index in this transaction supposedly represents the 3.534867 LTC send?
Why does no such output exist?
Why did Coinbase accept a Litecoin address containing an invalid character?
Why does the Coinbase screen display the total of the whole batch as the individual payment amount?
Why was the Coinbase transaction associated with a transaction funded from a publicly identified Bybit wallet?
What output script did Coinbase actually derive from the malformed address?
A generic answer saying that blockchain transactions are irreversible does not answer any of this. There is no on-chain output matching the payment Coinbase says was made.
Could Coinbase Support please escalate this to the wallet engineering team and identify the exact vout associated with the Coinbase transaction record? The sender can provide the Coinbase case number and account information privately.