This post was flagged by the community and is temporarily hidden.
1 Like
The address actually encodes a smart contract bytecode. For P2PKH addresses, they work the same on both BTC and BCH because they encode the same kind of smart contract (require public key and signature to spend coins), so in that case you could just import the BTC seed in BCH wallet and get access. In case of P2PKH and since your wallet is custodial, the coins moving would mean this Narnia wallet operator swept your coins (because they have the wallet’s seed) - so open a ticket with them.
If it was SegWit address, then it works a bit different - only miners can sweep.
Problem is, SegWit addresses encode smart contract that is executed one way on BTC (require segwit contract validation) and other way on BCH (no extra validation needed). This is because SegWit was a soft fork - introduced additional consensus rules without breaking any old rules - it overloaded old P2SH addresses (addresses recognized by both networks) with additional rules, rules not recognized by BCH.
This means that if you accidentally send BCH to SegWit then any miner can sweep it.
If your address was SegWit that means some miner already swept it. In that case, look up the block that had the TX mined and see which pool mined it. Then, try to contact them. They’re under no obligation to give you the coins back, because those coins are fair game on BCH, but some pools do help users get it back for a fee.
2 Likes
@bitcoincashautist already gave a great response. But please keep in mind that this is not a help forum.
Sorry guys. Wasn’t sure in which topic to add the comment. But massive Thanks to @bitcoincashautist for his reply. Its more info than Ive been able to gather from anywhere else, so thanks!. I’ll PM you directly