You are sheltering spam in your mempool, are you knot?

Reply to this note

Please Login to reply.

Discussion

oooooooooooooh.

Cleans up nicely

Yes, running knots

If spam filtering didn’t work, why would Ben put this comment on his OP_RETURN bot:

“// if this is non-standard, double the fee rate and make sure it's at least 5 sats/vbyte

// we double the fee rate to make sure it gets in since there is only a few pools that will accept it

// otherwise, add 4 sats/vbyte, just to make sure it gets in”

Spam filters are deterrent, and doubling the fee is a sign of it working

What does into the mined chain is different than what I want to relay as a node runner.

h/t: nostr:nprofile1qqszrqlfgavys8g0zf8mmy79dn92ghn723wwawx49py0nqjn7jtmjagpr4mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmp0qyf8wumn8ghj7mn0wd68yat99e3k7mf08mhure nostr:npub1u8lnhlw5usp3t9vmpz60ejpyt649z33hu82wc2hpv6m5xdqmuxhs46turz

I just do that because people want to be in the next block. If more hash rate supported it, I wouldn't need it.

And why is more of hash rate not supporting it yet? Is it because of the default 80 byte limit they are using?

There's been no demand because people can already write data into the chain in other ways.