submitted by /u/ToTheMempoolGuy [link] [comments] |
source https://www.reddit.com/r/btc/comments/jw3iyd/bch_is_reenabled_on_bitpay_wallet_and_copay/
This blog brings you the best Cryptocurrency & Blockchain, ICO & P2P and Exchange & Laws news. Also contains technology and research based post from all around the world every single day. Get informed! Think Future!
Hey everyone, Leading up to and since the Nov 15th fork, I've been getting my BCH ready for the split.
The intent was to sell off most if not all of my ABC coinage... While I have been relatively unsuccessful thus far, I instead have insight into how dead the ABC side of the fork is.
First off - splitting was a breeze.
In fact, there are so many nodes on the BCHN side of the fork and so few on the BCHABC side that it's almost a guarantee that your transaction won't properly broadcast to the ABC side of the fork.
Initially, I was looking at the chained transaction limit and thinking I'd need to push more than 500 transactions within the same ABC block for the coins to hit the transaction cap and split.
I was dumbfounded to find that a double move within the same block did the trick. Technically speaking - that shouldn't have worked.
Next, I booted up my ABC client to synch and see what happened...
Well it turns out that the first transaction didn't even broadcast because it didn't connect to ANY ABC 0.22.6 node. I thought "ok, cool... BCHN is doing a great job of filtering out ABC nodes... this will be easier than I thought."
So the time came to synch the client. I get to around the "304 blocks to go" mark and it just stops.
I take a look at the console and realize that ABC has only connected to peers with a block height of ~661960 - the wrong side of the fork. In addition, ABC failed to find a single ABC 0.22.6 node to properly update.
I spent the next hour disconnecting from every Unlimited 1.9.0.1 client and every client with a BCHN block height (which surprisingly includes a metric ton of updated ABC nodes as well.
After doing that, I realized that my client started with the wrong headers (which is why it says it's over 300 blocks behind)
I then realized I probably needed to scrap the headers it found and restart synching from scratch.
I booted all non-ABC clients and all clients with the wrong block height and am attempting to get a proper ABC block header synch.
Because there are so few valid clients, it will likely take days now.
On top of that, when I finally get to the point that I can transact - blocks coming every 3-4 hours means confirmation times for one of the few exchanges that actually support ABC will be astronomical.
This feels, at best, barely worth the $15/coin bounty I'm currently after.
TL;DR - In BCH, the phrase "Easy as ABC" means "ridiculously cumbersome and nearly impossible."
My heart is definitely in crypto and didn’t plan on ever selling but due to unforeseen expenses and unemployment messing up my claim because of COVID along with CA never set to reopen my job. I sadly had to sell off years of DCA. I knew this run would happen eventually and as much as I love to see it happen it’s a little bitter sweet.
Just wanted to see if anyone else has had a similar experience or if they bought back in close to what they sold out, that ship has sailed for me right now. Just patiently waiting to start my DCA process all over again and build back up!