Timeline for How is an unspent TX output value verified?
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 5, 2021 at 3:29 | comment | added | LeanMan | I was thinking that too. Thanks for the confirm! | |
| Nov 5, 2021 at 2:49 | comment | added | chytrik | @LeanMan it is simply more efficient to work forwards once and keep a continuously updated UTXO set, than it is to work backwards for each new transaction a node hears about. Especially in the (not uncommon) case where a UTXO may have a shared history with a massive number of previous outputs! Each node's 'reference point' is the genesis block that is hardcoded in, and it is from there that the node can work to independently figure out the state of the network. | |
| Nov 5, 2021 at 2:24 | comment | added | LeanMan | Interesting. I would have thought it was the other way around, where a UTXO would have been calculated walking backwards as that is the only reference any node would have starting with the UTXO and the reference of the previous transaction(s) to compute the current UTXO, not the other way around (since going forwards can only be done once) but going backwards is always available. | |
| Nov 5, 2021 at 1:48 | history | answered | chytrik | CC BY-SA 4.0 |