-
-- [Javascript Client](grid3_javascript_readme.md)
- - [Installation](grid3_javascript_installation.md)
- - [Loading Client](grid3_javascript_loadclient.md)
- - [Deploy a VM](grid3_javascript_vm.md)
- - [Capacity Planning](grid3_javascript_capacity_planning.md)
- - [Deploy Multiple VMs](grid3_javascript_vms.md)
- - [Deploy CapRover](grid3_javascript_caprover.md)
- - [Gateways](grid3_javascript_vm_gateways.md)
- - [Deploy a Kubernetes Cluster](grid3_javascript_kubernetes.md)
- - [Deploy a ZDB](grid3_javascript_zdb.md)
- - [Deploy ZDBs for QSFS](grid3_javascript_qsfs_zdbs.md)
- - [QSFS](grid3_javascript_qsfs.md)
- - [Key Value Store](grid3_javascript_kvstore.md)
- - [VM with Wireguard and Gateway](grid3_wireguard_gateway.md)
- - [GPU Support](grid3_javascript_gpu_support.md)
-- [Go Client](grid3_go_readme.md)
- - [Installation](grid3_go_installation.md)
- - [Loading Client](grid3_go_load_client.md)
- - [Deploy a VM](grid3_go_vm.md)
- - [Deploy Multiple VMs](grid3_go_vms.md)
- - [Deploy Gateways](grid3_go_gateways.md)
- - [Deploy Kubernetes](grid3_go_kubernetes.md)
- - [Deploy a QSFS](grid3_go_qsfs.md)
- - [GPU Support](grid3_go_gpu.md)
-- [TFCMD](tfcmd.md)
- - [Getting Started](tfcmd_basics.md)
- - [Deploy a VM](tfcmd_vm.md)
- - [Deploy Kubernetes](tfcmd_kubernetes.md)
- - [Deploy ZDB](tfcmd_zdbs.md)
- - [Gateway FQDN](tfcmd_gateway_fqdn.md)
- - [Gateway Name](tfcmd_gateway_name.md)
- - [Contracts](tfcmd_contracts.md)
-- [TFROBOT](tfrobot.md)
- - [Installation](tfrobot_installation.md)
- - [Configuration File](tfrobot_config.md)
- - [Deployment](tfrobot_deploy.md)
- - [Commands and Flags](tfrobot_commands_flags.md)
- - [Supported Configurations](tfrobot_configurations.md)
-- [ThreeFold Chain](tfchain.md)
- - [Introduction](introduction.md)
- - [Farming Policies](farming_policies.md)
- - [External Service Contract](tfchain_external_service_contract.md)
- - [Solution Provider](tfchain_solution_provider.md)
-- [Grid Proxy](proxy_readme.md)
- - [Introducing Grid Proxy](proxy.md)
- - [Setup](setup.md)
- - [DB Testing](db_testing.md)
- - [Commands](commands.md)
- - [Contributions](contributions.md)
- - [Explorer](explorer.md)
- - [Database](database.md)
- - [Production](production.md)
- - [Release](release.md)
-- [Flist](flist.md)
- - [ThreeFold Hub Intro](zos_hub.md)
- - [Generate an API Token](api_token.md)
- - [Convert Docker Image Into Flist](convert_docker_image.md)
- - [Supported Flists](grid3_supported_flists.md)
- - [Flist Case Studies](flist_case_studies.md)
- - [Case Study: Debian 12](flist_debian_case_study.md)
- - [Case Study: Nextcloud AIO](flist_nextcloud_case_study.md)
-- [Internals](internals.md)
- - [Reliable Message Bus (RMB)](rmb_toc.md)
- - [Introduction to RMB](rmb_intro.md)
- - [RMB Specs](rmb_specs.md)
- - [RMB Peer](peer.md)
- - [RMB Relay](relay.md)
- - [ZOS](index.md)
- - [Manual](manual.md)
- - [Workload Types](workload_types.md)
- - [Internal Modules](zos_internals.md)
- - [Capacity](capacity.md)
- - [Performance Monitor Package](performance.md)
- - [Public IPs Validation Task](publicips.md)
- - [CPUBenchmark](cpubench.md)
- - [IPerf](iperf.md)
- - [Health Check](healthcheck.md)
- - [API](api.md)
-- [Grid Deployment](grid_deployment.md)
- - [TFGrid Stacks](tfgrid_stacks.md)
- - [Full VM Grid Deployment](grid_deployment_full_vm.md)
- - [Grid Snapshots](snapshots.md)
- - [Deploy the Dashboard](deploy_dashboard.md)
- - [Application Case Study: Nextcloud](app_case_study_nextcloud.md)
\ No newline at end of file
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/.gitignore b/docs_projectinca/.gitignore
deleted file mode 100644
index 6240da8..0000000
--- a/docs_projectinca/.gitignore
+++ /dev/null
@@ -1,21 +0,0 @@
-# build output
-dist/
-# generated types
-.astro/
-
-# dependencies
-node_modules/
-
-# logs
-npm-debug.log*
-yarn-debug.log*
-yarn-error.log*
-pnpm-debug.log*
-
-
-# environment variables
-.env
-.env.production
-
-# macOS-specific files
-.DS_Store
diff --git a/docs_projectinca/Makefile b/docs_projectinca/Makefile
deleted file mode 100644
index 202b232..0000000
--- a/docs_projectinca/Makefile
+++ /dev/null
@@ -1,3 +0,0 @@
-run:
- npm install
- npm run dev
diff --git a/docs_projectinca/README.md b/docs_projectinca/README.md
deleted file mode 100644
index 4bc2272..0000000
--- a/docs_projectinca/README.md
+++ /dev/null
@@ -1,103 +0,0 @@
-
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
-
-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
deleted file mode 100644
index 123d759..0000000
--- a/docs_projectinca/astro.config.mjs
+++ /dev/null
@@ -1,70 +0,0 @@
-import { defineConfig } from 'astro/config';
-import starlight from '@astrojs/starlight';
-
-// https://astro.build/config
-export default defineConfig({
- integrations: [
- starlight({
- title: 'Project INCA Docs',
- social: {
- github: 'https://github.com/threefoldtech',
- telegram: 'https://t.me/threefold',
- 'x.com': 'https://x.com/threefold_io',
- discord: 'https://discord.com/invite/NZqKC4jEhD',
- },
- sidebar: [
- {
- label: 'Start Here',
- items: [
-
- { label: 'Getting Started', link: '/start_here/getting_started/' },
- ],
- },
- {
- label: 'Steps',
- items: [
-
- { label: 'Install ThreeFold Connect', link: '/guides/threefold_connect/' },
- { label: 'Create an INCA Farm', link: '/guides/create_farm/' },
- { label: 'Get INCA Nodes', link: '/guides/get_inca_nodes/' },
- { label: 'Connect Your Nodes', link: '/guides/connect_the_nodes/' },
- { label: 'Manage Your Rewards', link: '/guides/manage_rewards/' },
- ],
- },
- {
- label: 'Resources',
- items: [
-
- { label: 'How to Use the Bots', link: '/resources/resources_introduction/' },
- { label: 'Node Status Bot', link: '/resources/node_status_bot/' },
- { label: 'Farmerbot', link: '/resources/farmerbot/' },
- ],
- },
- {
- label: 'References',
- items: [
-
- { label: 'Glossary', link: '/references/glossary/' },
- { label: 'Disclaimer', link: '/references/disclaimer/' },
- ],
- },
- {
- label: 'Legal',
- items: [
-
- { label: 'Terms and Conditions', link: '/legal/terms_and_conditions/' },
- { label: 'Privacy Policy', link: '/legal/privacy_policy/' },
- ],
- },
- ],
- head: [
- {
- tag: 'script',
- attrs: {
- src: '/crisp.js',
- },
- },
- ],
- }),
- ],
-});
diff --git a/docs_projectinca/crisp.js b/docs_projectinca/crisp.js
deleted file mode 100644
index 9e5aaa5..0000000
--- a/docs_projectinca/crisp.js
+++ /dev/null
@@ -1 +0,0 @@
-window.$crisp=[];window.CRISP_WEBSITE_ID="1a5a5241-91cb-4a41-8323-5ba5ec574da0";(function(){d=document;s=d.createElement("script");s.src="https://client.crisp.chat/l.js";s.async=1;d.getElementsByTagName("head")[0].appendChild(s);})();
\ No newline at end of file
diff --git a/docs_projectinca/docs_starlight/starlight_README.md b/docs_projectinca/docs_starlight/starlight_README.md
deleted file mode 100644
index b51abaa..0000000
--- a/docs_projectinca/docs_starlight/starlight_README.md
+++ /dev/null
@@ -1,54 +0,0 @@
-# Starlight Starter Kit: Basics
-
-[](https://starlight.astro.build)
-
-```
-npm create astro@latest -- --template starlight
-```
-
-[](https://stackblitz.com/github/withastro/starlight/tree/main/examples/basics)
-[](https://codesandbox.io/p/sandbox/github/withastro/starlight/tree/main/examples/basics)
-[](https://vercel.com/new/clone?repository-url=https%3A%2F%2Fgithub.com%2Fwithastro%2Fstarlight%2Ftree%2Fmain%2Fexamples%2Fbasics&project-name=my-starlight-docs&repository-name=my-starlight-docs)
-
-> 🧑🚀 **Seasoned astronaut?** Delete this file. Have fun!
-
-## 🚀 Project Structure
-
-Inside of your Astro + Starlight project, you'll see the following folders and files:
-
-```
-.
-├── public/
-├── src/
-│ ├── assets/
-│ ├── content/
-│ │ ├── docs/
-│ │ └── config.ts
-│ └── env.d.ts
-├── astro.config.mjs
-├── package.json
-└── tsconfig.json
-```
-
-Starlight looks for `.md` or `.mdx` files in the `src/content/docs/` directory. Each file is exposed as a route based on its file name.
-
-Images can be added to `src/assets/` and embedded in Markdown with a relative link.
-
-Static assets, like favicons, can be placed in the `public/` directory.
-
-## 🧞 Commands
-
-All commands are run from the root of the project, from a terminal:
-
-| Command | Action |
-| :------------------------ | :----------------------------------------------- |
-| `npm install` | Installs dependencies |
-| `npm run dev` | Starts local dev server at `localhost:4321` |
-| `npm run build` | Build your production site to `./dist/` |
-| `npm run preview` | Preview your build locally, before deploying |
-| `npm run astro ...` | Run CLI commands like `astro add`, `astro check` |
-| `npm run astro -- --help` | Get help using the Astro CLI |
-
-## 👀 Want to learn more?
-
-Check out [Starlight’s docs](https://starlight.astro.build/), read [the Astro documentation](https://docs.astro.build), or jump into the [Astro Discord server](https://astro.build/chat).
diff --git a/docs_projectinca/package.json b/docs_projectinca/package.json
deleted file mode 100644
index c606ce9..0000000
--- a/docs_projectinca/package.json
+++ /dev/null
@@ -1,19 +0,0 @@
-{
- "name": "",
- "type": "module",
- "version": "0.0.1",
- "scripts": {
- "dev": "astro dev",
- "start": "astro dev",
- "build": "astro check && astro build",
- "preview": "astro preview",
- "astro": "astro"
- },
- "dependencies": {
- "@astrojs/check": "^0.7.0",
- "@astrojs/starlight": "^0.24.3",
- "astro": "^4.10.3",
- "sharp": "^0.32.5",
- "typescript": "^5.4.5"
- }
-}
diff --git a/docs_projectinca/public/favicon.svg b/docs_projectinca/public/favicon.svg
deleted file mode 100644
index 11eda84..0000000
--- a/docs_projectinca/public/favicon.svg
+++ /dev/null
@@ -1,36 +0,0 @@
-
-
-
-
\ No newline at end of file
diff --git a/docs_projectinca/src/assets/black_threefold.png b/docs_projectinca/src/assets/black_threefold.png
deleted file mode 100644
index ae46096..0000000
Binary files a/docs_projectinca/src/assets/black_threefold.png and /dev/null differ
diff --git a/docs_projectinca/src/assets/hero_host3.png b/docs_projectinca/src/assets/hero_host3.png
deleted file mode 100644
index 6fc9e4c..0000000
Binary files a/docs_projectinca/src/assets/hero_host3.png and /dev/null differ
diff --git a/docs_projectinca/src/assets/houston.webp b/docs_projectinca/src/assets/houston.webp
deleted file mode 100644
index 930c164..0000000
Binary files a/docs_projectinca/src/assets/houston.webp and /dev/null differ
diff --git a/docs_projectinca/src/assets/inca_background.webp b/docs_projectinca/src/assets/inca_background.webp
deleted file mode 100644
index 57e5f5c..0000000
Binary files a/docs_projectinca/src/assets/inca_background.webp and /dev/null differ
diff --git a/docs_projectinca/src/content/config.ts b/docs_projectinca/src/content/config.ts
deleted file mode 100644
index 45f60b0..0000000
--- a/docs_projectinca/src/content/config.ts
+++ /dev/null
@@ -1,6 +0,0 @@
-import { defineCollection } from 'astro:content';
-import { docsSchema } from '@astrojs/starlight/schema';
-
-export const collections = {
- docs: defineCollection({ schema: docsSchema() }),
-};
diff --git a/docs_projectinca/src/content/docs/guides/connect_the_nodes.md b/docs_projectinca/src/content/docs/guides/connect_the_nodes.md
deleted file mode 100644
index 3d3d137..0000000
--- a/docs_projectinca/src/content/docs/guides/connect_the_nodes.md
+++ /dev/null
@@ -1,14 +0,0 @@
----
-title: Connect the Nodes
-description: How to connect the nodes to the grid
----
-
-Once you've received your INCA nodes, it takes a few minutes to connect it:
-
-- Plug the Ethernet cable in your INCA node and connect the cable to your router
-- Plug the power cable in your INCA node and connect the cable to a power outlet
-- Push the power on button to start the node
-
-The node will automatically connect to the grid. That's it!
-
-The node is self-healing and you will need miminal if any maintenance.
\ No newline at end of file
diff --git a/docs_projectinca/src/content/docs/guides/create_farm.md b/docs_projectinca/src/content/docs/guides/create_farm.md
deleted file mode 100644
index b38cce0..0000000
--- a/docs_projectinca/src/content/docs/guides/create_farm.md
+++ /dev/null
@@ -1,22 +0,0 @@
----
-title: Create a Farm
-description: How to create a Farm with ThreeFold Connect
----
-
-## Introduction
-
-We cover the steps to create a farm with the ThreeFold Connect app.
-
-## Steps
-
-Follow those steps to create a farm:
-
-- Open the main menu of the app and click on `Farming`
-- Next to `Farms` click on the plus button
-- Choose a farm name and click `Submit`
-
-## Farm ID
-
-Take note of the farm ID, it will be requested when you order your INCA nodes.
-
-Read more in the next section.
\ No newline at end of file
diff --git a/docs_projectinca/src/content/docs/guides/get_inca_nodes.md b/docs_projectinca/src/content/docs/guides/get_inca_nodes.md
deleted file mode 100644
index 0afe505..0000000
--- a/docs_projectinca/src/content/docs/guides/get_inca_nodes.md
+++ /dev/null
@@ -1,14 +0,0 @@
----
-title: Get INCA Nodes
-description: How to get INCA nodes
----
-
-There are different models of INCA nodes available.
-
-Visit the [official INCA website](https://internetcapacity.org/farming/) to choose and buy INCA nodes.
-
-## Input Your Farm ID
-
-When you buy an INCA node, you will be requested to enter your farm ID.
-
-For more information on this, read the [previous section](/guides/create_farm).
diff --git a/docs_projectinca/src/content/docs/guides/manage_rewards.md b/docs_projectinca/src/content/docs/guides/manage_rewards.md
deleted file mode 100644
index c3c2cd2..0000000
--- a/docs_projectinca/src/content/docs/guides/manage_rewards.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: Manage Rewards
-description: How to manage farming rewards
----
-
-Farming rewards will be sent automatically to your ThreeFold Connect wallet.
-
-Simply visit your ThreeFold Connect wallet to see your rewards.
\ No newline at end of file
diff --git a/docs_projectinca/src/content/docs/guides/threefold_connect.md b/docs_projectinca/src/content/docs/guides/threefold_connect.md
deleted file mode 100644
index f1871e2..0000000
--- a/docs_projectinca/src/content/docs/guides/threefold_connect.md
+++ /dev/null
@@ -1,32 +0,0 @@
----
-title: ThreeFold Connect
-description: How to install the ThreeFold Connect app
----
-
-## Introduction
-
-In this section, we cover the basics and advanced features of the ThreeFold Connect app.
-
-## Installation
-
-We cover the steps to install the app:
-
-- Download the app
- - [Android](https://play.google.com/store/apps/details?id=org.jimber.threebotlogin&hl=en&gl=US)
- - [iOS](https://apps.apple.com/us/app/threefold-connect/id1459845885)
-- Open the app
-- Click on `SIGN UP`
-- Choose a ThreeFold Connect ID
-- Enter your email address
-- Take note of the mnemonics
-- Open the confirmation email and
-- Choose a 4-digit pin
-
-## Create a Wallet
-
-We cover the steps to create a wallet:
-
-- In the menu, click on `Wallet`
-- Click on `Create Initial Wallet`
-
-Once you've installed ThreeFold Connect and created a wallet, create a farm. More on this in the next section!
\ No newline at end of file
diff --git a/docs_projectinca/src/content/docs/index.mdx b/docs_projectinca/src/content/docs/index.mdx
deleted file mode 100644
index 517c711..0000000
--- a/docs_projectinca/src/content/docs/index.mdx
+++ /dev/null
@@ -1,36 +0,0 @@
----
-title: Welcome to the Project INCA Docs
-description: Get started building your docs site with Starlight.
-template: splash
-hero:
- tagline: Learn how to deploy INCA nodes to earn rewards!
- image:
- file: ../../assets/hero_host3.png
- actions:
- - text: Get Started
- link: /start_here/getting_started/
- icon: right-arrow
- variant: primary
- - text: Visit the website
- link: https://internetcapacity.org/
- icon: external
----
-
-import { Card, CardGrid } from '@astrojs/starlight/components';
-
-## Become a Cloud Service Provider
-
-
-
- Read the [INCA Docs](/start_here/getting_started) to learn how to set up your INCA nodes and to know more about the ThreeFold ecosystem.
-
-
- Get INCA nodes at the [official INCA website](https://internetcapacity.org/farming/) to provide compute, storage and network resources to the world.
-
-
- Project INCA is the fourth version of the [ThreeFold Grid](https://threefold.io/) available in 60+ countries with thousands of nodes!
-
-
- When you deploy INCA nodes, you contribute to the growth of the ThreeFold Grid and earn INCA rewards!
-
-
diff --git a/docs_projectinca/src/content/docs/legal/privacy_policy.md b/docs_projectinca/src/content/docs/legal/privacy_policy.md
deleted file mode 100644
index 6c1acfd..0000000
--- a/docs_projectinca/src/content/docs/legal/privacy_policy.md
+++ /dev/null
@@ -1,115 +0,0 @@
----
-title: Privacy Policy
-description: Privacy Policy concerning Project INCA
----
-
-*This privacy policy will explain how ThreeFold Movement ("companies", "we", or "us") uses the personal data we collect from you when you use our websites, including the Project INCA website.*
-
-### What data do we collect?
-
-All websites using the ThreeFold Movement Privacy Policy do not collect any data on a personal level by default. All data being processed is anonymized. When signing up for our newsletter we collect your: *email address*.
-
-**How do we collect your data?**
-
-Browsing data:
-We automatically collect data and process data when you use or view our website via your browser's cookies.
-
-Newsletter Signups:
-Collected only with your permission through our sign-up form that uses a double opt-in mechanism for you to explicitly accept.
-
-### How will we use your data?
-
-We use this information to monitor and analyze your use of our website and for the website's technical administration, to increase our website's functionality and user-friendliness, and to better tailor it to our visitors needs.
-
-If you agree, our companies will share your data with the following partner companies so that they may offer you or us their products and services:
-
-* Matomo: offers us services relating to monitoring and measuring website traffic and access, creating user navigation reports, etc. All information processed here is anonymized. We run this service within our own environments. The data being processed does not leave our servers and is not shared with any thrid parties.
-
-* Mailerlite: offers us services relating newsletter sending and monitoring.
-
-**We do not track individual IP's or any other personal data.**
-
-The aforementioned processors operate independently from us and have their own privacy policy, which we strongly suggest you review. These processors may use the information collected through their services to evaluate visitors’ activity, as set out in their respective privacy policies.
-
-### How do we store your data?
-
-We store the anonmyzed data in Matomo for us to research usage and improve user experience on our websites.
-We store email addresses in Mailerlite's system.
-
-### Marketing
-
-We will not use your information for any (re)marketing reasons, nor send you information about products and/or services of ours or any partner companies unless you explicitly agreed to signing up for our newsletter.
-
-### What are your data protection rights?
-
-We would like to make sure you are fully aware of all of your data protection rights. Every user is entitled to the following:
-
-#### The right to access
-
-You have the right to request from us copies of your personal data. We may charge you a small fee for this service.
-
-#### The right to rectification
-
-You have the right to request that we correct any information you believe is inaccurate. You also have the right to request us to complete information you believe is incomplete.
-
-#### The right to erasure
-
-You have the right to request that we erase your personal data, under certain conditions.
-
-#### The right to restrict processing
-
-You have the right to request that we restrict the processing of your personal data, under certain conditions.
-
-#### The right to object to processing
-
-You have the right to object to our companies' processing of your personal data, under certain conditions.
-
-#### The right to data portability
-
-You have the right to request that we transfer the data that we have collected to another organization, or directly to you, under certain conditions.
-
-If you make a request, we have one month to respond to you. If you would like to exercise any of these rights, please contact us:
-
-* email: dataprivacy@threefold.io
-
-### What are cookies?
-
-Cookies are text files placed on your computer to collect standard Internet log information and visitor behavior information. When you visit our websites, we may collect information from you automatically through cookies or similar technology.
-
-For further information, visit: http://allaboutcookies.org/
-
-### How do we use cookies?
-
-We use cookies in a range of ways to improve your experience on our website, including:
-
-* understanding how you use our website
-
-* for the websites technical administration
-
-### What types of cookies do we use?
-
-There are a number of different types of cookies, however, our websites use:
-
-* Functionality - Our companies use these cookies so that we recognize you on our website and remember your previously selected preferences. These could include what language you prefer and the location you are in. A mix of first-party and third-party cookies are used.
-
-* No Advertising - Our companies use these cookies to collect information about your visit to our website, the content you viewed, the links you followed and information about your browser, device, and your IP address. However, we will not share this data with third parties for advertising purposes.
-
-* Analytics cookies - Our companies use these to monitor how users reached the Site, and how they interact with and move around once on the Site. These cookies let us know what features on the Site are working the best and what features on the Site can be improved.
-
-### How to manage cookies
-
-You can set your browser to not accept cookies, and the above website tells you how to remove cookies from your browser. However, in a few cases, some of our website features may not function as a result.
-
-### Privacy policies of other websites
-
-Our website contains links to other websites. Our privacy policy applies only to our website, so if you click on a link to another website, you should read their privacy policy.
-
-### Changes to our privacy policy
-
-We keep our privacy policy under regular review and places any updates on this web page.
-
-### How to contact us
-
-If you have any questions about our privacy policy, the data we hold on you, or you would like to exercise one of your data protection rights, please do not hesitate to contact us.
-
-Email us at: dataprivacy@threefold.io
\ No newline at end of file
diff --git a/docs_projectinca/src/content/docs/legal/terms_and_conditions.md b/docs_projectinca/src/content/docs/legal/terms_and_conditions.md
deleted file mode 100644
index befc138..0000000
--- a/docs_projectinca/src/content/docs/legal/terms_and_conditions.md
+++ /dev/null
@@ -1,154 +0,0 @@
----
-title: Terms and Conditions
-description: Terms and Conditions for the Project INCA
----
-
-These Terms of Use constitute a legally binding agreement made between you, whether personally or on behalf of an entity (“you”) and ThreeFold, doing business as ThreeFold (“ThreeFold“, “we”, “us”, or “our”), concerning your access to and use of the threefold related websites:
-
-The project INCA website, websites/wikis/forums ending with threefold.io, threefold.me, grid.tf, threefold.tech, TFT.com, freeflownation.org, 3bot.org, incubaid.com or consciousinternet.org or any other website as used/promoted by the ThreeFold Foundation or any other site as originating from our open-source git repository on https://github.com/threefoldfoundation, as well as any other media form, media channel, forum, mobile website or mobile application related, linked, or otherwise connected thereto (collectively, the “Site”).
-
-You agree that by accessing the Site, you have read, understood, and agreed to be bound by all of these Terms of Use.
-
-IF YOU DO NOT AGREE WITH ALL OF THESE TERMS OF USE, THEN YOU ARE EXPRESSLY PROHIBITED FROM USING THE SITE AND YOU MUST DISCONTINUE USE IMMEDIATELY.
-
-Supplemental terms and conditions or documents that may be posted on the Site from time to time are hereby expressly incorporated herein by reference. We reserve the right, in our sole discretion, to make changes or modifications to these Terms of Use at any time and for any reason. We will alert you about any changes by updating the “Last updated” date of these Terms of Use, and you waive any right to receive specific notice of each such change. It is your responsibility to periodically review these Terms of Use to stay informed of updates. You will be subject to, and will be deemed to have been made aware of and to have accepted, the changes in any revised Terms of Use by your continued use of the Site after the date such revised Terms of Use are posted.
-
-The information provided on the Site is not intended for distribution to or use by any person or entity in any jurisdiction or country where such distribution or use would be contrary to law or regulation or which would subject us to any registration requirement within such jurisdiction or country. Accordingly, those persons who choose to access the Site from other locations do so on their own initiative and are solely responsible for compliance with local laws, if and to the extent local laws are applicable.
-
-The Site is intended for users who are at least 18 years old. Persons under the age of 18 are not permitted to use or register for the Site.
-
-**INTELLECTUAL PROPERTY RIGHTS**
-
-Unless otherwise indicated, the Site is our proprietary property and all source code, databases, functionality, software, website designs, audio, video, text, photographs, and graphics on the Site (collectively, the “Content”) and the trademarks, service marks, and logos contained therein (the “Marks”) are owned or controlled by us or licensed to us, and are protected by copyright and trademark laws and various other intellectual property rights and EU competition laws, foreign jurisdictions, and international conventions. The Content and the Marks are provided on the Site “AS IS” for your information and personal use only. Except as expressly provided in these Terms of Use, no part of the Site and no Content or Marks may be copied, reproduced, aggregated, republished, uploaded, posted, publicly displayed, encoded, translated, transmitted, distributed, sold, licensed, or otherwise exploited for any commercial purpose whatsoever, without our express prior written permission.
-
-Provided that you are eligible to use the Site, you are granted a limited license to access and use the Site and to download or print a copy of any portion of the Content to which you have properly gained access solely for your personal, non-commercial use. We reserve all rights not expressly granted to you in and to the Site, the Content and the Marks.
-
-**USER REPRESENTATIONS**
-
-By using the Site, you represent and warrant that: (1) all registration information you submit will be true, accurate, current, and complete; (2) you will maintain the accuracy of such information and promptly update such registration information as necessary; (3) you have the legal capacity and you agree to comply with these Terms of Use; (4) you are not a minor in the jurisdiction in which you reside; (5) you will not access the Site through automated or non-human means, whether through a bot, script, or otherwise; (6) you will not use the Site for any illegal or unauthorized purpose; and (7) your use of the Site will not violate any applicable law or regulation.
-
-If you provide any information that is untrue, inaccurate, not current, or incomplete, we have the right to suspend or terminate your account and refuse any and all current or future use of the Site (or any portion thereof).
-
-**USER REGISTRATION**
-
-You may be required to register with the Site. You agree to keep your password confidential and will be responsible for all use of your account and password. We reserve the right to remove, reclaim, or change a username you select if we determine, in our sole discretion, that such username is inappropriate, obscene, or otherwise objectionable.
-
-**PROHIBITED ACTIVITIES**
-
-You may not access or use the Site for any purpose other than that for which we make the Site available. The Site may not be used in connection with any commercial endeavors except those that are specifically endorsed or approved by us.
-
-As a user of the Site, you agree not to:
-
-- Systematically retrieve data or other content from the Site to create or compile, directly or indirectly, a collection, compilation, database, or directory without written permission from us.
-- Circumvent, disable, or otherwise interfere with security-related features of the Site, including features that prevent or restrict the use or copying of any Content or enforce limitations on the use of the Site and/or the Content contained therein.
-- Engage in unauthorized framing of or linking to the Site.
-- Trick, defraud, or mislead us and other users, especially in any attempt to learn sensitive account information such as user passwords.
-- Engage in any automated use of the system, such as using scripts to send comments or messages, or using any data mining, robots, or similar data gathering and extraction tools.
-- Interfere with, disrupt, or create an undue burden on the Site or the networks or services connected to the Site.
-- Use the Site as part of any effort to compete with us or otherwise use the Site and/or the Content for any revenue-generating endeavor or commercial enterprise.
-- Decipher, decompile, disassemble, or reverse engineer any of the software comprising or in any way making up a part of the Site.
-- Upload or transmit (or attempt to upload or to transmit) viruses, Trojan horses, or other material, including excessive use of capital letters and spamming (continuous posting of repetitive text), that interferes with any party’s uninterrupted use and enjoyment of the Site or modifies, impairs, disrupts, alters, or interferes with the use, features, functions, operation, or maintenance of the Site.
-- Upload or transmit (or attempt to upload or to transmit) any material that acts as a passive or active information collection or transmission mechanism, including without limitation, clear graphics interchange formats (“gifs”), 1×1 pixels, web bugs, cookies, or other similar devices (sometimes referred to as “spyware” or “passive collection mechanisms” or “pcms”).
-- Except as may be the result of standard search engine or Internet browser usage, use, launch, develop, or distribute any automated system, including without limitation, any spider, robot, cheat utility, scraper, or offline reader that accesses the Site, or using or launching any unauthorized script or other software.
-- Use the Site in a manner inconsistent with any applicable laws or regulations.
-
-**USER GENERATED CONTRIBUTIONS**
-
-The Site may invite you to chat, contribute to, or participate in blogs, message boards, online forums, and other functionality, and may provide you with the opportunity to create, submit, post, display, transmit, perform, publish, distribute, or broadcast content and materials to us or on the Site, including but not limited to text, writings, video, audio, photographs, graphics, comments, suggestions, or personal information or other material (collectively, “Contributions”). Contributions may be viewable by other users of the Site and through third-party websites. As such, any Contributions you transmit may be treated as non-confidential and non-proprietary. When you create or make available any Contributions, you thereby represent and warrant that:
-
-- The creation, distribution, transmission, public display, or performance, and the accessing, downloading, or copying of your Contributions do not and will not infringe the proprietary rights, including but not limited to the copyright, patent, trademark, trade secret, or moral rights of any third party.
-- You are the creator and owner of or have the necessary licenses, rights, consents, releases, and permissions to use and to authorize us, the Site, and other users of the Site to use your Contributions in any manner contemplated by the Site and these Terms of Use.
-- You have the written consent, release, and/or permission of each and every identifiable individual person in your Contributions to use the name or likeness of each and every such identifiable individual person to enable inclusion and use of your Contributions in any manner contemplated by the Site and these Terms of Use.
-- Your Contributions are not false, inaccurate, or misleading.
-- Your Contributions are not unsolicited or unauthorized advertising, promotional materials, pyramid schemes, chain letters, spam, mass mailings, or other forms of solicitation.
-- Your Contributions are not obscene, lewd, lascivious, filthy, violent, harassing, libelous, slanderous, or otherwise objectionable (as determined by us).
-- Your Contributions do not ridicule, mock, disparage, intimidate, or abuse anyone. 98 Your Contributions do not advocate the violent overthrow of any government or incite, encourage, or threaten physical harm against another.
-- Your Contributions do not violate any applicable law, regulation, or rule.
-- Your Contributions do not violate the privacy or publicity rights of any third party.
-- Your Contributions do not contain any material that solicits personal information from anyone under the age of 18 or exploits people under the age of 18 in a sexual or violent manner.
-- Your Contributions do not violate any federal or state law concerning child pornography, or otherwise intended to protect the health or well-being of minors;
-- Your Contributions do not include any offensive comments that are connected to race, national origin, gender, sexual preference, or physical handicap.
-- Your Contributions do not otherwise violate, or link to material that violates, any provision of these Terms of Use, or any applicable law or regulation.
-- Any use of the Site in violation of the foregoing violates these Terms of Use and may result in, among other things, termination or suspension of your rights to use the Site. CONTRIBUTION LICENSE
-
-By posting your Contributions to any part of the Site or making Contributions accessible to the Site by linking your account from the Site to any of your social networking accounts, you automatically grant, and you represent and warrant that you have the right to grant, to us an unrestricted, unlimited, irrevocable, perpetual, non-exclusive, transferable, royalty-free, fully-paid, worldwide right, and license to host, use, copy, reproduce, disclose, sell, resell, publish, broadcast, retitle, archive, store, cache, publicly perform, publicly display, reformat, translate, transmit, excerpt (in whole or in part), and distribute such Contributions (including, without limitation, your image and voice) for any purpose, commercial, advertising, or otherwise, and to prepare derivative works of, or incorporate into other works, such Contributions, and grant and authorize sublicenses of the foregoing. The use and distribution may occur in any media formats and through any media channels.
-
-This license will apply to any form, media, or technology now known or hereafter developed, and includes our use of your name, company name, and franchise name, as applicable, and any of the trademarks, service marks, trade names, logos, and personal and commercial images you provide. You waive all moral rights in your Contributions, and you warrant that moral rights have not otherwise been asserted in your Contributions.
-
-We do not assert any ownership over your Contributions. You retain full ownership of all of your Contributions and any intellectual property rights or other proprietary rights associated with your Contributions. We are not liable for any statements or representations in your Contributions provided by you in any area on the Site. You are solely responsible for your Contributions to the Site and you expressly agree to exonerate us from any and all responsibility and to refrain from any legal action against us regarding your Contributions.
-
-We have the right, in our sole and absolute discretion, (1) to edit, redact, or otherwise change any Contributions; (2) to re-categorize any Contributions to place them in more appropriate locations on the Site; and (3) to pre-screen or delete any Contributions at any time and for any reason, without notice. We have no obligation to monitor your Contributions.
-
-**SOCIAL MEDIA**
-
-As part of the functionality of the Site, you may link your account with online accounts you have with third-party service providers (each such account, a “Third-Party Account”) by either: (1) providing your Third-Party Account login information through the Site; or (2) allowing us to access your Third-Party Account, as is permitted under the applicable terms and conditions that govern your use of each Third-Party Account. You represent and warrant that you are entitled to disclose your Third-Party Account login information to us and/or grant us access to your Third-Party Account, without breach by you of any of the terms and conditions that govern your use of the applicable Third-Party Account, and without obligating us to pay any fees or making us subject to any usage limitations imposed by the third-party service provider of the Third-Party Account. By granting us access to any Third-Party Accounts, you understand that (1) we may access, make available, and store (if applicable) any content that you have provided to and stored in your Third-Party Account (the “Social Network Content”) so that it is available on and through the Site via your account, including without limitation any friend lists and (2) we may submit to and receive from your Third-Party Account additional information to the extent you are notified when you link your account with the Third-Party Account. Depending on the Third-Party Accounts you choose and subject to the privacy settings that you have set in such Third-Party Accounts, personally identifiable information that you post to your Third-Party Accounts may be available on and through your account on the Site. Please note that if a Third-Party Account or associated service becomes unavailable or our access to such Third Party Account is terminated by the third-party service provider, then Social Network Content may no longer be available on and through the Site. You will have the ability to disable the connection between your account on the Site and your Third-Party Accounts at any time.
-
-PLEASE NOTE THAT YOUR RELATIONSHIP WITH THE THIRD-PARTY SERVICE PROVIDERS ASSOCIATED WITH YOUR THIRD-PARTY ACCOUNTS IS GOVERNED SOLELY BY YOUR AGREEMENT(S) WITH SUCH THIRD-PARTY SERVICE PROVIDERS.
-
-We make no effort to review any Social Network Content for any purpose, including but not limited to, for accuracy, legality, or non-infringement, and we are not responsible for any Social Network Content. You acknowledge and agree that we may access your email address book associated with a Third-Party Account and your contacts list stored on your mobile device or tablet computer solely for purposes of identifying and informing you of those contacts who have also registered to use the Site. You can deactivate the connection between the Site and your Third-Party Account by contacting us using the contact information below or through your account settings (if applicable). We will attempt to delete any information stored on our servers that was obtained through such Third-Party Account, except the username and profile picture that become associated with your account.
-
-**SUBMISSIONS**
-
-You acknowledge and agree that any questions, comments, suggestions, ideas, feedback, or other information regarding the Site (“Submissions”) provided by you to us are non-confidential and shall become our sole property. We shall own exclusive rights, including all intellectual property rights, and shall be entitled to the unrestricted use and dissemination of these Submissions for any lawful purpose, commercial or otherwise, without acknowledgment or compensation to you. You hereby waive all moral rights to any such Submissions, and you hereby warrant that any such Submissions are original with you or that you have the right to submit such Submissions. You agree there shall be no recourse against us for any alleged or actual infringement or misappropriation of any proprietary right in your Submissions.
-
-**THIRD-PARTY WEBSITES AND CONTENT**
-
-The Site may contain (or you may be sent via the Site) links to other websites (“Third-Party Websites”) as well as articles, photographs, text, graphics, pictures, designs, music, sound, video, information, applications, software, and other content or items belonging to or originating from third parties (“Third-Party Content”). Such Third-Party Websites and Third-Party Content are not investigated, monitored, or checked for accuracy, appropriateness, or completeness by us, and we are not responsible for any Third-Party Websites accessed through the Site or any Third-Party Content posted on, available through, or installed from the Site, including the content, accuracy, offensiveness, opinions, reliability, privacy practices, or other policies of or contained in the Third-Party Websites or the Third-Party Content. Inclusion of, linking to, or permitting the use or installation of any Third-Party Websites or any Third-Party Content does not imply approval or endorsement thereof by us. If you decide to leave the Site and access the Third-Party Websites or to use or install any Third-Party Content, you do so at your own risk, and you should be aware these Terms of Use no longer govern. You should review the applicable terms and policies, including privacy and data gathering practices, of any website to which you navigate from the Site or relating to any applications you use or install from the Site. Any purchases you make through Third-Party Websites will be through other websites and from other companies, and we take no responsibility whatsoever in relation to such purchases which are exclusively between you and the applicable third party. You agree and acknowledge that we do not endorse the products or services offered on Third-Party Websites and you shall hold us harmless from any harm caused by your purchase of such products or services. Additionally, you shall hold us harmless from any losses sustained by you or harm caused to you relating to or resulting in any way from any Third-Party Content or any contact with Third-Party Websites.
-
-**SITE MANAGEMENT**
-
-We reserve the right, but not the obligation, to: (1) monitor the Site for violations of these Terms of Use; (2) take appropriate legal action against anyone who, in our sole discretion, violates the law or these Terms of Use, including without limitation, reporting such user to law enforcement authorities; (3) in our sole discretion and without limitation, refuse, restrict access to, limit the availability of, or disable (to the extent technologically feasible) any of your Contributions or any portion thereof; (4) in our sole discretion and without limitation, notice, or liability, to remove from the Site or otherwise disable all files and content that are excessive in size or are in any way burdensome to our systems; and (5) otherwise manage the Site in a manner designed to protect our rights and property and to facilitate the proper functioning of the Site.
-
-**PRIVACY POLICY**
-
-We care about data privacy and security. Please review our Privacy Policy.
-
-By using the Site, you agree to be bound by our Privacy Policy, which is incorporated into these Terms of Use. Please be advised the Site is hosted in the United States. If you access the Site from the European Union, Asia, or any other region of the world with laws or other requirements governing personal data collection, use, or disclosure that differ from applicable laws in the United States, then through your continued use of the Site, you are transferring your data to the United States, and you expressly consent to have your data transferred to and processed in the United States. Further, we do not knowingly accept, request, or solicit information from children or knowingly market to children. Therefore, in accordance with the U.S. Children’s Online Privacy Protection Act, if we receive actual knowledge that anyone under the age of 13 has provided personal information to us without the requisite and verifiable parental consent, we will delete that information from the Site as quickly as is reasonably practical.
-
-**TERM AND TERMINATION**
-
-These Terms of Use shall remain in full force and effect while you use the Site. WITHOUT LIMITING ANY OTHER PROVISION OF THESE TERMS OF USE, WE RESERVE THE RIGHT TO, IN OUR SOLE DISCRETION AND WITHOUT NOTICE OR LIABILITY, DENY ACCESS TO AND USE OF THE SITE (INCLUDING BLOCKING CERTAIN IP ADDRESSES), TO ANY PERSON FOR ANY REASON OR FOR NO REASON, INCLUDING WITHOUT LIMITATION FOR BREACH OF ANY REPRESENTATION, WARRANTY, OR COVENANT CONTAINED IN THESE TERMS OF USE OR OF ANY APPLICABLE LAW OR REGULATION. WE MAY TERMINATE YOUR USE OR PARTICIPATION IN THE SITE OR DELETE YOUR ACCOUNT AND ANY CONTENT OR INFORMATION THAT YOU POSTED AT ANY TIME, WITHOUT WARNING, IN OUR SOLE DISCRETION.
-
-If we terminate or suspend your account for any reason, you are prohibited from registering and creating a new account under your name, a fake or borrowed name, or the name of any third party, even if you may be acting on behalf of the third party. In addition to terminating or suspending your account, we reserve the right to take appropriate legal action, including without limitation pursuing civil, criminal, and injunctive redress.
-
-**MODIFICATIONS AND INTERRUPTIONS**
-
-We reserve the right to change, modify, or remove the contents of the Site at any time or for any reason at our sole discretion without notice. However, we have no obligation to update any information on our Site. We also reserve the right to modify or discontinue all or part of the Site without notice at any time. We will not be liable to you or any third party for any modification, price change, suspension, or discontinuance of the Site.
-
-We cannot guarantee the Site will be available at all times. We may experience hardware, software, or other problems or need to perform maintenance related to the Site, resulting in interruptions, delays, or errors. We reserve the right to change, revise, update, suspend, discontinue, or otherwise modify the Site at any time or for any reason without notice to you. You agree that we have no liability whatsoever for any loss, damage, or inconvenience caused by your inability to access or use the Site during any downtime or discontinuance of the Site. Nothing in these Terms of Use will be construed to obligate us to maintain and support the Site or to supply any corrections, updates, or releases in connection therewith.
-
-**GOVERNING LAW**
-
-These Terms of Use and your use of the Site are governed by and construed in accordance with the laws of Belgium, without regard to its conflict of law principles. DISPUTE RESOLUTION
-
-Any legal action of whatever nature brought by either you or us (collectively, the “Parties” and individually, a “Party”) shall be commenced or prosecuted in courts located in Belgium, Ghent, and the Parties hereby consent to, and waive all defenses of lack of personal jurisdiction and forum non conveniens with respect to venue and jurisdiction in such state and federal courts. Application of the United Nations Convention on Contracts for the International Sale of Goods and the Uniform Computer Information Transaction Act (UCITA) are excluded from these Terms of Use. In no event shall any claim, action, or proceeding brought by either Party related in any way to the Site be commenced more than one (1) years after the cause of action arose.
-
-**CORRECTIONS**
-
-There may be information on the Site that contains typographical errors, inaccuracies, or omissions, including descriptions, pricing, availability, and various other information. We reserve the right to correct any errors, inaccuracies, or omissions and to change or update the information on the Site at any time, without prior notice.
-
-**DISCLAIMER**
-
-THE SITE IS PROVIDED ON AN AS-IS AND AS-AVAILABLE BASIS. YOU AGREE THAT YOUR USE OF THE SITE AND OUR SERVICES WILL BE AT YOUR SOLE RISK. TO THE FULLEST EXTENT PERMITTED BY LAW, WE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, IN CONNECTION WITH THE SITE AND YOUR USE THEREOF, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. WE MAKE NO WARRANTIES OR REPRESENTATIONS ABOUT THE ACCURACY OR COMPLETENESS OF THE SITE’S CONTENT OR THE CONTENT OF ANY WEBSITES LINKED TO THE SITE AND WE WILL ASSUME NO LIABILITY OR RESPONSIBILITY FOR ANY (1) ERRORS, MISTAKES, OR INACCURACIES OF CONTENT AND MATERIALS, (2) PERSONAL INJURY OR PROPERTY DAMAGE, OF ANY NATURE WHATSOEVER, RESULTING FROM YOUR ACCESS TO AND USE OF THE SITE, (3) ANY UNAUTHORIZED ACCESS TO OR USE OF OUR SECURE SERVERS AND/OR ANY AND ALL PERSONAL INFORMATION AND/OR FINANCIAL INFORMATION STORED THEREIN, (4) ANY INTERRUPTION OR CESSATION OF TRANSMISSION TO OR FROM THE SITE, (5) ANY BUGS, VIRUSES, TROJAN HORSES, OR THE LIKE WHICH MAY BE TRANSMITTED TO OR THROUGH THE SITE BY ANY THIRD PARTY, AND/OR (6) ANY ERRORS OR OMISSIONS IN ANY CONTENT AND MATERIALS OR FOR ANY LOSS OR DAMAGE OF ANY KIND INCURRED AS A RESULT OF THE USE OF ANY CONTENT POSTED, TRANSMITTED, OR OTHERWISE MADE AVAILABLE VIA THE SITE. WE DO NOT WARRANT, ENDORSE, GUARANTEE, OR ASSUME RESPONSIBILITY FOR ANY PRODUCT OR SERVICE ADVERTISED OR OFFERED BY A THIRD PARTY THROUGH THE SITE, ANY HYPERLINKED WEBSITE, OR ANY WEBSITE OR MOBILE APPLICATION FEATURED IN ANY BANNER OR OTHER ADVERTISING, AND WE WILL NOT BE A PARTY TO OR IN ANY WAY BE RESPONSIBLE FOR MONITORING ANY TRANSACTION BETWEEN YOU AND ANY THIRD-PARTY PROVIDERS OF PRODUCTS OR SERVICES. AS WITH THE PURCHASE OF A PRODUCT OR SERVICE THROUGH ANY MEDIUM OR IN ANY ENVIRONMENT, YOU SHOULD USE YOUR BEST JUDGMENT AND EXERCISE CAUTION WHERE APPROPRIATE. LIMITATIONS OF LIABILITY
-
-IN NO EVENT WILL WE OR OUR DIRECTORS, EMPLOYEES, OR AGENTS BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, EXEMPLARY, INCIDENTAL, SPECIAL, OR PUNITIVE DAMAGES, INCLUDING LOST PROFIT, LOST REVENUE, LOSS OF DATA, OR OTHER DAMAGES ARISING FROM YOUR USE OF THE SITE, EVEN IF WE HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. NOTWITHSTANDING ANYTHING TO THE CONTRARY CONTAINED HEREIN, OUR LIABILITY TO YOU FOR ANY CAUSE WHATSOEVER AND REGARDLESS OF THE FORM OF THE ACTION, WILL AT ALL TIMES BE LIMITED TO $1.00 USD. CERTAIN STATE LAWS DO NOT ALLOW LIMITATIONS ON IMPLIED WARRANTIES OR THE EXCLUSION OR LIMITATION OF CERTAIN DAMAGES. IF THESE LAWS APPLY TO YOU, SOME OR ALL OF THE ABOVE DISCLAIMERS OR LIMITATIONS MAY NOT APPLY TO YOU, AND YOU MAY HAVE ADDITIONAL RIGHTS. INDEMNIFICATION
-
-You agree to defend, indemnify, and hold us harmless, including our subsidiaries, affiliates, and all of our respective officers, agents, partners, and employees, from and against any loss, damage, liability, claim, or demand, including reasonable attorneys’ fees and expenses, made by any third party due to or arising out of: (1) your Contributions; (2) use of the Site; (3) breach of these Terms of Use; (4) any breach of your representations and warranties set forth in these Terms of Use; (5) your violation of the rights of a third party, including but not limited to intellectual property rights; or (6) any overt harmful act toward any other user of the Site with whom you connected via the Site. Notwithstanding the foregoing, we reserve the right, at your expense, to assume the exclusive defense and control of any matter for which you are required to indemnify us, and you agree to cooperate, at your expense, with our defense of such claims. We will use reasonable efforts to notify you of any such claim, action, or proceeding which is subject to this indemnification upon becoming aware of it.
-
-**USER DATA**
-
-We will maintain certain data that you transmit to the Site for the purpose of managing the performance of the Site, as well as data relating to your use of the Site. Although we perform regular routine backups of data, you are solely responsible for all data that you transmit or that relates to any activity you have undertaken using the Site. You agree that we shall have no liability to you for any loss or corruption of any such data, and you hereby waive any right of action against us arising from any such loss or corruption of such data.
-
-**ELECTRONIC COMMUNICATIONS, TRANSACTIONS, AND SIGNATURES**
-
-Visiting the Site, sending us emails, and completing online forms constitute electronic communications. You consent to receive electronic communications, and you agree that all agreements, notices, disclosures, and other communications we provide to you electronically, via email and on the Site, satisfy any legal requirement that such communication be in writing. YOU HEREBY AGREE TO THE USE OF ELECTRONIC SIGNATURES, CONTRACTS, ORDERS, AND OTHER RECORDS, AND TO ELECTRONIC DELIVERY OF NOTICES, POLICIES, AND RECORDS OF TRANSACTIONS INITIATED OR COMPLETED BY US OR VIA THE SITE. You hereby waive any rights or requirements under any statutes, regulations, rules, ordinances, or other laws in any jurisdiction which require an original signature or delivery or retention of non-electronic records, or to payments or the granting of credits by any means other than electronic means. MISCELLANEOUS
-
-These Terms of Use and any policies or operating rules posted by us on the Site or in respect to the Site constitute the entire agreement and understanding between you and us. Our failure to exercise or enforce any right or provision of these Terms of Use shall not operate as a waiver of such right or provision. These Terms of Use operate to the fullest extent permissible by law. We may assign any or all of our rights and obligations to others at any time. We shall not be responsible or liable for any loss, damage, delay, or failure to act caused by any cause beyond our reasonable control. If any provision or part of a provision of these Terms of Use is determined to be unlawful, void, or unenforceable, that provision or part of the provision is deemed severable from these Terms of Use and does not affect the validity and enforceability of any remaining provisions. There is no joint venture, partnership, employment or agency relationship created between you and us as a result of these Terms of Use or use of the Site. You agree that these Terms of Use will not be construed against us by virtue of having drafted them. You hereby waive any and all defenses you may have based on the electronic form of these Terms of Use and the lack of signing by the parties hereto to execute these Terms of Use.
-
-**CONTACT US**
-
-In order to resolve a complaint regarding the Site or to receive further information regarding use of the Site, please contact us at:
-
-- ThreeFold FCZ
-- BA1120 DMCC BUSINESS CENTRE, LEVEL NO 1, JEWELLERY & GEMPLEX 3, DUBAI, UNITED EMIRATES ARAB
-- info@threefold.io
\ No newline at end of file
diff --git a/docs_projectinca/src/content/docs/references/disclaimer.md b/docs_projectinca/src/content/docs/references/disclaimer.md
deleted file mode 100644
index 8404b1a..0000000
--- a/docs_projectinca/src/content/docs/references/disclaimer.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Disclaimer
-description: Disclaimer concerning Project INCA
----
-
-## Disclaimer
-
-> The information provided in these tutorials or any related discussion is not intended as investment advice. The purpose is to provide educational and informational content only. Investing in cryptocurrencies or any other assets carries inherent risks, and it is crucial to conduct your own research and exercise caution before making any investment decisions.
->
-> **The INCA Token** is not to be considered as a traditional investment instrument. The value of cryptocurrencies can be volatile, and there are no guarantees of profits or returns. Always be aware of the risks involved and make informed choices based on your own assessment and understanding.
\ No newline at end of file
diff --git a/docs_projectinca/src/content/docs/references/glossary.md b/docs_projectinca/src/content/docs/references/glossary.md
deleted file mode 100644
index c7f8001..0000000
--- a/docs_projectinca/src/content/docs/references/glossary.md
+++ /dev/null
@@ -1,35 +0,0 @@
----
-title: Glossary
-description: Glossary of terms from the INCA ecosystem
----
-
-## Introduction
-
-We provide definitions of terms you may encounter while exploring the INCA ecosystem.
-
-## Terms and Definitions
-
-### Compute
-
-Compute refers to the processing power and resources required to perform calculations, execute instructions, and complete tasks. In computing, compute resources include central processing units (CPUs), graphics processing units (GPUs), and other processing units that execute software instructions.
-### Network
-
-A network is a collection of interconnected devices, such as computers, servers, and peripherals, that communicate with each other to share resources and exchange data. Networks can be wired or wireless and can range from small local area networks (LANs) to large-scale wide area networks (WANs) and the internet.
-### Storage
-
-Storage refers to the holding and preservation of data in a digital form. This can include hard disk drives, solid-state drives, flash drives, and other devices that store data. Storage can be local, such as on a personal computer, or remote, such as in a cloud-based storage service.
-### Cloud
-
-Cloud refers to a model of delivering computing services over the internet, where resources such as servers, storage, and applications are provided as a service to users on-demand. Cloud computing allows users to access and use computing resources without having to manage or maintain the underlying infrastructure.
-### DePIN
-
-A DePIN (Decentralized Physical Infrastructure Network) is a protocol that uses cryptocurrency tokens to incentivize communities to build and maintain physical infrastructure networks in a decentralized manner. These networks can range from wireless and sensor networks to energy networks and cloud storage.
-### Blockchain
-
-Blockchain is a decentralized, distributed ledger technology that enables secure, transparent, and tamper-proof transactions. It is the underlying technology behind cryptocurrencies such as Bitcoin and Ethereum, but it also has applications in supply chain management, smart contracts, and other areas.
-### Operating System
-
-An operating system (OS) is a software that manages and controls a computer's hardware and software resources. It acts as an intermediary between computer hardware and user-level applications, providing services such as process management, memory management, and input/output management. Examples of operating systems include Windows, macOS, and Linux.
-### End-to-End Encryption
-
-End-to-end encryption is a method of secure communication where only the communicating parties can read the messages. It ensures that data is encrypted at the sender's end and decrypted at the receiver's end, making it unreadable to anyone intercepting the data in transit. This provides a high level of security and privacy for online communications.
\ No newline at end of file
diff --git a/docs_projectinca/src/content/docs/resources/farmerbot.md b/docs_projectinca/src/content/docs/resources/farmerbot.md
deleted file mode 100644
index cd3c60e..0000000
--- a/docs_projectinca/src/content/docs/resources/farmerbot.md
+++ /dev/null
@@ -1,255 +0,0 @@
----
-title: Farmerbot
-description: How to use the Farmerbot
----
-
-## Introduction
-
-In this guide, we show how to deploy the [Farmerbot](https://github.com/threefoldtech/tfgrid-sdk-go/tree/development/farmerbot) on a full VM running on the TFGrid.
-
-This guide can be done on bare metal or on a full VM running on the TFGrid. You need at least two 3Nodes on the same farm to make use of the Farmerbot.
-
-This version of the Farmerbot also works with ARM64. This means that if you have a Pi 3, 4, or Zero 2 with a 64 bit OS, you can download the appropriate release archive and it will work properly.
-
-Read the [Additional Information](farmerbot_information.md) section for further details concerning the Farmerbot.
-
-## Prerequisites
-
-- The TFChain account associated with the farm should have at least 5 TFT (recommended is 50 TFT)
-
-## Farmerbot Costs on the TFGrid
-
-If you run the Farmerbot on a 3Node on the TFGrid, you will have to pay TFT to deploy on that 3Node. You can run a full VM at minimum specs for the Farmerbot, that is 1vcore, 15GB of SSD storage and 512MB of RAM. Note that you can use the Planetary Network. You do not need to deploy a 3Node with IPv4. The cost on main net for this kind of workload is around 0.175TFT/hour (as of the date 11-07-23).
-
-Next to that, you will have to pay the transaction fees every time the Farmerbot has to wake up or shut down a node. This means that you need some TFT on the account tied to the twin of your farm.
-
-For the periodic wakeups, each node in the farm is shut down and powered on once a day, i.e. 30 times per month. Also, there is 10 random wakeups per month for each node. This means that each node is turned off and on 40 times per month in average. In that case, the average cost per month to power on nodes and shut them back down equals:
-
-> average transaction fees cost per month = 0.001 TFT (extrinsic fee) * amount of nodes * 40 * 2 (1 for powering down, one for powering up)
-
-## Enable Wake-On-Lan
-
-For a 3Node to work properly with the Farmerbot, the parameter wake-on-lan must be enabled. Enabling wake-on-lan on your 3Node may differ depending on your computer model. Please refer to the documentation of your computer if needed.
-
-Usually the feature will be called Wake-on-Lan and you need to set it as "enabled" in the BIOS/UEFI settings.
-
-Here are some examples to guide you:
-
-* Racker Server, Dell R720
- * Go into `System Setup -> Device Settings -> NIC Port -> NIC Configuration`
- * Set Wake-on-Lan to `Enable`
-* Desktop Computer, HP EliteDesk G1
- * Go to Power -> Hardware Power Management
- * Disable `S5 Maximum Power Saving`
- * Go to `Advanced -> Power-On Options`
- * Set `Remote Wake up Boot source` to `Remote Server`
-
-> Hint: Check the Z-OS monitor screen and make sure that all the 3Nodes are within the same lan (e.g. all 3Nodes addresses are between 192.168.15.00 and 192.168.15.255).
-
-## Deploy a Full VM
-
-For this guide, we run the Farmerbot on a Full VM running on the TFGrid. Note that while you do not need to run the Farmerbot on the TFGrid, the whole process is very simple as presented here.
-
-- Deploy a full VM on the TFGrid
-- Update and upgrade the VM
- ```
- apt update && apt upgrade
- ```
-- Reboot and reconnect to the VM
- ```
- reboot
- ```
-
-## Farmerbot Setup
-
-We present the different steps to run the Farmerbot using the binaries.
-
-> For a script that can help automate the steps in this guide, [check this forum post](https://forum.threefold.io/t/new-farmerbot-install-script/4207).
-
-### Download the Farmerbot Binaries
-
-- Download the latest [ThreeFold tfgrid-sdk-go release](https://github.com/threefoldtech/tfgrid-sdk-go/releases) and extract the farmerbot for your specific setup (here we use `x86_64`). On the line `wget ...`, make sure to replace `` with the latest Farmerbot release.
- ```
- wget https://github.com/threefoldtech/tfgrid-sdk-go/releases/download//tfgrid-sdk-go_Linux_x86_64.tar.gz
- tar xf tfgrid-sdk-go_Linux_x86_64.tar.gz farmerbot
- ```
-- Move the Farmerbot
- ```
- mv farmerbot /usr/local/bin
- ```
-- Remove the tar file
- ```
- rm tfgrid-sdk-go_Linux_x86_64.tar.gz
- ```
-
-### Create the Farmerbot Files
-
-- Create Farmerbot files directory
- ```
- cd ~
- mkdir farmerbotfiles
- ```
-- Create the Farmerbot `config.yml` file ([see template below](#configuration-file-template-configyml))
- ```
- nano ~/farmerbotfiles/config.yml
- ```
-- Create the environment variables file and set the variables ([see template below](#environment-variables-file-template-env))
- ```
- nano ~/farmerbotfiles/.env
- ```
-
-### Run the Farmerbot
-
-We run the Farmerbot with the following command:
-
-```
-farmerbot run -e ~/farmerbotfiles/.env -c ~/farmerbotfiles/config.yml -d
-```
-
-For farmers with **ed25519** keys, the flag `-k` should be used. Note that by default, the Farmerbot uses the **sr25519** keys.
-
-```
-farmerbot run -k ed25519 -e ~/farmerbotfiles/.env -c ~/farmerbotfiles/config.yml -d
-```
-
-Once you've verified that the Farmerbot runs properly, you can stop the Farmerbot and go to the next section to set a Farmerbot service. This step will ensure the Farmerbot keeps running after exiting the VM.
-
-### Set a systemd Service
-
-It is highly recommended to set a Ubuntu systemd service to keep the Farmerbot running after exiting the VM.
-
-* Create the service file
- * ```
- nano /etc/systemd/system/farmerbot.service
- ```
-* Set the Farmerbot systemd service
-
- ```
- [Unit]
- Description=ThreeFold Farmerbot
- StartLimitIntervalSec=0
-
- [Service]
- Restart=always
- RestartSec=5
- StandardOutput=append:/root/farmerbotfiles/farmerbot.log
- StandardError=append:/root/farmerbotfiles/farmerbot.log
- ExecStart=/usr/local/bin/farmerbot run -e /root/farmerbotfiles/.env -c /root/farmerbotfiles/config.yml -d
-
- [Install]
- WantedBy=multi-user.target
- ```
-* Enable the Farmerbot service
- ```
- systemctl daemon-reload
- systemctl enable farmerbot
- systemctl start farmerbot
- ```
-* Verify that the Farmerbot service is properly running
- ```
- systemctl status farmerbot
- ```
-
-### Check the Farmerbot Logs
-
-Once you've set a Farmerbot systemd service [as show above](#set-a-systemd-service), the Farmerbot will start writing logs to the file `farmerbot.log` in the directory `farmerbotfiles`.
-
-Thus, you can get more details on the operation of the Farmerbot by inspecting the log file. This can also be used to see the **Farmerbot Report Table** as this table is printed in the Farmerbot log.
-
-* See all logs so far
- ```
- cat ~/farmerbotfiles/farmerbot.log
- ```
-* See the last ten lines and new logs as they are generated
- ```
- tail -f ~/farmerbotfiles/farmerbot.log
- ```
-* See all logs and new lines as they are generated
- ```
- tail -f -n +1 ~/farmerbotfiles/farmerbot.log
- ```
-* See the last report table
- ```
- tac ~/farmerbotfiles/farmerbot.log | grep -B5000 -m1 "Nodes report" | tac
- ```
-
-### Stop the Farmerbot
-
-You can stop the farmerbot with the following command:
-
-```
-systemctl stop farmerbot
-```
-
-After stopping the farmerbot, any nodes in standby mode will remain in standby. To bring them online, use this command:
-
-```
-farmerbot start all -e /root/farmerbotfiles/.env --farm
-```
-
-## Farmerbot Files
-
-### Configuration File Template (config.yml)
-
-In this example, the farm ID is 1, we are setting the Farmerbot with 4 nodes and the node 1 never shuts down, we set a periodic wakeup at 1:00PM.
-
-Note that the timezone of the farmerbot will be the same as the time zone of the machine the farmerbot running inside. By default, a full VM on the TFGrid will be set in UTC.
-
-```
-farm_id: 1
-included_nodes:
- - 1
- - 2
- - 3
- - 4
-never_shutdown_nodes:
- - 1
-power:
- periodic_wake_up_start: 01:00PM
-```
-
-Note that if the user wants to include all the nodes within a farm, they can simply omit the `included_nodes` section. In this case, all nodes of the farm will be included in the Farmerbot, as shown in the example below. If you are proceeding like this, make sure that you don't have any unused node IDs on your farm, as the Farmerbot would try to wake up nodes that aren't running anymore on the grid.
-
-```
-farm_id: 1
-never_shutdown_nodes:
- - 1
-power:
- periodic_wake_up_start: 01:00PM
-```
-
-### Environment Variables File Template (.env)
-
-The network can be either `main`, `tets`, `dev` or `qa`. The following example is with the main network.
-
-```
-MNEMONIC_OR_SEED="word1 word2 word3 ... word12"
-NETWORK="main"
-```
-
-## Running Multiple Farmerbots on the Same VM
-
-You can run multiple instances of the Farmerbot on the same VM.
-
-To do so, you need to create a directory for each instance of the Farmerbot. Each directory should contain the configuration and variables files as shown above. Once you've set the files, you can simply execute the Farmerbot `run` command to start each bot in each directory.
-
-It's recommended to use distinct names for the directories and the services to easily differentiate the multiple farmerbots running on the VM.
-
-For example, the directory tree of two Farmerbots could be:
-
-```
-└── farmerbotfiles
- ├── farmerbot1
- │ ├── .env
- │ └── config.yml
- └── farmerbot2
- ├── .env
- └── config.yml
-```
-
-For example, the services of two Farmerbots could be named as follows:
-
-```
-farmerbot1.service
-farmerbot2.service
-```
\ No newline at end of file
diff --git a/docs_projectinca/src/content/docs/resources/node_status_bot.md b/docs_projectinca/src/content/docs/resources/node_status_bot.md
deleted file mode 100644
index a4a4512..0000000
--- a/docs_projectinca/src/content/docs/resources/node_status_bot.md
+++ /dev/null
@@ -1,115 +0,0 @@
----
-title: Node Status Bot
-description: How to use the Node Status bot
----
-
-## Introduction
-
-We present the [Node Status Bot](https://t.me/tfnodestatusbot) and how to use it.
-
-The Node Status Bot is a very helpful tool for farmers of the ThreeFold Grid. It can give you relevant information on your node status, notify you if the node status changes and also provide information on minting violations.
-
-You can find the bot source code on GitHub [here](https://github.com/threefoldfoundation/node-status-bot).
-
-## Disclaimer
-
-Note that the bot is developed and operated on a best effort basis. You are responsible for your nodes' uptime and your farming rewards.
-
-## Getting Started with the Bot
-
-To get started with the bot, simply go to the [bot link on Telegram](https://t.me/tfnodestatusbot) and hit the start button to begin interacting with the bot.
-
-You can get the real time status of a node with the status command. For example, this gives the status of node 42
-
-```
-/status 42
-```
-
-The bot can also send you a message when the status of a node changes. Use the subscribe command (or sub for short) to begin alerts for one or more nodes. Here we are subscribing to nodes 1, 2, and 3:
-
-```
-/sub 1 2 3
-```
-
-Once you have subscribed you can issue the status command with no input to get the current status of the nodes you are subscribed to:
-
-```
-/status
-```
-
-By default, the bot is on main network. To change the network to the dev or test networks, use the network (net) command. Changing the network does not affect any existing subscriptions, and the bot does not specify which network the nodes belong to in its messages. Here's an example to change the network to devnet:
-
-```
-/net dev
-```
-
-You can also check if there are any violations in the current minting period. Like status, this command takes a node id as input or works on the currently subscribed nodes if no input is given:
-
-```
-/violations
-```
-
-The next section covers in-depth the different commands available.
-
-## Commands
-
-Here is a reference for all supported commands and their different forms:
-
-- `/help`
- - Print the start message with all the available commands
-- `/status`
- - Check the current status of one or all nodes.
- - This uses a similar method as the Dashboard for determining node status, and update may be delayed by an hour
- - With no input, a status report will be generated for all subscribed nodes, if any
- - Examples
- - Check status of node ID 1
- - `/status 1`
- - Check status of all currently subscribed nodes
- - `/status`
-- `/violations`
- - Scan for farmerbot related violations during the current and previous minting periods
- - Like status, this works on all subscribed nodes when no input is given
- - Examples
- - Check violations of node ID 1
- - `/violations 1`
- - Check status of all currently subscribed nodes
- - `/violations`
-- `/subscribe`
- - Subscribe to updates about one or more nodes
- - You can use the shortcut `/sub`
- - If you don't provide an input, the nodes you are currently subscribed to will be shown
- - Examples
- - Subscribe to node ID 1
- - `/sub 1`
- - Subscribe to node ID 1, 2, 3
- - `/sub 1 2 3`
- - Check all subscribed nodes
- - `/sub`
-- `/unsubscribe`
- - Unsubscribe to updates about one or more nodes
- - You can use the shortcut `/unsub`
- - Examples
- - Unsubscribe to node ID 1
- - `/unsubscribe 1`
- - Unsubscribe to node ID 1, 2, 3
- - `/unsubscribe 1 2 3`
- - Unsubscribe to all currently subscribed nodes
- - `/unsub all`
-- `/network`
- - Change the network to `dev`, `test`, or `main`
- - Default is `main`
- - You can use the shortcut `/net`
- - If you don't provide an input, the currently selected network is shown
- - Examples
- - Check current network
- - `/network`
- - Change to another network, e.g. to `dev`
- - `/net dev`
-
-## Bugs and Features
-
-To report bugs and request features, please open an issue on the [GitHub repo](https://github.com/threefoldfoundation/node-status-bot) or contact [Scott Yeager on Telegram](https://t.me/scottyeager).
-
-## Node Status Bot News
-
-If you use the bot, please also subscribe to the [Node Status Bot News channel](https://t.me/node_bot_updates) on Telegram to receive occasional updates and news concerning the bot.
diff --git a/docs_projectinca/src/content/docs/resources/resources_introduction.md b/docs_projectinca/src/content/docs/resources/resources_introduction.md
deleted file mode 100644
index e160831..0000000
--- a/docs_projectinca/src/content/docs/resources/resources_introduction.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: How to Use the Bots
-description: Resources Introduction
----
-
-This section is optional. We present two bots to optimize your farming experience.
-
-## The Bots
-
-- The Node Status Bot give you relevant information on your node status, notify you if the node status changes and also provide information on minting violations.
-- The Farmerbot is a service that farmers can run in order to automatically manage the nodes in their farms.
\ No newline at end of file
diff --git a/docs_projectinca/src/content/docs/start_here/getting_started.md b/docs_projectinca/src/content/docs/start_here/getting_started.md
deleted file mode 100644
index dbac45b..0000000
--- a/docs_projectinca/src/content/docs/start_here/getting_started.md
+++ /dev/null
@@ -1,28 +0,0 @@
----
-title: Getting Started
-description: Basic Steps to Farm INCA!
----
-
-> IMPORTANT: Project INCA Docs will be updated for the launch of the project. The content of this website is not the final version and steps are not yet implemented for INCA nodes.
-
-It's now easier than ever to become a farmer on the ThreeFold Grid thanks to Project **IN**ternet **CA**pacity.
-
-Farmers are cloud service providers who offer compute, storage and network resources to the world. In exchange, farmers receive INCA rewards.
-
-You can contribute to the worldwide cloud landscape and own your own part of the Internet!
-
-## Main Steps
-
-There are only a handful of steps needed to become a cloud service provider.
-
-- Install the ThreeFold Connect app
-- Create an INCA Farm
-- Get INCA nodes
-- Connect your nodes
-- Manage your rewards
-
-## Let's Go
-
-The next pages will guide you through the process of becoming a cloud service provider.
-
-All aboard the ThreeFold Grid... Let's deploy some INCA nodes!
\ No newline at end of file
diff --git a/docs_projectinca/src/env.d.ts b/docs_projectinca/src/env.d.ts
deleted file mode 100644
index acef35f..0000000
--- a/docs_projectinca/src/env.d.ts
+++ /dev/null
@@ -1,2 +0,0 @@
-///
-///
diff --git a/docs_projectinca/tsconfig.json b/docs_projectinca/tsconfig.json
deleted file mode 100644
index 77da9dd..0000000
--- a/docs_projectinca/tsconfig.json
+++ /dev/null
@@ -1,3 +0,0 @@
-{
- "extends": "astro/tsconfigs/strict"
-}
\ No newline at end of file
diff --git a/heroscript/developers/book_collections.md b/heroscript/devs/book_collections.md
similarity index 91%
rename from heroscript/developers/book_collections.md
rename to heroscript/devs/book_collections.md
index c49abbb..eef936d 100644
--- a/heroscript/developers/book_collections.md
+++ b/heroscript/devs/book_collections.md
@@ -1,7 +1,7 @@
```js
-!!book.generate name:'developers' title:'ThreeFold Developers Manual' printbook:false foldlevel:0
- url:'https://git.ourworld.tf/tfgrid/info_tfgrid/src/branch/main/books/developers'
+!!book.generate name:'devs' title:'ThreeFold Developers Manual' printbook:false foldlevel:0
+ url:'https://git.ourworld.tf/tfgrid/info_tfgrid/src/branch/main/books/devs'
!!doctree.add
url:'https://git.ourworld.tf/tfgrid/info_tfgrid/src/branch/main/collections/manual'
diff --git a/heroscript/developers/context.md b/heroscript/devs/context.md
similarity index 100%
rename from heroscript/developers/context.md
rename to heroscript/devs/context.md
diff --git a/heroscript/developers/sshkey.md b/heroscript/devs/sshkey.md
similarity index 100%
rename from heroscript/developers/sshkey.md
rename to heroscript/devs/sshkey.md
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
diff --git a/heroscript/tfgrid4specs/context.md b/heroscript/tfgrid4specs/context.md
new file mode 100644
index 0000000..a8f5892
--- /dev/null
+++ b/heroscript/tfgrid4specs/context.md
@@ -0,0 +1,11 @@
+
+```js
+
+!!books.configure
+ buildroot:'~/hero/var/mdbuild'
+ publishroot:'~/hero/www/info'
+ install:true
+ reset:false
+
+```
+
diff --git a/heroscript/tfgrid4specs/sshkey.md b/heroscript/tfgrid4specs/sshkey.md
new file mode 100644
index 0000000..85acfe6
--- /dev/null
+++ b/heroscript/tfgrid4specs/sshkey.md
@@ -0,0 +1,14 @@
+
+```js
+!!sshagent.key_add
+ name:'books'
+ privkey:'
+ -----BEGIN OPENSSH PRIVATE KEY-----
+ b3BlbnNzaC1rZXktdjEAAAAABG5vbmUAAAAEbm9uZQAAAAAAAAABAAAAMwAAAAtzc2gtZW
+ QyNTUxOQAAACDXf9Z/2AH8/8a1ppagCplQdhWyQ8wZAieUw3nNcxsDiQAAAIhb3ybRW98m
+ 0QAAAAtzc2gtZWQyNTUxOQAAACDXf9Z/2AH8/8a1ppagCplQdhWyQ8wZAieUw3nNcxsDiQ
+ AAAEC+fcDBPqdJHlJOQJ2zXhU2FztKAIl3TmWkaGCPnyts49d/1n/YAfz/xrWmlqAKmVB2
+ FbJDzBkCJ5TDec1zGwOJAAAABWJvb2tz
+ -----END OPENSSH PRIVATE KEY-----
+ '
+```
\ No newline at end of file