Setting the fees too high will just serve to drive up the required/suggested fees for the following blocks.
It shouldn't impact much, really. The blocks are 1k kilobytes (or 1 MB) as of late. A single transaction, assuming "average" size of 200 bytes, would be less than 1/5,000th of this size. If everyone is using the normal fee, you'd have to pay 5,000x that fee just to make the average double.
Granted that it wouldn't matter much
if he was the only one doing it. But we both know that the likelihood of that is almost nil.
I keep seeing people on multiple threads say, 'just set a higher fee' , 'you should always add a high fee', etc.
But the problem with that is most don't even know how to calculate transaction size and so they don't realize how/what '80/byte' means. (I was like that before, and so I asked multiple times on how to do it.Finally, someone answered.)
Which is why I'm now trying to share to those who are unaware, the method on how to calculate transaction size as well as the possible outcome if everyone keeps on blindly setting very high fees.
(I made a transaction earlier, the suggested fee per byte was 80 but I set it at 110/byte because I really really needed it to confirm ASAP. I know it doesn't really matter much but I still felt kinda guilty. lol.
just sharing.haha)