tfgrid/info_tfgrid
30
3
Fork 0
Code Issues Pull Requests 1 Packages Projects Releases Activity

Merge pull request 'decentralization update project inca' (#136) from development_dec2 into development

Browse Source 
Reviewed-on: #136
This commit is contained in:
mik-tf 2024-08-20 15:49:55 +00:00
commit 972d0e48a9
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
collections/projectinca/decentralization/decentralization.md
View File

@ -19,13 +19,13 @@ The following is our own subjective evaluation for the TFGrid V3 and should not
| Code Development | No | +90% done by TFTech: we need more participants |
| Funding For Tech Creation & TFGrid Promotion | No | More or less all done by TFTech and TF Dubai: we need more participants to make this community owned |
| Input on testing cycle & collaboration | Yes | We have a testnet on which everyone can contribute |
| Quality and transparancy of code | Yes | All is on GitHub (3), everyone can review, comment |
| Input on process & roadmap for code development | Yes | All is on GitHub (3), everyone can review, comment |
| Quality and transparancy of code | Yes | All is on GitHub (3): everyone can review and comment |
| Input on process & roadmap for code development | Yes | All is on GitHub (3): everyone can review and comment |
| Tracking of available compute, storage, network capacity | Yes | All is tracked on the blockchain TFChain (farming) |
| Tracking of used compute, storage, network capacity | Yes | All is tracked on the blockchain TFChain (utilization) |
| Minting of tokens (farming) | Yes | Code uses the information on blockchain and creates minting report |
| Verification of minting of tokens (farming) | Yes | Minting reports checked by guardians (4) and hash kept on blockchain when doing the minting |
| The actual minting | Yes | Multisignature of guardians is needed to valudate the transactions, each minting links back to report |
| Verification of minting of tokens (farming) | Yes | Minting reports checked by Guardians (4) and hash kept on blockchain when doing the minting |
| The actual minting | Yes | Multisignature of Guardians is needed to valudate the transactions, each minting links back to report |
| It's possible for super smart hackers to fake capacity | No | Probably yes on non-certified nodes, but it's not easy (5) |
| All components redundant and distributed enough | No | We need more TFGrid Validators |
@ -34,9 +34,9 @@ The following is our own subjective evaluation for the TFGrid V3 and should not
- (1) [Github TF Dubai](https://github.com/threefoldfoundation)
- (2) [ThreeFold Forum](https://forum.threefold.io/)
- (3) [Github TF9](https://github.com/threefoldtech), list of components see [here](https://github.com/threefoldtech/home/blob/master/wiki/components/components_overview.md)
- (3) [Github TF9](https://github.com/threefoldtech). For the list of components, see [here](https://github.com/threefoldtech/home/blob/master/wiki/components/components_overview.md)
- (4) There are multiple Guardians to guide this process
- (5) They would have to re-engineer how ZOS works and tells TFChain, but human chain (i.e. guardians) can still see. We are planning to make this 100x more difficult in V4.0. If a hacker succeeds, they would basically receive tokens which are not really earned. This is probably not possible on certified node, because of silicon route of trust with protected BIOS.
- (5) They would have to re-engineer how ZOS works and tells TFChain, but human chain (i.e. Guardians) can still see. We are planning to make this 100x more difficult in V4.0. If a hacker succeeds, they would basically receive tokens which are not really earned. This is probably not possible on certified node, because of silicon route of trust with protected BIOS.
## TFGrid V4.x