you do know even when activated core wont have a walet enabled release for people straight away...
The wallet in Bitcoin Core supports segwit (it's what most people use for testing!), it just doesn't use it by default.even the segwit guide says the wallet is not and will not be publicly available to be USED on mainnet until after activation
https://bitcoincore.org/en/segwit_wallet_dev/
Quote
Upgrade Safety
End users MUST NOT be allowed to generate any P2SH-P2WPKH or other segwit addresses before segwit is fully activated on the network. Before activation, using P2SH-P2WPKH or other segwit addresses may lead to permanent fund loss
Similarly, change MUST NOT be sent to a segwit output before activation
End users MUST NOT be allowed to generate any P2SH-P2WPKH or other segwit addresses before segwit is fully activated on the network. Before activation, using P2SH-P2WPKH or other segwit addresses may lead to permanent fund loss
Similarly, change MUST NOT be sent to a segwit output before activation
you do know why segwit needs to be upstream filters and actively ban other non-segwit nodes from being upstream. this includes banning pools and their non segwit blocks from being added on after.
Lie. They do not ban non-segwit nodes.
stop trying to be clever with language.
It's not acceptable for the network topology to suddenly change when segwit activates-- can you imagine that? drop all your current connections and then form new ones hoping that the network can make a non-partitioned graph?-- that would be irresponsible. Instead, it changes its connection preference at install time, so if there were any issues they could be addressed while the user is paying attention.
let me guess instead of the word "ban".. if i said at setup the segwit node has already chosen to not prefer to let a non-segwit node be the upstream, this its not a ban. its just an avoidance from even making the connection in the first place to not require banning later.
you do know why segwit will not relay segwit unconfirmed tx's to non-segwit nodes.
Lie.let me guess due to the 'preferencial' connection at set up, the segwit node is already not connected to non-sgwit nodes to not need to worry about sending unconfirmed segwit tx's to native nodes.
...
oh and gmaxwell if all things are fine and dandy and everything is fully compatible. how about you send a segwit tx to BTCC to force into a block.. knowing that old nodes will be fine receiving the block..
show the network that evrything is backward compatible.
at worse BTCC block gets rejected and you/dcg can easily repay them $13k out of the millions of investment..for a test to thank them for wasting their time if it rejects.
atleast it will show confidence in the "backward compatibility" claims and the "nothing needs to change" claims