Inscription spam is possible because compromised Core devs allowed it.

They rejcted Luke's fix.

They now use it as excuse for more spam on OP_RETURN.

Are you doing the same thing?

nostr:nevent1qqsp8xcjfzwnj8huaymzr0s033h94gp8ha43vef55nsdspg3f2nnw2gppemhxue69uhkummn9ekx7mp0qy08wumn8ghj7mn0wd68yttsw43zuam9d3kx7unyv4ezumn9wshsz8thwden5te0dehhxarj9e3xjarrda5kuetj9eek7cmfv9kz7e4vc5c

Reply to this note

Please Login to reply.

Discussion

Luke’s “fix” wouldn’t have fixed it, which is also why it was rejected.

BS. It is fixed in Bitcoin Knots.

Why do you thing inscription spammers are worried about thight mempool policies?

If it’s fixed in Bitcoin Knots, and you can run Bitcoin Knots, you should be happy. Are you happy?

I am very happy. Thanks. I hope you are happy too.

I’m happy that everyone can run the software that best fits their needs :)

But I’d be even happier if people stopped harassing developers!

Truth is harassment? Are you part of ministry of speech?

To be honest, Knots haven't fixed anything.

that is not honest

That's very honest and straight to the point.