News for hackers. Stuff that matters.
Re:A peek under Bitcoin’s hood: Writing a client that can cr... by iso-8859-1 on Monday June 05, 2017 @04:32PM (#14491624)
Because the miner almost always expects a fee, so why not just infer how high it is and you don't need to spend block bytes on it?
Re:A peek under Bitcoin’s hood: Writing a client that can cr... by sprt on Monday June 05, 2017 @04:54PM (#14491926)
Ok, but the unspent output takes space as well. I think you could just replace it with the fee. Not sure if I'm missing something or if it was just an arbitrary design decision.
Re:A peek under Bitcoin’s hood: Writing a client that can cr... by samlewis on Monday June 05, 2017 @05:30PM (#14492295)
It has to do with the way transactions and the blockchain ledger works, reread the transaction part of the article and it might make more sense. Basically, transaction outputs can either be spent or unspent, you can't half spend an output (or perhaps more accurately, you can't spend a previous output twice).
Re:A peek under Bitcoin’s hood: Writing a client that can cr... by sprt on Monday June 05, 2017 @06:05PM (#14492646)
Yes I understand that's how it works, but I don't get why it's important. Surely you could double spend an output as long as you don't exceed its value; and that looks easily verifiable.
Re:A peek under Bitcoin’s hood: Writing a client that can cr... by samlewis on Monday June 05, 2017 @06:31PM (#14492854)
Ah, my bad. Sorry if I was being condescending in my previous reply then.

I suspect it was a design decision, yeah. If outputs could be spent multiple times then you'd need to traverse the chain of outputs backwards to see how much an output has left in it. Bitcoin's implementation is less complex and more elegant, imo.