attack bitcoin through writing data directly into output's scriptPubKeys

In this post, Steve Ellis wrote :

“[…]Writing data directly into a output’s scriptPubKey is not prunable[…]where as non-prunable outputs will forever create bloat and slowdown the set traversal(e.g. during block verification).[…]

Wouldn’t this be a relatively cost effective way to slow down bitcoin by writing the maximum possible data into into scriptPubKey?

Source link

Leave a Comment

Your email address will not be published.