New answers tagged

0

If your address is a SegWit 3... address as Murch said, then you would have to Make a transaction from the wallet (for this, you need to send a little amount of BTC sent to the address) Find a miner that you can trust (Reddit? r/bitcoincash) and give them the TXID They'll DEDUCT a percentage fee (don't pay them! that would sound like a scam) before sending ...


0

The only one that can help you is CashApp, since you locked your funds to a key they control. AFAIK, CashApp uses segwit addresses, and BCH does not support segwit, so recovery would require a bunch of additional (likely manual) intervention. You'll have to negotiate with them.


0

The value of the transaction is irrelevant to the transaction fee. Because altcoins have fewer users and thus see much fewer transactions, altcoin transactions with low fees are confirmed, as there is no competition. We saw the same thing with Bitcoin before it became popular :)


1

you should check in history/activity when your btc was sold. Btc forked to bch and bchscv so your btc became all 3. if you had 0.2btc then you also have 0.2 bch (at current price that is about the amount you mention) If you dont recall selling the BTC it is also possible to see what IP address was accessing your account.


0

I am picking up 2 blockchains, one for BTC and BCH? There are a vast amount of numbers that are valid Bitcoin-addresses (BTC). Most of them have never been used and never will be. Many of these same numbers are also valid Bitcoin-cash addresses (BCH) because of the way Bitcoin Cash was created. So your address is a valid address in at least four different ...


2

No, BCH and BTC transactions were never replayable to the other network. Starting with the very first BCH block, all BCH transactions were required to use a different SIGHASH_FORKID than used in BTC. This mandatory replay-protection causes BCH transactions to appear invalid to BTC clients, and vice versa, BTC transactions to appear invalid to BCH clients. ...


1

No, there is no such problem. When BCH developers thought about introduction replay protection, they first agreed on the OP_RETURN-based one. Then they changed their minds and decided to use the better SIGHASH_FORKID-based one (see details about BCH replay protection). Their first replay protection wasn't removed. It expired with block 530,000. After that ...


Top 50 recent answers are included