smeb_y/0g-storage-node
1
0
Fork 0
mirror of https://github.com/0glabs/0g-storage-node.git synced 2025-02-23 04:07:06 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

docs: Fixing Documentation Typos (#308)

Browse Source 
* docs: typo fix Update transaction-processing.md

* docs: typo fix Update run.md

* docs: typo fix Update onebox-test.md
This commit is contained in:
Dmitry 2025-02-11 11:37:33 +03:00 committed by GitHub
parent bc6bcf857c
commit b0a9a415f7
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
3 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/onebox-test.md
View File

@ -19,7 +19,7 @@ The blockchain node binaries will be compiled or downloaded from github to `test
## Run Tests
Changes to the `tests` folder and run the following command to run all tests:
Change to the `tests` folder and run the following command to run all tests:
```
python test_all.py

2
docs/run.md
View File

@ -4,7 +4,7 @@
### Setup Environment
Install dependencies Node.js, yarn, hardhat.
Install the dependencies Node.js, yarn, hardhat.
- Linux

2
docs/transaction-processing.md
View File

@ -12,4 +12,4 @@ When an application server with the key-value runtime encounters the commit reco
## Concurrent Assumption
This transaction model assumes that the transaction participants are collaborative and will honestly compose the commit record with the correct content. Although this assumption in a decentralized environment is too strong, it is still achievable for specific applications. For example, for an application like Google Docs, a user normally shares the access to others who can be trusted. In case this assumption cannot hold, the code of the transaction can be stored in the ZeroGravity log and some mechanism of verifiable computation like zero-knowledge proof or hardware with trust execution environment (TEE) can be employed by the transaction executors to detect the validity of the commit record.
This transaction model assumes that the transaction participants are collaborative and will honestly compose the commit record with the correct content. Although this assumption in a decentralized environment is too strong, it is still achievable for specific applications. For example, for an application like Google Docs, a user normally shares the access to others who can be trusted. In case this assumption cannot hold, the code of the transaction can be stored in the ZeroGravity log and some mechanism of verifiable computation like zero-knowledge proof or hardware with trusted execution environment (TEE) can be employed by the transaction executors to detect the validity of the commit record.