reply on: Stacker Saloon \ stacker news

21 sats \ 7 replies \ @Natalia 11 Feb \ on: Stacker Saloon

sat / vB is out of sync

@ekzyis

21 sats \ 6 replies \ @ek 11 Feb freebie

Out of sync with what?

We are fetching it from our own node.

0 sats \ 5 replies \ @Natalia 11 Feb

the fee - 13 sat/vB from mempool, showing 27 here 👀

0 sats \ 4 replies \ @ek 11 Feb

You mean mempool.space?

I think they are running a node with a mempool larger than default (1GB vs 300MB). That's probably where the difference comes from.

Mempools are unique per node but I think you know that. We're just fetching it from our own node since that made more sense from a technical perspective. Maybe we should use the fee rate from mempool.space?

0 sats \ 1 reply \ @nikotsla 11 Feb

Na... complex and depend of a 3rd party... keep with your node.

0 sats \ 0 replies \ @ek 11 Feb freebie

I was thinking about using the mempool.space API first¹ and use our own node as a fallback. This isn't the first question and won't be the last question where someone is confused about the fee rate we show. I don't necessarily like that everyone seems to use mempool.space to look up fee rates (myself included) but it is what it is.

Maybe we should "fall in line" and meet user expectations there.

it was actually first considered to use it during implementation, but they weren't transparent with their rate limits. The answer in some Github ticket was only: "if you wonder about the rate limits, you're probably above them." ↩

Footnotes