check the CODE
legacy have the * 4..
Check the entire code not just one line of it.
A lot of things are multiplied by 4 meaning if you are multiplying the legacy transaction size by 4 to get its virtual size then it is also compared by the block size (that was previously 1) that is multiplied by 4 (turning it into 4 MB).
That still doesn't make legacy transactions more expensive than before SegWit activation. A legacy transaction with 250 byte size paid 250 satoshi fee (1 satoshi/byte) before SegWit and it is still paying 250 satoshi (1 satoshi/byte) after SegWit.
thanks for showing you now see the * 4
and yes the cludge extends beying a legacy TX to falsely make a block appear as 4mb. but there in lays the cludge.. because real data. in reality(no dont redefine reality) is that blocks are not actually physically 4mb.. and thats the rub
as for the tx sat for byte thing which you think exists..
i dunno if i should laugh or just facepalm
cores wallet does not charge based on sats per byte...
they charge based on the Weight Unit principles of cludgy code math
i just showed you an example of the lines of code that have have nothing to do with straight forward sat for byte fee discovery for legacy.. because there is no standard sat for byte fee discovery for legacy. its all done via the cludge weigh unit cludge.. AS DEMONSTRATED IN REAL CODE
in short if legacy fees were straight sat/byte. there would be no cludge.. no multiplier no scale factor
just length(tx) * sats
emphases to avoid multiple posts.. hoping you can get it in just one post with needing to re post the simple fact..
if legacy was doing old normal real byte fee costings).. without weight units... there would be no weight unit *4!! involved in a legacy fee costing code
the reason for the *4 is to premiumize legacy into making people not want to use it due to the extra premium expense they [dev-politics] added to legacy
anyways
back to topic
there are a few wallets now that if you import a key
they default a legacy key to p2pkh and dont support p2pk.
so already support for some forms of key types have disappeared (unless you can search out a certain wallet(limiting your wallet options of free choice))
it only takes a couple lines of code to not support other type too.. and that can happen without needing any hard fork consensus decisions to approve such change.
as someone said the only option is to try to keep old node software and hope it will still sync or communicate with peers in the future should a change happen
(diminished, redefined RPC calls(INV messages) have broke the ability of some older nodes communication ability with the network)
