pull down to refresh

635 sats \ 9 replies \ @optimism 6h \ parent \ on: Peter Wuille post about dropping OP_RETURN limit bitcoin
If you disagree with every single point of someone that has literally written more than half of the critical code that you use also when you run Knots, does that make it nonsense?
write
preview
231 sats \ 7 replies \ @LibreHans 6h
Argument from authority
reply
0 sats \ 6 replies \ @optimism 6h
Maybe you're right, but then, is it really nonsense? Or a different view from your own? For example, how do you estimate fee in the face of different miner policies?
reply
100 sats \ 5 replies \ @LibreHans 6h
The same way I've estimated fees since before the feature existed. And it doesn't matter if it's optimal or not anyway since we got RBF.
"You have to relay spam to have a computer give you economic advice for fees you can replace anyway" - really makes no sense.
reply
0 sats \ 4 replies \ @optimism 5h
The same way I've estimated fees since before the feature existed
"the feature" being estimatesmartfee?
How do you estimate then?
PS: you don't have to relay. Just have to have knowledge about it.
reply
100 sats \ 3 replies \ @LibreHans 5h
It seems like you're missing the point. How I personally estimate fees is irrelevant, the point is that it's not a computer science problem and that a computer can't solve it, and that it doesn't matter because of RBF anyway.
reply
102 sats \ 2 replies \ @optimism 5h
Oh, well, I'm sorry to be a noob. Apologies for asking questions.
reply
200 sats \ 1 reply \ @LibreHans 5h
There's no need to be snarky, I was trying to get us on the same level, but you don't have to if you don't want to.
reply
0 sats \ 0 replies \ @optimism 5h
So was I, hence the questions? After all, if you would share your methods, maybe I will learn something about fee estimation.
reply on another page
0 sats \ 0 replies \ @gregtonoski 6h
deleted by author