Running #ordisrespector patch on my #Bitcoin node.
Probably will be useless, but my node, my rules.
Discussion
Do you think your fee estimation will be wildly inaccurate now?
Probably this would be happened. Need to check mempool.space for more accurate estimation.
mempool.space is just another node, so estimates are not more accurate then yours, if you run a node and do not apply filters.
Mine were already probably off, since I don't drop transactions: when mempool.space shows a network congestion and transactions < n sat/vbyte are dropped by their mempool, my node keeps and relays them.
Yes, using bitcoin core default setting seems resulting similar estimation result like mempool.space . What i mean is in this context that your own hosted mempool.space using patched bitcoin core will be give more inacurate estimation mainly due to not having any ordinal transation. Inacurate estimation relative to 'popular tools '.
Yes, you are right.
I thought about this.
Probably.
But I don't care because I use always 1 sat/vbyte for onchain transactions.
What is more interesting is to know if forced closure of LN channels will have the correct estimates or if this is not an issue at all because they are not affected.
By the way, I'm also wondering if Ordinals/Inscriptions are affecting them.
Building from source on the raspi to apply ordisrespector patch as well