Merge branch 'development' of git.ourworld.tf:tfgrid/info_tfgrid into development
This commit is contained in:
44
collections/projectinca/decentralization/decentralization.md
Normal file
44
collections/projectinca/decentralization/decentralization.md
Normal file
@@ -0,0 +1,44 @@
|
||||
|
||||
<h1> Decentralization </h1>
|
||||
|
||||

|
||||
|
||||
Decentralization, in our view, isn't solely about employing blockchain technology everywhere. Instead, we envision it as the culmination of a global community collaborating transparently, sharing everything they do, and actively seeking feedback. Our goal is to ensure that the platform we deploy operates in the most distributed and decentralized manner possible.
|
||||
|
||||
## TFGrid V3.x
|
||||
|
||||
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 |
|
||||
| ---------------------------------------------------------- | --------------- | ----------------------------------------------------------------------------------------------------- |
|
||||
| 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) |
|
||||
| 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 |
|
||||
| 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) |
|
||||
| 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 |
|
||||
| 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.
|
||||
|
||||
|
||||
## TFGrid V4.x
|
||||
|
||||
Our next generation Grid has lots of improvements in relation to decentralization. [See the specific document for TFGrid V4.x](decentralization4.md).
|
@@ -0,0 +1,41 @@
|
||||
# **The ThreeFold’s 3.x Decentralization Model**
|
||||
|
||||
## Fully Decentralized Farming - TF Nodes
|
||||
|
||||
Today more than 500 farmers host the nodes which make up the TF Grid 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.
|
||||
|
||||
## Grid Enhancement Proposals (GEP's)
|
||||
|
||||
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 GEPS are proposed by ThreeFold Dubai and published on Forum and registerd on TFChain.
|
||||
|
||||
The GEPS need to be voted for by the farming community.
|
||||
|
||||
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)
|
||||
|
||||
## TF Validator Stacks
|
||||
|
||||
- The TFChain is our blockchain component in 3.x to provide identity, billing, capacity tracking, utilization tracking, pricing, ...
|
||||
- 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
|
||||
- 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)
|
||||
|
||||
## The 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
|
||||
- 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
|
@@ -0,0 +1,81 @@
|
||||
|
||||
# **The ThreeFold’s 4.0 Decentralization Model**
|
||||
|
||||
## Fully Decentralized Farming - TF Nodes
|
||||
|
||||
Today more than 500 farmers host the nodes which make up the TF Grid 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.
|
||||
|
||||
We expect to have many thousands of independent compute, storage, Network farmers in the world. This is the true nature of our decentralization.
|
||||
|
||||
The communication between the marketplace, 3Nodes, Farming Pool Agents and other participants all goes over the mycelium network which leads to an full peer2peer control and communication plane. All communication is end2end encrypted, all messages are signed by the participants.
|
||||
|
||||
The billing & tracking of capacity in v 4.0 will be based on a mutual credit and capacity accounting system which is carried and peer2peer executed by the farmers.
|
||||
|
||||
## Farming Pools
|
||||
|
||||
Many people will want to he a hoster of capacity but not have to deal with the duties of being a farmer, they can connect to a farming pool and add their capacity to such a pool.
|
||||
|
||||
They can chose the farming pool they like, farming pools can be DAO's by themselves, they organize their own governance indepent of ThreeFold. A Farming pool defines the price, service levels, ... A Farming pool defines how the proceeds are split over their members.
|
||||
|
||||
We expect that more than 80% of the capacity in the future will be provider over Farming Pools, in our opinion this leads to a super decentralized structure while making it possible to provide strong SLA's.
|
||||
|
||||
## Grid Enhancement Proposals (GEP's)
|
||||
|
||||
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 GEPS are proposed by the ThreeFold Cooperation and/or ThreeFold Dubai.
|
||||
|
||||
The GEPS need to be voted for by the farming and user community, the exact rules of voting are still being worked on, we are learning from our 3.x experience.
|
||||
|
||||
GEPS deal with
|
||||
|
||||
- approve functionality & roadmap (priorities)
|
||||
- approve changes in protocol or anything which has impact on fundamental working of the TGGrid
|
||||
|
||||
## Grid Upgrade Proposals (GUP's)
|
||||
|
||||
GUPs us much more practical, its providing a control path for code changes, community members or farmers will probably lack the knowledge as required to have meaningful review capability on these proposals.
|
||||
|
||||
GUPS deal with
|
||||
|
||||
- code updates on production TFGrid
|
||||
|
||||
## TF Protectors run the TF Grid Validators
|
||||
|
||||
We have been learning from what Hashgraph did and we like their model (see here for more [info](https://hedera.com/blog/decentralized-on-hedera)).
|
||||
|
||||
ThreeFold’s validator consensus model is addressing the challenges of decentralization in a practical way. It brings together up to 9 to 30 term-limited organizations (TF Protectors) from across multiple continents, ensuring a truly global perspective.
|
||||
|
||||
Each TF Protector does the following
|
||||
|
||||
- operate a [TF Validator Clusters](TFValidatorCluster.md), which requires an investment and requires an operational team
|
||||
- validate the code written and sign off on the changes (validation step on code & functionality)
|
||||
- validate the GEP's and execute a VETO right if needed, the TF Protectors can stop a GEP.
|
||||
- validate and approve the GUP's
|
||||
|
||||
Each Protector member has an equal vote, which prevents any single entity from gaining undue influence and keeps the governance balanced and fair.
|
||||
|
||||
ThreeFold’s proof-of-stake model (v4.x) has been designed to prevent the concentration of power. Nodes gain influence only when $TFT or $INCA is staked to them by individual users, ensuring that the community has a direct role in the network’s governance.
|
||||
|
||||
## TF Cooperative
|
||||
|
||||
In 2025, we plan to establish a Cooperative structure that will unite and represent the interests of all TFGrid Farmers as well as TFGrid Users.
|
||||
|
||||
Cooperatives are powerful, regulated entities with a long history of promoting decentralization and community-driven governance. By forming a cooperative, we can create a structure that not only aggregates the voices and needs of our farmers and users but also provides a legally recognized framework for truly decentralized decision-making.
|
||||
|
||||
Cooperatives are uniquely suited to the decentralized ethos of the ThreeFold Grid. They operate on democratic principles, ensuring that each member—whether a farmer or user—has an equal say in the direction and operation of the network. This approach aligns perfectly with our vision of a decentralized, peer-to-peer infrastructure where power is distributed, not concentrated.
|
||||
|
||||
Moreover, cooperatives are recognized globally as legitimate and effective governance structures. This recognition will help us engage with regulatory bodies and broader societal systems, ensuring that the decentralized nature of the ThreeFold Grid is respected and protected as we continue to grow.
|
||||
|
||||
The TF Grants, distribution of Farming & Promotion Rewards will all be arranged by the TF Cooperative.
|
||||
|
||||
Please note that the rewards and grants only unlock over 3 to 4 years.
|
||||
|
||||
As long as the TF Cooperative is not up and running ThreeFold Dubai will keep on executing this role and provide full transparancy to the community.
|
||||
|
||||
|
||||
## Development & OpenSource
|
||||
|
||||
The development of ThreeFold is an open, collaborative process. All software powering the network, including services and developer tools, is open-sourced under an Apache 2.0 license. The decentralized development model encourages contributions from a wide range of participants, including the ThreeFold developer community. This approach improves innovation and ensures that the platform continuously evolves to meet the needs of its users.
|
@@ -0,0 +1,16 @@
|
||||
## TF Validator Cluster
|
||||
|
||||
In version 4.0 we will have minimum 9, maximum 30 Protectors (commercial partners from different continents) who run a TF Validator Cluster.
|
||||
|
||||
Each TF Validator Cluster has following functions
|
||||
|
||||
- consensus chains e.g. the TFChain for 3.x Grid, TF Validators for 4.x grid
|
||||
- TF explorers (interfaces to allow us to digest and find the relevant information easier from the TFGrid)
|
||||
- TF Hub's (conversion service from docker to deduped filesystems as used for our compute workloads).
|
||||
- a node for the Bridging functionality (INCA support on multiple chains)
|
||||
- CI/CD Service for TFGrid code (Continuous Integration, Continuous Development)
|
||||
- All necessary webservices (websites, manuals, UI)
|
||||
- TF Marketplace & Components as relevant for the TF Liquidity Pool.
|
||||
|
||||
|
||||
|
Reference in New Issue
Block a user