The announcement was SegWit2X signaling, but if you look at the pic you would realize it still UASF SegWit1X, just look at the feed coming through
You are viewing a single comment's thread from:
The announcement was SegWit2X signaling, but if you look at the pic you would realize it still UASF SegWit1X, just look at the feed coming through
Feed from where though? From what I can see it is showing that some of the peers connected to that node are signalling UASF. Could be a bug, could be an anomaly. For example when I use the getpeerinfo command I get a completely different result. The only way to know overall is to check sites like Coindance.
you can check this site http://segwit.co/ be careful with downloading anything though, you just never know, once its UASF nothing has changed.. you said it Could be a bug I thought Bitcoin was immune to those things, if not well that's interesting... I have never used Coindance but I would check it out, send me a direct link....there is a lot of noise around until I see SegWit2X i would believe it...you can also check in with the miners, and see who's going with what https://bitcoincore.org/en/segwit_adoption/ I am learning this stuff so the bug thing is abit new for me
I don't need to check there as there are multiple sites that show the same thing as CoinDance. Why use sites if you are not sure if they are trustworthy?
https://coin.dance/blocks
the segwit.co sites are legit, I just don't download anything, I just take a screen shot... I had some bad experience with crypto so I don't even trust sites even when my anti-virus says secure... i usually just screen shot those things, but thanks for the link I would check it out...sorry for the late response, just getting lunch break