Update rfc-001-smart-contracts-engine.md

This commit is contained in:
Greg Fitzgerald 2018-06-22 22:45:22 -07:00 committed by GitHub
parent 3313c69898
commit 9c50302a39
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 0 deletions

View File

@ -139,12 +139,15 @@ void reduce_r(
Transactions are batched and processed in parallel at each stage.
```
+-----------+ +--------------+ +---------------+ +-----------+
| sigverify |--->| debit verify |--->| memory verify |--->| execution |
+-----------+ +--------------+ +---------------+ +-----------+
```
Continued:
```
+-----------+ +---------------+
| execution |-+->| memory commit |
+-----------+ | +---------------+
@ -156,6 +159,7 @@ Continued:
| +----=----------+
+->| credit commit |
+---------------+
```
The `debit verify` stage is very similar to `memory verify`. Proof of key ownership is used to check if the callers key has some state allocated with the contract, then the memory is loaded and executed. After execution stage, the dirty pages are written back by the contract. Because know all the memory accesses during execution, we can batch transactions that do not interfere with each other. We can also appy the debit and credit stages of the transaction.