-
Notifications
You must be signed in to change notification settings - Fork 3.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[docs] Update AptosVM readme #15251
[docs] Update AptosVM readme #15251
Conversation
⏱️ 34m total CI duration on this PR
|
This stack of pull requests is managed by Graphite. Learn more about stacking. Join @georgemitenkov and the rest of your teammates on Graphite |
aptos-move/aptos-vm/README.md
Outdated
### AptosSimulationVM | ||
|
||
Used to simulate transactions before executing them on a real network. | ||
Implementation-wise, wraps AptosVM with some minor modifications for multi-signature transactions, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Replace the trailing comma with a period to maintain consistent sentence punctuation throughout the document.
Spotted by Graphite Reviewer
Is this helpful? React 👍 or 👎 to let us know.
738a286
to
9681dd5
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor comments to look at.
For every user transaction, the following steps are performed: | ||
|
||
1. ***Prologue:*** | ||
Responsible for checking the structure of the transaction such as signature verification, balance checks on the account paying gas for this transaction, etc. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the previous version of this document, it is mentioned that bytecode verifier runs in the prologue in verifier mode.
In this new text, the bytecode verifier is not discussed. Perhaps add a brief discussion?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It doesn't necessarily run in prologue, so the old text is wrong (and is probably very old - there used to be no entry functions and scripts were the only way to run code iirc). Bytecode verifier runs for scripts, still, but for entry functions, and this is part of step 2. I added a few sentences explaining this.
aptos-move/aptos-vm/README.md
Outdated
Runs the code specified by the transaction - can be a script or an entry function. | ||
Internally, the code execution is done by MoveVM which AptosVM wraps. | ||
If execution is successful, produces a change set that can be (but is not yet) applied to the blockchain state. | ||
3. **Aborted execution (hack):** |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The "hack" seems out of place. It is not clear to the reader whether the current implementation is a hack that we intend to fix in some way, or something else. Probably best to explain whatever is the intention in the prose, instead of just mentioning it here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removed the "hack" part.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
✅ Forge suite
|
✅ Forge suite
|
Description
Fixes #14606. We had some really ugly/old docs for AptosVM, quickly updated.
How Has This Been Tested?
Key Areas to Review
Type of Change
Which Components or Systems Does This Change Impact?
Checklist