Quote:
Originally Posted by theskillzdatklls
Segwit from what I know is a very complicated code structure and could have stuff lying around as well. also its scaling ability is pretty piss poor. 1.7x is good for what, the next month, if not already over saturated with the current market?
that said, ive said before i think both scaling functions can be deployed, ive never understood why these are all so mutually exclusive. increase blocksize, let that multiple through with sw. but core has had infinite resistance to this idea.
The code is out in the open, was one of the most widely pieces of code changed, and has been operating on Testnet for quite some time. 2.1x is what it gets you immediately, and with LN, 1000x+ scaling. All without a chain split!
BU is completely broken. It's a ticket to give miners complete control over whatever they want in the future. No competent developer or user will touch it.
Quote:
Originally Posted by vikthunder
It sounds like SegWit had a pretty big problem on test net that was causing unintended forks to happen.
Basically, non-upgraded nodes don't communicate properly with upgraded nodes, so non-upgraded nodes forked off onto their own chain. Maybe Core shouldn't be throwing so many stones from their glass house.
FUD FUD FUD FUD.
Pure bull****, vik, as expected from a BU propagandist.
Long re-orgs are extremely common on Testnet, all the time. This is nothing new. One guy with one miner can basically erase hundreds of blocks whenever he wants because no one is really mining it. Sometimes people do it for fun. Has nothing to do with SegWit.
The issue you describe- since blocks must be repackaged for non-SegWit nodes, a SegWit node cannot accept a SegWit block from a non-SegWit node (Since they don't have the full data to validate). SegWit nodes actively search for other SegWit nodes (since those are the only ones that can provide them with the complete block).
Here's what a developer said on the mailing list about it:
Quote:
Miners using 0.13.0+ will produce blocks that propagate well. This is because 0.12.x- nodes will accept those blocks, and so will 0.13.0+. Furthermore Core 0.13.0+ will use its outbound connections to connect to segwit enabled peers so that it will be relaying segwit blocks to someone. However Bitcoin Core 0.13.0+ will not request blocks from peers that are not segwit enabled (because with segwit, they will be receiving blocks without witnesses which are invalid to a segwit node), so they will not receive blocks mined by a 0.12.x- node. This means that 0.12.x- mined blocks propagate poorly, even though are valid. Because of the poor propagation, a 0.13.0+ miner can find a block at the same height which is more likely to get built upon. However, the poorly propagated block can still reach other 0.12.x- miners who can build upon it due to the low difficulty and difficulty resets, thus causing multiple chains to exist, particularly among pockets of 0.12.x- nodes. The reorgs happen when either the 0.12.x- nodes hear of the segwit blockchain that is presumably longer because it has the majority hashrate, or when people run bridges which allow 0.12.x- nodes relay blocks to 0.13.0+ nodes.
BTW, Dash is a pure scam, just a pump and dump. Roger Ver is creating drama to try to drive people to Dash (Where he clearly bought a bunch of ), so he can unload at the top and profit. The entire Masternodes system is a complete ponzi trash scam.
