...
This commit is contained in:
@@ -1,5 +0,0 @@
|
||||
{
|
||||
"label": "Architecture",
|
||||
"position": 10,
|
||||
"link": {"type": "generated-index"}
|
||||
}
|
||||
@@ -1,14 +0,0 @@
|
||||
---
|
||||
sidebar_position: 1
|
||||
---
|
||||
|
||||
|
||||
# Base Layer for Many Usecases
|
||||
|
||||
|
||||
|
||||
Our Decentralized Cloud Technology the ideal platform for hosting any web3 and AI workloads.
|
||||
|
||||
Our Zero-OS operating system also supports integrated GPUs, ensuring optimal performance for decentralized AI applications.
|
||||
|
||||
> Any workload (web2/3 and AI) can run on on our Decentralized Cloud.
|
||||
@@ -1,27 +0,0 @@
|
||||
---
|
||||
sidebar_position: 2
|
||||
---
|
||||
|
||||
|
||||
# Architecture Cloud Engine
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
The 3 Nodes form the base layer, providing compute, storage, and network capabilities.
|
||||
|
||||
The quantum safe network enables all IT workloads to communicate with one another using the most efficient route and the strongest security measures.
|
||||
|
||||
|
||||
|
||||
The Storage layer make sure we all have perfect control over our storage and can never loose our information.
|
||||
|
||||
|
||||
|
||||
## Autonomous Deployments
|
||||
|
||||
|
||||
|
||||
The hero's can deploy and manage IT workloads on our behalf.
|
||||
|
||||
@@ -1,32 +0,0 @@
|
||||
---
|
||||
sidebar_position: 4
|
||||
---
|
||||
|
||||
# Hero as Virtual System Administrator
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Every individual has a personal Hero—a virtual assistant that manages your digital life and serves as your system administrator for AI or Edge Cloud workloads.
|
||||
|
||||
These Heroes communicate with each other over the private Mycelium network, which offers a secure message bus for scalable and secure communication.
|
||||
|
||||
A Hero can store an unlimited amount of information, and only your Hero has access to this data, deciding how and when it can be shared with other Heroes or AI systems.
|
||||
|
||||
Active 24/7, your Hero continuously monitors your IT infrastructure. If something goes wrong, the Hero will automatically resolve the issue, ensuring smooth and uninterrupted service.
|
||||
|
||||
|
||||
### Natural Evolution
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
We believe this represents the natural evolution away from reliance on centralized services.
|
||||
|
||||
With millions of Heroes working together, can form a collective global intelligence, leveraging various tools to interact with existing services on behalf of their users within all safety of our own sovereignity.
|
||||
|
||||
|
||||
|
||||
@@ -1,64 +0,0 @@
|
||||
---
|
||||
sidebar_position: 3
|
||||
---
|
||||
|
||||
# Architecture for an Upgraded Internet
|
||||
|
||||
|
||||
|
||||
|
||||
- **3Nodes**: Deliver compute, storage, and GPU capacity.
|
||||
- **Mycelium Routers**: Allow all Mycelium Network participants to communicate with each other and also connect over existing Internet links. Mycelium Routers provide bandwidth to our ecosystem.
|
||||
- **WebGateways**: Provide a bridge between the current Internet and the Mycelium Network.
|
||||
- **Hero 3Bots**: Represent our digital lives and possess the knowledge to act as virtual system administrators, ensuring our IT workloads remain operational.
|
||||
- **Users**: Arrange their digital lives through their Hero 3Bots.
|
||||
- **AI Clouds**: Are created by connecting GPUs from the 3Nodes over the Mycelium Network.
|
||||
|
||||
## 3Nodes
|
||||
|
||||
Each 3node provides compute, storage and network capacity, its the core capacity layer of the cloud.
|
||||
|
||||
|
||||
|
||||
A cloud needs hardware/servers to function. Servers of all shapes and sizes can be added. The production of Cloud Capacity is called Farming and parties who add these servers to the grid are called Farmers.
|
||||
|
||||
Farmers download the Zero-OS operating system and boot their servers. Once booted, these servers become 3Nodes. The 3Nodes will register themselves in a blockchain. Once registered, the capacity of the 3Nodes will become available. This enables a peer2peer environment for people or companies to reserve their Internet Capacity directly from the hardware but yet allowing full control by commercial parties if that would be required.
|
||||
|
||||
Each 3Node is running our Zero-OS operating system.
|
||||
|
||||
## Mycelium Routers
|
||||
|
||||
Mycelium is an end-to-end encrypted overlay meshed wireless network with agents available for any desktop and mobile operating system.
|
||||
|
||||
We have also created a dedicated Mycelium Router. Mycelium Routers seamlessly integrate with our Mycelium network technology, efficiently selecting the shortest path between all participants.
|
||||
|
||||
These Mycelium Routers are compatible not only with Satelite, Wi-Fi but also with 4G and 5G networks, ensuring versatile connectivity options.
|
||||
|
||||
The Mycelium Routers can be installed in locations with substantial network capacity, allowing everyone to bridge between the current Internet and the overlay Mycelium network.
|
||||
|
||||
## Web Gateways
|
||||
|
||||
The Web Gateway serves as a mechanism to connect the private (overlay) networks (Mycelium) to the open Internet.
|
||||
|
||||
By not providing an open and direct path into the private network, many malicious phishing and hacking attempts are stopped at the Web Gateway level for container applications.
|
||||
|
||||
The Web Gateways provide HTTP(S) and, in the future, other web services, which get forwarded to the relevant service exposing itself over Mycelium. This setup offers multiple access points to various backend services.
|
||||
|
||||
|
||||
## TFChain: Our Blockchain
|
||||
|
||||
This blockchain does the following:
|
||||
|
||||
- registry for all 3bots (identity system, aka phonebook)
|
||||
- registry for all farmers & 3nodes
|
||||
- registry for our reputation system
|
||||
- info as required for the Smart Contract for IT
|
||||
|
||||
This is the hart of our operational system of our decentralized cloud.
|
||||
|
||||
|
||||
## Ultra Scalable
|
||||
|
||||
|
||||
|
||||
This architecture scales to the planet.
|
||||
@@ -1,7 +0,0 @@
|
||||
{
|
||||
"label": "Core Features",
|
||||
"position": 9,
|
||||
"link": {
|
||||
"type": "generated-index",
|
||||
}
|
||||
}
|
||||
@@ -1,7 +0,0 @@
|
||||
{
|
||||
"label": "Compute",
|
||||
"position": 2,
|
||||
"link": {
|
||||
"type": "generated-index",
|
||||
}
|
||||
}
|
||||
@@ -1,24 +0,0 @@
|
||||
---
|
||||
sidebar_position: 1
|
||||
title: Compute Layer
|
||||
---
|
||||
|
||||
# Compute Layer
|
||||
|
||||
|
||||
|
||||
Default features:
|
||||
|
||||
- Compatible with Docker
|
||||
- Compatible with any VM (Virtual Machine)
|
||||
- Compatible with any Linux workload
|
||||
- Integrated unique storage & network primitives
|
||||
- Integrated smart contract for IT layer
|
||||
|
||||
We have the 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 (Mycelium)
|
||||
- The containers can use a web gateway to allow internet users to connect to the applications which are running in their secure containers
|
||||
- Can use core-x to manage the workload
|
||||
@@ -1,39 +0,0 @@
|
||||
---
|
||||
sidebar_position: 3
|
||||
title: Zero-Deploy
|
||||
---
|
||||
|
||||
|
||||
## Deterministic Deployment
|
||||
|
||||
|
||||
The concept of Zero-Deploy is a key component of the **Smart Contract for IT** framework, which can be applied to any type of workload—whether it's containers, virtual machines (VMs), network gateways, volumes, Kubernetes resources, or other network elements. This framework serves as a formal agreement between a farmer (provider) and a user regarding the deployment of an IT workload.
|
||||
|
||||
### Process
|
||||
|
||||
1. **Build Your Code**
|
||||
Develop and prepare your application code.
|
||||
|
||||
2. **Convert to Zero-Image**
|
||||
Use a CI/CD solution (e.g., Hero CI/CD) to convert your Docker build (or other format) into a Zero-Image format.
|
||||
|
||||
3. **Define the Workload**
|
||||
Specify all the details of your workload, including network bridges, web gateways, required machines, and more.
|
||||
|
||||
4. **Register and Sign**
|
||||
Register the workload and sign it with your private key.
|
||||
|
||||
5. **Automatic Detection**
|
||||
All necessary Zero-OS nodes (our infrastructure) will detect that a new workload needs to be deployed.
|
||||
|
||||
6. **Deployment Process**
|
||||
The nodes will pull down the formal workload descriptions and initiate the deployment process.
|
||||
|
||||
7. **Validation**
|
||||
Every step of the deployment is verified by Zero-OS (ZOS) to ensure that the intended result is accurately replicated. If any discrepancies are detected, ZOS will halt the deployment and provide an error message.
|
||||
|
||||
### Benefits
|
||||
|
||||
- **Deterministic Deployment**: There is no dynamic behavior during deployment at runtime, ensuring a consistent and predictable outcome.
|
||||
- **Strict Compliance**: No process can start unless all files and configurations are fully described at the flist level.
|
||||
|
||||
@@ -1,35 +0,0 @@
|
||||
---
|
||||
sidebar_position: 4
|
||||
title: Zero-Install
|
||||
---
|
||||
|
||||
|
||||
## Zero install
|
||||
|
||||
|
||||
|
||||
The Zero-OS is delivered to the 3Nodes over the internet network (network boot) and does not need to be installed.
|
||||
|
||||
|
||||
### 3Node Install
|
||||
|
||||
1. Deploy a computer
|
||||
2. Configure a farm on the TFGrid explorer
|
||||
3. Download the bootloader and put on a USB stick or configure a network boot device
|
||||
4. Power on the computer and connect to the internet
|
||||
5. Boot! The computer will automatically download the components of the operating system (Zero-OS)
|
||||
|
||||
The actual bootloader is very small, it brings up the network interface of your computer and queries TFGrid for the remainder of the boot files needed.
|
||||
|
||||
The operating system is not installed on any local storage medium (hard disk, ssd), Zero-OS is stateless.
|
||||
|
||||
The mechanism to allow this to work in a safe and efficient manner is an innovation called our container virtual filesystem.
|
||||
|
||||
### Process
|
||||
|
||||
- optionally: configure booting from secure BIOS
|
||||
- optionally: install signing certificate in the BIOS, to make sure that only the right bootloader can be started
|
||||
- the bootloader (ISO, PXE, USB, ...) get's downloaded from Internet (TFGrid CDN or private deployment)
|
||||
- core-0 (the first boot process) starts, self verification happens
|
||||
- the metadata for the the required software modules is downloaded and checked against signature and hashes
|
||||
- the core-0 zero_image service
|
||||
@@ -1,46 +0,0 @@
|
||||
---
|
||||
sidebar_position: 2
|
||||
title: Zero-OS
|
||||
---
|
||||
|
||||
|
||||
# Zero-OS
|
||||
|
||||
|
||||
|
||||
A revolutionary operating system which can be booted on most modern computers. Once installed Zero-OS locks the hardware and makes it accessible to the decentralized marketplace or a centralized ultra secure deployment system. Blockchain mechanism can be used to strongly control how workloads are deployed on the system.
|
||||
|
||||
|
||||
|
||||
## ZOS Compute & Storage Overview
|
||||
|
||||
|
||||
|
||||
## ZOS Network Overview
|
||||
|
||||
|
||||
|
||||
|
||||
### Imagine An Operating System With The Following Benefits
|
||||
|
||||
- Up to 10x more efficient for certain workloads (e.g. storage)
|
||||
- No install required
|
||||
- All files are deduped for the VM's, containers and the ZOS itself, no more data duplicated filesystems
|
||||
- The hacking footprint is very small which leads to much safer systems
|
||||
- Every file is fingerprinted and gets checked at launch time of an application
|
||||
- There is no shell or server interface on the operating system
|
||||
- The networks are end2end encrypted between all Nodes
|
||||
- It is possible to completely disconnect the compute/storage from the network service part which means hackers have a lot less chance to access the data
|
||||
- A smart contract for the IT layer allows groups of people to deploy IT workloads with consensus and full control
|
||||
- All workloads which can run on linux can run on Zero-OS but in a much more controlled, private and safe way
|
||||
|
||||
> We have created an operating system from scratch. We used the Linux kernel and its components and then built further on it. We have been able to achieve all of the above benefits.
|
||||
|
||||
## Requirements:
|
||||
|
||||
- **Autonomy**: TF Grid needs to create compute, storage and networking capacity everywhere. We could not rely on a remote (or a local) maintenance of the operating system by owners or operating system administrators.
|
||||
- **Simplicity**: An operating system should be simple, able to exist anywhere for anyone, and be good for the planet.
|
||||
- **Stateless**: In a grid (peer-to-peer) set up, the sum of the components provides a stable basis for single elements to fail and not bring the whole system down. Therefore, it is necessary for single elements to be stateless, and the state needs to be stored within the grid.
|
||||
|
||||
|
||||
|
||||
@@ -1,34 +0,0 @@
|
||||
---
|
||||
sidebar_position: 5
|
||||
title: ZKube
|
||||
---
|
||||
|
||||
|
||||
# ZKube
|
||||
|
||||
TFGrid is compatible with Kubernetes Technology.
|
||||
|
||||
|
||||
|
||||
### Unique for our Kubernetes implementation
|
||||
|
||||
- The Kubernetes networks are on top of our Mycelium 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 Quantum Safe Storage System 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 zero_vms)
|
||||
* can be easily deployed at the edge
|
||||
* single-tenant!
|
||||
|
||||
<!--
|
||||
### Zero VM 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
|
||||
|
||||
|
||||
|
||||
@@ -1,7 +0,0 @@
|
||||
{
|
||||
"label": "Network",
|
||||
"position": 4,
|
||||
"link": {
|
||||
"type": "generated-index",
|
||||
}
|
||||
}
|
||||
@@ -1,7 +0,0 @@
|
||||
{
|
||||
"label": "Storage",
|
||||
"position": 2,
|
||||
"link": {
|
||||
"type": "generated-index",
|
||||
}
|
||||
}
|
||||
7
docs/geoaware/_category_.json
Normal file
7
docs/geoaware/_category_.json
Normal file
@@ -0,0 +1,7 @@
|
||||
{
|
||||
"label": "The Solution \"Geo Aware\"",
|
||||
"position": 3,
|
||||
"link": {
|
||||
"type": "generated-index"
|
||||
}
|
||||
}
|
||||
32
docs/geoaware/geo_aware.md
Normal file
32
docs/geoaware/geo_aware.md
Normal file
@@ -0,0 +1,32 @@
|
||||
---
|
||||
sidebar_position: 1
|
||||
title: 'What is Geo Awareness'
|
||||
hide_title: true
|
||||
---
|
||||
|
||||
|
||||
|
||||
## What is Geo Awareness
|
||||
|
||||
**Geo-awareness** ensures that digital systems operate with respect to geographic and physical realities. This concept radically shifts how we approach storage, computation, and networking by enabling location-centric control and efficiency. Here's what it entails:
|
||||
|
||||
#### Key Features of Geo-Awareness:
|
||||
|
||||
1. **Shortest Physical Path for Communication**
|
||||
Communication between two parties happens through the shortest physical route, reducing latency and energy consumption while increasing efficiency.
|
||||
|
||||
2. **Data Sovereignty and Integrity**
|
||||
Users can decide where their data is stored. The data remains incorruptible and accessible only to the user or their personal AI agent, ensuring data privacy and sovereignty.
|
||||
|
||||
3. **Resilient Internet Functionality**
|
||||
Even in cases of internet outages or disasters, most apps and services remain operational, ensuring reliability and continuity.
|
||||
|
||||
4. **Control Over Applications and AI**
|
||||
Geo-awareness enables users to decide where their applications and personal AI agents operate, giving them full control over their digital footprint and reducing external vulnerabilities.
|
||||
|
||||
5. **Transparent Deployment of Code**
|
||||
Knowing exactly which code or app is deployed where ensures security and prevents tampering.
|
||||
|
||||
6. **Relevance for Nations and Public Infrastructure**
|
||||
Unlike public blockchains that lack geo-awareness, this model empowers countries with localized control, enhancing sovereignty and trust.
|
||||
|
||||
BIN
docs/geoaware/img/geo_aware.png
Normal file
BIN
docs/geoaware/img/geo_aware.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 792 KiB |
BIN
docs/geoaware/img/geo_aware2.png
Normal file
BIN
docs/geoaware/img/geo_aware2.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 884 KiB |
BIN
docs/geoaware/img/geo_aware3.png
Normal file
BIN
docs/geoaware/img/geo_aware3.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 648 KiB |
66
docs/geoaware/solution.md
Normal file
66
docs/geoaware/solution.md
Normal file
@@ -0,0 +1,66 @@
|
||||
---
|
||||
sidebar_position: 4
|
||||
title: 'Solution For a Better Internet'
|
||||
hide_title: true
|
||||
---
|
||||
|
||||
|
||||
|
||||
## Geo Awareness is the Solution for many of the Internet Problems
|
||||
|
||||
The problems:
|
||||
|
||||
- [Compare Electricity](../internet_today/compare_electricity.md) - Compares the inefficiency of relying on distant internet infrastructure to the absurdity of using electricity generated on the other side of the world.
|
||||
- [Internet Basics](../internet_today/internet_basics.md) - Explains the three fundamental layers of the internet: compute/AI/storage, network, and applications, highlighting current centralization issues.
|
||||
- [Centralization Risk](../internet_today/centralization_risk.md) - Details the dangers of relying on centralized infrastructure and services, using real-world examples like the Ukraine conflict.
|
||||
- [The Race For Intelligence](../internet_today/ai.md) - Discusses how AI agents will replace traditional apps within 2 years and the implications of centralized AI development.
|
||||
- [GDP Negative Impact](../internet_today/gdp_negative.md) - Reveals how the current internet structure causes economic losses for developing nations, with case studies showing billions in yearly losses.
|
||||
- [Internet Protocol Is Broken](../internet_today/internet_risk.md) - Explains why TCP/IP's outdated design is inadequate for modern internet needs and explores RINA as a potential solution.
|
||||
- [Painkillers Approach](../internet_today/onion_analogy.md) - Uses an onion analogy to illustrate how adding layers to internet infrastructure masks symptoms rather than solving core problems.
|
||||
|
||||
|
||||
**The following table shows how the problems as listed above are fixed because of geo awareness.**
|
||||
|
||||
|
||||
| **Problem Area** | **Web2** | **Web3** | **Web 0 = Geo-Aware** |
|
||||
| ---------------------------------- | ----------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------- |
|
||||
| **Centralization** | Dominated by a few corporations; creates fragility and dependency. | Often more Decentralized, but lacks local autonomy; often relies on centralized validators and still datacenters. | Fully decentralized and location-specific, empowering local infrastructure and sovereignty. |
|
||||
| **Data Sovereignty** | Data stored in centralized data centers controlled by corporations. | Decentralized storage, but users often lack control over physical location. | Users choose specific locations for data storage, ensuring sovereignty and privacy. |
|
||||
| **Infrastructure Resilience** | Vulnerable to disasters, geopolitical issues, and single points of failure. | Often less resilient compared to Web2 (^1) | Shortest physical paths and local redundancies ensure continued operation during disruptions. New paths are found when needed even by using nodes from your friends |
|
||||
| **Economic Impact (GDP Negative)** | High costs for infrastructure; revenue flows to global platforms. | The validators are still too centralized and often hosted in centralized datanceters. Too complicated and too early days to help right now. | Localized infrastructure boosts regional economies, keeping revenue within countries. |
|
||||
| **Internet Efficiency** | Long data routes; underutilized hardware; inefficient layers. | Reliant on outdated protocols, vulnerable because of used ledger tech (^1) and layered inefficiencies. | Shortest paths reduce latency and cost; full hardware optimization ensures efficiency. |
|
||||
| **Security and Transparency** | Complex, security by smart employees of the corporations. | Smart contracts improve security, but issues remain as code upgrade path. | Transparent and tamper-proof deployments ensure security and resilience. |
|
||||
| **Layer Complexity** | Redundant layers create inefficiencies and fragility. | Often web3 is more complex compared to web 2. | Simplifies architecture by localizing compute, storage, and networking. 10x less development effort is possible |
|
||||
| **Application Hosting** | Hosted in large centralized data centers, increasing latency and cost. | Sometimes, decentralized hosting but not geographically optimized. | Applications can be hosted locally, reducing latency and ensuring autonomy. |
|
||||
| **Access Inequality** | Over 50% of the world lacks reliable access. | Expands access but without addressing local infrastructure challenges. | Geo-aware systems build localized, affordable infrastructure to improve access. |
|
||||
| **Session Management** | Breaks under interruptions; no native continuity. | Some continuity improvements via decentralized protocols. | Built-in session management ensures reliability even during disruptions. |
|
||||
|
||||
|
||||
|
||||
### Challenges in the Current Depin (Decentralized Internet) World
|
||||
|
||||
Despite advancements in decentralized technology, geo-awareness remains under-prioritized.
|
||||
|
||||
Current Web3 solutions focus on decentralization without accounting for the geographic efficiency or sovereignty that geo-awareness offers.
|
||||
|
||||
---
|
||||
|
||||
### Comparison Table: Current Web3 Solutions vs. Geo-Aware Systems
|
||||
|
||||
|
||||
| **Feature** | **Current Web3 Solutions** | **Geo-Awareness** |
|
||||
| ----------------------- | ------------------------------------------------------- | -------------------------------------------------------- |
|
||||
| **Storage** | Global, often randomly distributed without user control | Users choose storage locations; data remains sovereign |
|
||||
| **Compute** | Decentralized but lacks location-specific optimization | Compute occurs at chosen locations; optimized for region |
|
||||
| **Network** | Relies on global, non-optimized routing | Shortest physical path for communication |
|
||||
| **Ledger** | Public blockchains are unreliable in case of network issues | Location-aware sovereign ledgers for national and local control |
|
||||
| **Resilience** | Vulnerable to global internet disruptions | Independent operation during outages |
|
||||
| **Application Control** | Limited transparency on app deployment locations and upgrade paths. | Full control and visibility of app deployment |
|
||||
| **Data Integrity** | Prone to distributed risks and complexities | Tamper-proof, user-controlled data access |
|
||||
|
||||
|
||||
---
|
||||
|
||||
### Why Geo-Awareness Matters
|
||||
|
||||
The current centralized and globalized digital architecture exacerbates inefficiencies, compromises sovereignty, and creates economic dependencies. Geo-awareness addresses these problems by creating a decentralized yet location-sensitive framework. This ensures that infrastructure is resilient, secure, and operates in harmony with the physical realities of the world, ultimately empowering users and nations alike.
|
||||
@@ -1,6 +1,6 @@
|
||||
{
|
||||
"label": "Internet Re-Invented",
|
||||
"position": 3,
|
||||
"position": 4,
|
||||
"link": {
|
||||
"type": "generated-index",
|
||||
}
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
sidebar_position: 2
|
||||
---
|
||||
|
||||
# Architecture
|
||||
# Threefold Architecture
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Internet Re-Invented
|
||||
title: Internet Natural Progression
|
||||
sidebar_position: 2
|
||||
---
|
||||
|
||||
|
||||
@@ -21,7 +21,8 @@ In the decentralized infrastructure (DePIN) space, establishing trust and reliab
|
||||
|
||||
Customers often prefer to pay a higher price for cloud, AI, Internet services that guarantee better uptime and reliability.
|
||||
|
||||
For example, paying $10 per terabyte for a service with stellar uptime and customer support is more appealing than a $5 per terabyte service with frequent downtimes and minimal support. The value proposition lies in uninterrupted access to data and services, which is critical for business operations.
|
||||
For example, paying $10 per terabyte for a service with stellar uptime and customer support is more appealing than a $5 per terabyte service with frequent downtimes and minimal support. The value proposition lies in uninterrupted access to data and services, which is critical for business op
|
||||
erations.
|
||||
|
||||
### Service Level Agreements (SLAs)
|
||||
|
||||
|
||||
@@ -1,12 +1,9 @@
|
||||
---
|
||||
title: Decentralized Cloud Technology
|
||||
sidebar_position: 1
|
||||
title: Geo-Aware Cloud
|
||||
sidebar_position: 3
|
||||
---
|
||||
|
||||
|
||||
# Decentralized Cloud Technology Features
|
||||
|
||||
We present the highlights of our decentralized cloud technology that solves many of the current IT and cloud challenges.
|
||||
|
||||
|
||||
|
||||
14
docs/key_innovations_overview/compute_inno/for_everyone.md
Normal file
14
docs/key_innovations_overview/compute_inno/for_everyone.md
Normal file
@@ -0,0 +1,14 @@
|
||||
---
|
||||
title: 'For Everyone'
|
||||
sidebar_position: 2
|
||||
description: 'Everyone can build on top of the ThreeFold new internet'
|
||||
# hide_title: true
|
||||
---
|
||||
|
||||
## Zero-OS is easy to dploy
|
||||
|
||||
|
||||
|
||||
## Everyone Can Build
|
||||
|
||||
|
||||
BIN
docs/key_innovations_overview/compute_inno/img/deterministic.png
Normal file
BIN
docs/key_innovations_overview/compute_inno/img/deterministic.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 70 KiB |
BIN
docs/key_innovations_overview/compute_inno/img/for_everyone.png
Normal file
BIN
docs/key_innovations_overview/compute_inno/img/for_everyone.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 233 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 142 KiB |
BIN
docs/key_innovations_overview/compute_inno/img/superhub.png
Normal file
BIN
docs/key_innovations_overview/compute_inno/img/superhub.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 481 KiB |
BIN
docs/key_innovations_overview/compute_inno/img/zos_intro.png
Normal file
BIN
docs/key_innovations_overview/compute_inno/img/zos_intro.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 134 KiB |
BIN
docs/key_innovations_overview/compute_inno/img/zos_simple.png
Normal file
BIN
docs/key_innovations_overview/compute_inno/img/zos_simple.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 307 KiB |
16
docs/key_innovations_overview/compute_inno/super_hub.md
Normal file
16
docs/key_innovations_overview/compute_inno/super_hub.md
Normal file
@@ -0,0 +1,16 @@
|
||||
---
|
||||
title: 'Super HUB'
|
||||
sidebar_position: 20
|
||||
description: 'Ultra scalable architecture.'
|
||||
hide_title: true
|
||||
---
|
||||
|
||||
|
||||
## Superhub Architecture
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -1,13 +1,15 @@
|
||||
---
|
||||
title: Deterministic Deploy
|
||||
sidebar_position: 3
|
||||
sidebar_position: 5
|
||||
hide_title: true
|
||||
---
|
||||
|
||||
|
||||
|
||||
# Deterministic Deployment
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
## Deterministic Deployment
|
||||
|
||||
|
||||
The concept of Zero-Deploy is a key component of the **Smart Contract for IT** framework, which can be applied to any type of workload—whether it's containers, virtual machines (VMs), network gateways, volumes, Kubernetes resources, or other network elements. This framework serves as a formal agreement between a farmer (provider) and a user regarding the deployment of an IT workload.
|
||||
@@ -15,24 +17,28 @@ The concept of Zero-Deploy is a key component of the **Smart Contract for IT** f
|
||||
### Process
|
||||
|
||||
1. **Build Your Code**
|
||||
Develop and prepare your application code.
|
||||
2.
|
||||
Develop and prepare your application (AI agents, web 2, web 3) code.
|
||||
|
||||
2. **Convert to Zero-Image**
|
||||
Use a CI/CD solution (e.g., Hero CI/CD) to convert your Docker build (or other format) into a Zero-Image format.
|
||||
3. **Convert to Zero-Image**
|
||||
|
||||
Use a CI/CD solution to convert your Docker build (or other format) into a Zero-Image format. The 3Bot will do this on behalf of the user in the future.
|
||||
|
||||
4. **Define the Workload**
|
||||
|
||||
3. **Define the Workload**
|
||||
Specify all the details of your workload, including network bridges, web gateways, required machines, and more.
|
||||
|
||||
4. **Register and Sign**
|
||||
5. **Register and Sign**
|
||||
|
||||
Register the workload and sign it with your private key.
|
||||
|
||||
5. **Automatic Detection**
|
||||
6. **Automatic Detection**
|
||||
All necessary Zero-OS nodes (our infrastructure) will detect that a new workload needs to be deployed.
|
||||
|
||||
6. **Deployment Process**
|
||||
7. **Deployment Process**
|
||||
The nodes will pull down the formal workload descriptions and initiate the deployment process.
|
||||
|
||||
7. **Validation**
|
||||
8. **Validation**
|
||||
Every step of the deployment is verified by Zero-OS (ZOS) to ensure that the intended result is accurately replicated. If any discrepancies are detected, ZOS will halt the deployment and provide an error message.
|
||||
|
||||
### Benefits
|
||||
@@ -40,3 +46,5 @@ The concept of Zero-Deploy is a key component of the **Smart Contract for IT** f
|
||||
- **Deterministic Deployment**: There is no dynamic behavior during deployment at runtime, ensuring a consistent and predictable outcome.
|
||||
- **Strict Compliance**: No process can start unless all files and configurations are fully described at the flist level.
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -1,11 +1,68 @@
|
||||
---
|
||||
title: 'ZOS - geo-aware OS'
|
||||
sidebar_position: 1
|
||||
description: The computer layer of the grid
|
||||
description: The computer layer
|
||||
hide_title: true
|
||||
---
|
||||
|
||||
# Compute Layer
|
||||
|
||||
| | Compute Layer | Default |
|
||||
|
||||
|
||||
# ZOS - geo-aware 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.
|
||||
|
||||
|
||||
### Imagine An Operating System With The Following Benefits
|
||||
|
||||
- Up to 10x more efficient for certain workloads (e.g. storage)
|
||||
- No install required
|
||||
- All files are deduped for the VM's, containers and the ZOS itself, no more data duplicated filesystems
|
||||
- The hacking footprint is very small which leads to much safer systems
|
||||
- Every file is fingerprinted and gets checked at launch time of an application
|
||||
- There is no shell or server interface on the operating system
|
||||
- The networks are end2end encrypted between all Nodes
|
||||
- It is possible to completely disconnect the compute/storage from the network service part which means hackers have a lot less chance to access the data
|
||||
- A smart contract for the IT layer allows groups of people to deploy IT workloads with consensus and full control
|
||||
- All workloads which can run on linux can run on Zero-OS but in a much more controlled, private and safe way
|
||||
|
||||
> We have created an operating system from scratch. We used the Linux kernel and its components and then built further on it. We have been able to achieve all of the above benefits.
|
||||
|
||||
## Requirements:
|
||||
|
||||
- **Autonomy**: TF Grid needs to create compute, storage and networking capacity everywhere. We could not rely on a remote (or a local) maintenance of the operating system by owners or operating system administrators.
|
||||
- **Simplicity**: An operating system should be simple, able to exist anywhere for anyone, and be good for the planet.
|
||||
- **Stateless**: In a grid (peer-to-peer) set up, the sum of the components provides a stable basis for single elements to fail and not bring the whole system down. Therefore, it is necessary for single elements to be stateless, and the state needs to be stored within the grid.
|
||||
|
||||
|
||||
|
||||
## 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**
|
||||
|
||||
Default features:
|
||||
|
||||
- Compatible with Docker
|
||||
- Compatible with any VM (Virtual Machine)
|
||||
- Compatible with any Linux workload
|
||||
- Integrated unique storage & network primitives
|
||||
- Integrated smart contract for IT layer
|
||||
|
||||
## benefits
|
||||
|
||||
- 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 (Mycelium)
|
||||
- The containers can use a web gateway to allow internet users to connect to the applications which are running in their secure containers
|
||||
- Can use core-x to manage the workload
|
||||
|
||||
|
||||
|
||||
| | Zos Compute Layer Benefits | 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 |
|
||||
@@ -15,50 +72,14 @@ description: The computer layer of the grid
|
||||
| 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 |
|
||||
| Sovereign | Yes | Mostly not. |
|
||||
| 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
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -0,0 +1,35 @@
|
||||
---
|
||||
title: 'Smart Contract for IT'
|
||||
sidebar_position: 3
|
||||
description: 'How smart contract tech can be used to deploy IT workloads.'
|
||||
hide_title: true
|
||||
---
|
||||
|
||||
|
||||
## Deployment of Workloads Using Secure Smart IT Contracts
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Workloads can be deployed through a secure and decentralized system enabled by **smart IT contracts**.
|
||||
|
||||
|
||||
These contracts ensure the following:
|
||||
|
||||
1. **Multi-Signature Authorization**
|
||||
Before a workload is deployed, multiple authorized individuals must sign off on the deployment contract. This ensures a consensus-driven process, adding a layer of security and accountability. No single individual has unilateral control over the process.
|
||||
|
||||
2. **Immutable and Autonomous Deployment**
|
||||
Once the deployment is signed and approved, the workload is executed as defined in the smart IT contract. The system ensures that:
|
||||
- No party, including the signers, can alter the deployed workload or access the stored data.
|
||||
- The deployment process is verified, authenticated, and recorded immutably on the blockchain, guaranteeing transparency and trust.
|
||||
|
||||
3. **Managed by Virtual Administrators (3BOTs)**
|
||||
The workloads can optionally be autonomously managed by virtual administrators, known as **3BOTs**. These bots operate as trustworthy system administrators and ensure the deployed solution adheres strictly to the agreed-upon parameters.
|
||||
|
||||
4. **Registered on a Decentralized Geo-Aware Ledger**
|
||||
Once the contract is finalized and deployment occurs, the details are permanently registered in the **TFChain blockchain**, providing an immutable record of the transaction. This further enhances security and transparency.
|
||||
|
||||
By leveraging these mechanisms, the system ensures that IT workloads are deployed securely, remain tamper-proof, and operate in a decentralized, autonomous manner. This approach eliminates risks of unauthorized changes and protects the integrity of deployed solutions.
|
||||
BIN
docs/key_innovations_overview/network_inno/img/how_network.png
Normal file
BIN
docs/key_innovations_overview/network_inno/img/how_network.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 116 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 106 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 260 KiB |
@@ -5,6 +5,16 @@ sidebar_position: 2
|
||||
|
||||
|
||||
|
||||
# Mycelium: Our Planetary Network
|
||||
|
||||
|
||||
|
||||
The planetary network called Mycelium is an overlay network which lives on top of the existing Internet or other peer-to-peer networks created.
|
||||
|
||||
In the Mycelium network, everyone is connected to everyone. End-to-end encryption between users of an app and the app runs behind the network wall.
|
||||
|
||||
!!wiki.include page:'tech:mycelium0.md'
|
||||
|
||||
## Mycelium: A New Network Layer for the Internet
|
||||
|
||||
|
||||
|
||||
@@ -1,76 +0,0 @@
|
||||
---
|
||||
title: Virtual Browser
|
||||
sidebar_position: 5
|
||||
---
|
||||
|
||||
|
||||
|
||||
## Secure Remote Browser Concept
|
||||
|
||||
### Overview
|
||||
|
||||
In this concept, users interact with a secure web application through their web browsers without running JavaScript locally.
|
||||
|
||||
Instead, the actual browser logic and JavaScript execution occur in a secure, remote virtual browser hosted in a secure part of a private cloud. This setup provides enhanced security and control, ensuring that users are protected from malicious scripts and other threats.
|
||||
|
||||
### Key Components
|
||||
|
||||
1. **Client-Side Browser (Local Browser)**
|
||||
- **Rendering Only**: The user's local browser is responsible only for rendering content. It draws the user interface using technologies like HTML5 Canvas.
|
||||
- **No Local JavaScript Execution**: No JavaScript code runs on the local browser, eliminating the risk of client-side script attacks.
|
||||
|
||||
2. **Remote Browser (Virtual Browser)**
|
||||
- **Secure Execution Environment**: The remote browser runs within a secure container in the cloud. For example, this could be within the secure network of a bank.
|
||||
- **JavaScript Execution**: All JavaScript execution happens in the remote browser. This environment is tightly controlled and monitored.
|
||||
- **Context Validation**: Each JavaScript file executed is checked to ensure it originates from the original, built application. This prevents unauthorized or malicious scripts from running.
|
||||
|
||||
3. **Session Management**
|
||||
- **Ephemeral Sessions**: Each user session is temporary. After a session ends, the context is destroyed and rebuilt for the next session, ensuring a clean state each time.
|
||||
- **Session Recording**: Sessions can be recorded, similar to screen CCTV, for auditing and security purposes. This allows for detailed monitoring and review if needed.
|
||||
|
||||
4. **Network Service Lists and Mycelium Integration**
|
||||
- **Secure Communication**: The connection between the local browser and the remote browser uses end-to-end encryption. The Mycelium overlay network ensures the shortest path and secure, peer-to-peer communication.
|
||||
- **Access Control**: Network service lists and group-based access control manage which users can access specific applications, enhancing security and control.
|
||||
|
||||
### Example Workflow
|
||||
|
||||
1. **User Initiates Connection**
|
||||
- The user opens their local browser and navigates to the bank's application URL.
|
||||
- The local browser connects to the remote browser hosted in the bank's secure cloud environment.
|
||||
|
||||
2. **Remote Browser Setup**
|
||||
- A new, secure container is instantiated for the user's session.
|
||||
- The remote browser loads the bank's application and validates all JavaScript files.
|
||||
|
||||
3. **Rendering in Local Browser**
|
||||
- The remote browser executes the JavaScript and sends the rendered output to the local browser.
|
||||
- The local browser draws this output on the canvas, providing a seamless user experience.
|
||||
|
||||
4. **Session Management**
|
||||
- Throughout the session, all interactions are processed by the remote browser.
|
||||
- User interactions (e.g., clicks, form submissions) are sent to the remote browser, which processes them and updates the rendered output accordingly.
|
||||
|
||||
5. **Session Termination**
|
||||
- When the user finishes their session, the remote browser context is destroyed.
|
||||
- Any recorded session data is stored securely for auditing purposes.
|
||||
|
||||
### Benefits
|
||||
|
||||
1. **Enhanced Security**
|
||||
- By not running JavaScript locally, the risk of client-side attacks such as cross-site scripting (XSS) is eliminated.
|
||||
- The remote browser's secure environment ensures that only validated scripts execute.
|
||||
|
||||
2. **Controlled Environment**
|
||||
- The bank has full control over the execution environment, allowing for stringent security policies and monitoring.
|
||||
- Ephemeral sessions ensure that each user starts with a clean slate, reducing the risk of persistent threats.
|
||||
|
||||
3. **Auditing and Compliance**
|
||||
- Session recording provides a detailed audit trail, which is valuable for security reviews and compliance with regulatory requirements.
|
||||
|
||||
4. **Improved User Experience**
|
||||
- Users benefit from a secure browsing experience without performance degradation, as rendering is offloaded to the client's local browser.
|
||||
|
||||
### Integration with Mycelium and Network Service Lists
|
||||
By combining this remote browser concept with Mycelium and network service lists, we can ensure secure and efficient communication:
|
||||
- **Mycelium Overlay Network**: Ensures that the connection between the local and remote browser is routed through the most efficient path, leveraging peer-to-peer connections where possible.
|
||||
- **Network Service Lists**: Manage which users and groups can access the remote browser and specific applications, providing fine-grained access control.
|
||||
@@ -3,7 +3,7 @@ title: FungiStor
|
||||
sidebar_position: 4
|
||||
---
|
||||
|
||||
## FungiStor (End 2024)
|
||||
## FungiStor (H2 2025)
|
||||
|
||||
### The Problem
|
||||
|
||||
|
||||
BIN
docs/key_innovations_overview/storage_inno/img/how_data.png
Normal file
BIN
docs/key_innovations_overview/storage_inno/img/how_data.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 104 KiB |
BIN
docs/key_innovations_overview/storage_inno/img/storage_old.png
Normal file
BIN
docs/key_innovations_overview/storage_inno/img/storage_old.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 140 KiB |
BIN
docs/key_innovations_overview/storage_inno/img/unbreakable2.png
Normal file
BIN
docs/key_innovations_overview/storage_inno/img/unbreakable2.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 271 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 569 KiB |
@@ -4,7 +4,7 @@ sidebar_position: 3
|
||||
---
|
||||
|
||||
|
||||
## Zero-Stor : A Quantum Safe Backend Storage System
|
||||
## Zero-Stor : An Unbreakable Backend Storage System
|
||||
|
||||
Zeros-Stor is a quantum safe backend storage system that use efficient algorithms to ensure maximal use of storage.
|
||||
|
||||
|
||||
@@ -1,7 +0,0 @@
|
||||
{
|
||||
"label": "Roadmap",
|
||||
"position": 6,
|
||||
"link": {
|
||||
"type": "generated-index",
|
||||
}
|
||||
}
|
||||
@@ -1,53 +0,0 @@
|
||||
---
|
||||
title: Enterprise Roadmap
|
||||
sidebar_position: 2
|
||||
---
|
||||
|
||||
|
||||
# Government, Commercial hosters, Telco and Enterprise Roadmap
|
||||
|
||||
We are working on our Government, Commercial hosters, Telco and Enterprise Release of our Technology.
|
||||
|
||||
> 90% of the work has been done as part of our base offering but we need additional features for enterprise
|
||||
|
||||
## Enterprise User Interface
|
||||
|
||||
The current user interface is designed for an open-source tech audience. For enterprise use, we need a different approach to meet the unique needs of enterprise environments:
|
||||
|
||||
- **Private or Hybrid Context**: All operations should be conducted within a private or hybrid cloud context to ensure security and compliance.
|
||||
- **Enhanced Monitoring**: We need more comprehensive monitoring dashboard screens to provide real-time insights and analytics.
|
||||
- **Identity Management Integration**: Integration with enterprise-grade Identity Management solutions, such as LDAP, Active Directory, and SSO (Single Sign-On), is essential.
|
||||
- **Enterprise-Friendly UI**: The user interface needs to be redesigned to be more intuitive and tailored to enterprise users, focusing on usability and efficiency.
|
||||
- **Token Irrelevance**: Tokens are not a priority in this context and should be de-emphasized in the solution.
|
||||
|
||||
## Windows Support
|
||||
|
||||
The virtual Machine technology we use does support windows, but we need to do some further integration.
|
||||
|
||||
## High Performance Network Integration
|
||||
|
||||
- **Local Network Integration**: Zero-OS is designed to support a wide range of technologies, though additional integration work is required to optimize performance.
|
||||
- **High-Speed Backbones**: We aim to support high-speed Ethernet and RDMA (Infiniband) based backbones.
|
||||
- **Instrumentation Enhancements**: Additional instrumentation needs to be incorporated into Zero-OS to achieve optimal performance.
|
||||
- **Target Performance**: Our goal is to achieve network speeds exceeding 100 Gbps.
|
||||
- **Custom Integration**: We offer integration with selected network equipment from our customers, accommodating custom integration requirements.
|
||||
|
||||
## High Performance Storage Block Device Integration
|
||||
|
||||
Next to the existing already integrated storage backends we want to support a high performance redundant storage block device.
|
||||
|
||||
- High performance redundant storage network
|
||||
- Supports our high speed backbone as defined above
|
||||
- Scalable to thousands of machines per cluster.
|
||||
- Replication capability between zones.
|
||||
- **Custom Integration**: We offer integration with selected storage equipment from our customers, accommodating custom integration requirements.
|
||||
|
||||
## Service Level Management
|
||||
|
||||
- The system will have hooks and visualization for achievement of Service levels.
|
||||
- This will allow a commercial service provider to get to higher revenue and better uptime management.
|
||||
|
||||
## Support for Liquid Cooling tanks
|
||||
|
||||
- Do a test setup in liquid cooling rack or node, we can use our selfhealing capabilities to manage better.
|
||||
- Is Integration effort, not really code changes
|
||||
@@ -1,28 +0,0 @@
|
||||
---
|
||||
title: Hero Roadmap
|
||||
sidebar_position: 4
|
||||
---
|
||||
|
||||
|
||||
## Hero (3Bot) High Level Roadmap
|
||||
|
||||
The first version of our Hero enables the management of core services such as an innovative database backend, a sovereign git system, and the automatic integration and deployment of our workloads.
|
||||
|
||||
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 | Q4 24 |
|
||||
| Hero CI = Continuous Integration | Easier to use Continuous Integration / Development, very powerfull, with multi node support | Q4 24 |
|
||||
| Hero Play | Integrate declarative automation and configuration management as part of wiki approach in hero Publisher | Q4 24 |
|
||||
| Hero Git | Alternative to centralized Github (based on Gitea), fully integrated on top of TFGrid | Q4 24 |
|
||||
| Hero DB | Flexible ultra redundant database stor with indexing, queries, stored procesudes, super scalable replication | Q4 24 |
|
||||
| Hero OSIS | Object Storage and Index system integrates with hero Git, all data on git based backend | Q4 24 |
|
||||
| Hero WEB | Web framework (with co-routines) using Vlang, deployable globally on TFGrid, integrated with Mycelium Net and Names. | Q4 24 |
|
||||
| Hero Monitor | Monitor all your different components on redundant monitoring stack | Q4 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.
|
||||
@@ -1,43 +0,0 @@
|
||||
---
|
||||
title: Roadmap in Phases
|
||||
sidebar_position: 1
|
||||
---
|
||||
|
||||
|
||||
|
||||
|
||||
# Roadmap in Phases
|
||||
|
||||
## phase 1: wave 1 of companies, leading to our expertise
|
||||
|
||||
- technology creation, was result of 20 years of evolution
|
||||
- 7 startups acquired as part of this process
|
||||
- technology used globally by big vendors
|
||||
- +600m USD Exits
|
||||
|
||||
## phase 2: proof of tech
|
||||
|
||||
- Technology launched globally (as opensource)
|
||||
- +60,000,000 vcpu active
|
||||
- Large scale proof of core technology
|
||||
- Focus on early adoptors in tech space (cloud, web 2/3 ...)
|
||||
- 50m USD funded by founders, community and farmers (people providing capacity)
|
||||
|
||||
## phase 3: commercialization & global expansion
|
||||
|
||||
### phase 3.1: Commercial Partners
|
||||
|
||||
- ThreeFold Launches with Commercial Strategic Partners
|
||||
- Telco Operatators
|
||||
- IT Integrators
|
||||
- Enterprise Roadmap delivered < 6 months (is mainly integration, documentation and UI work)
|
||||
- Together with partners we deliver on the many projects which are in our funnel today e.g. East Africa, Brazil
|
||||
|
||||
### phase 3.2: Large Scale Financancing for Infrastructure
|
||||
|
||||
**Large scaling financing round**
|
||||
|
||||
- financing for infrastructure projects (trillions available right now for infra in emerging countries)
|
||||
- Public STO (security token offering), let world co-own the infra for their Internet
|
||||
- large partnerships drive alternative to Tier 3/4 Datacenters
|
||||
|
||||
@@ -1,61 +0,0 @@
|
||||
---
|
||||
title: Open-Source TFGrid Roadmap
|
||||
sidebar_position: 3
|
||||
---
|
||||
|
||||
|
||||
## TFGrid 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.
|
||||
|
||||
Below you can find some of the planned features of TFGrid 4.0 mainly to achieve ability to scale to hundred of thousand of nodes.
|
||||
|
||||
| | Roadmap | Timing |
|
||||
| ----------------------------------- | ---------------------------------------------------------------- | ------ |
|
||||
| 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 Hero CI/CD) | Q4 24 |
|
||||
| Zero-Images Hub | CI/CD integration (See Hero CI/CD) 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 |
|
||||
Reference in New Issue
Block a user