4 ms·

No explanation? How is it even possible for something like this to happen?

by aphextron 9y ago

krallja 9y ago
Like a check, you can write whatever value you want in the "Amount" box.
- mhluongo 9y ago
  Most wallets estimate fees based on transaction size, so this did require a particular wallet or using an "advanced setting"
  - mikeash 9y ago
    Or a bug. In any case, since this post is from the recipient of the fee, they probably have no way of knowing how it happened. At least, not until and unless the person who paid it comes forward.
mhluongo 9y ago
Someone set a custom fee or built a transaction manually and made a mistake. Alternatively, someone just learned an expensive programming lesson.
cjbprime 9y ago
Some exchanges/apps have poor UX that makes the purpose of text fields unclear and allows you to get them confused with each other.
zargon 9y ago
You ask for an explanation as if it's btc.com's mistake. It's not. They merely mined the block that had the fee. They have no way of knowing why the entity that signed that transaction gave it the fee that they did.
FabHK 9y ago
In a transaction, you specify the inputs (addresses, sources of BTC, and they're completely used up), and the output (destination addresses) and how much each destination gets. A typical transaction might look like this: 1) Inputs: my wallet (1 BTC, and this is all taken) 2) Outputs: 2a) pay something to merchant A (0.1 BTC), 2b) pay most of the rest back to my wallet (0.89 BTC) 3) Remainder: The rest (1 - 0.1 - 0.89 = 0.01 BTC) goes to the miner as the transaction fee. The sum of outputs ((2, what you spend) must be less than or equal to the sum of inputs ((1), what you got) - that's checked by the miners. Any remainder (3), however, is taken to be a mining fee and goes to the miner. So, could be what happened here is that someone forgot to add (2b), paying the "change" back into their own wallet. By default, then, it becomes (3): transaction fee. This doesn't happen with well written wallet software, of course, but if you manually create transactions, who knows.

No explanation? How is it even possible for something like this to happen?

krallja 9y ago

Like a check, you can write whatever value you want in the "Amount" box.

mhluongo 9y ago
Most wallets estimate fees based on transaction size, so this did require a particular wallet or using an "advanced setting"
- mikeash 9y ago
  Or a bug. In any case, since this post is from the recipient of the fee, they probably have no way of knowing how it happened. At least, not until and unless the person who paid it comes forward.

mhluongo 9y ago

Someone set a custom fee or built a transaction manually and made a mistake. Alternatively, someone just learned an expensive programming lesson.

cjbprime 9y ago

Some exchanges/apps have poor UX that makes the purpose of text fields unclear and allows you to get them confused with each other.

zargon 9y ago

You ask for an explanation as if it's btc.com's mistake. It's not. They merely mined the block that had the fee. They have no way of knowing why the entity that signed that transaction gave it the fee that they did.

FabHK 9y ago

In a transaction, you specify the inputs (addresses, sources of BTC, and they're completely used up), and the output (destination addresses) and how much each destination gets. A typical transaction might look like this: 1) Inputs: my wallet (1 BTC, and this is all taken) 2) Outputs: 2a) pay something to merchant A (0.1 BTC), 2b) pay most of the rest back to my wallet (0.89 BTC) 3) Remainder: The rest (1 - 0.1 - 0.89 = 0.01 BTC) goes to the miner as the transaction fee. The sum of outputs ((2, what you spend) must be less than or equal to the sum of inputs ((1), what you got) - that's checked by the miners. Any remainder (3), however, is taken to be a mining fee and goes to the miner. So, could be what happened here is that someone forgot to add (2b), paying the "change" back into their own wallet. By default, then, it becomes (3): transaction fee. This doesn't happen with well written wallet software, of course, but if you manually create transactions, who knows.