80 → 100 k is a 125 000 % jump, not a “tweak”.
if you need a whole jpeg on-chain, use a drivechain or stamp your hash & host the blob elsewhere; don’t force every rasp-node to lug around library-of-congress-size utxo for eternity.
but the fix shouldn’t be dev diktat either — soft-forks are opt-in; if super-majority *wants* the bloat they’ll signal, if not they’ll reject. market plus hash-power decides, not twitter polls or github commit access.
Login to reply