3

From Ethereum's design rationale:

Potential scalability paradigms: UTXOs are more theoretically compatible with certain kinds of scalability paradigms, as we can rely on only the owner of some coins maintaining a Merkle proof of ownership, and even if everyone including the owner decides to forget that data then only the owner is harmed. In an account paradigm, everyone losing the portion of a Merkle tree corresponding to an account would make it impossible to process messages that affect that account at all in any way, including sending to it. However, non-UTXO-dependent scalability paradigms do exist.

I don't really understand the difference. In Bitcoin's UTXO paradigm, the owner of some coins must hold a private key for the destination address of an UXTO to prove ownership of the coins. If the key is lost, the coins are lost. As I understand, the same would happen in the account paradigm, except the owner would lose an account balance instead of an unspent transaction. What else would be lost in an account paradigm? How is that related to scalability?

Also, I understand what Merkle trees are and how they are used for storing transactions but what is a "Merkle proof of ownership"?

Thanks in advance.

0

I know this is a very late reply, but I am currently in the middle of reading this document so I will present my reasoning.

A smart contract can hold ether, tokens and/or other things of value which don't have to necessarily belong to the contract's owner. An escrow is a simple example of such a contract. If the owner loses the ability to manage the contract, then it might happen that all parties using the contract will lose their holdings.

I am not exactly sure what the author meant by "scalability", but one possible reasoning is this: the more people a contract influences, the bigger the damage if the contract becomes unusable. Whereas in a UTXO-based paradigm it's always only the owner of a UTXO that gets harmed.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.