(...)
there have been examples where one person has put in over 10,000 crap memes into the blockchain. and its that bloat in of itself that is causing problems. it doesnt matter if other people then trade it or price it or any other worthless social stuff.. its that 1 person being capable of adding between 3GB (0.3mb meme*10000) to 39gb (3.9mb*10000) all by themself
in less than a couple months
(...)
and then put upto 10 of them per block to fill a block
with a stockpile to keep repeating for upto 1000 blocks (a week shortest time)
Wouldn't that make it
very costly though? If they were to fill the entire block, to get in, they'd have to pay around of what the average fees-per-block is, currently over $4k (if my quick search was correct).
these memes are being put into blocks by pools that love cheap spam
this one for instance is 122kb of dead weight. but only paying 0.5sat/byte ($13 for 122kb)
https://www.blockchain.com/explorer/transactions/btc/d6537aa2e01e5cb5532ff30ba4401986ba9b7247f5e772f68a23fac5eca2d098here is one that is 3.9mb of dead weight and paid NO FEE
https://www.blockchain.com/explorer/transactions/btc/0301e0480b374b32851a9462db29dc19fe830a7f7d7a88b81612b9d42099c0aean average block has about 2000tx. is about 1.3mb in size and pays about 0.1x in fees
however there are some blocks that contain lots of deadweight memes
where the fee is far less but the total size of block is over 3mb
such as block
779272 with only 427 tx and only paying a total block fee of 0.02891196
What does Taproot actually do? Does it only allow to upload images on chain, or does it also reduces the cost of doing that somehow?
taproot was suppose to promise "one signature length" witness weight max..
(the idea was to make multisig less bloaty)
here is the thing. as soon as taproot got activated (business sponsored request for taproot) sipa then retired and relinquished his github privileges. the other core devs are now unsure what to do so playing party games of saying nothing can be done..
yep the remaining lead maintainers of core have the coding power but dont/cant use it due to how much cludge they would have to undo now. without the guy that implemented it to consult
however the solution is simple.
simply changing the "upto wight(4mb)" they can say that taproot is upto 64-80byte(one signature length)
and it does not break "backward" nodes. because a taproot if only 80byte witness is still with the upto 4mb status of current acceptance parameters. thus no harm to the network. but does stop future bloat