Quote from: ebliever on March 27, 2017, 07:22:28 PM

I'd point out, though, that Segwit does alleviate the immediate TX pressure,

no it doesnt..
its worth you trying to atleast learn how segwit actually works

heres things to think about

Quote from: franky1 on March 26, 2017, 06:04:03 AM

segwit promises: 2mb-4mb block promise when activated.
segwit reality:at activation.. nothing.. people using standard UTXO (native/legacy tx keypair) will have their data stuck in the base block limit of 1mb (no gain for them). only segwit utxo spenders(users who have funds on segwit tx keypair) will have part of the tx data outside the base block.
meaning it requires people to spend their native utxo and move the funds into segwit keys.. and then when they spend the segwit UTXO then they are helping with the ratio inside and outside the base block.*

segwit promises: malleability fix promise when activated.
segwit reality:at activation.. nothing.. people using standard UTXO (native/legacy tx keypair) will have their data stuck in the base block and can still do malleability. only segwit utxo (segwit tx keypair) will move part of the tx data outside the base block. meaning it requires people spend their native utxo and move the funds into segwit keys.. and then when they spend the segwit UTXO then they are helping with the not malleating because they are disarmed.*

segwit promises: quadratic sigop fix promise when activated.
segwit reality:at activation.. nothing.. people using standard UTXO (native/legacy tx keypair) will have their data stuck in the base block and can still do sigop spam. only segwit utxo (segwit tx keypair) will move part of the tx data outside the base block. meaning it requires people spend their native utxo and move the funds into segwit keys.. and then when they spend the segwit UTXO then they are helping with the not sigop spamming because they are disarmed.*

*the issues:
trying to move 46mill native UTXO.. is a laugh to think will be 100% accomplished, especially in any rational time or ability to achieve
thinking 100% of users will voluntarily use segwit keys and stick to segwit.
thinking that malicious spammers/attacker would voluntarily use segwit keys, voluntarily disarming and de-spamming themselves.. is the opposite of the motives of said malicious spammers.

infact segwit opens up new attack vectors for these spammers. which will make it even harder for people to move funds across. and all this having to move funds just to try disarming themselves will be ADDING to the mempool spam

dont expect to get anywhere near 2mb of 'capacity' just like we didnt get 7tx/s in bitcoin 2009-2017 even when maths estimations suggested it was possible

segwit promises: keeps node costs down
segwit reality: 2mb of data is still 2mb of data for a full node no matter if the signatures are in the middle of a tx or end of a tx.. yea you can claim enabling prunned or no witness mode.. but then your no longer the upstream tier of a full node. and just part of the downstream lower tier cesspools of not full data nodes, thus might aswell just be spv/litenodes. they are not counted/treated as "full nodes"

segwit promises: keeps node counts up
segwit reality: enabling prunned or no witness mode.. they are no longer the upstream tier of a full node network. and just part of the downstream lower tier cesspits of not full data nodes, thus might aswell just be spv/litenodes. they are not counted/treated as "full nodes"
moving non segwit nodes off the network. again drops the full node count.