...

collections/tech/SUMMARY.md

@@ -0,0 +1 @@
+../../books/tech/SUMMARY.md

collections/tech/architecture/architecture.md

@@ -0,0 +1,7 @@
+
+## Architecture
+
+![](img/architecture.png)
+
+
+

collections/tech/energy_efficient.md

@@ -0,0 +1,6 @@
+# energy efficient
+
+![alt text](energy_efficient.png)
+
+> Depending the usecase the ThreeFold approach can lead to 10x energy savings.
+

collections/tech/features.md

@@ -0,0 +1 @@
+# ThreeFold Cloud Features

collections/tech/grid/concepts/cloudunits.md

@@ -0,0 +1,13 @@
+# Cloud Units
+
+Cloud units are the basis for buying & selling capacity on the ThreeFold Grid (for more info see here).
+
+- 1 CU = 1 compute unit
+- 1 SU = 1 storage unit
+- 1 NU = 1 network unit
+
+
+References:
+- Cloud units the the building blocks for any Cloud / IT workload.  See definition [here](https://library.threefold.me/info/threefold#/tfgrid/farming/threefold__resource_units_calc_cloudunits)
+- Cloud units are also used to determine commercial pricing for utilisation.  See definition [here](https://library.threefold.me/info/threefold#/cloud/threefold__pricing?id=discount-levels)
+- Low level primitive [cloud functions](https://library.threefold.me/info/threefold/#/technology/threefold__tfgrid_primitives)

collections/tech/grid/concepts/concepts.md

@@ -0,0 +1 @@
+# Concepts

collections/tech/grid/concepts/cultivation.md

@@ -0,0 +1,5 @@
+# Cultivation
+
+![cultivation](img/threefold__cloud_blockchain_.jpg)
+> See: [https://library.threefold.me/info/threefold/#/cloud/threefold__cloud_home](https://library.threefold.me/info/threefold/#/cloud/threefold__cloud_home)
+

collections/tech/grid/concepts/farming.md

@@ -0,0 +1,4 @@
+# Farming
+
+![farming](img/threefold__grid_new_.png)
+> See: [https://library.threefold.me/info/threefold/#/tfgrid/farming/threefold__farming_intro](https://library.threefold.me/info/threefold/#/tfgrid/farming/threefold__farming_intro)

collections/tech/grid/consensus3_mechanism/consensus3.md

@@ -0,0 +1,18 @@
+![](img/grid_header.jpg)
+
+# DAO Consensus Engine
+
+
+
+## DAO Engine
+
+On TFGrid 3.0 ThreeFold has implemented a DAO consensus engine using Polkadot/TFChain blockchain technology.
+
+This is a powerful blockchain construct which allows us to run our TFGrid and maintain consensus on global scale.
+
+This system has been designed to be compatible with multiple blockchains.
+
+
+
+
+

collections/tech/grid/consensus3_mechanism/consensus3_engine_farming.md

@@ -0,0 +1,17 @@
+![](img/grid_header.jpg)
+
+### consensus engine in relation to TFT Farming Rewards in TFGrid 3.0
+
+
+
+The consensus engine checks the farming rules as defined in 
+
+- [farming logic 3.0](farming_reward)
+- [farming reward calculator](farming_calculator)
+
+- if uptime + 98% per month then the TFT will be rewarded to the farmer (for TFGrid 3.0, can change later).
+
+All the data of the farmer and the 3nodes are registered on TFChain
+
+- See [Roadmap TFChain/DAO 3.x](roadmap_tfchain3) for info of implementation.
+

collections/tech/grid/consensus3_mechanism/consensus3_oracles.md

@@ -0,0 +1,43 @@
+
+## Consensus 3.X Oracles used
+
+Oracles are external resources of information.
+
+The TFChain captures and holds that information so we get more certainty about the accuracy.
+
+We have oracles for price & reputation for e.g. TFFarmers and TFNodes.
+
+These oracles are implemented on TF_CHAIN for TFGrid 3.0.
+
+```mermaid
+
+
+graph TB
+    subgraph Digital Currency Ecosystem
+        money_blockchain[Money Blockchain Explorers]
+        Exch1[Money Blockchain Decentralized Exchange]
+        OracleEngine --> Exch1[Polkadot]
+        OracleEngine --> Exch1[Money Blockchain Exchange]
+        OracleEngine --> Exch2[Binance Exchange]
+        OracleEngine --> Exch3[other... exchanges]        
+    end
+    subgraph ThreeFold Grid
+        Monitor_Engine --> TFNode1
+        Monitor_Engine --> TFNode2
+        Monitor_Engine --> TFNode3
+    end
+    subgraph TFChainNode1[TFGrid Blockchain Node]
+        Monitor_Engine
+        Explorers[TFChain Explorers]-->TFGridDB --> BCNode
+        Explorers --> BCNode
+        ConsensusEngine1-->BCNode[Blockchain Validator Node]
+        ConsensusEngine1 --> money_blockchain[Money Blockchain]
+        ConsensusEngine1 --> ReputationEngine[Reputation Engine]
+        ReputationEngine --> Monitor_Engine[Monitor Engine]
+        ConsensusEngine1 --> OracleEngine[Oracle For Pricing Digital Currencies]
+    end
+
+```
+
+- See [Roadmap TFChain/DAO 3.x](roadmap_tfchain3) for info of implementation.
+

collections/tech/grid/consensus3_mechanism/consensus3_overview_graph.md

@@ -0,0 +1,51 @@
+
+```mermaid
+graph TB
+    subgraph Money Blockchain
+        money_blockchain --> account1
+        money_blockchain --> account2
+        money_blockchain --> account3
+        click money_blockchain "/threefold/#money_blockchain"
+    end
+    subgraph TFChainNode1[TFChain BCNode]
+        Explorer1-->BCNode1
+        ConsensusEngine1-->BCNode1
+        ConsensusEngine1 --> money_blockchain
+        ConsensusEngine1 --> ReputationEngine1
+        ReputationEngine1 --> Monitor_Engine1
+        click ReputationEngine1 "/info/threefold/#reputationengine"
+        click ConsensusEngine1 "/info/threefold/#consensusengine"
+        click BCNode1 "/info/threefold/#bcnode"
+        click Explorer1 "/info/threefold/#tfexplorer"
+    end
+    subgraph TFChainNode2[TFChain BCNode]
+        Explorer2-->BCNode2
+        ConsensusEngine2-->BCNode2
+        ConsensusEngine2 --> money_blockchain
+        ConsensusEngine2 --> ReputationEngine2
+        ReputationEngine2 --> Monitor_Engine2
+        click ReputationEngine2 "/info/threefold/#reputationengine"
+        click ConsensusEngine2 "/info/threefold/#consensusengine"
+        click BCNoBCNode2de1 "/info/threefold/#bcnode"
+        click Explorer2 "/info/threefold/#tfexplorer"
+
+    end
+    Monitor_Engine1 --> TFNode1
+    Monitor_Engine1 --> TFNode2
+    Monitor_Engine1 --> TFNode3
+    Monitor_Engine2 --> TFNode1
+    Monitor_Engine2 --> TFNode2
+    Monitor_Engine2 --> TFNode3
+    click TFNode1 "/info/threefold/#3node"
+    click TFNode2 "/info/threefold/#3node"
+    click TFNode3 "/info/threefold/#3node"
+    click Monitor_Engine1 "/info/threefold/#monitorengine"
+    click Monitor_Engine2 "/info/threefold/#monitorengine"
+
+
+```
+
+*click on the parts of the image, they will go to more info*
+
+- See [Roadmap TFChain/DAO 3.x](roadmap_tfchain3) for info of implementation.
+

collections/tech/grid/consensus3_mechanism/consensus3_principles.md

@@ -0,0 +1,45 @@
+# Consensus Mechanism
+
+## Blockchain node components
+
+
+
+- A Blockchain node (= TFChain node) called TF-Chain, containing all entities interacting with each other on the TF-Grid
+- An explorer = a Rest + GraphQL interface to TF-Chain (Graphql is a nice query language to make it easy for everyone to query for info)
+- Consensus Engine
+  - is a Multisignature Engine running on TF-Chain
+  - The multisignature is done for the Money BlockchainAccounts
+  - It checks the AccountMetadata versus reality and if ok, will sign, which allows transactions to happen after validation of the "smart contract"
+- SLA & reputation engine
+  - Each node uptime is being checked by Monitor_Engine
+  - Also bandwidth will be checked in the future (starting 3.x)
+
+### Remarks
+
+- Each Monitor_Engine checks uptime of X nr of nodes (in beginning it can do all nodes), and stores the info in local DB (to keep history of check)
+- [Roadmap for TFChain deployment mechanism](roadmap_tfchain3)
+
+## Principle
+
+- We keep things as simple as we can
+  - Money Blockchain blockchain used to hold the money
+    - Money Blockchain has all required features to allow users to manage their money like wallet support, decentralized exchange, good reporting, low transaction fees, ...
+  - TFChain based TFChain is holding the metadata for the accounts which express what we need to know per account to allow the start contracts to execute.
+  - Smart Contracts are implemented using multisignature feature on Money Blockchain in combination with Multi Signature done by Consensus_Engine.
+- on money_blockchain:
+  - each user has Money BlockchainAccounts (each of them holds money)
+  - there are normal Accounts (means people can freely transfer money from these accounts) as well as RestrictedAccounts. Money cannot be transfered out of RestrictedAccounts unless consensus has been achieved from ConsensusEngine.
+- Restricted_Account
+  - On stellar we use the multisignature feature to make sure that locked/vesting or FarmingPool cannot transfer money unless consensus is achieved by the ConsensusEngine
+
+- Each account on money_blockchain (Money BlockchainAccount) has account record in TFChain who needs advanced features like:
+  - lockup
+  - vesting
+  - minting (rewards to farmers)
+  - tfta to tft conversion
+
+- The Account record in TFGrid_DB is called AccountMetadata.
+  - The AccountMetadata describes all info required to be able for consensus engine to define what to do for advanced features like vesting, locking, ...
+
+- See [Roadmap TFChain/DAO 3.x](roadmap_tfchain3) for info of implementation.
+

collections/tech/grid/consensus3_mechanism/consensus3_toc.md

@@ -0,0 +1,14 @@
+
+## Consensus Engine Information
+
+- [Consensus Engine Homepage](consensus3)
+- [Principles TFChain 3.0 Consensus](consensus3_principles)
+- [Consensus Engine Farming 3.0](consensus3_engine_farming)
+- [TFGrid 3.0 wallets](tfgrid3_wallets)
+- Architecture:
+  - [Money Blockchains/TFChain architecture](money_blockchain_partity_link)
+  - [ThreeFold Chain Oracles](consensus3_oracles)
+<!-- - [Consensus Engine Weight System](consensus3_weights) -->
+
+> implemented in TFGrid 3.0
+

collections/tech/grid/consensus3_mechanism/money_blockchain_partity_link.md

@@ -0,0 +1,52 @@
+
+## Link between different Money Blockchain & TFChain
+
+TF-Chain is the ThreeFold blockchain infrastructure, set up in the TFChain framework.
+
+We are building a consensus layer which allows us to easily bridge between different money blockchains.
+
+Main blockchain for TFT remains the Stellar network for now. A secure bridging mechanism exists, able to transfer TFT between the different blockchains. 
+Active bridges as from TFGrid 3.0 release: 
+- Stellar <> Binance Smart Chain
+- Stellar <> Parity TFChain
+More bridges are under development. 
+
+```mermaid
+
+
+graph TB
+    subgraph Money Blockchain
+        money_blockchain --- account1a
+        money_blockchain --- account2a
+        money_blockchain --- account3a
+        account1a --> money_user_1
+        account2a --> money_user_2
+        account3a --> money_user_3
+        click money_blockchain "/info/threefold/#money_blockchain"
+    end
+    subgraph ThreeFold Blockchain On Parity
+        TFBlockchain --- account1b[account 1]
+        TFBlockchain --- account2b[account 2]
+        TFBlockchain --- account3b[account 3]
+        account1b --- smart_contract_data_1
+        account2b --- smart_contract_data_2
+        account3b --- smart_contract_data_3
+        click TFBlockchain "/info/threefold/#tfchain"
+    end
+    account1b ---- account1a[account 1]
+    account2b ---- account2a[account 2]
+    account3b ---- account3a[account 3]
+
+    consensus_engine --> smart_contract_data_1[fa:fa-ban smart contract metadata]
+    consensus_engine --> smart_contract_data_2[fa:fa-ban smart contract metadata ]
+    consensus_engine --> smart_contract_data_3[fa:fa-ban smart contract metadata]
+    consensus_engine --> account1a
+    consensus_engine --> account2a
+    consensus_engine --> account3a
+    click consensus_engine "/info/threefold/#consensus_engine"
+
+
+```
+
+Above diagram shows how our consensus engine can deal with TFChain and multiple Money Blockchains at same time.
+

collections/tech/grid/consensus3_mechanism/roadmap_tfchain3.md

@@ -0,0 +1,53 @@
+
+# Roadmap For our TFCHain and ThreeFold DAO
+
+![](img/limitedsupply_.png)
+
+## TFChain / DAO 3.0.2
+
+For this phase our TFChain and TFDAO has been implemented using parity/TFChain.
+
+Features
+
+- poc
+- pou
+- identity management
+- consensus for upgrades of DAO and TFChain (code)
+- capacity tracking (how much capacity used)
+- uptime achieved
+- capacity utization
+- smart contract for IT
+- validators for L1 (TFChain level)
+- storage of value = TFT
+- request/approval for adding a validator
+
+Basically all basic DAO concepts are in place
+
+## TFChain / DAO 3.0.x
+
+TBD version nr, planned Q1 2022
+
+NEW
+
+- proposals for TFChain/DAO/TFGrid changes (request for change) = we call them TFCRP (ThreeFold Change Request Proposal)
+- voting on proposals = we call them TFCRV (ThreeFold Change Request Vote)
+
+
+## TFChain / DAO 3.1.x
+
+TBD version nr, planned Q1 2022
+
+This version adds more layers to our existing DAO and prepares for an even more scalable future.
+
+NEW
+
+- Cosmos based chain on L2
+- Validator Nodes for TFGrid and TFChain.
+- Cosmos based HUB = security for all TFChains
+
+> More info about our DAO strategy see TFDAO.
+
+
+
+
+

collections/tech/grid/consensus3_mechanism/tfgrid3_wallets.md

@@ -0,0 +1,72 @@
+
+# TFGrid 3.0 Wallets
+
+ThreeFold has a mobile wallet which will allow to be used on the TFChain backend (TFChain) as well as any other Money Blockchain it supports.
+
+This provides for a very secure digital currency infrastructure with lots of advantages.
+
+- [X] ultra flexible smart contracts possible 
+- [X] super safe
+- [X] compatible with multiple blockchains (money blockchains)
+- [X] ultra scalable
+
+```mermaid
+
+
+graph TB
+
+    subgraph Money Blockchain
+        money_blockchain[Money Blockchain Explorers]
+        money_blockchain --- money_blockchain_node_1 & money_blockchain_node_2
+        money_blockchain_node_1
+        money_blockchain_node_2
+    end
+
+    subgraph ThreeFold Wallets
+        mobile_wallet[Mobile Wallet]
+        desktop_wallet[Desktop Wallet]
+        mobile_wallet & desktop_wallet --> money_blockchain
+        mobile_wallet & desktop_wallet  --> Explorers
+        money_blockchain_wallet[Any Money Blockchain Wallet] --> money_blockchain
+    end
+
+
+    subgraph TFChain[TFGrid Blockchain on TFChain]
+        Explorers[TFChain Explorers]-->TFGridDB --> BCNode
+        Explorers --> BCNode
+    end
+
+
+```
+
+Generic overview:
+
+```mermaid
+
+graph TB
+
+    subgraph TFChain[TFGrid Chain]
+        guardian1[TFChain Node 1]
+        guardian2[TFChain Node 2]
+        guardian3[TFChain Node 3...9]
+    end
+
+    User_wallet[User Wallet] --> money_blockchain_account
+    User_wallet[User Wallet] --> money_blockchain_restricted_account
+
+    subgraph Money Blockchain Ecosystem
+        money_blockchain_account
+        money_blockchain_restricted_account --- guardian1 & guardian2  & guardian3
+    end
+
+    subgraph consensus[Consensus Layer on TFChain]
+        guardian1 --> ReputationEngine & PricingOracle
+        guardian1 --> contract1[Smart Contract Vesting]
+        guardian1 --> contract2[Smart Contract Minting/Farming]        
+    end
+
+
+
+
+```
+

collections/tech/grid/consensus3_mechanism/tfgrid_db_models.v

@@ -0,0 +1,52 @@
+
+// - vesting
+//   - startdate: epoch
+//   - currency: USD
+//   - [[$month_nr,$minprice_unlock,$TFT_to_vest],...]
+//     - if 48 months then list will have 48 parts
+//     - month 0 = first month
+//     - e.g. [[0,0.11,10000],[1,0.12,10000],[2,0.13,10000],[3,0.14,10000]...]
+
+//information stored at account level in TFGridDB
+struct AccountMeta{
+	//corresponds to unique address on money_blockchain
+	money_blockchain_address string
+	vesting Vesting[]
+	unlocked_TFT int
+}
+
+struct Vesting{
+	startdate int
+	//which currency is used to execute on the acceleration in the vesting
+	//if price above certain level (which is currency + amount of that currency) the auto unlock
+	currency CurrencyEnum
+	months []VestingMonth
+}
+
+struct VestingMonth{
+	month_nr int
+	//if 0 then will not unlock based on price
+	unlock_price f32
+	tft_amount int
+}
+
+enum CurrencyEnum{
+	usd
+	eur
+	egp
+	gbp
+	aed
+}
+
+//this is stored in the TFGridDB
+fn (mut v AccountMeta) serialize() string{
+	//todo code which does serialization see above
+	return ""
+}
+
+
+//write minting pool
+
+
+//REMARKS
+// if unlock triggered because of month or price then that record in the VestingMonth[] goes away and TFT go to unlocked_TFT

collections/tech/history/c64.md

@@ -0,0 +1,9 @@
+## we forgot to use hardware well
+
+The IT world does not utilize computer hardware well.
+
+![](img/c64.png)
+
+Hardware advancements surged, while experiences and features stagnated, unable to match the pace. 
+
+> TODO: c64 describe better

collections/tech/history/layers.md

@@ -0,0 +1,11 @@
+# Layers
+
+![](img/layers.png)
+
+Too many abstraction layers results in bad efficiency, performance loss, increased management costs, and scalability challenges.
+
+This is due to a number of reasons.
+
+![](img/fourreasons.png)
+
+>TODO: 

collections/tech/img/.done

@@ -0,0 +1,6 @@
+3node_simple.png
+architecture_usage.png
+manual.png
+tech_overview.png
+tech_overview2.png
+web_remade.png

collections/tech/innovations/flist_innovation.md

@@ -0,0 +1,4 @@
+
+## FList: a new way how to deal with OS Images
+
+!!wiki.include page:flist_innovation_short

collections/tech/innovations/flist_innovation_short.md

@@ -0,0 +1,28 @@
+
+
+
+### Why?
+
+The current method of deploying workloads in the cloud using Docker containers and virtual machine images has inherent issues. These images consume significant storage space, result in slow and bandwidth-intensive transfers to the internet's edge, drive up costs, introduce complexity, and pose security risks due to difficulties in tracking their contents over time.
+
+For instance, a complete Ubuntu image can easily be 2 GB in size, comprising millions of files. In contrast, the Flist for a full Ubuntu image is less than 2 MB (1000 times smaller), containing only the necessary files required to launch an application.
+
+### What?
+
+A new image format that separates the image data (comprising files and subfile parts) from the metadata describing the image structure. 
+
+An Flists format uniquely encompasses comprehensive file descriptions along with all relevant metadata such as size, modification and creation timestamps, and POSIX attributes. Additionally, it incorporates a fingerprint for each component, ensuring deterministic behavior—a crucial feature for security-focused use cases.
+
+Flists provide the flexibility to manage metadata and data as separate entities, offering a versatile approach to handling various build and delivery scenarios.
+
+### Benefits
+
+- **Rapid Deployment:** Zero-OS enables containers and virtual machines to launch up to 100 times faster, especially in decentralized scenarios.
+- **Enhanced Security:** Zero-OS prevents tampering with images, ensuring higher security levels.
+- **Reduced Storage and Bandwidth:** Zero-OS significantly reduces storage and bandwidth requirements, potentially achieving up to a 100-fold improvement.
+- **Deterministic Deployments:** Engineers can precisely define deployments beforehand, ensuring predictable outcomes without changes during deployment.
+- **100% compatible:** with existing standards, docker, virtual machines... The same format is useful for VM's as well as any container technology.
+
+### Status?
+
+- Usable for years, see Zero-OS.

collections/tech/innovations/fungistor_innovation.md

@@ -0,0 +1,4 @@
+
+## FungiStor (end 2024)
+
+!!wiki.include page:'fungistor_innovation_short'

collections/tech/innovations/fungistor_innovation_short.md

@@ -0,0 +1,22 @@
+
+
+### Why?
+
+Existing blockchain, internet, and P2P content delivery and storage systems suffer from sluggish performance and are too expensive. Content retrieval is often slow, and the overhead for ensuring redundancy is excessive. We require innovative approaches to facilitate efficient information sharing among users.
+
+Content delivery frequently represents the most significant expense for social networks. Running a basic social video network for 10 million users currently costs approximately $2 million per month using traditional cloud providers. We have the potential to reduce this cost by several orders of magnitude.
+
+
+### What?
+
+FungiStor is a peer-to-peer (P2P) content delivery layer designed to store and distribute an extensive range of objects, including images, videos, files, and more. It has the capability to handle trillions of objects and files efficiently. FungiStor serves as an excellent solution for content delivery networks (CDNs), significantly reducing costs for organizations seeking to stream or deliver substantial data volumes to their user base.
+
+Furthermore, FungiStor will act as the backend infrastructure for the Flists within our own system. However, it is versatile and can be utilized by anyone in need of a global-level content delivery system for files, objects, and images.
+
+### Benefits?
+
+- **Global Scalability, Sub-50ms Lookups:** FungiStor scales worldwide with ultra-fast data retrieval under 50 milliseconds.
+- **Localized Content Delivery:** Prioritizes local data access for optimized speed and efficiency.
+- **Quantum-Safe Security:** Incorporates robust quantum security measures.
+- **Interoperability:** Works seamlessly with IPFS, Torrent, and more.
+- **Cost Efficiency:** Offers significant cost savings, potentially 10 to 100 times less than conventional solutions.

collections/tech/innovations/key_innovations.md

@@ -0,0 +1,36 @@
+
+# Key Innovations
+
+
+## Mycelium: a new network layer for the internet
+
+!!wiki.include page:mycelium_innovation_short.md
+
+## Zero-OS: a minimalistic more efficient server operating system
+
+!!wiki.include page:zos_innovation_short
+
+## FList: a new way how to deal with OS Images
+
+!!wiki.include page:flist_innovation_short
+
+
+## Zero-Stor : a quantum safe backend storage system.
+
+!!wiki.include page:zstor_innovation_short
+
+
+## Quantum Safe File System 
+
+
+!!wiki.include page:qsfs_innovation_short
+
+
+## FungiStor
+
+!!wiki.include page:'fungistor_innovation_short'
+
+
+## NetworkWall
+
+!!wiki.include page:network_wall_innovation_short

collections/tech/innovations/key_innovations_overview.md

@@ -0,0 +1,13 @@
+
+![](dream_comes_true.png)
+
+# Key Innovations
+
+
+- [Mycelium: a new network layer for the internet](mycelium_innovation.md)
+- [Zero-OS: a minimalistic more efficient server operating system](zos_innovation)
+- [Quantum Safe Storage](zstor_innovation.md)
+- [Quantum Safe Filesystem](qsfs_innovation.md)
+- [FList: a new way how to deal with OS Images](flist_innovation.md)
+- [FungiStor](fungistor_innovation.md)
+- [Network Wall](network_wall_innovation.md)

collections/tech/innovations/mycelium_innovation.md

@@ -0,0 +1,4 @@
+
+## Mycelium: a new network layer for the internet
+
+!!wiki.include page:mycelium_innovation_short.md

collections/tech/innovations/mycelium_innovation_short.md

@@ -0,0 +1,25 @@
+
+### Why?
+
+The current centralized state of the internet poses significant security risks, with compromised routers and growing cyber threats (trillions of USD per year now), making everyone vulnerable to hacking. Industry responses involve disabling original features, hindering true peer-to-peer connectivity and personal server capabilities. Workarounds and system hacks have become the norm.
+
+**Our Internet is seriously broken, we need new ways how to communicate**
+
+### What?
+
+Mycelium is an overlay network layer designed to enhance the existing internet infrastructure while remaining compatible with all current applications. It empowers true peer-to-peer communication. By installing a Network Agent on your device, you gain the ability to securely connect with any other participant on this network. Mycelium intelligently reroutes traffic to maintain connectivity taking location of you and your peer into consideration.
+
+### Benefits?
+
+- **Continuous Connectivity:** Mycelium ensures uninterrupted connectivity by dynamically rerouting traffic through available connections (friends, satellites, 4/5G, fiber).
+- **End-to-End Encryption:** Robust encryption stops man-in-the-middle attacks, guaranteeing secure communication.
+- **Proof of authenticity ([POA](p2p:poa.md))**: make sure we know who we communicate with 
+- **Optimized Routing:** Mycelium finds the shortest path between network participants, reducing latency and keeping traffic localized.
+- **Universal Server Capability:** Empowers individuals to act as servers, a foundational element for any peer-to-peer system.
+- **Full Compatibility:** Mycelium seamlessly integrates with the current internet, supporting any application.
+- **Impressive Speed:** Achieves 1 Gbps per Network Agent, ensuring rapid data transfer.
+
+### Status?
+
+- In beta and usable from TFGrid 3.13, its our 3e generation approach to networking and took us years to do. We are looking forward to your feedback.
+

collections/tech/innovations/network_wall_innovation.md

@@ -0,0 +1,6 @@
+
+## NetworkWall
+
+![](network_wall.png)
+
+!!wiki.include page:network_wall_innovation_short

collections/tech/innovations/network_wall_innovation_short.md

@@ -0,0 +1,20 @@
+
+
+### Why?
+
+Traditional firewalls are increasingly ineffective in addressing modern security challenges. They struggle to mitigate emerging threats, particularly against backdoors and man-in-the-middle attacks. Backdoors can render firewalls obsolete as attackers find ways to bypass them. New, innovative approaches to cybersecurity are necessary to address these evolving security problems.
+
+## What?
+
+Imagine a scenario where you deploy applications within secure, liquid-cooled physical containers or smaller POD's that operate without relying on traditional TCP/IP or Ethernet protocols. By avoiding the use of standard low-level protocols, the existing backdoors are unable to communicate with the external world.
+
+Incoming traffic is intercepted at the application level and securely transported into the protected environment through physical communication mechanisms based on RDMA (Remote Direct Memory Access). The integration of this solution into Zero-OS ensures a seamless and transparent experience for developers and system administrators.
+
+It's important to note that this solution is primarily intended for commercial use cases, but its existence is valuable knowledge in the realm of cybersecurity and network security.
+
+## Benefits
+
+- **Enhanced Security and Privacy:** The solution offers significantly improved security and privacy measures, mitigating potential risks and vulnerabilities.
+- **Ultra-Fast Connectivity:** Within the POD/Container, the connectivity is exceptionally fast, ensuring rapid data transfer and application performance.
+- **Robust Data and Application-Aware Proxies:** Secure proxies between the Internet and the protected backend application provide an additional layer of security, safeguarding data and ensuring application-level awareness.
+- **Seamless Integration:** The solution is designed for ease of integration within existing environments, minimizing disruptions and complexities during implementation.

collections/tech/innovations/qsfs_innovation.md

@@ -0,0 +1,4 @@
+## Quantum Safe File System 
+
+
+!!wiki.include page:qsfs_innovation_short

collections/tech/innovations/qsfs_innovation_short.md

@@ -0,0 +1,29 @@
+
+
+
+
+### Why?
+
+There is a growing need for more accessible and user-friendly solutions to store and manage large volumes of data efficiently.
+
+While Zero-Stor addresses numerous storage challenges effectively, it may not be accessible or user-friendly for typical developers or system administrators. QSFS has been developed to bridge this gap and provide a more approachable storage solution.
+
+### What?
+
+A FUSE-based filesystem utilizing Zero-Stor as its backend. Metadata is safeguarded to prevent loss, inheriting Zero-Stor's benefits and simplifying usage for developers and system administrators.
+
+The filesystem is always deployed in one location, data is distributed (using zero-stor) across multiple sites for unparalleled reliability. 
+
+Metadata redundancy is included. While not consistently synchronized in real-time, the system allows configuration of consistency levels. Typically, the decentralized state may lag by up to 15 minutes.
+
+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.
+- Provides a user-friendly interface for seamless integration with a wide range of applications.
+- Offers considerable scalability capabilities, although not unlimited in scale.
+- Achieves reasonable performance data transfer rates of up to 50 MB/sec, particularly for larger files.
+- Can scale to about 2 million files per filesystem.

collections/tech/innovations/world_records.md

@@ -0,0 +1,8 @@
+## World Records
+
+![](img/world_records.png)
+
+Our team is working on re-inventing layers of the Internet for more than 30 years.
+
+While we were doing so this has resulted in some world records and innovative products.
+

collections/tech/innovations/zos_innovation.md

@@ -0,0 +1,5 @@
+## Zero-OS: a minimalistic more efficient server operating system
+
+![](img/zos_innovation.png)
+
+!!wiki.include page:zos_innovation_short

collections/tech/innovations/zos_innovation_short.md

@@ -0,0 +1,26 @@
+
+### Why?
+
+Current Linux-based operating systems are challenging to use safely and efficiently on the edges of the Internet. They require central management, involve excessive complexity, and prove difficult to update and maintain, resulting in numerous security vulnerabilities. To revolutionize the internet, we must rethink how we host our applications, essentially reinventing the concept of a cloud-based operating system.
+
+### What?
+
+An innovative operating system, retaining the Linux kernel but fundamentally redesigned for heightened security, efficiency, and support for true peer-to-peer and decentralized workloads.
+
+This unique operating system doesn't require installation on hard disks or SSDs; it remains stateless, consistently up to date, and autonomously managed without human intervention. Its design enables self-healing application delivery, opening new possibilities in system resilience and reliability.
+
+### Benefits?
+
+- **Compatibility with Existing Workloads:** Our primary goal is to ensure Zero-OS compatibility with over 99% of the workloads commonly hosted in centralized cloud environments today. This includes support for Docker containers, virtual machines, Kubernetes, and more.
+- **Reduced Attack Surface:** Zero-OS boasts a smaller hacking surface, enhancing security by minimizing potential vulnerabilities.
+- **Stateless Design:** Its statelessness simplifies deployment and updates, making it easier to maintain while ensuring it's always up to date.
+- **Autonomous Operation:** Whether you have one instance or a billion, Zero-OS operates autonomously, streamlining management and maintaining consistency across all instances.
+- **Rapid Deployment:** With Zero-OS, you can deploy 1000 virtual machines in just 2 minutes, ensuring agility and efficiency in scaling up resources.
+- **Unique Security Features:** Zero-OS offers support for distinctive security features to enhance protection and fortify your infrastructure.
+- **Lower Cost, Easier to Maintain:** Zero-OS significantly reduces the operational expenses associated with cloud infrastructure by automating most processes. This results in minimal operational costs and eliminates the need for extensive engineering efforts.
+- **Ready for a Decentralized World:** Zero-OS empowers individuals to become hosts for required Internet capacity (storage, network, compute, gpu), allowing them to be rewarded for providing computing resources and internet connectivity. This aligns with the vision of a truly decentralized and distributed computing ecosystem.
+
+### Status?
+
+- 3e generation, active for +4 years, tested by thousands
+- Play with it yourself see www.threefold.io

collections/tech/innovations/zstor_innovation.md

@@ -0,0 +1,6 @@
+
+## Zero-Stor : a quantum safe backend storage system.
+
+![](qsss.png)
+
+!!wiki.include page:zstor_innovation_short

collections/tech/innovations/zstor_innovation_short.md

@@ -0,0 +1,40 @@
+
+## Zero-Stor : a quantum safe backend storage system.
+
+### Why?
+
+Traditional backend storage systems have their roots in centralized environments, focusing on low-latency and closed security setups. However, these characteristics make them less suitable for use in decentralized cloud contexts.
+
+Newer-generation storage systems like protocol-driven or blockchain-based solutions may face scalability and performance limitations and may not fulfill certain critical requirements that we consider essential.
+
+### What?
+
+A redesigned storage system which can scale to planet level, is super secure private and fast enough for more usecases. Its designed to operate in a decentralized context. Data can never be lost of corrupted.
+
+This storage system is a backend storage system, cannot be used by end users, its meant to be integrated with a front end storage system like e.g. S3 or a filesystem (see next section).
+
+
+### Benefits?
+
+
+- **Data Resilience:** Ensures data is never lost or corrupted.
+- **Planetary Scalability:** Capable of scaling to a global level.
+- **Cost-Efficient:** Offers exceptional cost efficiency.
+- **Versatility:** Suitable for various use cases, including archiving, backup, files, and CDNs.
+- **Low Overhead:** Requires only a 20% overhead for building a storage network where any four nodes can be lost simultaneously, compared to a 400% overhead in traditional storage systems.
+- **Security and Privacy:** Provides robust security, even impervious to quantum computers.
+- **Data Sovereignty:** Users have complete control over data placement.
+- **Empowering Front-End Applications:** Can be integrated into various front-end storage applications, such as blockchains, archives, or S3.
+- **CDN Support:** Functions effectively as a backend for CDN applications, facilitating content delivery.
+- **Sustainability:** Uses 10 times less energy compared to traditional storage systems, contributing to sustainability efforts.
+- **Locality Aware:** Data can be delivered to where the users are ideal for sovereign usecases.
+
+
+### Status?
+
+- Zero-OS has been in beta for over four years, with continuous development and improvement.
+- A notable deployment in Switzerland, with over 50 petabytes of storage capacity, served as a substantial test environment, although it's no longer active.
+- Within the current TFGrid network, there's an impressive capacity of over 20 petabytes available for use.
+- Lacking some monitoring, documentation ... will be added in TFGrid 3.15
+- Previous releases have been successfully utilized by major government organizations on a massive scale (hundreds of petabytes), providing strong evidence of the concept's viability and effectiveness.
+

collections/tech/internet/internet_today.md

@@ -0,0 +1,35 @@
+# The Internet Is Broken
+
+**THE THREE LAYERS OF THE INTERNET**
+
+![](internet_3layers.png)
+
+The Internet is made up out of 3 layers
+
+- compute, storage: this is where the applications are being served from
+  - today: highly centralized and running from large datacenters (see below)
+- network: ability for information to travel
+  - can be as wireless, cables (fiber) and satelite links, ...
+  - right now the information needs to travel very far, for most countries there is few local information
+  - very few companies own +80% of the network capacity
+- applications:
+  - today hosted in huge datacenters using the compute and storage capacity as provided
+  - too centralized and because of that also vulnerable
+
+The information travels mainly over large fiber backbone links.
+
+![](global_net.png)
+
+The Internet as we know it is far away from the original intent, if 2 people in e.g. Zanzibar (an Island in Africa) use Zoom with each other then the information will travel to Europe in a large datacenter where the Zoom servers are being hosted.
+
+This leads to very inneficient behavior, slower performance, less reliability and a cost which is higher than what it should be.
+
+![](network_path.png)
+
+We became products.
+
+![alt text](we_are_products.png)
+
+- All our data is hosted in large datacenters owned by few large corporations.
+- We exist many times, and each time a full infrastructure has been built to deliver the applications from.
+

collections/tech/key_innovations.md

@@ -1,203 +0,0 @@
-
-# Key Innovations
-
-
-## Mycelium: a new network layer for the internet
-
-### Why?
-
-The current centralized state of the internet poses significant security risks, with compromised routers and growing cyber threats (trillions of USD per year now), making everyone vulnerable to hacking. Industry responses involve disabling original features, hindering true peer-to-peer connectivity and personal server capabilities. Workarounds and system hacks have become the norm.
-
-**Our Internet is seriously broken, we need new ways how to communicate**
-
-### What?
-
-Mycelium is an overlay network layer designed to enhance the existing internet infrastructure while remaining compatible with all current applications. It empowers true peer-to-peer communication. By installing a Network Agent on your device, you gain the ability to securely connect with any other participant on this network. Mycelium intelligently reroutes traffic to maintain connectivity taking location of you and your peer into consideration.
-
-### Benefits?
-
-
-- **Continuous Connectivity:** Mycelium ensures uninterrupted connectivity by dynamically rerouting traffic through available connections (friends, satellites, 4/5G, fiber).
-- **End-to-End Encryption:** Robust encryption stops man-in-the-middle attacks, guaranteeing secure communication.
-- **Proof of authenticity ([POA](p2p:poa.md))**: make sure we know who we communicate with 
-- **Optimized Routing:** Mycelium finds the shortest path between network participants, reducing latency and keeping traffic localized.
-- **Universal Server Capability:** Empowers individuals to act as servers, a foundational element for any peer-to-peer system.
-- **Full Compatibility:** Mycelium seamlessly integrates with the current internet, supporting any application.
-- **Impressive Speed:** Achieves 1 Gbps per Network Agent, ensuring rapid data transfer.
-
-### Status?
-
-- In beta and usable from TFGrid 3.13, its our 3e generation approach to networking and took us years to do. We are looking forward to your feedback.
-
-
-## Zero-OS: a minimalistic more efficient server operating system
-
-### Why?
-
-Current Linux-based operating systems are challenging to use safely and efficiently on the edges of the Internet. They require central management, involve excessive complexity, and prove difficult to update and maintain, resulting in numerous security vulnerabilities. To revolutionize the internet, we must rethink how we host our applications, essentially reinventing the concept of a cloud-based operating system.
-
-### What?
-
-An innovative operating system, retaining the Linux kernel but fundamentally redesigned for heightened security, efficiency, and support for true peer-to-peer and decentralized workloads.
-
-This unique operating system doesn't require installation on hard disks or SSDs; it remains stateless, consistently up to date, and autonomously managed without human intervention. Its design enables self-healing application delivery, opening new possibilities in system resilience and reliability.
-
-### Benefits?
-
-- **Compatibility with Existing Workloads:** Our primary goal is to ensure Zero-OS compatibility with over 99% of the workloads commonly hosted in centralized cloud environments today. This includes support for Docker containers, virtual machines, Kubernetes, and more.
-- **Reduced Attack Surface:** Zero-OS boasts a smaller hacking surface, enhancing security by minimizing potential vulnerabilities.
-- **Stateless Design:** Its statelessness simplifies deployment and updates, making it easier to maintain while ensuring it's always up to date.
-- **Autonomous Operation:** Whether you have one instance or a billion, Zero-OS operates autonomously, streamlining management and maintaining consistency across all instances.
-- **Rapid Deployment:** With Zero-OS, you can deploy 1000 virtual machines in just 2 minutes, ensuring agility and efficiency in scaling up resources.
-- **Unique Security Features:** Zero-OS offers support for distinctive security features to enhance protection and fortify your infrastructure.
-- **Lower Cost, Easier to Maintain:** Zero-OS significantly reduces the operational expenses associated with cloud infrastructure by automating most processes. This results in minimal operational costs and eliminates the need for extensive engineering efforts.
-- **Ready for a Decentralized World:** Zero-OS empowers individuals to become hosts for required Internet capacity (storage, network, compute, gpu), allowing them to be rewarded for providing computing resources and internet connectivity. This aligns with the vision of a truly decentralized and distributed computing ecosystem.
-
-### Status?
-
-- 3e generation, active for +4 years, tested by thousands
-- Play with it yourself see www.threefold.io
-
-
-## FList: a new way how to deal with OS Images
-
-### Why?
-
-The current method of deploying workloads in the cloud using Docker containers and virtual machine images has inherent issues. These images consume significant storage space, result in slow and bandwidth-intensive transfers to the internet's edge, drive up costs, introduce complexity, and pose security risks due to difficulties in tracking their contents over time.
-
-For instance, a complete Ubuntu image can easily be 2 GB in size, comprising millions of files. In contrast, the Flist for a full Ubuntu image is less than 2 MB (1000 times smaller), containing only the necessary files required to launch an application.
-
-### What?
-
-A new image format that separates the image data (comprising files and subfile parts) from the metadata describing the image structure. 
-
-An Flists format uniquely encompasses comprehensive file descriptions along with all relevant metadata such as size, modification and creation timestamps, and POSIX attributes. Additionally, it incorporates a fingerprint for each component, ensuring deterministic behavior—a crucial feature for security-focused use cases.
-
-Flists provide the flexibility to manage metadata and data as separate entities, offering a versatile approach to handling various build and delivery scenarios.
-
-### Benefits
-
-- **Rapid Deployment:** Zero-OS enables containers and virtual machines to launch up to 100 times faster, especially in decentralized scenarios.
-- **Enhanced Security:** Zero-OS prevents tampering with images, ensuring higher security levels.
-- **Reduced Storage and Bandwidth:** Zero-OS significantly reduces storage and bandwidth requirements, potentially achieving up to a 100-fold improvement.
-- **Deterministic Deployments:** Engineers can precisely define deployments beforehand, ensuring predictable outcomes without changes during deployment.
-- **100% compatible:** with existing standards, docker, virtual machines... The same format is useful for VM's as well as any container technology.
-
-### Status?
-
-- Usable for years, see Zero-OS.
-
-
-## Zero-Stor : a quantum safe backend storage system.
-
-### Why?
-
-Traditional backend storage systems have their roots in centralized environments, focusing on low-latency and closed security setups. However, these characteristics make them less suitable for use in decentralized cloud contexts.
-
-Newer-generation storage systems like protocol-driven or blockchain-based solutions may face scalability and performance limitations and may not fulfill certain critical requirements that we consider essential.
-
-### What?
-
-A redesigned storage system which can scale to planet level, is super secure private and fast enough for more usecases. Its designed to operate in a decentralized context. Data can never be lost of corrupted.
-
-This storage system is a backend storage system, cannot be used by end users, its meant to be integrated with a front end storage system like e.g. S3 or a filesystem (see next section).
-
-
-### Benefits?
-
-
-- **Data Resilience:** Ensures data is never lost or corrupted.
-- **Planetary Scalability:** Capable of scaling to a global level.
-- **Cost-Efficient:** Offers exceptional cost efficiency.
-- **Versatility:** Suitable for various use cases, including archiving, backup, files, and CDNs.
-- **Low Overhead:** Requires only a 20% overhead for building a storage network where any four nodes can be lost simultaneously, compared to a 400% overhead in traditional storage systems.
-- **Security and Privacy:** Provides robust security, even impervious to quantum computers.
-- **Data Sovereignty:** Users have complete control over data placement.
-- **Empowering Front-End Applications:** Can be integrated into various front-end storage applications, such as blockchains, archives, or S3.
-- **CDN Support:** Functions effectively as a backend for CDN applications, facilitating content delivery.
-- **Sustainability:** Uses 10 times less energy compared to traditional storage systems, contributing to sustainability efforts.
-- **Locality Aware:** Data can be delivered to where the users are ideal for sovereign usecases.
-
-
-### Status?
-
-- Zero-OS has been in beta for over four years, with continuous development and improvement.
-- A notable deployment in Switzerland, with over 50 petabytes of storage capacity, served as a substantial test environment, although it's no longer active.
-- Within the current TFGrid network, there's an impressive capacity of over 20 petabytes available for use.
-- Lacking some monitoring, documentation ... will be added in TFGrid 3.15
-- Previous releases have been successfully utilized by major government organizations on a massive scale (hundreds of petabytes), providing strong evidence of the concept's viability and effectiveness.
-
-
-
-## Quantum Safe File System 
-
-
-### Why?
-
-There is a growing need for more accessible and user-friendly solutions to store and manage large volumes of data efficiently.
-
-While Zero-Stor addresses numerous storage challenges effectively, it may not be accessible or user-friendly for typical developers or system administrators. QSFS has been developed to bridge this gap and provide a more approachable storage solution.
-
-### What?
-
-A FUSE-based filesystem utilizing Zero-Stor as its backend. Metadata is safeguarded to prevent loss, inheriting Zero-Stor's benefits and simplifying usage for developers and system administrators.
-
-The filesystem is always deployed in one location, data is distributed (using zero-stor) across multiple sites for unparalleled reliability. 
-
-Metadata redundancy is included. While not consistently synchronized in real-time, the system allows configuration of consistency levels. Typically, the decentralized state may lag by up to 15 minutes.
-
-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.
-- Provides a user-friendly interface for seamless integration with a wide range of applications.
-- Offers considerable scalability capabilities, although not unlimited in scale.
-- Achieves reasonable performance data transfer rates of up to 50 MB/sec, particularly for larger files.
-- Can scale to about 2 million files per filesystem.
-
-## FungiStor (end 2024)
-
-### Why?
-
-Existing blockchain, internet, and P2P content delivery and storage systems suffer from sluggish performance and are too expensive. Content retrieval is often slow, and the overhead for ensuring redundancy is excessive. We require innovative approaches to facilitate efficient information sharing among users.
-
-Content delivery frequently represents the most significant expense for social networks. Running a basic social video network for 10 million users currently costs approximately $2 million per month using traditional cloud providers. We have the potential to reduce this cost by several orders of magnitude.
-
-
-### What?
-
-FungiStor is a peer-to-peer (P2P) content delivery layer designed to store and distribute an extensive range of objects, including images, videos, files, and more. It has the capability to handle trillions of objects and files efficiently. FungiStor serves as an excellent solution for content delivery networks (CDNs), significantly reducing costs for organizations seeking to stream or deliver substantial data volumes to their user base.
-
-Furthermore, FungiStor will act as the backend infrastructure for the Flists within our own system. However, it is versatile and can be utilized by anyone in need of a global-level content delivery system for files, objects, and images.
-
-### Benefits?
-
-- **Global Scalability, Sub-50ms Lookups:** FungiStor scales worldwide with ultra-fast data retrieval under 50 milliseconds.
-- **Localized Content Delivery:** Prioritizes local data access for optimized speed and efficiency.
-- **Quantum-Safe Security:** Incorporates robust quantum security measures.
-- **Interoperability:** Works seamlessly with IPFS, Torrent, and more.
-- **Cost Efficiency:** Offers significant cost savings, potentially 10 to 100 times less than conventional solutions.
-
-## NetworkWall (OEM only)
-
-### Why?
-
-Traditional firewalls are increasingly ineffective in addressing modern security challenges. They struggle to mitigate emerging threats, particularly against backdoors and man-in-the-middle attacks. Backdoors can render firewalls obsolete as attackers find ways to bypass them. New, innovative approaches to cybersecurity are necessary to address these evolving security problems.
-
-## What?
-
-Imagine a scenario where you deploy applications within secure, liquid-cooled physical containers or smaller POD's that operate without relying on traditional TCP/IP or Ethernet protocols. By avoiding the use of standard low-level protocols, the existing backdoors are unable to communicate with the external world.
-
-Incoming traffic is intercepted at the application level and securely transported into the protected environment through physical communication mechanisms based on RDMA (Remote Direct Memory Access). The integration of this solution into Zero-OS ensures a seamless and transparent experience for developers and system administrators.
-
-It's important to note that this solution is primarily intended for commercial use cases, but its existence is valuable knowledge in the realm of cybersecurity and network security.
-
-## Benefits
-
-- **Enhanced Security and Privacy:** The solution offers significantly improved security and privacy measures, mitigating potential risks and vulnerabilities.
-- **Ultra-Fast Connectivity:** Within the POD/Container, the connectivity is exceptionally fast, ensuring rapid data transfer and application performance.
-- **Robust Data and Application-Aware Proxies:** Secure proxies between the Internet and the protected backend application provide an additional layer of security, safeguarding data and ensuring application-level awareness.
-- **Seamless Integration:** The solution is designed for ease of integration within existing environments, minimizing disruptions and complexities during implementation.

collections/tech/layers/capacity_layer_intro.md

@@ -0,0 +1,52 @@
+## ThreeFold Capacity Layer
+
+![](img/architecture_why_us.jpg) 
+
+### Zero-OS
+
+ThreeFold has build its 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. 
+
+Zero-OS supports a small number of primitives, and performs low-level functions natively. 
+
+It delivers 3 primitive functions:
+ 
+- storage capacity
+- compute capacity 
+- network capacity
+
+There is no shell, local nor remote attached to Zero-OS. It does not allow for inbound network connections to happen to the core. Also, 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) Internet, meaning hackers cannot get in, while also eliminating human error from the paradigm. 
+
+### TFNode
+
+The ThreeFold_Grid needs hardware/servers to function. Servers of all shapes and sizes can be added to the grid by anyone, anywhere in the world. The production of Internet Capacity on the Threefold Grid is called Farming and people who add these servers to the grid are called Farmers. This is a fully decentralized process and they get rewarded by the means of TFT. 
+
+Farmers download the Zero-OS operating system and boot their servers themselves. Once booted, these servers become TFNodes. The TFNodes will register themselves in a database called the TF Explorer. Once registered in the TF Explorer, the capacity of the TFNodes will become available on the TF Grid Explorer. Also, given the autonomous nature of the ThreeFold Grid, there is no need for any intermediaries between the user and TFNodes. 
+
+This enables a complete peer2peer environment for people to reserve their Internet Capacity directly from the hardware.
+
+### 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.
+
+Learn more about smart contract for IT [here](../smartcontract_it/smartcontract_it_full.md).
+
+### TFChain
+
+A blockchain running on the TFGrid stores the following information (TFGrid 3.0)
+
+- registry for all digital twins (identity system, aka phonebook)
+- registry for all farmers & 3nodes
+- registry for our reputation system
+- info as required for the Smart Contract for IT
+
+This is the hart of our operational system of the TFGrid
+
+### Peer-to-Peer Network
+
+The peer2peer network allows any zmachine or user to connect with other zmachine or users on the TF Grid securely, and creates a private shortest path peer2peer network. 
+
+### Web Gateway
+
+ The Web Gateway is a mechanism to connect the private (overlay) networks 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. 

collections/tech/layers/technology_layers.md

@@ -0,0 +1 @@
+# Layers

collections/tech/natural_progression/how_does_it_work.md

@@ -0,0 +1,43 @@
+
+
+#  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.
+
+> We have a vision of the Internet which is much more close to how the Internet was intended to be.
+
+
+![alt text](natural_progression.png)
+
+We believe in a world where every person is the center of his/her digital life.  In this new Internet each person has his/her own digital avatar which we call a hero. 
+
+The technical component which makes hero possible is a compoment called 3bot. This 3Bot server is only owned and managed by you lives on top of the ThreeFold Cloud.
+
+All the 3Bots communicate to each other over the shortest possible path, this path is end2end encrypted.
+
+
+![alt text](arch_minimal.png)
+
+The underlying network of capacity is the ThreeFold Cloud which is the IT Energy which makes all possible.
+
+The ThreeFold Cloud is the result of more than 10 years of development and now active on more than 2000 nodes.
+
+
+## Requirements For A New Internet
+
+![alt text](requirements.png)
+
+- Compute, Storage, Network need to be
+  - Local
+  - Sovereign
+  - Private
+  - More Secure
+- Storage needs to be
+  - More reliable with less overhead (only 20% overhead needed)
+  - Capable to be global and be used as CDN (Content Delivery Network)
+  - Fast enough for the Use Case at hand
+- Network needs to be
+  - 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)

collections/tech/primitives/compute/beyond_containers.md

@@ -0,0 +1,14 @@
+## Compatible
+
+Default features:
+
+- compatible with Docker
+- compatible with any Linux workload
+
+We have following unique advantages:
+
+- no need to work with images, we work with our unique zos_fs
+- every container runs in a dedicated virtual machine providing more security
+- the containers talk to each other over a private network: zos_net
+- the containers can use web_gw to allow users on the internet connect to the applications as running in their secure containers 
+- can use core-x to manage the workload

collections/tech/primitives/compute/compute.md

@@ -0,0 +1,8 @@
+
+## TFGrid Compute Layer
+
+![](img/tfgrid_compute_.jpg)
+
+We are more than just Container or VM technology, see [our Beyond Container Document](../../primitives/compute/beyond_containers.md).
+
+For more information see [ZeroOS](../../zos/zos_toc.md)

collections/tech/primitives/compute/corex.md

@@ -0,0 +1,13 @@
+
+# CoreX
+
+![](img/corex.jpg)
+
+This tool allows you to manage your ZMachine over web remotely.
+
+ZMachine process manager
+
+- Provide a web interface and a REST API to control your processes
+- Allow to watch the logs of your processes
+- Or use it as a web terminal (access over https to your terminal)!
+

collections/tech/primitives/compute/zkube.md

@@ -0,0 +1,30 @@
+# ZKube
+
+TFGrid is compatible with Kubernetes Technology.
+
+![](img/kubernetes_0_.jpg)
+
+Each eVDC as shown above is a full blown Kubernetes deployment.
+
+### Unique for our Kubernetes implementation
+
+- The Kubernetes networks are on top of our [ZNet](znet) technology which means all traffic between containers and kubernetes hosts is end2end encrypted independent of where your Kubernetes nodes are deployed.
+- You can mount a QSFS underneath a Kubernetes Node (VM), which means that you can deploy containers on top of QSFS to host unlimited amounts of storage in a super safe way.
+- You Kubernetes environment is for sure 100% decentralized, you define where you want to deploy your Kubernetes nodes and only you have access to the deployed workloads on the TFGrid.
+
+### Features
+
+*   integration with znet (efficient, secure encrypted network between the zmachines)
+*   can be easily deployed at the edge
+*   single-tenant!
+
+<!-- 
+### ZMachine Benefits
+
+*   [ZOS Protect](zos_protect): no hacking surface to the Zero-Nodes, integrate silicon route of trust
+*   [ZNet](znet) and [Planetary Net](planetary_network): a true global single backplane network connecting us all -->
+
+### Architecture
+
+![](img/zkube_architecture_.jpg)
+

collections/tech/primitives/compute/zmachine.md

@@ -0,0 +1,22 @@
+# ZMachine
+
+
+
+### Features
+
+*   import from docker (market std for containers)
+*   can be easily deployed at the edge (edge cloud)
+*   single-tenant, fully decentralized!
+*   can deploy unlimited amounts of storage using our qsfs
+*   minimal hacking surface to the Zero-Nodes, integrate silicon route of trust
+*   ZOS Filesystem: dedupe, zero-install, hacker-proof
+*   Webgateway: intelligent connection between web (internet) and container services
+*   integration with ZNet (efficient, secure encrypted network between the zmachines)
+*   Planetary Net: a true global single backplane network connecting us all
+
+### Architecture
+
+![](img/zmachine_zos_.jpg)
+
+A ZMachine is running as a virtual machine on top of Zero-OS.
+

collections/tech/primitives/network/mycelium.md

@@ -0,0 +1,49 @@
+
+# Mycelium our Planetary Network
+
+![](img/planet_net_.jpg)
+
+> TODO: need to upgrade image, also digital twin needs to be named '3bot'
+
+The planetary network is an overlay network which lives on top of the existing internet or other peer2peer networks created. In this network, everyone is connected to everyone. End-to-end encryption between users of an app and the app running behind the network wall.
+
+Each user end network point is strongly authenticated and uniquely identified, independent of the network carrier used. There is no need for a centralized firewall or VPN solutions, as there is a circle based networking security in place.
+
+Benefits :
+- It finds shortest possible paths between peers
+- There's full security through end-to-end encrypted messaging
+- It allows for peer2peer links like meshed wireless
+- It can survive broken internet links and re-route when needed
+- It resolves the shortage of IPV4 addresses
+
+
+Whereas current computer networks depend heavily on very centralized design and configuration, this networking concept breaks this mould by making use of a global spanning tree to form a scalable IPv6 encrypted mesh network. This is a peer2peer implementation of a networking protocol.
+
+The following table illustrates high-level differences between traditional networks like the internet, and the planetary threefold network:
+
+| Characteristic                                                  | Traditional | Mycelium |
+| --------------------------------------------------------------- | ----------- | ----------------- |
+| End-to-end encryption for all traffic across the network        | No          | Yes               |
+| Decentralized routing information shared using a DHT            | No          | Yes               |
+| Cryptographically-bound IPv6 addresses                          | No          | Yes               |
+| Node is aware of its relative location to other nodes           | No          | Yes               |
+| IPv6 address remains with the device even if moved              | No          | Yes               |
+| Topology extends gracefully across different mediums, i.e. mesh | No          | Yes               |
+
+## What are the problems solved here?
+
+The internet as we know it today doesn’t conform to a well-defined topology. This has largely happened over time - as the internet has grown, more and more networks have been “bolted together”. The lack of defined topology gives us some unavoidable problems:
+
+- The routing tables that hold a “map” of the internet are huge and inefficient
+- There isn’t really any way for a computer to know where it is located on the internet relative to anything else
+- It’s difficult to examine where a packet will go on its journey from source to destination without actually sending it
+- It’s very difficult to install reliable networks into locations that change often or are non-static, i.e. wireless mesh networks
+
+These problems have been partially mitigated (but not really solved) through centralization - rather than your computers at home holding a copy of the global routing table, your ISP does it for you. Your computers and network devices are configured just to “send it upstream” and to let your ISP decide where it goes from there, but this does leave you entirely at the mercy of your ISP who can redirect your traffic anywhere they like and to inspect, manipulate or intercept it.
+
+In addition, wireless meshing requires you to know a lot about the network around you, which would not typically be the case when you have outsourced this knowledge to your ISP. Many existing wireless mesh routing schemes are not scalable or efficient, and do not bridge well with existing networks.
+
+![](img/planetary_net.jpg)
+
+The planetary network is a continuation and implementation of the [Planetary Network](https://Planetary Network-network.github.io/about.html) network initiative. This technology is in beta but has been proven to work already quite well.
+

collections/tech/primitives/network/network.md

@@ -0,0 +1,13 @@
+# Network Primitives
+
+- [Planetary network](planetary_network.md): 
+    - is a planetary scalable network, we have clients for windows, osx, android and iphone.
+- [ZOS Net](znet.md):
+    - is a fast end2end encrypted network technology, keep your traffic between your z_machines 100% private.
+- [ZOS NIC](znic.md): 
+    - connection to a public ipaddress
+- [WEB GW](webgw3.md): 
+    - web gateway, a secure way to allow internet traffic reach your secure Z-Machine.
+
+
+

collections/tech/primitives/network/networking.md

@@ -0,0 +1,32 @@
+![](img/zos_network_overlay.jpg)
+
+# ThreeFold Network Technology Overview
+
+Decentralized networking platform allowing any compute and storage workload to be connected together on a private (overlay) network and exposed to the existing internet network. The Peer2Peer network platform allows any workload to be connected over secure encrypted networks which will look for the shortest path between the nodes.
+
+### Secure mesh overlay network (peer2peer)
+
+Z_NET is the foundation of any architecture running on the TF Grid. It can be seen as a virtual private datacenter and the network allows all of the *N* containers to connect to all of the *(N-1)* other containers. Any network connection is a secure network connection between your containers, it creates peer 2 peer network between containers. 
+
+![alt text](net1.png)
+
+No connection is made with the internet. The ZNet is a single tenant network and by default not connected to the public internet. Everything stays private. For connecting to the public internet, a Web Gateway is included in the product to allows for public access if and when required.
+
+### Redundancy
+
+As integrated with [WebGW](webgw):
+
+![alt text](net2.png)
+
+- Any app can get (securely) connected to the internet by any chosen IP address made available by ThreeFold network farmers through [WebGW](webgw)
+- An app can be connected to multiple web gateways at once, the DNS round robin principle will provide load balancing and redundancy
+- An easy clustering mechanism where web gateways and nodes can be lost and the public service will still be up and running
+- Easy maintenance. When containers are moved or re-created, the same end user connection can be reused as that connection is terminated on the Web Gateway. The moved or newly created Web Gateway will recreate the socket to the Web Gateway and receive inbound traffic.
+
+### Network Wall
+
+![](network_wall.png)
+
+For OEM projects we can implement the ThreeFold project without using TCP-IP or Ethernet this can lead to super secure environments, ideal to battle the Cuber Pandemic.
+
+

collections/tech/primitives/network/webgw.md

@@ -0,0 +1,42 @@
+
+
+# TFGrid WebGW
+
+The Web Gateway is a mechanism to connect the private networks to the open Internet, in such a way that there is no direct connection between internet and the secure workloads running in the ZMachines.
+
+![](img/webgateway.jpg)
+
+
+
+
+- Separation between where compute workloads are and where services are exposed
+- Redundant
+    - Each app can be exposed on multiple webgateways at once
+- Support for many interfaces...
+- Helps resolve shortage of IPv4 addresses
+
+### Implementation
+
+Some 3nodes supports gateway functionality (configured by the farmers). A 3node with gateway configuration can then accept gateway workloads and then forward traffic to ZMachines that only have Planetary Network (planetary network) or Ipv6 addresses.
+
+The gateway workloads consists of a name (prefix) that need to be reserved on the block chain first. Then the list of backend IPs. There are other flags that can be set to control automatic TLS (please check terraform documentations for the exact details of a reservation).
+
+Once the 3node receives this workloads, the network configure proxy for this name and the Planetary Network IPs.
+
+### Security
+
+ZMachines have to have a Planetary Network IP or any other IPv6 (also IPv4 are accepted), it means that any person who is connected to the Planetary Network, can also reach the ZMachine without the need for a proxy.
+
+So it's up to the ZMachine owner/maintainer to make sure it is secured and only have the required ports open.
+
+### Redundant Network Connection
+
+![](img/redundant_net.jpg)
+
+
+### Unlimited Scale
+
+![](img/webgw_scaling.jpg)
+
+
+The network architecture is a pure scale-out network system, it can scale to unlimited size, there is simply no bottleneck. Network "supply" is created by network farmers, and network "demand" is done by TF Grid users. Supply and demand scale independently, for supply there can be unlimited network, farmers providing the web gateways on their own 3nodes, and unlimited compute farmers providing 3nodes for compute and storage. The demand side is driven by developers creating software that runs on the grid, system integrators creating solutions for enterprises. This demand side is exponentially growing for data processing and storage use cases.

collections/tech/primitives/network/znic.md

@@ -0,0 +1,11 @@
+# ZNIC
+
+ZNIC is the network interface which is connected to ZMachine.
+
+Can be implemented as interface to
+
+- planetary_network
+- public ip address on a Zero-OS
+
+![](img/znet_znic.jpg)
+