+ -
+
- Planet First +
- People Second +
- Profit As Result +
+ Everything we do needs: +
-
+
- To have a chance to improve our planet situation (climate change, regenerative, less use of resources, …) +
- To help our communities in becoming their best powerful and aware self, where love and respect comes first. +
+ A more aware approach to global problems: +
-
+
- Humbleness (I am nothing) +
- Gratefulness (planet and people first) +
- Authenticity (I can be the true me and in my power) +
+
+We believe in:
+
+* **Planet First**
+* **People Second**
+* **Profit As Result**
+
+
+Anything we do needs to improve our planet's situation (climate change, regenerative, respect resources, …) and help the people around us. As a result of doing so, we as investors of time and money will have created most value and will get the benefits from our efforts.
+
+Of course being financially healthy is the first requirement.
+
+We are in the forefront of a growing movement, more and more companies are being pushed by customers and stakeholders to prioritize sustainability and planet positive policies. We are not swimming against the stream,
+we are part of a group of leaders of change and making real the zeitgeist of the 21st century.
+
+Together we are a movement, not just a project or company. Together we are creating the Internet of Internets:
+
+* abundance based
+* unlimited knowledge
+* glocal communication and collaboration
+* exchange of value without limitations or intermediaries.
+
+
diff --git a/collections/values/ppp_threefold.md b/collections/values/ppp_threefold.md
new file mode 100644
index 0000000..459c2c6
--- /dev/null
+++ b/collections/values/ppp_threefold.md
@@ -0,0 +1,5 @@
+
+{{#include ppp.md}}
+
+To learn more about ThreeFold read our litepaper on: [http://litepaper.threefold.me](http://litepaper.threefold.me).
+
diff --git a/collections/web4/architecture_highlevel/img/bad_internet_growth2.jpg b/collections/web4/architecture_highlevel/img/bad_internet_growth2.jpg
new file mode 100644
index 0000000..b311c34
Binary files /dev/null and b/collections/web4/architecture_highlevel/img/bad_internet_growth2.jpg differ
diff --git a/collections/web4/architecture_highlevel/img/blockchain_based_distr_computer.jpg b/collections/web4/architecture_highlevel/img/blockchain_based_distr_computer.jpg
new file mode 100644
index 0000000..0d5dc7f
Binary files /dev/null and b/collections/web4/architecture_highlevel/img/blockchain_based_distr_computer.jpg differ
diff --git a/collections/web4/architecture_highlevel/img/blockchain_is_clientserver.jpg b/collections/web4/architecture_highlevel/img/blockchain_is_clientserver.jpg
new file mode 100644
index 0000000..508b968
Binary files /dev/null and b/collections/web4/architecture_highlevel/img/blockchain_is_clientserver.jpg differ
diff --git a/collections/web4/architecture_highlevel/img/compare_3_parts.jpg b/collections/web4/architecture_highlevel/img/compare_3_parts.jpg
new file mode 100644
index 0000000..8e62f10
Binary files /dev/null and b/collections/web4/architecture_highlevel/img/compare_3_parts.jpg differ
diff --git a/collections/web4/architecture_highlevel/img/digital_twin_to_browser.jpg b/collections/web4/architecture_highlevel/img/digital_twin_to_browser.jpg
new file mode 100644
index 0000000..5d5e192
Binary files /dev/null and b/collections/web4/architecture_highlevel/img/digital_twin_to_browser.jpg differ
diff --git a/collections/web4/architecture_highlevel/img/digital_twin_to_browser_easy.jpg b/collections/web4/architecture_highlevel/img/digital_twin_to_browser_easy.jpg
new file mode 100644
index 0000000..0447ec4
Binary files /dev/null and b/collections/web4/architecture_highlevel/img/digital_twin_to_browser_easy.jpg differ
diff --git a/collections/web4/architecture_highlevel/img/everything_client_server.jpg b/collections/web4/architecture_highlevel/img/everything_client_server.jpg
new file mode 100644
index 0000000..89a4ed8
Binary files /dev/null and b/collections/web4/architecture_highlevel/img/everything_client_server.jpg differ
diff --git a/collections/web4/architecture_highlevel/img/executors_.jpg b/collections/web4/architecture_highlevel/img/executors_.jpg
new file mode 100644
index 0000000..e12122e
Binary files /dev/null and b/collections/web4/architecture_highlevel/img/executors_.jpg differ
diff --git a/collections/web4/architecture_highlevel/img/internet_evolution.jpg b/collections/web4/architecture_highlevel/img/internet_evolution.jpg
new file mode 100644
index 0000000..941b791
Binary files /dev/null and b/collections/web4/architecture_highlevel/img/internet_evolution.jpg differ
diff --git a/collections/web4/architecture_highlevel/img/nature_twin_.jpg b/collections/web4/architecture_highlevel/img/nature_twin_.jpg
new file mode 100644
index 0000000..53c056e
Binary files /dev/null and b/collections/web4/architecture_highlevel/img/nature_twin_.jpg differ
diff --git a/collections/web4/architecture_highlevel/img/power_generation.jpg b/collections/web4/architecture_highlevel/img/power_generation.jpg
new file mode 100644
index 0000000..020ab9e
Binary files /dev/null and b/collections/web4/architecture_highlevel/img/power_generation.jpg differ
diff --git a/collections/web4/architecture_highlevel/img/power_generator_comparison.jpg b/collections/web4/architecture_highlevel/img/power_generator_comparison.jpg
new file mode 100644
index 0000000..87c73e4
Binary files /dev/null and b/collections/web4/architecture_highlevel/img/power_generator_comparison.jpg differ
diff --git a/collections/web4/architecture_highlevel/img/storage_twin_.jpg b/collections/web4/architecture_highlevel/img/storage_twin_.jpg
new file mode 100644
index 0000000..4e30c91
Binary files /dev/null and b/collections/web4/architecture_highlevel/img/storage_twin_.jpg differ
diff --git a/collections/web4/architecture_highlevel/img/storage_web4_twin.png b/collections/web4/architecture_highlevel/img/storage_web4_twin.png
new file mode 100644
index 0000000..15ad966
Binary files /dev/null and b/collections/web4/architecture_highlevel/img/storage_web4_twin.png differ
diff --git a/collections/web4/architecture_highlevel/img/twin_capabilities_.jpg b/collections/web4/architecture_highlevel/img/twin_capabilities_.jpg
new file mode 100644
index 0000000..1dd9eff
Binary files /dev/null and b/collections/web4/architecture_highlevel/img/twin_capabilities_.jpg differ
diff --git a/collections/web4/architecture_highlevel/img/unlimited_3nodes.png b/collections/web4/architecture_highlevel/img/unlimited_3nodes.png
new file mode 100644
index 0000000..e1671c9
Binary files /dev/null and b/collections/web4/architecture_highlevel/img/unlimited_3nodes.png differ
diff --git a/collections/web4/architecture_highlevel/img/vlang_executors_.jpg b/collections/web4/architecture_highlevel/img/vlang_executors_.jpg
new file mode 100644
index 0000000..3f3a6a2
Binary files /dev/null and b/collections/web4/architecture_highlevel/img/vlang_executors_.jpg differ
diff --git a/collections/web4/architecture_highlevel/img/web2_integration_w4.png b/collections/web4/architecture_highlevel/img/web2_integration_w4.png
new file mode 100644
index 0000000..3b417ac
Binary files /dev/null and b/collections/web4/architecture_highlevel/img/web2_integration_w4.png differ
diff --git a/collections/web4/architecture_highlevel/img/web4_architecture_intro.png b/collections/web4/architecture_highlevel/img/web4_architecture_intro.png
new file mode 100644
index 0000000..4fb6321
Binary files /dev/null and b/collections/web4/architecture_highlevel/img/web4_architecture_intro.png differ
diff --git a/collections/web4/architecture_highlevel/img/web4_bc_link.png b/collections/web4/architecture_highlevel/img/web4_bc_link.png
new file mode 100644
index 0000000..6c73587
Binary files /dev/null and b/collections/web4/architecture_highlevel/img/web4_bc_link.png differ
diff --git a/collections/web4/architecture_highlevel/img/web_intro_0.png b/collections/web4/architecture_highlevel/img/web_intro_0.png
new file mode 100644
index 0000000..0b72f1a
Binary files /dev/null and b/collections/web4/architecture_highlevel/img/web_intro_0.png differ
diff --git a/collections/web4/architecture_highlevel/img/worldview_executors_.jpg b/collections/web4/architecture_highlevel/img/worldview_executors_.jpg
new file mode 100644
index 0000000..7d6d507
Binary files /dev/null and b/collections/web4/architecture_highlevel/img/worldview_executors_.jpg differ
diff --git a/collections/web4/architecture_highlevel/img/your_digital_twin.jpg b/collections/web4/architecture_highlevel/img/your_digital_twin.jpg
new file mode 100644
index 0000000..d9cbd4b
Binary files /dev/null and b/collections/web4/architecture_highlevel/img/your_digital_twin.jpg differ
diff --git a/collections/web4/architecture_highlevel/inspired_by_nature.md b/collections/web4/architecture_highlevel/inspired_by_nature.md
new file mode 100644
index 0000000..3d8b83c
--- /dev/null
+++ b/collections/web4/architecture_highlevel/inspired_by_nature.md
@@ -0,0 +1,28 @@
+
+# ThreeFold grid inspired by nature
+
+
+
+- Just like we have trillions of cells in our body, so can billions of twins live next to each other
+- Each twin has memory, knows how to communicate, has knowledge, history, ...
+- Twins like cells cannot live without a body = TFGrid.
+
+## This approach scales for ever
+
+
+
+- There can be unlimited amounts of 3Nodes as well as Executors (Digital Twins and Web4)
+- There are no bottlenecks nor centralization points
+- Our peer2peer network technology takes care of routing and security issues between the Twins and the 3Nodes. The shortest paths is always looked for.
+
+
+## ThreeFold is compatible with the current IT world.
+
+While we push for a new possible, in the meantime our TFGrid infrastructure is compatible with the existing IT and internet ecosystem.
+
+
+
+- any workload which can run inside linux can run on top of our TFGrid
+- any web developer can create apps (experiences) on top of the Digital Twin
+- just like kwatth is used as a measurement of capacity for solar panels we have [CU](tfgrid:cloudunits), [SU](tfgrid:cloudunits) and [NU](tfgrid:cloudunits), which are called cloudunits.
+- TFT is required to buy CU,SU,NU
\ No newline at end of file
diff --git a/collections/web4/architecture_highlevel/internet_evolution.md b/collections/web4/architecture_highlevel/internet_evolution.md
new file mode 100644
index 0000000..4532404
--- /dev/null
+++ b/collections/web4/architecture_highlevel/internet_evolution.md
@@ -0,0 +1,53 @@
+# Internet Evolution to Web 4.0
+
+### Classic Internet
+
+
+
+Everything is structured as client-server model
+
+
+
+- The servers run as applications inside huge datacenters using a lot of energy
+- Most of the processes in those servers are being repeated = highly inefficient
+- We exist 100x times, very inefficient
+- This leads to a lot of centralization -> insecure, as well as abuse of our data
+- This has also been called Web 1.0 and Web 2.0
+
+### Blockchain Based Web 3.0 Vision
+
+Blockchain decentralized the server, but in principle it remains a client - server model
+
+
+
+- It is definitely a step in the right direction but the paradigm is the same
+- We as users still exist in different systems, and have to deal with different applications (protocols)
+- These blockchains can be integrated, and through Web 2.0 concepts the web application can interact with multiple blockchains at the same time
+- This has also been called Web 3.0
+
+
+
+The browser has now become our operating system running on javascript. All applications run in our browser and interact with multiple blockchains.
+
+> Please note we are 100% compatible with Web3 and we support this way of working completely. We see ourselves as a missing layer for Web 3.0.
+
+### Evolution To Peer2Peer
+
+
+
+### The Web 4.0 Digital Twin Vision
+
+In the Web 4.0 vision, the user has been put in the center (digital twin usecase)
+
+
+
+- you in the center of your digital life
+- blockchain only needed for specific functions (money, identity, smart contracts, ...)
+- internet 10x more efficient
+- data sovereignity for all
+- an internet created by all for all = **be the internet**
+
+
+
+
+
diff --git a/collections/web4/architecture_highlevel/tfgrid_itenergy.md b/collections/web4/architecture_highlevel/tfgrid_itenergy.md
new file mode 100644
index 0000000..a8b15a4
--- /dev/null
+++ b/collections/web4/architecture_highlevel/tfgrid_itenergy.md
@@ -0,0 +1,19 @@
+
+## The ThreeFold Grid Provides the IT energy
+
+
+
+Each 3Node is an IT Power generator. The TFGrid is the network of these 3Nodes.
+
+
+
+Needs to be super simple, just like a solar panel generates electricity.
+
+
+
+- The 3nodes do for internet what solar panels do for large scale electricity power plants.
+- They allow everyone to contribute to a new internet.
+- People investing in the 3nodes are called [farmers](farming_home).
+- Each farmer receives tokens called TFT for providing this IT capacity.
+- IT Capacity is storage, compute and network capacity for this upgraded internet.
+- The Twins need TFT to pay for the IT capacity they need.
diff --git a/collections/web4/architecture_highlevel/web4_architecture_intro.md b/collections/web4/architecture_highlevel/web4_architecture_intro.md
new file mode 100644
index 0000000..768462d
--- /dev/null
+++ b/collections/web4/architecture_highlevel/web4_architecture_intro.md
@@ -0,0 +1 @@
+# What Is
diff --git a/collections/web4/architecture_highlevel/web4_digital_twin.md b/collections/web4/architecture_highlevel/web4_digital_twin.md
new file mode 100644
index 0000000..8e31b72
--- /dev/null
+++ b/collections/web4/architecture_highlevel/web4_digital_twin.md
@@ -0,0 +1,28 @@
+# Web 4.0 Digital Twin
+
+The ThreeFold web4 Digital Twin architecture puts the user in the center of its digital life, for that every user owns a digital twin running on the ThreeFold grid.
+
+
+
+Every user uses any browser to access their digital twin.
+
+### The twin has many capabilities:
+
+The twin has basic capabilities which are strongly version controlled, but contributions from the global community are more than welcome.
+
+
+
+### Experiences
+
+Developers create Experiences using the twin capabilities, not apps.
+
+Experiences re-use the same capabilities.
+
+This has huge benefits
+
+- a lot less development effort needed per experience
+- more sustainable (less energy loss)
+- easier for user, no duplication
+- more simplicy
+- more powerful
+
diff --git a/collections/web4/architecture_highlevel/web4_integration_web2.md b/collections/web4/architecture_highlevel/web4_integration_web2.md
new file mode 100644
index 0000000..d21c785
--- /dev/null
+++ b/collections/web4/architecture_highlevel/web4_integration_web2.md
@@ -0,0 +1,16 @@
+
+## Integration to Web 2
+
+Each Digital Twin can talk to the classic internet and web 2 interfaces.
+
+
+
+
+
+Each Twin knows how to talk legacy protocols like SMTP, POP3, DNS, ... (in development) to allow seamless integration.
+
+In case more compute is required for a specific usecase like gaming, AI, data processing the twin can spin up compute & storage requirements on the TFGrid and as such become way more powerful for the time required.
+
+This leads to huge flexibility and efficiency.
+
+Any application can be developed on top and is compatible with existing development world.
\ No newline at end of file
diff --git a/collections/web4/architecture_highlevel/web4_integration_web3.md b/collections/web4/architecture_highlevel/web4_integration_web3.md
new file mode 100644
index 0000000..fa15759
--- /dev/null
+++ b/collections/web4/architecture_highlevel/web4_integration_web3.md
@@ -0,0 +1,14 @@
+
+## Integration with blockchain (web 3)
+
+The twin integrates with web 3 or blockchain for the following functions:
+
+- money
+- smart contract between people
+- consensus between lots of people around info
+- proof of authority, authentication, ...
+- reputation system
+
+
+
+Each twin can talk to any required blockchain in a way that is 100% transparent for the user.
diff --git a/collections/web4/architecture_highlevel/web4_intro.md b/collections/web4/architecture_highlevel/web4_intro.md
new file mode 100644
index 0000000..4a59f0a
--- /dev/null
+++ b/collections/web4/architecture_highlevel/web4_intro.md
@@ -0,0 +1,4 @@
+
+# Web 4 Intro
+
+{{#include web4_intro_.md}}
\ No newline at end of file
diff --git a/collections/web4/architecture_highlevel/web4_intro_.md b/collections/web4/architecture_highlevel/web4_intro_.md
new file mode 100644
index 0000000..3e36430
--- /dev/null
+++ b/collections/web4/architecture_highlevel/web4_intro_.md
@@ -0,0 +1,21 @@
+
+
+
+Web 4 is a new concept which is the combination of Web 3 (blockchain) and digital twin technology.
+
+Its a concept with many advantages like
+
+- less power usage
+- more scalability
+- more flexibility
+- faster development
+- more security
+
+### Architecture Intro
+
+
+
+**Specific for storage, there are some cool features:**
+
+Each twin has its own storage system where data cannot be lost or corrupted. Each twin decides for itself where the data will be stored.
+
diff --git a/collections/web4/architecture_highlevel/web4_intro_generic.md b/collections/web4/architecture_highlevel/web4_intro_generic.md
new file mode 100644
index 0000000..0d24752
--- /dev/null
+++ b/collections/web4/architecture_highlevel/web4_intro_generic.md
@@ -0,0 +1,4 @@
+
+# Modern Digital Backbone Architecture
+
+{{#include web4_intro_.md}}
\ No newline at end of file
diff --git a/collections/web4/architecture_highlevel/web4_storage_architecture.md b/collections/web4/architecture_highlevel/web4_storage_architecture.md
new file mode 100644
index 0000000..4891b6f
--- /dev/null
+++ b/collections/web4/architecture_highlevel/web4_storage_architecture.md
@@ -0,0 +1,13 @@
+## Web 4 unique storage architecture
+
+
+
+Each Digital Twin can now store data which can never be lost or corrupted.
+
+- This is not based on replication or blockchain!
+- Data is distributed over multiple 3nodes in such a way that not even a quantum computer can hack it.
+- The data is 100% owned by the owner and zero-knowledge proof to the the TFGrid.
+- This concept scales unlimited.
+
+
+
diff --git a/collections/web4/executor/executor_terraform.md b/collections/web4/executor/executor_terraform.md
new file mode 100644
index 0000000..3217bf3
--- /dev/null
+++ b/collections/web4/executor/executor_terraform.md
@@ -0,0 +1,22 @@
+## Executor TERRAFORM
+
+> Terraform is a mechanism on how to deploy IT workloads in a reproducible and safe way.
+
+
+
+A terraform script has multiple parts and can get deployed by an executor.
+
+
+
+See the ThreeFold Technology book to learn more about how to use smarts contracts for IT and deploy any workload.
+
+### Consensus Owned & Deployed Solutions
+
+
+
+
+
+
+> Coming H1 2023
\ No newline at end of file
diff --git a/collections/web4/executor/executor_vlang.md b/collections/web4/executor/executor_vlang.md
new file mode 100644
index 0000000..c766dfc
--- /dev/null
+++ b/collections/web4/executor/executor_vlang.md
@@ -0,0 +1,19 @@
+# Executor VLANG
+
+
+
+VLang is an exciting language sponsored by ThreeFold. VLang has 27000 github stars and we believe its a very good language to build executor functions with.
+
+Why did we choose vlang as a first language to support on the TF Executors?
+
+- Its a very fast language (minimal energy & cpu footprint)
+- Its easy to learn
+- It compiles very fast
+
+
+
+### Utilization
+
+- As smart contract language inside chosen blockchain
+- As provisioning layer for TFGrid
+- As serverless function layer for Executors (super exciting)
diff --git a/collections/web4/executor/executors_peer2peer.md b/collections/web4/executor/executors_peer2peer.md
new file mode 100644
index 0000000..82c15f6
--- /dev/null
+++ b/collections/web4/executor/executors_peer2peer.md
@@ -0,0 +1,12 @@
+
+## From Client Server to Peer2Peer
+
+
+
+Peer2peer is the most decentralized way to experience our digital life.
+
+- all executors talk to each other over private secure links
+- there is no blockchain involved for the compute, storage & network requirements.
+- each executor needs compute, network and storage resources this is managed by L0 Validators.
+- The executor (web4 or twin) is the only entity who has control over the resource it requires, its all 100% private and fully peer2peer.
+
\ No newline at end of file
diff --git a/collections/web4/executor/executors_usecases.md b/collections/web4/executor/executors_usecases.md
new file mode 100644
index 0000000..b048b61
--- /dev/null
+++ b/collections/web4/executor/executors_usecases.md
@@ -0,0 +1,9 @@
+## 3 INITIAL USECASES FOR EXECUTORS
+
+- IPFS
+ - distributed storage location service
+ - we add: reliability, locality, cost effectiveness, …
+- TERRAFORM EXECUTORS
+ - Smart contract for IT
+- WEBGATEWAY
+ - Bridge web protocols to internal compute workloads
diff --git a/collections/web4/executor/img/consensus_deployed_.jpg b/collections/web4/executor/img/consensus_deployed_.jpg
new file mode 100644
index 0000000..5bf1334
Binary files /dev/null and b/collections/web4/executor/img/consensus_deployed_.jpg differ
diff --git a/collections/web4/executor/img/executor_arch1_.jpg b/collections/web4/executor/img/executor_arch1_.jpg
new file mode 100644
index 0000000..291518a
Binary files /dev/null and b/collections/web4/executor/img/executor_arch1_.jpg differ
diff --git a/collections/web4/executor/img/peer2peer_executors_.jpg b/collections/web4/executor/img/peer2peer_executors_.jpg
new file mode 100644
index 0000000..73651a2
Binary files /dev/null and b/collections/web4/executor/img/peer2peer_executors_.jpg differ
diff --git a/collections/web4/executor/img/storage_layer_ipfs_.jpg b/collections/web4/executor/img/storage_layer_ipfs_.jpg
new file mode 100644
index 0000000..9fa12cf
Binary files /dev/null and b/collections/web4/executor/img/storage_layer_ipfs_.jpg differ
diff --git a/collections/web4/executor/img/terraform_iac2_.jpg b/collections/web4/executor/img/terraform_iac2_.jpg
new file mode 100644
index 0000000..b47d875
Binary files /dev/null and b/collections/web4/executor/img/terraform_iac2_.jpg differ
diff --git a/collections/web4/executor/img/terraform_iac_.jpg b/collections/web4/executor/img/terraform_iac_.jpg
new file mode 100644
index 0000000..5d30b04
Binary files /dev/null and b/collections/web4/executor/img/terraform_iac_.jpg differ
diff --git a/collections/web4/executor/img/terraform_pokt_.jpg b/collections/web4/executor/img/terraform_pokt_.jpg
new file mode 100644
index 0000000..2fe8d12
Binary files /dev/null and b/collections/web4/executor/img/terraform_pokt_.jpg differ
diff --git a/collections/web4/executor/img/vlang.png b/collections/web4/executor/img/vlang.png
new file mode 100644
index 0000000..b6e7898
Binary files /dev/null and b/collections/web4/executor/img/vlang.png differ
diff --git a/collections/web4/executor/img/vlang_executors_.jpg b/collections/web4/executor/img/vlang_executors_.jpg
new file mode 100644
index 0000000..3f3a6a2
Binary files /dev/null and b/collections/web4/executor/img/vlang_executors_.jpg differ
diff --git a/collections/web4/executor/storage_ipfs.md b/collections/web4/executor/storage_ipfs.md
new file mode 100644
index 0000000..1562b2f
--- /dev/null
+++ b/collections/web4/executor/storage_ipfs.md
@@ -0,0 +1,15 @@
+## IPFS storage integration on Web4
+
+> IPFS is a standard used in the blockchain world on how to store and retrieve data from the blockchain.
+
+
+
+Each executor in the form of Web4 or twin is compatible with IPFS.
+
+Each IPFS object can be safely stored on QSSS.
+
+This provides the following unique Features
+
+- unbreakable storage for IPFS
+- more distribution on global scale
+- more performance for the enduser
diff --git a/collections/web4/executor/web4_executors.md b/collections/web4/executor/web4_executors.md
new file mode 100644
index 0000000..0d46409
--- /dev/null
+++ b/collections/web4/executor/web4_executors.md
@@ -0,0 +1,16 @@
+
+# ThreeFold executors
+
+Executors are like digital twins but they are not linked to one specific person, they are stateless and can work on our behalf for any specific usecase and/or any pre-implemented. Some would call it our approach to serverless functions.
+
+
+
+Peer2peer is the most decentralized way to experience our digital life.
+
+- all executors talk to each other over private secure links
+- there is no blockchain involved for the compute, storage & network requirements
+- each executor needs compute, network and storage resources, this is managed by L0 Validators
+- The executor (web4 or twin) is the only entity who has control over the resource it requires, its all 100% private and fully peer2peer
+
+
+
\ No newline at end of file
diff --git a/collections/web4/features/features.md b/collections/web4/features/features.md
new file mode 100644
index 0000000..cf3022c
--- /dev/null
+++ b/collections/web4/features/features.md
@@ -0,0 +1,3 @@
+# Digital Backbone Features
+
+
diff --git a/collections/web4/features/img/anywebapp_on_top.png b/collections/web4/features/img/anywebapp_on_top.png
new file mode 100644
index 0000000..6c86da0
Binary files /dev/null and b/collections/web4/features/img/anywebapp_on_top.png differ
diff --git a/collections/web4/features/img/develop_anything_on_op.png b/collections/web4/features/img/develop_anything_on_op.png
new file mode 100644
index 0000000..299d38c
Binary files /dev/null and b/collections/web4/features/img/develop_anything_on_op.png differ
diff --git a/collections/web4/features/img/peer2peer_new.jpg b/collections/web4/features/img/peer2peer_new.jpg
new file mode 100644
index 0000000..a8e3f90
Binary files /dev/null and b/collections/web4/features/img/peer2peer_new.jpg differ
diff --git a/collections/web4/features/img/storage_web4_twin.png b/collections/web4/features/img/storage_web4_twin.png
new file mode 100644
index 0000000..15ad966
Binary files /dev/null and b/collections/web4/features/img/storage_web4_twin.png differ
diff --git a/collections/web4/features/img/unbreakable_deployment.png b/collections/web4/features/img/unbreakable_deployment.png
new file mode 100644
index 0000000..eb31068
Binary files /dev/null and b/collections/web4/features/img/unbreakable_deployment.png differ
diff --git a/collections/web4/features/unbreakable_deployment.md b/collections/web4/features/unbreakable_deployment.md
new file mode 100644
index 0000000..45ffe64
--- /dev/null
+++ b/collections/web4/features/unbreakable_deployment.md
@@ -0,0 +1,28 @@
+## Unbreakable Deployment
+
+
+
+Ultra Scalable & Secure Decentralized Deployment
+
+**Example deployment**
+
+* lots of locations (offices, banks, small datacenters, universities, ...), each providing compute & storage to a private and/or public grid by means of the 3Nodes
+* Each node runs Zero-OS which has no shell and cannot be accessed by any person in the organization (bank, government, enterprise)
+* None of the nodes has enough data to allow anyone to reconstruct the data
+* The different nodes together deliver a super resilient network of compute & network resources
+
+**Even if, in a disaster scenario, 30% of the locations would go down, the system would still function and be available to its users. This is the most reliable deployment possible in IT landscape today.**
+
+What runs on the 3Nodes
+
+* Blockchain Nodes
+* The distributed storage system (ultra safe, zero-knowledge proof)
+* Digital Twins for users
+* Secure Browser Engines (can be in ultra safe location)
+* Stateless high security (e.g. financial) apps
+
+This can then be combined with super nodes running in even more secure places for more central apps if there are any.
+
+This system works with and enables the planetary network and quantum safe storage system.
+
+
diff --git a/collections/web4/features/unbreakable_storage.md b/collections/web4/features/unbreakable_storage.md
new file mode 100644
index 0000000..714af9c
--- /dev/null
+++ b/collections/web4/features/unbreakable_storage.md
@@ -0,0 +1 @@
+{{#include ../architecture_highlevel/web4_storage_architecture.md}}
\ No newline at end of file
diff --git a/collections/web4/features/unlimited_scaleout.md b/collections/web4/features/unlimited_scaleout.md
new file mode 100644
index 0000000..9061910
--- /dev/null
+++ b/collections/web4/features/unlimited_scaleout.md
@@ -0,0 +1,14 @@
+
+## Ultimate Scale Out Capabilities
+
+Peer2peer is the most decentralized way to experience our digital life
+
+
+
+- each user has a digital twin
+- this twin serves your complete digital life
+- the digital twin represents you and has all logic required to act on your behalf
+- all digital twins talk to each other over private secure links
+- there is no blockchain involved for the compute, storage & network requirements
+- each digital twin needs compute, network and storage resources to survive, the twin will use TFT to reserve and pay for these resources as used on the ThreeFold Grid
+- The twin is the only entity who has control over the resources it requires, it is all 100% private and no blockchain involved to reserve and use that capacity
\ No newline at end of file
diff --git a/collections/web4/features/web4_develop_anything.md b/collections/web4/features/web4_develop_anything.md
new file mode 100644
index 0000000..4572ea7
--- /dev/null
+++ b/collections/web4/features/web4_develop_anything.md
@@ -0,0 +1,13 @@
+
+## Develop any application on top of Web4
+
+
+
+Developers can program anything on top on a digital twin. Any javascript framework can be used.
+
+This allows ANYONE to create ANY experience with the least amount of effort.
+
+This approach seamlessly integrates with any Web 3 or Blockchain Solutions.
+
+
+
diff --git a/collections/web4/features/web4_goals.md b/collections/web4/features/web4_goals.md
new file mode 100644
index 0000000..ea4245b
--- /dev/null
+++ b/collections/web4/features/web4_goals.md
@@ -0,0 +1,21 @@
+# Web 4 Goals
+
+- 10x faster development efficiency should be possible
+ - One Language to do all (smart contract, backend, frontend, logic …)
+ - Easy to read & learn (few ways how to do things)
+ - Leads to less security issues and lower maintenance cost
+- Resolve the onion issue
+ - Solutions grow exponentially in complexity as they grow, Web 4 resolves this
+- No Painkiller Approach (resolve the root of the problem)
+ - Governments or Large Enterprises want one digital backbone system to resolve all their needs
+ -Today they have too many systems and it's too complex, expensive and not secure
+- Ultimate Scale
+ - We want to be able to grow to billions of users, our system is 100% scale out
+ - Our smart contract for IT allows deployment of any web 2,3 and 4 workload everywhere
+- Ultimate Sovereignity
+ - Governments want all data in the country and their independence
+- Antidote for the Cyber Pandemic
+ - This is a very hard one, the current architectures are very vulnerable
+ - The ThreeFold architecture allows for a real end2end solution
+ - We have e.g. browser virtualization technology (run no javascript in existing browsers)
+
diff --git a/collections/web4/finance/defi_p2p_exchange.md b/collections/web4/finance/defi_p2p_exchange.md
new file mode 100644
index 0000000..607c55f
--- /dev/null
+++ b/collections/web4/finance/defi_p2p_exchange.md
@@ -0,0 +1,10 @@
+# DeFi and Peer To Peer Exchange
+
+
+
+
+DeFi is an amazing trend which banks should try to leverage, if not for internal usage, to provide a more transparent and safer way for their customers to exchange their currencies (digital and fiat) in a fully regulated environment.
+
+We have all the building blocks available to make this work.
+
+Thanks to the digital twin this is implemented in a fully peer2peer way, while using DeFi Smart Contracts on the blockchain.
\ No newline at end of file
diff --git a/collections/web4/finance/digitial_currency_wrapping.md b/collections/web4/finance/digitial_currency_wrapping.md
new file mode 100644
index 0000000..1b25499
--- /dev/null
+++ b/collections/web4/finance/digitial_currency_wrapping.md
@@ -0,0 +1,16 @@
+# Digital Currency Wrapping
+
+
+
+
+In Addition to allowing a user to directly integrate with an outside digital currency, we also suggest allowing wrapping of the outside currencies e.g. a wrapped BitCoin (BTC).
+
+This Wrapped BTC is then stored on the main or dedicated digital currency chain (can even be one chain per wrapped asset). The IBC (see below) allows the wrapped BTC to be used by the user from their wallet and digital twin.
+
+The Original BTC is stored offline in the Knox Security Vault using our Quantum Safe Storage Codec. This allows for ultimate security and flexibility for users.
+
+The bank can choose to allow users to exchange digital currencies with the external world or not, through IBC (Inter Blockchain Protocol, see below), this can be easily achieved. The bank can even choose to become a liquidity provider for the existing digital currency world (optional).
+
+Revolut, for example, has chosen to keep the digital currencies in their internal system, and the user can only exchange from their own fiat currency to the digital currency and back. We believe though that it's nicer to allow the user to exchange digital currencies with the outside world if it matches the Bank’s Regulatory requirements.
+
+It is possible to introduce multiple stages e.g. in the digital bank ecosystem, users can freely exchange currencies with each other (stays on chain). Once they want to go off chain, extra checks are done to make sure there is no fraud involved, it can then take a certain time before it executes.
\ No newline at end of file
diff --git a/collections/web4/finance/finance.md b/collections/web4/finance/finance.md
new file mode 100644
index 0000000..8b13789
--- /dev/null
+++ b/collections/web4/finance/finance.md
@@ -0,0 +1 @@
+
diff --git a/collections/web4/finance/img/cryptocurrency.png b/collections/web4/finance/img/cryptocurrency.png
new file mode 100644
index 0000000..e7af659
Binary files /dev/null and b/collections/web4/finance/img/cryptocurrency.png differ
diff --git a/collections/web4/finance/img/defi_exchange.png b/collections/web4/finance/img/defi_exchange.png
new file mode 100644
index 0000000..7988521
Binary files /dev/null and b/collections/web4/finance/img/defi_exchange.png differ
diff --git a/collections/web4/finance/img/distributed_storage.png b/collections/web4/finance/img/distributed_storage.png
new file mode 100644
index 0000000..46fcd6e
Binary files /dev/null and b/collections/web4/finance/img/distributed_storage.png differ
diff --git a/collections/web4/finance/img/security_vault.png b/collections/web4/finance/img/security_vault.png
new file mode 100644
index 0000000..55a0d2c
Binary files /dev/null and b/collections/web4/finance/img/security_vault.png differ
diff --git a/collections/web4/finance/knox_security_vault.md b/collections/web4/finance/knox_security_vault.md
new file mode 100644
index 0000000..20ceb52
--- /dev/null
+++ b/collections/web4/finance/knox_security_vault.md
@@ -0,0 +1,14 @@
+# Knox Security Vault
+
+
+
+
+The ability to use multiple secure areas which can be used to provide offline storage of keys and digital currency cold wallets.
+
+
+
+
+
+Each Knox Security Vault is an ultra safe area. Thanks to our Quantum Safe Storage system, it is not possible to retrieve a key even if a hacker would be in one safe, as a combination of three safes is required to recover information.
+
+We suggest using the key storage in the following way: each wallet from a user stores the encrypted dispersed key distributed over four or five Knox Security Vaults. Only in the case of a disaster and user strong identification, an user could get access (in the case of death of the customer, to hand-over to the relatives).
\ No newline at end of file
diff --git a/collections/web4/finance/p2p_reputation_system.md b/collections/web4/finance/p2p_reputation_system.md
new file mode 100644
index 0000000..5bdde29
--- /dev/null
+++ b/collections/web4/finance/p2p_reputation_system.md
@@ -0,0 +1,9 @@
+# Peer2Peer Reputation System
+
+Reputation is a very important part to any financial system. This allows users to see the reputation of the people they are transacting or doing business with.
+
+We are developing a unique peer2peer reputation system to allow the power of network effects to come up with strong verification and reputation proofs. We think this might become an important added value that any financial institution government could deliver to its customers/citizens.
+
+Such a system can easily be integrated and extended by a standard KYC and AML system.
+
+This goes had in had with the Proof of Authenticity system.
diff --git a/collections/web4/finance/proof_of_authenticity.md b/collections/web4/finance/proof_of_authenticity.md
new file mode 100644
index 0000000..35d2aa7
--- /dev/null
+++ b/collections/web4/finance/proof_of_authenticity.md
@@ -0,0 +1,36 @@
+# Proof of Authenticity
+
+Proof of Authenticity (PoA) is an algorithm that allows peers to verify that people, products and statements on the ThreeFold Grid are genuine. It acts as a reputation engine to validate any information on the grid.
+
+## Why Proof of Authenticity
+
+Any system that contains a vast amount of information, should require proof of authenticity.
+
+We believe users should be able to measure authenticity in relation to
+
+- The people they connect with;
+- The products and services they access;
+- The information they consume.
+
+Therefore, to automate information search in a decentralized and trustful environemnt, an algorithm that is able to scale information verification in a neutral way is required.
+
+Proof of authenticity puts forward a very simple method to verify the genuiness of information.
+
+Here's an example of how PoA works in a decentralized context:
+
+- Someone fills in their profile with their personal and professional data.
+- A former colleague finds their information and verifies their information as being authentic.
+- Once a user gets verified e.g. 10 times, they can be trusted to be real and genuine.
+
+The above can also apply to products, statements and more. In that sense, PoA can solve multiple digital challenges such as:
+
+- The verifiability of information and news
+- A non-biased way to rate products and services.
+- website authenticity
+- etc.
+
+## Applicability
+
+POA can be used for any type of information but one of the first ones is identity, KYC/AML is a mechanism to identify people but peer authentication is a very powerful way to extend this with.
+
+
diff --git a/collections/web4/introduction.md b/collections/web4/introduction.md
new file mode 100644
index 0000000..fcf3dfa
--- /dev/null
+++ b/collections/web4/introduction.md
@@ -0,0 +1 @@
+# WEB 4
diff --git a/collections/web4/network/img/planetary_network.png b/collections/web4/network/img/planetary_network.png
new file mode 100644
index 0000000..437f13e
Binary files /dev/null and b/collections/web4/network/img/planetary_network.png differ
diff --git a/collections/web4/network/img/traditional_threefold_comparison.png b/collections/web4/network/img/traditional_threefold_comparison.png
new file mode 100644
index 0000000..452a91d
Binary files /dev/null and b/collections/web4/network/img/traditional_threefold_comparison.png differ
diff --git a/collections/web4/network/planetary_network.md b/collections/web4/network/planetary_network.md
new file mode 100644
index 0000000..b4e03bb
--- /dev/null
+++ b/collections/web4/network/planetary_network.md
@@ -0,0 +1,13 @@
+# Planetary network
+
+
+
+
+The planetary network leads to serious benefits in scalability, reliability and security:
+
+
+
+
+
+
+##
\ No newline at end of file
diff --git a/collections/web4/ourledger/architecture.md b/collections/web4/ourledger/architecture.md
new file mode 100644
index 0000000..14171ff
--- /dev/null
+++ b/collections/web4/ourledger/architecture.md
@@ -0,0 +1 @@
+# OurLedger
diff --git a/collections/web4/ourledger/blockchain_pruning.md b/collections/web4/ourledger/blockchain_pruning.md
new file mode 100644
index 0000000..01e4752
--- /dev/null
+++ b/collections/web4/ourledger/blockchain_pruning.md
@@ -0,0 +1,7 @@
+# Blockchain Pruning
+
+
+
+Existing blockchains don’t have a pruning feature, which means old data cannot get archived, this leads to very large blockchains rather quickly. We have developed a technology which can enable any chosen blockchain and allow old data to be parked on the Quantum Safe Storage system (means can never be corrupted or lost). It means only active data remain on the online chain, this allows for much more scalability and better utilization of the hardware.
+
+To do effective pruning we need to modify parts of the chosen blockchain, but we know how to do this.
\ No newline at end of file
diff --git a/collections/web4/ourledger/img/consensus_subsystem.png b/collections/web4/ourledger/img/consensus_subsystem.png
new file mode 100644
index 0000000..199b07e
Binary files /dev/null and b/collections/web4/ourledger/img/consensus_subsystem.png differ
diff --git a/collections/web4/ourledger/img/digital_twin_executor.png b/collections/web4/ourledger/img/digital_twin_executor.png
new file mode 100644
index 0000000..7483a34
Binary files /dev/null and b/collections/web4/ourledger/img/digital_twin_executor.png differ
diff --git a/collections/web4/ourledger/img/pruning.png b/collections/web4/ourledger/img/pruning.png
new file mode 100644
index 0000000..0b7be19
Binary files /dev/null and b/collections/web4/ourledger/img/pruning.png differ
diff --git a/collections/web4/ourledger/img/web_remade_twin.png b/collections/web4/ourledger/img/web_remade_twin.png
new file mode 100644
index 0000000..e25eb33
Binary files /dev/null and b/collections/web4/ourledger/img/web_remade_twin.png differ
diff --git a/collections/web4/ourledger/legacy_blockchain_compatability.md b/collections/web4/ourledger/legacy_blockchain_compatability.md
new file mode 100644
index 0000000..44e4341
--- /dev/null
+++ b/collections/web4/ourledger/legacy_blockchain_compatability.md
@@ -0,0 +1,12 @@
+# Compatible with Blockchain & Legacy Systems
+
+
+
+
+The Twins can connect to any blockchain solutions, theey are close to the twins which are on safe locations where full blockchain nodes are deployed, this leads to even more security. In other words, it's not the browser of the user who connects to the blockchain, the browser of the user connects over the Browser Firewall to the apps running on the twin which connects the blockchain. Hackers have no possibility to abuse javascript or browser vulnerabilities.
+
+
+
+
+
+This is also compatible with any other classic IT system running behind firewalls in protected environments. The Twins can connect to any possible IT system, blockchain or classic in an ultra secure setting.
\ No newline at end of file
diff --git a/collections/web4/ourledger/ourledger.md b/collections/web4/ourledger/ourledger.md
new file mode 100644
index 0000000..0e28388
--- /dev/null
+++ b/collections/web4/ourledger/ourledger.md
@@ -0,0 +1,43 @@
+# OurLedger
+
+OurLedger is the base consensus layer to develop any business or government solution on top of.
+
+
+
+Multiple VLang engines become the validators of this system. Each VLang engine runs smart contract code and will integrate with the blockchain through the consensus layer.
+
+Only once the consensus is achieved, the result of the code will result in change in the real world (e.g. a blockchain), this allows for a lot of flexibility.
+
+The blockchain is needed to support authentication, money transactions, multi signature, auditing records, ...
+
+This approach is designed to be compatible with all existing blockchain technologies, although some are more efficient than others.
+
+### Benefits
+
+- order of magnitude faster development
+- Integrates with everything, easy to extend
+- 100% sovereign (can be deployed anywhere)
+- Unlimited Scalable, uses Quantum Safe Storage System
+- Works with unlimited amount of blockchains and over all protocols
+- Super safe, only needs the most basic functionalities from a blockchain
+- No limite in what can be created
+- Actor based
+
+
+### The developer has unified DSL for
+
+- Blockchain
+- NFT
+- Money
+- Identity
+- Consensus
+- Ledger
+- Internet Protocols
+- SMS, Mail, Chat…
+- Deployment of Web 2 and 3 workloads
+
+A DSL can be created for everything.
+
+DSL stands for Domain Specific Language.
+
+
diff --git a/collections/web4/security/browser_firewall.md b/collections/web4/security/browser_firewall.md
new file mode 100644
index 0000000..cff6778
--- /dev/null
+++ b/collections/web4/security/browser_firewall.md
@@ -0,0 +1,24 @@
+## Secure Access Mechanism = Browser Firewall
+
+
+
+
+For ultra secure use cases, the user doesn't use javascript in his browser, he connects over an ultra secure end2end encrypted and multi authenticated link from his browser to a secure location. In the secure location, the secure browser engine gives access to the required web and banking applications which connect further.
+
+
+
+
+
+As an option, the web sessions can be recorded for auditing or anti-hacking/fraud detection, also in a secure location.
+
+The twin can communicate with other twins, in a close ultra secure context, giving no chance to hackers to interfere. The data is stored on a Quantum Safe Storage system (see further).
+
+
+
+
+
+This leads to very good protection and ‘Auditing’ opportunities.
+
+Cyber crime will have a much harder time to be successful, way more difficult (we hope impossible).
+
+Even in the very unlikely event a hacker would succeed, he would only interfere with one twin, which means only one customer would be affected!!! This makes it so much harder for hackers to deploy capital to hack and social engineer their way into a secure environment.
diff --git a/collections/web4/security/img/browser_firewall.png b/collections/web4/security/img/browser_firewall.png
new file mode 100644
index 0000000..817efa3
Binary files /dev/null and b/collections/web4/security/img/browser_firewall.png differ
diff --git a/collections/web4/security/img/cyber_security.png b/collections/web4/security/img/cyber_security.png
new file mode 100644
index 0000000..fae71de
Binary files /dev/null and b/collections/web4/security/img/cyber_security.png differ
diff --git a/collections/web4/security/img/twin_functions.png b/collections/web4/security/img/twin_functions.png
new file mode 100644
index 0000000..68372e6
Binary files /dev/null and b/collections/web4/security/img/twin_functions.png differ
diff --git a/collections/web4/security/security.md b/collections/web4/security/security.md
new file mode 100644
index 0000000..a7abb2e
--- /dev/null
+++ b/collections/web4/security/security.md
@@ -0,0 +1,3 @@
+# Security
+
+Security is a super important element of our Solution.
\ No newline at end of file
diff --git a/collections/web4/storage/img/qss_twin.png b/collections/web4/storage/img/qss_twin.png
new file mode 100644
index 0000000..1a0c296
Binary files /dev/null and b/collections/web4/storage/img/qss_twin.png differ
diff --git a/collections/web4/storage/img/quantum_safe_storage.png b/collections/web4/storage/img/quantum_safe_storage.png
new file mode 100644
index 0000000..a0e9949
Binary files /dev/null and b/collections/web4/storage/img/quantum_safe_storage.png differ
diff --git a/collections/web4/storage/qss_twin.md b/collections/web4/storage/qss_twin.md
new file mode 100644
index 0000000..cea1cf8
--- /dev/null
+++ b/collections/web4/storage/qss_twin.md
@@ -0,0 +1,29 @@
+# Quantum Safe Twin Storage System
+
+
+
+
+Each Twin or Executor stores the data on a quantum safe filesystem, which means data can never be lost, any application just sees a normal filesystem so it's compatible with any application.
+
+This is an ultra scalable design, there are no limits to the size which can be achieved.
+
+This is a ‘zero knowledge’ proof system which means that, once the data leaves the twin it is impossible for any hacker or even quantum computer to get access or to modify the data, there is simply not enough information available.
+
+A redundant filesystem can store PB’s (millions of gigabytes) of information.
+
+Unique features:
+
+* Unlimited scalable (many petabytes) filesystem
+* Quantum Safe: even if used on the ThreeFold Grid, no farmer knows what the data is about
+* Even a quantum computer cannot decrypt
+* Data can’t be lost
+* Protection for datarot, data will auto repair
+* Data is kept forever
+* Data is dispersed over multiple sites
+* Sites can go down, data not lost
+* Up to 10x more efficient than storing on classic storage cloud systems
+* Can be mounted as a filesystem on any OS or any deployment system (OSX, Linux, Windows, Docker, Kubernetes, ThreeFold Grid, …)
+* Compatible with ± all data workloads (not high performance data driven workloads like a database)
+* Self-healing: when a node or disk is lost, storage system can get back to the original redundancy level
+* Helps with compliance to regulations like GDPR (as the hosting facility has no view on what is stored, information is encrypted and incomplete)
+* Hybrid: can be installed onsite, public, private, …
\ No newline at end of file
diff --git a/collections/web4/storage/quantum_safe_storage.md b/collections/web4/storage/quantum_safe_storage.md
new file mode 100644
index 0000000..9c11a43
--- /dev/null
+++ b/collections/web4/storage/quantum_safe_storage.md
@@ -0,0 +1,19 @@
+# Quantum Safe Storage
+
+
+
+Imagine a storage system with the following benefits:
+
+* upto 10x more efficient (power and usage of hardware)
+* ultra reliable, data can not be lost
+* ultra safe & private
+* ultra scalable
+* sovereign, data is close to you in the country of your choice
+* true Peer To Peer, by everyone for everyone.
+
+It is not a dream, it does already exist, and is the underpinning of the ultra safe **Cloud & Internet Backend System** empowering this solution.
+
+ Our storage architecture follows the true Peer To Peer design. Any participating nodes (can be on ultra safe locations) only store small incomplete parts of data (files, photos, movies, databases…) by only offering a slice of their current (local) storage devices. Managing the storage and retrieval of all these ‘distributed fragments’ is done by a software that creates ‘development and/or end-user interfaces’ for this storage algorithm. We call this ‘dispersed storage‘.
+
+
+
diff --git a/collections/web4/vlang/img/v_programming_language.png b/collections/web4/vlang/img/v_programming_language.png
new file mode 100644
index 0000000..3207a05
Binary files /dev/null and b/collections/web4/vlang/img/v_programming_language.png differ
diff --git a/collections/web4/vlang/vlang_dev.md b/collections/web4/vlang/vlang_dev.md
new file mode 100644
index 0000000..cc2975a
--- /dev/null
+++ b/collections/web4/vlang/vlang_dev.md
@@ -0,0 +1,28 @@
+# VLANG Powerful Development Environment
+
+ThreeFold is the main sponsor behind vlang
+
+
+
+Vlang is a language heavily inspired by google’s GOLANG but faster and more friendly with resources. It's also a language much easier to understand and code in. This language has 28.000 github stars which is +25% of google itself for golang, this shows the potential.
+
+We use VLANG for
+
+* Digital twin backend (the main language for our digital life)
+* Provisioning language for Threefold Grid (in progress)
+* Language integrated with our chosen blockchain Algorand (we are close to having a full VLang compatible SDK for Algorand as well as VTeal smart contract language, this will be the easiest way to integrate and develop on top of Algorand)
+* Dynamic Executor Language (fastest way to develop peer2peer on top of ThreeFold Grid).
+
+This Dynamic Executor Language is used in
+ * Digital Twin
+ * BCDB = BlockChain Database
+ * ThreeFold Grid Executors (serverless functions & compatibility layer for old internet)
+
+This approach allows us maximum productivity and minimal resources utilization which leads to much more power and hardware efficient design.
+
+Our approach is
+
+* Ultimate simplicity (do more with less)
+* Easy to read code (DSL = Domain Specific Languages)
+* Ultra reliable communication thanks to RMB (Reliable Message Bus)
+* Safety, only support one best way how to do something
diff --git a/collections/web4/zos/cloud_layer.md b/collections/web4/zos/cloud_layer.md
new file mode 100644
index 0000000..c47298b
--- /dev/null
+++ b/collections/web4/zos/cloud_layer.md
@@ -0,0 +1,7 @@
+# Cloud Layer
+
+
+
+To allow web4 to work we need a reliable cloud layer, which is a layer capable to execute all workloads as described in this document in a safe and a reliable way.
+
+
diff --git a/collections/web4/zos/img/cloudlayer.png b/collections/web4/zos/img/cloudlayer.png
new file mode 100644
index 0000000..ac2380e
Binary files /dev/null and b/collections/web4/zos/img/cloudlayer.png differ
diff --git a/collections/web4/zos/img/zero_os.png b/collections/web4/zos/img/zero_os.png
new file mode 100644
index 0000000..b046858
Binary files /dev/null and b/collections/web4/zos/img/zero_os.png differ
diff --git a/collections/web4/zos/img/zero_os_server.png b/collections/web4/zos/img/zero_os_server.png
new file mode 100644
index 0000000..95f5e83
Binary files /dev/null and b/collections/web4/zos/img/zero_os_server.png differ
diff --git a/collections/web4/zos/zero_os.md b/collections/web4/zos/zero_os.md
new file mode 100644
index 0000000..a7ae1fd
--- /dev/null
+++ b/collections/web4/zos/zero_os.md
@@ -0,0 +1,44 @@
+# Ultra Secure Operating System = Zero-OS
+
+
+
+
+Zero-OS is a lightweight and efficient operating system. There is no shell, local nor remote. It supports a small number of primitives; the low-level functions it could perform natively in the operating system. Zero-OS (ZOS) is the operating system which allows the 3Nodes to be used to provide IT capacity in all safety to its applications. ZOS has been developed by ThreeFold from scratch, starting from the Linux kernel with the purpose to improve on efficiency, energy usage, performance, scale, cost of management and security. All applications, twins and blockchains are secured by the Zero-OS operating system.
+
+
+### Why?
+
+Most centrally managed operating systems rely on human management and intervention, which leads to downtime and security issues.
+
+Since the creation of the Internet, the development of operating systems mostly arises through the addition of further layers of code to improve capabilities and functionalities of software, this leads to too much complexity, performance loss, and energy usage issues.
+
+To build a truly scalable, private and efficient Internet infrastructure, we had to start from scratch to ensure a minimal hacking surface, improve efficiency, and ensure that anyone who connects hardware to the ThreeFold Grid wouldn’t be able to access the private user data thanks to our Quantum Safe Storage System.
+
+The result is game-changing as ZOS is able to provide the following benefits:
+
+
+
+* Stateless: without shell, local or remote, it does not allow for inbound network connections to happen nor can data be fetched by node operators.
+* Lightweight: Zero-OS can save up-to 10X energy on storage workloads.
+* Autonomous: it runs by itself and doesn’t require humans to maintain it, removing human error and considerably reducing the hacking surface.
+* Decentralized: deploy IT workloads and infrastructures in a private and neutral environment.
+* Secure: store workloads in a quantum safe (future proof) way.
+* Private: communicate end-to-end without centralized servers or APIs in the middle.
+* Compatible: run anything that can run on Linux but in a decentralized environment.
+
+
+
+Imagine an operating system with the following benefits
+
+* Upto 10x more efficient for certain workloads (e.g. storage)
+* No installation required
+* All files are deduplicated for the VM’s, containers and the ZOS itself, no more data duplicated filesystems
+* The hacking footprint is super small, which leads to much more safe 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
+* There is the possibility to completely disconnect the compute/storage from the network service part which means hackers have a lot less chance to get to the data.
+* A smart contract for IT layer allows groups of people to deploy IT workloads with concensus 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
+
+More info see [https://library.threefold.me/info/threefold#/technology/zos](https://library.threefold.me/info/threefold#/technology/zos)