diff --git a/books/projectinca/SUMMARY.md b/books/projectinca/SUMMARY.md
index a9d83f2..a29bb21 100644
--- a/books/projectinca/SUMMARY.md
+++ b/books/projectinca/SUMMARY.md
@@ -1,12 +1,48 @@
- [Introduction](projectinca/intro.md)
-- [The Plan](projectinca/theplan_c.md)
+- [The Plan](projectinca/theplan_a.md)
+ - [**Requirements**](projectinca/requirements.md)
+ - [Tokens](projectinca/inca1.md)
- [Funding](projectinca/funding.md)
- [P2P Promotion](projectinca/peer2peer_promotion.md)
- [Liquidity](projectinca/liquidity.md)
-- [INCA Tokenomics](projectinca/tokens.md)
- - [INCA](projectinca/inca.md)
- - [TFT](projectinca/tft.md)
+ - [Governance](projectinca/governance.md)
+- [Collaboration](projectinca/collab.md)
+ - [Principles](projectinca/collaboration.md)
+ - [Messaging](tfgrid3/messaging.md)
+ - [Teams](projectinca/teams.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)
+ - [About Us](tfgrid3/who_are_we.md)
+ - [The Internet Today](tech/internet_today.md)
+ - [History of Computers](tech/history/c64.md)
+ - [Too Many Layers](tech/history/layers.md)
+ - [Values](values/planet_people_first.md)
+ - [Why TFGrid](why/why.md)
+ - [Cloud Too Centralized](why/current_cloud_too_centralized.md)
+ - [Countries Don't Have Their Internet](why/countries_no_internet.md)
+ - [Human Right](why/internet_human_right.md)
+ - [Social Warming](why/social_warming.md)
+- [**Technology**](projectinca/technology.md)
+- [INCA Tokenomics](projectinca/tokens1.md)
+- [INCA Marketplace](projectinca/marketplace.md)
+ - [Pricing](projectinca/marketplace_pricing.md)
+ - [AI Slices](tfgrid4/aislice.md)
+ - [Cloud Slices](tfgrid4/cloudslice.md)
+ - [Storage Slices](tfgrid4/storageslice.md)
+- [INCA Farming](projectinca/inca_farming.md)
+ - [INCA Nodes](projectinca/inca_nodes.md)
+ - [INCA Node Silver](projectinca/inca_node_silver.md)
+ - [INCA Node Platinum](projectinca/inca_node_platinum.md)
+ - [INCA Node AI](projectinca/inca_node_ai.md)
+ - [INCA Routers](projectinca/inca_routers.md)
+ - [INCA Network Map](projectinca/networkmap.md)
+ - [Reward Simulation](projectinca/inca_farming_reward.md)
+- [INCA Stories](projectinca/stories.md)
+ - [INCA App Spec](projectinca/inca1pp.md)
- [INCA Grants](projectinca/grants.md)
- [v3.x Grants](projectinca/grants_tft.md)
- [Deploy AISlices](projectinca/grant_aislice.md)
@@ -22,76 +58,22 @@
- [Establish Thorchain DEX](projectinca/grant_thorchain.md)
- [v4.x Grants](projectinca/grants_inca.md)
- [Grant Voting Process](projectinca/grant_voting_process.md)
-- [INCA Marketplace](projectinca/marketplace.md)
- - [Pricing](projectinca/marketplace_pricing.md)
- - [AI Slices](tfgrid4/aislice.md)
- - [Cloud Slices](tfgrid4/cloudslice.md)
- - [Storage Slices](tfgrid4/storageslice.md)
-- [INCA Farming](projectinca/inca_farming.md)
- - [INCA Nodes](projectinca/inca_nodes.md)
- - [INCA Node Silver](projectinca/inca_node_silver.md)
- - [INCA Node Platinum](projectinca/inca_node_platinum.md)
- - [INCA Node AI](projectinca/inca_node_ai.md)
- - [INCA Routers](projectinca/inca_routers.md)
- - [INCA Network Map](projectinca/networkmap.md)
- - [Reward Simulation](projectinca/inca_farming_reward.md)
-- [INCA Launch Collaboration](projectinca/collab.md)
- - [Remuneration](projectinca/remuneration.md)
- - [Promotion Effort](tfgrid3/promotion.md)
- - [Messaging](tfgrid3/messaging.md)
- - [Teams](projectinca/teams.md)
-- [INCA Stories](projectinca/stories.md)
- - [INCA App Spec](projectinca/inca_app.md)
- [INCA Grid Utilization](partners_utilization/partners.md)
+ - [Holochain](partners_utilization/holochain.md)
- [Hero - Project Mycelium](projectinca/hero.md)
- [Digital Freezone](partners_utilization/freezone.md)
- [Tanzania Internet](partners_utilization/tanzania.md)
- [Elestio](partners_utilization/elestio.md)
- [Earth Wallet](partners_utilization/earth_wallet.md)
- - [Holochain](partners_utilization/holochain.md)
- - [Helium](partners_utilization/helium.md)
- [Sikana](partners_utilization/sikana.md)
- [Vindo](partners_utilization/vindo.md)
- [Vverse](partners_utilization/vverse.md)
- [Tier S Datacenter](partners_utilization/tier_s_datacenter.md)
- [Engineering](projectinca/engineering.md)
- [INCA Grid 4.0](projectinca/tfgrid4.md)
-- [Project Info](projectinca/project_info.md)
- - [About Us](tfgrid3/who_are_we.md)
- - [The Internet Today](tech/internet_today.md)
- - [History of Computers](tech/history/c64.md)
- - [Too Many Layers](tech/history/layers.md)
- - [Values](values/planet_people_first.md)
- - [Tech Key Innovations](tech/key_innovations_overview.md)
- - [Mycelium Network](tech/mycelium_innovation.md)
- - [Zero-OS](tech/zos_innovation.md)
- - [Quantum Safe Storage](tech/zstor_innovation.md)
- - [Quantum Safe Filesystem](tech/qsfs_innovation.md)
- - [Flist: Better OS Images](tech/flist_innovation.md)
- - [FungiStor](tech/fungistor_innovation.md)
- - [Network Wall](tech/network_wall_innovation.md)
- - [Technology](tech/technology.md)
- - [Architecture](tech/architecture.md)
- - [Energy Efficient](tech/energy_efficient.md)
- - [Why TFGrid](why/why.md)
- - [Cloud Too Centralized](why/current_cloud_too_centralized.md)
- - [Countries Don't Have Their Internet](why/countries_no_internet.md)
- - [Human Right](why/internet_human_right.md)
- - [Social Warming](why/social_warming.md)
-- [INCA Cloud Core Capabilities](tech/features.md)
- - [Compute](tech/compute.md)
- - [Zero-OS](tech/zos.md)
- - [Infrastructure As Code](tech/smartcontract_iac.md)
- - [CoreX](tech/corex.md)
- - [Storage](tech/qsss_home.md)
- - [Quantum Safe Storage Algo](tech/qss_algorithm.md)
- - [Zero Knowledge proof](tech/qss_zero_knowledge_proof.md)
- - [NFT Storage](tech/nft_storage.md)
- - [S3 Storage](tech/s3_interface)
- - [File System](tech/qss_filesystem.md)
- - [Network](tech/networking.md)
- - [Mycelium](tech/mycelium.md)
- - [Web Gateway](tech/webgw.md)
+- [Plan B](projectinca/theplan_b.md)
+ - [INCA Plan B](projectinca/tokens0.md)
+ - [TFT](projectinca/tft0.md)
- [Appendix](projectinca/appendix.md)
- [Tokenomics TFGrid 3.14](tfgrid3/tokenomics.md)
- [Farming Reward TFGrid 3](tfgrid3/farming_reward.md)
diff --git a/books/system_administrators/Makefile b/books/sysadmins/Makefile
similarity index 100%
rename from books/system_administrators/Makefile
rename to books/sysadmins/Makefile
diff --git a/books/system_administrators/SUMMARY.md b/books/sysadmins/SUMMARY.md
similarity index 99%
rename from books/system_administrators/SUMMARY.md
rename to books/sysadmins/SUMMARY.md
index a1dfc94..aa0d1e3 100644
--- a/books/system_administrators/SUMMARY.md
+++ b/books/sysadmins/SUMMARY.md
@@ -1,4 +1,4 @@
-- [Table of Contents](system_administrators/system_administrators_book_toc.md)
+- [Introduction](system_administrators/system_administrators_book.md)
- [Getting Started](system_administrators/getstarted/tfgrid3_getstarted.md)
- [SSH Remote Connection](system_administrators/getstarted/ssh_guide/ssh_guide.md)
- [SSH with OpenSSH](system_administrators/getstarted/ssh_guide/ssh_openssh.md)
diff --git a/books/system_administrators/scripts/calculate_cloud_pricing.sh b/books/sysadmins/scripts/calculate_cloud_pricing.sh
similarity index 100%
rename from books/system_administrators/scripts/calculate_cloud_pricing.sh
rename to books/sysadmins/scripts/calculate_cloud_pricing.sh
diff --git a/books/system_administrators/scripts/calculate_marketcap.sh b/books/sysadmins/scripts/calculate_marketcap.sh
similarity index 100%
rename from books/system_administrators/scripts/calculate_marketcap.sh
rename to books/sysadmins/scripts/calculate_marketcap.sh
diff --git a/books/system_administrators/scripts/generate_wallets.sh b/books/sysadmins/scripts/generate_wallets.sh
similarity index 100%
rename from books/system_administrators/scripts/generate_wallets.sh
rename to books/sysadmins/scripts/generate_wallets.sh
diff --git a/books/system_administrators/sync_production.sh b/books/sysadmins/sync_production.sh
similarity index 85%
rename from books/system_administrators/sync_production.sh
rename to books/sysadmins/sync_production.sh
index c2cee8b..db1860a 100755
--- a/books/system_administrators/sync_production.sh
+++ b/books/sysadmins/sync_production.sh
@@ -1,5 +1,5 @@
#!/bin/bash
set -ex
-export NAME=system_administrators
+export NAME=sysadmins
hero mdbook -u https://git.ourworld.tf/tfgrid/info_tfgrid/src/branch/manual/heroscript/$NAME
rsync -rv ~/hero/www/info/$NAME/ root@info.ourworld.tf:/root/hero/www/info/$NAME/
diff --git a/books/tech/SUMMARY.md b/books/tech/SUMMARY.md
index 7799bb6..d3c9e02 100644
--- a/books/tech/SUMMARY.md
+++ b/books/tech/SUMMARY.md
@@ -1,20 +1,30 @@
-- [Introduction](tech/technology.md)
+- [Overview](tech/overview.md)
- [The Internet Today](tech/internet_today.md)
- [History of Computers](tech/history/c64.md)
- [Too Many Layers](tech/history/layers.md)
- [The Internet Re-invented](tech/how_does_it_work.md)
- [World Records](tech/world_records.md)
-- [Key Innovations](tech/key_innovations_overview.md)
- - [Mycelium Network](tech/mycelium_innovation.md)
- - [Zero-OS](tech/zos_innovation.md)
- - [Quantum Safe Storage](tech/zstor_innovation.md)
- - [Quantum Safe Filesystem](tech/qsfs_innovation.md)
- - [FList: Better OS Images](tech/flist_innovation.md)
- - [FungiStor](tech/fungistor_innovation.md)
- - [Network Wall](tech/network_wall_innovation.md)
- [Architecture](tech/architecture.md)
-- [Energy Efficient](tech/energy_efficient.md)
-- [Decentralized Cloud Core Capabilities](tech/features.md)
+- [Key Innovations](tech/key_innovations_overview.md)
+ - [Compute](tech/compute_inno.md)
+ - [Zero-OS](tech/zos_innovation.md)
+ - [Zero-Images](tech/flist_innovation.md)
+ - [Network](tech/network_inno.md)
+ - [Mycelium](tech/mycelium_innovation.md)
+ - [Network Wall](tech/network_wall_innovation.md)
+ - [Storage](tech/storage_inno.md)
+ - [Quantum Safe Storage](tech/zstor_innovation.md)
+ - [Quantum Safe Filesystem](tech/qsfs_innovation.md)
+ - [FungiStor](tech/fungistor_innovation.md)
+ - [Energy Efficient](tech/energy_efficient.md)
+- [Status/Roadmap](tech/tfgrid_roadmap.md)
+ - [Hero Roadmap](tech/hero_roadmap.md)
+- [ThreeFold Core Components](tech/features.md)
+ - [Compute](tech/compute.md)
+ - [Zero-OS](tech/zero_os.md)
+ - [Zero-Chance](tech/zero_chance.md)
+ - [Zero-Install](tech/zero_install.md)
+ - [Zero-Boot](tech/zero_boot.md)
- [Storage](tech/qsss_home.md)
- [Quantum Safe Storage Algo](tech/qss_algorithm.md)
- [Zero Knowledge proof](tech/qss_zero_knowledge_proof.md)
@@ -24,15 +34,16 @@
- [Network](tech/networking.md)
- [Mycelium](tech/mycelium.md)
- [Web Gateway](tech/webgw.md)
-- [Partners Utilization](partners_utilization/partners.md)
+- [Partners / Utilization](partners_utilization/partners.md)
- [Sikana](partners_utilization/sikana.md)
- [Vindo](partners_utilization/vindo.md)
- [Mkondo](partners_utilization/mkondo.md)
- [Vverse](partners_utilization/vverse.md)
- - [Earth Wallet](partners_utilization/earth_wallet.md)
- - [Elestio](partners_utilization/elestio.md)
- - [OW Freezone](partners_utilization/freezone.md)
- - [Helium](partners_utilization/helium.md)
- [Holochain](partners_utilization/holochain.md)
- [TZG](partners_utilization/tanzania.md)
- - [Tier-S DC](partners_utilization/tier_s_datacenter.md)
\ No newline at end of file
+ - [Tier-S DC](partners_utilization/tier_s_datacenter.md)
+ - [OW Freezone](partners_utilization/freezone.md)
+ - [Earth Wallet](partners_utilization/earth_wallet.md)
+ - [Helium](partners_utilization/helium.md)
+
+
diff --git a/collections/mkondo/mkondo.md b/collections/mkondo/mkondo.md
index 238c8b2..79229e9 100644
--- a/collections/mkondo/mkondo.md
+++ b/collections/mkondo/mkondo.md
@@ -6,5 +6,7 @@
Above is not a movie or photo, we can stream 100% photorealistic real time rendered environments to our customers.
-Check out the result on http://metaversestreaming.threefold.me , please note this is not a video of a real place, this is a rendered result of streaming a virtual reality session to the user.
+
+
+Check out the result on [this link](https://vimeo.com/888463280) , please note this is not a video of a real place, this is a rendered result of streaming a virtual reality session to the user.
diff --git a/collections/partners_utilization/partners.md b/collections/partners_utilization/partners.md
index 7055063..d63a431 100644
--- a/collections/partners_utilization/partners.md
+++ b/collections/partners_utilization/partners.md
@@ -8,7 +8,6 @@ The following partners all have the potential to utilize a lot of our capacity a
- [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.
- [Tanzania Sovereign Internet](tanzania.md) a sovereign Internet for a country
-- [Elestio](elestio.md) +300 opensource apps on top of TFGrid (managed, supported)
- [Mkondo](mkondo.md) most realistic rendering of VR/AR env on top of TFGrid
- [Vindo](vindo.md) collaborative metaverse, best quality at low bandwidth
- [Vverse](vverse.md) virtual reality museum
diff --git a/collections/projectinca/checklist.md b/collections/projectinca/checklist.md
new file mode 100644
index 0000000..e73ad06
--- /dev/null
+++ b/collections/projectinca/checklist.md
@@ -0,0 +1,20 @@
+
+
+# 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 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.
+- [ ] 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
+
+## For go2market contributors
+
+Everyone dealing with product management, tokens, marketing or any other go2market activity.
+
+- [ ] [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)
\ No newline at end of file
diff --git a/collections/projectinca/collab/teams.md b/collections/projectinca/collab/teams.md
index 5097520..24303c5 100644
--- a/collections/projectinca/collab/teams.md
+++ b/collections/projectinca/collab/teams.md
@@ -1,5 +1,11 @@
# Teams
+> TODO: complete
+
+
+## Core Team
+
+> todo:
## Direct Promotion: PP2P teams
diff --git a/collections/projectinca/grants/grants_tft.md b/collections/projectinca/grants/grants_tft.md
index 4461b36..40ff7ec 100644
--- a/collections/projectinca/grants/grants_tft.md
+++ b/collections/projectinca/grants/grants_tft.md
@@ -2,6 +2,8 @@
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
option = {
title: {
diff --git a/collections/projectinca/hero.md b/collections/projectinca/hero.md
index f216747..485b8d9 100644
--- a/collections/projectinca/hero.md
+++ b/collections/projectinca/hero.md
@@ -6,7 +6,7 @@
The project will launch our **HERO**, a super efficient digital companion.
-This project will do a new token and token sell, private and public. This project has the potential to fund a lot of the further ThreeFold Grid expansion (version 4). This project uses TFGrid 4.0 as the main cloud for its decentralization.
+This project will probably do a new token and token sell, private and public. This project has the potential to fund a lot of the further ThreeFold Grid expansion (version 4). This project uses TFGrid 4.0 as the main cloud for its decentralization.
**The first Digital Backbone in the world compatible with Web2, Web3 and AI.**:
diff --git a/collections/projectinca/img/tech.png b/collections/projectinca/img/tech.png
new file mode 100644
index 0000000..6957d3e
Binary files /dev/null and b/collections/projectinca/img/tech.png differ
diff --git a/collections/projectinca/intro.md b/collections/projectinca/intro.md
index 5452a0a..8dbce96 100644
--- a/collections/projectinca/intro.md
+++ b/collections/projectinca/intro.md
@@ -1,30 +1,12 @@
-# Compute is currency of future
-
-
-
-
-## ThreeFold DePIN Launch: Project INCA
-
-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.
-
-*Please do note the name INCA will prob still change.*
-
-## 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.
-
+!!wiki.include page:'intro0.md'
## Learn More
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
diff --git a/collections/projectinca/intro0.md b/collections/projectinca/intro0.md
new file mode 100644
index 0000000..4d0a2bd
--- /dev/null
+++ b/collections/projectinca/intro0.md
@@ -0,0 +1,22 @@
+
+# Compute is currency of future
+
+
+
+
+## ThreeFold DePIN Launch: Project INCA
+
+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.
+
+
diff --git a/collections/projectinca/links.md b/collections/projectinca/links.md
new file mode 100644
index 0000000..f86065d
--- /dev/null
+++ b/collections/projectinca/links.md
@@ -0,0 +1,5 @@
+
+
+# Links
+
+> TODO: make list of all important links e.g. Telegram, ...
\ No newline at end of file
diff --git a/collections/projectinca/peer2peer_promotion.md b/collections/projectinca/peer2peer_promotion.md
index ab53b2d..7a4b4ba 100644
--- a/collections/projectinca/peer2peer_promotion.md
+++ b/collections/projectinca/peer2peer_promotion.md
@@ -1,5 +1,7 @@
+> TODO: to be discussed & completed
+
# Peer2Peer Promotion (P2PP)
We believe the rollout must be viral. Here's how to achieve this.
@@ -19,6 +21,8 @@ We expect the TF Scouts to do the following:
**Reward**:
+> TODO: complete/discuss
+
- TF Connect Installed -> 500 INCA
- Referral to other person -> 50 INCA (after installing the TFConnect)
- Stories as executed by P2PP Team
@@ -29,7 +33,6 @@ We expect the TF Scouts to do the following:
## Technical Requirements
-- New TFConnect
-- New backend for TFConnect (can be run by TF DMCC)
-- Referral system
+- New INCA App
+- Referral system in INCA App
diff --git a/collections/projectinca/plan/advisors.md b/collections/projectinca/plan/advisors.md
new file mode 100644
index 0000000..9f92029
--- /dev/null
+++ b/collections/projectinca/plan/advisors.md
@@ -0,0 +1,2 @@
+## Advisors
+
diff --git a/collections/projectinca/plan/collaboration.md b/collections/projectinca/plan/collaboration.md
new file mode 100644
index 0000000..4559ccd
--- /dev/null
+++ b/collections/projectinca/plan/collaboration.md
@@ -0,0 +1,88 @@
+
+
+# Collaboration
+
+We had the pleasure collaborating on the creation and succesful development for more than 10 high tech startups.
+
+We realized that the way how we collaborate defines a big part of the outcome.
+
+> A lot of this knowledge can be found on [https://threefold.info/cocreation](https://threefold.info/cocreation)/
+
+Working together with the OurWorld / ThreeFold ecosystem means you agree and are committed to above as such its highly appreciated you take some time to go over the info.
+
+## Summary lets choose the best of the 2 ways
+
+There are 2 ways how to collaborate:
+
+1. The typical pyramid system, where a boss manages (directs) a sub boss until the required results are achieved and any non compliance results in “fixing” the issue. This results in harsh cultures and not even that effective.
+2. A circular system with clear stakeholders, examples are scrum, … These are more agile methods and leave a lot of freedom but require a certain discipline. To let 2 work agreement on how to interface (tools, process reports, …) needs to be agreed upon between ALL stakeholders because it's more dynamic and more interconnected compared to 1.
+
+Obviously we are not a believer of 1, this means certain discipline and agreement to following existing tooling is a must.
+
+2 is a commitment though, often we see people wanting to combine the benefits of 1 into 2, that often doesn’t work e.g. “TRUST me, I know what I am doing, let me alone…” these are statements which can work in 1 not in 2.
+
+ In 2 we trust each other by design but we require transparency and ability to comment on the work we are doing.
+
+
+## Tools
+
+TF has adopted a set of tools to work following “2”, these tools are maybe not something you are used to or comfortable with. But don’t panic, millions of people have been able to do this before you, \
+so I guess you can do the same (the system we use is the same as github but actually easier).
+
+### Our tools
+
+* We use Gitea for
+ * Task management
+ * Story Management
+ * Websites
+ * Specs, Code, …
+ * E-Books, Wiki’s, Manuals
+ * There is continuous integration & deployment.
+ * Gitea is the basis for our own future vision of how to collaborate deploy on TFGrid see [https://threefold.info/tech/tech/roadmap.html](https://threefold.info/tech/tech/roadmap.html)
+* We use GDrive for all our other documents
+ * All Info is in a GDrive folder dedicated for Project INCA
+* We use Telegram for internal communication
+ * Also groups, you can have topics just like we do in Slack.
+ * I am sorry but I don’t want our team to lose time by using yet another tool
+
+### Not enough reporting
+
+A common complaint is that gitea doesn’t give enough reporting, there is a plan to fix this
+
+* A portal is being created to make it easy for all of us to collaborate, will be done in Summer
+ * Company/Project Directory \
+(what are all projects our larger community is working on)
+ * People Directory
+ * Nice overview of Stories/Tasks/Milestones/… will get info from Gitea
+ * Priority management: will warn user when we are getting behind on tasks, stories
+ * Reward dashboard (tokens, shares, reward pool, …)
+ * Information overview (what is most relevant info per project)
+ * Contract overview (with security of course), includes our SAFE’s
+* Phase 2:
+ * Internal chat/messaging \
+(might replace telegram for internal communication at one point in time)
+ * Integrated sort of forum for discussions
+ * Video Conferencing
+
+
+## We work in an agile way
+
+As such we want everyone to understand and endorse that we are not a pyramid and are ok to work in a more Teal Based organization structure:
+
+* No-one is the boss of a pyramid, we don’t do politics.
+* Instead we have coordinators and they make sure that stories, milestones are understood, these are on gitea, they make sure there are stakeholders and stakeholders do agree on the stories & milestones. (do note stories are high level and have nicely described deliverables and requirements).
+* All information worked at all times is transparent, and on the right location, no-one keeps it on their own drive not even to prepare, people are disciplined to make sure files no longer relevant go to _archive folder.
+* We avoid too many meetings, we make stories, we make specs, we review specs, we use git… to get to consensus and then the occasional stakeholder meeting is used to find consensus. We log (comments) on the stories. We make everything accountable.
+* We accept our wiki as a single source of truth even if it means learning how to use it, we will not ad hoc put all kinds of documents everywhere which of course cannot be followed by the team and will need endless meetings.
+* We are aware of victimhood and try not to be there, we take responsibility for our own actions first, if the story is not clear and we accepted it it's our own fault, if we didn’t escalate to the right stakeholders it's our own fault, if we didn’t report our progress properly it's our own fault people don’t know,...
+* We avoid as much as we can centralized tools, only when there is really no alternative (yet) we use them e.g. GDrive and the stakeholders do agree. No-one has the power to choose another tool unless OurWorld, Project INCA & TF together agree. This is super important to make sure that we can create this portal and work together efficiently.
+* Whoever cannot work this way is not welcome to be an active contributor to the Project INCA Team. The coordinators make sure this section is enforced.
+
+
+## We do believe
+
+* Our Team Members are passionate and truly Believe TF has something to offer.
+* Our Team Members DO not do it to make a quick win (tokens), \
+Our Team Members do it in the first place because they want TF to succeed.
+* Our Team Members are capable of collaborating and being inclusive and respectful.
+* Our Team Members do understand we are different and want to be different
diff --git a/collections/projectinca/plan/governance.md b/collections/projectinca/plan/governance.md
new file mode 100644
index 0000000..85ac9cf
--- /dev/null
+++ b/collections/projectinca/plan/governance.md
@@ -0,0 +1,23 @@
+## 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
diff --git a/collections/projectinca/plan/ideas.md b/collections/projectinca/plan/ideas.md
new file mode 100644
index 0000000..c9fb40b
--- /dev/null
+++ b/collections/projectinca/plan/ideas.md
@@ -0,0 +1,19 @@
+
+
+# Ideas
+
+
+## INCA G
+
+
+* Replacement strategy of staking is
+ * People need INCA in their wallets to get discounts.
+ * Certain amount of INCA is needed to be held per Node if they want to guarantee their SLA’s , if they can’t achieve their SAL then these tokens are used to compensate market
+* An INCA G (Generator) token can be created
+ * INCA G is a generator token of future capacity, name can change
+ * This token can be sold with no limits even on Solana as long as people are whitelisted
+ * INCA G will be structured as a real Security in our Digital Freezone once we have it.
+ * INCA G can only be sold to people who did KYC/AML \
+and paid a 24 EUR membership fee to be part of our cooperative in the freezone.
+* We can organize semi public sell of INCA Tokens through free-zone
+* Other ideas ???
\ No newline at end of file
diff --git a/collections/projectinca/plan/requirements.md b/collections/projectinca/plan/requirements.md
new file mode 100644
index 0000000..b3ec1f3
--- /dev/null
+++ b/collections/projectinca/plan/requirements.md
@@ -0,0 +1,75 @@
+
+# Requirements = “our box we operate in”
+
+Its important we all agree on our requirements and all actions will be in line with these requirements.
+
+## Regulatory
+
+Avoid any possible link to token as security
+
+* There will be no staking of INCA or any other token created.
+* There will be no yield generating instruments created with INCA
+* There will be no public launch of INCA Tokens (private sell ok)
+
+A COOP might be a good structure for resolving our regulatory requirements for farmers \
+& larger customers.
+
+* It needs to be all super simple and easy for our user base.
+* Every farmer and every user who is spending more than 1000 USD/month \
+(using any supported digital or fiat currency) \
+is part of a COOP which will be structured in our digital freezone.
+* This will be made super easy (just KYC simple process) and you pay 24 USD to get started.
+* COOP Membership fee is :
+ * 1 USD per month for basic users (to be paid at setup) for INCA G holders
+ * 10 USD per month for members who need more features
+
+
+## Reputation
+
+One of our biggest strengths is how we link back to the real world through our government connections and soon a major telco. While this is great this also means we need to stay very clean in relation to reputation and how we come across.
+
+## Positioning
+
+* We don’t try to be like the other casino projects or even mimic what they do.
+* We are ourselves a decent project, with an aim to become the biggest Edge Cloud Provider in the world which is a viable alternative to the centralized players.
+* We focus on expansion because that is needed first.
+
+## Marketing Wise
+
+* We will not brand ourselves or even be understood as a pump & dump, \
+We stay loyal to our values at all times.
+* We are different and will position ourselves as being different.
+
+
+## Funding & Tokenomics
+
+Let's together agree on the following:
+
+
+
+* There is focus on finding funding, the people who do fundraise do understand how it works e.g. first get to the term sheet before giving certain info, get lots of info open for negotiation and advice, know that most questions asked are asked for other reasons, …
+* If there is vesting then Vesting for TFT holders will be the same for ALL TFT holders.
+* We are perfectly ok to show an overview of who has which tokens but some work needs to be done, some original token holders agree to grant tokens to a pool, some of the details are on our INCA wiki.
+* TFT x1 or TFT x2 can be part of negotiation once enough money has been found, e.g. if 30m EUR comes then I am sure we can convince our community to keep it on 1x \
+(1x = means 1 Billion of the 4 Billion)
+* We will not sell INCA tokens underneath 0.05 USD per INCA, \
+this needs to be the absolute lowest level (and anyhow no public sell).
+
+
+## Transparency
+
+
+* There is a weekly report sent to community, TF, Ourworld around what has been achieved
+* There are regular meetings with community
+* There are regular stakeholder meetings (at least 1x per week at start)
+* All our docs are as much as possible opensource, on gitea (doc…), if not possible gdrive but always in the same gdrive under the same root folder and open as much as possible.
+
+
+# Remark: we are ok with
+
+* Using exchanges, market makers, …
+* Meeting the market where it's at.
+* Use influencers.
+* Play the game (as long as we don’t lose our values)
+* Use whatever tools which are needed to reach communities (they can be centralized ofcourse)
+
diff --git a/collections/projectinca/plan/tf_colab.md b/collections/projectinca/plan/tf_colab.md
new file mode 100644
index 0000000..0c431b9
--- /dev/null
+++ b/collections/projectinca/plan/tf_colab.md
@@ -0,0 +1,27 @@
+
+# Threefold is involved
+
+
+## Involvement of TF9
+
+We communicate between the circles using our tooling…
+
+* Listen to requirements and keep on developing the tech.
+* Support the TFGrid, keep it up and running
+* Create TF Grid 4
+
+## Involvement of ThreeFold Dubai
+
+We communicate between the circles using our tooling…
+
+* Find nice projects who want to build on top of us e.g. Holochain, DFinity, …
+* Manage the grant pools.
+* Manage the validators for TFGrid, means help the people who host them, it's decentralized
+* Manage the tokens and guardians (protectors of smart contracts, bridges).
+* Help maintain the wiki’s, websites, …
+* Help in fundraise
+
+
+> TODO: complete
+
+
diff --git a/collections/projectinca/plan/theplan_a.md b/collections/projectinca/plan/theplan_a.md
new file mode 100644
index 0000000..2185384
--- /dev/null
+++ b/collections/projectinca/plan/theplan_a.md
@@ -0,0 +1,16 @@
+
+
+# DePIN Launch Plan A
+
+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)
+
diff --git a/collections/projectinca/plan/theplan_c.md b/collections/projectinca/plan/theplan_b.md
similarity index 98%
rename from collections/projectinca/plan/theplan_c.md
rename to collections/projectinca/plan/theplan_b.md
index 5273fa0..c78b225 100644
--- a/collections/projectinca/plan/theplan_c.md
+++ b/collections/projectinca/plan/theplan_b.md
@@ -1,6 +1,8 @@
-# DePIN Launch
+# DePIN Launch Plan B
+
+> In case not enough funding was found.
ThreeFold is expanding to the DePIN market.
diff --git a/collections/projectinca/project_info.md b/collections/projectinca/project_info.md
index 1fd9dc3..67e8dc9 100644
--- a/collections/projectinca/project_info.md
+++ b/collections/projectinca/project_info.md
@@ -4,5 +4,5 @@
In this section, we provide general information on the Project INCA.
-> Please do note the name will prob still change.
+
diff --git a/collections/projectinca/technology.md b/collections/projectinca/technology.md
new file mode 100644
index 0000000..3ad0e0d
--- /dev/null
+++ b/collections/projectinca/technology.md
@@ -0,0 +1,3 @@
+
+
+> see [https://threefold.info/tech](https://threefold.info/tech)
\ No newline at end of file
diff --git a/collections/projectinca/tokens/img/tokens_distr.png b/collections/projectinca/tokens0/img/tokens_distr.png
similarity index 100%
rename from collections/projectinca/tokens/img/tokens_distr.png
rename to collections/projectinca/tokens0/img/tokens_distr.png
diff --git a/collections/projectinca/tokens/img/tokens_release.png b/collections/projectinca/tokens0/img/tokens_release.png
similarity index 100%
rename from collections/projectinca/tokens/img/tokens_release.png
rename to collections/projectinca/tokens0/img/tokens_release.png
diff --git a/collections/projectinca/tokens0/inca0.md b/collections/projectinca/tokens0/inca0.md
new file mode 100644
index 0000000..0ab5af1
--- /dev/null
+++ b/collections/projectinca/tokens0/inca0.md
@@ -0,0 +1,69 @@
+
+## 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).
+
+
+
\ No newline at end of file
diff --git a/collections/projectinca/tokens/tft.md b/collections/projectinca/tokens0/tft0.md
similarity index 100%
rename from collections/projectinca/tokens/tft.md
rename to collections/projectinca/tokens0/tft0.md
diff --git a/collections/projectinca/tokens/tokens.md b/collections/projectinca/tokens0/tokens0.md
similarity index 90%
rename from collections/projectinca/tokens/tokens.md
rename to collections/projectinca/tokens0/tokens0.md
index 70e08b8..a1db858 100644
--- a/collections/projectinca/tokens/tokens.md
+++ b/collections/projectinca/tokens0/tokens0.md
@@ -1,4 +1,6 @@
-# Tokens Distribution
+# 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.
diff --git a/collections/projectinca/tokens/inca.md b/collections/projectinca/tokens1/inca1.md
similarity index 100%
rename from collections/projectinca/tokens/inca.md
rename to collections/projectinca/tokens1/inca1.md
diff --git a/collections/projectinca/tokens1/inca_a.md b/collections/projectinca/tokens1/inca_a.md
new file mode 100644
index 0000000..945c938
--- /dev/null
+++ b/collections/projectinca/tokens1/inca_a.md
@@ -0,0 +1,61 @@
+
+
+
+## TOKENS
+
+There might be 2 tokens
+
+> TODO: to complete
+
+### INCA Token
+
+> INCA = INternet CApacity (is the token of buying/selling Internet/Cloud Capacity)
+
+- 4 billion INCA will be created
+
+
+
+
+### INCA-G (to be discussed)
+
+> 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?
+
+> TODO: to be discussed
+
+### 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)
+
+> TODO: to be discussed
+
+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,
which are serious growth regions in the world.
+
diff --git a/collections/projectinca/tokens1/tft1.md b/collections/projectinca/tokens1/tft1.md
new file mode 100644
index 0000000..b1dd6d0
--- /dev/null
+++ b/collections/projectinca/tokens1/tft1.md
@@ -0,0 +1,55 @@
+## 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).
\ No newline at end of file
diff --git a/collections/projectinca/tokens1/tokens1.md b/collections/projectinca/tokens1/tokens1.md
new file mode 100644
index 0000000..6abbf86
--- /dev/null
+++ b/collections/projectinca/tokens1/tokens1.md
@@ -0,0 +1,48 @@
+# 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)'
+ }
+ }
+ }
+ ]
+};
+```
+
diff --git a/collections/system_administrators/system_administrators_book.md b/collections/system_administrators/system_administrators_book.md
new file mode 100644
index 0000000..5ccf13b
--- /dev/null
+++ b/collections/system_administrators/system_administrators_book.md
@@ -0,0 +1,3 @@
+# ThreeFold System Administrators Manual
+
+This manual covers all practical tutorials for system administrators working on the ThreeFold Grid.
\ No newline at end of file
diff --git a/collections/system_administrators/system_administrators_book_toc.md b/collections/system_administrators/system_administrators_book_toc.md
deleted file mode 100644
index 333106c..0000000
--- a/collections/system_administrators/system_administrators_book_toc.md
+++ /dev/null
@@ -1,93 +0,0 @@
-# ThreeFold System Administrators Manual
-
-This manual covers all practical tutorials for system administrators working on the ThreeFold Grid.
-
- Table of Contents
-
-- [Getting Started](tfgrid3_getstarted.md)
- - [SSH Remote Connection](ssh_guide.md)
- - [SSH with OpenSSH](ssh_openssh.md)
- - [SSH with PuTTY](ssh_putty.md)
- - [SSH with WSL](ssh_wsl.md)
- - [WireGuard Access](ssh_wireguard.md)
- - [Remote Desktop and GUI](remote_desktop_gui.md)
- - [Cockpit: a Web-based Interface for Servers](cockpit_guide.md)
- - [XRDP: an Open-Source Remote Desktop Protocol](xrdp_guide.md)
- - [Apache Guacamole: a Clientless Remote Desktop Gateway](guacamole_guide.md)
-- [Planetary Network](planetarynetwork.md)
-- [TFGrid Services](tf_grid_services_readme.md)
-- [GPU](gpu_toc.md)
- - [GPU Support](gpu.md)
-- [Terraform](terraform_toc.md)
- - [Overview](terraform_readme.md)
- - [Installing Terraform](terraform_install.md)
- - [Terraform Basics](terraform_basics.md)
- - [Full VM Deployment](terraform_full_vm.md)
- - [GPU Support](terraform_gpu_support.md)
- - [Resources](terraform_resources_readme.md)
- - [Using Scheduler](terraform_scheduler.md)
- - [Virtual Machine](terraform_vm.md)
- - [Web Gateway](terraform_vm_gateway.md)
- - [Kubernetes Cluster](terraform_k8s.md)
- - [ZDB](terraform_zdb.md)
- - [Zlogs](terraform_zlogs.md)
- - [Quantum Safe Filesystem](terraform_qsfs.md)
- - [QSFS on Micro VM](terraform_qsfs_on_microvm.md)
- - [QSFS on Full VM](terraform_qsfs_on_full_vm.md)
- - [CapRover](terraform_caprover.md)
- - [Advanced](terraform_advanced_readme.md)
- - [Terraform Provider](terraform_provider.md)
- - [Terraform Provisioners](terraform_provisioners.md)
- - [Mounts](terraform_mounts.md)
- - [Capacity Planning](terraform_capacity_planning.md)
- - [Updates](terraform_updates.md)
- - [SSH Connection with Wireguard](terraform_wireguard_ssh.md)
- - [Set a Wireguard VPN](terraform_wireguard_vpn.md)
- - [Synced MariaDB Databases](terraform_mariadb_synced_databases.md)
- - [Nomad](terraform_nomad.md)
- - [Nextcloud Deployments](terraform_nextcloud_toc.md)
- - [Nextcloud All-in-One Deployment](terraform_nextcloud_aio.md)
- - [Nextcloud Single Deployment](terraform_nextcloud_single.md)
- - [Nextcloud Redundant Deployment](terraform_nextcloud_redundant.md)
- - [Nextcloud 2-Node VPN Deployment](terraform_nextcloud_vpn.md)
-- [Pulumi](pulumi_readme.md)
- - [Introduction to Pulumi](pulumi_intro.md)
- - [Installing Pulumi](pulumi_install.md)
- - [Deployment Examples](pulumi_examples.md)
- - [Deployment Details](pulumi_deployment_details.md)
-- [Mycelium](mycelium_toc.md)
- - [Overview](overview.md)
- - [Installation](installation.md)
- - [Additional Information](information.md)
- - [Message](message.md)
- - [Packet](packet.md)
- - [Data Packet](data_packet.md)
- - [API YAML](api_yaml.md)
-- [Computer and IT Basics](computer_it_basics.md)
- - [CLI and Scripts Basics](cli_scripts_basics.md)
- - [Docker Basics](docker_basics.md)
- - [Git and GitHub Basics](git_github_basics.md)
- - [Firewall Basics](firewall_basics.md)
- - [UFW Basics](ufw_basics.md)
- - [Firewalld Basics](firewalld_basics.md)
- - [File Transfer](file_transfer.md)
- - [Screenshots](screenshots.md)
-- [Advanced](advanced.md)
- - [Token Transfer Keygenerator](token_transfer_keygenerator.md)
- - [Cancel Contracts](cancel_contracts.md)
- - [Contract Bills Reports](contract_bill_report.md)
- - [Listing Free Public IPs](list_public_ips.md)
- - [Cloud Console](cloud_console.md)
- - [Redis](grid3_redis.md)
- - [IPFS](ipfs_toc.md)
- - [IPFS on a Full VM](ipfs_fullvm.md)
- - [IPFS on a Micro VM](ipfs_microvm.md)
- - [MinIO Operator with Helm3](minio_helm3.md)
- - [Hummingbot](hummingbot.md)
- - [AI & ML Workloads](ai_ml_workloads.md)
- - [Ecommerce](ecommerce.md)
- - [WooCommerce](woocommerce.md)
- - [nopCommerce](nopcommerce.md)
- - [Hummingbot](hummingbot.md)
- - [HTTPS with Caddy](https_caddy.md)
- - [Node Status Bot](node_status_bot.md)
\ No newline at end of file
diff --git a/collections/tech/architecture/architecture.md b/collections/tech/architecture/architecture.md
index e7444de..e3e2fca 100644
--- a/collections/tech/architecture/architecture.md
+++ b/collections/tech/architecture/architecture.md
@@ -1,10 +1,15 @@
+
+
## Architecture
-The ThreeFold Grid architecture provides a myriad of cloud possibilities thanks to its interrelated layers.
-
+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.
@@ -15,46 +20,26 @@ A cloud needs hardware/servers to function. Servers of all shapes and sizes can
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.
-## Zero-OS
+## Core Components
-We have build our own operating system called Zero-OS, which was based starting from a Linux Kernel with as purpose to remove all the unnecessary complexities found on contemporary OS's.
+!!wiki.include page:components_links.md
-Zero-OS supports a small number of primitives, and performs low-level functions natively.
+### Web3 & Decentralized AI Compatibility
-It delivers 3 primitive functions:
-
-- storage capacity
-- compute capacity
-- network capacity
+Our Decentralized Cloud Technology the ideal platform for hosting any web3 and AI workloads.
-There is no shell, local nor remote attached to Zero-OS. Given its shell-less nature, the people and organizations, called farmers, that run 3nodes cannot issue any commands nor access its features. In that sense, Zero-OS enables a "zero people" (autonomous) Decentralzied Cloud, meaning hackers cannot get in, while also eliminating human error from the paradigm.
+Our Zero-OS operating system already supports integrated GPUs, ensuring optimal performance for decentralized AI applications.
+> Any workload (web2/3 and AI) can run on on our Decentralized Cloud.
-### 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.
-
-## 3Bots: The Autonomous Layer
-
-
-
-### Smart Contract for IT
-
-The purpose of the smart contract for IT is to create and enable autonomous IT. Autonomous self-driving IT is possible.
-
-Once a smart contract for IT is created, it will be registered in the TFChain Blockchain.
-
-### TFChain
+## TFChain: our Blockchain
This blockchain does the following:
@@ -64,15 +49,3 @@ This blockchain does the following:
- info as required for the Smart Contract for IT
This is the hart of our operational system of our decentralized cloud.
-
-### 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.
-
-### Web3 & Decentralized AI Compatibility
-
-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.
-
-> Any workload (web2/3 and AI) can run on on our Decentralized Cloud.
\ No newline at end of file
diff --git a/collections/tech/architecture/img/architecture_intro.png b/collections/tech/architecture/img/architecture_intro.png
new file mode 100644
index 0000000..134da48
Binary files /dev/null and b/collections/tech/architecture/img/architecture_intro.png differ
diff --git a/collections/tech/architecture/img/zos00.png b/collections/tech/architecture/img/zos00.png
new file mode 100644
index 0000000..ce96ec3
Binary files /dev/null and b/collections/tech/architecture/img/zos00.png differ
diff --git a/collections/tech/architecture/network.md b/collections/tech/architecture/network.md
new file mode 100644
index 0000000..9b0a5c3
--- /dev/null
+++ b/collections/tech/architecture/network.md
@@ -0,0 +1,14 @@
+
+
+
+### 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.
diff --git a/collections/tech/img/.done b/collections/tech/img/.done
index 8719703..e356f79 100644
--- a/collections/tech/img/.done
+++ b/collections/tech/img/.done
@@ -5,3 +5,5 @@ tech_overview.png
tech_overview2.png
web_remade.png
cloud_features.png
+base_layer.png
+scale.png
diff --git a/collections/tech/img/architecture_usage.png b/collections/tech/img/architecture_usage.png
index 464afc2..d3f8e7b 100644
Binary files a/collections/tech/img/architecture_usage.png and b/collections/tech/img/architecture_usage.png differ
diff --git a/collections/tech/img/base_layer.png b/collections/tech/img/base_layer.png
new file mode 100644
index 0000000..090c87b
Binary files /dev/null and b/collections/tech/img/base_layer.png differ
diff --git a/collections/tech/img/pathtoweb4.png b/collections/tech/img/pathtoweb4.png
new file mode 100644
index 0000000..d233d62
Binary files /dev/null and b/collections/tech/img/pathtoweb4.png differ
diff --git a/collections/tech/img/scale.png b/collections/tech/img/scale.png
new file mode 100644
index 0000000..312549f
Binary files /dev/null and b/collections/tech/img/scale.png differ
diff --git a/collections/tech/innovations/components_links.md b/collections/tech/innovations/components_links.md
new file mode 100644
index 0000000..f2395cb
--- /dev/null
+++ b/collections/tech/innovations/components_links.md
@@ -0,0 +1,12 @@
+Compute
+ - [Zero-OS: a minimalistic and more efficient server operating system](zos_innovation)
+ - [Zero-Image: a new way to deal with OS Images](flist_innovation.md)
+
+Network
+ - [Mycelium: a new network layer for the Internet](mycelium_innovation.md)
+ - [Network Wall: a secure way to connect your apps to Internet](network_wall_innovation.md)
+
+Storage
+ - [Quantum Safe Storage: storage which cannot get lost nor corrupted](zstor_innovation.md)
+ - [Quantum Safe Filesystem: host any storage interface e.g. IPFS](qsfs_innovation.md)
+ - [FungiStor: Content Delivery everwhere in the world](fungistor_innovation.md)
diff --git a/collections/tech/innovations/compute/compute_inno.md b/collections/tech/innovations/compute/compute_inno.md
new file mode 100644
index 0000000..3441edb
--- /dev/null
+++ b/collections/tech/innovations/compute/compute_inno.md
@@ -0,0 +1,60 @@
+
+# Compute
+
+| | Threefold Compute Layer | Default |
+|----------------|--------------------------------------------------------------------------------|------------------------------------------------------------------|
+| Management | Full P2P, done by 3bot Agents, blockchain IT contract | Centralized e.g. Kubernetes, ... |
+| OS Deploy | Stateless, there are no files copied on local HDD/SSD. | Deploy image or execute installer on a physical server |
+| OS Upgrade | Seamless, rolling upgrades, 100% modular and pre-deterministic, decentralized | Difficult and error prone + vulnerable from security perspective |
+| Tamperproof | If file gets modified Zero-OS will not boot the file. | No, man in middle is possible. |
+| Scalability | To the world | Expensive and depending on lots of capital |
+| Security | A lot of effort went into the capability to deploy for high security usecases. | Very hard to deploy securely, and expensive |
+| Green | For certain workloads we can safe upto 10x on power usage | Super power hungry. |
+| Liquid Cooling | Easy to do because of autonomous behavior no need to replace HW. | Hard to do, how to do maintenance. |
+| Sovereign | Yes | No |
+| Complexity | Anyone can do it, we made it to allow everyone to be a provider. | Real experts needed. |
+
+> We do not compare our system with those that claim to be full cloud solutions but merely deploy containers using other management systems and optionally connect to a blockchain for billing purposes. Nor do we compare with marketplace systems that simply act as frontends for other systems. We believe these systems, while visually impressive, lack substantial technological foundations and cannot serve as a fundamental base layer for others.
+
+## Zero-OS
+
+
+
+ThreeFold has developed its own operating system, Zero-OS, which is based on the Linux Kernel. The purpose of Zero-OS is to strip away the unnecessary complexities commonly found in contemporary operating systems.
+
+**Key Features of Zero-OS:**
+
+Zero-OS is designed with minimalism in mind, supporting only a few fundamental primitives that handle essential low-level functions:
+
+1. **Storage Capacity**
+2. **Compute Capacity**
+3. **Network Capacity**
+
+**Security and Simplicity:**
+
+Zero-OS provides a Autonomous Decentralized Cloud.
+
+This not only blocks hacker access but also eliminates human error, enhancing both security and reliability.
+
+### Deployment by IT contract
+
+Secure Reproducable Verified Authenticated
+
+
+
+The purpose of the smart contract for IT is to create and enable autonomous IT. Autonomous self-driving IT is possible.
+
+Once a smart contract for IT is created, it will be registered in the TFChain Blockchain.
+
+
+
+## Compatible with the world
+
+
+
+
+## 3Bots: The Autonomous Layer
+
+
+
+
diff --git a/collections/tech/innovations/compute/flist_innovation.md b/collections/tech/innovations/compute/flist_innovation.md
new file mode 100644
index 0000000..55d6e30
--- /dev/null
+++ b/collections/tech/innovations/compute/flist_innovation.md
@@ -0,0 +1,5 @@
+
+## Zero-Images: A New Way Of Dealing With OS Images
+
+!!wiki.include page:flist_innovation_short
+
diff --git a/collections/tech/innovations/flist_innovation_short.md b/collections/tech/innovations/compute/flist_innovation_short.md
similarity index 100%
rename from collections/tech/innovations/flist_innovation_short.md
rename to collections/tech/innovations/compute/flist_innovation_short.md
diff --git a/collections/tech/architecture/img/autonous3bots.png b/collections/tech/innovations/compute/img/autonous3bots.png
similarity index 100%
rename from collections/tech/architecture/img/autonous3bots.png
rename to collections/tech/innovations/compute/img/autonous3bots.png
diff --git a/collections/tech/innovations/compute/img/compatible.png b/collections/tech/innovations/compute/img/compatible.png
new file mode 100644
index 0000000..e2a6c12
Binary files /dev/null and b/collections/tech/innovations/compute/img/compatible.png differ
diff --git a/collections/tech/innovations/compute/img/itcontract.png b/collections/tech/innovations/compute/img/itcontract.png
new file mode 100644
index 0000000..820e13d
Binary files /dev/null and b/collections/tech/innovations/compute/img/itcontract.png differ
diff --git a/collections/tech/innovations/compute/img/itcontract2.png b/collections/tech/innovations/compute/img/itcontract2.png
new file mode 100644
index 0000000..7114507
Binary files /dev/null and b/collections/tech/innovations/compute/img/itcontract2.png differ
diff --git a/collections/tech/innovations/zos_innovation.md b/collections/tech/innovations/compute/zos_innovation.md
similarity index 100%
rename from collections/tech/innovations/zos_innovation.md
rename to collections/tech/innovations/compute/zos_innovation.md
diff --git a/collections/tech/innovations/zos_innovation_short.md b/collections/tech/innovations/compute/zos_innovation_short.md
similarity index 100%
rename from collections/tech/innovations/zos_innovation_short.md
rename to collections/tech/innovations/compute/zos_innovation_short.md
diff --git a/collections/tech/innovations/flist_innovation.md b/collections/tech/innovations/flist_innovation.md
deleted file mode 100644
index 805546b..0000000
--- a/collections/tech/innovations/flist_innovation.md
+++ /dev/null
@@ -1,4 +0,0 @@
-
-## FList: A New Way Of Dealing With OS Images
-
-!!wiki.include page:flist_innovation_short
\ No newline at end of file
diff --git a/collections/tech/innovations/key_innovations.md b/collections/tech/innovations/key_innovations.md
index f639982..1033d29 100644
--- a/collections/tech/innovations/key_innovations.md
+++ b/collections/tech/innovations/key_innovations.md
@@ -19,13 +19,10 @@
!!wiki.include page:zstor_innovation_short
-
## Quantum Safe File System
-
!!wiki.include page:qsfs_innovation_short
-
## FungiStor
!!wiki.include page:'fungistor_innovation_short'
diff --git a/collections/tech/innovations/key_innovations_overview.md b/collections/tech/innovations/key_innovations_overview.md
index 5ee8c07..71320a9 100644
--- a/collections/tech/innovations/key_innovations_overview.md
+++ b/collections/tech/innovations/key_innovations_overview.md
@@ -1,15 +1,7 @@
- Key Innovations
-
-Throughout the years, we've built innovative products that are now part of a whole ecosystem.
-Table of Contents
+# Key Innovations
+
+!!wiki.include page:components_links.md
-- [Mycelium: a new network layer for the internet](mycelium_innovation.md)
-- [Zero-OS: a minimalistic and more efficient server operating system](zos_innovation)
-- [Quantum Safe Storage](zstor_innovation.md)
-- [Quantum Safe Filesystem](qsfs_innovation.md)
-- [FList: a new way to deal with OS Images](flist_innovation.md)
-- [FungiStor](fungistor_innovation.md)
-- [Network Wall](network_wall_innovation.md)
\ No newline at end of file
diff --git a/collections/tech/innovations/mycelium_innovation.md b/collections/tech/innovations/mycelium_innovation.md
deleted file mode 100644
index 0f4cc37..0000000
--- a/collections/tech/innovations/mycelium_innovation.md
+++ /dev/null
@@ -1,4 +0,0 @@
-
-## Mycelium: A New Network Layer for the Internet
-
-!!wiki.include page:mycelium_innovation_short.md
\ No newline at end of file
diff --git a/collections/tech/innovations/network/img/.done b/collections/tech/innovations/network/img/.done
new file mode 100644
index 0000000..4a7a2ef
--- /dev/null
+++ b/collections/tech/innovations/network/img/.done
@@ -0,0 +1 @@
+mycelium00.png
diff --git a/collections/tech/innovations/network/img/mycelium00.png b/collections/tech/innovations/network/img/mycelium00.png
new file mode 100644
index 0000000..96cfa1b
Binary files /dev/null and b/collections/tech/innovations/network/img/mycelium00.png differ
diff --git a/collections/tech/innovations/network/img/network_wall.png b/collections/tech/innovations/network/img/network_wall.png
new file mode 100644
index 0000000..6baa448
Binary files /dev/null and b/collections/tech/innovations/network/img/network_wall.png differ
diff --git a/collections/tech/innovations/network/mycelium_innovation.md b/collections/tech/innovations/network/mycelium_innovation.md
new file mode 100644
index 0000000..01d4302
--- /dev/null
+++ b/collections/tech/innovations/network/mycelium_innovation.md
@@ -0,0 +1,7 @@
+
+
+
+
+## Mycelium: A New Network Layer for the Internet
+
+!!wiki.include page:mycelium_innovation_short.md
\ No newline at end of file
diff --git a/collections/tech/innovations/mycelium_innovation_short.md b/collections/tech/innovations/network/mycelium_innovation_short.md
similarity index 100%
rename from collections/tech/innovations/mycelium_innovation_short.md
rename to collections/tech/innovations/network/mycelium_innovation_short.md
diff --git a/collections/tech/innovations/network/network_inno.md b/collections/tech/innovations/network/network_inno.md
new file mode 100644
index 0000000..fcc0d57
--- /dev/null
+++ b/collections/tech/innovations/network/network_inno.md
@@ -0,0 +1,16 @@
+# Network
+
+| | ThreeFold Network Layer | Other Overlay Network Technologies (like VPN) |
+|-----------------------------|-----------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------|
+| Management | Full P2P, done by 3bot Agents, blockchain IT contract | Centralized leading to security issues |
+| Locality | Find shortest path on latency and quality, this allows traffic to stay sovereign. | NO, based on centralized control mechanisms or inefficient algorithms that route traffic indiscriminately across the globe. |
+| Encryption | End2End ecryption, unique for every relation, linked to private key | Normally based on key exchange, or pre-shared keys. |
+| Post Quantum | Possible (ask us) | No |
+| Scalability | Our aim is to be planetary scalable, but we need more exposure. | Bad |
+| Compatibility | We aim to support mobile, desktop, IOT, ... | Depends, often not |
+| Backdoors | NO, all is based on opensource | Often, yes, unfortunately. |
+| Performance | Quite good, 1 gbit / sec can be achieved on std node (which is high for overlay) | Often slow. |
+| Security Model | Whitelist model | Blacklist model, list who is bad e.g. firewalls |
+| Fully integrated in compute | Yes | Lots of different solutions |
+
+
diff --git a/collections/tech/innovations/network_wall_innovation.md b/collections/tech/innovations/network/network_wall_innovation.md
similarity index 69%
rename from collections/tech/innovations/network_wall_innovation.md
rename to collections/tech/innovations/network/network_wall_innovation.md
index e782b2c..d779010 100644
--- a/collections/tech/innovations/network_wall_innovation.md
+++ b/collections/tech/innovations/network/network_wall_innovation.md
@@ -1,8 +1,10 @@
+
+
+
## Network Wall
The Network Wall offers 100% separation between where compute workloads are and where services are exposed, proving an extremely high level of security.
-
!!wiki.include page:network_wall_innovation_short
\ No newline at end of file
diff --git a/collections/tech/innovations/network_wall_innovation_short.md b/collections/tech/innovations/network/network_wall_innovation_short.md
similarity index 100%
rename from collections/tech/innovations/network_wall_innovation_short.md
rename to collections/tech/innovations/network/network_wall_innovation_short.md
diff --git a/collections/tech/innovations/network_wall.png b/collections/tech/innovations/network_wall.png
deleted file mode 100644
index 11b3b2c..0000000
Binary files a/collections/tech/innovations/network_wall.png and /dev/null differ
diff --git a/collections/tech/innovations/fungistor_innovation.md b/collections/tech/innovations/storage/fungistor_innovation.md
similarity index 100%
rename from collections/tech/innovations/fungistor_innovation.md
rename to collections/tech/innovations/storage/fungistor_innovation.md
diff --git a/collections/tech/innovations/fungistor_innovation_short.md b/collections/tech/innovations/storage/fungistor_innovation_short.md
similarity index 100%
rename from collections/tech/innovations/fungistor_innovation_short.md
rename to collections/tech/innovations/storage/fungistor_innovation_short.md
diff --git a/collections/tech/innovations/fungistor_innovation_short0.md b/collections/tech/innovations/storage/fungistor_innovation_short0.md
similarity index 100%
rename from collections/tech/innovations/fungistor_innovation_short0.md
rename to collections/tech/innovations/storage/fungistor_innovation_short0.md
diff --git a/collections/tech/innovations/storage/img/.done b/collections/tech/innovations/storage/img/.done
new file mode 100644
index 0000000..a76e5eb
--- /dev/null
+++ b/collections/tech/innovations/storage/img/.done
@@ -0,0 +1 @@
+storage_inno.png
diff --git a/collections/tech/innovations/storage/img/storage_inno.png b/collections/tech/innovations/storage/img/storage_inno.png
new file mode 100644
index 0000000..01a0608
Binary files /dev/null and b/collections/tech/innovations/storage/img/storage_inno.png differ
diff --git a/collections/tech/innovations/qsfs_innovation.md b/collections/tech/innovations/storage/qsfs_innovation.md
similarity index 100%
rename from collections/tech/innovations/qsfs_innovation.md
rename to collections/tech/innovations/storage/qsfs_innovation.md
diff --git a/collections/tech/innovations/qsfs_innovation_short.md b/collections/tech/innovations/storage/qsfs_innovation_short.md
similarity index 96%
rename from collections/tech/innovations/qsfs_innovation_short.md
rename to collections/tech/innovations/storage/qsfs_innovation_short.md
index fe4d9f7..48189d2 100644
--- a/collections/tech/innovations/qsfs_innovation_short.md
+++ b/collections/tech/innovations/storage/qsfs_innovation_short.md
@@ -15,8 +15,6 @@ Metadata redundancy is included. While not consistently synchronized in real-tim
This filesystem can be mounted under various storage-aware applications, such as backup servers, file servers, or S3 servers, enhancing versatility.
-
-
### Benefits
- Inherits the advantages of Zero-Stor, including enhanced data security, efficiency, and scalability.
diff --git a/collections/tech/innovations/storage/storage_inno.md b/collections/tech/innovations/storage/storage_inno.md
new file mode 100644
index 0000000..04d2d6d
--- /dev/null
+++ b/collections/tech/innovations/storage/storage_inno.md
@@ -0,0 +1,17 @@
+
+
+# Storage
+
+
+| | ThreeFold Network Layer | Overlay Storage Systems / Networks |
+|-----------------------------|------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------|
+| 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 |
+| 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. |
+| Compatibility | Yes thanks to filesystem approach | Depends, often not |
+| Backdoors | NO, all is based on opensource | ? |
+| 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% |
+| Fully integrated in compute | Yes | Lots of different solutions |
\ No newline at end of file
diff --git a/collections/tech/internet/img/3layers.png b/collections/tech/internet/img/3layers.png
new file mode 100644
index 0000000..b4ab41c
Binary files /dev/null and b/collections/tech/internet/img/3layers.png differ
diff --git a/collections/tech/internet/internet_3layers.png b/collections/tech/internet/internet_3layers.png
deleted file mode 100644
index c3813e6..0000000
Binary files a/collections/tech/internet/internet_3layers.png and /dev/null differ
diff --git a/collections/tech/internet/internet_today.md b/collections/tech/internet/internet_today.md
index dd93838..89654e2 100644
--- a/collections/tech/internet/internet_today.md
+++ b/collections/tech/internet/internet_today.md
@@ -1,8 +1,8 @@
-# The Internet Is Broken
+# Rethinking the Internet
**The Three Layers Of The Internet**
-
+
The Internet is made up of 3 layers:
@@ -12,6 +12,10 @@ The Internet is made up of 3 layers:
3. Applications: currently applications are hosted in huge data centers using the compute and storage as provided. This system is too centralized and therefore very vulnerable.
+ThreeFold is providing solutions for the first 2 layers and allows everyone else to build on top.
+
+**Current Challenges**
+
Digital information mainly travels over large fiber backbone links as pictured here.
@@ -22,9 +26,28 @@ This leads to very inneficient behavior, slower performance, less reliability an
-Another important aspect is the lack of autonomy and sovereignty within this Internet. We have become the products. All of our data is hosted in large data centers owned by a few large corporations.
+**Issues with Autonomy and Sovereignty**
+
+Our current internet model compromises autonomy and sovereignty. Most data is stored in large data centers controlled by a few major corporations, effectively turning users into products.
-We also exist many times on the Internet across many applications and each time a full infrastructure has been built to deliver the applications from. This system is unsustainable and inefficient.
+Moreover, the internet is replicated many times across various applications, each requiring its own full infrastructure. This approach is unsustainable and inefficient.
+
+## ThreeFold wants to create a new base layer
+
+A Base layer who doesn't have these issues.
+
+ThreeFold resolves
+
+- reliability for data, data can never be corrupted nor lost
+- reliability for network, connectivity should always be possible
+- sovereignity
+- scalability
+- security
+- locality
+- cost
+- management (easier to scale)
+
+
diff --git a/collections/tech/internet/t.md b/collections/tech/internet/t.md
new file mode 100644
index 0000000..2bdfd22
--- /dev/null
+++ b/collections/tech/internet/t.md
@@ -0,0 +1,35 @@
+# Rethinking the Internet
+
+**Understanding the Three Layers of the Internet**
+
+
+
+The Internet is made of 3 layers:
+
+1. **Compute & Storage:** This layer houses applications and is predominantly centralized, operating from vast data centers.
+
+2. **Network:** The network layer facilitates the movement of information, whether it's wireless, via cables like fiber, or through satellite links. Today, information often travels long distances, with a few companies controlling over 80% of the internet’s network capacity.
+
+3. **Applications:** These are hosted in large data centers, relying on the centralized compute and storage layers. This centralization makes the system vulnerable.
+
+**Current Challenges**
+
+Digital information primarily flows through extensive fiber backbone networks, as shown here:
+
+
+
+The internet’s design causes inefficiencies, such as when two people in Zanzibar use a service like Zoom. Their data travels all the way to European data centers where Zoom's servers are hosted and back, leading to slow performance, decreased reliability, and increased costs.
+
+
+
+**Issues with Autonomy and Sovereignty**
+
+Our current internet model compromises autonomy and sovereignty. Most data is stored in large data centers controlled by a few major corporations, effectively turning users into products.
+
+
+
+Moreover, the internet is replicated many times across various applications, each requiring its own full infrastructure. This approach is unsustainable and inefficient.
+
+---
+
+This retains the original structure and links, ensuring that the information is clear and the visual aids are effectively utilized.
\ No newline at end of file
diff --git a/collections/tech/natural_progression/how_does_it_work.md b/collections/tech/natural_progression/how_does_it_work.md
index 7b6c9dd..bc691b8 100644
--- a/collections/tech/natural_progression/how_does_it_work.md
+++ b/collections/tech/natural_progression/how_does_it_work.md
@@ -1,24 +1,13 @@
+
+
# The Internet’s Natural Progression
-The Internet was always meant to be a peer-to-peer infrastructure. As large companies became profit and data centric, centralization quickly became the norm.
+The Internet was always meant to be a peer-to-peer infrastructure.
+
+As large companies became profit and data centric, centralization quickly became the norm.
***We have a vision of the Internet which is much more close to how the Internet was intended to be.***
-
-
-
-We believe in a world where every person is the center of their digital life. In this new Internet each person has their own digital avatar which we call a ***Hero***.
-
-The technical component which makes Hero possible is a compoment called 3Bot. This 3Bot server. only owned and managed by you, lives on top of the cecentralized cloud.
-
-All the 3Bots communicate to each other over the shortest possible path. This path is end-to-end encrypted.
-
-
-
-The underlying network of capacity is the decentralized cloud which is like the basic IT energy which makes all of this possible.
-
-The cecentralized cloud is the result of more than 10 years of development and it is now active on more than 2000 nodes.
-
## Requirements For A New Internet
@@ -37,4 +26,23 @@ The cecentralized cloud is the result of more than 10 years of development and i
- Working no matter what happens with existing network, route around issues
- Local sensitive (chose shortest path)
- End2End Encrypted
- - Capable to really know where information goes to or comes from (authenticity)
\ No newline at end of file
+ - Capable to really know where information goes to or comes from (authenticity)
+
+## Natural Progression
+
+
+
+We envision a world where every person is at the center of their digital life. In this new Internet, each person has their own digital avatar, which we call a ***Hero***.
+
+The technical backbone enabling the Hero is a component known as the 3Bot. This server, owned and managed by you, operates on our decentralized cloud infrastructure.
+
+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 in relation to TFGrid
+
+
+
+The underlying network of capacity is the decentralized cloud which is like the basic IT energy which makes all of this possible.
+
+The cecentralized cloud is the result of more than 20 years of development and it is now active on more than 2000 nodes.
+
diff --git a/collections/tech/overview.md b/collections/tech/overview.md
new file mode 100644
index 0000000..309e956
--- /dev/null
+++ b/collections/tech/overview.md
@@ -0,0 +1,47 @@
+
+
+For over 20 years, through more than seven startups, ThreeFold has been developing an infrastructure base layer of software. This platform is ideal for any Decentralized Physical Infrastructure Network (DePIN) or Web 2/3 project to build upon.
+
+This robust platform serves as a truly decentralized infrastructure base layer, designed to be hosted by everyone, for everyone.
+
+## ThreeFold: The Base Layer for DePin and Web 2 and 3
+
+
+
+ThreeFold has developed a scalable, reliable, and efficient decentralized infrastructure base layer.
+This serves as the foundational base for any Decentralized Physical Infrastructure Network (DePin) or Web 3 application.
+
+## Anyone can be a cloud service provider
+
+
+
+**Getting started is easy:** Just get a ThreeFold node and connect it to the Internet.
+
+Around the world, thousands of entities, from individuals to companies, have become ThreeFold farmers. They connect their computers, known as nodes, to the Internet and install our software. This allows them to provide GPU, compute, storage, and network capacity to the ThreeFold Grid.
+
+Farmers have two options: they can either buy a ready-made node from our partners or build their own using our detailed DIY (Do It Yourself) guides.
+
+
+## Usable by Everyone
+
+
+
+Our platform is designed for everyone, whether you are a developer, system administrator, or IT expert.
+
+## Open Source Technology
+
+All of our technology is open source and build by our tech company called TF9 and used to build the ThreeFold Gridt. For more information, visit the [ThreeFold Website](https://www.threefold.io).
+
+## Bridging the Web2, Web3, and Blockchain Worlds
+
+ThreeFold acts as the essential layer connecting traditional web technologies with the new, decentralized Web3 and blockchain worlds.
+
+
+
+## Scalability and Growth
+
+Our system is designed to scale effortlessly, meeting the needs of a rapidly evolving digital landscape.
+
+
+
+
diff --git a/collections/tech/roadmap/hero_roadmap.md b/collections/tech/roadmap/hero_roadmap.md
new file mode 100644
index 0000000..975734c
--- /dev/null
+++ b/collections/tech/roadmap/hero_roadmap.md
@@ -0,0 +1,22 @@
+## High Level Roadmap HERO Stack
+
+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.
+
+This stack allows everyone to deploy scalable web 2/3/4 apps on top of the TFGrid.
+
+
+| | Roadmap | Timing |
+| -------------------------------- | -------------------------------------------------------------------------------------------------------------------- | ------ |
+| Hero Publisher | Publish websites, e-books, ... on top of TFGrid | Q2 24 |
+| Hero CI = Continuous Integration | Easier to use Continuous Integration / Development, very powerfull, with multi node support | Q3 24 |
+| Hero Play | Integrate declarative automation and configuration management as part of wiki approach in hero Publisher | Q3 24 |
+| Hero Git | Alternative to centralized Github (based on Gitea), fully integrated on top of TFGrid | Q3 24 |
+| Hero DB | Flexible ultra redundant database stor with indexing, queries, stored procesudes, super scalable replication | Q3 24 |
+| Hero OSIS | Object Storage and Index system integrates with hero Git, all data on git based backend | Q3 24 |
+| Hero WEB | Web framework (with co-routines) using Vlang, deployable globally on TFGrid, integrated with Mycelium Net and Names. | Q3 24 |
+| Hero Monitor | Monitor all your different components on redundant monitoring stack | Q3 24 |
+| Hero Happs | Hero natively supports Holochain HAPPS | Q1 25 |
+| Hero Actors | Hero can serve actors which respond and act on OpenRPC calls ideal as backend for web or other apps. | Q1 25 |
+| Hero Web 3 Gateway | Hero aims to have native support for chosen Web3 partner solutions | Q1 25 |
+
+All of above is fully integrated with Mycelium Network and the TF Grid.
diff --git a/collections/tech/roadmap/tfgrid_roadmap.md b/collections/tech/roadmap/tfgrid_roadmap.md
new file mode 100644
index 0000000..11cbf15
--- /dev/null
+++ b/collections/tech/roadmap/tfgrid_roadmap.md
@@ -0,0 +1,56 @@
+## High Level Roadmap
+
+### Status Today
+
+The core offering is functioning effectively, maintained through a community-driven, best-effort approach. Currently,
+there are no Service Level Agreements (SLAs) in place, and there should be increased visibility for users regarding their expectations for uptime,
+performance, and other service related requirements.
+
+The uptime and stability of Zero-OS are very good.
+
+Additionally, hardware compatibility is excellent, with most machines now supported out of the box.
+
+
+| | Status today | SDK/API | Web UI |
+| ----------------------- | ------------------------------------------------------------------------------------------------------------ | ------- | ------ |
+| Zero-OS | Used for management of +30,000 logical CPU cores | yes | yes |
+| Zero-Images (flists) | Basis for Zero-OS modules as well as replaces images for VM's ... | yes | yes |
+| Zero-Images from Docker | convert docker through our Hub | yes | yes |
+| Zero-Images Hub | ThreeFold is hosting some as well as everyone can install their own Hub | yes | yes |
+| Mycelium Core | Integrated in Zero-OS for VM's as well s ZDB and monitoring | yes | yes |
+| Mycelium Message Bus | Can be used by any developer for their own usecases | NA | NA |
+| Quantum Safe Storage | Usable for experts only, is reliably working for +6 years, +100 MB/sec per stream | yes | no |
+| Quantum Safe Filesystem | QSFS= usable for experts, is a fuse based filesystem on top of the QSS Core | yes | no |
+| Zero-OS Kubernetes | Working very well, Integrated in ZOS, uses our overlay networks based on Wireguard, can use QSFS underneith. | yes | yes |
+| Zero-OS VM's | The base of our service portfolio, missing is better service level management | yes | yes |
+| Zero-OS Monitoring | Working well | yes | yes |
+| Zero-OS VM Monitoring | Working well, can be retrieved through SDK | yes | yes |
+| Zero-OS Web Gateway | Working well, but documentation not good enough, and not enough of them deployed | yes | yes |
+| Zero-Boot | There are multiple ways active on how to deploy Zero-OS all are stateless and capable for full secure boot | | |
+| | | | |
+
+
+### Planned new features:
+
+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.
+
+| | Roadmap | Timing |
+| ----------------------------------- | ---------------------------------------------------------------- | ------ |
+| Zero-OS v4 (our next major release) | v4, no more TFChain, mutual credit, marketplace | Q1 25 |
+| FungiStor | A revolutionary different way how to deliver content | Q1 25 |
+| Zero-Images on FungiStor | Can be stored on FungiStor | Q1 25 |
+| Zero-Images from Docker | CI/CD integration (See below) | Q4 24 |
+| Zero-Images Hub | CI/CD integration (See below)
no more need for separate Hub | Q4 24 |
+| Mycelium Core | Just more hardening and testing | Q4 24 |
+| Mycelium Message Bus | Replace our current RMB, all our own RPC over Mycelium | Q4 24 |
+| Quantum Safe Storage | Integration in UI, better documentation | Q4 24 |
+| Quantum Safe Filesystem | Integration in UI, better documentation | Q4 24 |
+| Zero-OS Kubernetes | No changes planned | |
+| Zero-OS VM's | Integration Hero CI , use cloud slices to manage | Q1 25 |
+| Zero-OS Monitoring | More docu and easier API | Q1 25 |
+| Zero-OS Web Gateway | Need more deployed, better integration with new Mycelium | Q4 24 |
+| Zero-Boot | No changes planned | |
+| Mycelium Names | in v4, name services | Q1 25 |
+| Zero-OS Cloud,Storage,AI Slices | as part of marketplace for v4, flexible billing mutual credit | Q1 25 |
+| | | |
diff --git a/collections/tech/technology.md b/collections/tech/technology.md
deleted file mode 100644
index d29aac7..0000000
--- a/collections/tech/technology.md
+++ /dev/null
@@ -1,28 +0,0 @@
-
-# ThreeFold Grid Technology
-
-ThreeFold has developed a highly efficient infrastructure layer for a new Internet.
-
-Providing Internet & cloud capacity is as easy as getting a node and connecting it to the Internet.
-
-
-
-A lot of capacity has been deployed in the world, hundreds of ThreeFold farmers acquired a computer and connected it to the Internet, as such they use our operating system to provide Internet capacity to the world. Farmers can buy pre-built node or build their own via our DIY guides.
-
-There are multiple ways in which people can interact with our platform, as a developer, a sysadmin, IT expert, etc.
-
-
-
-All technology is developed by ThreeFold and is opensource, this technology is being used for the ThreeFold grid (see the [ThreeFold Website](https://www.threefold.io)) which is the deployment of a new Internet which is green, safe and owned by all of us.
-
-This document explains how ThreeFold is the missing layer for the full web2, web3 and blockchain world.
-
-This leads to a system which is highly scalable.
-
-
-
-
-
-
-
-
diff --git a/collections/tech/zos/benefits/deterministic_deployment.md b/collections/tech/zos/benefits/zero_chance.md
similarity index 96%
rename from collections/tech/zos/benefits/deterministic_deployment.md
rename to collections/tech/zos/benefits/zero_chance.md
index 0926675..63920e1 100644
--- a/collections/tech/zos/benefits/deterministic_deployment.md
+++ b/collections/tech/zos/benefits/zero_chance.md
@@ -1,5 +1,5 @@
-## Deterministic Deployment
+## Zero-Chance = Deterministic Deployment
@@ -16,10 +16,6 @@ Metadata is exposed. The system sees the full tree of the image, but data itself
It is a static agreement between farmer and user about deployment of an IT workload
- no dynamic behavior for deployment at runtime
- no process can start unless the files are 100% described on flist level
-
-
-
-
### There are multiple ways to create an flist:
diff --git a/collections/tech/zos/benefits/zos_protect.md b/collections/tech/zos/benefits/zos_zero_tech.md
similarity index 99%
rename from collections/tech/zos/benefits/zos_protect.md
rename to collections/tech/zos/benefits/zos_zero_tech.md
index 11d7948..20700bd 100644
--- a/collections/tech/zos/benefits/zos_protect.md
+++ b/collections/tech/zos/benefits/zos_zero_tech.md
@@ -1,4 +1,4 @@
-# ZOS Protect
+# Zero-Tech
- The operating system of the 3node (Zero-OS) is made to exist in environments without the presence of technical knowhow. 3nodes are made to exist everywhere where network meet a power socket. The OS does not have a login shell and does not allow people to log in with physical access to a keyboard and screen nor does it allows logins over the network. There is no way the 3node accepts user initiated login attempts.
- For certified capacity a group of known strategic vendors are able to lock the [BIOS](https://en.wikipedia.org/wiki/BIOS) of their server range and make sure no-one but them can unlock and change features present in the BIOS. Some vendors have an even higher degree of security and can store private keys in chips in side the computer to provider unique identification based on private keys or have mechanisms to check wether the server has been opened / tampered with in the transportation from the factory / vendor to the Farmer. All of this leads to maximum protection on the hardware level.
diff --git a/docs_projectinca/README.md b/docs_projectinca/README.md
index 4bc2272..cfa222a 100644
--- a/docs_projectinca/README.md
+++ b/docs_projectinca/README.md
@@ -1,103 +1,103 @@
- Project INCA Docs
-
-Table of Contents
-
-- [Introduction](#introduction)
-- [Prerequisites](#prerequisites)
- - [Install the prerequisites on Ubuntu](#install-the-prerequisites-on-ubuntu)
- - [Install the prerequisites on MAC or Linux with Brew](#install-the-prerequisites-on-mac-or-linux-with-brew)
- - [Check if the Prerequisites Are Installed](#check-if-the-prerequisites-are-installed)
-- [Clone the Repository](#clone-the-repository)
-- [Preview the Website](#preview-the-website)
-- [License](#license)
-- [References](#references)
-- [Contribute](#contribute)
-
----
-
-## Introduction
-
-This subrepository contains the code to deploy the Project INCA Docs website, a project by [ThreeFold](https://threefold.io).
-
-## Prerequisites
-
-You need [npm](https://www.npmjs.com/) to run this website.
-
-To clone the repository, you need `git`.
-
-To use the Makefile for quick deployment, you need `make`
-
-### Install the prerequisites on Ubuntu
-```
-sudo apt update
-sudo apt install nodejs
-sudo apt install git
-sudo apt install make
-```
-
-### Install the prerequisites on MAC or Linux with Brew
-
-- [Install Brew](https://brew.sh/)
- ```
- /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
- ```
-- Install the prerequisites
- ```
- brew install node
- brew install git
- brew install make
- ```
-
-### Check if the Prerequisites Are Installed
-
-```
-npm --version
-git version
-make --version
-```
-
-## Clone the Repository
-
-
-```
-git clone https://git.ourworld.tf/tfgrid/info_tfgrid
-cd info_tfgrid/docs_projectinca
-```
-
-For more information, read the original [AstroWind docs](./docs_starlight/starlight_README.md).
-
-## Preview the Website
-
-You can preview the website with those two lines.
-
-```
-npm install
-npm run dev
-```
-
-The equivalent can be achieved using the Makefile:
-
-```
-make run
-```
-
-## License
-
-**INCA Docs** is licensed under the Apache 2.0 license — see the [LICENSE](../LICENSE.md) file for details.
-
-## References
-
-This Project INCA Docs website is based on the amazing [AstroWind Starlight repo](https://github.com/withastro/starlight).
-
-We changed the license from MIT to Apache 2.0 to suit this specific project.
-
-## Contribute
-
-To contribute to this repository:
-
-- Make a new branch with `development_` as a prefix (e.g. `development_update`)
-- Make changes locally on your code editor
-- Push changes to the new branch
-- Make a pull request to `development` branch
-
+ Project INCA Docs
+
+Table of Contents
+
+- [Introduction](#introduction)
+- [Prerequisites](#prerequisites)
+ - [Install the prerequisites on Ubuntu](#install-the-prerequisites-on-ubuntu)
+ - [Install the prerequisites on MAC or Linux with Brew](#install-the-prerequisites-on-mac-or-linux-with-brew)
+ - [Check if the Prerequisites Are Installed](#check-if-the-prerequisites-are-installed)
+- [Clone the Repository](#clone-the-repository)
+- [Preview the Website](#preview-the-website)
+- [License](#license)
+- [References](#references)
+- [Contribute](#contribute)
+
+---
+
+## Introduction
+
+This subrepository contains the code to deploy the Project INCA Docs website, a project by [ThreeFold](https://threefold.io).
+
+## Prerequisites
+
+You need [npm](https://www.npmjs.com/) to run this website.
+
+To clone the repository, you need `git`.
+
+To use the Makefile for quick deployment, you need `make`
+
+### Install the prerequisites on Ubuntu
+```
+sudo apt update
+sudo apt install nodejs
+sudo apt install git
+sudo apt install make
+```
+
+### Install the prerequisites on MAC or Linux with Brew
+
+- [Install Brew](https://brew.sh/)
+ ```
+ /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
+ ```
+- Install the prerequisites
+ ```
+ brew install node
+ brew install git
+ brew install make
+ ```
+
+### Check if the Prerequisites Are Installed
+
+```
+npm --version
+git version
+make --version
+```
+
+## Clone the Repository
+
+
+```
+git clone https://git.ourworld.tf/tfgrid/info_tfgrid
+cd info_tfgrid/docs_projectinca
+```
+
+For more information, read the original [AstroWind docs](./docs_starlight/starlight_README.md).
+
+## Preview the Website
+
+You can preview the website with those two lines.
+
+```
+npm install
+npm run dev
+```
+
+The equivalent can be achieved using the Makefile:
+
+```
+make run
+```
+
+## License
+
+**INCA Docs** is licensed under the Apache 2.0 license — see the [LICENSE](../LICENSE) file for details.
+
+## References
+
+This Project INCA Docs website is based on the amazing [AstroWind Starlight repo](https://github.com/withastro/starlight).
+
+We changed the license from MIT to Apache 2.0 to suit this specific project.
+
+## Contribute
+
+To contribute to this repository:
+
+- Make a new branch with `development_` as a prefix (e.g. `development_update`)
+- Make changes locally on your code editor
+- Push changes to the new branch
+- Make a pull request to `development` branch
+
The code owners will merge `development` branch to `main` branch.
\ No newline at end of file
diff --git a/docs_projectinca/astro.config.mjs b/docs_projectinca/astro.config.mjs
index 123d759..e086214 100644
--- a/docs_projectinca/astro.config.mjs
+++ b/docs_projectinca/astro.config.mjs
@@ -45,6 +45,7 @@ export default defineConfig({
items: [
{ label: 'Glossary', link: '/references/glossary/' },
+ { label: 'Whitepaper', link: '/references/inca_whitepaper/' },
{ label: 'Disclaimer', link: '/references/disclaimer/' },
],
},
diff --git a/docs_projectinca/src/content/docs/references/img/devops.png b/docs_projectinca/src/content/docs/references/img/devops.png
new file mode 100644
index 0000000..183380c
Binary files /dev/null and b/docs_projectinca/src/content/docs/references/img/devops.png differ
diff --git a/docs_projectinca/src/content/docs/references/img/image1.png b/docs_projectinca/src/content/docs/references/img/image1.png
new file mode 100644
index 0000000..a24070e
Binary files /dev/null and b/docs_projectinca/src/content/docs/references/img/image1.png differ
diff --git a/docs_projectinca/src/content/docs/references/img/image4.png b/docs_projectinca/src/content/docs/references/img/image4.png
new file mode 100644
index 0000000..df63275
Binary files /dev/null and b/docs_projectinca/src/content/docs/references/img/image4.png differ
diff --git a/docs_projectinca/src/content/docs/references/img/qsss_overview.png b/docs_projectinca/src/content/docs/references/img/qsss_overview.png
new file mode 100644
index 0000000..81af868
Binary files /dev/null and b/docs_projectinca/src/content/docs/references/img/qsss_overview.png differ
diff --git a/docs_projectinca/src/content/docs/references/img/redundant_net.jpg b/docs_projectinca/src/content/docs/references/img/redundant_net.jpg
new file mode 100644
index 0000000..6f6539b
Binary files /dev/null and b/docs_projectinca/src/content/docs/references/img/redundant_net.jpg differ
diff --git a/docs_projectinca/src/content/docs/references/img/release_schedule.png b/docs_projectinca/src/content/docs/references/img/release_schedule.png
new file mode 100644
index 0000000..ef44cdb
Binary files /dev/null and b/docs_projectinca/src/content/docs/references/img/release_schedule.png differ
diff --git a/docs_projectinca/src/content/docs/references/img/smartcontract3_flow.jpg b/docs_projectinca/src/content/docs/references/img/smartcontract3_flow.jpg
new file mode 100644
index 0000000..c5b4054
Binary files /dev/null and b/docs_projectinca/src/content/docs/references/img/smartcontract3_flow.jpg differ
diff --git a/docs_projectinca/src/content/docs/references/img/storage_today.png b/docs_projectinca/src/content/docs/references/img/storage_today.png
new file mode 100644
index 0000000..be3e068
Binary files /dev/null and b/docs_projectinca/src/content/docs/references/img/storage_today.png differ
diff --git a/docs_projectinca/src/content/docs/references/img/webgateway.jpg b/docs_projectinca/src/content/docs/references/img/webgateway.jpg
new file mode 100644
index 0000000..a14706a
Binary files /dev/null and b/docs_projectinca/src/content/docs/references/img/webgateway.jpg differ
diff --git a/docs_projectinca/src/content/docs/references/img/webgw_scaling.jpg b/docs_projectinca/src/content/docs/references/img/webgw_scaling.jpg
new file mode 100644
index 0000000..a0c0af5
Binary files /dev/null and b/docs_projectinca/src/content/docs/references/img/webgw_scaling.jpg differ
diff --git a/docs_projectinca/src/content/docs/references/img/word_records.png b/docs_projectinca/src/content/docs/references/img/word_records.png
new file mode 100644
index 0000000..7bbe65b
Binary files /dev/null and b/docs_projectinca/src/content/docs/references/img/word_records.png differ
diff --git a/docs_projectinca/src/content/docs/references/img/zero_knowledge_proof.png b/docs_projectinca/src/content/docs/references/img/zero_knowledge_proof.png
new file mode 100644
index 0000000..9f0df3a
Binary files /dev/null and b/docs_projectinca/src/content/docs/references/img/zero_knowledge_proof.png differ
diff --git a/docs_projectinca/src/content/docs/references/inca_whitepaper.md b/docs_projectinca/src/content/docs/references/inca_whitepaper.md
new file mode 100644
index 0000000..cf092c2
--- /dev/null
+++ b/docs_projectinca/src/content/docs/references/inca_whitepaper.md
@@ -0,0 +1,1040 @@
+---
+title: Internet Capacity Whitepaper
+description: The whitepaper presenting the Internet Capacity project
+---
+
+## Introduction
+
+This document introduces the fourth iteration of the ThreeFold Grid: Project Internet Capacity. The ThreeFold Internet Capacity project represents a complete self-healing and autonomous decentralized cloud, based on open-source work and decades of work in the IT and cloud businesses with more than 500 million USD of exits for various projects and products. Our team achieved various feats in the world of cloud computing and the ThreeFold enterprise represents our cohesive integration of all the technology we've built, an all-encompassing knowledge base that we've learned in the past years. Our team is dedicated to bring forth to the world technology and ecosystems that will enable everyone, everywhere, no matter the creed or situation, to thrive with freedom and security within the worldwide cloud landscape.
+
+A major aim of the Project Internet Capacity is to maximize and enable strong collaboration with projects from the DePIN space. 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 Internet Capacity.
+
+This white paper will provide a clear portrait of the project at this precise moment in time, as well as the direction we are taking and the upcoming achievements we set in our way. Our roadmap is filled with concrete technological advancements and we are now adding a clear focus to the project: ensuring that the tech we so dearly created throughout the years is accessible to anyone to further their Internet capacity sovereignty.
+
+### Problems & Solutions
+
+Cloud is growing at an unprecedented rate, the evolution of edge cloud and AI are huge drivers. There is a real need to provide a more decentralized offering with higher standards of security and equality.
+
+ThreeFold provides a new way to deploy AI and Cloud capacity (storage, compute and network). Internet capacity Providers (we call them Farmers) deploy capacity, and developers use this capacity. Applications can be deployed on this network of capacity in neutrality and with data sovereignty.
+
+The aim of the ThreeFold project is to provide an alternative Cloud and Internet experience:
+
+- We want to help bring the Internet to the 3 billion people who don’t have reasonable access yet.
+- Allow everyone to build on top (open source), equality is important
+- Give everyone their personal 3Bot to make the Internet more easy and safe to use without the need for manipulation. The Internet should be a tool, not take over our life.
+- Green = up to 3 to 10x energy savings (by using the 3Bot concept)
+
+Today, the technology is live in its 3rd generation and this document presents its 4th generation. The current grid has been connected in more than 60 countries across the globe.
+
+
+
+### The Internet is Broken
+
+Today's Internet is broken. The promise of a neutral peer-to-peer network connecting the entire planet remains unfulfilled. Instead, people became products and data became like digital oil, fueling another extractive and unsustainable industry.
+
+This Internet largely relies on massive centralized data centers that exist only in a handful of regions and are mostly controlled by a handful of large corporations. Nearly half the planet remains unconnected, and the current model can't scale with ever-increasing demand from those who are connected.
+
+While blockchain and web3 represent an important improvement for the future of the Internet, these
+technologies are not a complete solution. The next generation Internet will need to handle massive amounts of data and computation in a way that's independent from the legacy web2 infrastructure and the corporations who own it.
+
+ThreeFold enables anyone to participate in the creation and the utilization of a regenerative, safe, and sovereign Internet infrastructure. Upon that foundation, any digital experience or application can be hosted in a way that's efficient and secure.
+People today can become co-owners of a powerful decentralized computing network by connecting their hardware to a network made possible by ThreeFold's unique software, including a unique autonomous operating system. Likewise, individual communities can form their own independent Internet network that serves as one node in a global mesh. ThreeFold has the potential to serve every person on Earth.
+
+The baseline of this model is both abundance and freedom: abundance of knowledge and digital resources as well as freedom to access and publish information. Simultaneously, it allows individuals and groups to really own and control their data, in a way that's private and indestructible. The original promise of the Internet: a peer-to-peer participatory network that can meet the needs of all of humanity for generations to come.
+
+The TFGrid, in essence, is built of ThreeFold Nodes and 3Bots. ThreeFold Nodes are computers which run our operating system called Zero-OS and provide a given amount of compute, network and storage capacity. Farmers (miners) receive rewards for hosting a ThreeFold Node and connecting to the standard Internet. 3Bots are personal gateways providing access to the decentralized web3 universe while also making sure that the data of users can never get corrupted nor lost.
+This new Internet, as we call it, is fully compatible with the existing one. Indeed, ThreeFold has successfully developed a peer-to-peer cloud operating system running on bare hardware, directly using the computer native resources.
+
+Our aim is to build a robust, sustainable, and genuinely decentralized Internet capacity layer, including storage and computing resources, for any blockchain project to thrive on, and much more. The following document will outline in further detail the possibilities that ThreeFold offers.
+
+
+## Project INCA: A Sovereign Internet
+
+Imagine a world where YOU are the Internet.
+
+Imagine a world where communities can build and own their own Internets from scratch – which would deliver all the needs for a better future life.
+This Internet is here! It includes:
+ - A regenerative, safe, sovereign Internet infrastructure layer = ThreeFold (TFGrid).
+ - A set of experiences (applications) and information to allow everyone on an equal basis to learn,
+create, exchange, travel, … basically to experience an abundance-based world.
+
+Abundance is our baseline:
+
+ - An abundance of free information, education, and knowledge (e.g. books, journals, studies), information about our planet (e.g. maps, databases), and creativity (e.g. music, video, digital art, immersive museums).
+ - Access to all applications required for your personal and professional digital life.
+ - You can safely communicate with the world.
+ - You can freely exchange anything for anything else (money for goods, goods for goods, money for money, etc.).
+ - No need for manipulative marketing – you can find anything for free and promote everything for free.
+
+This decentralized Internet lets you co-own a supercomputer at the edge, which gives you unlimited access to advanced digital experiences in high quality, such as augmented reality (education, shopping, …), virtual reality (online meetings, travel, concerts, …), metaverse (a metaverse owned by you), and more.
+
+You can keep your full digital life history in your personal ultra-secure archive. All the data is yours, forever.
+
+
+### Why A New Internet?
+
+
+Fundamentally, the current Internet cannot keep up with emerging demand.
+
+The digital economy and our future as digital citizens are wholly dependent on the Internet. However, today’s Internet and cloud infrastructure is too centralized, cannot grow fast enough to meet growing demand nor support future use cases, and promises neither data sovereignty nor equality.
+
+More than 80% of today's Internet infrastructure is owned by less than twenty (20) organizations. The lack of ownership of our own data and the consequent commercialization of that data is a major concern for individuals, communities, and governments alike. The future neutrality and democratization of the Internet is an absolute necessity in this regard.
+
+The Internet is growing like crazy. Today, the Internet is mainly delivered out of hyperscale data centers, which are massive buildings containing up to millions of servers. They consume excessive amounts of energy and are expensive to build. Simply increasing the number of data centers is not a realistic solution.
+
+There are not enough data centers today and this won't change in the short term: it is too expensive and too complex of an undertaking.
+They are not glocal (close to the source where required) and they are too centralized: as such, they present a single target for hackers.
+
+Data centers are not war-proof; they are vulnerable to attack and catastrophes (e.g. Sudan, Ukraine).
+
+ThreeFold is different. We present an Internet where communities can build and own their own Internet capacity.
+
+
+### Project Vision
+
+Our vision is to create a truly decentralized internet where every user has control over their data and digital interactions. We envision a global network of interconnected servers and nodes, collectively known as the grid, that democratizes access to computing power and storage. This network will be the backbone of a new digital era, characterized by sovereignty, security, privacy and inclusivity.
+
+Through our Internet Capacity token ($INCA), we aim to facilitate a robust and scalable ecosystem that supports the free and open exchange of internet capacity for cloud service providers hosting on the grid and builders and users deploying on it.
+
+### Mission Statement
+
+We promote the growth of a decentralized cloud network that is community-driven and inclusive. Our mission is to empower individuals and organisations with secure, private, and autonomous access to computing resources. Everyone deserves fair access to the cloud.
+
+A unique combination of technologies provides a resilient and censorship-resistant infrastructure that ensures data integrity, privacy, and seamless hosting of data and applications. We are committed to fostering innovation, enhancing digital sovereignty, and creating a more equitable internet for all.
+
+### Values
+
+The ThreeFold Internet Capacity project is defined by strong values that are rooted in a planet and people first philosophy.
+
+**Digital Sovereignty**
+
+We believe in the autonomy of cyberspace. The internet should be free from external control and interference, allowing users to govern their own digital spaces.
+
+**Universal Access**
+
+Access to the internet is a fundamental right. We strive to ensure that everyone, regardless of location or socioeconomic status, can connect to the digital world.
+
+**Privacy and Security**
+
+Every user has the right to privacy and security online. We are committed to protecting personal data and ensuring safe digital interactions.
+
+**Open Innovation**
+
+The internet should be a platform for innovation and creativity. We support open-source projects and collaborative efforts that drive technological advancement.
+
+**Free Expression**
+
+Freedom of speech is essential in cyberspace. We defend the right to express ideas and opinions without fear of censorship or retribution.
+
+**Decentralization**
+
+Power should not be concentrated in the hands of a few. We advocate for decentralized networks and systems that distribute control and foster resilience
+
+**Transparency**
+
+Transparency builds trust. We promote open governance and clear communication about how digital platforms operate and make decisions.
+
+**Community Governance**
+
+The internet community should have a say in how cyberspace is managed. We encourage participatory decision-making processes that reflect the diverse voices of users.
+
+**Digital Literacy**
+
+Empowering users with knowledge is crucial. We support education and resources that help people navigate and utilize the internet effectively and responsibly.
+
+**Sustainable Development**
+
+The growth of the internet should be sustainable. We are committed to practices that minimize environmental impact and promote long-term digital health.
+
+### Team
+
+Our team brings together +30 years of experience in cloud automation, Internet storage, and infrastructure services. We are a passionate group on a collective mission to make the world a better place for the people around us.
+
+We were fortunate to be part of the first rollout of the Internet in the early 1990’s.
+
+Our team has multiple world records for scaling projects on the Internet and invented the first data deduplication system for backup, the first ultra scalable distributed storage system using forward-looking error correcting codes, one of the first cloud systems, the first always-consistent distributed database, and the first decentralized operating system using blockchain technology. The team has achieved over +500m USD in exits to Sun Microsystems, Western Digital, Verizon, Symantec, and others.
+
+Our ThreeFold system brings us back to the Internet as originally conceived. A collaborative and community-based network of compute, storage and network resources, peer-to-peer connected and delivered by all. Only this time, we can use advanced technologies and structures which were only developed very recently.
+
+### Exits
+
+Our team has extensive experience in building cloud businesses, having successfully exited multiple companies in this space. Combining a recurring revenue model with the community engagement and certified commercial capacity of the TFGrid creates a compelling narrative and a robust business proposition.
+
+
+
+At Hostbasket, we managed a successful recurring revenue model with 30,000 customers. If executed properly, such models have the potential for exponential growth. At Dedigate we were managing super big projects. At Q-Layer we basically invented the basics of cloud. At Amplidata we developed an incredibly scalable and safe storage system.
+While traditionally running a hosting business, such as AI or Cloud services, comes with significant capital expenditure (CAPEX), that's not the case for us. Our unique advantage lies in the super cost-effective compute, network, and storage capacities we have developed over our 5-year history. Through building the ThreeFold Cloud, we have streamlined our resources and infrastructure, thus significantly reducing our overhead costs and enabling us to offer highly competitive rates.
+
+### World Records
+
+Our team is working on re-inventing layers of the Internet for more than 30 years. While we were doing so this has resulted in some world records and innovative products.
+
+Here is an overview of those achievements:
+
+
+
+### Timeline and Roadmap
+
+- 2017: Launch of ThreeFold Token (TFT) on our own blockchain
+- 2018: Launch of ThreeFold Grid 1.0
+- 2018: +5000 CPU cores, +10.000.000 GB storage capacity deployed (only for test workloads)
+- 2019: Launch of ThreeFold Grid 2.0, TFT moves to Stellar blockchain2021 Q3: +17.000 CPU cores, +80.000.000 GB storage capacity deployed
+- 2021 Q4: Nov 11, 1000 farmers milestone, 1000 farmers provide capacity on TFGrid
+- 2021 Q4: Launch of ThreeFold Grid 3.0 testnet
+- 2022 Q1: Marketing & public launch of our ThreeFold Grid version 3.0 (first availability for commercial use)
+- 2022: Introduction of Internet of Internets Concept
+- 2022 Q4: Signed head of terms with a country for a digital freezone
+- 2023 H1: Announcement of the first country-wide agreement for ThreeFold Grid deployments
+- 2024 Q4: (Expected) Launch of ThreeFold Grid 4.0 with Project Internet Capacity
+
+## Partners
+
+Our great partners make the grid what it is: a community-driven, open-source and decentralized cloud for all.
+
+We are proud of our partners stemming from all sectors of the industry. Our ecosystem is always expanding and we're always ready for new collaborations.
+
+We present here some of our amazing partners. This also serves to showcase the different use cases possible on the grid.
+
+### Holochain
+
+[Holochain](https://www.holochain.org/) is a framework for creating and powering distributed applications, incorporating peer-to-peer content distribution protocol, cryptography, and hash tables. It avoids scalability issues, and is extremely environmentally friendly.
+
+### Digital Free Zone
+
+The [OurWorld Digital FreeZone](https://ourworld.tf/), established in Zanzibar, is a groundbreaking partnership between ThreeFold and the government of Tanzania. This initiative aims to create a free sovereign digital and economic area, fostering innovation, growth, and prosperity.
+
+### Earth Wallet
+
+[Earth Wallet](https://www.earthwallet.io/) is a cutting-edge digital wallet solution designed to empower users with secure and decentralized control over their digital assets. With a focus on accessibility, security, and sustainability, Earth Wallet offers a seamless and user-friendly interface for managing various cryptocurrencies.
+
+### Elestio
+
+[Elestio](https://elest.io/) is an innovative platform dedicated to providing cutting-edge decentralized applications (dApps) and services to users worldwide, with a focus on accessibility, security, and user empowerment. Users of the grid can thus access Elestio's services from anywhere in the world.
+
+### Sikana
+
+[Sikana](https://www.sikana.tv/en), a platform dedicated to providing education for all, has delivered over 400 million lessons through free educational videos. This partnership will empower communities worldwide with knowledge and skills, irrespective of their financial or geographical limitations.
+
+### Tanzania Sovereign Internet
+
+ThreeFold is proud to announce its partnership with the government of Tanzania to establish a [sovereign internet](https://www.ictc.go.tz/), an unprecedented initiative poised to revolutionize Tanzania's startup ecosystem fostering digital freedom via a collaborative peer-to-peer platform.
+
+### Vverse
+
+[Vverse](https://www.vindo.ai/) is an innovative platform that aims to create a virtual universe where users can explore, interact, and create in immersive virtual environments. It leverages cutting-edge technologies such as virtual reality (VR), augmented reality (AR), and blockchain.
+
+## Token
+
+Here is an overview of the INCA token.
+
+### Tokenomics and Distribution
+
+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
+
+### 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%.
+
+### Grants
+
+While there are currently no grants defined yet for our INCA release, we present here the overall grant program.
+
+660,000,000 INCA is available for Grants (over all releases). This is subject to change as we define the project.
+
+Please contact us to let us know on which projects you would like to work, below you can see a suggested Distrubution of grants.
+
+The grant distribution in percentage would be as follows:
+
+- Community Expansion Projects: 20%
+- Development of Hardware for INCA: 20%
+- Organization of Rewards for Hackathlons: 10%
+- Organization of Localized Chapters: 15%
+- Development of Code: 30%
+- Training, Product Marketing: 5%
+
+#### Grant Voting Process
+
+We present the general grant voting process. This is subject to change as we implement the project, but it can serve as a good overview of the process.
+
+- Go to INCA Connect
+- See the projects
+- Vote yes or no for a given project
+- Vote requests for projects need to be live for a minimum of 2 weeks
+- Votes are not free
+ - Minimum 5 USD, but preferred 10 or more
+ - The proceeds of votes go back to the treasury
+- Each project defines
+ - Minimum number of votes
+ - Voting fee
+ - If dedicated account
+ - Proper description
+ - Vesting scheme
+- Everyone can see the projects on the Project INCA Projects website and comment if logged in and accepted as commenter or moderator
+- We need simple majority to have a positive vote
+- Once we have a positive vote, the money goes in the account created for the project
+ - There can be vesting on it, with acceleration, etc.
+- Supported chains
+ - We start by supporting Stellar
+ - Then we will also support Solana
+
+
+## Consensus Mechanisms
+
+### Proof-of-Capacity
+
+ThreeFold Nodes (computers) deliver storage, compute, and network capacity as the basis for our new Internet.
+
+Our unique operating system, Zero-OS, measures the capacity as provided by a farmer and this gets registered in our blockchain.
+
+> TFT Reward per Month = ThreeFold Node Capacity * TFT Reward per Unit of Capacity / Month.
+
+This TFT Reward Amount :
+
+- is recorded in the blockchain at the moment of a ThreeFold Node’s registration and verification. Every hour, our operating system and blockchain verifies the available capacity.
+- is calculated so that it generates, per month, more or less 1/5 of all TFT needed to buy all capacity at the point of registration,e.g. if a ThreeFold Node can generate commercial value of 100 USD per month for all Internet capacity and the TFT price is 0.1 at that point, then 100*0.1/5 is more or less the amount of TFT that will be rewarded (generated) per month.
+This means TFT is by design undervalued in relation to utilization at connection.
+- is agreed upon by the DAO per Regional Internet to make sure there is consensus.
+The farmer can receive boosters rewards (still to be defined) if certain achievements are reached, e.g. uptime, good bandwidth to Internet, good utilization, etc. There is no link between farming & utilization.
+
+
+#### How It Works
+
+The Proof-of-Capacity records Internet resources from the ThreeFold Node:
+
+The ThreeFold Blockchain (TFChain) uses work algorythm called "Proof-of-Capacity" to verify the Internet capacity provided by ThreeFold Nodes. Put simply, PoC verifies, on an ongoing basis, that farms are honestly representing the Internet capacity they provide to the network.
+
+**See Proof-of-Capacity in action** by visiting the [ThreeFold Grid Node Finder](https://dashboard.grid.tf/#/deploy/node-finder/) which represents the best resource to view POC-related data.
+
+#### What is proof-of-capacity?
+
+POC allows ThreeFold Farmers to earn reward according to their contribution. Farming is the "work" itself, the act of providing Internet capacity to the network and making it accessible via our TFDAO and TFChain.
+
+The PoC algorythm records four different types of Internet capacity:
+
+- Compute Capacity (CPU)
+- Memory Capacity (RAM)
+- Storage Capacity (SSD/HDD)
+- Network Capacity (Bandwidth, IP Addresses)
+
+#### Why Proof-of-Capacity?
+
+PoC comes with a number of benefits, including:
+
+- Energy efficiency: earning reward in form of TFT does not waste energy, farming TFT is a carbon_negative operation.
+- Lower barriers to entry with reduced hardware requirements: no need for elite hardware to stand a chance for earning rewards.
+- Decentralized: allows anyone to connect a ThreeFold Node to the network. TFGrid runs as a DAO.
+
+The main advantage of PoC to farmers it makes it really easy to run a ThreeFold Node. It doesn't require huge investments in hardware or energy and everyone earns a fair reward for their contribution. It is more decentralized, allowing for increased participation, and more ThreeFold Nodes doesn't mean increased returns, like in mining.
+
+#### How Does Proof-of-Capacity Work?
+
+1. A farmer boots hardware with Zero-OS (multiple boot methods available)
+2. Zero-OS is a low level OS, with no shell, farmers cannot access Zero-OS
+3. Zero-OS reports used IT capacity towards TFChain
+4. TFChain and TFDAO will calculate rewards as required for the farmer (TFGrid 3.1.x)
+5. TFChain will mint the required TFT and send them to account on TFChain of TFFarmer.
+6. Everyone can use the ThreeFold Node Finder to see where capacity is available. This info comes from the TFChain.
+
+> DISCLAIMER: ThreeFold Foundation organizes this process. This process is the result of the execution of code written by open source developers (Zero-OS and minting code) and a group of people who checks this process voluntarily. No claims can be made or damages asked for to any person or group related to ThreeFold Foundation like, but not limited to, the different councils. This process changes for TFGrid 3.X once the TFDAO is fully active.
+
+> Important note: The ThreeFold Token ($TFT) and Internet Capacity Token ($INCA) is not an investment instrument. TFTs are used to buy and sell IT capacity on the ThreeFold Grid.
+
+### Proof-of-Utilization
+
+ThreeFold Token ("TFT") is an Utility token and gets generated by ThreeFold Farmers, see proof-of-capacity for more information.
+
+Each ThreeFold Grid user can now use this capacity. The ThreeFold Chain ("TFChain") - ThreeFold Blockchain will track the utilization of this capacity. This process is called Proof-of-Utilization. Each hour the utilization is being tracked on the blockchain and charged to the capacity's user.
+
+#### What is Proof-of-Utilization?
+
+Proof-of-utilization is the underlying mechanisms that verifies the utilization of Internet capacity on the ThreeFold Grid.
+
+Every hour, the utilization is recorded in TFChain and the user is charged for the Internet capacity used on the ThreeFold Grid. Discount calculated in line with the amount of TFT users have in their accounts on TFChain.
+
+#### How Does Proof-of-Utilization Work?
+
+1. A user reserves Internet capacity on a given set of 3Nodes.
+2. Zero-OS records the reserved and used CU, SU, NU and IPAddresses in correlation with TFChain records.
+3. The TFChain DAO will charge the costs to the user in line with discount mechanism
+4. TFT from the user account are burned/distributed in line to table below.
+
+| Percentage | Description | Remark |
+| ---------- | -------------------------------------- | ------------------------------------------------------------------------ |
+| 35% | TFT burning | A mechanism used to maintain scarcity in the TFT economy. |
+| 10% | ThreeFold Foundation | Funds allocated to promote and grow the ThreeFold Grid. |
+| 5% | Validator Staking Pool | Rewards farmers that run TFChain 3.0 validator nodes. |
+| 50% | Solution providers & sales channel | managed by ThreFold DAO |
+
+> Note: While the solution provider program is still active, the plan is to discontinue the program in the near future. We will update the manual as we get more information. We currently do not accept new solution providers.
+
+##### TFGrid Capacity Utilization
+
+- Each solution provider and sales channel gets registered in TFChain and as such the distribution can be defined and calculated at billing time.
+- For billing purposes, ThreeFold DAO will check if it is from a known sales channel or solution provider. If yes, then the billing smart contract code will know how to distribute the TFTs. If the channel of solution provider is not known, then the 50% will go to the ThreeFold Foundation.
+- For Certified Farming, ThreeFold Tech can define the solution & sales channel parameters, these are channels as provided by ThreeFold Tech.
+- Burning can be lowered to 25% if too many tokens would be burned, ThreeFold DAO consensus needs to be achieved.
+
+##### Other Ways TFT are Required
+
+- Anyone building solutions on top of the TFGrid can use TFT as a currency to charge for the added value they provide, this gives an extra huge requirement for TFT.
+- Some will use TFT as a store or exchange of value, like money, because TFT is a valuable commodity. The hoarding of TFT means that TFT are not available to be used on the TFGrid.
+
+## Ecosystem
+
+We present an overview of the INCA ecosystem.
+
+### INCA Cockpit: Cloud Marketplace
+
+We are introducing a market place and our next generation grid v4.0 (INCA).
+
+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
+
+- Better utilization of hardware capacity.
+- 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 to monitor and enforce SLA's
+- Easier to track utilization and expansion
+- Can and will be extended to other Internet/cloud Services
+
+
+#### Pricing
+
+#### Slice Concept
+
+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.
+
+These Cloud, Storage or AISlices can be bought by the INCA/TF Community through the INCA marketplace.
+
+#### AI Slices
+
+An AI box is a unit of AI capacity (GPU or future TPU driven).
+
+The mininal GPU supported for now is a Nvidia 4090 or comparable
+An AI box can be launched in our Zero-OS and can enable any possible AI workload.
+
+#### Cloud Slices
+
+A cloudslice is a unit of compute, fast storage and memory. There are unlimited different configurations of cloudslice.
+
+A configuration of a machine defines the cloudslice which can be made.
+
+A cloudslice can be aggregated to make a bigger cloudslice.
+
+The default cloudslice has:
+
+- 4GB memory
+- 2 virtual cores of CPU
+- Minimal 50 GB of fast storage (can be more, as to be defined by provider)
+- Minimal availability of 1 mbit/s bandwidth at all times
+
+#### Storage Slices
+
+A storageslice is a unit of ZDB storage as can be used as backend for Zero-Stor (our quantum safe storage system).
+
+The default cloudslice has:
+
+- 100GB of storage
+
+A storagehour is like a kwatth unit for electricty, it represents a storageslice being used for 1h and billed as such.
+
+INCA Hosts (our cloud providers) can price the StorageHour themselves in a chosen currency.
+
+### INCA Connect: Token Wallet
+
+INCA Connect is a mobile app that serves as a gateway to the INCA ecosystem and its various products and services.
+
+Some key features and benefits of the INCA Connect app are:
+
+- 2FA Authenticator:
+ - INCA Connect is a passwordless 2FA authenticator that ensures a user is who they claim to be.
+- Decentralized:
+ - The app is decentralized, allowing users to access the INCA Network platforms and their fully private digital wallet.
+- Private Digital Wallet:
+ - Users can manage their INCA tokens and view their transaction history on the TF chain.
+- Support Chat:
+ - The app provides a support chat where users can get answers to their questions about INCA-related topics.
+- News Section:
+ - The app features a news section where users can find the latest INCA news and updates.
+
+## Farming
+
+The process of farming consists of a person or a company offering compute, storage and network capacity to the network.
+
+- Farmers buy INCA Nodes
+- They connect the INCA Nodes to internet and get rewards for providing capacity
+- Farmers earn rewards mainly for utilization, but there are also lots of rewards available for providing capacity.
+- Farmers help their community to get access to sovereign Internet and cloud applications on an unbreakabale and co-owned Internet and cloud.
+
+### INCA Nodes
+
+To become an INCA farmer, all you need is to acquire an INCA node, whether it is a DIY or certified node, and connect it to the grid. Farmers will receive INCA rewards based on the capacity they bring to the grid and the utilization they get on their nodes.
+
+#### Certified Nodes
+
+We offer certified nodes that are essentially plug-n-earn. Once you have a node, simply plug it to a power source and the internet to connect to the grid. Farming rewards are attributed to farmers for offering capacity and for the utilization it generates.
+
+We present the basic features of our certified nodes. This is subject to change.
+
+- SILVER
+ - 16 GB of Memory
+ - 1,000 GB of SSD
+ - 4 Logical CPU Cores
+- PLATINUM
+ - 64 GB of Memory
+ - 2,000 GB of SSD + 10,000 GB of HDD
+ - 16 Logical CPU Cores
+- AI
+ - 64 GB of Memory
+ - 4,000 GB of SSD + 10,000 GB of HDD
+ - RTX 4900 GPU
+
+#### DIY Nodes
+
+It is possible to build DIY nodes to connect to the INCA grid. Our manual covers the necessary information to build DIY nodes.
+
+### Network Map
+
+We are planning on creating a network map to visualize all INCA nodes and also devices from partners.
+
+### Reward Simulation
+
+We will provide a reward simulator for farmers. This will enable farmers to estimate farming rewards based on utilization.
+
+## Architecture
+
+### ThreeFold Grid
+
+The ThreeFold Grid is the co-owned infrastructure layer, and can be seen as a decentralized cloud. Farmers provide storage, compute, and network capacity to the people around them and earn for it. Farmers can be commercial entities or anyone using our open-source software to deploy nodes in their homes, schools and offices.
+
+3Bots live on top of the ThreeFold Grid and act as Web2 and Web3 gateways as well as self-healing bots for IT workloads. They are private virtual assistants that help users achieve a convenient, secure, and authentic digital life. They assist Web3 developers in achieving quicker results by alleviating concerns related to decentralization, scalability, storage stability, and performance, among other things.
+
+3Bots communicate directly with each other and the rest of the world (existing centralized services) as well as existing blockchain technologies. The data is stored using a novel storage technology which makes sure it is safe and can never get lost, yet it is only owned by you and not even a quantum computer can hack it.
+
+### ThreeFold Node
+
+Together we have the chance to build a new Internet, which consists of a network of ThreeFold Nodes. A ThreeFold Node is a standard computer which runs our Operating System called Zero-OS.
+
+Your ThreeFold Node has a certain amount of compute, network and storage capacity, a Farmer (miner) receives rewards for hosting a ThreeFold Node and connecting to the standard Internet. Today, you can become a farmer on our global proof of concept TFGrid network (version 3.0). See the [Internet Capacity website](https://internetcapacity.org) for more information. As of now, about 60,000 virtual CPU cores and 25,000,000 GB of storage are active on the TFGrid.
+
+A ThreeFold Node boots over the Internet network and runs our own stateless Zero-OS operating system. The Zero-OS allows the deployment of any IT workload in a safe way. Not only that, but any IT workload which can run on Linux is supported. Zero-OS supports many compute, storage and network primitives (virtual machines, deduped filesystems, quantum safe filesystem, planetary-scalable networks, containers, Kubernetes, etc.).
+
+## Technology
+
+We present an overview of the technology developed over the years.
+
+### Quantum Safe Storage: QSFS
+
+The Quantum Safe Storage Algorithm is the heart of the Storage engine. The storage engine takes the original data objects and creates data part descriptions that it stores over many virtual storage devices (ZDB/s).
+
+Data gets stored over multiple ZDB's in such a way that data can never be lost.
+
+Unique features
+
+- Data always append, can never be lost
+- Even a quantum computer cannot decrypt the data
+- Data is spread over multiple sites. If these sites are lost the data will still be available
+- Protects from datarot
+
+#### The Problem
+
+Today we produce more data than ever before. We cannot continue to make full copies of data to make sure it is stored reliably. This will simply not scale. We need to move from securing the whole dataset to securing all the objects that make up a dataset.
+
+We are using technology which was originally used for communication in space.
+
+The algo stores data fragments over multiple devices (physical storage devices ).
+
+The solution is not based on replication or sharding, the algo represents the data as equasions which are distributed over multiple locations.
+
+
+#### How Data Is Stored Today
+
+
+
+In most distributed systems, as used on the Internet or in blockchain today, the data will get replicated (sometimes after sharding, which means distributed based on the content of the file and spread out over the world).
+
+This leads to a lot of overhead and minimal control where the data is.
+
+In well optimized systems overhead will be 400% but in some it can be orders of magnitude higher to get to a reasonable redundancy level.
+
+#### The Quantum Safe Storage System Works Differently
+
+
+
+We have developed a new storage algorithm which is more efficient, ultra reliable and gives you full control over where your data is stored.
+
+Our approach is different. Let's try to visualize this new approach with a simple analogy using equations.
+
+Let a,b,c,d.... be the parts of the original object. You could create endless unique equations using these parts. A simple example: let's assume we have 3 parts of original objects that have the following values:
+
+```
+a=1
+b=2
+c=3
+```
+
+(and for reference the part of the real-world objects is not a simple number like `1` but a unique digital number describing the part, like the binary code for it `110101011101011101010111101110111100001010101111011.....`).
+
+
+With these numbers we could create endless amounts of equations:
+
+```
+1: a+b+c=6
+2: c-b-a=0
+3: b-c+a=0
+4: 2b+a-c=2
+5: 5c-b-a=12
+
+etc.
+
+```
+
+Mathematically we only need 3 to describe the content (value) of the fragments. But creating more adds reliability. Now store those equations distributed (one equation per physical storage device) and forget the original object. So we no longer have access to the values of a, b, c and we just remember the locations of all the equations created with the original data fragments.
+
+Mathematically we need three equations (any 3 of the total) to recover the original values for a, b or c. So do a request to retrieve 3 of the many equations and the first 3 to arrive are good enough to recalculate the original values. Three randomly retrieved equations are:
+
+```
+5c-b-a=12
+b-c+a=0
+2b+a-c=2
+```
+And this is a mathematical system we could solve:
+
+- First: `b-c+a=0 -> b=c-a`
+- Second: `2b+a-c=2 -> c=2b+a-2 -> c=2(c-a)+a-2 -> c=2c-2a+a-2 -> c=a+2`
+- Third: `5c-b-a=12 -> 5(a+2)-(c-a)-a=12 -> 5a+10-(a+2)+a-a=12 -> 5a-a-2=2 -> 4a=4 -> a=1`
+
+Now that we know `a=1` we could solve the rest `c=a+2=3` and `b=c-a=2`. And we have from 3 random equations regenerated the original fragments and could now recreate the original object.
+
+The redundancy and reliability in this system results from creating equations (more than needed) and storing them. As shown these equations in any random order can recreate the original fragments and therefore redundancy comes in at a much lower overhead.
+
+In our system we don't do this with 3 parts but with thousands.
+
+##### Example of 16/4
+
+Each object is fragmented into 16 parts. So we have 16 original fragments for which we need 16 equations to mathematically describe them. Now let's make 20 equations and store them dispersedly on 20 devices. To recreate the original object we only need 16 equations. The first 16 that we find and collect allows us to recover the fragment and in the end the original object. We could lose any 4 of those original 20 equations.
+
+The likelihood of losing 4 independent, dispersed storage devices at the same time is very low. Since we have continuous monitoring of all of the stored equations, we could create additional equations immediately when one of them is missing, making it an auto-regeneration of lost data and a self-repairing storage system.
+
+> The overhead in this example is 4 out of 20 which is a mere **20%** instead of **400%** .
+
+#### Content Delivery
+
+This system can be used as backend for content delivery networks.
+
+E.g. content distribution policy could be a 10/50 distribution which means, the content of a movie would be distributed over 60 locations from which we can lose 50 at the same time.
+
+If someone now wants to download the data, the first 10 locations to answer will provide enough of the data parts to rebuild the data.
+
+The overhead here is more, compared to previous example, but stil orders of magnitude lower compared to other CDN systems.
+
+#### The Quantum Safe Storage System Can Avoid Datarot
+
+Datarot is the fact that data storage degrades over time and becomes unreadable e.g. on a harddisk.
+
+The storage system provided by ThreeFold intercepts this silent data corruption ensurinf that data does not rot.
+
+#### Zero Knowledge Proof Storage System
+
+The Quantum Safe Storage System is zero knowledge proof compliant. The storage system is made up of / split into 2 components: the actual storage devices use to store the data (ZDB's) and the Quantum Safe Storage engine.
+
+
+
+The zero proof knowledge compliancy comes from the fact that all of the physical storage nodes (3Nodes) can prove that they store a valid part of the data that the quantum safe storage engine (QSSE) has stored on multiple independent devices. The QSSE can validate that all of the QSSE storage devices have a valid part of the original information. The storage devices however have no idea what the original stored data is as they only have a part (description) of the original data and have no access to the original data part or the complete original data objects.
+
+
+#### Mount Any Files In Your Storage Infrastructure
+
+The QSFS is a mechanism to mount any file system (in any format) on the grid, in a quantum secure way.
+
+This storage layer relies on 3 primitives:
+
+- [0-db](https://github.com/threefoldtech/0-db) is the storage engine.
+It is an always append database, which stores objects in an immutable format. It allows history to be kept out-of-the-box, good performance on disk, low overhead, easy data structure and easy backup (linear copy and immutable files).
+
+- [0-stor-v2](https://github.com/threefoldtech/0-stor_v2) is used to disperse the data into chunks by performing 'forward-looking error-correcting code' (FLECC) on it and send the fragments to safe locations.
+It takes files in any format as input, encrypts the file with AES based on a user-defined key, then FLECC-encodes the file and spreads out the result
+to multiple 0-DBs. The number of generated chunks is configurable to make it more or less robust against data loss through unavailable fragments. Even if some 0-DBs are unreachable, you can still retrieve the original data, and missing 0-DBs can even be rebuilt to have full consistency. It is an essential element of the operational backup.
+
+- [0-db-fs](https://github.com/threefoldtech/0-db-fs) is the filesystem driver which uses 0-DB as a primary storage engine. It manages the storage of directories and metadata in a dedicated namespace and file payloads in another dedicated namespace.
+
+Together they form a storage layer that is quantum secure: even the most powerful computer can't hack the system because no single node contains all of the information needed to reconstruct the data.
+
+
+
+This concept scales forever, and you can bring any file system on top of it:
+- S3 storage
+- any backup system
+- an ftp-server
+- IPFS and Hypercore distributed file sharing protocols
+
+
+
+#### Architecture
+
+By using our filesystem inside a Virtual Machine or Kubernetes, the cloud user can deploy any storage application on top e.g. Minio for S3 storage, OwnCloud as online fileserver.
+
+Any storage workload can be deployed on top of the zstor.
+
+### Quantum Safe Network: Mycelium
+
+
+Mycelium is an end-2-end encrypted IPv6 overlay network written in Rust where each node that joins the overlay network will receive an overlay network IP in the 400::/7 range.
+
+The overlay network uses some of the core principles of the [Babel routing protocol](https://www.irif.fr/~jch/software/babel).
+
+The planetary network called Mycelium is an overlay network which lives on top of the existing Internet or other peer-to-peer networks created.
+
+In the Mycelium network, everyone is connected to everyone. End-to-end encryption between users of an app and the app runs behind the network wall.
+
+Mycelium is an overlay network which lives on top of the existing Internet or other peer-to-peer networks created. In this network, everyone is connected to everyone. End-to-end encryption between users of an app and the app runs behind the network wall.
+
+Each user end network point is strongly authenticated and uniquely identified, independent of the network carrier used. There is no need for a centralized firewall or VPN solutions, as there is a circle-based networking security in place.
+
+#### Features
+
+- Mycelium, is locality aware, it will look for the shortest path between nodes
+- All traffic between the nodes is end-2-end encrypted
+- Traffic can be routed over nodes of friends, location aware
+- If a physical link goes down Mycelium will automatically reroute your traffic
+- The IP address is IPV6 and linked to private key
+- A simple reliable messagebus is implemented on top of Mycelium
+- Mycelium has multiple ways how to communicate quic, tcp, ... and we are working on holepunching for Quick which means P2P traffic without middlemen for NATted networks e.g. most homes
+- Scalability is very important for us, we tried many overlay networks before and got stuck on all of them, we are trying to design a network which scales to a planetary level
+- You can run mycelium without TUN and only use it as reliable message bus.
+
+#### Key Benefits
+
+- It finds shortest possible paths between peers
+- There is full security through end-to-end encrypted messaging
+- It allows for peer-to-peer links, like meshed wireless
+- It can survive broken Internet links and re-route when needed
+- It resolves the shortage of IPV4 addresses
+
+Whereas current computer networks depend heavily on very centralized design and configuration, this networking concept breaks this mold by making use of a global-spanning tree to form a scalable IPv6 encrypted mesh network. This is a peer-to-peer implementation of a networking protocol.
+
+The following table illustrates the high-level differences between traditional networks like today's Internet, and the Planetary Network created by ThreeFold:
+
+| Characteristic | Traditional | Mycelium |
+| --------------------------------------------------------------- | ----------- | -------- |
+| End-to-end encryption for all traffic across the network | No | Yes |
+| Decentralized routing information shared using a DHT | No | Yes |
+| Cryptographically-bound IPv6 addresses | No | Yes |
+| Node is aware of its relative location to other nodes | No | Yes |
+| IPv6 address remains with the device even if moved | No | Yes |
+| Topology extends gracefully across different mediums, i.e. mesh | No | Yes |
+| Post Quantum Safe | No | Yes |
+
+#### What are the problems solved here?
+
+The Internet as we know it today doesn’t conform to a well-defined topology. This has largely happened over time - as the Internet has grown, more and more networks have been “bolted together." The lack of defined topology gives us some unavoidable problems:
+
+- The routing tables that hold a “map” of the Internet are huge and inefficient
+- There isn’t really any way for a computer to know where it is located on the Internet relative to anything else
+- It is difficult to examine where a packet will go on its journey, from source to destination, without actually sending it
+- It is very difficult to install reliable networks into locations that change often or are non-static, i.e. wireless mesh networks
+
+These problems have been partially mitigated (but not really solved) through centralization - rather than your computers at home holding a copy of the global routing table, your ISP does it for you. Your computers and network devices are configured just to “send it upstream” and to let your ISP decide where it goes from there, but this does leave you entirely at the mercy of your ISP, who can redirect your traffic anywhere they like and to inspect, manipulate, or intercept it.
+
+In addition, wireless meshing requires you to know a lot about the network around you, which would not typically be the case when you have outsourced this knowledge to your ISP. Many existing wireless mesh routing schemes are not scalable or efficient, and do not bridge well with existing networks.
+
+### Zero-OS Operating System
+
+Z-OS (Zero Operating System) is a lightweight and secure operating system designed specifically for running workloads on the ThreeFold Grid. Z-OS provides a minimalistic and containerized environment for applications, enabling efficient resource allocation and management. With Z-OS, developers can deploy their applications easily and take advantage of the scalability and resilience offered by the ThreeFold Grid.
+
+ThreeFold built this decentralized autonomous operating system (OS) from scratch, starting with just a Linux kernel, for the purpose of dedicating hardware capacity to users of the TF Grid.
+
+Based on ThreeFold’s open-source technology, Zero-OS is a stateless and lightweight operating system that allows for an improved efficiency of up to 10x for certain workloads. Our OS achieves unparalleled levels of efficiency and security. With no remote shell or login and extremely small footprint, Zero-OS ensures that hosted workloads are protected from administrative exploits and human intervention.
+
+All 3Nodes are booted with Zero-OS to provide the storage, compute and network primitives for our open-source peer-to-peer Internet infrastructure. Due to the unique design of Zero-OS, any server-like hardware with an AMD or Intel processor can be booted and dedicated to the network.
+
+Zero-OS runs autonomously on 3Nodes once booted, requiring no maintenance or administration. The process is actually quite simple, also enabling people without technical skills to join the TFGrid by connecting a node in their home or office with full data sovereignty and security.
+
+#### Zero-OS Installation
+
+The Zero-OS is delivered to the 3Nodes over the internet network (network boot) and does not need to be installed.
+
+##### 3Node Install
+
+1. Acquire a computer (server).
+2. Configure a farm on the TFGrid explorer.
+3. Download the bootloader and put on a USB stick or configure a network boot device.
+4. Power on the computer and connect to the internet.
+5. Boot! The computer will automatically download the components of the operating system (Zero-OS).
+
+The actual bootloader is very small. It brings up the network interface of your computer and queries TFGeid for the remainder of the boot files needed.
+
+The operating system is not installed on any local storage medium (hard disk, ssd). Zero-OS is stateless.
+
+The mechanism to allow this to work in a safe and efficient manner is a ThreeFold innovation called our container virtual filesystem.
+
+For more information on setting a 3Node, please refer to the [Farmers documentation](../../../../documentation/farmers/farmers.md).
+
+
+#### Unbreakable Storage
+
+- Unlimited history
+- Survives network, datacenter or node breakdown
+- No silent corruption possible
+- Quantum safe (data cannot be decrypted by quantum computers) as long as quantum computer has no access to the metadata
+- Self-healing & autocorrecting
+
+
+If you deploy a container with simple disk access, you don’t have it.
+Performance is around 50MB/second, if a bit more CPU is given for the distributed storage encoder, we achieve this performance.
+
+#### Zero Hacking Surface
+
+Zero does not mean is not possible but we use this term to specificy that we minized the attack surface for hackers.
+
+- There is no shell/server interface on zero-os level (our operating system)
+- There are no hidden or unintended processes running which are not prevalidatedOne comment: still ssh server running with keys of a few people on each server, not yet disabled. To be disabled in the near future, now still useful to debug but it is a backdoor. The creation of a new primitive where the farmer agrees to give access to administrators under analysis. This way, when a reservation is sent to a node, a ssh server is booted up with chosen key to allow admins to go in.
+
+#### Zero Boot
+
+> Zero Boot = Zero-OS boot process
+
+ZOS Boot is a boot facility that allows 3nodes to boot from network boot servers located in the TF Grid. This boot mechanism creates as little as possible operational and administration overhead. ZOS Boot is a crucial part for enabling autonomy by *not* having the operating system installed on local disks on 3nodes. With a boot network facility and no local operating system files you immediate erase a number of operational and administration tasks:
+
+- to install the operating system to start with
+- to keep track of which systems run which version of the operating system (especially in large setups this is a complicated and error prone task)
+- to keep track of patches and bug fixes that have been applied to systems
+
+That's just the administration and operational part of maintaining a server estate with local installed operating system. On the security side of things the benefits are even greater:
+- many hacking activities are geared towards adding to or changing parts of the operating system files. This is a threat from local physical access to servers as well as over the network. When there are no local operating system files installed this threat does not exist.
+- accidental overwrite, delete or corruption of operating system files. Servers run many processes and many of these processes have administrative access to be able to do what they need to do. Accidental deletion or overwrites of crucial files on disk will make the server fail a reboot.
+- access control. I there is no local operating system installed access control, user rights etc etc. are unnecessary functions and features and do not have to be implemented.
+
+#### How
+
+In this image from fs, a small partition is mounted in memory to start booting the machine, it gets IPXE (downloads what it needs), and then 0-OS boots.
+After that, going to the hub, downloading different lists.
+
+There is 1 main flist that triggers downloads of multiple flists. Read more [here](../../../../documentation/developers/flist/flist.md).
+In there all the components/daemons that do part of the 0-OS.
+Also the download of the zos-bins, i.e. external binaries are triggered this way (https://hub.grid.tf/tf-zos-bins).
+
+The core components of zero-os can be found in: [Zero-OS repo](https://github.com/threefoldtech/zos/tree/master/bins/packages) = If something changes in the directory, a workflow is triggered to rebuild the full flist and push it to the hub.
+
+When a node discovers there is a new version of one of these lists on the hub, it downloads it, restarts the daemon with the new version.
+Over the lifetime of the node, it keeps pulling on the hub directories to check whether new daemons/flists/binaries are available and whether things need get upgraded.
+
+#### Features
+
+The features of ZOS Boot are:
+
+- no local operating system installed
+- network boot from the grid to get on the grid
+- decreased administrative and operational work, allowing for autonomous operations
+- increased security
+- increased efficiency (deduplication, only one version of the OS stored for thousands of servers)
+- all server storage space is available for enduser workloads (average operating system size around 10GB)
+- bootloader is less than 1MB in size and can be presented to the servers as a PXE script, USB boot device, ISO boot image.
+
+
+#### Deterministic Deployment
+
+- flists concept (deduped vfilesystem, no install, ...)
+
+The Dedupe filesystem flist uses fuse = interface which allows you to create the file system interface in user space, it is a virtual filesystem.
+Metadata is exposed. The system sees the full tree of the image, but data itself not there, data is downloaded whenever they are accessed.
+
+There are multiple ways to create an flist:
+ - Convert an existing docker image which is hosted on the docker hub
+ - Push an archive like a tjz on the hub
+ - A library and CLI tool exist to build the flist from scratch: doing it this way, the directory is locally populated, and the flist is then created from the CLI tool.
+ - A [GitHub action](https://github.com/threefoldtech/publish-flist) allows to build a flist directly from GitHub action, useful for developers on GitHub
+
+Be aware that the flist system works a bit differently than the usual deployment of containers (dockers), which doesn't do mounting of volumes from your local disk into container for configuration.
+With flists you need to modify your image to get configuration from environment. This is basically how docker was originally intended to be used.
+
+ - Smart contract for IT
+ The smart contract for IT concept is applicable to any workload: containers, VMs, all gateways primitives, volumes, kubernetes and network.
+ It is a static agreement between farmer and user about deployment of an IT workload.
+
+ - no dynamic behavior for deployment at runtime
+
+ - no process can start unless the files are 100% described on flist level
+
+#### Zero-OS Protect
+
+- The operating system of the 3node (Zero-OS) is made to exist in environments without the presence of technical knowhow. 3nodes are made to exist everywhere where network meet a power socket. The OS does not have a login shell and does not allow people to log in with physical access to a keyboard and screen nor does it allows logins over the network. There is no way the 3node accepts user initiated login attempts.
+- For certified capacity a group of known strategic vendors are able to lock the [BIOS](https://en.wikipedia.org/wiki/BIOS) of their server range and make sure no-one but them can unlock and change features present in the BIOS. Some vendors have an even higher degree of security and can store private keys in chips in side the computer to provider unique identification based on private keys or have mechanisms to check wether the server has been opened / tampered with in the transportation from the factory / vendor to the Farmer. All of this leads to maximum protection on the hardware level.
+- 3nodes boot from a network facility. This means that they do not have local installed operating system files. Also they do not have a local username / password file or database. Viruses and hackers have very little work with if there are no local files to plant viruses or trojan horses in. Also the boot facility provides hashes for the files sent to the booting 3node so that the 3node can check wether is receives the intended file, no more man in the middle attacks.
+- The zos_fs provides the same hash and file check mechanism. Every application file presented to a booting container has a hash describing it and the 3node on which the container is booting can verify if the received file matches the previously received hash.
+- Every deployment of one or more applications starts with the creation of a (private) [znet](../../primitives/network/znet.md). This private overlay network is single tenant and not connected to the public internet. Every application or service that is started in a container in this overlay network is connection to all of the other containers via a point to point, encrypted network connection.
+
+### Smart Contract for IT
+
+
+From TFGrid 3.0, the 'Smart Contract for IT' concept for reserving capacity is fully decentralized and runs on TF-Chain, the ThreeFold blockchain infrastructure on Parity Substrate.
+
+#### Architecture
+
+Two main components play a role in achieving a decentralised consensus between a user and a farmer.
+
+- TFGrid Substrate Database Pallet TFGrid
+- TFGrid Smart Contract
+
+The TF-Grid Substrate Database will keep a record of all Entities, Twins, Nodes and Farmers in the TF-Grid network. This makes it easy to integrate the Smart Contract on Substrate as well since we can read from that storage in runtime.
+
+
+
+The Smart Contract on Substrate works as following:
+
+#### 1: Deploy a Workload
+
+To deploy a workload, the user interacts with this smart contract pallet and calls: `create_contract` with the input being:
+
+The user must instruct his twin to create the contract. *This program containing his digital twin is yet to be defined.* A contract will always belong to a twin and to a node. This relationship is important because only the user's twin and target node's twin can update the contract.
+
+```js
+contract = {
+ version: contractVersion,
+ contract_id: contractID,
+ twin_id: NumericTwinID for the contract,
+ // node_address is the node address.
+ node_id: NumericNodeID
+ // data is the encrypted deployment body. This encrypted the deployment with the **USER** public key. So only the user can read this data later on (or any other key that he keeps safe).
+ // this data part is read only by the user and can actually hold any information to help him reconstruct his deployment or can be left empty.
+ data: encrypted(deployment) // optional
+ // hash: is the deployment predictable hash. the node must use the same method to calculate the challenge (bytes) to compute this same hash.
+ //used for validating the deployment from node side.
+ deployment_hash: hash(deployment),
+ // public_ips: number of ips that need to be reserved by the contract and used by the deployment
+ public_ips: 0,
+ state: ContractState (created, deployed),
+ public_ips_list: list of public ips on this contract
+}
+```
+
+The `node_id` field is the target node's ID. A user can do lookup for a node to find its corresponding ID.
+
+The workload data is encrypted by the user and contains the workload definition for the node.
+
+If `public_ips` is specified, the contract will reserve the number of public ips requested on the node's corresponding farm. If there are not enough ips available an error will be returned. If the contract is canceled by either the user or the node, the IPs for that contract will be freed.
+
+This pallet saves this data to storage and returns the user a `contract_id`.
+
+#### 2: Sending Data
+
+The user sends the contractID and workload through the RMB to the destination Node.
+
+The Node reads from the [RMB](https://github.com/threefoldtech/rmb) and sees a deploy command, it reads the contractID and workload definition from the payload.
+It decodes the workload and reads the contract from chain using the contract ID, the Node will check if the user that created the contract and the deployment hash on the contract is the same as what the Node receives over RMB. If all things check out, the Node deploys the workload.
+
+#### 3: Reports
+
+The Node sends consumption reports to the chain
+
+The Node periodically sends consumption reports back to the chain for each deployed contract. The chain will compute how much is being used and will bill the user based on the farmers prices (the chain can read these prices by quering the farmers storage and reading the pricing data). See [PricingPolicy](https://github.com/threefoldtech/substrate-pallets/blob/03a5823ce79200709d525ec182036b47a60952ef/pallet-tfgrid/src/types.rs#L120).
+
+A report looks like:
+
+json
+```
+{
+ "contract_id": contractID,
+ "timestamp": "timestampOfReport",
+ "cru": cpus,
+ "sru": ssdInBytes,
+ "hru": hddInBytes,
+ "mru": memInBytes,
+ "nru": trafficInBytes
+}
+```
+
+The node can call `add_reports` on this module to submit reports in batches.
+
+Usage of SU, CU and NU will be computed based on the prices and the rules that Threefold set out for cloud pricing.
+
+Billing will be done in Database Tokens and will be send to the corresponding farmer. If the user runs out of funds the chain will set the contract state to `cancelled` or it will be removed from storage. The Node needs to act on this 'contract cancelled' event and decommission the workload.
+
+The main currency of this chain. More information on this is explained here: TODO
+
+#### Notes
+
+Sending the workloads encrypted to the chain makes sure that nobody except the user can read his deployment data. It also facilitates a way for the user to recreate his workload data from the chain.
+
+#### Infrastructure as Code and DevOps
+
+Smart Contract on TFChain allows for efective DevOps deployments. DevOps is a process framework that ensures collaboration between Development and Operations Team to deploy code to production environment faster in a repeatable and automated way.
+
+In simple terms, DevOps can be defined as an alignment between development and IT operations with better communication and collaboration.
+
+
+
+### Web Gateway
+
+The Web Gateway is a mechanism to connect private networks to the open Internet in such a way that there is no direct connection between the Internet and the secure workloads running in the ZMachines.
+
+
+
+#### Key Benefits
+
+- Separation between where compute workloads are and where services are exposed
+- Redundancy: Each app can be exposed on multiple web gateways at once
+- Support for many interfaces
+- Helps resolve shortage of IPv4 addresses
+
+#### Implementation
+
+Some 3Nodes support gateway functionality (this is configured by the farmers). A 3Node with gateway configuration can then accept gateway workloads and forward traffic to ZMachines that only have Planetary Network or IPv6 addresses.
+
+The gateway workloads consist of a name (prefix) that first needs to be reserved on the blockchain. Then, the list of backend IPs. There are other flags that can be set to control automatic TLS (please check Terraform documentation for the exact details of a reservation).
+
+Once the 3Node receives this workload, the network configures proxy for this name and the Planetary Network IPs.
+
+#### Security
+
+ZMachines have to have a Planetary Network IP or any other IPv6 (IPv4 is also accepted). This means that any person connected to the Planetary Network can also reach the ZMachine without the need for a proxy.
+
+So it's up to the ZMachine owner/maintainer to make sure it is secured and that only the required ports are open.
+
+#### Redundant Network Connection
+
+
+
+#### Unlimited Scale
+
+
+
+The network architecture is a pure scale-out network system. It can scale to unlimited size, there is simply no bottleneck. Network "supply" is created by network farmers, and network "demand" is done by TF Grid users.
+
+Supply and demand scale independently. For supply, there can be unlimited network farmers providing web gateways on their own 3Nodes, and unlimited compute farmers providing 3Nodes for compute and storage. The demand side is driven by developers creating software that runs on the grid, system integrators creating solutions for enterprises, and so on. Globally, there is exponentially-growing demand for data processing and storage use cases.
+
+## Disclaimer
+
+This document represents a vision of the ThreeFold Internet Capacity project at a given time in space. It might not be representative of the future and is written as a best effort basis. This is not financial advice and we encourage everyone to do their own research.
+
+The information provided on this website and in any related materials is not intended as investment advice or a recommendation to buy or sell any security, including cryptocurrencies. The information provided is for general educational purposes only and should not be relied upon as the sole basis for making investment decisions.
+
+We make no warranties or guarantees regarding the performance or value of any cryptocurrency or blockchain-based asset. We do not guarantee that any investment will be profitable or that you will recoup your investment.
+
+By using this website and participating in the project, you acknowledge that you have read and understood the risks associated with investing in cryptocurrencies and blockchain-based assets, and you agree to use this website and participate in the project at your own risk.
+
+The whole project is open-source, mostly under the Apache 2.0 license. We encourage everyone to participate in the Internet Capacity project.
+
+By accessing this website and participating in the project, you acknowledge that you have read and understood this disclaimer and the risks associated with investing in cryptocurrencies and blockchain-based assets.
+
+If you have any questions or concerns about this disclaimer or the project, please contact us at [info@threefold.io](mailto:info@threefold.io).
\ No newline at end of file
diff --git a/heroscript/system_administrators/book_collections.md b/heroscript/sysadmins/book_collections.md
similarity index 90%
rename from heroscript/system_administrators/book_collections.md
rename to heroscript/sysadmins/book_collections.md
index dc32726..8993bfe 100644
--- a/heroscript/system_administrators/book_collections.md
+++ b/heroscript/sysadmins/book_collections.md
@@ -1,7 +1,7 @@
```js
-!!book.generate name:'system_administrators' title:'ThreeFold System Administrators Manual' printbook:false foldlevel:0
- url:'https://git.ourworld.tf/tfgrid/info_tfgrid/src/branch/main/books/system_administrators'
+!!book.generate name:'sysadmins' title:'ThreeFold System Administrators Manual' printbook:false foldlevel:0
+ url:'https://git.ourworld.tf/tfgrid/info_tfgrid/src/branch/main/books/sysadmins'
!!doctree.add
url:'https://git.ourworld.tf/tfgrid/info_tfgrid/src/branch/main/collections/manual'
diff --git a/heroscript/system_administrators/context.md b/heroscript/sysadmins/context.md
similarity index 100%
rename from heroscript/system_administrators/context.md
rename to heroscript/sysadmins/context.md
diff --git a/heroscript/system_administrators/sshkey.md b/heroscript/sysadmins/sshkey.md
similarity index 100%
rename from heroscript/system_administrators/sshkey.md
rename to heroscript/sysadmins/sshkey.md