docs: UTXO and VM #225
Draft
docs: UTXO and VM #225
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
https://forum.celestia.org/t/accounts-strict-access-lists-and-utxos/37
|
|
|
||
| - **Register-based Virtual Machine:** Opting for a register-based architecture, FVM achieves a reduction in the number of required instructions for executing operations. This optimization translates into lower gas costs and enhanced performance compared to stack-based virtual machines like EVM. | ||
|
|
||
| - **Advanced Smart Contract Capabilities:** FVM introduces scripts and predicates that simplify executing complex transactions and smart contract logic. This approach enhances user experience and operational efficiency within the blockchain ecosystem. |
There was a problem hiding this comment.
We should also link to a doc that explains scripts and predicates, even briefly. Perhaps linking directly to the section in the new Relationship to Ethereum doc that mentions a definition for them?
docs/fuel-101/intro-to-utxo.mdx
Outdated
| # Understanding UTXO | ||
|
|
||
| The Unspent Transaction Output (UTXO) model, is a fundamental concept in Fuel's underlying blockchain architecture. Fuel tracks digital currency through transaction outputs, each representing a discrete piece of state that can be spent. This model is extended by stateful UTXOs to include additional data or conditions, enabling complex transactions and smart contract functionalities within a UTXO framework. | ||
|
|
There was a problem hiding this comment.
It feels like there should be a section header here like "How do transactions work with a UTXO model?" or something
Co-authored-by: Ben Greenberg <[email protected]>
Co-authored-by: Sarah Schwartz <[email protected]>
Co-authored-by: Sarah Schwartz <[email protected]>
Co-authored-by: Sarah Schwartz <[email protected]>
Co-authored-by: Sarah Schwartz <[email protected]>
Co-authored-by: Sarah Schwartz <[email protected]>
Co-authored-by: Sarah Schwartz <[email protected]>
Co-authored-by: Sarah Schwartz <[email protected]>
docs/fuel-101/intro-to-utxo.mdx
Outdated
|
|
||
| By using strict access lists, transactions explicitly list the contracts they intend to interact with, allowing for the seamless interaction among contracts by utilizing their UTXOs in a unified transaction. | ||
|
|
||
| ## Why Choose UTXO Over Account-Based Models? |
There was a problem hiding this comment.
We should add a section on state minimization as a benefit as well
|
|
||
| > The Fuel Virtual Machine is an operating system designed for unparalleled speed in blockchain computation on the execution layer. | ||
|
|
||
| The Fuel Virtual Machine fundamentally serves as an execution environment tailored for smart contracts, scripts, and predicates. With Fuel's main objective being to maximize throughput, the development of a new VM is essential for advancing scalable blockchain technology. |
There was a problem hiding this comment.
Suggested change
| The Fuel Virtual Machine fundamentally serves as an execution environment tailored for smart contracts, scripts, and predicates. With Fuel's main objective being to maximize throughput, the development of a new VM is essential for advancing scalable blockchain technology. | |
| The Fuel Virtual Machine serves as an execution environment tailored for smart contracts, scripts, and predicates. With Fuel's main objective being to maximize throughput, the development of a new VM is essential for advancing scalable blockchain technology. |
|
|
||
| The Fuel VM addresses key limitations of the Ethereum Virtual Machine (EVM) in order to facilitate the fastest and most cost-effective transaction execution. The EVM's requirement for backward compatibility means that EVM-based Layer 2 solutions (L2s) must rely on legacy software and be constrained to single-threaded computation. | ||
|
|
||
| The surging demand for block space, driven by surging activity in Decentralized Finance (DeFi), Gaming, Decentralized Physical Infrastructure Networks (DePIN), among other areas, necessitating the need for better solutions. By adopting the UTXO model, Fuel leverages the full potential of modern computer cores, significantly enhancing transaction throughput by several orders of magnitude, all while maintaining the foundational security of Ethereum. |
There was a problem hiding this comment.
Suggested change
| The surging demand for block space, driven by surging activity in Decentralized Finance (DeFi), Gaming, Decentralized Physical Infrastructure Networks (DePIN), among other areas, necessitating the need for better solutions. By adopting the UTXO model, Fuel leverages the full potential of modern computer cores, significantly enhancing transaction throughput by several orders of magnitude, all while maintaining the foundational security of Ethereum. | |
| The surging demand for block space, driven by increasing activity in Decentralized Finance (DeFi), Gaming, Decentralized Physical Infrastructure Networks (DePIN), among other areas, necessitates the need for better solutions. By adopting the UTXO model, Fuel leverages the full potential of modern computer cores, significantly enhancing transaction throughput by several orders of magnitude, all while maintaining the foundational security of Ethereum. |
|
|
||
| By using strict access lists, transactions explicitly list the contracts they intend to interact with, allowing for the seamless interaction among contracts by utilizing their UTXOs in a unified transaction. | ||
|
|
||
| ## Why Choose UTXO Over Account-Based Models? |
There was a problem hiding this comment.
We need to add other benefits as well such as minimizing state bloat
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Notes:
1. UTXO explanation needs to be much clearer than the one now it is too muddled with a non stateful version2. VM does not have information from the specs and needs to be simplified and reworded
3. UTXO needs a diagram