Quote from: Charles-Tim on May 01, 2023, 08:22:00 AM

Those transactions do not look like transaction send from exchanges that the withdrawal fees are very high. The sender mighty have made a mistake and used too high fee. There are some people in the past that mistakenly used too high fee. If it is because of a reason, I think the senders will be the one that can best answer the reason.

One can make a mistake for one time but for multiple times? If you dig into Transaction^[3] and see his other transactions between other wallets, you'll clearly see that the owner always sends/receives transactions with 1,012 sat/vB.

Quote from: Charles-Tim on May 01, 2023, 08:29:12 AM

Quote from: Little Mouse on May 01, 2023, 08:22:24 AM

Or they are using a wallet which estimates the wrong fee

I have used some wallets that estimate fee wrongly. Even most wallets do that. There are times I will check the mempool and check the reputed wallets, there will be difference in fee estimation at times, but just little differences. What I know is that even as the wallets estimates fee wrongly, the wallet do not include fee very high like that. Likely not because of bitcoin wallet fee estimation algorithm.

There is a difference between actual withdrawal fees and Electrum fees, sometimes Electrum shows higher fees, sometimes it shows normal or sometimes even slightly lower than recommended. But the difference is never as high as 10x and more.

Quote from: DaveF on May 01, 2023, 04:24:46 PM

This has been brought up a few times and the same answers keep coming around. Mistakes, CPFP, Exchanges, people who absolutely want to be in the next block.
What I don't see mentioned a lot of the time is old bad software.

There are a lot of things out there running code that worked in 2014 and still works today in 2023 and back then BTC was at such a low price fees really did not matter so they hard coded in a large number and called it a day. This way the programmer did not have to sit there and worry about figuring out what fee had to be paid by looking at the mempool and doing whatever. It just worked. Close to a decade later, it's still running the same code paying the same fees because nobody has changed anything.

-Dave

If you have a look at transactions, you can clearly see that all of them are done from SegWit addresses and SegWit was activated on 1st August, 2017, so, this should not be an issue because transaction fees become a problem since 2016 as far as I know.