tfgrid/docs_tfgrid4
10
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

update status v3

Browse Source
This commit is contained in:
mik-tf 2024-12-11 21:02:27 -05:00
parent cae6afaa3d
commit 1525d1934e
5 changed files with 47 additions and 53 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/become-a-farmer/get_started.md
View File

@ -12,5 +12,5 @@ We are now preparing our next phase, where we invite the community to host milli
The ThreeFold V4 nodes are available and you can buy them directly on our official partners' websites:
- [HostService.nl](https://hostservice.nl/en/)
- [DuckFarm Data](https://duckfarmdata.com/)
- [HostService](https://hostservice.nl/en/) (America)
- [Duck Farm Data](https://duckfarmdata.com/) (Europe, Asia, Africa, Australia)

4
docs/components/node.md
View File

@ -55,5 +55,5 @@ You can buy, build and host ThreeFold Nodes now.
The ThreeFold V4 nodes are available and you can buy them directly on our official partners' websites:
- [HostService](https://hostservice.nl/en/)
- [Duck Farm Data](https://duckfarmdata.com/)
- [HostService](https://hostservice.nl/en/) (America)
- [Duck Farm Data](https://duckfarmdata.com/) (Europe, Asia, Africa, Australia)

2
docs/decentralization/status/_category_.json
View File

@ -3,6 +3,6 @@
"position": 10,
"link": {
"type": "generated-index",
"description": "Status of Decentralization on the TFGrid."
"description": "We present the Decentralization status of ThreeFold V3 and V4."
}
}

86
docs/decentralization/status/decentralization3.md
View File

@ -1,81 +1,75 @@
---
title: 'TFGrid 3'
sidebar_position: 12
description: ThreeFold Grid V3 Status
description: ThreeFold V3 Decentralization Model
---
# **The ThreeFold’s 3.x Decentralization Model**
## TFGrid V3.x
## ThreeFold V3 Decentralization Model
The following is our own subjective evaluation for the TFGrid V3 and should not be construed as a guarantee or commitment. We welcome any differing opinions or feedback.
| Description | Good Enough | Remark |
| Description | Good Enough | Remarks |
| ---------------------------------------------------------- | --------------- | ----------------------------------------------------------------------------------------------------- |
| TFNodes owned and invested by Independent Farmers | Yes | Less than 5% owned by ThreeFold Cloud/Dubai |
| Open documentation & feedback | Yes | All open-source on GitHub, anyone can contribute and give feedback.|
| Transparancy and input on any change to do with tokenomics | Yes | See the discussions on the ThreeFold Forum (2) and the GEP process |
| Transparancy about tokens, history | Yes | See GitHub organizations (1) (3) |
| TFNodes owned and invested by independent farmers | Yes | Less than 5% owned by ThreeFold Cloud/Dubai |
| Open documentation & feedback | Yes | Everyting is open-source on GitHub, anyone can contribute and give feedback.|
| Transparancy and input on any change to do with tokenomics | Yes | See the discussions on the ThreeFold Forum [^1] and the GEP process |
| Transparancy about tokens, history | Yes | See GitHub organizations[^2][^3] |
| TFChain deployment | No | Too few run the validator stack, we need more validators |
| 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 |
| 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 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) |
| Quality and transparancy of code | Yes | Everything is on GitHub[^3]: everyone can review and comment |
| Input on process & roadmap for code development | Yes | Everything is on GitHub[^3]: everyone can review and comment |
| Tracking of available compute, storage, network capacity | Yes | Everything is tracked on the blockchain TFChain (farming) |
| Tracking of used compute, storage, network capacity | Yes | Everything 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 |
| 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 |
### Notes
- (1) [Github TF Dubai](https://github.com/threefoldfoundation)
- (2) [ThreeFold Forum](https://forum.threefold.io/)
- (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.
| 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 |
[^1]: ThreeFold Forum [Link](https://forum.threefold.io/)
[^2]: GitHub TF Dubai [Link](https://github.com/threefoldfoundation)
[^3]: GitHub TF9 [Link](https://github.com/threefoldtech) — List of components [Link](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. 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.
## Fully Decentralized Farming - TF Nodes
Today more than 500 farmers host the nodes which make up the TF Grid Network.
Today more than 500 farmers host the nodes which make up the TFGrid Network.
None of the ThreeFold Companies or its team has the ability to break this model, its our aim to have the farmers independant completely from Threefold.
None of the ThreeFold companies or its team has the ability to break this model, its our aim to have the farmers independant completely from Threefold.
## Grid Enhancement Proposals (GEP's)
## Grid Enhancement Proposals (GEP)
The decisions that shape the technology and standards of ThreeFold are driven by the community through the Grid Enhancement Proposal (GEP) program. These proposals are reviewed and approved farmers, technical steering committee as well as the cooperative, ensuring that the best ideas rise to the top.
The decisions that shape the technology and standards of ThreeFold are driven by the community through the Grid Enhancement Proposal (GEP) program. These proposals are reviewed and approved by farmers, technical steering committees as well as the cooperative, ensuring that the best ideas rise to the top.
The GEPS are proposed by ThreeFold Dubai and published on Forum and registerd on TFChain.
The GEPS are proposed by ThreeFold Dubai and published on the [ThreeFold Forum](https://forum.threefold.io) and registerd on TFChain.
The GEPS need to be voted for by the farming community.
GEPS deal with
GEPS deal with:
- approve changes in protocol or anything which has impact on fundamental working of the TGGrid
- upgrades of the TFGrid with new software
- approve functionality & roadmap when needed (priorities)
- Changes approvals in protocol or anything which has impact on any fundamental working of the TGGrid
- Upgrades of the TFGrid with new software
- Functionality & roadmap approvals when needed (e.g. priorities)
## TF Validator Stacks
- The TFChain is our blockchain component in 3.x to provide identity, billing, capacity tracking, utilization tracking, pricing, ...
- The TFChain is our blockchain component in V3 to provide identity, billing, capacity tracking, utilization tracking, pricing, etc.
- TFGrid Validators are the control plane of the TFGrid and allows us to Interact with the TFGrid.
- A TFGrid Validator is combination of TFChain (blockchain node), Monitoring Nodes, TF Explorer, TF Hub, all Web Interfaces
- TFGrid Validators are run by TF Guardians
- A TFGrid Validator is combination of TFChain (blockchain node), Monitoring Nodes, TF Explorer, TF Hub, all Web Interfaces.
- TFGrid Validators are run by ThreeFold Guardians.
- The TF guardians get a monthly fixed fee for running the Validators (in TFT and/or INCA).
- ThreeFold Dubai is helping the guardians to do it right and gives support.
- Token minting (TFGrid 3) is executed by code and validated by the guardians to make sure there are no mistakes.
- Each TFGrid validator stack has a name as follows: $location.grid.tf the the dashboard would e.g. be dashboard.ghent.grid.tf, a global loadbalancer makes sure that normal users of the solution don't have to understand this naming convention
- Code & Protocol Changes need to be voted for by a DAO on the TFChain (our blockchain)
- Each TFGrid validator stack has a name as follows: $location.grid.tf, e.g. the the dashboard would be `dashboard.ghent.grid.tf`, a global loadbalancer makes sure that normal users of the solution don't have to understand this naming convention.
- Code & protocol changes need to be voted for by a DAO on the TFChain, the ThreeFold blockchain.
## The main players in the ecosystem
## Main Players in the Ecosystem
- +500 Farmers (people or companies hosting the nodes of the TF Grid)
- ThreeFold Dubai (DMCC) for all the grid management, promotion and token related activities. This is our main company from which we run the Opensource TFGrid project.
- ThreeFold BVI for specific token related activities
- +500 Farmers, people or companies hosting the nodes of the TFGrid.
- ThreeFold Dubai (DMCC) for all the grid management, promotion and token related activities. This is our main company from which we run the open-source TFGrid project.
- ThreeFold BVI for specific token related activities.
- TF9, the tech company who develops the opensource code, all code is available for ThreeFold Dubai as well as any other opensource enthousiast, TF9 will commercialize the tech for commercial usecases. TF9 has nothing to do with the tokens TFT and/or INCA.
- ThreeFold CH (Switzerland), not used right now
- ThreeFold CH (Switzerland). It is not used right now.

4
docs/decentralization/status/decentralization4.md
View File

@ -1,10 +1,10 @@
---
title: 'TFGrid 4'
sidebar_position: 13
description: ThreeFold Grid V4 Status
description: ThreeFold V4 Decentralization Model
---
# **The ThreeFold’s 4.0 Decentralization Model**
## ThreeFold V4 Decentralization Model
## Fully Decentralized Farming - TF Nodes