Author

Topic: Help Request: Recover BCH in BTC segwit account (Read 135 times)

legendary
Activity: 3500
Merit: 6320
Crypto Swap Exchange
October 24, 2019, 02:47:19 PM
#4
You can try pinging out to MemoryDealers

Here:
https://bitcointalksearch.org/user/memorydealers-10310

Or on reddit:

https://www.reddit.com/user/MemoryDealers

He might be able to help.

-Dave
newbie
Activity: 2
Merit: 0
Yes, I need a BCH miner. Hoping for a lead here.
legendary
Activity: 2352
Merit: 6089
bitcoindata.science
I was reading that there is no easy solution for this.

Segwit addresses are invalid in bch network, so your transaction is non standard
https://blog.coinbase.com/a-deep-dive-into-the-recent-bch-hard-fork-incident-2ee14132f435
Quote
Allow Segwit recovery. Segwit is an address format that is valid on the BTC network and invalid on the BCH network. BCH coins are occasionally sent to segwit addresses, which, prior to this upgrade, resulted in these coins being unspendable. This upgrade changed the status of these coins from being unspendable to, in certain cases, being claimable by BCH miners. Part II provides more information on this.


-snip-

Recovering P2WPKH Segwit funds.

As we have previously mentioned, in order to spend funds accidentally sent to a P2WPKH (Pay-to-Witness-Public-Key-Hash) segwit address on the BCH network, a miner must know the hash of that address’s public key. The public key hash may be obtained directly from the owner of the address or, if the same segwit address has spent funds on the BTC blockchain, extracted from the transaction that spent the funds on the BTC blockchain.

You need the help of a bch miner. Do they use this forum?
You will have to pay for him to include your transaction
newbie
Activity: 2
Merit: 0
Description of Problem
- On Jan. 12, sent 7.27 bch from Coinbase exchange to personal Trezor1 btc (segwit) address
- No attempt to spend from address since
- btc address dusted May 18 (.00001472)

Related Addresses
- BCH: pr743ysazkurkddtl6t67f27299p2gnwpgxgemr7yy
- BTC: 3Qnaz5eMDNnKKLNuSQcUiS1T3CTeay4nFP

Recovery fee anticipated.
Jump to: