franky1 | Weak | Weak | Weak | Weak | Weak | Weak | Weak | Weak |
[tr]
[td]franky1 [/td]
[td][glow=cyan,2,100]Weak[/glow][/td]
[td][glow=cyan,2,100]Weak[/glow][/td]
[td][glow=cyan,2,100]Weak[/glow][/td]
[td][glow=cyan,2,100]Weak[/glow][/td]
[td][glow=cyan,2,100]Weak[/glow][/td]
[td][glow=cyan,2,100]Weak[/glow][/td]
[td][glow=cyan,2,100]Weak[/glow][/td]
[td][glow=cyan,2,100]Weak[/glow][/td]
[/tr]
they are all missing things.
segwit148149 segwit2x are all 2merkle which is cludgy code, also doesnt limit txsigops of legacy tx's very well or uses cludgy maths to do it
the dynamic bips have issues too
like 106 for instance has crap bip of going down as well as up, which can cause blocks made before going down (thus being more then new limit) potentially getting orphaned out.. there should be no need to drop a consensus limit as that causes issues for the chain.. pools can simply do a policy blocksize drop instead
segwit+size increases still rely on developer spoon feeding/promises after X. which is still empty promises/delays
its as if devs want to promote the worse versions there are, as ways to keep the dev's in control/ or to make the devs remain relevant by always having issues for the devs to be needed to then fix later
any bip that actually gives nodes full control to not rely on dev endless requirement ends up being tossed aside
concepts i prefer
dynamics - takes the dv spoonfeeding/2year debate out of the way because NODES control size (yep i said nodes not pools)
but with other things aswell such as
1 merkle block where all keypairs sit side by side in same area
all the stuff people want new keypairs, weak/thin blocks
nodes request a UTXO set first to run in lite mode while it syncs so that people can see unspents and make tx's meaning they are not waiting a week before even being able to do anything
other things like
proper limiting sigops and bloat per tx
add a new fee priority mechanism that penalises people that spend more then once a day and reward those that dont, (yep there are ways to do it)