Re: Post your SegWit questions here - open discussion - big week for Bitcoin!
So I guess no one noticed the blacklisting in the new 0.13.1 code?
So if you run 0.13.1 you will find that it will connect to other 0.13.1 nodes on the network, but not to 0.13.0 or lower.
i.e. you are disconnecting yourself from the majority of pools, mining transactions on the network.
At the moment that's ~75% of blocks.
Your txns can of course get to the pools via other roundabout ways, but you wont connect to them directly.
Yeah even the main core developers implement blacklists without making it clear they exist
So if you run 0.13.1 you will find that it will connect to other 0.13.1 nodes on the network, but not to 0.13.0 or lower.
i.e. you are disconnecting yourself from the majority of pools, mining transactions on the network.
At the moment that's ~75% of blocks.
Your txns can of course get to the pools via other roundabout ways, but you wont connect to them directly.
Yeah even the main core developers implement blacklists without making it clear they exist
It looks like "blacklisting" might be an exaggeration here... nonetheless, the soft fork is a touchy subject and it's for reasons like this. Suddenly Segquit blocks are "higher quality" than non-Segquit ones.
I see that the Segwit adoption rate has flatlined at around 25%. I'm not running it, I'm running core 0.12. Reason being (sorry devs, I respect, but...), Segfault is a NERD SOLUTION: hugely overcomplicated, risky, and unnecessary. It's like going to get a car at a dealer and coming home with a portable automotive manufacturing plant! Now before anybody buttrages on me, please understand that I've been a huge critic of the lame code forks like Classic, XT, and Unlimited, etc (heck, look at my username!). Those code forks were done with the worst of intentions by the worst devs. However, the blocksize needs to increase... I guess we're in a "stonewall period" right now where nobody wants to scream about blocksize anymore, all the cards are on the table, and everything that can be said has been said. Antonopolous says a compromise is near and I hope he's right...
Whoever is filling the mempool with sh*t will probably be able to do that even if the blocksize is 4MB, so that will be the next problem to solve. Ironically, if they are spamming, which is what I see, they're currently pricing themselves out of the market - fees are rising rapidly! I suspect it's "churn", people pumping the price... Thanks for listening.