Merge pull request 'development to main periodic update' (#122) from development into main
Reviewed-on: #122
This commit is contained in:
commit
06039ac195
@ -1,12 +1,48 @@
|
||||
|
||||
- [Introduction](projectinca/intro.md)
|
||||
- [The Plan](projectinca/theplan_c.md)
|
||||
- [The Plan](projectinca/theplan_a.md)
|
||||
- [**Requirements**](projectinca/requirements.md)
|
||||
- [Tokens](projectinca/inca1.md)
|
||||
- [Funding](projectinca/funding.md)
|
||||
- [P2P Promotion](projectinca/peer2peer_promotion.md)
|
||||
- [Liquidity](projectinca/liquidity.md)
|
||||
- [INCA Tokenomics](projectinca/tokens.md)
|
||||
- [INCA](projectinca/inca.md)
|
||||
- [TFT](projectinca/tft.md)
|
||||
- [Governance](projectinca/governance.md)
|
||||
- [Collaboration](projectinca/collab.md)
|
||||
- [Principles](projectinca/collaboration.md)
|
||||
- [Messaging](tfgrid3/messaging.md)
|
||||
- [Teams](projectinca/teams.md)
|
||||
- [ThreeFold Collaboration](projectinca/tf_colab.md)
|
||||
- [Remuneration](projectinca/remuneration.md)
|
||||
- [My **Checklist**](projectinca/checklist.md)
|
||||
- [My **Links**](projectinca/links.md)
|
||||
- [Project Info](projectinca/project_info.md)
|
||||
- [About Us](tfgrid3/who_are_we.md)
|
||||
- [The Internet Today](tech/internet_today.md)
|
||||
- [History of Computers](tech/history/c64.md)
|
||||
- [Too Many Layers](tech/history/layers.md)
|
||||
- [Values](values/planet_people_first.md)
|
||||
- [Why TFGrid](why/why.md)
|
||||
- [Cloud Too Centralized](why/current_cloud_too_centralized.md)
|
||||
- [Countries Don't Have Their Internet](why/countries_no_internet.md)
|
||||
- [Human Right](why/internet_human_right.md)
|
||||
- [Social Warming](why/social_warming.md)
|
||||
- [**Technology**](projectinca/technology.md)
|
||||
- [INCA Tokenomics](projectinca/tokens1.md)
|
||||
- [INCA Marketplace](projectinca/marketplace.md)
|
||||
- [Pricing](projectinca/marketplace_pricing.md)
|
||||
- [AI Slices](tfgrid4/aislice.md)
|
||||
- [Cloud Slices](tfgrid4/cloudslice.md)
|
||||
- [Storage Slices](tfgrid4/storageslice.md)
|
||||
- [INCA Farming](projectinca/inca_farming.md)
|
||||
- [INCA Nodes](projectinca/inca_nodes.md)
|
||||
- [INCA Node Silver](projectinca/inca_node_silver.md)
|
||||
- [INCA Node Platinum](projectinca/inca_node_platinum.md)
|
||||
- [INCA Node AI](projectinca/inca_node_ai.md)
|
||||
- [INCA Routers](projectinca/inca_routers.md)
|
||||
- [INCA Network Map](projectinca/networkmap.md)
|
||||
- [Reward Simulation](projectinca/inca_farming_reward.md)
|
||||
- [INCA Stories](projectinca/stories.md)
|
||||
- [INCA App Spec](projectinca/inca1pp.md)
|
||||
- [INCA Grants](projectinca/grants.md)
|
||||
- [v3.x Grants](projectinca/grants_tft.md)
|
||||
- [Deploy AISlices](projectinca/grant_aislice.md)
|
||||
@ -22,76 +58,22 @@
|
||||
- [Establish Thorchain DEX](projectinca/grant_thorchain.md)
|
||||
- [v4.x Grants](projectinca/grants_inca.md)
|
||||
- [Grant Voting Process](projectinca/grant_voting_process.md)
|
||||
- [INCA Marketplace](projectinca/marketplace.md)
|
||||
- [Pricing](projectinca/marketplace_pricing.md)
|
||||
- [AI Slices](tfgrid4/aislice.md)
|
||||
- [Cloud Slices](tfgrid4/cloudslice.md)
|
||||
- [Storage Slices](tfgrid4/storageslice.md)
|
||||
- [INCA Farming](projectinca/inca_farming.md)
|
||||
- [INCA Nodes](projectinca/inca_nodes.md)
|
||||
- [INCA Node Silver](projectinca/inca_node_silver.md)
|
||||
- [INCA Node Platinum](projectinca/inca_node_platinum.md)
|
||||
- [INCA Node AI](projectinca/inca_node_ai.md)
|
||||
- [INCA Routers](projectinca/inca_routers.md)
|
||||
- [INCA Network Map](projectinca/networkmap.md)
|
||||
- [Reward Simulation](projectinca/inca_farming_reward.md)
|
||||
- [INCA Launch Collaboration](projectinca/collab.md)
|
||||
- [Remuneration](projectinca/remuneration.md)
|
||||
- [Promotion Effort](tfgrid3/promotion.md)
|
||||
- [Messaging](tfgrid3/messaging.md)
|
||||
- [Teams](projectinca/teams.md)
|
||||
- [INCA Stories](projectinca/stories.md)
|
||||
- [INCA App Spec](projectinca/inca_app.md)
|
||||
- [INCA Grid Utilization](partners_utilization/partners.md)
|
||||
- [Holochain](partners_utilization/holochain.md)
|
||||
- [Hero - Project Mycelium](projectinca/hero.md)
|
||||
- [Digital Freezone](partners_utilization/freezone.md)
|
||||
- [Tanzania Internet](partners_utilization/tanzania.md)
|
||||
- [Elestio](partners_utilization/elestio.md)
|
||||
- [Earth Wallet](partners_utilization/earth_wallet.md)
|
||||
- [Holochain](partners_utilization/holochain.md)
|
||||
- [Helium](partners_utilization/helium.md)
|
||||
- [Sikana](partners_utilization/sikana.md)
|
||||
- [Vindo](partners_utilization/vindo.md)
|
||||
- [Vverse](partners_utilization/vverse.md)
|
||||
- [Tier S Datacenter](partners_utilization/tier_s_datacenter.md)
|
||||
- [Engineering](projectinca/engineering.md)
|
||||
- [INCA Grid 4.0](projectinca/tfgrid4.md)
|
||||
- [Project Info](projectinca/project_info.md)
|
||||
- [About Us](tfgrid3/who_are_we.md)
|
||||
- [The Internet Today](tech/internet_today.md)
|
||||
- [History of Computers](tech/history/c64.md)
|
||||
- [Too Many Layers](tech/history/layers.md)
|
||||
- [Values](values/planet_people_first.md)
|
||||
- [Tech Key Innovations](tech/key_innovations_overview.md)
|
||||
- [Mycelium Network](tech/mycelium_innovation.md)
|
||||
- [Zero-OS](tech/zos_innovation.md)
|
||||
- [Quantum Safe Storage](tech/zstor_innovation.md)
|
||||
- [Quantum Safe Filesystem](tech/qsfs_innovation.md)
|
||||
- [Flist: Better OS Images](tech/flist_innovation.md)
|
||||
- [FungiStor](tech/fungistor_innovation.md)
|
||||
- [Network Wall](tech/network_wall_innovation.md)
|
||||
- [Technology](tech/technology.md)
|
||||
- [Architecture](tech/architecture.md)
|
||||
- [Energy Efficient](tech/energy_efficient.md)
|
||||
- [Why TFGrid](why/why.md)
|
||||
- [Cloud Too Centralized](why/current_cloud_too_centralized.md)
|
||||
- [Countries Don't Have Their Internet](why/countries_no_internet.md)
|
||||
- [Human Right](why/internet_human_right.md)
|
||||
- [Social Warming](why/social_warming.md)
|
||||
- [INCA Cloud Core Capabilities](tech/features.md)
|
||||
- [Compute](tech/compute.md)
|
||||
- [Zero-OS](tech/zos.md)
|
||||
- [Infrastructure As Code](tech/smartcontract_iac.md)
|
||||
- [CoreX](tech/corex.md)
|
||||
- [Storage](tech/qsss_home.md)
|
||||
- [Quantum Safe Storage Algo](tech/qss_algorithm.md)
|
||||
- [Zero Knowledge proof](tech/qss_zero_knowledge_proof.md)
|
||||
- [NFT Storage](tech/nft_storage.md)
|
||||
- [S3 Storage](tech/s3_interface)
|
||||
- [File System](tech/qss_filesystem.md)
|
||||
- [Network](tech/networking.md)
|
||||
- [Mycelium](tech/mycelium.md)
|
||||
- [Web Gateway](tech/webgw.md)
|
||||
- [Plan B](projectinca/theplan_b.md)
|
||||
- [INCA Plan B](projectinca/tokens0.md)
|
||||
- [TFT](projectinca/tft0.md)
|
||||
- [Appendix](projectinca/appendix.md)
|
||||
- [Tokenomics TFGrid 3.14](tfgrid3/tokenomics.md)
|
||||
- [Farming Reward TFGrid 3](tfgrid3/farming_reward.md)
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
- [Table of Contents](system_administrators/system_administrators_book_toc.md)
|
||||
- [Introduction](system_administrators/system_administrators_book.md)
|
||||
- [Getting Started](system_administrators/getstarted/tfgrid3_getstarted.md)
|
||||
- [SSH Remote Connection](system_administrators/getstarted/ssh_guide/ssh_guide.md)
|
||||
- [SSH with OpenSSH](system_administrators/getstarted/ssh_guide/ssh_openssh.md)
|
||||
@ -1,5 +1,5 @@
|
||||
#!/bin/bash
|
||||
set -ex
|
||||
export NAME=system_administrators
|
||||
export NAME=sysadmins
|
||||
hero mdbook -u https://git.ourworld.tf/tfgrid/info_tfgrid/src/branch/manual/heroscript/$NAME
|
||||
rsync -rv ~/hero/www/info/$NAME/ root@info.ourworld.tf:/root/hero/www/info/$NAME/
|
||||
@ -1,20 +1,30 @@
|
||||
- [Introduction](tech/technology.md)
|
||||
- [Overview](tech/overview.md)
|
||||
- [The Internet Today](tech/internet_today.md)
|
||||
- [History of Computers](tech/history/c64.md)
|
||||
- [Too Many Layers](tech/history/layers.md)
|
||||
- [The Internet Re-invented](tech/how_does_it_work.md)
|
||||
- [World Records](tech/world_records.md)
|
||||
- [Architecture](tech/architecture.md)
|
||||
- [Key Innovations](tech/key_innovations_overview.md)
|
||||
- [Mycelium Network](tech/mycelium_innovation.md)
|
||||
- [Compute](tech/compute_inno.md)
|
||||
- [Zero-OS](tech/zos_innovation.md)
|
||||
- [Zero-Images](tech/flist_innovation.md)
|
||||
- [Network](tech/network_inno.md)
|
||||
- [Mycelium](tech/mycelium_innovation.md)
|
||||
- [Network Wall](tech/network_wall_innovation.md)
|
||||
- [Storage](tech/storage_inno.md)
|
||||
- [Quantum Safe Storage](tech/zstor_innovation.md)
|
||||
- [Quantum Safe Filesystem](tech/qsfs_innovation.md)
|
||||
- [FList: Better OS Images](tech/flist_innovation.md)
|
||||
- [FungiStor](tech/fungistor_innovation.md)
|
||||
- [Network Wall](tech/network_wall_innovation.md)
|
||||
- [Architecture](tech/architecture.md)
|
||||
- [Energy Efficient](tech/energy_efficient.md)
|
||||
- [Decentralized Cloud Core Capabilities](tech/features.md)
|
||||
- [Status/Roadmap](tech/tfgrid_roadmap.md)
|
||||
- [Hero Roadmap](tech/hero_roadmap.md)
|
||||
- [ThreeFold Core Components](tech/features.md)
|
||||
- [Compute](tech/compute.md)
|
||||
- [Zero-OS](tech/zero_os.md)
|
||||
- [Zero-Chance](tech/zero_chance.md)
|
||||
- [Zero-Install](tech/zero_install.md)
|
||||
- [Zero-Boot](tech/zero_boot.md)
|
||||
- [Storage](tech/qsss_home.md)
|
||||
- [Quantum Safe Storage Algo](tech/qss_algorithm.md)
|
||||
- [Zero Knowledge proof](tech/qss_zero_knowledge_proof.md)
|
||||
@ -24,15 +34,16 @@
|
||||
- [Network](tech/networking.md)
|
||||
- [Mycelium](tech/mycelium.md)
|
||||
- [Web Gateway](tech/webgw.md)
|
||||
- [Partners Utilization](partners_utilization/partners.md)
|
||||
- [Partners / Utilization](partners_utilization/partners.md)
|
||||
- [Sikana](partners_utilization/sikana.md)
|
||||
- [Vindo](partners_utilization/vindo.md)
|
||||
- [Mkondo](partners_utilization/mkondo.md)
|
||||
- [Vverse](partners_utilization/vverse.md)
|
||||
- [Earth Wallet](partners_utilization/earth_wallet.md)
|
||||
- [Elestio](partners_utilization/elestio.md)
|
||||
- [OW Freezone](partners_utilization/freezone.md)
|
||||
- [Helium](partners_utilization/helium.md)
|
||||
- [Holochain](partners_utilization/holochain.md)
|
||||
- [TZG](partners_utilization/tanzania.md)
|
||||
- [Tier-S DC](partners_utilization/tier_s_datacenter.md)
|
||||
- [OW Freezone](partners_utilization/freezone.md)
|
||||
- [Earth Wallet](partners_utilization/earth_wallet.md)
|
||||
- [Helium](partners_utilization/helium.md)
|
||||
|
||||
<!-- - [Elestio](partners_utilization/elestio.md) -->
|
||||
|
||||
@ -6,5 +6,7 @@
|
||||
|
||||
Above is not a movie or photo, we can stream 100% photorealistic real time rendered environments to our customers.
|
||||
|
||||
Check out the result on http://metaversestreaming.threefold.me , please note this is not a video of a real place, this is a rendered result of streaming a virtual reality session to the user.
|
||||
<div style="padding:56.6% 0 0 0;position:relative;"><iframe src="https://player.vimeo.com/video/888463280?badge=0&autopause=0&player_id=0&app_id=58479" frameborder="0" allow="autoplay; fullscreen; picture-in-picture; clipboard-write" style="position:absolute;top:0;left:0;width:100%;height:100%;" title="pixelstreaming"></iframe></div><script src="https://player.vimeo.com/api/player.js"></script>
|
||||
|
||||
Check out the result on [this link](https://vimeo.com/888463280) , please note this is not a video of a real place, this is a rendered result of streaming a virtual reality session to the user.
|
||||
|
||||
|
||||
@ -8,7 +8,6 @@ The following partners all have the potential to utilize a lot of our capacity a
|
||||
- [Earth Wallet](earth_wallet.md) alternative to BTC Lightening (cheap transactions, scale)
|
||||
- [Digital Freezone](freezone.md) a digital freezone made for hundreds of millions of people.
|
||||
- [Tanzania Sovereign Internet](tanzania.md) a sovereign Internet for a country
|
||||
- [Elestio](elestio.md) +300 opensource apps on top of TFGrid (managed, supported)
|
||||
- [Mkondo](mkondo.md) most realistic rendering of VR/AR env on top of TFGrid
|
||||
- [Vindo](vindo.md) collaborative metaverse, best quality at low bandwidth
|
||||
- [Vverse](vverse.md) virtual reality museum
|
||||
|
||||
20
collections/projectinca/checklist.md
Normal file
20
collections/projectinca/checklist.md
Normal file
@ -0,0 +1,20 @@
|
||||
|
||||
|
||||
# Checklist
|
||||
|
||||
Its important that every contributor to this project has gone over next checklist.
|
||||
|
||||
- [ ] I have read [The Collaboration Doc](collaboration.md) and browsed to the underlying info.
|
||||
- I am committed to work this way and understand why.
|
||||
- [ ] I have basic understand of [The Tech](technology.md), and did some effort understanding the basics.
|
||||
- [ ] Not all has been finalized yet, quite some further ideas to be finalized.
|
||||
- I will give my feedback to relevant stakeholders.
|
||||
- [ ] I have read the [**Requirements**](projectinca/requirements.md) and agree
|
||||
|
||||
## For go2market contributors
|
||||
|
||||
Everyone dealing with product management, tokens, marketing or any other go2market activity.
|
||||
|
||||
- [ ] [I have an account on gitea](https://git.ourworld.tf)
|
||||
- If not contact Mik or Sabrina
|
||||
- [ ] [I am committed to work with our Kanban on Gitea](https://git.ourworld.tf/tfgrid/circle_go2market/projects/80)
|
||||
@ -1,5 +1,11 @@
|
||||
# Teams
|
||||
|
||||
> TODO: complete
|
||||
|
||||
|
||||
## Core Team
|
||||
|
||||
> todo:
|
||||
|
||||
## Direct Promotion: PP2P teams
|
||||
|
||||
|
||||
@ -2,6 +2,8 @@
|
||||
|
||||
Below you can find the grants as are open and being executed on for the 3.x version of our project.
|
||||
|
||||
> It is possible that these grants will move to our Project INCA and be unified as one set of grants.
|
||||
|
||||
```echarts
|
||||
option = {
|
||||
title: {
|
||||
|
||||
@ -6,7 +6,7 @@
|
||||
|
||||
The project will launch our **HERO**, a super efficient digital companion.
|
||||
|
||||
This project will do a new token and token sell, private and public. This project has the potential to fund a lot of the further ThreeFold Grid expansion (version 4). This project uses TFGrid 4.0 as the main cloud for its decentralization.
|
||||
This project will probably do a new token and token sell, private and public. This project has the potential to fund a lot of the further ThreeFold Grid expansion (version 4). This project uses TFGrid 4.0 as the main cloud for its decentralization.
|
||||
|
||||
**The first Digital Backbone in the world compatible with Web2, Web3 and AI.**:
|
||||
|
||||
|
||||
BIN
collections/projectinca/img/tech.png
Normal file
BIN
collections/projectinca/img/tech.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 384 KiB |
@ -1,30 +1,12 @@
|
||||
|
||||
# Compute is currency of future
|
||||
|
||||
|
||||
|
||||
|
||||
## ThreeFold DePIN Launch: Project INCA
|
||||
|
||||
Welcome to the Project INCA by ThreeFold.
|
||||
|
||||
With the project INCA, we want to create a decentralized future for ThreeFold by means of a launch in the DePIN ecosystem on top of Solana.
|
||||
|
||||
*Please do note the name INCA will prob still change.*
|
||||
|
||||
## Contributing to DePIN community
|
||||
|
||||
The current marketcap of the project is under 40 million USD, while other DePIN projects have marketcaps of 1 billion USD and more.
|
||||
|
||||
We believe that ThreeFold is ready and has rock solid technology to offer to the DePIN space. We think that what ThreeFold has to offer is comptabile to this space and that we can work in parallel and under many if not all projects in the DePIN space.
|
||||
|
||||
ThreeFold now has the necessary support from a lot of parties. We are entering a new exciting phase: Project INCA.
|
||||
|
||||
!!wiki.include page:'intro0.md'
|
||||
|
||||
## Learn More
|
||||
|
||||
Read this ebook to learn more about the project and how you can participate to this phase.
|
||||
|
||||
>> Its all important we agree with the content in this ebook.
|
||||
|
||||
> CONFIDENTIAL INFORMATION
|
||||
|
||||
|
||||
|
||||
22
collections/projectinca/intro0.md
Normal file
22
collections/projectinca/intro0.md
Normal file
@ -0,0 +1,22 @@
|
||||
|
||||
# Compute is currency of future
|
||||
|
||||
|
||||
|
||||
|
||||
## ThreeFold DePIN Launch: Project INCA
|
||||
|
||||
Welcome to the Project INCA by ThreeFold.
|
||||
|
||||
With the project INCA, we want to create a decentralized future for ThreeFold by means of a launch in the DePIN ecosystem on top of Solana.
|
||||
|
||||
|
||||
## Contributing to DePIN community
|
||||
|
||||
The current marketcap of the project is under 40 million USD, while other DePIN projects have marketcaps of 1 billion USD and more.
|
||||
|
||||
We believe that ThreeFold is ready and has rock solid technology to offer to the DePIN space. We think that what ThreeFold has to offer is comptabile to this space and that we can work in parallel and under many if not all projects in the DePIN space.
|
||||
|
||||
ThreeFold now has the necessary support from a lot of parties. We are entering a new exciting phase: Project INCA.
|
||||
|
||||
|
||||
5
collections/projectinca/links.md
Normal file
5
collections/projectinca/links.md
Normal file
@ -0,0 +1,5 @@
|
||||
|
||||
|
||||
# Links
|
||||
|
||||
> TODO: make list of all important links e.g. Telegram, ...
|
||||
@ -1,5 +1,7 @@
|
||||
|
||||
|
||||
> TODO: to be discussed & completed
|
||||
|
||||
# Peer2Peer Promotion (P2PP)
|
||||
|
||||
We believe the rollout must be viral. Here's how to achieve this.
|
||||
@ -19,6 +21,8 @@ We expect the TF Scouts to do the following:
|
||||
|
||||
**Reward**:
|
||||
|
||||
> TODO: complete/discuss
|
||||
|
||||
- TF Connect Installed -> 500 INCA
|
||||
- Referral to other person -> 50 INCA (after installing the TFConnect)
|
||||
- Stories as executed by P2PP Team
|
||||
@ -29,7 +33,6 @@ We expect the TF Scouts to do the following:
|
||||
|
||||
## Technical Requirements
|
||||
|
||||
- New TFConnect
|
||||
- New backend for TFConnect (can be run by TF DMCC)
|
||||
- Referral system
|
||||
- New INCA App
|
||||
- Referral system in INCA App
|
||||
|
||||
|
||||
2
collections/projectinca/plan/advisors.md
Normal file
2
collections/projectinca/plan/advisors.md
Normal file
@ -0,0 +1,2 @@
|
||||
## Advisors
|
||||
|
||||
88
collections/projectinca/plan/collaboration.md
Normal file
88
collections/projectinca/plan/collaboration.md
Normal file
@ -0,0 +1,88 @@
|
||||
|
||||
|
||||
# Collaboration
|
||||
|
||||
We had the pleasure collaborating on the creation and succesful development for more than 10 high tech startups.
|
||||
|
||||
We realized that the way how we collaborate defines a big part of the outcome.
|
||||
|
||||
> A lot of this knowledge can be found on [https://threefold.info/cocreation](https://threefold.info/cocreation)/
|
||||
|
||||
Working together with the OurWorld / ThreeFold ecosystem means you agree and are committed to above as such its highly appreciated you take some time to go over the info.
|
||||
|
||||
## Summary lets choose the best of the 2 ways
|
||||
|
||||
There are 2 ways how to collaborate:
|
||||
|
||||
1. The typical pyramid system, where a boss manages (directs) a sub boss until the required results are achieved and any non compliance results in “fixing” the issue. This results in harsh cultures and not even that effective.
|
||||
2. A circular system with clear stakeholders, examples are scrum, … These are more agile methods and leave a lot of freedom but require a certain discipline. To let 2 work agreement on how to interface (tools, process reports, …) needs to be agreed upon between ALL stakeholders because it's more dynamic and more interconnected compared to 1.
|
||||
|
||||
Obviously we are not a believer of 1, this means certain discipline and agreement to following existing tooling is a must.
|
||||
|
||||
2 is a commitment though, often we see people wanting to combine the benefits of 1 into 2, that often doesn’t work e.g. “TRUST me, I know what I am doing, let me alone…” these are statements which can work in 1 not in 2.
|
||||
|
||||
In 2 we trust each other by design but we require transparency and ability to comment on the work we are doing.
|
||||
|
||||
|
||||
## Tools
|
||||
|
||||
TF has adopted a set of tools to work following “2”, these tools are maybe not something you are used to or comfortable with. But don’t panic, millions of people have been able to do this before you, \
|
||||
so I guess you can do the same (the system we use is the same as github but actually easier).
|
||||
|
||||
### Our tools
|
||||
|
||||
* We use Gitea for
|
||||
* Task management
|
||||
* Story Management
|
||||
* Websites
|
||||
* Specs, Code, …
|
||||
* E-Books, Wiki’s, Manuals
|
||||
* There is continuous integration & deployment.
|
||||
* Gitea is the basis for our own future vision of how to collaborate deploy on TFGrid see [https://threefold.info/tech/tech/roadmap.html](https://threefold.info/tech/tech/roadmap.html)
|
||||
* We use GDrive for all our other documents
|
||||
* All Info is in a GDrive folder dedicated for Project INCA
|
||||
* We use Telegram for internal communication
|
||||
* Also groups, you can have topics just like we do in Slack.
|
||||
* I am sorry but I don’t want our team to lose time by using yet another tool
|
||||
|
||||
### Not enough reporting
|
||||
|
||||
A common complaint is that gitea doesn’t give enough reporting, there is a plan to fix this
|
||||
|
||||
* A portal is being created to make it easy for all of us to collaborate, will be done in Summer
|
||||
* Company/Project Directory \
|
||||
(what are all projects our larger community is working on)
|
||||
* People Directory
|
||||
* Nice overview of Stories/Tasks/Milestones/… will get info from Gitea
|
||||
* Priority management: will warn user when we are getting behind on tasks, stories
|
||||
* Reward dashboard (tokens, shares, reward pool, …)
|
||||
* Information overview (what is most relevant info per project)
|
||||
* Contract overview (with security of course), includes our SAFE’s
|
||||
* Phase 2:
|
||||
* Internal chat/messaging \
|
||||
(might replace telegram for internal communication at one point in time)
|
||||
* Integrated sort of forum for discussions
|
||||
* Video Conferencing
|
||||
|
||||
|
||||
## We work in an agile way
|
||||
|
||||
As such we want everyone to understand and endorse that we are not a pyramid and are ok to work in a more Teal Based organization structure:
|
||||
|
||||
* No-one is the boss of a pyramid, we don’t do politics.
|
||||
* Instead we have coordinators and they make sure that stories, milestones are understood, these are on gitea, they make sure there are stakeholders and stakeholders do agree on the stories & milestones. (do note stories are high level and have nicely described deliverables and requirements).
|
||||
* All information worked at all times is transparent, and on the right location, no-one keeps it on their own drive not even to prepare, people are disciplined to make sure files no longer relevant go to _archive folder.
|
||||
* We avoid too many meetings, we make stories, we make specs, we review specs, we use git… to get to consensus and then the occasional stakeholder meeting is used to find consensus. We log (comments) on the stories. We make everything accountable.
|
||||
* We accept our wiki as a single source of truth even if it means learning how to use it, we will not ad hoc put all kinds of documents everywhere which of course cannot be followed by the team and will need endless meetings.
|
||||
* We are aware of victimhood and try not to be there, we take responsibility for our own actions first, if the story is not clear and we accepted it it's our own fault, if we didn’t escalate to the right stakeholders it's our own fault, if we didn’t report our progress properly it's our own fault people don’t know,...
|
||||
* We avoid as much as we can centralized tools, only when there is really no alternative (yet) we use them e.g. GDrive and the stakeholders do agree. No-one has the power to choose another tool unless OurWorld, Project INCA & TF together agree. This is super important to make sure that we can create this portal and work together efficiently.
|
||||
* Whoever cannot work this way is not welcome to be an active contributor to the Project INCA Team. The coordinators make sure this section is enforced.
|
||||
|
||||
|
||||
## We do believe
|
||||
|
||||
* Our Team Members are passionate and truly Believe TF has something to offer.
|
||||
* Our Team Members DO not do it to make a quick win (tokens), \
|
||||
Our Team Members do it in the first place because they want TF to succeed.
|
||||
* Our Team Members are capable of collaborating and being inclusive and respectful.
|
||||
* Our Team Members do understand we are different and want to be different
|
||||
23
collections/projectinca/plan/governance.md
Normal file
23
collections/projectinca/plan/governance.md
Normal file
@ -0,0 +1,23 @@
|
||||
## INCA Governance
|
||||
|
||||
A Wisdom Council approves budgets in line to tokenomics above.
|
||||
|
||||
The ThreeFold Wisdom Council will have 9 members in total. For any decision taken by the council, at least 6 must agree to go forward.
|
||||
|
||||
### Council Members
|
||||
|
||||
We start with 7 members and 2 more members will need to be added later on.
|
||||
|
||||
- 1 OurWorld (Kristof)
|
||||
- 1 ThreeFold DMCC (Adnan)
|
||||
- 1 TF9 (Jan)
|
||||
- 1 Sikana (Greg)
|
||||
- 1 CodeScalers (Nayer)
|
||||
- 1 ThreeFold COOP (Sabrina)
|
||||
- The COOP project is still ongoing and will still be created.
|
||||
- 1 GreenEdge (MWW)
|
||||
|
||||
### Budget Allocation
|
||||
|
||||
- Budgets get allocated to projects on git.threefold.info
|
||||
- Clear stories with clear budget allocations and cashflow tracking or time tracking
|
||||
19
collections/projectinca/plan/ideas.md
Normal file
19
collections/projectinca/plan/ideas.md
Normal file
@ -0,0 +1,19 @@
|
||||
|
||||
|
||||
# Ideas
|
||||
|
||||
|
||||
## INCA G
|
||||
|
||||
|
||||
* Replacement strategy of staking is
|
||||
* People need INCA in their wallets to get discounts.
|
||||
* Certain amount of INCA is needed to be held per Node if they want to guarantee their SLA’s , if they can’t achieve their SAL then these tokens are used to compensate market
|
||||
* An INCA G (Generator) token can be created
|
||||
* INCA G is a generator token of future capacity, name can change
|
||||
* This token can be sold with no limits even on Solana as long as people are whitelisted
|
||||
* INCA G will be structured as a real Security in our Digital Freezone once we have it.
|
||||
* INCA G can only be sold to people who did KYC/AML \
|
||||
and paid a 24 EUR membership fee to be part of our cooperative in the freezone.
|
||||
* We can organize semi public sell of INCA Tokens through free-zone
|
||||
* Other ideas ???
|
||||
75
collections/projectinca/plan/requirements.md
Normal file
75
collections/projectinca/plan/requirements.md
Normal file
@ -0,0 +1,75 @@
|
||||
|
||||
# Requirements = “our box we operate in”
|
||||
|
||||
Its important we all agree on our requirements and all actions will be in line with these requirements.
|
||||
|
||||
## Regulatory
|
||||
|
||||
Avoid any possible link to token as security
|
||||
|
||||
* There will be no staking of INCA or any other token created.
|
||||
* There will be no yield generating instruments created with INCA
|
||||
* There will be no public launch of INCA Tokens (private sell ok)
|
||||
|
||||
A COOP might be a good structure for resolving our regulatory requirements for farmers \
|
||||
& larger customers.
|
||||
|
||||
* It needs to be all super simple and easy for our user base.
|
||||
* Every farmer and every user who is spending more than 1000 USD/month \
|
||||
(using any supported digital or fiat currency) \
|
||||
is part of a COOP which will be structured in our digital freezone.
|
||||
* This will be made super easy (just KYC simple process) and you pay 24 USD to get started.
|
||||
* COOP Membership fee is :
|
||||
* 1 USD per month for basic users (to be paid at setup) for INCA G holders
|
||||
* 10 USD per month for members who need more features
|
||||
|
||||
|
||||
## Reputation
|
||||
|
||||
One of our biggest strengths is how we link back to the real world through our government connections and soon a major telco. While this is great this also means we need to stay very clean in relation to reputation and how we come across.
|
||||
|
||||
## Positioning
|
||||
|
||||
* We don’t try to be like the other casino projects or even mimic what they do.
|
||||
* We are ourselves a decent project, with an aim to become the biggest Edge Cloud Provider in the world which is a viable alternative to the centralized players.
|
||||
* We focus on expansion because that is needed first.
|
||||
|
||||
## Marketing Wise
|
||||
|
||||
* We will not brand ourselves or even be understood as a pump & dump, \
|
||||
We stay loyal to our values at all times.
|
||||
* We are different and will position ourselves as being different.
|
||||
|
||||
|
||||
## Funding & Tokenomics
|
||||
|
||||
Let's together agree on the following:
|
||||
|
||||
|
||||
|
||||
* There is focus on finding funding, the people who do fundraise do understand how it works e.g. first get to the term sheet before giving certain info, get lots of info open for negotiation and advice, know that most questions asked are asked for other reasons, …
|
||||
* <span style="text-decoration:underline;">If there is vesting then Vesting for TFT holders will be the same for ALL TFT holders.</span>
|
||||
* We are perfectly ok to show an overview of who has which tokens but some work needs to be done, some original token holders agree to grant tokens to a pool, some of the details are on our INCA wiki.
|
||||
* TFT x1 or TFT x2 can be part of negotiation once enough money has been found, e.g. if 30m EUR comes then I am sure we can convince our community to keep it on 1x \
|
||||
(1x = means 1 Billion of the 4 Billion)
|
||||
* We will not sell INCA tokens underneath 0.05 USD per INCA, \
|
||||
this needs to be the absolute lowest level (and anyhow no public sell).
|
||||
|
||||
|
||||
## Transparency
|
||||
|
||||
|
||||
* There is a weekly report sent to community, TF, Ourworld around what has been achieved
|
||||
* There are regular meetings with community
|
||||
* There are regular stakeholder meetings (at least 1x per week at start)
|
||||
* All our docs are as much as possible opensource, on gitea (doc…), if not possible gdrive but always in the same gdrive under the same root folder and open as much as possible.
|
||||
|
||||
|
||||
# Remark: we are ok with
|
||||
|
||||
* Using exchanges, market makers, …
|
||||
* Meeting the market where it's at.
|
||||
* Use influencers.
|
||||
* Play the game (as long as we don’t lose our values)
|
||||
* Use whatever tools which are needed to reach communities (they can be centralized ofcourse)
|
||||
|
||||
27
collections/projectinca/plan/tf_colab.md
Normal file
27
collections/projectinca/plan/tf_colab.md
Normal file
@ -0,0 +1,27 @@
|
||||
|
||||
# Threefold is involved
|
||||
|
||||
|
||||
## Involvement of TF9
|
||||
|
||||
We communicate between the circles using our tooling…
|
||||
|
||||
* Listen to requirements and keep on developing the tech.
|
||||
* Support the TFGrid, keep it up and running
|
||||
* Create TF Grid 4
|
||||
|
||||
## Involvement of ThreeFold Dubai
|
||||
|
||||
We communicate between the circles using our tooling…
|
||||
|
||||
* Find nice projects who want to build on top of us e.g. Holochain, DFinity, …
|
||||
* Manage the grant pools.
|
||||
* Manage the validators for TFGrid, means help the people who host them, it's decentralized
|
||||
* Manage the tokens and guardians (protectors of smart contracts, bridges).
|
||||
* Help maintain the wiki’s, websites, …
|
||||
* Help in fundraise
|
||||
|
||||
|
||||
> TODO: complete
|
||||
|
||||
|
||||
16
collections/projectinca/plan/theplan_a.md
Normal file
16
collections/projectinca/plan/theplan_a.md
Normal file
@ -0,0 +1,16 @@
|
||||
|
||||
|
||||
# DePIN Launch Plan A
|
||||
|
||||
ThreeFold is expanding to the DePIN market.
|
||||
|
||||
- INCA is the token for the TFGrid 4.x
|
||||
- It's our commercialization token
|
||||
- It will be used on the INCA marketplace
|
||||
|
||||
|
||||
## info
|
||||
|
||||
- [INCA Token](inca1.md)
|
||||
- [Governance](governance.md)
|
||||
|
||||
@ -1,6 +1,8 @@
|
||||
|
||||
|
||||
# DePIN Launch
|
||||
# DePIN Launch Plan B
|
||||
|
||||
> In case not enough funding was found.
|
||||
|
||||
ThreeFold is expanding to the DePIN market.
|
||||
|
||||
@ -4,5 +4,5 @@
|
||||
|
||||
In this section, we provide general information on the Project INCA.
|
||||
|
||||
> Please do note the name will prob still change.
|
||||
|
||||
|
||||
|
||||
3
collections/projectinca/technology.md
Normal file
3
collections/projectinca/technology.md
Normal file
@ -0,0 +1,3 @@
|
||||
|
||||
|
||||
> see [https://threefold.info/tech](https://threefold.info/tech)
|
||||
|
Before Width: | Height: | Size: 219 KiB After Width: | Height: | Size: 219 KiB |
|
Before Width: | Height: | Size: 150 KiB After Width: | Height: | Size: 150 KiB |
69
collections/projectinca/tokens0/inca0.md
Normal file
69
collections/projectinca/tokens0/inca0.md
Normal file
@ -0,0 +1,69 @@
|
||||
|
||||
## High Level Tokenomics INCA (Plan B)
|
||||
|
||||
> This is the plan if we don't find enough funding for Project INCA and need to grow organically.
|
||||
|
||||
There can never be more than 4 Billion INCA.
|
||||
|
||||
- 50% of supply for Farming
|
||||
- People expanding the network with Router & Node capacity over the multiple releases
|
||||
- 14% Million for community grants
|
||||
- We want to expand and build our project in first place together with the community
|
||||
- 1.5% Million for community expansion specifically for INCA
|
||||
- Promotion of the TFGrid
|
||||
- 5.5% for liquidity providing (DEX, marketmakers, ...)
|
||||
- 11.5% originating from "Original Technology Acquisition"
|
||||
- ThreeFold and INCA is the result of technology developed in a tech company, which got acquired many years ago, this resulted in a token grant for the stakeholders of that company
|
||||
- 17.5% for team and contributor rewards
|
||||
- It's for people who help to expand the Grid (starting now)
|
||||
- A lot of it is to reward our partners to help launch the INCA Tokens & the TFGrid
|
||||
|
||||
|
||||
```echarts
|
||||
option = {
|
||||
title: {
|
||||
text: 'INCA Token',
|
||||
subtext: 'Distribution',
|
||||
left: 'center'
|
||||
},
|
||||
tooltip: {
|
||||
trigger: 'item'
|
||||
},
|
||||
series: [
|
||||
{
|
||||
name: 'Distribution',
|
||||
type: 'pie',
|
||||
radius: '70%',
|
||||
data: [
|
||||
{ value: 2000, name: 'Farming Rewards' },
|
||||
{ value: 229, name: 'Liquidity' },
|
||||
{ value: 560, name: 'Community Grants' },
|
||||
{ value: 460, name: 'Original Technology Acquisition' },
|
||||
{ value: 60, name: 'Community Expansion' },
|
||||
{ value: 700, name: 'Team' },
|
||||
],
|
||||
emphasis: {
|
||||
itemStyle: {
|
||||
shadowBlur: 10,
|
||||
shadowOffsetX: 0,
|
||||
shadowColor: 'rgba(0, 0, 0, 0.5)'
|
||||
}
|
||||
}
|
||||
}
|
||||
]
|
||||
};
|
||||
```
|
||||
|
||||
## Release Schedule
|
||||
|
||||
|
||||
|
||||
The following table shows planned release, some of the mechanisms and details are still being worked on.
|
||||
|
||||
*Accelerated Vesting means: if INCA gets above 0.5 USD per INCA (50%), the vesting accelerates in proportion to the percentage (e.g. 0.6 CHF per INCA = 60$ acceleration). At 1 CHF per INCA (100%) and more, the acceleration is 100%.*
|
||||
|
||||
|
||||
For more information about our gen3 token see [here](tft.md).
|
||||
|
||||
|
||||
<!-- https://docs.google.com/spreadsheets/d/1c1eR7oGcRdDkPnqOrERqLwY46V7PbVgKB8Vt-OUvj60/edit#gid=575798760 -->
|
||||
@ -1,4 +1,6 @@
|
||||
# Tokens Distribution
|
||||
# Tokens Distribution (Plan B)
|
||||
|
||||
> This is the plan if we don't find enough funding for Project INCA and need to grow organically.
|
||||
|
||||
The INCA token is the result of our 4 generations of product releases.
|
||||
|
||||
61
collections/projectinca/tokens1/inca_a.md
Normal file
61
collections/projectinca/tokens1/inca_a.md
Normal file
@ -0,0 +1,61 @@
|
||||
|
||||
|
||||
|
||||
## TOKENS
|
||||
|
||||
There might be 2 tokens
|
||||
|
||||
> TODO: to complete
|
||||
|
||||
### INCA Token
|
||||
|
||||
> INCA = INternet CApacity (is the token of buying/selling Internet/Cloud Capacity)
|
||||
|
||||
- 4 billion INCA will be created
|
||||
|
||||
|
||||
<br>
|
||||
|
||||
### INCA-G (to be discussed)
|
||||
|
||||
> INCA-G = INCA Generator (is a token generating INCA typically over 48 months)
|
||||
|
||||
An INCA-G token generates INCA over a certain period. INCA stands for Internet Capacity token, enabling individuals to buy/sell Internet & Cloud Capacity.
|
||||
|
||||
We can analogize the generation of Cloud/Internet capacity to the generation of electricity. In this analogy, INCA is akin to the KWH token, while INCA-G is comparable to the KW token (representing capacity to generate electricity).
|
||||
|
||||
INCA-G tokens are unique and come with metadata specifying how INCA will be generated. This metadata outlines the generation schedule of INCA over the next X months.
|
||||
|
||||
!!wiki.include page:'projectinca:inca.md'
|
||||
|
||||
## How to Acquire the INCA-G Token?
|
||||
|
||||
> TODO: to be discussed
|
||||
|
||||
### Round 1: SwissBorg & TF Cooperative
|
||||
|
||||
1 INCA-G token generates 15,000 INCA over 48 months.
|
||||
|
||||
1 INCA-G can be bought:
|
||||
|
||||
- From SwissBorg for 500 CHF
|
||||
- Crypto-enabled bank in Switzerland
|
||||
- Maximum sold is 5,000 INCA-G tokens
|
||||
- with TFT which is the founder creator currency of the current grid
|
||||
- There will never be more than 1 billion TFT
|
||||
- 1 INCA-G token costs 10,000 TFT (\*)
|
||||
|
||||
> (\*) The pricing will depend on price of TFT at that moment.
|
||||
|
||||
### Round 2: **A**frica and Latin **A**merica INCA-G Tokens (AA)
|
||||
|
||||
> TODO: to be discussed
|
||||
|
||||
1 INCA-G AA Token generates 10,000 INCA over 48 months.
|
||||
|
||||
AA stands for Africa and latin America
|
||||
|
||||
- From SwissBorg for *TBD* CHF.
|
||||
|
||||
The incoming funds will be used to generate Cloud & Internet capacity in these regions, <br>which are serious growth regions in the world.
|
||||
|
||||
55
collections/projectinca/tokens1/tft1.md
Normal file
55
collections/projectinca/tokens1/tft1.md
Normal file
@ -0,0 +1,55 @@
|
||||
## TFT Main Stats
|
||||
|
||||
TFT is the token on Stellar as was used on our previous grids (v 1,2,3).
|
||||
|
||||
- **The TFT is our Creator Token, it has established and proven the technology**
|
||||
|
||||
- Right now about 5 million TFT are farmed (mined) per month
|
||||
- Farming of TFT will stop at 1 Billion TFT
|
||||
|
||||
|
||||
```echarts
|
||||
option = {
|
||||
title: {
|
||||
text: 'TFT Token Version 3.x',
|
||||
subtext: 'Distribution',
|
||||
left: 'center'
|
||||
},
|
||||
tooltip: {
|
||||
trigger: 'item'
|
||||
},
|
||||
series: [
|
||||
{
|
||||
name: 'Distribution',
|
||||
type: 'pie',
|
||||
radius: '70%',
|
||||
data: [
|
||||
{ value: 700, name: 'Farming Done' },
|
||||
{ value: 80, name: 'Liquidity' },
|
||||
{ value: 360, name: 'Grants' },
|
||||
{ value: 460, name: 'Technology Acquisition' },
|
||||
{ value: 400, name: 'Advisors, Founders & Team' },
|
||||
],
|
||||
emphasis: {
|
||||
itemStyle: {
|
||||
shadowBlur: 10,
|
||||
shadowOffsetX: 0,
|
||||
shadowColor: 'rgba(0, 0, 0, 0.5)'
|
||||
}
|
||||
}
|
||||
}
|
||||
]
|
||||
};
|
||||
```
|
||||
|
||||
- Rivine-minted TFT: 112,862,249
|
||||
- Stellar-minted TFT: 181,262,054
|
||||
|
||||
### On v3.x of our Grid TFT Farming is limited to 1 Billion
|
||||
|
||||
- Farming on TFGrid (our v3 release) stops at 1 Billion.
|
||||
- Farming continues (over v4 release) total will be 50% of the total supply (1,2,3 and 4 release)
|
||||
|
||||
*The values above are estimate in some cases as we don't have full visibility and details for all wallets, but of course the totals are correct.*
|
||||
|
||||
For the Grants, see [the Grants Document](grants.md).
|
||||
48
collections/projectinca/tokens1/tokens1.md
Normal file
48
collections/projectinca/tokens1/tokens1.md
Normal file
@ -0,0 +1,48 @@
|
||||
# INCA Tokens Distribution
|
||||
|
||||
> Not ready yet, we are defining how to do this best.
|
||||
|
||||
The INCA token is the result of our 4 generations of product releases.
|
||||
|
||||
- INCA will be on many DEXes
|
||||
- The INCA will be bridged to other major blockchains and we aim to have INCA available on Exchanges.
|
||||
|
||||
We are a community driven project and that shows in our tokenomics, over the both generations:
|
||||
|
||||
- +70% of all tokens over both generation net's is for the community (farming, grants, liquidity providing ...)
|
||||
- 11.5% was for the original technology acquisition
|
||||
- 17.5% is for the team and contributors
|
||||
|
||||
```echarts
|
||||
option = {
|
||||
title: {
|
||||
text: 'INCA Token',
|
||||
subtext: 'Distribution',
|
||||
left: 'center'
|
||||
},
|
||||
tooltip: {
|
||||
trigger: 'item'
|
||||
},
|
||||
series: [
|
||||
{
|
||||
name: 'Distribution',
|
||||
type: 'pie',
|
||||
radius: '70%',
|
||||
data: [
|
||||
{ value: 2710, name: 'Community Rewards: Farming + grants' },
|
||||
{ value: 130, name: 'Liquidity' },
|
||||
{ value: 460, name: 'Original Technology Acquisition' },
|
||||
{ value: 700, name: 'Team' },
|
||||
],
|
||||
emphasis: {
|
||||
itemStyle: {
|
||||
shadowBlur: 10,
|
||||
shadowOffsetX: 0,
|
||||
shadowColor: 'rgba(0, 0, 0, 0.5)'
|
||||
}
|
||||
}
|
||||
}
|
||||
]
|
||||
};
|
||||
```
|
||||
|
||||
@ -0,0 +1,3 @@
|
||||
# ThreeFold System Administrators Manual
|
||||
|
||||
This manual covers all practical tutorials for system administrators working on the ThreeFold Grid.
|
||||
@ -1,93 +0,0 @@
|
||||
# ThreeFold System Administrators Manual
|
||||
|
||||
This manual covers all practical tutorials for system administrators working on the ThreeFold Grid.
|
||||
|
||||
<h2> Table of Contents </h2>
|
||||
|
||||
- [Getting Started](tfgrid3_getstarted.md)
|
||||
- [SSH Remote Connection](ssh_guide.md)
|
||||
- [SSH with OpenSSH](ssh_openssh.md)
|
||||
- [SSH with PuTTY](ssh_putty.md)
|
||||
- [SSH with WSL](ssh_wsl.md)
|
||||
- [WireGuard Access](ssh_wireguard.md)
|
||||
- [Remote Desktop and GUI](remote_desktop_gui.md)
|
||||
- [Cockpit: a Web-based Interface for Servers](cockpit_guide.md)
|
||||
- [XRDP: an Open-Source Remote Desktop Protocol](xrdp_guide.md)
|
||||
- [Apache Guacamole: a Clientless Remote Desktop Gateway](guacamole_guide.md)
|
||||
- [Planetary Network](planetarynetwork.md)
|
||||
- [TFGrid Services](tf_grid_services_readme.md)
|
||||
- [GPU](gpu_toc.md)
|
||||
- [GPU Support](gpu.md)
|
||||
- [Terraform](terraform_toc.md)
|
||||
- [Overview](terraform_readme.md)
|
||||
- [Installing Terraform](terraform_install.md)
|
||||
- [Terraform Basics](terraform_basics.md)
|
||||
- [Full VM Deployment](terraform_full_vm.md)
|
||||
- [GPU Support](terraform_gpu_support.md)
|
||||
- [Resources](terraform_resources_readme.md)
|
||||
- [Using Scheduler](terraform_scheduler.md)
|
||||
- [Virtual Machine](terraform_vm.md)
|
||||
- [Web Gateway](terraform_vm_gateway.md)
|
||||
- [Kubernetes Cluster](terraform_k8s.md)
|
||||
- [ZDB](terraform_zdb.md)
|
||||
- [Zlogs](terraform_zlogs.md)
|
||||
- [Quantum Safe Filesystem](terraform_qsfs.md)
|
||||
- [QSFS on Micro VM](terraform_qsfs_on_microvm.md)
|
||||
- [QSFS on Full VM](terraform_qsfs_on_full_vm.md)
|
||||
- [CapRover](terraform_caprover.md)
|
||||
- [Advanced](terraform_advanced_readme.md)
|
||||
- [Terraform Provider](terraform_provider.md)
|
||||
- [Terraform Provisioners](terraform_provisioners.md)
|
||||
- [Mounts](terraform_mounts.md)
|
||||
- [Capacity Planning](terraform_capacity_planning.md)
|
||||
- [Updates](terraform_updates.md)
|
||||
- [SSH Connection with Wireguard](terraform_wireguard_ssh.md)
|
||||
- [Set a Wireguard VPN](terraform_wireguard_vpn.md)
|
||||
- [Synced MariaDB Databases](terraform_mariadb_synced_databases.md)
|
||||
- [Nomad](terraform_nomad.md)
|
||||
- [Nextcloud Deployments](terraform_nextcloud_toc.md)
|
||||
- [Nextcloud All-in-One Deployment](terraform_nextcloud_aio.md)
|
||||
- [Nextcloud Single Deployment](terraform_nextcloud_single.md)
|
||||
- [Nextcloud Redundant Deployment](terraform_nextcloud_redundant.md)
|
||||
- [Nextcloud 2-Node VPN Deployment](terraform_nextcloud_vpn.md)
|
||||
- [Pulumi](pulumi_readme.md)
|
||||
- [Introduction to Pulumi](pulumi_intro.md)
|
||||
- [Installing Pulumi](pulumi_install.md)
|
||||
- [Deployment Examples](pulumi_examples.md)
|
||||
- [Deployment Details](pulumi_deployment_details.md)
|
||||
- [Mycelium](mycelium_toc.md)
|
||||
- [Overview](overview.md)
|
||||
- [Installation](installation.md)
|
||||
- [Additional Information](information.md)
|
||||
- [Message](message.md)
|
||||
- [Packet](packet.md)
|
||||
- [Data Packet](data_packet.md)
|
||||
- [API YAML](api_yaml.md)
|
||||
- [Computer and IT Basics](computer_it_basics.md)
|
||||
- [CLI and Scripts Basics](cli_scripts_basics.md)
|
||||
- [Docker Basics](docker_basics.md)
|
||||
- [Git and GitHub Basics](git_github_basics.md)
|
||||
- [Firewall Basics](firewall_basics.md)
|
||||
- [UFW Basics](ufw_basics.md)
|
||||
- [Firewalld Basics](firewalld_basics.md)
|
||||
- [File Transfer](file_transfer.md)
|
||||
- [Screenshots](screenshots.md)
|
||||
- [Advanced](advanced.md)
|
||||
- [Token Transfer Keygenerator](token_transfer_keygenerator.md)
|
||||
- [Cancel Contracts](cancel_contracts.md)
|
||||
- [Contract Bills Reports](contract_bill_report.md)
|
||||
- [Listing Free Public IPs](list_public_ips.md)
|
||||
- [Cloud Console](cloud_console.md)
|
||||
- [Redis](grid3_redis.md)
|
||||
- [IPFS](ipfs_toc.md)
|
||||
- [IPFS on a Full VM](ipfs_fullvm.md)
|
||||
- [IPFS on a Micro VM](ipfs_microvm.md)
|
||||
- [MinIO Operator with Helm3](minio_helm3.md)
|
||||
- [Hummingbot](hummingbot.md)
|
||||
- [AI & ML Workloads](ai_ml_workloads.md)
|
||||
- [Ecommerce](ecommerce.md)
|
||||
- [WooCommerce](woocommerce.md)
|
||||
- [nopCommerce](nopcommerce.md)
|
||||
- [Hummingbot](hummingbot.md)
|
||||
- [HTTPS with Caddy](https_caddy.md)
|
||||
- [Node Status Bot](node_status_bot.md)
|
||||
@ -1,10 +1,15 @@
|
||||
|
||||
|
||||
|
||||
## Architecture
|
||||
|
||||
The ThreeFold Grid architecture provides a myriad of cloud possibilities thanks to its interrelated layers.
|
||||
|
||||
|
||||
|
||||
The system has been designed to be scalable to a planet level.
|
||||
|
||||
- Mycelium is the Network Layer
|
||||
- 3Nodes are the nodes running Zero-OS which is our own operating System providing compute, storage and network capacity
|
||||
|
||||
### 3Nodes
|
||||
|
||||
The network of nodes which make up the cloud. Each node provides compute, storage and network capacity.
|
||||
@ -15,46 +20,26 @@ A cloud needs hardware/servers to function. Servers of all shapes and sizes can
|
||||
|
||||
Farmers download the Zero-OS operating system and boot their servers. Once booted, these servers become 3Nodes. The 3Nodes will register themselves in a blockchain. Once registered, the capacity of the 3Nodes will become available. This enables a peer2peer environment for people or companies to reserve their Internet Capacity directly from the hardware but yet allowing full control by commercial parties if that would be required.
|
||||
|
||||
|
||||
## Ultra Scalable
|
||||
|
||||
|
||||
|
||||
This architecture scales to the planet.
|
||||
|
||||
## Zero-OS
|
||||
## Core Components
|
||||
|
||||
We have build our own operating system called Zero-OS, which was based starting from a Linux Kernel with as purpose to remove all the unnecessary complexities found on contemporary OS's.
|
||||
!!wiki.include page:components_links.md
|
||||
|
||||
Zero-OS supports a small number of primitives, and performs low-level functions natively.
|
||||
### Web3 & Decentralized AI Compatibility
|
||||
|
||||
It delivers 3 primitive functions:
|
||||
Our Decentralized Cloud Technology the ideal platform for hosting any web3 and AI workloads.
|
||||
|
||||
- storage capacity
|
||||
- compute capacity
|
||||
- network capacity
|
||||
Our Zero-OS operating system already supports integrated GPUs, ensuring optimal performance for decentralized AI applications.
|
||||
|
||||
There is no shell, local nor remote attached to Zero-OS. Given its shell-less nature, the people and organizations, called farmers, that run 3nodes cannot issue any commands nor access its features. In that sense, Zero-OS enables a "zero people" (autonomous) Decentralzied Cloud, meaning hackers cannot get in, while also eliminating human error from the paradigm.
|
||||
> Any workload (web2/3 and AI) can run on on our Decentralized Cloud.
|
||||
|
||||
|
||||
### Mycelium Routers
|
||||
|
||||
Thanks to Mycelium Routers anyone can now operate as a network service provider.
|
||||
|
||||
Mycelium Routers seamlessly integrate with our Mycelium network technology, efficiently selecting the shortest path between all participants.
|
||||
|
||||
These Mycelium Routers are not only compatible with Wi-Fi but also with 4G and 5G networks, ensuring versatile connectivity options.
|
||||
|
||||
## 3Bots: The Autonomous Layer
|
||||
|
||||
|
||||
|
||||
### Smart Contract for IT
|
||||
|
||||
The purpose of the smart contract for IT is to create and enable autonomous IT. Autonomous self-driving IT is possible.
|
||||
|
||||
Once a smart contract for IT is created, it will be registered in the TFChain Blockchain.
|
||||
|
||||
### TFChain
|
||||
## TFChain: our Blockchain
|
||||
|
||||
This blockchain does the following:
|
||||
|
||||
@ -64,15 +49,3 @@ This blockchain does the following:
|
||||
- info as required for the Smart Contract for IT
|
||||
|
||||
This is the hart of our operational system of our decentralized cloud.
|
||||
|
||||
### Web Gateways
|
||||
|
||||
The Web Gateway is a mechanism to connect the private (overlay) networks (Mycelium) to the open Internet. By not providing an open and direct path in to the private network, a lot of malicious phishing and hacking attempts are stopped at the Web Gateway level for container applications.
|
||||
|
||||
### Web3 & Decentralized AI Compatibility
|
||||
|
||||
Our Decentralized Cloud Technology the ideal platform for hosting any web3 and AI workloads.
|
||||
|
||||
Our Zero-OS operating system already supports integrated GPUs, ensuring optimal performance for decentralized AI applications.
|
||||
|
||||
> Any workload (web2/3 and AI) can run on on our Decentralized Cloud.
|
||||
BIN
collections/tech/architecture/img/architecture_intro.png
Normal file
BIN
collections/tech/architecture/img/architecture_intro.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 316 KiB |
BIN
collections/tech/architecture/img/zos00.png
Normal file
BIN
collections/tech/architecture/img/zos00.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 320 KiB |
14
collections/tech/architecture/network.md
Normal file
14
collections/tech/architecture/network.md
Normal file
@ -0,0 +1,14 @@
|
||||
|
||||
|
||||
|
||||
### Mycelium Routers
|
||||
|
||||
Thanks to Mycelium Routers anyone can now operate as a network service provider.
|
||||
|
||||
Mycelium Routers seamlessly integrate with our Mycelium network technology, efficiently selecting the shortest path between all participants.
|
||||
|
||||
These Mycelium Routers are not only compatible with Wi-Fi but also with 4G and 5G networks, ensuring versatile connectivity options.
|
||||
|
||||
### Web Gateways
|
||||
|
||||
The Web Gateway is a mechanism to connect the private (overlay) networks (Mycelium) to the open Internet. By not providing an open and direct path in to the private network, a lot of malicious phishing and hacking attempts are stopped at the Web Gateway level for container applications.
|
||||
@ -5,3 +5,5 @@ tech_overview.png
|
||||
tech_overview2.png
|
||||
web_remade.png
|
||||
cloud_features.png
|
||||
base_layer.png
|
||||
scale.png
|
||||
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 549 KiB After Width: | Height: | Size: 533 KiB |
BIN
collections/tech/img/base_layer.png
Normal file
BIN
collections/tech/img/base_layer.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 394 KiB |
BIN
collections/tech/img/pathtoweb4.png
Normal file
BIN
collections/tech/img/pathtoweb4.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 313 KiB |
BIN
collections/tech/img/scale.png
Normal file
BIN
collections/tech/img/scale.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 277 KiB |
12
collections/tech/innovations/components_links.md
Normal file
12
collections/tech/innovations/components_links.md
Normal file
@ -0,0 +1,12 @@
|
||||
Compute
|
||||
- [Zero-OS: a minimalistic and more efficient server operating system](zos_innovation)
|
||||
- [Zero-Image: a new way to deal with OS Images](flist_innovation.md)
|
||||
|
||||
Network
|
||||
- [Mycelium: a new network layer for the Internet](mycelium_innovation.md)
|
||||
- [Network Wall: a secure way to connect your apps to Internet](network_wall_innovation.md)
|
||||
|
||||
Storage
|
||||
- [Quantum Safe Storage: storage which cannot get lost nor corrupted](zstor_innovation.md)
|
||||
- [Quantum Safe Filesystem: host any storage interface e.g. IPFS](qsfs_innovation.md)
|
||||
- [FungiStor: Content Delivery everwhere in the world](fungistor_innovation.md)
|
||||
60
collections/tech/innovations/compute/compute_inno.md
Normal file
60
collections/tech/innovations/compute/compute_inno.md
Normal file
@ -0,0 +1,60 @@
|
||||
|
||||
# Compute
|
||||
|
||||
| | Threefold Compute Layer | Default |
|
||||
|----------------|--------------------------------------------------------------------------------|------------------------------------------------------------------|
|
||||
| Management | Full P2P, done by 3bot Agents, blockchain IT contract | Centralized e.g. Kubernetes, ... |
|
||||
| OS Deploy | Stateless, there are no files copied on local HDD/SSD. | Deploy image or execute installer on a physical server |
|
||||
| OS Upgrade | Seamless, rolling upgrades, 100% modular and pre-deterministic, decentralized | Difficult and error prone + vulnerable from security perspective |
|
||||
| Tamperproof | If file gets modified Zero-OS will not boot the file. | No, man in middle is possible. |
|
||||
| Scalability | To the world | Expensive and depending on lots of capital |
|
||||
| Security | A lot of effort went into the capability to deploy for high security usecases. | Very hard to deploy securely, and expensive |
|
||||
| Green | For certain workloads we can safe upto 10x on power usage | Super power hungry. |
|
||||
| Liquid Cooling | Easy to do because of autonomous behavior no need to replace HW. | Hard to do, how to do maintenance. |
|
||||
| Sovereign | Yes | No |
|
||||
| Complexity | Anyone can do it, we made it to allow everyone to be a provider. | Real experts needed. |
|
||||
|
||||
> We do not compare our system with those that claim to be full cloud solutions but merely deploy containers using other management systems and optionally connect to a blockchain for billing purposes. Nor do we compare with marketplace systems that simply act as frontends for other systems. We believe these systems, while visually impressive, lack substantial technological foundations and cannot serve as a fundamental base layer for others.
|
||||
|
||||
## Zero-OS
|
||||
|
||||
|
||||
|
||||
ThreeFold has developed its own operating system, Zero-OS, which is based on the Linux Kernel. The purpose of Zero-OS is to strip away the unnecessary complexities commonly found in contemporary operating systems.
|
||||
|
||||
**Key Features of Zero-OS:**
|
||||
|
||||
Zero-OS is designed with minimalism in mind, supporting only a few fundamental primitives that handle essential low-level functions:
|
||||
|
||||
1. **Storage Capacity**
|
||||
2. **Compute Capacity**
|
||||
3. **Network Capacity**
|
||||
|
||||
**Security and Simplicity:**
|
||||
|
||||
Zero-OS provides a Autonomous Decentralized Cloud.
|
||||
|
||||
This not only blocks hacker access but also eliminates human error, enhancing both security and reliability.
|
||||
|
||||
### Deployment by IT contract
|
||||
|
||||
Secure Reproducable Verified Authenticated
|
||||
|
||||
|
||||
|
||||
The purpose of the smart contract for IT is to create and enable autonomous IT. Autonomous self-driving IT is possible.
|
||||
|
||||
Once a smart contract for IT is created, it will be registered in the TFChain Blockchain.
|
||||
|
||||
|
||||
|
||||
## Compatible with the world
|
||||
|
||||
|
||||
|
||||
|
||||
## 3Bots: The Autonomous Layer
|
||||
|
||||
|
||||
|
||||
|
||||
5
collections/tech/innovations/compute/flist_innovation.md
Normal file
5
collections/tech/innovations/compute/flist_innovation.md
Normal file
@ -0,0 +1,5 @@
|
||||
|
||||
## Zero-Images: A New Way Of Dealing With OS Images
|
||||
|
||||
!!wiki.include page:flist_innovation_short
|
||||
|
||||
|
Before Width: | Height: | Size: 229 KiB After Width: | Height: | Size: 229 KiB |
BIN
collections/tech/innovations/compute/img/compatible.png
Normal file
BIN
collections/tech/innovations/compute/img/compatible.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 294 KiB |
BIN
collections/tech/innovations/compute/img/itcontract.png
Normal file
BIN
collections/tech/innovations/compute/img/itcontract.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 224 KiB |
BIN
collections/tech/innovations/compute/img/itcontract2.png
Normal file
BIN
collections/tech/innovations/compute/img/itcontract2.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 307 KiB |
@ -1,4 +0,0 @@
|
||||
|
||||
## FList: A New Way Of Dealing With OS Images
|
||||
|
||||
!!wiki.include page:flist_innovation_short
|
||||
@ -19,13 +19,10 @@
|
||||
|
||||
!!wiki.include page:zstor_innovation_short
|
||||
|
||||
|
||||
## Quantum Safe File System
|
||||
|
||||
|
||||
!!wiki.include page:qsfs_innovation_short
|
||||
|
||||
|
||||
## FungiStor
|
||||
|
||||
!!wiki.include page:'fungistor_innovation_short'
|
||||
|
||||
@ -1,15 +1,7 @@
|
||||
<h1> Key Innovations </h1>
|
||||
|
||||
Throughout the years, we've built innovative products that are now part of a whole ecosystem.
|
||||
|
||||
|
||||
|
||||
<h2>Table of Contents</h2>
|
||||
# Key Innovations
|
||||
|
||||
!!wiki.include page:components_links.md
|
||||
|
||||
- [Mycelium: a new network layer for the internet](mycelium_innovation.md)
|
||||
- [Zero-OS: a minimalistic and more efficient server operating system](zos_innovation)
|
||||
- [Quantum Safe Storage](zstor_innovation.md)
|
||||
- [Quantum Safe Filesystem](qsfs_innovation.md)
|
||||
- [FList: a new way to deal with OS Images](flist_innovation.md)
|
||||
- [FungiStor](fungistor_innovation.md)
|
||||
- [Network Wall](network_wall_innovation.md)
|
||||
@ -1,4 +0,0 @@
|
||||
|
||||
## Mycelium: A New Network Layer for the Internet
|
||||
|
||||
!!wiki.include page:mycelium_innovation_short.md
|
||||
1
collections/tech/innovations/network/img/.done
Normal file
1
collections/tech/innovations/network/img/.done
Normal file
@ -0,0 +1 @@
|
||||
mycelium00.png
|
||||
BIN
collections/tech/innovations/network/img/mycelium00.png
Normal file
BIN
collections/tech/innovations/network/img/mycelium00.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 512 KiB |
BIN
collections/tech/innovations/network/img/network_wall.png
Normal file
BIN
collections/tech/innovations/network/img/network_wall.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 386 KiB |
@ -0,0 +1,7 @@
|
||||
|
||||
|
||||
|
||||
|
||||
## Mycelium: A New Network Layer for the Internet
|
||||
|
||||
!!wiki.include page:mycelium_innovation_short.md
|
||||
16
collections/tech/innovations/network/network_inno.md
Normal file
16
collections/tech/innovations/network/network_inno.md
Normal file
@ -0,0 +1,16 @@
|
||||
# Network
|
||||
|
||||
| | ThreeFold Network Layer | Other Overlay Network Technologies (like VPN) |
|
||||
|-----------------------------|-----------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------|
|
||||
| Management | Full P2P, done by 3bot Agents, blockchain IT contract | Centralized leading to security issues |
|
||||
| Locality | Find shortest path on latency and quality, this allows traffic to stay sovereign. | NO, based on centralized control mechanisms or inefficient algorithms that route traffic indiscriminately across the globe. |
|
||||
| Encryption | End2End ecryption, unique for every relation, linked to private key | Normally based on key exchange, or pre-shared keys. |
|
||||
| Post Quantum | Possible (ask us) | No |
|
||||
| Scalability | Our aim is to be planetary scalable, but we need more exposure. | Bad |
|
||||
| Compatibility | We aim to support mobile, desktop, IOT, ... | Depends, often not |
|
||||
| Backdoors | NO, all is based on opensource | Often, yes, unfortunately. |
|
||||
| Performance | Quite good, 1 gbit / sec can be achieved on std node (which is high for overlay) | Often slow. |
|
||||
| Security Model | Whitelist model | Blacklist model, list who is bad e.g. firewalls |
|
||||
| Fully integrated in compute | Yes | Lots of different solutions |
|
||||
|
||||
|
||||
@ -1,8 +1,10 @@
|
||||
|
||||
|
||||
|
||||
|
||||
## Network Wall
|
||||
|
||||
The Network Wall offers 100% separation between where compute workloads are and where services are exposed, proving an extremely high level of security.
|
||||
|
||||
|
||||
|
||||
!!wiki.include page:network_wall_innovation_short
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 422 KiB |
1
collections/tech/innovations/storage/img/.done
Normal file
1
collections/tech/innovations/storage/img/.done
Normal file
@ -0,0 +1 @@
|
||||
storage_inno.png
|
||||
BIN
collections/tech/innovations/storage/img/storage_inno.png
Normal file
BIN
collections/tech/innovations/storage/img/storage_inno.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 246 KiB |
@ -15,8 +15,6 @@ Metadata redundancy is included. While not consistently synchronized in real-tim
|
||||
|
||||
This filesystem can be mounted under various storage-aware applications, such as backup servers, file servers, or S3 servers, enhancing versatility.
|
||||
|
||||
|
||||
|
||||
### Benefits
|
||||
|
||||
- Inherits the advantages of Zero-Stor, including enhanced data security, efficiency, and scalability.
|
||||
17
collections/tech/innovations/storage/storage_inno.md
Normal file
17
collections/tech/innovations/storage/storage_inno.md
Normal file
@ -0,0 +1,17 @@
|
||||
|
||||
|
||||
# Storage
|
||||
|
||||
|
||||
| | ThreeFold Network Layer | Overlay Storage Systems / Networks |
|
||||
|-----------------------------|------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------|
|
||||
| Management | Full P2P, done by 3bot Agents, blockchain IT contract | Centralized leading to security issues |
|
||||
| Locality | Data can be local and sovereign, full control by the the user (data creator) | Based on centralized control mechanisms or inefficient algorithms that route traffic indiscriminately across the globe. |
|
||||
| Quantum Safe | Yes, novel encoding system (not encryption based) makes impossible to hack data. | No |
|
||||
| Post Quantum | Possible (ask us) | No |
|
||||
| Scalability | Yes, this system exists +10 years, is being used by large orgs for zetabytes. | Some systems, most not, but centralized. |
|
||||
| Compatibility | Yes thanks to filesystem approach | Depends, often not |
|
||||
| Backdoors | NO, all is based on opensource | ? |
|
||||
| Performance | Is not a super fast system but good for most cases, +- 100 MB / sec per content creator. | Variable, hard to say, some are |
|
||||
| Efficiency for redundancy | Ultra efficient, only 20% overhead to allow 4 locations to go down | NO, sometimes +5 copies = 500% |
|
||||
| Fully integrated in compute | Yes | Lots of different solutions |
|
||||
BIN
collections/tech/internet/img/3layers.png
Normal file
BIN
collections/tech/internet/img/3layers.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 424 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 360 KiB |
@ -1,8 +1,8 @@
|
||||
# The Internet Is Broken
|
||||
# Rethinking the Internet
|
||||
|
||||
**The Three Layers Of The Internet**
|
||||
|
||||
|
||||
|
||||
|
||||
The Internet is made up of 3 layers:
|
||||
|
||||
@ -12,6 +12,10 @@ The Internet is made up of 3 layers:
|
||||
|
||||
3. Applications: currently applications are hosted in huge data centers using the compute and storage as provided. This system is too centralized and therefore very vulnerable.
|
||||
|
||||
ThreeFold is providing solutions for the first 2 layers and allows everyone else to build on top.
|
||||
|
||||
**Current Challenges**
|
||||
|
||||
Digital information mainly travels over large fiber backbone links as pictured here.
|
||||
|
||||
|
||||
@ -22,9 +26,28 @@ This leads to very inneficient behavior, slower performance, less reliability an
|
||||
|
||||
|
||||
|
||||
Another important aspect is the lack of autonomy and sovereignty within this Internet. We have become the products. All of our data is hosted in large data centers owned by a few large corporations.
|
||||
**Issues with Autonomy and Sovereignty**
|
||||
|
||||
Our current internet model compromises autonomy and sovereignty. Most data is stored in large data centers controlled by a few major corporations, effectively turning users into products.
|
||||
|
||||
|
||||
|
||||
|
||||
We also exist many times on the Internet across many applications and each time a full infrastructure has been built to deliver the applications from. This system is unsustainable and inefficient.
|
||||
Moreover, the internet is replicated many times across various applications, each requiring its own full infrastructure. This approach is unsustainable and inefficient.
|
||||
|
||||
## ThreeFold wants to create a new base layer
|
||||
|
||||
A Base layer who doesn't have these issues.
|
||||
|
||||
ThreeFold resolves
|
||||
|
||||
- reliability for data, data can never be corrupted nor lost
|
||||
- reliability for network, connectivity should always be possible
|
||||
- sovereignity
|
||||
- scalability
|
||||
- security
|
||||
- locality
|
||||
- cost
|
||||
- management (easier to scale)
|
||||
|
||||
|
||||
|
||||
35
collections/tech/internet/t.md
Normal file
35
collections/tech/internet/t.md
Normal file
@ -0,0 +1,35 @@
|
||||
# Rethinking the Internet
|
||||
|
||||
**Understanding the Three Layers of the Internet**
|
||||
|
||||
|
||||
|
||||
The Internet is made of 3 layers:
|
||||
|
||||
1. **Compute & Storage:** This layer houses applications and is predominantly centralized, operating from vast data centers.
|
||||
|
||||
2. **Network:** The network layer facilitates the movement of information, whether it's wireless, via cables like fiber, or through satellite links. Today, information often travels long distances, with a few companies controlling over 80% of the internet’s network capacity.
|
||||
|
||||
3. **Applications:** These are hosted in large data centers, relying on the centralized compute and storage layers. This centralization makes the system vulnerable.
|
||||
|
||||
**Current Challenges**
|
||||
|
||||
Digital information primarily flows through extensive fiber backbone networks, as shown here:
|
||||
|
||||
|
||||
|
||||
The internet’s design causes inefficiencies, such as when two people in Zanzibar use a service like Zoom. Their data travels all the way to European data centers where Zoom's servers are hosted and back, leading to slow performance, decreased reliability, and increased costs.
|
||||
|
||||
|
||||
|
||||
**Issues with Autonomy and Sovereignty**
|
||||
|
||||
Our current internet model compromises autonomy and sovereignty. Most data is stored in large data centers controlled by a few major corporations, effectively turning users into products.
|
||||
|
||||
|
||||
|
||||
Moreover, the internet is replicated many times across various applications, each requiring its own full infrastructure. This approach is unsustainable and inefficient.
|
||||
|
||||
---
|
||||
|
||||
This retains the original structure and links, ensuring that the information is clear and the visual aids are effectively utilized.
|
||||
@ -1,24 +1,13 @@
|
||||
|
||||
|
||||
# The Internet’s Natural Progression
|
||||
|
||||
The Internet was always meant to be a peer-to-peer infrastructure. As large companies became profit and data centric, centralization quickly became the norm.
|
||||
The Internet was always meant to be a peer-to-peer infrastructure.
|
||||
|
||||
As large companies became profit and data centric, centralization quickly became the norm.
|
||||
|
||||
***We have a vision of the Internet which is much more close to how the Internet was intended to be.***
|
||||
|
||||
|
||||
|
||||
|
||||
We believe in a world where every person is the center of their digital life. In this new Internet each person has their own digital avatar which we call a ***Hero***.
|
||||
|
||||
The technical component which makes Hero possible is a compoment called 3Bot. This 3Bot server. only owned and managed by you, lives on top of the cecentralized cloud.
|
||||
|
||||
All the 3Bots communicate to each other over the shortest possible path. This path is end-to-end encrypted.
|
||||
|
||||
|
||||
|
||||
The underlying network of capacity is the decentralized cloud which is like the basic IT energy which makes all of this possible.
|
||||
|
||||
The cecentralized cloud is the result of more than 10 years of development and it is now active on more than 2000 nodes.
|
||||
|
||||
## Requirements For A New Internet
|
||||
|
||||
|
||||
@ -38,3 +27,22 @@ The cecentralized cloud is the result of more than 10 years of development and i
|
||||
- Local sensitive (chose shortest path)
|
||||
- End2End Encrypted
|
||||
- Capable to really know where information goes to or comes from (authenticity)
|
||||
|
||||
## Natural Progression
|
||||
|
||||
|
||||
|
||||
We envision a world where every person is at the center of their digital life. In this new Internet, each person has their own digital avatar, which we call a ***Hero***.
|
||||
|
||||
The technical backbone enabling the Hero is a component known as the 3Bot. This server, owned and managed by you, operates on our decentralized cloud infrastructure.
|
||||
|
||||
Communication between 3Bots is optimized to use the shortest possible paths, ensuring that all interactions are end-to-end encrypted for maximum security and privacy.
|
||||
|
||||
## 3Bot Architecture in relation to TFGrid
|
||||
|
||||
|
||||
|
||||
The underlying network of capacity is the decentralized cloud which is like the basic IT energy which makes all of this possible.
|
||||
|
||||
The cecentralized cloud is the result of more than 20 years of development and it is now active on more than 2000 nodes.
|
||||
|
||||
|
||||
47
collections/tech/overview.md
Normal file
47
collections/tech/overview.md
Normal file
@ -0,0 +1,47 @@
|
||||
|
||||
|
||||
For over 20 years, through more than seven startups, ThreeFold has been developing an infrastructure base layer of software. This platform is ideal for any Decentralized Physical Infrastructure Network (DePIN) or Web 2/3 project to build upon.
|
||||
|
||||
This robust platform serves as a truly decentralized infrastructure base layer, designed to be hosted by everyone, for everyone.
|
||||
|
||||
## ThreeFold: The Base Layer for DePin and Web 2 and 3
|
||||
|
||||
|
||||
|
||||
ThreeFold has developed a scalable, reliable, and efficient decentralized infrastructure base layer.
|
||||
This serves as the foundational base for any Decentralized Physical Infrastructure Network (DePin) or Web 3 application.
|
||||
|
||||
## Anyone can be a cloud service provider
|
||||
|
||||
|
||||
|
||||
**Getting started is easy:** Just get a ThreeFold node and connect it to the Internet.
|
||||
|
||||
Around the world, thousands of entities, from individuals to companies, have become ThreeFold farmers. They connect their computers, known as nodes, to the Internet and install our software. This allows them to provide GPU, compute, storage, and network capacity to the ThreeFold Grid.
|
||||
|
||||
Farmers have two options: they can either buy a ready-made node from our partners or build their own using our detailed DIY (Do It Yourself) guides.
|
||||
|
||||
|
||||
## Usable by Everyone
|
||||
|
||||
|
||||
|
||||
Our platform is designed for everyone, whether you are a developer, system administrator, or IT expert.
|
||||
|
||||
## Open Source Technology
|
||||
|
||||
All of our technology is open source and build by our tech company called TF9 and used to build the ThreeFold Gridt. For more information, visit the [ThreeFold Website](https://www.threefold.io).
|
||||
|
||||
## Bridging the Web2, Web3, and Blockchain Worlds
|
||||
|
||||
ThreeFold acts as the essential layer connecting traditional web technologies with the new, decentralized Web3 and blockchain worlds.
|
||||
|
||||
|
||||
|
||||
## Scalability and Growth
|
||||
|
||||
Our system is designed to scale effortlessly, meeting the needs of a rapidly evolving digital landscape.
|
||||
|
||||
|
||||
|
||||
|
||||
22
collections/tech/roadmap/hero_roadmap.md
Normal file
22
collections/tech/roadmap/hero_roadmap.md
Normal file
@ -0,0 +1,22 @@
|
||||
## High Level Roadmap HERO Stack
|
||||
|
||||
The first version of our Hero enables the management of core services such as an innovative database backend, a sovereign git system, and the automatic integration and deployment of our workloads.
|
||||
|
||||
This stack allows everyone to deploy scalable web 2/3/4 apps on top of the TFGrid.
|
||||
|
||||
|
||||
| | Roadmap | Timing |
|
||||
| -------------------------------- | -------------------------------------------------------------------------------------------------------------------- | ------ |
|
||||
| Hero Publisher | Publish websites, e-books, ... on top of TFGrid | Q2 24 |
|
||||
| Hero CI = Continuous Integration | Easier to use Continuous Integration / Development, very powerfull, with multi node support | Q3 24 |
|
||||
| Hero Play | Integrate declarative automation and configuration management as part of wiki approach in hero Publisher | Q3 24 |
|
||||
| Hero Git | Alternative to centralized Github (based on Gitea), fully integrated on top of TFGrid | Q3 24 |
|
||||
| Hero DB | Flexible ultra redundant database stor with indexing, queries, stored procesudes, super scalable replication | Q3 24 |
|
||||
| Hero OSIS | Object Storage and Index system integrates with hero Git, all data on git based backend | Q3 24 |
|
||||
| Hero WEB | Web framework (with co-routines) using Vlang, deployable globally on TFGrid, integrated with Mycelium Net and Names. | Q3 24 |
|
||||
| Hero Monitor | Monitor all your different components on redundant monitoring stack | Q3 24 |
|
||||
| Hero Happs | Hero natively supports Holochain HAPPS | Q1 25 |
|
||||
| Hero Actors | Hero can serve actors which respond and act on OpenRPC calls ideal as backend for web or other apps. | Q1 25 |
|
||||
| Hero Web 3 Gateway | Hero aims to have native support for chosen Web3 partner solutions | Q1 25 |
|
||||
|
||||
All of above is fully integrated with Mycelium Network and the TF Grid.
|
||||
56
collections/tech/roadmap/tfgrid_roadmap.md
Normal file
56
collections/tech/roadmap/tfgrid_roadmap.md
Normal file
@ -0,0 +1,56 @@
|
||||
## High Level Roadmap
|
||||
|
||||
### Status Today
|
||||
|
||||
The core offering is functioning effectively, maintained through a community-driven, best-effort approach. Currently,
|
||||
there are no Service Level Agreements (SLAs) in place, and there should be increased visibility for users regarding their expectations for uptime,
|
||||
performance, and other service related requirements.
|
||||
|
||||
The uptime and stability of Zero-OS are very good.
|
||||
|
||||
Additionally, hardware compatibility is excellent, with most machines now supported out of the box.
|
||||
|
||||
|
||||
| | Status today | SDK/API | Web UI |
|
||||
| ----------------------- | ------------------------------------------------------------------------------------------------------------ | ------- | ------ |
|
||||
| Zero-OS | Used for management of +30,000 logical CPU cores | yes | yes |
|
||||
| Zero-Images (flists) | Basis for Zero-OS modules as well as replaces images for VM's ... | yes | yes |
|
||||
| Zero-Images from Docker | convert docker through our Hub | yes | yes |
|
||||
| Zero-Images Hub | ThreeFold is hosting some as well as everyone can install their own Hub | yes | yes |
|
||||
| Mycelium Core | Integrated in Zero-OS for VM's as well s ZDB and monitoring | yes | yes |
|
||||
| Mycelium Message Bus | Can be used by any developer for their own usecases | NA | NA |
|
||||
| Quantum Safe Storage | Usable for experts only, is reliably working for +6 years, +100 MB/sec per stream | yes | no |
|
||||
| Quantum Safe Filesystem | QSFS= usable for experts, is a fuse based filesystem on top of the QSS Core | yes | no |
|
||||
| Zero-OS Kubernetes | Working very well, Integrated in ZOS, uses our overlay networks based on Wireguard, can use QSFS underneith. | yes | yes |
|
||||
| Zero-OS VM's | The base of our service portfolio, missing is better service level management | yes | yes |
|
||||
| Zero-OS Monitoring | Working well | yes | yes |
|
||||
| Zero-OS VM Monitoring | Working well, can be retrieved through SDK | yes | yes |
|
||||
| Zero-OS Web Gateway | Working well, but documentation not good enough, and not enough of them deployed | yes | yes |
|
||||
| Zero-Boot | There are multiple ways active on how to deploy Zero-OS all are stateless and capable for full secure boot | | |
|
||||
| | | | |
|
||||
|
||||
|
||||
### Planned new features:
|
||||
|
||||
Considerable effort is being made to enable our partners to go into production;
|
||||
however, for this initiative to truly succeed on planetary level, we need many more nodes deployed in the field.
|
||||
|
||||
| | Roadmap | Timing |
|
||||
| ----------------------------------- | ---------------------------------------------------------------- | ------ |
|
||||
| Zero-OS v4 (our next major release) | v4, no more TFChain, mutual credit, marketplace | Q1 25 |
|
||||
| FungiStor | A revolutionary different way how to deliver content | Q1 25 |
|
||||
| Zero-Images on FungiStor | Can be stored on FungiStor | Q1 25 |
|
||||
| Zero-Images from Docker | CI/CD integration (See below) | Q4 24 |
|
||||
| Zero-Images Hub | CI/CD integration (See below) <BR> 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 |
|
||||
| | | |
|
||||
@ -1,28 +0,0 @@
|
||||
|
||||
# ThreeFold Grid Technology
|
||||
|
||||
ThreeFold has developed a highly efficient infrastructure layer for a new Internet.
|
||||
|
||||
Providing Internet & cloud capacity is as easy as getting a node and connecting it to the Internet.
|
||||
|
||||
|
||||
|
||||
A lot of capacity has been deployed in the world, hundreds of ThreeFold farmers acquired a computer and connected it to the Internet, as such they use our operating system to provide Internet capacity to the world. Farmers can buy pre-built node or build their own via our DIY guides.
|
||||
|
||||
There are multiple ways in which people can interact with our platform, as a developer, a sysadmin, IT expert, etc.
|
||||
|
||||
|
||||
|
||||
All technology is developed by ThreeFold and is opensource, this technology is being used for the ThreeFold grid (see the [ThreeFold Website](https://www.threefold.io)) which is the deployment of a new Internet which is green, safe and owned by all of us.
|
||||
|
||||
This document explains how ThreeFold is the missing layer for the full web2, web3 and blockchain world.
|
||||
|
||||
This leads to a system which is highly scalable.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
|
||||
## Deterministic Deployment
|
||||
## Zero-Chance = Deterministic Deployment
|
||||
|
||||
|
||||
|
||||
@ -17,10 +17,6 @@ Metadata is exposed. The system sees the full tree of the image, but data itself
|
||||
- no dynamic behavior for deployment at runtime
|
||||
- no process can start unless the files are 100% described on flist level
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### There are multiple ways to create an flist:
|
||||
|
||||
- Convert an existing docker image which is hosted on the docker hub
|
||||
@ -1,4 +1,4 @@
|
||||
# ZOS Protect
|
||||
# Zero-Tech
|
||||
|
||||
- The operating system of the 3node (Zero-OS) is made to exist in environments without the presence of technical knowhow. 3nodes are made to exist everywhere where network meet a power socket. The OS does not have a login shell and does not allow people to log in with physical access to a keyboard and screen nor does it allows logins over the network. There is no way the 3node accepts user initiated login attempts.
|
||||
- For certified capacity a group of known strategic vendors are able to lock the [BIOS](https://en.wikipedia.org/wiki/BIOS) of their server range and make sure no-one but them can unlock and change features present in the BIOS. Some vendors have an even higher degree of security and can store private keys in chips in side the computer to provider unique identification based on private keys or have mechanisms to check wether the server has been opened / tampered with in the transportation from the factory / vendor to the Farmer. All of this leads to maximum protection on the hardware level.
|
||||
@ -83,7 +83,7 @@ make run
|
||||
|
||||
## License
|
||||
|
||||
**INCA Docs** is licensed under the Apache 2.0 license — see the [LICENSE](../LICENSE.md) file for details.
|
||||
**INCA Docs** is licensed under the Apache 2.0 license — see the [LICENSE](../LICENSE) file for details.
|
||||
|
||||
## References
|
||||
|
||||
|
||||
@ -45,6 +45,7 @@ export default defineConfig({
|
||||
items: [
|
||||
|
||||
{ label: 'Glossary', link: '/references/glossary/' },
|
||||
{ label: 'Whitepaper', link: '/references/inca_whitepaper/' },
|
||||
{ label: 'Disclaimer', link: '/references/disclaimer/' },
|
||||
],
|
||||
},
|
||||
|
||||
BIN
docs_projectinca/src/content/docs/references/img/devops.png
Normal file
BIN
docs_projectinca/src/content/docs/references/img/devops.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 428 KiB |
BIN
docs_projectinca/src/content/docs/references/img/image1.png
Normal file
BIN
docs_projectinca/src/content/docs/references/img/image1.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 517 KiB |
BIN
docs_projectinca/src/content/docs/references/img/image4.png
Normal file
BIN
docs_projectinca/src/content/docs/references/img/image4.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 376 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 245 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 463 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 134 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 337 KiB |
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in New Issue
Block a user