Sattler on Nostr: Not so sure about 1. Even if it would be possible to implement it via OP_RETURN, you ...
Not so sure about 1.
Even if it would be possible to implement it via OP_RETURN, you would only have 80 bytes and probably a huge percentage would be gone for management overhead leaving just a tiny fraction for the payload.
So economically, it's now order of magnitudes cheaper to spam.
We can just hope that RGB is outcompeting it quite fast so that it'll vanish.
I"m still surprised that the mempool is not clogged.
The biggest threat is child porn as some sort of poison pill. Look at how outraged people like Francis or Luke are.
Luke is already implementing mempool censoring Features and others pointed out that mempool censoring won't work..
But I haven't heard anything about pruning. Is that even possible? If it's possible to prune, why isn't it possible to mempool-censoring?
Even if it would be possible to implement it via OP_RETURN, you would only have 80 bytes and probably a huge percentage would be gone for management overhead leaving just a tiny fraction for the payload.
So economically, it's now order of magnitudes cheaper to spam.
We can just hope that RGB is outcompeting it quite fast so that it'll vanish.
I"m still surprised that the mempool is not clogged.
The biggest threat is child porn as some sort of poison pill. Look at how outraged people like Francis or Luke are.
Luke is already implementing mempool censoring Features and others pointed out that mempool censoring won't work..
But I haven't heard anything about pruning. Is that even possible? If it's possible to prune, why isn't it possible to mempool-censoring?