Quote from: NotATether on Today at 08:36:29 AM

Quote from: franky1 on Today at 07:47:30 AM

90% of block base 1mb blockspace, standard tx(normal legacy, normal multisig, normal segwit not using opcodes of 'assumevalid' bypass)..
10% block this junk using certain opcode and or their utxos are less than 144confirm age

I may have a simpler idea - adjust the weight unit calculation and place x10 multiplier on script sizes >10000 bytes. This means the vsize is now almost x10 itself which corresponds to an x10 increase in fees. Now Ordinals and BRC-20 users who abuse the protocol to dump stupid JSON like:

great thing about code is there are many ways to do thing
i was thinking back to the days when there was a fee formulae that created a score. where by 50,000bytes had 'priorty' of 0 fee. then there was 250,000bytte of high fee space and then 700,000byte of low priority low fee..
but modernising it by using a priority space based on opcodees.. where there were 2 separate "fee estimation" where nodes would default to 200x fee for the 10% space of junk.. that junk can only go in that 10% space. and mining pools would only put junk in if they are paying the 200x fee rate estimate