s
This commit is contained in:
parent
da14091106
commit
564345e26b
Binary file not shown.
|
Before Width: | Height: | Size: 38 KiB |
@ -1,20 +1,13 @@
|
|||||||
|
|
||||||
- [Introduction](projectinca/intro.md)
|
- [Introduction](projectinca/intro.md)
|
||||||
- [The Plan](projectinca/theplan_a.md)
|
- [Tokenomics](projectinca/tokens.md)
|
||||||
- [**Requirements**](projectinca/requirements.md)
|
- [Liquidity Pool](projectinca/liquidity_pool.md)
|
||||||
- [Tokens](projectinca/inca1.md)
|
|
||||||
- [Funding](projectinca/funding.md)
|
|
||||||
- [P2P Promotion](projectinca/peer2peer_promotion.md)
|
|
||||||
- [Liquidity](projectinca/liquidity.md)
|
- [Liquidity](projectinca/liquidity.md)
|
||||||
- [Governance](projectinca/governance.md)
|
- [Decentralization](projectinca/decentralization.md)
|
||||||
- [Collaboration](projectinca/collab.md)
|
- [Decentralization 3.x](projectinca/decentralization3.md)
|
||||||
- [Principles](projectinca/collaboration.md)
|
- [Decentralization 4.x](projectinca/decentralization4.md)
|
||||||
- [Messaging](tfgrid3/messaging.md)
|
- [TF Validators 4.x](projectinca/TFValidatorCluster.md)
|
||||||
- [Teams](projectinca/teams.md)
|
- [**Technology**](projectinca/technology.md)
|
||||||
- [ThreeFold Collaboration](projectinca/tf_colab.md)
|
|
||||||
- [Remuneration](projectinca/remuneration.md)
|
|
||||||
- [My **Checklist**](projectinca/checklist.md)
|
|
||||||
- [My **Links**](projectinca/links.md)
|
|
||||||
- [Project Info](projectinca/project_info.md)
|
- [Project Info](projectinca/project_info.md)
|
||||||
- [About Us](tfgrid3/who_are_we.md)
|
- [About Us](tfgrid3/who_are_we.md)
|
||||||
- [The Internet Today](tech/internet_today.md)
|
- [The Internet Today](tech/internet_today.md)
|
||||||
@ -25,56 +18,58 @@
|
|||||||
- [Cloud Too Centralized](why/current_cloud_too_centralized.md)
|
- [Cloud Too Centralized](why/current_cloud_too_centralized.md)
|
||||||
- [Countries Don't Have Their Internet](why/countries_no_internet.md)
|
- [Countries Don't Have Their Internet](why/countries_no_internet.md)
|
||||||
- [Human Right](why/internet_human_right.md)
|
- [Human Right](why/internet_human_right.md)
|
||||||
- [Social Warming](why/social_warming.md)
|
- [Marketplace](projectinca/marketplace.md)
|
||||||
- [**Technology**](projectinca/technology.md)
|
|
||||||
- [INCA Tokenomics](projectinca/tokens1.md)
|
|
||||||
- [INCA Marketplace](projectinca/marketplace.md)
|
|
||||||
- [Pricing](projectinca/marketplace_pricing.md)
|
- [Pricing](projectinca/marketplace_pricing.md)
|
||||||
- [AI Slices](tfgrid4/aislice.md)
|
- [AI Slices](tfgrid4/AISlice.md)
|
||||||
- [Cloud Slices](tfgrid4/cloudslice.md)
|
- [Cloud Slices](tfgrid4/CloudSlice.md)
|
||||||
- [Storage Slices](tfgrid4/storageslice.md)
|
- [Storage Slices](tfgrid4/storageslice.md)
|
||||||
- [INCA Farming](projectinca/inca_farming.md)
|
- [Farming](projectinca/inca_farming.md)
|
||||||
- [INCA Nodes](projectinca/inca_nodes.md)
|
- [3Nodes](projectinca/inca_nodes.md)
|
||||||
- [INCA Node Silver](projectinca/inca_node_silver.md)
|
- [3Node Silver](projectinca/inca_node_silver.md)
|
||||||
- [INCA Node Platinum](projectinca/inca_node_platinum.md)
|
- [3Node Platinum](projectinca/inca_node_platinum.md)
|
||||||
- [INCA Node AI](projectinca/inca_node_ai.md)
|
- [3Node AI](projectinca/inca_node_ai.md)
|
||||||
- [INCA Routers](projectinca/inca_routers.md)
|
- [Mycelium Routers](projectinca/inca_routers.md)
|
||||||
- [INCA Network Map](projectinca/networkmap.md)
|
- [Network Map](projectinca/networkmap.md)
|
||||||
- [Reward Simulation](projectinca/inca_farming_reward.md)
|
- [Reward Simulation](projectinca/inca_farming_reward.md)
|
||||||
- [INCA Stories](projectinca/stories.md)
|
- [Grants](projectinca/grants.md)
|
||||||
- [INCA App Spec](projectinca/inca1pp.md)
|
- [Open Grants](projectinca/grants_now.md)
|
||||||
- [INCA Grants](projectinca/grants.md)
|
- [Deploy AI Slices](projectinca/grant_ai_slices.md)
|
||||||
- [v3.x Grants](projectinca/grants_tft.md)
|
- [Deploy Cloud Slices](projectinca/grant_cloud_slices.md)
|
||||||
- [Deploy AISlices](projectinca/grant_aislice.md)
|
- [Deploy Storage Slices](projectinca/grant_storage_slices.md)
|
||||||
- [Deploy CloudSlices](projectinca/grant_cloudslice.md)
|
- [Develop TF Marketplace](projectinca/marketplace_grant.md)
|
||||||
- [Deploy StorageSlices](projectinca/grant_storageslice.md)
|
|
||||||
- [Develop INCA Marketplace](projectinca/marketplace_grant.md)
|
|
||||||
- [Contributor Rewards](projectinca/contributor_rewards.md)
|
- [Contributor Rewards](projectinca/contributor_rewards.md)
|
||||||
- [Chapter Tanzania](projectinca/chapter_tanzania.md)
|
- [Chapter Tanzania](projectinca/chapter_tanzania.md)
|
||||||
- [Chapter Brazil](projectinca/chapter_brazil.md)
|
- [Chapter Brazil](projectinca/chapter_brazil.md)
|
||||||
- [Biz Dev Rewards](projectinca/biz_dev_rewards.md)
|
- [Biz Dev Rewards](projectinca/biz_dev_rewards.md)
|
||||||
- [Code TFGrid 3.13](projectinca/grant_tf_3_13.md)
|
- [Code TFGrid 3.13](projectinca/grant_tf_3_13.md)
|
||||||
- [Code TFGrid 3.14](projectinca/grant_tf_3_14.md)
|
- [Code TFGrid 3.14](projectinca/grant_tf_3_14.md)
|
||||||
- [Establish Thorchain DEX](projectinca/grant_thorchain.md)
|
- [Code TFGrid 3.15](projectinca/grant_tf_3_15.md)
|
||||||
- [v4.x Grants](projectinca/grants_inca.md)
|
- [Future Grants](projectinca/grants_future.md)
|
||||||
- [Grant Voting Process](projectinca/grant_voting_process.md)
|
- [Grid Utilization](partners_utilization/partners.md)
|
||||||
- [INCA Grid Utilization](partners_utilization/partners.md)
|
- [Tier S Datacenter](partners_utilization/tier_s_datacenter.md)
|
||||||
- [Holochain](partners_utilization/holochain.md)
|
|
||||||
- [Hero - Project Mycelium](projectinca/hero.md)
|
|
||||||
- [Digital Freezone](partners_utilization/freezone.md)
|
- [Digital Freezone](partners_utilization/freezone.md)
|
||||||
- [Tanzania Internet](partners_utilization/tanzania.md)
|
- [Tanzania Internet](partners_utilization/tanzania.md)
|
||||||
- [Elestio](partners_utilization/elestio.md)
|
|
||||||
- [Earth Wallet](partners_utilization/earth_wallet.md)
|
|
||||||
- [Sikana](partners_utilization/sikana.md)
|
- [Sikana](partners_utilization/sikana.md)
|
||||||
- [Vindo](partners_utilization/vindo.md)
|
- [Vindo](partners_utilization/vindo.md)
|
||||||
- [Vverse](partners_utilization/vverse.md)
|
- [Vverse](partners_utilization/vverse.md)
|
||||||
- [Tier S Datacenter](partners_utilization/tier_s_datacenter.md)
|
- [Holochain](partners_utilization/holochain.md)
|
||||||
- [Engineering](projectinca/engineering.md)
|
- [Hero - Project Mycelium](projectinca/hero.md)
|
||||||
- [INCA Grid 4.0](projectinca/tfgrid4.md)
|
- [Internal Wiki](projectinca/internal.md)
|
||||||
- [Plan B](projectinca/theplan_b.md)
|
- [The Plan](projectinca/theplan_a.md)
|
||||||
- [INCA Plan B](projectinca/tokens0.md)
|
- [**Requirements**](projectinca/requirements.md)
|
||||||
- [TFT](projectinca/tft0.md)
|
- [Funding](projectinca/funding.md)
|
||||||
- [Appendix](projectinca/appendix.md)
|
- [P2P Promotion](projectinca/peer2peer_promotion.md)
|
||||||
- [Tokenomics TFGrid 3.14](tfgrid3/tokenomics.md)
|
- [Collaboration](projectinca/collab.md)
|
||||||
- [Farming Reward TFGrid 3](tfgrid3/farming_reward.md)
|
- [Principles](projectinca/collaboration.md)
|
||||||
- [Tokens Overview TFGrid 3](tfgrid3/tokens_overview.md)
|
- [Messaging](tfgrid3/messaging.md)
|
||||||
|
- [Teams](projectinca/teams.md)
|
||||||
|
- [ThreeFold Collaboration](projectinca/tf_colab.md)
|
||||||
|
- [Remuneration](projectinca/remuneration.md)
|
||||||
|
- [Stories](projectinca/stories.md)
|
||||||
|
- [My **Checklist**](projectinca/checklist.md)
|
||||||
|
- [My **Links**](projectinca/links.md)
|
||||||
|
- [Engineering](projectinca/engineering.md)
|
||||||
|
- [TFGrid 4.0](projectinca/tfgrid4.md)
|
||||||
|
|
||||||
|
<!-- - [Appendix](projectinca/appendix.md) -->
|
||||||
|
<!-- - [Grant Voting Process](projectinca/grant_voting_process.md) -->
|
||||||
@ -1,12 +1,17 @@
|
|||||||
- [Overview](tech/overview.md)
|
- [Overview](tech/overview.md)
|
||||||
- [Status Today](tech/statustoday.md)
|
- [Presentation](tech/presentation.md)
|
||||||
- [The Cloud Today](tech/cloud_today.md)
|
- [The Cloud Today](tech/cloud_today.md)
|
||||||
- [The Internet Today](tech/internet_today.md)
|
- [The Internet Today](tech/internet_today.md)
|
||||||
- [History of Computers](tech/history/c64.md)
|
- [History of Computers](tech/history/c64.md)
|
||||||
- [Too Many Layers](tech/history/layers.md)
|
- [Too Many Layers](tech/history/layers.md)
|
||||||
- [Cloud Re-invented](tech/how_does_it_work.md)
|
- [The Cloud Re-invented](tech/cloud_reinvented.md)
|
||||||
|
- [The Internet Re-invented](tech/internet_reinvented.md)
|
||||||
|
- [Cloud Beyond Cost](tech/cloud_like_insurance.md)
|
||||||
- [World Records](tech/world_records.md)
|
- [World Records](tech/world_records.md)
|
||||||
- [Architecture](tech/architecture.md)
|
- [Architecture](tech/architecture.md)
|
||||||
|
- [Cloud Engine](tech/cloudengine.md)
|
||||||
|
- [Empowers Internet](tech/internet_arch.md)
|
||||||
|
- [Hero as Virtual Administrator](tech/hero_virtual_admin.md)
|
||||||
- [Key Innovations](tech/key_innovations_overview.md)
|
- [Key Innovations](tech/key_innovations_overview.md)
|
||||||
- [Compute](tech/compute_inno.md)
|
- [Compute](tech/compute_inno.md)
|
||||||
- [Zero-OS](tech/zos_innovation.md)
|
- [Zero-OS](tech/zos_innovation.md)
|
||||||
@ -24,7 +29,9 @@
|
|||||||
- [Quantum Safe Filesystem](tech/qsfs_innovation.md)
|
- [Quantum Safe Filesystem](tech/qsfs_innovation.md)
|
||||||
- [FungiStor](tech/fungistor_innovation.md)
|
- [FungiStor](tech/fungistor_innovation.md)
|
||||||
- [Energy Efficient](tech/energy_efficient.md)
|
- [Energy Efficient](tech/energy_efficient.md)
|
||||||
- [Status/Roadmap](tech/tfgrid_roadmap.md)
|
- [Status/Roadmap](tech/roadmap.md)
|
||||||
|
- [Enterprise Roadmap](tech/enterprise_roadmap.md)
|
||||||
|
- [Opensource TFGrid Roadmap](tech/tfgrid_roadmap.md)
|
||||||
- [Hero Roadmap](tech/hero_roadmap.md)
|
- [Hero Roadmap](tech/hero_roadmap.md)
|
||||||
- [ThreeFold Core Features](tech/features.md)
|
- [ThreeFold Core Features](tech/features.md)
|
||||||
- [Compute](tech/compute.md)
|
- [Compute](tech/compute.md)
|
||||||
@ -41,15 +48,15 @@
|
|||||||
- [Network](tech/networking.md)
|
- [Network](tech/networking.md)
|
||||||
- [Mycelium](tech/mycelium.md)
|
- [Mycelium](tech/mycelium.md)
|
||||||
- [Web Gateway](tech/webgw.md)
|
- [Web Gateway](tech/webgw.md)
|
||||||
- [Partners / Utilization](partners_utilization/partners.md)
|
- [Use Cases](partners_utilization/partners.md)
|
||||||
- [Sikana](partners_utilization/sikana.md)
|
- [Tier-S DC](partners_utilization/tier_s_datacenter.md)
|
||||||
- [Vindo](partners_utilization/vindo.md)
|
- [Digital Freezone](partners_utilization/freezone.md)
|
||||||
- [Mkondo](partners_utilization/mkondo.md)
|
- [Mkondo](partners_utilization/mkondo.md)
|
||||||
- [Vverse](partners_utilization/vverse.md)
|
- [Vverse](partners_utilization/vverse.md)
|
||||||
- [Holochain](partners_utilization/holochain.md)
|
- [Holochain](partners_utilization/holochain.md)
|
||||||
- [TZG](partners_utilization/tanzania.md)
|
- [TZG](partners_utilization/tanzania.md)
|
||||||
- [Tier-S DC](partners_utilization/tier_s_datacenter.md)
|
- [Sikana](partners_utilization/sikana.md)
|
||||||
- [OW Freezone](partners_utilization/freezone.md)
|
- [Vindo](partners_utilization/vindo.md)
|
||||||
- [Helium](partners_utilization/helium.md)
|
|
||||||
|
|
||||||
|
<!-- - [Helium](partners_utilization/helium.md) -->
|
||||||
<!-- - [Elestio](partners_utilization/elestio.md) -->
|
<!-- - [Elestio](partners_utilization/elestio.md) -->
|
||||||
|
|||||||
@ -11,4 +11,4 @@ GEP stands for Grid Enhancement Proposal. A GEP is a design document providing i
|
|||||||
|
|
||||||
*some inspiration comes from https://www.python.org/dev/peps/pep-0001*
|
*some inspiration comes from https://www.python.org/dev/peps/pep-0001*
|
||||||
|
|
||||||
!!!def alias:gep
|
|
||||||
|
|||||||
@ -64,6 +64,5 @@ To use a dedicated node, you will have to reserve a 3node for yourself in your a
|
|||||||
|
|
||||||
!!!include:staking_discount_levels
|
!!!include:staking_discount_levels
|
||||||
|
|
||||||
!!!def alias:tfpricing,cloudunit_pricing,threefold_pricing
|
|
||||||
|
|
||||||
!!!tfpriceinfo
|
!!!tfpriceinfo
|
||||||
|
|||||||
@ -1,9 +1,9 @@
|
|||||||
# INCA Marketplace
|
# TF Marketplace
|
||||||
|
|
||||||
> planned for TFGrid 4.0 = INCA Grid
|
> planned for TFGrid 4.0 = TFGrid
|
||||||
|
|
||||||
The INCA Marketplace allows people to buy our TF Grid products and services using credit cards, digital currencies, …
|
The TF Marketplace allows people to buy our TF Grid products and services using credit cards, digital currencies, …
|
||||||
|
|
||||||
Underneath of course everything goes back to INCA as the reserve currency.
|
Underneath of course everything goes back to INCA as the reserve currency.
|
||||||
|
|
||||||
The INCA Marketplace will have a simplified API which allows our partners to buy and sell services more easily and of course in line with all required regulations.
|
The TF Marketplace will have a simplified API which allows our partners to buy and sell services more easily and of course in line with all required regulations.
|
||||||
|
|||||||
@ -2,4 +2,3 @@
|
|||||||
|
|
||||||
!!!include:farming_certification_benefits
|
!!!include:farming_certification_benefits
|
||||||
|
|
||||||
!!!def alias:certified_farming
|
|
||||||
@ -30,4 +30,4 @@ The Titan V2.1 node is a certified node. Certified nodes are eligible for more
|
|||||||
- A certified farmer is required to use certified_nodes.
|
- A certified farmer is required to use certified_nodes.
|
||||||
|
|
||||||
|
|
||||||
!!!def alias:certified_node
|
|
||||||
|
|||||||
BIN
collections/partners_utilization/cloud_farming.jpg
Normal file
BIN
collections/partners_utilization/cloud_farming.jpg
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 146 KiB |
@ -1,16 +1,15 @@
|
|||||||
|
|
||||||
|
|
||||||
# Partners
|
# Use Cases.
|
||||||
|
|
||||||
The following partners all have the potential to utilize a lot of our capacity and will drive the growth of our grid.
|
The following usecases are concrete uses cases which will be rolled out on our V4.0 of our Platform
|
||||||
|
|
||||||
|
- [Tier S Datacenter](tier_s_datacenter.md) more secure and efficient datacenter approach
|
||||||
- [Holochain](holochain.md) holochain, peer2peer transaction layer and dapp layer on top of TFGrid
|
- [Holochain](holochain.md) holochain, peer2peer transaction layer and dapp layer on top of TFGrid
|
||||||
- [Earth Wallet](earth_wallet.md) alternative to BTC Lightening (cheap transactions, scale)
|
|
||||||
- [Digital Freezone](freezone.md) a digital freezone made for hundreds of millions of people.
|
- [Digital Freezone](freezone.md) a digital freezone made for hundreds of millions of people.
|
||||||
- [Tanzania Sovereign Internet](tanzania.md) a sovereign Internet for a country
|
- [Tanzania Sovereign Internet](tanzania.md) a sovereign Internet for a country
|
||||||
- [Mkondo](mkondo.md) most realistic rendering of VR/AR env on top of TFGrid
|
- [Mkondo](mkondo.md) most realistic rendering of VR/AR env on top of TFGrid
|
||||||
- [Vindo](vindo.md) collaborative metaverse, best quality at low bandwidth
|
- [Vindo](vindo.md) collaborative metaverse, best quality at low bandwidth
|
||||||
- [Vverse](vverse.md) virtual reality museum
|
- [Vverse](vverse.md) virtual reality museum
|
||||||
- [Tier S Datacenter](tier_s_datacenter.md) more secure and efficient datacenter approach
|
|
||||||
- [Helium](helium.md) Decentralized IoT Network
|
|
||||||
- [Sikana](sikana.md) Virtual Learning Platfrom
|
- [Sikana](sikana.md) Virtual Learning Platfrom
|
||||||
|
|
||||||
|
|||||||
@ -5,16 +5,10 @@
|
|||||||
Its important that every contributor to this project has gone over next checklist.
|
Its important that every contributor to this project has gone over next checklist.
|
||||||
|
|
||||||
- [ ] I have read [The Collaboration Doc](collaboration.md) and browsed to the underlying info.
|
- [ ] I have read [The Collaboration Doc](collaboration.md) and browsed to the underlying info.
|
||||||
- I am committed to work this way and understand why.
|
|
||||||
- [ ] I have basic understand of [The Tech](technology.md), and did some effort understanding the basics.
|
- [ ] I have basic understand of [The Tech](technology.md), and did some effort understanding the basics.
|
||||||
- [ ] Not all has been finalized yet, quite some further ideas to be finalized.
|
|
||||||
- I will give my feedback to relevant stakeholders.
|
|
||||||
- [ ] I have read the [**Requirements**](projectinca/requirements.md) and agree
|
- [ ] I have read the [**Requirements**](projectinca/requirements.md) and agree
|
||||||
|
|
||||||
## For go2market contributors
|
Some practical items:
|
||||||
|
|
||||||
Everyone dealing with product management, tokens, marketing or any other go2market activity.
|
|
||||||
|
|
||||||
- [ ] [I have an account on gitea](https://git.ourworld.tf)
|
- [ ] [I have an account on gitea](https://git.ourworld.tf)
|
||||||
- If not contact Mik or Sabrina
|
|
||||||
- [ ] [I am committed to work with our Kanban on Gitea](https://git.ourworld.tf/tfgrid/circle_go2market/projects/80)
|
- [ ] [I am committed to work with our Kanban on Gitea](https://git.ourworld.tf/tfgrid/circle_go2market/projects/80)
|
||||||
@ -3,29 +3,19 @@
|
|||||||
|
|
||||||
|
|
||||||
|
|
||||||
<h2>Table of Contents</h2>
|
|
||||||
|
|
||||||
- [Introduction](#introduction)
|
|
||||||
- [V3.11](#v311)
|
|
||||||
- [V4.x](#v4x)
|
|
||||||
|
|
||||||
***
|
|
||||||
|
|
||||||
## Introduction
|
|
||||||
|
|
||||||
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.
|
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.
|
||||||
|
|
||||||
## V3.11
|
## V3.x
|
||||||
|
|
||||||
| Description | Good Enough (1) | Remark |
|
| Description | Good Enough (1) | Remark |
|
||||||
| ---------------------------------------------------------- | --------------- | ----------------------------------------------------------------------------------------------------- |
|
| ---------------------------------------------------------- | --------------- | ----------------------------------------------------------------------------------------------------- |
|
||||||
| TFNodes owned and invested by Independent Farmers | Yes | less than 10% owned by ThreeFold Cloud/Dubai |
|
| TFNodes owned and invested by Independent Farmers | Yes | less than 5% owned by ThreeFold Cloud/Dubai |
|
||||||
| open documentation & feedback | Yes | all opensource on github, anyone can contribute and give feedback, whcih does happen quite well |
|
| open documentation & feedback | Yes | all opensource on github, anyone can contribute and give feedback.|
|
||||||
| transparancy and input on any change to do with tokenomics | Yes | see the discussions on forum (3) and GEP's process |
|
| transparancy and input on any change to do with tokenomics | Yes | see the discussions on forum (3) and GEP's process |
|
||||||
| transparancy about tokens, history | Yes | see wiki (2) which is also on github, a lot of info |
|
| transparancy about tokens, history | Yes | see github |
|
||||||
| TFChain deployment | No | too few run the validator stack, we need more validators |
|
| TFChain deployment | No | too few run the validator stack, we need more validators |
|
||||||
| Code Development | No | +90% done by TFTech , we need more participants |
|
| Code Development | No | +90% done by TFTech , we need more participants |
|
||||||
| Funding For Tech Creation & TFGrid Promotion | No | +- all done by TFTech and TF Cloud , we need more participants to make this community owned |
|
| Funding For Tech Creation & TFGrid Promotion | No | +- 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 |
|
| 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 (4), everyone can review, comment |
|
| quality and transparancy of code | Yes | all is on github (4), everyone can review, comment |
|
||||||
| input on process & roadmap for code development | Yes | all is on github (4), everyone can review, comment |
|
| input on process & roadmap for code development | Yes | all is on github (4), everyone can review, comment |
|
||||||
@ -34,37 +24,19 @@ Decentralization, in our view, isn't solely about employing blockchain technolog
|
|||||||
| minting of tokens (farming) | Yes | code uses the information on blockchain and creates minting report |
|
| 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 (5) and hash kept on blockchain when doing the minting |
|
| verification of minting of tokens (farming) | Yes | minting reports checked by guardians (5) 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 |
|
| the actual minting | Yes | multisignature of guardians is needed to valudate the transactions, each minting links back to report |
|
||||||
| its possible for super smart hackers to fake capacity | No | probably yes on non certified nodes, yes but not easy (6) |
|
| its possible for super smart hackers to fake capacity | No | probably yes on non certified nodes, but not easy (6) |
|
||||||
| are all components redundant and distributed enough | No | e.g. TF Hub, TF Proxy, do note this does not weaken security, only reliability (7) |
|
| are all components redundant and distributed enough | No | we need more TFGrid Validators |
|
||||||
|
|
||||||
|
|
||||||
- (1) This is our subjective evaluation and should not be construed as a guarantee or commitment. We welcome any differing opinions or feedback.
|
- (1) This is our subjective evaluation and should not be construed as a guarantee or commitment. We welcome any differing opinions or feedback.
|
||||||
- (2) [The wiki](https://library.threefold.me/info/threefold#/)
|
- (2) [Github TF Dubai](https://github.com/threefoldfoundation)
|
||||||
- (3) [The forum](https://forum.threefold.io/)
|
- (3) [The forum](https://forum.threefold.io/)
|
||||||
- (4) [Github](https://github.com/threefoldtech), list of components see [here](https://github.com/threefoldtech/home/blob/master/wiki/components/components_overview.md)
|
- (4) [Github TF9](https://github.com/threefoldtech), list of components see [here](https://github.com/threefoldtech/home/blob/master/wiki/components/components_overview.md)
|
||||||
- (5) there are 9 Guardians, 6 need to approve (TODO, double check)
|
- (5) there are multiple Guardians to guide this process
|
||||||
- (6) they would have to re-engineer how ZOS works and tells TFChain, but human chain = 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.
|
- (6) they would have to re-engineer how ZOS works and tells TFChain, but human chain = 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.
|
||||||
- (7) TF Cloud is operating a kubernetes cluster to run some of these services. In v3.13 we expect more farmers to run this independently
|
|
||||||
|
|
||||||
|
|
||||||
## V4.x
|
## V4.x
|
||||||
|
|
||||||
With V4.x, we aim at the first 100% independent grid deployment.
|
Our next generation Grid has lots of improvements in relation to decentralization, see the specific document for 4.x
|
||||||
|
|
||||||
> mid to end 2024
|
|
||||||
|
|
||||||
- Run Independently means
|
|
||||||
- less than 20% of the validators or other tech components should be managed by TFTech or TFCloud
|
|
||||||
- less than 20% of the guardians are linked to TFTech or TFCloud
|
|
||||||
- guardians will have to decide on upgrades of 3nodes linked to their regional internet
|
|
||||||
- Anyone community in the world can run their own regional Internet without any help of TFCloud/TFTech.
|
|
||||||
- This basically means if TFTech and TFCloud would no longer exist and community has interest to keep on funding the project, then the project can continue by itself.
|
|
||||||
|
|
||||||
Following features make sure the grid can get to full independance.
|
|
||||||
|
|
||||||
- peer2peer billing & payment
|
|
||||||
- peer2peer deployments
|
|
||||||
- peer2peer farmering cooperative (group farmers to become more effective)
|
|
||||||
- compatibility with major money blockchains
|
|
||||||
|
|
||||||
|
|
||||||
@ -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 (TFT/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.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -7,7 +7,7 @@ mnode_2b.png
|
|||||||
mnode_lr.png
|
mnode_lr.png
|
||||||
mnode_physical.png
|
mnode_physical.png
|
||||||
networkmap.png
|
networkmap.png
|
||||||
INCA Router.png
|
Mycelium Router.png
|
||||||
tfrouter_2.png
|
tfrouter_2.png
|
||||||
tfrouter_lr.png
|
tfrouter_lr.png
|
||||||
tfrouter_physical.png
|
tfrouter_physical.png
|
||||||
|
|||||||
@ -15,11 +15,11 @@ The farmers make capacity available and specify their price.
|
|||||||
|
|
||||||
The recommended pricing is:
|
The recommended pricing is:
|
||||||
|
|
||||||
- $0.1-10 for AISlice Capacity (GPU Nodes with lots of memory, cpu for AI workloads) (per hour)
|
- $0.1-10 for AI Slice Capacity (GPU Nodes with lots of memory, cpu for AI workloads) (per hour)
|
||||||
- $0.005-4 for CloudSlice Capacity (VM, Containers, Kubernetes, ...) (per hour)
|
- $0.005-4 for Cloud Slice Capacity (VM, Containers, Kubernetes, ...) (per hour)
|
||||||
- Options: $0.005-0.02 for 1 GB Storage (per month)
|
- Options: $0.005-0.02 for 1 GB Storage (per month)
|
||||||
- Options: $0.01-0.2 for 1 GB Transfer (bandwidth)
|
- Options: $0.01-0.2 for 1 GB Transfer (bandwidth)
|
||||||
- $0.005-4 for CloudSlice Capacity (VM, Containers, Kubernetes, ...) (per hour)
|
- $0.005-4 for Cloud Slice Capacity (VM, Containers, Kubernetes, ...) (per hour)
|
||||||
- $0.2-2 for Storage Box (100 GB of storage) (per month)
|
- $0.2-2 for Storage Box (100 GB of storage) (per month)
|
||||||
|
|
||||||
- Farmers can also make money with other services e.g.
|
- Farmers can also make money with other services e.g.
|
||||||
@ -44,7 +44,7 @@ For red cells, the additional farming booster reward is the highest.
|
|||||||
|
|
||||||
### How to Become a Farmer
|
### How to Become a Farmer
|
||||||
|
|
||||||
- Buy a *INCA NODE (Compute/Storage/AI node) or *INCA ROUTER (Mycelium Network Node).
|
- Buy a 3Node (Compute/Storage/AI node) or Mycelium Router (Mycelium Network Node).
|
||||||
- Assemble your own node
|
- Assemble your own node
|
||||||
- Our software makes it easy to get started. Check [ThreeFold](https://threefold.io/) v3 for more info.
|
- Our software makes it easy to get started. Check [ThreeFold](https://threefold.io/) v3 for more info.
|
||||||
|
|
||||||
@ -74,7 +74,7 @@ If a farmer uses a farming pool, they will have to give a part of their reward t
|
|||||||
|
|
||||||
Incoming Internet traffic should be enabled to earn rewards from network bandwidth.
|
Incoming Internet traffic should be enabled to earn rewards from network bandwidth.
|
||||||
|
|
||||||
If a farmer lacks this capability, their INCA Node will connect to a neighboring INCA Node with good internet connectivity and public incoming access. In this case, the neighbor farmer will earn money from the Internet traffic, while the farmer will continue to earn rewards for compute and storage."
|
If a farmer lacks this capability, their 3Node will connect to a neighboring 3Node with good internet connectivity and public incoming access. In this case, the neighbor farmer will earn money from the Internet traffic, while the farmer will continue to earn rewards for compute and storage."
|
||||||
|
|
||||||
All traffic is end2end encrypted over the Mycelium network = our P2P Network which lives on top of current Internet.
|
All traffic is end2end encrypted over the Mycelium network = our P2P Network which lives on top of current Internet.
|
||||||
|
|
||||||
|
|||||||
@ -3,7 +3,7 @@
|
|||||||
|--------------------------|--------------------------|
|
|--------------------------|--------------------------|
|
||||||
|  |  |
|
|  |  |
|
||||||
|
|
||||||
# INCA Node AI
|
# 3Node AI
|
||||||
|
|
||||||
* <200 watt avg out
|
* <200 watt avg out
|
||||||
* 16 Cores Up to 4.5GHz
|
* 16 Cores Up to 4.5GHz
|
||||||
|
|||||||
@ -2,7 +2,7 @@
|
|||||||
|
|
||||||
|
|
||||||
|
|
||||||
# INCA Node Platinum
|
# 3Node Platinum
|
||||||
|
|
||||||
* <100 watt avg out
|
* <100 watt avg out
|
||||||
* 24 Cores
|
* 24 Cores
|
||||||
|
|||||||
@ -1,7 +1,7 @@
|
|||||||
|
|
||||||
|
|
||||||
|
|
||||||
# INCA Node Silver
|
# 3Node Silver
|
||||||
|
|
||||||
* <20-25 watt
|
* <20-25 watt
|
||||||
* 4 Cores Up to 3.4GHz
|
* 4 Cores Up to 3.4GHz
|
||||||
|
|||||||
@ -1,16 +1,16 @@
|
|||||||
|
|
||||||
# Available INCA Nodes
|
# Available INCA Nodes
|
||||||
|
|
||||||
### INCA Node Silver
|
### 3Node Silver
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
Almost ready to go
|
Almost ready to go
|
||||||
|
|
||||||
> see [INCA Node Silver](inca_node_silver.md)
|
> see [3Node Silver](inca_node_silver.md)
|
||||||
|
|
||||||
|
|
||||||
### INCA Node Gold
|
### 3Node Gold
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -21,7 +21,7 @@ Almost ready to go
|
|||||||
|
|
||||||
It will cost less than 1000 USD.
|
It will cost less than 1000 USD.
|
||||||
|
|
||||||
### INCA Node Platinum
|
### 3Node Platinum
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -33,7 +33,7 @@ It will cost less than 1000 USD.
|
|||||||
|
|
||||||
It will cost less than 2000 USD.
|
It will cost less than 2000 USD.
|
||||||
|
|
||||||
### INCA Node AI
|
### 3Node AI
|
||||||
|
|
||||||
| | |
|
| | |
|
||||||
|--------------------------|--------------------------|
|
|--------------------------|--------------------------|
|
||||||
@ -47,12 +47,12 @@ It will cost less than 2000 USD.
|
|||||||
|
|
||||||
|
|
||||||
|
|
||||||
### INCA Node Datacenter
|
### 3Node Datacenter
|
||||||
|
|
||||||
- put your own INCA Node in a datacenter of choice, make sure you have great and cost effective reliable connectivity to internet.
|
- put your own 3Node in a datacenter of choice, make sure you have great and cost effective reliable connectivity to internet.
|
||||||
- The Farmer buys their own hardware, ThreeFold supports the farmer to get up and running.
|
- The Farmer buys their own hardware, ThreeFold supports the farmer to get up and running.
|
||||||
|
|
||||||
### INCA Node Dedicated Rental
|
### 3Node Dedicated Rental
|
||||||
|
|
||||||
- rent a node in a dacenter, make sure you have good capacity in that datacenter. Companies like OVH and Hetzner come to mind as reliable and cost effective.
|
- rent a node in a dacenter, make sure you have good capacity in that datacenter. Companies like OVH and Hetzner come to mind as reliable and cost effective.
|
||||||
|
|
||||||
|
|||||||
@ -1,13 +1,13 @@
|
|||||||
|
|
||||||
## INCA Routers
|
## INCA Routers
|
||||||
|
|
||||||
The INCA Routers allow everyone to connect the users of our network with the INCA Node.
|
The INCA Routers allow everyone to connect the users of our network with the 3Node.
|
||||||
|
|
||||||
### INCA Router Indoor
|
### Mycelium Router Indoor
|
||||||
|
|
||||||
We are partnering with WiFi device vendors to extend the Mycelium Network in a full peer-to-peer fashion.
|
We are partnering with WiFi device vendors to extend the Mycelium Network in a full peer-to-peer fashion.
|
||||||
|
|
||||||
WiFi 6 is now a reality and a native capacity from our first chosen node. The INCA Router Indoor can be purchased starting now.
|
WiFi 6 is now a reality and a native capacity from our first chosen node. The Mycelium Router Indoor can be purchased starting now.
|
||||||
|
|
||||||
It's an exciting node with a reasonable price point and enough CPU capacity to run the Mycelium Network stack within the node itself.
|
It's an exciting node with a reasonable price point and enough CPU capacity to run the Mycelium Network stack within the node itself.
|
||||||
|
|
||||||
@ -16,23 +16,23 @@ More than 1 node can be installed in a larger office, hotel, home, etc., and the
|
|||||||
|
|
||||||
|
|
||||||
|
|
||||||
### INCA Router Edge
|
### Mycelium Router Edge
|
||||||
|
|
||||||
The INCA Router Edge is a powerhouse, equipped with a strong CPU and lots of memory to run edge network functions. This router can be connected to multiple uplinks (satellite, cable, fiber, 5G), ...
|
The Mycelium Router Edge is a powerhouse, equipped with a strong CPU and lots of memory to run edge network functions. This router can be connected to multiple uplinks (satellite, cable, fiber, 5G), ...
|
||||||
|
|
||||||
Mycelium ensures that the shortest and fastest path is always used, and all communication is end-to-end encrypted between an INCA Router or even your mobile or computer if you have the Mycelium agent installed.
|
Mycelium ensures that the shortest and fastest path is always used, and all communication is end-to-end encrypted between an Mycelium Router or even your mobile or computer if you have the Mycelium agent installed.
|
||||||
|
|
||||||
The integrated antennas are powerful, with a long range, and are controlled independently.
|
The integrated antennas are powerful, with a long range, and are controlled independently.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
This INCA Router is super fast and has lots of connectivity.
|
This Mycelium Router is super fast and has lots of connectivity.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
> Purchasing this INCA router is currently possible.
|
> Purchasing this Mycelium Router is currently possible.
|
||||||
|
|
||||||
### INCA Router Outdoor + Long Range
|
### Mycelium Router Outdoor + Long Range
|
||||||
|
|
||||||
We are in the process of selecting the appropriate network equipment to bridge between two locations and enable the creation of meshed wireless networks at the lowest cost.
|
We are in the process of selecting the appropriate network equipment to bridge between two locations and enable the creation of meshed wireless networks at the lowest cost.
|
||||||
|
|
||||||
@ -46,4 +46,4 @@ Currently, we rely on fiber or existing internet connections to link between loc
|
|||||||
|
|
||||||
|
|
||||||
|
|
||||||
<!-- !!task.add story:'TFRouter_selection' title:'describe loran on INCA Router' -->
|
<!-- !!task.add story:'TFRouter_selection' title:'describe loran on Mycelium Router' -->
|
||||||
@ -1,11 +1,15 @@
|
|||||||
|
|
||||||
|
|
||||||
|
|
||||||
# Funding Through Project Mycelium and/or OurWorld
|
# Funding Through OurWorld
|
||||||
|
|
||||||
Our partner projects are fundraising and do need a lot of capacity, they are planning to buy a lot of TFT/INCA.
|
Our partner projects are fundraising and do need a lot of capacity, they are planning to buy a lot of TFT/INCA.
|
||||||
|
|
||||||
# Funding INCA-G
|
# Funding Through Private Token Sale
|
||||||
|
|
||||||
|
We are factfinding.
|
||||||
|
|
||||||
|
# Funding Through INCA-G
|
||||||
|
|
||||||
Funding INCA-G needs to be explored further. Selling INCA-G NFT tokens through entities such as SwissBorg might be a good option.
|
Funding INCA-G needs to be explored further. Selling INCA-G NFT tokens through entities such as SwissBorg might be a good option.
|
||||||
|
|
||||||
|
|||||||
@ -1,6 +1,2 @@
|
|||||||
We believe in the power of grants to build together the necessary components or reward the community to further develop the project.
|
We believe in the power of grants to build together the necessary components or reward the community to further develop the project.
|
||||||
|
|
||||||
- 1,2,3.X series are called TFGrid
|
|
||||||
- The website is www.threefold.io
|
|
||||||
- 4.x series called INCA (INternet CApacity)
|
|
||||||
- The website will be released soon
|
|
||||||
|
|||||||
@ -1,8 +1,8 @@
|
|||||||
## Grant Voting Process
|
## Grant Voting Process
|
||||||
|
|
||||||
The voting process is as follows:
|
> JUST IDEAS, not ok yet
|
||||||
|
|
||||||
- Go to INCA Connect
|
The voting process is as follows:
|
||||||
- See the projects
|
- See the projects
|
||||||
- Vote yes or no for a given project
|
- Vote yes or no for a given project
|
||||||
- Vote requests for projects need to be live for a minimum of 2 weeks
|
- Vote requests for projects need to be live for a minimum of 2 weeks
|
||||||
|
|||||||
@ -1,10 +1,5 @@
|
|||||||
# Project INCA Grants
|
# Suggested Future Grant Distribution
|
||||||
|
|
||||||
!!wiki.include page:'projectinca:grant_versions.md'
|
|
||||||
|
|
||||||
There are no grants defined yet for our INCA release.
|
|
||||||
|
|
||||||
Please contact us to let us know on which projects you would like to work, below you can see a suggested Distrubution of grants.
|
|
||||||
|
|
||||||
```echarts
|
```echarts
|
||||||
option = {
|
option = {
|
||||||
@ -22,12 +17,12 @@ option = {
|
|||||||
type: 'pie',
|
type: 'pie',
|
||||||
radius: '70%',
|
radius: '70%',
|
||||||
data: [
|
data: [
|
||||||
{ value: 20, name: 'Community Expansion Projects' },
|
{ value: 10, name: 'Community Expansion Projects' },
|
||||||
{ value: 20, name: 'Development of Hardware for INCA' },
|
|
||||||
{ value: 10, name: 'Organization of Rewards for Hackathlons' },
|
{ value: 10, name: 'Organization of Rewards for Hackathlons' },
|
||||||
{ value: 15, name: 'Organization of Localized Chapters' },
|
{ value: 15, name: 'Organization of Localized Chapters' },
|
||||||
{ value: 30, name: 'Development of Code' },
|
{ value: 30, name: 'Development of Code' },
|
||||||
{ value: 5, name: 'Training, Product Marketing' },
|
{ value: 5, name: 'Training, Product Marketing' },
|
||||||
|
{ value: 20, name: 'Development of Mycelium Router & Volume 3Node ' },
|
||||||
],
|
],
|
||||||
emphasis: {
|
emphasis: {
|
||||||
itemStyle: {
|
itemStyle: {
|
||||||
@ -41,6 +36,5 @@ option = {
|
|||||||
};
|
};
|
||||||
```
|
```
|
||||||
|
|
||||||
## TFT Grants Treasury
|
Please contact us to let us know on which projects you would like to work, below you can see a suggested Distrubution of grants.
|
||||||
|
|
||||||
- **660,000,000 INCA is available for Grants (over all releases)**
|
|
||||||
@ -1,9 +1,7 @@
|
|||||||
# TFGrid 3.x Grants
|
# Current Grants
|
||||||
|
|
||||||
Below you can find the grants as are open and being executed on for the 3.x version of our project.
|
Below you can find the grants as are open and being executed on for the 3.x version of our project.
|
||||||
|
|
||||||
> It is possible that these grants will move to our Project INCA and be unified as one set of grants.
|
|
||||||
|
|
||||||
```echarts
|
```echarts
|
||||||
option = {
|
option = {
|
||||||
title: {
|
title: {
|
||||||
@ -20,17 +18,18 @@ option = {
|
|||||||
type: 'pie',
|
type: 'pie',
|
||||||
radius: '70%',
|
radius: '70%',
|
||||||
data: [
|
data: [
|
||||||
{ value: 10, name: 'Deploy AISlices' },
|
{ value: 10, name: 'Deploy AI Slices' },
|
||||||
{ value: 15, name: 'Deploy CloudSlices' },
|
{ value: 15, name: 'Deploy Cloud Slices' },
|
||||||
{ value: 5, name: 'Deploy StorageSlices' },
|
{ value: 5, name: 'Deploy StorageSlices' },
|
||||||
{ value: 5, name: 'Code INCA Marketplace' },
|
{ value: 5, name: 'Code TF Marketplace' },
|
||||||
{ value: 20, name: 'Contributor Rewards' },
|
{ value: 20, name: 'Contributor Rewards' },
|
||||||
{ value: 5, name: 'Chapter Tanzania' },
|
{ value: 5, name: 'Chapter Tanzania' },
|
||||||
{ value: 5, name: 'Chapter Brazil' },
|
{ value: 5, name: 'Chapter Brazil' },
|
||||||
{ value: 10, name: 'Biz dev rewards' },
|
{ value: 10, name: 'Biz dev rewards' },
|
||||||
{ value: 10, name: 'Code TFGrid 3.13' },
|
{ value: 10, name: 'Code TFGrid 3.13' },
|
||||||
{ value: 5, name: 'Code TFGrid 3.14' },
|
{ value: 5, name: 'Code TFGrid 3.14' },
|
||||||
{ value: 5, name: 'Deploy Thorchain DEX Launch' },
|
{ value: 2, name: 'Code TFGrid 3.15' },
|
||||||
|
{ value: 3, name: 'Code TFGrid 3.16' },
|
||||||
],
|
],
|
||||||
emphasis: {
|
emphasis: {
|
||||||
itemStyle: {
|
itemStyle: {
|
||||||
@ -44,28 +43,21 @@ option = {
|
|||||||
};
|
};
|
||||||
```
|
```
|
||||||
|
|
||||||
## TFT Grants Treasury
|
|
||||||
|
|
||||||
- At least 180,000,000 TFT (which could be converted to 360,000,000 INCA) is available for grants
|
|
||||||
- Projects defined below
|
|
||||||
- Will be available in the future on https://projectinca.info/projects
|
|
||||||
- Voting through INCA Connect
|
|
||||||
- <10m in locked pool (dead wallets)
|
|
||||||
|
|
||||||
## Reward Projects
|
## Reward Projects
|
||||||
|
|
||||||
Initial projects are listed below.
|
- [Deploy AI Slices](projectinca/grant_AI_Slices.md) : 10m TFT
|
||||||
|
- [Deploy Cloud Slices](projectinca/grant_Cloud_Slices.md) : 15m TFT
|
||||||
> Remark: all TFT are with vesting and have min execution price 0.1 USD per TFT or higher!
|
- [Deploy StorageSlices](projectinca/grant_storage_slices.md) : 5m TFT
|
||||||
|
- [Develop Marketplace](projectinca/marketplace_grant.md) : 5m TFT
|
||||||
- [Deploy AISlices](projectinca/grant_aislice.md) : 10m TFT
|
|
||||||
- [Deploy CloudSlices](projectinca/grant_cloudslice.md) : 15m TFT
|
|
||||||
- [Deploy StorageSlices](projectinca/grant_storageslice.md) : 5m TFT
|
|
||||||
- [Develop INCA Marketplace](projectinca/marketplace_grant.md) : 5m TFT
|
|
||||||
- [Contributor Rewards](projectinca/contributor_rewards.md) : rewards for contributors (10-25m TFT)
|
- [Contributor Rewards](projectinca/contributor_rewards.md) : rewards for contributors (10-25m TFT)
|
||||||
- [Chapter Tanzania](projectinca/chapter_tanzania.md) : 4,000 per 3Node, 10,000 TFT per hackathon
|
- [Chapter Tanzania](projectinca/chapter_tanzania.md) : 4,000 per 3Node, 10,000 TFT per hackathon
|
||||||
- [Chapter Brazil](projectinca/chapter_brazil.md) : 4,000 per 3Node, 10,000 TFT per hackathon
|
- [Chapter Brazil](projectinca/chapter_brazil.md) : 4,000 per 3Node, 10,000 TFT per hackathon
|
||||||
- [Biz dev rewards](projectinca/biz_dev_rewards.md) : 5% of raised token sales or other investments in TFT at 0.1 USD per TFT or higher.
|
- [Biz dev rewards](projectinca/biz_dev_rewards.md) : 5% of raised token sales or other investments in TFT at 0.1 USD per TFT or higher.
|
||||||
- [Code TFGrid 3.13](projectinca/grant_tf_3_13.md) : 10m TFT
|
- [Code TFGrid 3.13](projectinca/grant_tf_3_13.md) : 10m TFT
|
||||||
- [Code TFGrid 3.14](projectinca/grant_tf_3_14.md) : 5m TFT
|
- [Code TFGrid 3.14](projectinca/grant_tf_3_14.md) : 5m TFT
|
||||||
- [Establish Thorchain DEX](projectinca/grant_thorchain.md) : 5m TFT
|
|
||||||
|
## TFT Grants Treasury
|
||||||
|
|
||||||
|
- At least 150,000,000 TFT, today managed by TF Dubai and GEP's used to approve.
|
||||||
|
- GEP's still need to be executed to approve the grants, they are not suggested nor approved yet.
|
||||||
@ -1,8 +1,8 @@
|
|||||||
# AISlices Grants
|
# AI Slices Grants
|
||||||
|
|
||||||
The aim is to reward the creation of capacity for 1,000 AISlices, each available AISlice is rewarded as in the table below.
|
The aim is to reward the creation of capacity for 1,000 AI Slices, each available AI Slice is rewarded as in the table below.
|
||||||
|
|
||||||
The total size of the grant is 10m TFT but can be expended later.
|
The total size of the grant is 10m TFT but can be expanded later.
|
||||||
|
|
||||||
|
|
||||||
- terms
|
- terms
|
||||||
@ -18,16 +18,8 @@ The total size of the grant is 10m TFT but can be expended later.
|
|||||||
- location of datacenters
|
- location of datacenters
|
||||||
- company info which manages the servers
|
- company info which manages the servers
|
||||||
- Hosting agreement signed with TF DMCC
|
- Hosting agreement signed with TF DMCC
|
||||||
- Utilization of INCA Marketplace
|
- Utilization of TF Marketplace
|
||||||
- hoster provisions and makes [Ai slice](tfgrid4:aislice.md) available
|
- hoster provisions and makes [AI slices](tfgrid4:AI Slice.md) available
|
||||||
- Approved location, we are trying to expand good capacity in the world
|
- Approved location, we are trying to expand good capacity in the world
|
||||||
|
|
||||||
!!wiki.include page:'projectinca:box_vesting_include.md'
|
!!wiki.include page:'projectinca:box_vesting_include.md'
|
||||||
|
|
||||||
## Grant Calculation
|
|
||||||
|
|
||||||
We believe the current minimal real price of TFT is at least 0.1 or 0.2, not the current marketcap which has no liquidity
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
!!wiki.include page:'tfgrid4:cloudslice'
|
|
||||||
@ -1,6 +1,6 @@
|
|||||||
# CloudSlices Grants
|
# Cloud Slices Grants
|
||||||
|
|
||||||
The aim is to reward the creation of capacity for 100,000 StorageSlices, each available cloudslice is rewarded as in the table below.
|
The aim is to reward the creation of capacity for 100,000 StorageSlices, each available Cloud Slice is rewarded as in the table below.
|
||||||
|
|
||||||
- terms
|
- terms
|
||||||
- 15m TFT for aggregated capacity
|
- 15m TFT for aggregated capacity
|
||||||
@ -8,7 +8,6 @@ The aim is to reward the creation of capacity for 100,000 StorageSlices, each av
|
|||||||
- min price for release 0.1 USD per TFT
|
- min price for release 0.1 USD per TFT
|
||||||
- SLA achieved (sign off by TF Coop and/or TF DMCC)
|
- SLA achieved (sign off by TF Coop and/or TF DMCC)
|
||||||
- SLA
|
- SLA
|
||||||
- always at least 20 ip addr free per site
|
|
||||||
- uptime 99.9% achieved per month
|
- uptime 99.9% achieved per month
|
||||||
- bandwidth free +10 mbit/s
|
- bandwidth free +10 mbit/s
|
||||||
- servers can be filled till 90%
|
- servers can be filled till 90%
|
||||||
@ -17,16 +16,9 @@ The aim is to reward the creation of capacity for 100,000 StorageSlices, each av
|
|||||||
- location of datacenters
|
- location of datacenters
|
||||||
- company info which manages the servers
|
- company info which manages the servers
|
||||||
- Hosting agreement signed with TF DMCC
|
- Hosting agreement signed with TF DMCC
|
||||||
- Utilization of INCA Marketplace
|
- Utilization of TF Marketplace
|
||||||
- hoster provisions and makes [StorageSlices](tfgrid4:CloudSlice.md) available
|
- hoster provisions and makes [Cloud Slices](tfgrid4:Cloud Slice.md) available
|
||||||
- Approved location, we are trying to expand good capacity in the world
|
- Approved location, we are trying to expand good capacity in the world
|
||||||
|
|
||||||
!!wiki.include page:'projectinca:box_vesting_include.md'
|
!!wiki.include page:'projectinca:box_vesting_include.md'
|
||||||
|
|
||||||
## Grant Calculation
|
|
||||||
|
|
||||||
We believe the minimal real price of TFT is at least 0.1 or 0.2, not the current marketcap which has no liquidity
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
!!wiki.include page:'tfgrid4:cloudslice'
|
|
||||||
@ -1,6 +1,6 @@
|
|||||||
# StorageSlices Grant
|
# Storage Slices Grant
|
||||||
|
|
||||||
The aim is to reward the creation of capacity for 100,000 StorageSlices, each available storageslice is rewarded as in the table below.
|
The aim is to reward the creation of capacity for 100,000 StorageSlices, each available Storage Slice is rewarded as in the table below.
|
||||||
|
|
||||||
- terms
|
- terms
|
||||||
- 5m TFT for aggregated capacity
|
- 5m TFT for aggregated capacity
|
||||||
@ -17,16 +17,9 @@ The aim is to reward the creation of capacity for 100,000 StorageSlices, each av
|
|||||||
- location of datacenters
|
- location of datacenters
|
||||||
- company info which manages the servers
|
- company info which manages the servers
|
||||||
- Hosting agreement signed with TF DMCC
|
- Hosting agreement signed with TF DMCC
|
||||||
- Utilization of INCA Marketplace
|
- Utilization of TF Marketplace
|
||||||
- hoster provisions and makes [StorageSlices](tfgrid4:storageslice.md) available
|
- hoster provisions and makes [Storage Slices](tfgrid4:storageslice.md) available
|
||||||
- Approved location, we are trying to expand good capacity in the world
|
- Approved location, we are trying to expand good capacity in the world
|
||||||
|
|
||||||
!!wiki.include page:'projectinca:box_vesting_include.md'
|
!!wiki.include page:'projectinca:box_vesting_include.md'
|
||||||
|
|
||||||
## Grant Calculation
|
|
||||||
|
|
||||||
We believe the minimal real price of TFT is at least 0.1 or 0.2, not the current marketcap which has no liquidity
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
!!wiki.include page:'tfgrid4:storageslice'
|
|
||||||
@ -12,10 +12,3 @@ There is a grant of 10m TFT foreseen for the work done by the codescalers & TF9
|
|||||||
- customers operational
|
- customers operational
|
||||||
- See: https://dashboard.grid.tf/
|
- See: https://dashboard.grid.tf/
|
||||||
|
|
||||||
|
|
||||||
## The Tokens Are Vested
|
|
||||||
|
|
||||||
- Min price to sell 0.1 USD per TFT for 50% (means the developer can only sell their tokens once this price achieved)
|
|
||||||
- Min price to sell 0.15 USD per TFT for 50%
|
|
||||||
|
|
||||||
This makes sure we don't add to the price pressure.
|
|
||||||
@ -6,7 +6,7 @@ There is a grant of 5m TFT foreseen for the work as will be done by the codescal
|
|||||||
|
|
||||||
## Requirements
|
## Requirements
|
||||||
|
|
||||||
- The work as defined on [project management tool](https://git.ourworld.tf/tfgrid/circle_engineering/projects/28) is executed and delivered
|
- The work as defined on [project management tool](https://git.ourworld.tf/tfgrid/-/projects/46) is executed and delivered
|
||||||
- Project is delivered
|
- Project is delivered
|
||||||
- opensource
|
- opensource
|
||||||
- customers operational
|
- customers operational
|
||||||
@ -14,10 +14,3 @@ There is a grant of 5m TFT foreseen for the work as will be done by the codescal
|
|||||||
- All is tested
|
- All is tested
|
||||||
- Release is on mainnet
|
- Release is on mainnet
|
||||||
|
|
||||||
|
|
||||||
## The Tokens Are Vested
|
|
||||||
|
|
||||||
- Min price to sell 0.1 USD per TFT for 50% (means the developer can only sell their tokens once this price achieved)
|
|
||||||
- Min price to sell 0.15 USD per TFT for 50%
|
|
||||||
|
|
||||||
This makes sure we don't add to the price pressure.
|
|
||||||
16
collections/projectinca/grants/tf3/grant_tf_3_15.md
Normal file
16
collections/projectinca/grants/tf3/grant_tf_3_15.md
Normal file
@ -0,0 +1,16 @@
|
|||||||
|
# Grant TFGrid 3.15
|
||||||
|
|
||||||
|
The teams are doing a lot of work on the next release which will give us much better supportability.
|
||||||
|
|
||||||
|
There is a grant of 2m TFT foreseen for the work as will be done by the codescalers & TF9 teams.
|
||||||
|
|
||||||
|
## Requirements
|
||||||
|
|
||||||
|
- The work as defined on [project management tool](https://git.ourworld.tf/tfgrid/-/projects/99) is executed and delivered
|
||||||
|
- Project is delivered
|
||||||
|
- opensource
|
||||||
|
- customers operational
|
||||||
|
- Result will be visible on https://dashboard.grid.tf/
|
||||||
|
- All is tested
|
||||||
|
- Release is on mainnet
|
||||||
|
|
||||||
@ -6,7 +6,7 @@ ThreeFold DMCC and TF COOP will host such a market place.
|
|||||||
|
|
||||||
The marketplace will intitially be used to sell
|
The marketplace will intitially be used to sell
|
||||||
|
|
||||||
- [CloudSlices](tfgrid4:cloudslice.md)
|
- [Cloud Slices](tfgrid4:Cloud Slice.md)
|
||||||
- [StorageSlices](tfgrid4:storageslice.md)
|
- [StorageSlices](tfgrid4:storageslice.md)
|
||||||
|
|
||||||
But many more services will be added.
|
But many more services will be added.
|
||||||
@ -28,8 +28,3 @@ There is a grant of 5m TFT foreseen.
|
|||||||
- opensource
|
- opensource
|
||||||
- working and operational with at least TF DMCC
|
- working and operational with at least TF DMCC
|
||||||
- first customers operational
|
- first customers operational
|
||||||
- Min price to sell 0.1 USD per TFT for 50%
|
|
||||||
- This means the developer can only sell their tokens once this price achieved
|
|
||||||
- Min price to sell 0.15 USD per TFT for 50%
|
|
||||||
|
|
||||||
This makes sure we don't add to the price pressure.
|
|
||||||
@ -11,6 +11,6 @@
|
|||||||
- The marketplace needs to do KYC for users doing more than 1k USD per month
|
- The marketplace needs to do KYC for users doing more than 1k USD per month
|
||||||
- The marketplace needs to run a monitoring stack to independently verify the SLA of the cloud and StorageSlices
|
- The marketplace needs to run a monitoring stack to independently verify the SLA of the cloud and StorageSlices
|
||||||
- The UI needs to be made in Reflex or Flet and be opensource
|
- The UI needs to be made in Reflex or Flet and be opensource
|
||||||
- Customers need to see their deployed CloudSlices or StorageSlices
|
- Customers need to see their deployed Cloud Slices or StorageSlices
|
||||||
- Customers can cancel their workloads: CloudSlices or StorageSlices
|
- Customers can cancel their workloads: Cloud Slices or StorageSlices
|
||||||
- Customers can see monitoring info of their workloads: CloudSlices or StorageSlices
|
- Customers can see monitoring info of their workloads: Cloud Slices or StorageSlices
|
||||||
|
|||||||
2
collections/projectinca/internal.md
Normal file
2
collections/projectinca/internal.md
Normal file
@ -0,0 +1,2 @@
|
|||||||
|
# Internal
|
||||||
|
|
||||||
@ -5,8 +5,4 @@
|
|||||||
|
|
||||||
Read this ebook to learn more about the project and how you can participate to this phase.
|
Read this ebook to learn more about the project and how you can participate to this phase.
|
||||||
|
|
||||||
>> Its all important we agree with the content in this ebook.
|
|
||||||
|
|
||||||
> CONFIDENTIAL INFORMATION
|
|
||||||
|
|
||||||
|
|
||||||
|
|||||||
@ -4,19 +4,4 @@
|
|||||||
|
|
||||||
|
|
||||||
|
|
||||||
## ThreeFold DePIN Launch: Project INCA
|
> TODO: explain how our marketcap and liquidity is too low in relation to the potential
|
||||||
|
|
||||||
Welcome to the Project INCA by ThreeFold.
|
|
||||||
|
|
||||||
With the project INCA, we want to create a decentralized future for ThreeFold by means of a launch in the DePIN ecosystem on top of Solana.
|
|
||||||
|
|
||||||
|
|
||||||
## Contributing to DePIN community
|
|
||||||
|
|
||||||
The current marketcap of the project is under 40 million USD, while other DePIN projects have marketcaps of 1 billion USD and more.
|
|
||||||
|
|
||||||
We believe that ThreeFold is ready and has rock solid technology to offer to the DePIN space. We think that what ThreeFold has to offer is comptabile to this space and that we can work in parallel and under many if not all projects in the DePIN space.
|
|
||||||
|
|
||||||
ThreeFold now has the necessary support from a lot of parties. We are entering a new exciting phase: Project INCA.
|
|
||||||
|
|
||||||
|
|
||||||
@ -1,11 +1,17 @@
|
|||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
> TODO: not good enough
|
||||||
|
|
||||||
# Liquidity
|
# Liquidity
|
||||||
|
|
||||||
## Solana
|
## Solana
|
||||||
|
|
||||||
Our INCA token will be released on Solana blockchain and we are relying on their ecosystem to provide liquidity.
|
Our INCA token will probably be released on Solana blockchain and we are relying on their ecosystem to provide liquidity.
|
||||||
|
|
||||||
|
## Exchanges
|
||||||
|
|
||||||
|
We are working with our partners to see which exchanges are good to list and get listed on.
|
||||||
|
|
||||||
## DEXes
|
## DEXes
|
||||||
|
|
||||||
|
|||||||
7
collections/projectinca/liquidity/liquidity_pool.md
Normal file
7
collections/projectinca/liquidity/liquidity_pool.md
Normal file
@ -0,0 +1,7 @@
|
|||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
# Liquidity Pool
|
||||||
|
|
||||||
|
> Kristof: todo
|
||||||
|
|
||||||
Binary file not shown.
|
Before Width: | Height: | Size: 348 KiB After Width: | Height: | Size: 303 KiB |
@ -1,13 +1,13 @@
|
|||||||
# INCA Marketplace
|
# ThreeFold Marketplace
|
||||||
|
|
||||||
We have reached a sizeable grid and want to promote commercialization.
|
We have reached a sizeable grid and want to promote commercialization.
|
||||||
|
|
||||||
- We are introducing a market place and our next generation grid v4.0 (INCA)
|
- We are introducing a market place and our next generation grid v4.0
|
||||||
- This will make it a lot more easy for 3rd parties to use our infrastructure
|
- This will make it a lot more easy for 3rd parties to use our infrastructure
|
||||||
- The currency as used on the marketplace is INCA, there will be a bridge between TFT and INCA
|
|
||||||
|
|
||||||
## Benefits
|
## Benefits
|
||||||
|
|
||||||
|
- Utilization of FIAT currencies (CHF, USD, EUR, ...)
|
||||||
- Better utilization of hardware capacity.
|
- Better utilization of hardware capacity.
|
||||||
- Farmers can define their own price, means market mechanism define price in relation to quality and supply
|
- Farmers can define their own price, means market mechanism define price in relation to quality and supply
|
||||||
- Easier for users to find right priced service
|
- Easier for users to find right priced service
|
||||||
@ -23,6 +23,6 @@ Read the next sections for more information on the slices concept.
|
|||||||
|
|
||||||
## See grants in relation to our marketplace
|
## See grants in relation to our marketplace
|
||||||
|
|
||||||
- [Development CloudSlices](projectinca:grant_cloudslice.md)
|
- [Development Cloud Slices](projectinca:grant_cloud_slices.md)
|
||||||
- [Development StorageSlices](projectinca:grant_storageslice.md)
|
- [Development Storage Slices](projectinca:grant_storage_slices.md)
|
||||||
- [Development AISlices](projectinca:grant_aislice.md)
|
- [Development AI Slices](projectinca:grant_AI_Slices.md)
|
||||||
@ -6,11 +6,11 @@
|
|||||||
|
|
||||||
|
|
||||||
|
|
||||||
- The Farmers set pricing but the sheet above shows you have the INCA Grid is super competive.
|
- The Farmers set pricing but the sheet above shows you have the TFGrid is super competive.
|
||||||
- In the calculation above the user has enough INCA in his wallet to get 50% discount.
|
- In the calculation above the user has enough TFT/INCA in his account on the TF Liquidity Pool to get 50% discount.
|
||||||
|
|
||||||
To see average prices you can look at [cloudorado](https://www.cloudorado.com/)
|
To see average prices you can look at [cloudorado](https://www.cloudorado.com/)
|
||||||
|
|
||||||
> see [this spreadsheet](https://docs.google.com/spreadsheets/d/1E6MpGs15h1_flyT5AtyKp1TixH1ILuGo5tzHdmjeYdQ/edit#gid=1821201540)
|
> see [this spreadsheet](https://docs.google.com/spreadsheets/d/1E6MpGs15h1_flyT5AtyKp1TixH1ILuGo5tzHdmjeYdQ/edit?gid=1821201540#gid=1821201540)
|
||||||
|
|
||||||
|
|
||||||
|
|||||||
@ -1,23 +0,0 @@
|
|||||||
## INCA Governance
|
|
||||||
|
|
||||||
A Wisdom Council approves budgets in line to tokenomics above.
|
|
||||||
|
|
||||||
The ThreeFold Wisdom Council will have 9 members in total. For any decision taken by the council, at least 6 must agree to go forward.
|
|
||||||
|
|
||||||
### Council Members
|
|
||||||
|
|
||||||
We start with 7 members and 2 more members will need to be added later on.
|
|
||||||
|
|
||||||
- 1 OurWorld (Kristof)
|
|
||||||
- 1 ThreeFold DMCC (Adnan)
|
|
||||||
- 1 TF9 (Jan)
|
|
||||||
- 1 Sikana (Greg)
|
|
||||||
- 1 CodeScalers (Nayer)
|
|
||||||
- 1 ThreeFold COOP (Sabrina)
|
|
||||||
- The COOP project is still ongoing and will still be created.
|
|
||||||
- 1 GreenEdge (MWW)
|
|
||||||
|
|
||||||
### Budget Allocation
|
|
||||||
|
|
||||||
- Budgets get allocated to projects on git.threefold.info
|
|
||||||
- Clear stories with clear budget allocations and cashflow tracking or time tracking
|
|
||||||
@ -5,13 +5,13 @@ The network of 3Nodes running Zero-OS will use a marketplace as its front end.
|
|||||||
|
|
||||||
## NEW
|
## NEW
|
||||||
|
|
||||||
- Simplified concept of [CloudSlices](tfgrid4:cloudslice.md) & [StorageSlices](tfgrid4:storageslice.md)
|
- Simplified concept of [Cloud Slices](tfgrid4:Cloud Slice.md) & [StorageSlices](tfgrid4:storageslice.md)
|
||||||
- SLA management
|
- SLA management
|
||||||
- More strict enforcement about suportability from a farming perspective
|
- More strict enforcement about suportability from a farming perspective
|
||||||
- All farmers can set their pricing
|
- All farmers can set their pricing
|
||||||
- Mutual credit based billing & tracking
|
- Mutual credit based billing & tracking
|
||||||
- Introduction of 3bot as our personal System administrator
|
- Introduction of 3bot as our personal System administrator
|
||||||
- Introduction of the INCA marketplace as the best way how to provision and manage workloads on the TFGrid 4.0
|
- Introduction of the TF Marketplace as the best way how to provision and manage workloads on the TFGrid 4.0
|
||||||
- INCA is the currency for TFGrid 4
|
- INCA is the currency for TFGrid 4
|
||||||
|
|
||||||
> TODO: and so much more
|
> TODO: and so much more
|
||||||
@ -4,13 +4,6 @@
|
|||||||
|
|
||||||
ThreeFold is expanding to the DePIN market.
|
ThreeFold is expanding to the DePIN market.
|
||||||
|
|
||||||
- INCA is the token for the TFGrid 4.x
|
|
||||||
- It's our commercialization token
|
|
||||||
- It will be used on the INCA marketplace
|
|
||||||
|
|
||||||
|
|
||||||
## info
|
|
||||||
|
|
||||||
- [INCA Token](inca1.md)
|
|
||||||
- [Governance](governance.md)
|
|
||||||
|
|
||||||
|
|||||||
@ -1,120 +0,0 @@
|
|||||||
|
|
||||||
|
|
||||||
# DePIN Launch Plan B
|
|
||||||
|
|
||||||
> In case not enough funding was found.
|
|
||||||
|
|
||||||
ThreeFold is expanding to the DePIN market.
|
|
||||||
|
|
||||||
- TFT is the token for the TFGrid 3.x
|
|
||||||
- It's our creator and founder token
|
|
||||||
- INCA is the token for the TFGrid 4.x
|
|
||||||
- It's our commercialization token
|
|
||||||
- It will be used on the INCA marketplace
|
|
||||||
- During 2024 the price between INCA & TFT is fixed
|
|
||||||
- 1 TFT buys 2 INCA
|
|
||||||
- From Jan 1 2025, the price is defined by market and will be in line to available INCA in liquidity pool.
|
|
||||||
|
|
||||||
## Two New Tokens on Solana
|
|
||||||
|
|
||||||
We launch 2 new tokens called INCA and INCA-G.
|
|
||||||
|
|
||||||
### INCA
|
|
||||||
|
|
||||||
> INCA = INternet CApacity (is the token of buying/selling Internet/Cloud Capacity)
|
|
||||||
|
|
||||||
- 4 billion INCA will be created
|
|
||||||
- 2 billion INCA can be bought by TFT holders transferring TFT to INCA (1 TFT buys 2 INCA)
|
|
||||||
- 2 billion INCA will be used to launch the next generation of our grid in the DePIN ecosystem
|
|
||||||
|
|
||||||
<br>
|
|
||||||
|
|
||||||
### INCA-G
|
|
||||||
|
|
||||||
> INCA-G = INCA Generator (is a token generating INCA typically over 48 months)
|
|
||||||
|
|
||||||
An INCA-G token generates INCA over a certain period. INCA stands for Internet Capacity token, enabling individuals to buy/sell Internet & Cloud Capacity.
|
|
||||||
|
|
||||||
We can analogize the generation of Cloud/Internet capacity to the generation of electricity. In this analogy, INCA is akin to the KWH token, while INCA-G is comparable to the KW token (representing capacity to generate electricity).
|
|
||||||
|
|
||||||
INCA-G tokens are unique and come with metadata specifying how INCA will be generated. This metadata outlines the generation schedule of INCA over the next X months.
|
|
||||||
|
|
||||||
!!wiki.include page:'projectinca:inca.md'
|
|
||||||
|
|
||||||
## How to Acquire the INCA-G Token?
|
|
||||||
|
|
||||||
### Round 1: SwissBorg & TF Cooperative
|
|
||||||
|
|
||||||
1 INCA-G token generates 15,000 INCA over 48 months.
|
|
||||||
|
|
||||||
1 INCA-G can be bought:
|
|
||||||
|
|
||||||
- From SwissBorg for 500 CHF
|
|
||||||
- Crypto-enabled bank in Switzerland
|
|
||||||
- Maximum sold is 5,000 INCA-G tokens
|
|
||||||
- with TFT which is the founder creator currency of the current grid
|
|
||||||
- There will never be more than 1 billion TFT
|
|
||||||
- 1 INCA-G token costs 10,000 TFT (\*)
|
|
||||||
|
|
||||||
> (\*) The pricing will depend on price of TFT at that moment.
|
|
||||||
|
|
||||||
### Round 2: **A**frica and Latin **A**merica INCA-G Tokens (AA)
|
|
||||||
|
|
||||||
1 INCA-G AA Token generates 10,000 INCA over 48 months.
|
|
||||||
|
|
||||||
AA stands for Africa and latin America
|
|
||||||
|
|
||||||
- From SwissBorg for *TBD* CHF.
|
|
||||||
|
|
||||||
The incoming funds will be used to generate Cloud & Internet capacity in these regions, <br>which are serious growth regions in the world.
|
|
||||||
|
|
||||||
|
|
||||||
## INCA Governance
|
|
||||||
|
|
||||||
A Wisdom Council approves budgets in line to tokenomics above.
|
|
||||||
|
|
||||||
The ThreeFold Wisdom Council will have 9 members in total. For any decision taken by the council, at least 6 must agree to go forward.
|
|
||||||
|
|
||||||
### Council Members
|
|
||||||
|
|
||||||
We start with 7 members and 2 more members will need to be added later on.
|
|
||||||
|
|
||||||
- 1 OurWorld (Kristof)
|
|
||||||
- 1 ThreeFold DMCC (Adnan)
|
|
||||||
- 1 TF9 (Jan)
|
|
||||||
- 1 Sikana (Greg)
|
|
||||||
- 1 CodeScalers (Nayer)
|
|
||||||
- 1 ThreeFold COOP (Sabrina)
|
|
||||||
- The COOP project is still ongoing and will still be created.
|
|
||||||
- 1 GreenEdge (MWW)
|
|
||||||
|
|
||||||
### Budget Allocation
|
|
||||||
|
|
||||||
- Budgets get allocated to projects on git.threefold.info
|
|
||||||
- Clear stories with clear budget allocations and cashflow tracking or time tracking
|
|
||||||
|
|
||||||
## TFT
|
|
||||||
|
|
||||||
The total supply of TFT is currently around 960 million TFT, while the max supply is 1 billion TFT.
|
|
||||||
|
|
||||||
## 3 Tokens: TFT, INCA & INCA-G
|
|
||||||
|
|
||||||
The 3 tokens co-exist within the TF ecosystem.
|
|
||||||
|
|
||||||
TFT has a max supply of 1 billion, INCA has a max supply of 4 billion. INCA-G generates INCA over a given period of time.
|
|
||||||
|
|
||||||
#### Implementation
|
|
||||||
|
|
||||||
- TFT is a token on Stellar blockchain (the original farming token)
|
|
||||||
- INCA is a token on Solana Blockchain (as digital currency for Internet Capacity)
|
|
||||||
- INCA-G Implemented as an NFT on the Solana Blockchain.
|
|
||||||
|
|
||||||
All can and will be bridged on multiple blockchains.
|
|
||||||
|
|
||||||
#### Metadata for INCA-G
|
|
||||||
|
|
||||||
Each INCA-G NFT contains information.
|
|
||||||
|
|
||||||
- Release date
|
|
||||||
- List of values
|
|
||||||
- Each value is the number of INCA tokens to be released monthly for a given period of time
|
|
||||||
@ -1,8 +1,8 @@
|
|||||||
|
|
||||||
|
|
||||||
# Project INCA
|
# ThreeFold Generic Info
|
||||||
|
|
||||||
In this section, we provide general information on the Project INCA.
|
In this section, we provide some general information on the ThreeFold Project.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|||||||
@ -1,4 +1,6 @@
|
|||||||
# TFConnect 3.14 Specs
|
# TFConnect Specs
|
||||||
|
|
||||||
|
> TODO:
|
||||||
|
|
||||||
A new version of TFConnect
|
A new version of TFConnect
|
||||||
|
|
||||||
@ -8,7 +10,7 @@ A new version of TFConnect
|
|||||||
- Sign T&C when starting
|
- Sign T&C when starting
|
||||||
|
|
||||||
|
|
||||||
# INCA APP 3.14 Specs
|
# INCA APP Specs
|
||||||
|
|
||||||
Name to be changed
|
Name to be changed
|
||||||
|
|
||||||
|
|||||||
BIN
collections/projectinca/tokenomics/img/release_table_tokens.png
Normal file
BIN
collections/projectinca/tokenomics/img/release_table_tokens.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 51 KiB |
BIN
collections/projectinca/tokenomics/img/token_release.png
Normal file
BIN
collections/projectinca/tokenomics/img/token_release.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 161 KiB |
BIN
collections/projectinca/tokenomics/img/token_release_stacked.png
Normal file
BIN
collections/projectinca/tokenomics/img/token_release_stacked.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 188 KiB |
89
collections/projectinca/tokenomics/tokens.md
Normal file
89
collections/projectinca/tokenomics/tokens.md
Normal file
@ -0,0 +1,89 @@
|
|||||||
|
|
||||||
|
# Tokenomics
|
||||||
|
|
||||||
|
```mermaid
|
||||||
|
flowchart TD
|
||||||
|
A[Cloud User] -->|CHF/EUR/...| B(CLOUD MARKET PLACE<br>Discount based on position<br>in TF Liquidity Pool.)
|
||||||
|
A[Cloud User] -->|CHF/EUR/...| B2((ThreeFold<br>Liquidity Pool))
|
||||||
|
B2 -->|TFT or INCA| B
|
||||||
|
B -->|TFT or INCA| C{Proof Of Utilization}
|
||||||
|
G[FARMING GRANTS<br>40m Tokens / Month]--> I{Proof Of Capacity<br>uptime, location, ...} --> D
|
||||||
|
C -->|80%| D[ThreeFold Farmers]
|
||||||
|
C -->|10%| E[ThreeFold Cooperative]
|
||||||
|
C -->|10%| F[Validators<br>Commercial Partners]
|
||||||
|
```
|
||||||
|
|
||||||
|
Farmers are rewarded by 80% of the fees as paid by the Cloud Users, the user pays in Fiat Currency. The marketplace automatically converts the FIAT currency to TFT and INCA as is needed to fullfil the request.
|
||||||
|
|
||||||
|
## Distribution
|
||||||
|
|
||||||
|
```echarts
|
||||||
|
option = {
|
||||||
|
title: {
|
||||||
|
text: 'Token',
|
||||||
|
subtext: 'Distribution',
|
||||||
|
left: 'center'
|
||||||
|
},
|
||||||
|
tooltip: {
|
||||||
|
trigger: 'item'
|
||||||
|
},
|
||||||
|
series: [
|
||||||
|
{
|
||||||
|
name: 'Distribution',
|
||||||
|
type: 'pie',
|
||||||
|
radius: '70%',
|
||||||
|
data: [
|
||||||
|
{ value: 725, name: 'Farmers & Tech ThreeFold Grid 1-3' },
|
||||||
|
{ value: 1475, name: 'Farmers ThreeFold Grid 4+' },
|
||||||
|
{ value: 300, name: 'Community Rewards + Promotion' },
|
||||||
|
{ value: 300, name: 'Grants' },
|
||||||
|
{ value: 200, name: 'Liquidity / Dex' },
|
||||||
|
{ value: 400, name: 'Investors' },
|
||||||
|
{ value: 100, name: 'ThreeFold Dubai Holdings' },
|
||||||
|
{ value: 500, name: 'Team' },
|
||||||
|
],
|
||||||
|
emphasis: {
|
||||||
|
itemStyle: {
|
||||||
|
shadowBlur: 10,
|
||||||
|
shadowOffsetX: 0,
|
||||||
|
shadowColor: 'rgba(0, 0, 0, 0.5)'
|
||||||
|
}
|
||||||
|
}
|
||||||
|
}
|
||||||
|
]
|
||||||
|
};
|
||||||
|
```
|
||||||
|
|
||||||
|
There can never be more than 4 Billion Tokens.
|
||||||
|
|
||||||
|
- 55% of supply for Farming and Tech
|
||||||
|
- People expanding the network with Router & Node capacity over the multiple releases
|
||||||
|
- 18.1%: Farmers & Tech ThreeFold Grid 1-3 (+95% minted, summer 2024)
|
||||||
|
- 36.9%: Farmers ThreeFold Grid 4+ (0% minted, summer 2024)
|
||||||
|
- 7.5% Community Expansion Rewards + Promotion
|
||||||
|
- Promotion of the TFGrid, Marketing Activities, ...
|
||||||
|
- 7.5% Community grants
|
||||||
|
- We want to expand and build our project in first place together with the community
|
||||||
|
- 5% for liquidity providing (DEX, marketmakers, ...)
|
||||||
|
- 2.5% ThreeFold Dubai holdings (held by the company who manages and promotes the grid)
|
||||||
|
- 10% For Investors
|
||||||
|
- 12.5% for team and contributor rewards
|
||||||
|
|
||||||
|
> Do note this table is still under deliberation and can change
|
||||||
|
|
||||||
|
|
||||||
|
## Release Schedule
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
- Investors release over 2 years, in equal tranches.
|
||||||
|
- Farmer rewards are released over 3 years.
|
||||||
|
- Ecosystem rewards over 4 years
|
||||||
|
|
||||||
|
This leads to following maximum unlocking table
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
The vesting accelerates if the token price gets above 0.5 USD, for each 0.1 USD above additional 10% unlocks into the INCA Liquidity pool.
|
||||||
|
Thanks to the liquidity pool the price remains stable even if people decide to chose the option to unvest faster.
|
||||||
|
|
||||||
Binary file not shown.
|
Before Width: | Height: | Size: 219 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 150 KiB |
@ -1,69 +0,0 @@
|
|||||||
|
|
||||||
## High Level Tokenomics INCA (Plan B)
|
|
||||||
|
|
||||||
> This is the plan if we don't find enough funding for Project INCA and need to grow organically.
|
|
||||||
|
|
||||||
There can never be more than 4 Billion INCA.
|
|
||||||
|
|
||||||
- 50% of supply for Farming
|
|
||||||
- People expanding the network with Router & Node capacity over the multiple releases
|
|
||||||
- 14% Million for community grants
|
|
||||||
- We want to expand and build our project in first place together with the community
|
|
||||||
- 1.5% Million for community expansion specifically for INCA
|
|
||||||
- Promotion of the TFGrid
|
|
||||||
- 5.5% for liquidity providing (DEX, marketmakers, ...)
|
|
||||||
- 11.5% originating from "Original Technology Acquisition"
|
|
||||||
- ThreeFold and INCA is the result of technology developed in a tech company, which got acquired many years ago, this resulted in a token grant for the stakeholders of that company
|
|
||||||
- 17.5% for team and contributor rewards
|
|
||||||
- It's for people who help to expand the Grid (starting now)
|
|
||||||
- A lot of it is to reward our partners to help launch the INCA Tokens & the TFGrid
|
|
||||||
|
|
||||||
|
|
||||||
```echarts
|
|
||||||
option = {
|
|
||||||
title: {
|
|
||||||
text: 'INCA Token',
|
|
||||||
subtext: 'Distribution',
|
|
||||||
left: 'center'
|
|
||||||
},
|
|
||||||
tooltip: {
|
|
||||||
trigger: 'item'
|
|
||||||
},
|
|
||||||
series: [
|
|
||||||
{
|
|
||||||
name: 'Distribution',
|
|
||||||
type: 'pie',
|
|
||||||
radius: '70%',
|
|
||||||
data: [
|
|
||||||
{ value: 2000, name: 'Farming Rewards' },
|
|
||||||
{ value: 229, name: 'Liquidity' },
|
|
||||||
{ value: 560, name: 'Community Grants' },
|
|
||||||
{ value: 460, name: 'Original Technology Acquisition' },
|
|
||||||
{ value: 60, name: 'Community Expansion' },
|
|
||||||
{ value: 700, name: 'Team' },
|
|
||||||
],
|
|
||||||
emphasis: {
|
|
||||||
itemStyle: {
|
|
||||||
shadowBlur: 10,
|
|
||||||
shadowOffsetX: 0,
|
|
||||||
shadowColor: 'rgba(0, 0, 0, 0.5)'
|
|
||||||
}
|
|
||||||
}
|
|
||||||
}
|
|
||||||
]
|
|
||||||
};
|
|
||||||
```
|
|
||||||
|
|
||||||
## Release Schedule
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
The following table shows planned release, some of the mechanisms and details are still being worked on.
|
|
||||||
|
|
||||||
*Accelerated Vesting means: if INCA gets above 0.5 USD per INCA (50%), the vesting accelerates in proportion to the percentage (e.g. 0.6 CHF per INCA = 60$ acceleration). At 1 CHF per INCA (100%) and more, the acceleration is 100%.*
|
|
||||||
|
|
||||||
|
|
||||||
For more information about our gen3 token see [here](tft.md).
|
|
||||||
|
|
||||||
|
|
||||||
<!-- https://docs.google.com/spreadsheets/d/1c1eR7oGcRdDkPnqOrERqLwY46V7PbVgKB8Vt-OUvj60/edit#gid=575798760 -->
|
|
||||||
@ -1,55 +0,0 @@
|
|||||||
## TFT Main Stats
|
|
||||||
|
|
||||||
TFT is the token on Stellar as was used on our previous grids (v 1,2,3).
|
|
||||||
|
|
||||||
- **The TFT is our Creator Token, it has established and proven the technology**
|
|
||||||
- Right now about 5 million TFT are farmed (mined) per month
|
|
||||||
- About 294,000,000 TFT have been farmed so far
|
|
||||||
- Farming of TFT will stop at 1 Billion TFT
|
|
||||||
|
|
||||||
|
|
||||||
```echarts
|
|
||||||
option = {
|
|
||||||
title: {
|
|
||||||
text: 'TFT Token Version 3.x',
|
|
||||||
subtext: 'Distribution',
|
|
||||||
left: 'center'
|
|
||||||
},
|
|
||||||
tooltip: {
|
|
||||||
trigger: 'item'
|
|
||||||
},
|
|
||||||
series: [
|
|
||||||
{
|
|
||||||
name: 'Distribution',
|
|
||||||
type: 'pie',
|
|
||||||
radius: '70%',
|
|
||||||
data: [
|
|
||||||
{ value: 700, name: 'Farming Done' },
|
|
||||||
{ value: 80, name: 'Liquidity' },
|
|
||||||
{ value: 360, name: 'Grants' },
|
|
||||||
{ value: 460, name: 'Technology Acquisition' },
|
|
||||||
{ value: 400, name: 'Advisors, Founders & Team' },
|
|
||||||
],
|
|
||||||
emphasis: {
|
|
||||||
itemStyle: {
|
|
||||||
shadowBlur: 10,
|
|
||||||
shadowOffsetX: 0,
|
|
||||||
shadowColor: 'rgba(0, 0, 0, 0.5)'
|
|
||||||
}
|
|
||||||
}
|
|
||||||
}
|
|
||||||
]
|
|
||||||
};
|
|
||||||
```
|
|
||||||
|
|
||||||
- Rivine-minted TFT: 112,862,249
|
|
||||||
- Stellar-minted TFT: 181,262,054
|
|
||||||
|
|
||||||
### On v3.x of our Grid TFT Farming is limited to 1 Billion
|
|
||||||
|
|
||||||
- Farming on TFGrid (our v3 release) stops at 1 Billion.
|
|
||||||
- Farming continues (over v4 release) total will be 50% of the total supply (1,2,3 and 4 release)
|
|
||||||
|
|
||||||
*The values above are estimate in some cases as we don't have full visibility and details for all wallets, but of course the totals are correct.*
|
|
||||||
|
|
||||||
For the Grants, see [the Grants Document](grants.md).
|
|
||||||
@ -1,50 +0,0 @@
|
|||||||
# Tokens Distribution (Plan B)
|
|
||||||
|
|
||||||
> This is the plan if we don't find enough funding for Project INCA and need to grow organically.
|
|
||||||
|
|
||||||
The INCA token is the result of our 4 generations of product releases.
|
|
||||||
|
|
||||||
- v 1,2,3 goes under the name of TFT and was minted on Stellar (max 2 Billion)
|
|
||||||
- INCA supercedes and integrates TFT, and is our v4 Token on Solana
|
|
||||||
- INCA will be on many DEXes
|
|
||||||
- The INCA will be bridged to other major blockchains and we aim to have INCA available on Exchanges.
|
|
||||||
|
|
||||||
We are a community driven project and that shows in our tokenomics, over the both generations:
|
|
||||||
|
|
||||||
- +70% of all tokens over both generation net's is for the community (farming, grants, liquidity providing ...)
|
|
||||||
- 11.5% was for the original technology acquisition
|
|
||||||
- 17.5% is for the team and contributors
|
|
||||||
|
|
||||||
```echarts
|
|
||||||
option = {
|
|
||||||
title: {
|
|
||||||
text: 'INCA Token',
|
|
||||||
subtext: 'Distribution',
|
|
||||||
left: 'center'
|
|
||||||
},
|
|
||||||
tooltip: {
|
|
||||||
trigger: 'item'
|
|
||||||
},
|
|
||||||
series: [
|
|
||||||
{
|
|
||||||
name: 'Distribution',
|
|
||||||
type: 'pie',
|
|
||||||
radius: '70%',
|
|
||||||
data: [
|
|
||||||
{ value: 2710, name: 'Community Rewards: Farming + grants' },
|
|
||||||
{ value: 130, name: 'Liquidity' },
|
|
||||||
{ value: 460, name: 'Original Technology Acquisition' },
|
|
||||||
{ value: 700, name: 'Team' },
|
|
||||||
],
|
|
||||||
emphasis: {
|
|
||||||
itemStyle: {
|
|
||||||
shadowBlur: 10,
|
|
||||||
shadowOffsetX: 0,
|
|
||||||
shadowColor: 'rgba(0, 0, 0, 0.5)'
|
|
||||||
}
|
|
||||||
}
|
|
||||||
}
|
|
||||||
]
|
|
||||||
};
|
|
||||||
```
|
|
||||||
|
|
||||||
@ -1,67 +0,0 @@
|
|||||||
|
|
||||||
## High Level Tokenomics INCA
|
|
||||||
|
|
||||||
There can never be more than 4 Billion INCA.
|
|
||||||
|
|
||||||
- 50% of supply for Farming
|
|
||||||
- People expanding the network with Router & Node capacity over the multiple releases
|
|
||||||
- 14% Million for community grants
|
|
||||||
- We want to expand and build our project in first place together with the community
|
|
||||||
- 1.5% Million for community expansion specifically for INCA
|
|
||||||
- Promotion of the TFGrid
|
|
||||||
- 5.5% for liquidity providing (DEX, marketmakers, ...)
|
|
||||||
- 11.5% originating from "Original Technology Acquisition"
|
|
||||||
- ThreeFold and INCA is the result of technology developed in a tech company, which got acquired many years ago, this resulted in a token grant for the stakeholders of that company
|
|
||||||
- 17.5% for team and contributor rewards
|
|
||||||
- It's for people who help to expand the Grid (starting now)
|
|
||||||
- A lot of it is to reward our partners to help launch the INCA Tokens & the TFGrid
|
|
||||||
|
|
||||||
|
|
||||||
```echarts
|
|
||||||
option = {
|
|
||||||
title: {
|
|
||||||
text: 'INCA Token',
|
|
||||||
subtext: 'Distribution',
|
|
||||||
left: 'center'
|
|
||||||
},
|
|
||||||
tooltip: {
|
|
||||||
trigger: 'item'
|
|
||||||
},
|
|
||||||
series: [
|
|
||||||
{
|
|
||||||
name: 'Distribution',
|
|
||||||
type: 'pie',
|
|
||||||
radius: '70%',
|
|
||||||
data: [
|
|
||||||
{ value: 2000, name: 'Farming Rewards' },
|
|
||||||
{ value: 229, name: 'Liquidity' },
|
|
||||||
{ value: 560, name: 'Community Grants' },
|
|
||||||
{ value: 460, name: 'Original Technology Acquisition' },
|
|
||||||
{ value: 60, name: 'Community Expansion' },
|
|
||||||
{ value: 700, name: 'Team' },
|
|
||||||
],
|
|
||||||
emphasis: {
|
|
||||||
itemStyle: {
|
|
||||||
shadowBlur: 10,
|
|
||||||
shadowOffsetX: 0,
|
|
||||||
shadowColor: 'rgba(0, 0, 0, 0.5)'
|
|
||||||
}
|
|
||||||
}
|
|
||||||
}
|
|
||||||
]
|
|
||||||
};
|
|
||||||
```
|
|
||||||
|
|
||||||
## Release Schedule
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
The following table shows planned release, some of the mechanisms and details are still being worked on.
|
|
||||||
|
|
||||||
*Accelerated Vesting means: if INCA gets above 0.5 USD per INCA (50%), the vesting accelerates in proportion to the percentage (e.g. 0.6 CHF per INCA = 60$ acceleration). At 1 CHF per INCA (100%) and more, the acceleration is 100%.*
|
|
||||||
|
|
||||||
|
|
||||||
For more information about our gen3 token see [here](tft.md).
|
|
||||||
|
|
||||||
|
|
||||||
<!-- https://docs.google.com/spreadsheets/d/1c1eR7oGcRdDkPnqOrERqLwY46V7PbVgKB8Vt-OUvj60/edit#gid=575798760 -->
|
|
||||||
@ -1,55 +0,0 @@
|
|||||||
## TFT Main Stats
|
|
||||||
|
|
||||||
TFT is the token on Stellar as was used on our previous grids (v 1,2,3).
|
|
||||||
|
|
||||||
- **The TFT is our Creator Token, it has established and proven the technology**
|
|
||||||
|
|
||||||
- Right now about 5 million TFT are farmed (mined) per month
|
|
||||||
- Farming of TFT will stop at 1 Billion TFT
|
|
||||||
|
|
||||||
|
|
||||||
```echarts
|
|
||||||
option = {
|
|
||||||
title: {
|
|
||||||
text: 'TFT Token Version 3.x',
|
|
||||||
subtext: 'Distribution',
|
|
||||||
left: 'center'
|
|
||||||
},
|
|
||||||
tooltip: {
|
|
||||||
trigger: 'item'
|
|
||||||
},
|
|
||||||
series: [
|
|
||||||
{
|
|
||||||
name: 'Distribution',
|
|
||||||
type: 'pie',
|
|
||||||
radius: '70%',
|
|
||||||
data: [
|
|
||||||
{ value: 700, name: 'Farming Done' },
|
|
||||||
{ value: 80, name: 'Liquidity' },
|
|
||||||
{ value: 360, name: 'Grants' },
|
|
||||||
{ value: 460, name: 'Technology Acquisition' },
|
|
||||||
{ value: 400, name: 'Advisors, Founders & Team' },
|
|
||||||
],
|
|
||||||
emphasis: {
|
|
||||||
itemStyle: {
|
|
||||||
shadowBlur: 10,
|
|
||||||
shadowOffsetX: 0,
|
|
||||||
shadowColor: 'rgba(0, 0, 0, 0.5)'
|
|
||||||
}
|
|
||||||
}
|
|
||||||
}
|
|
||||||
]
|
|
||||||
};
|
|
||||||
```
|
|
||||||
|
|
||||||
- Rivine-minted TFT: 112,862,249
|
|
||||||
- Stellar-minted TFT: 181,262,054
|
|
||||||
|
|
||||||
### On v3.x of our Grid TFT Farming is limited to 1 Billion
|
|
||||||
|
|
||||||
- Farming on TFGrid (our v3 release) stops at 1 Billion.
|
|
||||||
- Farming continues (over v4 release) total will be 50% of the total supply (1,2,3 and 4 release)
|
|
||||||
|
|
||||||
*The values above are estimate in some cases as we don't have full visibility and details for all wallets, but of course the totals are correct.*
|
|
||||||
|
|
||||||
For the Grants, see [the Grants Document](grants.md).
|
|
||||||
@ -1,48 +0,0 @@
|
|||||||
# INCA Tokens Distribution
|
|
||||||
|
|
||||||
> Not ready yet, we are defining how to do this best.
|
|
||||||
|
|
||||||
The INCA token is the result of our 4 generations of product releases.
|
|
||||||
|
|
||||||
- INCA will be on many DEXes
|
|
||||||
- The INCA will be bridged to other major blockchains and we aim to have INCA available on Exchanges.
|
|
||||||
|
|
||||||
We are a community driven project and that shows in our tokenomics, over the both generations:
|
|
||||||
|
|
||||||
- +70% of all tokens over both generation net's is for the community (farming, grants, liquidity providing ...)
|
|
||||||
- 11.5% was for the original technology acquisition
|
|
||||||
- 17.5% is for the team and contributors
|
|
||||||
|
|
||||||
```echarts
|
|
||||||
option = {
|
|
||||||
title: {
|
|
||||||
text: 'INCA Token',
|
|
||||||
subtext: 'Distribution',
|
|
||||||
left: 'center'
|
|
||||||
},
|
|
||||||
tooltip: {
|
|
||||||
trigger: 'item'
|
|
||||||
},
|
|
||||||
series: [
|
|
||||||
{
|
|
||||||
name: 'Distribution',
|
|
||||||
type: 'pie',
|
|
||||||
radius: '70%',
|
|
||||||
data: [
|
|
||||||
{ value: 2710, name: 'Community Rewards: Farming + grants' },
|
|
||||||
{ value: 130, name: 'Liquidity' },
|
|
||||||
{ value: 460, name: 'Original Technology Acquisition' },
|
|
||||||
{ value: 700, name: 'Team' },
|
|
||||||
],
|
|
||||||
emphasis: {
|
|
||||||
itemStyle: {
|
|
||||||
shadowBlur: 10,
|
|
||||||
shadowOffsetX: 0,
|
|
||||||
shadowColor: 'rgba(0, 0, 0, 0.5)'
|
|
||||||
}
|
|
||||||
}
|
|
||||||
}
|
|
||||||
]
|
|
||||||
};
|
|
||||||
```
|
|
||||||
|
|
||||||
@ -1,51 +1,14 @@
|
|||||||
|
|
||||||
|
|
||||||
|
|
||||||
## Architecture
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
The system has been designed to be scalable to a planet level.
|
|
||||||
|
|
||||||
- Mycelium is the Network Layer
|
|
||||||
- 3Nodes are the nodes running Zero-OS which is our own operating System providing compute, storage and network capacity
|
|
||||||
|
|
||||||
### 3Nodes
|
|
||||||
|
|
||||||
The network of nodes which make up the cloud. Each node provides compute, storage and network capacity.
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
A cloud needs hardware/servers to function. Servers of all shapes and sizes can be added. The production of Cloud Capacity is called Farming and parties who add these servers to the grid are called Farmers.
|
|
||||||
|
|
||||||
Farmers download the Zero-OS operating system and boot their servers. Once booted, these servers become 3Nodes. The 3Nodes will register themselves in a blockchain. Once registered, the capacity of the 3Nodes will become available. This enables a peer2peer environment for people or companies to reserve their Internet Capacity directly from the hardware but yet allowing full control by commercial parties if that would be required.
|
|
||||||
|
|
||||||
|
|
||||||
## Ultra Scalable
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
This architecture scales to the planet.
|
|
||||||
|
|
||||||
## Core Components
|
## Base Layer for Many Usecases
|
||||||
|
|
||||||
!!wiki.include page:components_links.md
|
|
||||||
|
|
||||||
### Web3 & Decentralized AI Compatibility
|
|
||||||
|
|
||||||
Our Decentralized Cloud Technology the ideal platform for hosting any web3 and AI workloads.
|
Our Decentralized Cloud Technology the ideal platform for hosting any web3 and AI workloads.
|
||||||
|
|
||||||
Our Zero-OS operating system already supports integrated GPUs, ensuring optimal performance for decentralized AI applications.
|
Our Zero-OS operating system also supports integrated GPUs, ensuring optimal performance for decentralized AI applications.
|
||||||
|
|
||||||
> Any workload (web2/3 and AI) can run on on our Decentralized Cloud.
|
> Any workload (web2/3 and AI) can run on on our Decentralized Cloud.
|
||||||
|
|
||||||
## TFChain: our Blockchain
|
|
||||||
|
|
||||||
This blockchain does the following:
|
|
||||||
|
|
||||||
- registry for all 3bots (identity system, aka phonebook)
|
|
||||||
- registry for all farmers & 3nodes
|
|
||||||
- registry for our reputation system
|
|
||||||
- info as required for the Smart Contract for IT
|
|
||||||
|
|
||||||
This is the hart of our operational system of our decentralized cloud.
|
|
||||||
|
|||||||
BIN
collections/tech/architecture/cloud_engine.jpg
Normal file
BIN
collections/tech/architecture/cloud_engine.jpg
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 146 KiB |
20
collections/tech/architecture/cloudengine.md
Normal file
20
collections/tech/architecture/cloudengine.md
Normal file
@ -0,0 +1,20 @@
|
|||||||
|
|
||||||
|
|
||||||
|
# Architecture Cloud Engine
|
||||||
|
|
||||||
|
The 3 Nodes form the base layer, providing compute, storage, and network capabilities.
|
||||||
|
|
||||||
|
The quantum safe network enables all IT workloads to communicate with one another using the most efficient route and the strongest security measures.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
The Storage layer make sure we all have perfect control over our storage and can never loose our information.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
## Autonomous Deployments
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
The hero's can deploy and manage IT workloads on our behalf.
|
||||||
|
|
||||||
27
collections/tech/architecture/hero_virtual_admin.md
Normal file
27
collections/tech/architecture/hero_virtual_admin.md
Normal file
@ -0,0 +1,27 @@
|
|||||||
|
|
||||||
|
|
||||||
|
# Hero as Virtual System Administrator and more
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
Every individual has a personal Hero—a virtual assistant that manages your digital life and serves as your system administrator for AI or Edge Cloud workloads.
|
||||||
|
|
||||||
|
These Heroes communicate with each other over the private Mycelium network, which offers a secure message bus for scalable and secure communication.
|
||||||
|
|
||||||
|
A Hero can store an unlimited amount of information, and only your Hero has access to this data, deciding how and when it can be shared with other Heroes or AI systems.
|
||||||
|
|
||||||
|
Active 24/7, your Hero continuously monitors your IT infrastructure. If something goes wrong, the Hero will automatically resolve the issue, ensuring smooth and uninterrupted service.
|
||||||
|
|
||||||
|
|
||||||
|
### Natural Evolution
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
We believe this represents the natural evolution away from reliance on centralized services.
|
||||||
|
|
||||||
|
With millions of Heroes working together, can form a collective global intelligence, leveraging various tools to interact with existing services on behalf of their users within all safety of our own sovereignity.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -2,3 +2,6 @@ architecture.png
|
|||||||
3node.png
|
3node.png
|
||||||
architecture_scalable.png
|
architecture_scalable.png
|
||||||
autonous3bots.png
|
autonous3bots.png
|
||||||
|
3bot_virtualsysadmin.png
|
||||||
|
autonomous_workloads.png
|
||||||
|
cloudengine_architecture.png
|
||||||
|
|||||||
BIN
collections/tech/architecture/img/3bot_hero.png
Normal file
BIN
collections/tech/architecture/img/3bot_hero.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 344 KiB |
BIN
collections/tech/architecture/img/3bot_virtualsysadmin.png
Normal file
BIN
collections/tech/architecture/img/3bot_virtualsysadmin.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 347 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 804 KiB After Width: | Height: | Size: 590 KiB |
BIN
collections/tech/architecture/img/autonomous_workloads.png
Normal file
BIN
collections/tech/architecture/img/autonomous_workloads.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 207 KiB |
BIN
collections/tech/architecture/img/cloudengine_architecture.png
Normal file
BIN
collections/tech/architecture/img/cloudengine_architecture.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 196 KiB |
BIN
collections/tech/architecture/img/hero_archit.png
Normal file
BIN
collections/tech/architecture/img/hero_archit.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 458 KiB |
BIN
collections/tech/architecture/img/usecases_tfgrid.png
Normal file
BIN
collections/tech/architecture/img/usecases_tfgrid.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 330 KiB |
55
collections/tech/architecture/internet_arch.md
Normal file
55
collections/tech/architecture/internet_arch.md
Normal file
@ -0,0 +1,55 @@
|
|||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
# Architecture for an Upgraded Internet
|
||||||
|
|
||||||
|
!!wiki.include page:'internet_archtecture0.md'
|
||||||
|
|
||||||
|
#### 3Nodes
|
||||||
|
|
||||||
|
Each 3node provides compute, storage and network capacity, its the core capacity layer of the cloud.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
A cloud needs hardware/servers to function. Servers of all shapes and sizes can be added. The production of Cloud Capacity is called Farming and parties who add these servers to the grid are called Farmers.
|
||||||
|
|
||||||
|
Farmers download the Zero-OS operating system and boot their servers. Once booted, these servers become 3Nodes. The 3Nodes will register themselves in a blockchain. Once registered, the capacity of the 3Nodes will become available. This enables a peer2peer environment for people or companies to reserve their Internet Capacity directly from the hardware but yet allowing full control by commercial parties if that would be required.
|
||||||
|
|
||||||
|
Each 3Node is running our Zero-OS operating system.
|
||||||
|
|
||||||
|
#### Mycelium Routers
|
||||||
|
|
||||||
|
Mycelium is an end-to-end encrypted overlay meshed wireless network with agents available for any desktop and mobile operating system.
|
||||||
|
|
||||||
|
We have also created a dedicated Mycelium Router. Mycelium Routers seamlessly integrate with our Mycelium network technology, efficiently selecting the shortest path between all participants.
|
||||||
|
|
||||||
|
These Mycelium Routers are compatible not only with Satelite, Wi-Fi but also with 4G and 5G networks, ensuring versatile connectivity options.
|
||||||
|
|
||||||
|
The Mycelium Routers can be installed in locations with substantial network capacity, allowing everyone to bridge between the current Internet and the overlay Mycelium network.
|
||||||
|
|
||||||
|
#### Web Gateways
|
||||||
|
|
||||||
|
The Web Gateway serves as a mechanism to connect the private (overlay) networks (Mycelium) to the open Internet.
|
||||||
|
|
||||||
|
By not providing an open and direct path into the private network, many malicious phishing and hacking attempts are stopped at the Web Gateway level for container applications.
|
||||||
|
|
||||||
|
The Web Gateways provide HTTP(S) and, in the future, other web services, which get forwarded to the relevant service exposing itself over Mycelium. This setup offers multiple access points to various backend services.
|
||||||
|
|
||||||
|
|
||||||
|
##### TFChain: our Blockchain
|
||||||
|
|
||||||
|
This blockchain does the following:
|
||||||
|
|
||||||
|
- registry for all 3bots (identity system, aka phonebook)
|
||||||
|
- registry for all farmers & 3nodes
|
||||||
|
- registry for our reputation system
|
||||||
|
- info as required for the Smart Contract for IT
|
||||||
|
|
||||||
|
This is the hart of our operational system of our decentralized cloud.
|
||||||
|
|
||||||
|
|
||||||
|
## Ultra Scalable
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
This architecture scales to the planet.
|
||||||
9
collections/tech/architecture/internet_archtecture0.md
Normal file
9
collections/tech/architecture/internet_archtecture0.md
Normal file
@ -0,0 +1,9 @@
|
|||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
- **3Nodes**: Deliver compute, storage, and GPU capacity.
|
||||||
|
- **Mycelium Routers**: Allow all Mycelium Network participants to communicate with each other and also connect over existing Internet links. Mycelium Routers provide bandwidth to our ecosystem.
|
||||||
|
- **WebGateways**: Provide a bridge between the current Internet and the Mycelium Network.
|
||||||
|
- **Hero 3Bots**: Represent our digital lives and possess the knowledge to act as virtual system administrators, ensuring our IT workloads remain operational.
|
||||||
|
- **Users**: Arrange their digital lives through their Hero 3Bots.
|
||||||
|
- **AI Clouds**: Are created by connecting GPUs from the 3Nodes over the Mycelium Network.
|
||||||
@ -1,14 +1,3 @@
|
|||||||
|
|
||||||
|
|
||||||
|
|
||||||
### Mycelium Routers
|
|
||||||
|
|
||||||
Thanks to Mycelium Routers anyone can now operate as a network service provider.
|
|
||||||
|
|
||||||
Mycelium Routers seamlessly integrate with our Mycelium network technology, efficiently selecting the shortest path between all participants.
|
|
||||||
|
|
||||||
These Mycelium Routers are not only compatible with Wi-Fi but also with 4G and 5G networks, ensuring versatile connectivity options.
|
|
||||||
|
|
||||||
### Web Gateways
|
|
||||||
|
|
||||||
The Web Gateway is a mechanism to connect the private (overlay) networks (Mycelium) to the open Internet. By not providing an open and direct path in to the private network, a lot of malicious phishing and hacking attempts are stopped at the Web Gateway level for container applications.
|
|
||||||
|
|||||||
BIN
collections/tech/architecture/virtual_sysadmin.jpg
Normal file
BIN
collections/tech/architecture/virtual_sysadmin.jpg
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 121 KiB |
@ -7,7 +7,7 @@ While Zero-Stor addresses numerous storage challenges effectively, it may not be
|
|||||||
|
|
||||||
### Introducing QSFS
|
### Introducing QSFS
|
||||||
|
|
||||||
A FUSE-based filesystem utilizing Zero-Stor as its backend. Metadata is safeguarded to prevent loss, inheriting Zero-Stor's benefits and simplifying usage for developers and system administrators.
|
A filesystem utilizing Zero-Stor as its backend. Metadata is safeguarded to prevent loss, inheriting Zero-Stor's benefits and simplifying usage for developers and system administrators.
|
||||||
|
|
||||||
The filesystem is always deployed in one location, data is distributed (using zero-stor) across multiple sites for unparalleled reliability.
|
The filesystem is always deployed in one location, data is distributed (using zero-stor) across multiple sites for unparalleled reliability.
|
||||||
|
|
||||||
|
|||||||
@ -3,10 +3,8 @@
|
|||||||
# Storage
|
# Storage
|
||||||
|
|
||||||
|
|
||||||
| | ThreeFold Network Layer | Overlay Storage Systems / Networks |
|
| | ThreeFold Storage Layer | Overlay Storage Systems |
|
||||||
|-----------------------------|------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------|
|
|-----------------------------|------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------|
|
||||||
| Management | Full P2P, done by 3bot Agents, blockchain IT contract | Centralized leading to security issues |
|
|
||||||
| Locality | Data can be local and sovereign, full control by the the user (data creator) | Based on centralized control mechanisms or inefficient algorithms that route traffic indiscriminately across the globe. |
|
|
||||||
| Quantum Safe | Yes, novel encoding system (not encryption based) makes impossible to hack data. | No |
|
| Quantum Safe | Yes, novel encoding system (not encryption based) makes impossible to hack data. | No |
|
||||||
| Post Quantum | Possible (ask us) | No |
|
| Post Quantum | Possible (ask us) | No |
|
||||||
| Scalability | Yes, this system exists +10 years, is being used by large orgs for zetabytes. | Some systems, most not, but centralized. |
|
| Scalability | Yes, this system exists +10 years, is being used by large orgs for zetabytes. | Some systems, most not, but centralized. |
|
||||||
@ -15,3 +13,5 @@
|
|||||||
| Performance | Is not a super fast system but good for most cases, +- 100 MB / sec per content creator. | Variable, hard to say, some are |
|
| Performance | Is not a super fast system but good for most cases, +- 100 MB / sec per content creator. | Variable, hard to say, some are |
|
||||||
| Efficiency for redundancy | Ultra efficient, only 20% overhead to allow 4 locations to go down | NO, sometimes +5 copies = 500% |
|
| Efficiency for redundancy | Ultra efficient, only 20% overhead to allow 4 locations to go down | NO, sometimes +5 copies = 500% |
|
||||||
| Fully integrated in compute | Yes | Lots of different solutions |
|
| Fully integrated in compute | Yes | Lots of different solutions |
|
||||||
|
| Management | Full P2P, done by 3bot Agents, blockchain IT contract | Centralized leading to security issues |
|
||||||
|
| Locality | Data can be local and sovereign, full control by the the user (data creator) | Based on centralized control mechanisms or inefficient algorithms that route traffic indiscriminately across the globe. |
|
||||||
|
|||||||
11
collections/tech/natural_progression/cloud_reinvented.md
Normal file
11
collections/tech/natural_progression/cloud_reinvented.md
Normal file
@ -0,0 +1,11 @@
|
|||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
# Cloud Re-Invented
|
||||||
|
|
||||||
|
## Requirements for a New Cloud Engine
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
!!wiki.include page:'cloud_requirements.md'
|
||||||
|
|
||||||
@ -1,8 +1,5 @@
|
|||||||
|
|
||||||
|
|
||||||
## Requirements For A New Genertion of Cloud Technology
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
- Compute, Storage, Network need to be
|
- Compute, Storage, Network need to be
|
||||||
- Local
|
- Local
|
||||||
|
|||||||
@ -1,2 +1,3 @@
|
|||||||
evolution.png
|
evolution.png
|
||||||
natural_progression_3bot.png
|
natural_progression_3bot.png
|
||||||
|
re_invented.png
|
||||||
|
|||||||
Binary file not shown.
|
Before Width: | Height: | Size: 375 KiB |
BIN
collections/tech/natural_progression/img/re_invented.png
Normal file
BIN
collections/tech/natural_progression/img/re_invented.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 1.0 MiB |
@ -1,6 +1,3 @@
|
|||||||
|
|
||||||
|
|
||||||
We need a new cloud engine which supports the evolution of the Internet
|
|
||||||
|
|
||||||
# The Internet’s Natural Progression
|
# The Internet’s Natural Progression
|
||||||
|
|
||||||
@ -12,8 +9,6 @@ As large companies became profit and data centric, centralization quickly became
|
|||||||
|
|
||||||
## Requirements For A New Internet
|
## Requirements For A New Internet
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
- Compute, Storage, Network need to be
|
- Compute, Storage, Network need to be
|
||||||
- Local
|
- Local
|
||||||
- Sovereign
|
- Sovereign
|
||||||
@ -21,7 +16,6 @@ As large companies became profit and data centric, centralization quickly became
|
|||||||
- More Secure
|
- More Secure
|
||||||
- Storage needs to be
|
- Storage needs to be
|
||||||
- More reliable with less overhead
|
- More reliable with less overhead
|
||||||
- Our technology has only 20% overhead needed
|
|
||||||
- Capable to be global and be used as Content Delivery Network (CDN)
|
- Capable to be global and be used as Content Delivery Network (CDN)
|
||||||
- Fast enough for the use case at hand
|
- Fast enough for the use case at hand
|
||||||
- Network needs to be
|
- Network needs to be
|
||||||
@ -30,6 +24,17 @@ As large companies became profit and data centric, centralization quickly became
|
|||||||
- End2End Encrypted
|
- End2End Encrypted
|
||||||
- Capable to really know where information goes to or comes from (authenticity)
|
- Capable to really know where information goes to or comes from (authenticity)
|
||||||
|
|
||||||
|
## Internet/Cloud Architecture
|
||||||
|
|
||||||
|
!!wiki.include page:'internet_archtecture0.md'
|
||||||
|
|
||||||
|
## Base Layer for a New Cloud / Internet
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
We need a new cloud engine which supports the evolution of the Internet
|
||||||
|
|
||||||
|
|
||||||
## Natural Progression
|
## Natural Progression
|
||||||
|
|
||||||
|
|
||||||
@ -40,6 +45,7 @@ The technical backbone enabling the Hero is a component known as the 3Bot. This
|
|||||||
|
|
||||||
Communication between 3Bots is optimized to use the shortest possible paths, ensuring that all interactions are end-to-end encrypted for maximum security and privacy.
|
Communication between 3Bots is optimized to use the shortest possible paths, ensuring that all interactions are end-to-end encrypted for maximum security and privacy.
|
||||||
|
|
||||||
|
|
||||||
## 3Bot Architecture
|
## 3Bot Architecture
|
||||||
|
|
||||||
|
|
||||||
3
collections/tech/natural_progression/re_invented.md
Normal file
3
collections/tech/natural_progression/re_invented.md
Normal file
@ -0,0 +1,3 @@
|
|||||||
|
|
||||||
|
|
||||||
|
# Re-Invented
|
||||||
25
collections/tech/presentation.md
Normal file
25
collections/tech/presentation.md
Normal file
@ -0,0 +1,25 @@
|
|||||||
|
|
||||||
|
# ThreeFold Project Presentation
|
||||||
|
|
||||||
|
<div style="position: relative; width: 100%; height: 0; padding-top: 56.2500%;
|
||||||
|
padding-bottom: 0; box-shadow: 0 2px 8px 0 rgba(63,69,81,0.16); margin-top: 1.6em; margin-bottom: 0.9em; overflow: hidden;
|
||||||
|
border-radius: 8px; will-change: transform;">
|
||||||
|
<iframe loading="lazy" style="position: absolute; width: 100%; height: 100%; top: 0; left: 0; border: none; padding: 0;margin: 0;"
|
||||||
|
src="https://www.canva.com/design/DAGMnf6wIcE/vNv1-MAAhH_BgBch4wEkjQ/view?embed" allowfullscreen="allowfullscreen" allow="fullscreen">
|
||||||
|
</iframe>
|
||||||
|
</div>
|
||||||
|
<a href="https://www.canva.com/design/DAGMnf6wIcE/vNv1-MAAhH_BgBch4wEkjQ/view?utm_content=DAGMnf6wIcE&utm_campaign=designshare&utm_medium=embeds&utm_source=link" target="_blank" rel="noopener">THREEFOLD, PROJECT INCA (public)</a> by Kristof De Spiegeleer
|
||||||
|
|
||||||
|
|
||||||
|
# ThreeFold Tech Presentation
|
||||||
|
|
||||||
|
<div style="position: relative; width: 100%; height: 0; padding-top: 56.2500%;
|
||||||
|
padding-bottom: 0; box-shadow: 0 2px 8px 0 rgba(63,69,81,0.16); margin-top: 1.6em; margin-bottom: 0.9em; overflow: hidden;
|
||||||
|
border-radius: 8px; will-change: transform;">
|
||||||
|
<iframe loading="lazy" style="position: absolute; width: 100%; height: 100%; top: 0; left: 0; border: none; padding: 0;margin: 0;"
|
||||||
|
src="https://www.canva.com/design/DAGMk0XzQsg/IAtqvFxW-SbD8E7hK-hpow/view?embed" allowfullscreen="allowfullscreen" allow="fullscreen">
|
||||||
|
</iframe>
|
||||||
|
</div>
|
||||||
|
<a href="https://www.canva.com/design/DAGMk0XzQsg/IAtqvFxW-SbD8E7hK-hpow/view?utm_content=DAGMk0XzQsg&utm_campaign=designshare&utm_medium=embeds&utm_source=link" target="_blank" rel="noopener">ThreeFold Technology v3.7 July 2024.pptx</a> by Kristof De Spiegeleer
|
||||||
|
|
||||||
|
|
||||||
47
collections/tech/roadmap/enterprise_roadmap.md
Normal file
47
collections/tech/roadmap/enterprise_roadmap.md
Normal file
@ -0,0 +1,47 @@
|
|||||||
|
# Government, Commercial hosters, Telco and Enterprise Roadmap
|
||||||
|
|
||||||
|
We are working on our Government, Commercial hosters, Telco and Enterprise Release of our Technology.
|
||||||
|
|
||||||
|
> 90% of the work has been done as part of our base offering but we need additional features for enterprise
|
||||||
|
|
||||||
|
## Enterprise User Interface
|
||||||
|
|
||||||
|
The current user interface is designed for an open-source tech audience. For enterprise use, we need a different approach to meet the unique needs of enterprise environments:
|
||||||
|
|
||||||
|
- **Private or Hybrid Context**: All operations should be conducted within a private or hybrid cloud context to ensure security and compliance.
|
||||||
|
- **Enhanced Monitoring**: We need more comprehensive monitoring dashboard screens to provide real-time insights and analytics.
|
||||||
|
- **Identity Management Integration**: Integration with enterprise-grade Identity Management solutions, such as LDAP, Active Directory, and SSO (Single Sign-On), is essential.
|
||||||
|
- **Enterprise-Friendly UI**: The user interface needs to be redesigned to be more intuitive and tailored to enterprise users, focusing on usability and efficiency.
|
||||||
|
- **Token Irrelevance**: Tokens are not a priority in this context and should be de-emphasized in the solution.
|
||||||
|
|
||||||
|
## Windows Support
|
||||||
|
|
||||||
|
The virtual Machine technology we use does support windows, but we need to do some further integration.
|
||||||
|
|
||||||
|
## High Performance Network Integration
|
||||||
|
|
||||||
|
- **Local Network Integration**: Zero-OS is designed to support a wide range of technologies, though additional integration work is required to optimize performance.
|
||||||
|
- **High-Speed Backbones**: We aim to support high-speed Ethernet and RDMA (Infiniband) based backbones.
|
||||||
|
- **Instrumentation Enhancements**: Additional instrumentation needs to be incorporated into Zero-OS to achieve optimal performance.
|
||||||
|
- **Target Performance**: Our goal is to achieve network speeds exceeding 100 Gbps.
|
||||||
|
- **Custom Integration**: We offer integration with selected network equipment from our customers, accommodating custom integration requirements.
|
||||||
|
|
||||||
|
## High Performance Storage Block Device Integration
|
||||||
|
|
||||||
|
Next to the existing already integrated storage backends we want to support a high performance redundant storage block device.
|
||||||
|
|
||||||
|
- High performance redundant storage network
|
||||||
|
- Supports our high speed backbone as defined above
|
||||||
|
- Scalable to thousands of machines per cluster.
|
||||||
|
- Replication capability between zones.
|
||||||
|
- **Custom Integration**: We offer integration with selected storage equipment from our customers, accommodating custom integration requirements.
|
||||||
|
|
||||||
|
## Service Level Management
|
||||||
|
|
||||||
|
- The system will have hooks and visualization for achievement of Service levels.
|
||||||
|
- This will allow a commercial service provider to get to higher revenue and better uptime management.
|
||||||
|
|
||||||
|
## Support for Liquid Cooling tanks
|
||||||
|
|
||||||
|
- Do a test setup in liquid cooling rack or node, we can use our selfhealing capabilities to manage better.
|
||||||
|
- Is Integration effort, not really code changes
|
||||||
@ -1,4 +1,4 @@
|
|||||||
## High Level Roadmap HERO Stack
|
## Hero (3Bot) High Level Roadmap
|
||||||
|
|
||||||
The first version of our Hero enables the management of core services such as an innovative database backend, a sovereign git system, and the automatic integration and deployment of our workloads.
|
The first version of our Hero enables the management of core services such as an innovative database backend, a sovereign git system, and the automatic integration and deployment of our workloads.
|
||||||
|
|
||||||
|
|||||||
BIN
collections/tech/roadmap/roadmap.jpg
Normal file
BIN
collections/tech/roadmap/roadmap.jpg
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 97 KiB |
37
collections/tech/roadmap/roadmap.md
Normal file
37
collections/tech/roadmap/roadmap.md
Normal file
@ -0,0 +1,37 @@
|
|||||||
|
|
||||||
|
|
||||||
|
# Roadmap
|
||||||
|
|
||||||
|
## phase 1: wave 1 of companies, leading to our expertise
|
||||||
|
|
||||||
|
- technology creation, was result of 20 years of evolution
|
||||||
|
- 7 startups acquired as part of this process
|
||||||
|
- technology used globally by big vendors
|
||||||
|
- +600m USD Exits
|
||||||
|
|
||||||
|
## phase 2: proof of tech
|
||||||
|
|
||||||
|
- ThreeFold Technology launched globally
|
||||||
|
- +60,000,000 vcpu active
|
||||||
|
- Large scale proof of core technology
|
||||||
|
- Focus on early adoptors in tech space (cloud, web 2/3 ...)
|
||||||
|
- 50m USD funded by founders, community and farmers (people providing capacity)
|
||||||
|
|
||||||
|
## phase 3: commercialization & global expansion
|
||||||
|
|
||||||
|
### phase 3.1: Commercial Partners
|
||||||
|
|
||||||
|
- ThreeFold Launches with Commercial Strategic Partners
|
||||||
|
- Telco Operatators
|
||||||
|
- IT Integrators
|
||||||
|
- Enterprise Roadmap delivered < 6 months (is mainly integration, documentation and UI work)
|
||||||
|
- Together with partners we deliver on the many projects which are in our funnel today e.g. East Africa, Brazil
|
||||||
|
|
||||||
|
### phase 3.2: Large Scale Financancing for Infrastructure
|
||||||
|
|
||||||
|
**Large scaling financing round**
|
||||||
|
|
||||||
|
- financing for infrastructure projects (trillions available right now for infra in emerging countries)
|
||||||
|
- Public STO (security token offering), let world co-own the infra for their Internet
|
||||||
|
- large partnerships drive alternative to Tier 3/4 Datacenters
|
||||||
|
|
||||||
@ -1,4 +1,4 @@
|
|||||||
## High Level Roadmap
|
## TFGrid High Level Roadmap
|
||||||
|
|
||||||
### Status Today
|
### Status Today
|
||||||
|
|
||||||
@ -35,6 +35,8 @@ Additionally, hardware compatibility is excellent, with most machines now suppor
|
|||||||
Considerable effort is being made to enable our partners to go into production;
|
Considerable effort is being made to enable our partners to go into production;
|
||||||
however, for this initiative to truly succeed on planetary level, we need many more nodes deployed in the field.
|
however, for this initiative to truly succeed on planetary level, we need many more nodes deployed in the field.
|
||||||
|
|
||||||
|
Below you can find some of the planned features of TFGrid 4.0 mainly to achieve ability to scale to hundred of thousand of nodes.
|
||||||
|
|
||||||
| | Roadmap | Timing |
|
| | Roadmap | Timing |
|
||||||
| ----------------------------------- | ---------------------------------------------------------------- | ------ |
|
| ----------------------------------- | ---------------------------------------------------------------- | ------ |
|
||||||
| Zero-OS v4 (our next major release) | v4, no more TFChain, mutual credit, marketplace | Q1 25 |
|
| Zero-OS v4 (our next major release) | v4, no more TFChain, mutual credit, marketplace | Q1 25 |
|
||||||
|
|||||||
@ -10,7 +10,7 @@ To build on the ThreeFold Grid, refer to the [Developers](developers@@developers
|
|||||||
- [The Internet Today](internet_today.md)
|
- [The Internet Today](internet_today.md)
|
||||||
- [History of Computers](c64.md)
|
- [History of Computers](c64.md)
|
||||||
- [Too Many Layers](layers.md)
|
- [Too Many Layers](layers.md)
|
||||||
- [The Internet Re-invented](how_does_it_work.md)
|
- [The Internet Re-invented](internet_reinvented.md)
|
||||||
- [World Records](world_records.md)
|
- [World Records](world_records.md)
|
||||||
- [Key Innovations](key_innovations_overview.md)
|
- [Key Innovations](key_innovations_overview.md)
|
||||||
- [Mycelium Network](mycelium_inno.md)
|
- [Mycelium Network](mycelium_inno.md)
|
||||||
|
|||||||
56
collections/tech/vision/cloud_like_insurance.md
Normal file
56
collections/tech/vision/cloud_like_insurance.md
Normal file
@ -0,0 +1,56 @@
|
|||||||
|
|
||||||
|
|
||||||
|
# The Cloud: Beyond Cost – A Business Perspective
|
||||||
|
|
||||||
|
## Introduction
|
||||||
|
|
||||||
|
The transition to cloud computing isn't solely driven by cost savings.
|
||||||
|
|
||||||
|
While affordability is a factor, the primary appeal of cloud services lies in their reliability, scalability, and performance.
|
||||||
|
|
||||||
|
This parallels the concept of insurance, where customers are willing to pay a premium for the assurance of superior service and uptime.
|
||||||
|
|
||||||
|
In the decentralized infrastructure (DePIN) space, establishing trust and reliability is super important, but not enough available in current offerings.
|
||||||
|
|
||||||
|
## Cost vs. Quality
|
||||||
|
|
||||||
|
### Reliability and Uptime
|
||||||
|
|
||||||
|
Customers often prefer to pay a higher price for cloud services that guarantee better uptime and reliability.
|
||||||
|
|
||||||
|
For example, paying $10 per terabyte for a service with stellar uptime and customer support is more appealing than a $5 per terabyte service with frequent downtimes and minimal support. The value proposition lies in uninterrupted access to data and services, which is critical for business operations.
|
||||||
|
|
||||||
|
### Service Level Agreements (SLAs)
|
||||||
|
|
||||||
|
Service Level Agreements (SLAs) play a crucial role in this decision-making process.
|
||||||
|
|
||||||
|
SLAs provide a clear, contractual guarantee of the service levels customers can expect. Companies offering robust SLAs with high uptime guarantees, fast response times, and comprehensive support are more attractive, even at a higher cost.
|
||||||
|
|
||||||
|
## Decentralized Infrastructure (DePIN) and Trust
|
||||||
|
|
||||||
|
### Challenges in DePIN
|
||||||
|
|
||||||
|
One of the significant challenges in DePIN is ensuring that customers can trust decentralized hosters.
|
||||||
|
|
||||||
|
Unlike traditional centralized providers, decentralized hosters need to establish credibility and reliability in a market that is inherently less controlled.
|
||||||
|
|
||||||
|
### Farming Pools and Legal Decentralization
|
||||||
|
|
||||||
|
#### Formation of Farming Pools
|
||||||
|
|
||||||
|
Hosters can group together in farming pools, creating a collaborative environment where resources and responsibilities are shared. These pools can offer combined storage and computational power, enhancing overall performance and reliability.
|
||||||
|
|
||||||
|
#### Security Token Offerings (STOs)
|
||||||
|
|
||||||
|
To fund these farming pools, we can utilize Security Token Offerings (STOs). Investors can buy tokens, representing shares in these pools, thus promoting legal decentralization. This model not only democratizes investment but also ensures that the operations of these pools are transparent and regulated.
|
||||||
|
|
||||||
|
### Transparency and Legal Assurance
|
||||||
|
|
||||||
|
#### Open SLAs
|
||||||
|
|
||||||
|
Each farming pool must be explicit about the SLAs they can deliver. Transparency in service commitments ensures that customers know what performance and reliability to expect. This openness is critical in building trust in a decentralized environment.
|
||||||
|
|
||||||
|
#### Legal Blockchain Contracts
|
||||||
|
|
||||||
|
Blockchain contracts must be legally binding in the real world. These contracts should clearly define the terms of service, dispute resolution mechanisms, and compliance with relevant regulations. Legal enforceability ensures that customers can trust the decentralized hosters to honor their commitments.
|
||||||
|
|
||||||
BIN
collections/tech/vision/farming_pools.jpg
Normal file
BIN
collections/tech/vision/farming_pools.jpg
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 132 KiB |
@ -4,4 +4,4 @@ ThreeFold_Grid is a global, neutral, and sustainable network of autonomous stora
|
|||||||
|
|
||||||
This Internet capacity is produced and allocated locally - similar to the way electricity and other utilities are purchased today. This allows any digital service or application provider to host their services and applications in proximity to the end user leading to significantly greater performance, a lower price point and better margins. This is both more cost effective and green.
|
This Internet capacity is produced and allocated locally - similar to the way electricity and other utilities are purchased today. This allows any digital service or application provider to host their services and applications in proximity to the end user leading to significantly greater performance, a lower price point and better margins. This is both more cost effective and green.
|
||||||
|
|
||||||
!!!def alias:Threefold_Grid,tf_grid
|
|
||||||
|
|||||||
@ -10,13 +10,13 @@ An AI box can be launched in our Zero-OS and can enable any possible AI workload
|
|||||||
|
|
||||||
## AI Hour (AH)
|
## AI Hour (AH)
|
||||||
|
|
||||||
AI hour (AH) is like a kwatth unit for electricty: it represents a AISlice being used for 1h and billed as such.
|
AI hour (AH) is like a kwatth unit for electricty: it represents a AI Slice being used for 1h and billed as such.
|
||||||
|
|
||||||
INCA Hosts (our cloud providers) can price the AI Hour themselves in a chosen currency.
|
INCA Hosts (our cloud providers) can price the AI Hour themselves in a chosen currency.
|
||||||
|
|
||||||
## AISlice Properties
|
## AI Slice Properties
|
||||||
|
|
||||||
The service provider (hoster) defines the following properties per AISlice:
|
The service provider (hoster) defines the following properties per AI Slice:
|
||||||
|
|
||||||
- Type of GPU
|
- Type of GPU
|
||||||
- Price per hour
|
- Price per hour
|
||||||
@ -24,10 +24,10 @@ The service provider (hoster) defines the following properties per AISlice:
|
|||||||
- Max bandwidth
|
- Max bandwidth
|
||||||
- Min bandwidth (min 1 mbit/sec)
|
- Min bandwidth (min 1 mbit/sec)
|
||||||
- Cost per GB bandwidth if any
|
- Cost per GB bandwidth if any
|
||||||
- Max aggregation size (how many of the AISlices can be combined in one node if relevant)
|
- Max aggregation size (how many of the AI Slices can be combined in one node if relevant)
|
||||||
- Link to support site if any (find info about hoster and service capabilities)
|
- Link to support site if any (find info about hoster and service capabilities)
|
||||||
- If linked to Hosting Pool (company giving support on the machines)
|
- If linked to Hosting Pool (company giving support on the machines)
|
||||||
- Location & type of location
|
- Location & type of location
|
||||||
|
|
||||||
Each AISlice has unique ID and can be looked at through a portal (or found).
|
Each AI Slice has unique ID and can be looked at through a portal (or found).
|
||||||
|
|
||||||
|
|||||||
@ -4,14 +4,14 @@
|
|||||||
|
|
||||||
## Cloud Slice
|
## Cloud Slice
|
||||||
|
|
||||||
A cloudslice is a unit of compute, fast storage and memory.
|
A Cloud Slice is a unit of compute, fast storage and memory.
|
||||||
There are unlimited different configurations of cloudslice.
|
There are unlimited different configurations of Cloud Slice.
|
||||||
|
|
||||||
A configuration of a machine defines the cloudslice which can be made.
|
A configuration of a machine defines the Cloud Slice which can be made.
|
||||||
|
|
||||||
A cloudslice can be aggregated to make a bigger cloudslice.
|
A Cloud Slice can be aggregated to make a bigger Cloud Slice.
|
||||||
|
|
||||||
The default cloudslice has
|
The default Cloud Slice has
|
||||||
|
|
||||||
- 4GB memory
|
- 4GB memory
|
||||||
- 2 virtual cores of CPU
|
- 2 virtual cores of CPU
|
||||||
@ -21,7 +21,7 @@ The default cloudslice has
|
|||||||
Terms
|
Terms
|
||||||
|
|
||||||
- The virtual cores are max oversubscribed 4x
|
- The virtual cores are max oversubscribed 4x
|
||||||
- Min passmark per cloudslice is 500 passmark (CPU benchmark)
|
- Min passmark per Cloud Slice is 500 passmark (CPU benchmark)
|
||||||
- At least 50 GB storage available, more is better
|
- At least 50 GB storage available, more is better
|
||||||
|
|
||||||
**Example a node with 64 GB or mem and 2 TB of SSD and 24 virtual cores.**
|
**Example a node with 64 GB or mem and 2 TB of SSD and 24 virtual cores.**
|
||||||
@ -35,15 +35,15 @@ Terms
|
|||||||
|
|
||||||
How does it work:
|
How does it work:
|
||||||
|
|
||||||
- When a developer wants to deploy a virtual machine, they need to define the required capacity and will be able to make a choice based on these CloudSlices, each CloudSlice has different base specs (mem, ssd, gpu, cpu) and reputation, the developer can now make a selection of how many of these StorageSlices need to be given to the virtual machine. This defines the monthly price which will have to be paid as well as capacity available to the VM.
|
- When a developer wants to deploy a virtual machine, they need to define the required capacity and will be able to make a choice based on these Cloud Slices, each Cloud Slice has different base specs (mem, ssd, gpu, cpu) and reputation, the developer can now make a selection of how many of these StorageSlices need to be given to the virtual machine. This defines the monthly price which will have to be paid as well as capacity available to the VM.
|
||||||
|
|
||||||
## Cloud Hour (CH)
|
## Cloud Hour (CH)
|
||||||
|
|
||||||
A cloudhour is like a kwatth unit for electricty: it represents a CloudSlice being used for 1h and billed as such.
|
A cloudhour is like a kwatth unit for electricty: it represents a Cloud Slice being used for 1h and billed as such.
|
||||||
|
|
||||||
INCA Hosts (our cloud providers) can price the CloudHour themselves in a chosen currency.
|
INCA Hosts (our cloud providers) can price the CloudHour themselves in a chosen currency.
|
||||||
|
|
||||||
## CloudSlice Properties
|
## Cloud Slice Properties
|
||||||
|
|
||||||
The service provider (hoster) defines the following properties per cloud box
|
The service provider (hoster) defines the following properties per cloud box
|
||||||
|
|
||||||
@ -57,12 +57,12 @@ The service provider (hoster) defines the following properties per cloud box
|
|||||||
- Cost per GB bandwidth
|
- Cost per GB bandwidth
|
||||||
- Cost for additional storage HDD or SSD per GB/month
|
- Cost for additional storage HDD or SSD per GB/month
|
||||||
- Max additional storage
|
- Max additional storage
|
||||||
- Max aggregation size (how many of the cloudslice can be combined)
|
- Max aggregation size (how many of the Cloud Slice can be combined)
|
||||||
- Link to support site if any (find info about hoster and service capabilities)
|
- Link to support site if any (find info about hoster and service capabilities)
|
||||||
- If linked to Hosting Pool (company giving support on the machines)
|
- If linked to Hosting Pool (company giving support on the machines)
|
||||||
- Pub ip address possible or not (is option)
|
- Pub ip address possible or not (is option)
|
||||||
- Link to monitoring page (if any)
|
- Link to monitoring page (if any)
|
||||||
- Location & type of location
|
- Location & type of location
|
||||||
|
|
||||||
Each cloudslice has unique ID and can be looked at through a portal (or found).
|
Each Cloud Slice has unique ID and can be looked at through a portal (or found).
|
||||||
|
|
||||||
|
|||||||
@ -1,7 +1,7 @@
|
|||||||
|
|
||||||
A Cloud, Storage or AISlice is a part of a server/computer (TF or INCA Node) which delivers a service which has well defined properties in relation to capacity, pricing, serviceabity, capabilities.
|
A Cloud, Storage or AI Slice is a part of a server/computer (3Node) which delivers a service which has well defined properties in relation to capacity, pricing, serviceabity, capabilities.
|
||||||
|
|
||||||
These Cloud, Storage or AISlices can be bought by the INCA/TF Community through the INCA marketplace.
|
These Cloud, Storage or AI Slices can be bought by the ThreeFold Community through the TF Marketplace.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|||||||
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in New Issue
Block a user