fix includes syntax
This commit is contained in:
timurgordon
@@ -2,7 +2,7 @@
|
||||
|
||||
# DAO Consensus Engine
|
||||
|
||||
!!!include:dao_info
|
||||
!!wiki.include page:dao_info
|
||||
|
||||
## DAO Engine
|
||||
|
||||
@@ -12,8 +12,8 @@ This is a powerful blockchain construct which allows us to run our TFGrid and ma
|
||||
|
||||
This system has been designed to be compatible with multiple blockchains.
|
||||
|
||||
!!!include:consensus3_overview_graph
|
||||
!!wiki.include page:consensus3_overview_graph
|
||||
|
||||
!!!include:consensus3_toc
|
||||
!!wiki.include page:consensus3_toc
|
||||
|
||||
!!!def alias:consensus3,consensus_engine
|
||||
!!def alias:consensus3,consensus_engine
|
||||
@@ -2,7 +2,7 @@
|
||||
|
||||
### consensus engine in relation to TFT Farming Rewards in TFGrid 3.0
|
||||
|
||||
!!!include:consensus3_overview_graph
|
||||
!!wiki.include page:consensus3_overview_graph
|
||||
|
||||
The consensus engine checks the farming rules as defined in
|
||||
|
||||
@@ -14,4 +14,4 @@ The consensus engine checks the farming rules as defined in
|
||||
All the data of the farmer and the 3nodes are registered on TFChain
|
||||
|
||||
|
||||
!!!include:consensus3_toc
|
||||
!!wiki.include page:consensus3_toc
|
||||
@@ -41,4 +41,4 @@ graph TB
|
||||
|
||||
> TODO: outdated info
|
||||
|
||||
!!!include:consensus3_toc
|
||||
!!wiki.include page:consensus3_toc
|
||||
@@ -2,7 +2,7 @@
|
||||
|
||||
## Blockchain node components
|
||||
|
||||
!!!include:consensus3_overview_graph
|
||||
!!wiki.include page:consensus3_overview_graph
|
||||
|
||||
- A Blockchain node (= Substrate node) called TF-Chain, containing all entities interacting with each other on the TF-Grid
|
||||
- An explorer = a Rest + GraphQL interface to TF-Chain (Graphql is a nice query language to make it easy for everyone to query for info)
|
||||
@@ -42,4 +42,4 @@
|
||||
|
||||
> TODO: outdated info
|
||||
|
||||
!!!include:consensus3_toc
|
||||
!!wiki.include page:consensus3_toc
|
||||
@@ -50,4 +50,4 @@ graph TB
|
||||
|
||||
Above diagram shows how our consensus engine can deal with Substrate and multiple Money Blockchains at same time.
|
||||
|
||||
!!!include:consensus3_toc
|
||||
!!wiki.include page:consensus3_toc
|
||||
@@ -48,5 +48,5 @@ NEW
|
||||
|
||||
|
||||
|
||||
!!!def alias:tfchain_roadmap,dao_roadmap,tfdao_roadmap
|
||||
!!def alias:tfchain_roadmap,dao_roadmap,tfdao_roadmap
|
||||
|
||||
|
||||
@@ -70,4 +70,4 @@ graph TB
|
||||
|
||||
```
|
||||
|
||||
!!!include:consensus3_toc
|
||||
!!wiki.include page:consensus3_toc
|
||||
@@ -1,7 +1,7 @@
|
||||
|
||||
!!!include:capacity_layer_intro
|
||||
!!wiki.include page:capacity_layer_intro
|
||||
|
||||
!!!include:autonomous_layer_intro
|
||||
!!wiki.include page:autonomous_layer_intro
|
||||
|
||||
!!!include:experience_layer_intro
|
||||
!!wiki.include page:experience_layer_intro
|
||||
|
||||
|
||||
@@ -2,4 +2,4 @@
|
||||
|
||||
>TODO
|
||||
|
||||
!!!include:zos_toc
|
||||
!!wiki.include page:zos_toc
|
||||
|
||||
@@ -47,8 +47,8 @@ In addition, wireless meshing requires you to know a lot about the network aroun
|
||||
|
||||
The planetary network is a continuation & implementation of the [Yggdrasil](https://yggdrasil-network.github.io/about.html) network initiative. This technology is in beta but has been proven to work already quite well.
|
||||
|
||||
!!!def alias:planet_net,planetary_net,planetary_network,pan
|
||||
!!def alias:planet_net,planetary_net,planetary_network,pan
|
||||
|
||||
!!!include:zos_toc
|
||||
!!wiki.include page:zos_toc
|
||||
|
||||
> Click [here](manual:planetary_network_connector) to read more about Planetary Network Connector Installation. Click [here](manual:yggdrasil_client) to read more about Planetary Network Installation (advanced).
|
||||
@@ -54,7 +54,7 @@ For 3.0 we start with a HTTP(S) proxy over Planetary network connection. Not all
|
||||
|
||||
Further future, we envisage support for many other protocols: sql, redis, udp, ...
|
||||
|
||||
!!!def alias:web_gw,zos_web_gateway
|
||||
!!def alias:web_gw,zos_web_gateway
|
||||
|
||||
!!!include:zos_toc
|
||||
!!wiki.include page:zos_toc
|
||||
|
||||
|
||||
@@ -94,4 +94,4 @@ The object (video,image) can easily be embedded in any website or other represen
|
||||
|
||||
|
||||
|
||||
!!!def alias:nft_storage,nft_storage_system
|
||||
!!def alias:nft_storage,nft_storage_system
|
||||
@@ -12,4 +12,4 @@ A typical setup would look like:
|
||||
|
||||
> TODO: link to manual on cloud how to deploy minio, using helm (3.0 release)
|
||||
|
||||
!!!def alias:s3_storage
|
||||
!!def alias:s3_storage
|
||||
@@ -34,6 +34,6 @@ By using our filesystem inside a Virtual Machine or Kubernetes the TFGrid user c
|
||||
|
||||
Any storage workload can be deployed on top of the zstor.
|
||||
|
||||
!!!def alias:quantumsafe_filesystem,planetary_fs,planet_fs,quantumsafe_file_system,zstor,qsfs
|
||||
!!def alias:quantumsafe_filesystem,planetary_fs,planet_fs,quantumsafe_file_system,zstor,qsfs
|
||||
|
||||
!!!include:qsss_toc
|
||||
!!wiki.include page:qsss_toc
|
||||
@@ -77,6 +77,6 @@ If someone now wants to download the data the first 10 locations who answer fast
|
||||
The overhead here is much more compared to previous example but stil order of magnitude lower compared to other cdn systems.
|
||||
|
||||
|
||||
!!!def alias:quantumsafe_storage_algo,quantumsafe_storage_algorithm,space_algo,space_algorithm,quantum_safe_storage_algo,qs_algo,qs_codec
|
||||
!!def alias:quantumsafe_storage_algo,quantumsafe_storage_algorithm,space_algo,space_algorithm,quantum_safe_storage_algo,qs_algo,qs_codec
|
||||
|
||||
!!!include:qsss_toc
|
||||
!!wiki.include page:qsss_toc
|
||||
@@ -5,4 +5,4 @@ The storage system provided by ThreeFold intercepts this silent data corruption,
|
||||
|
||||
> see also https://en.wikipedia.org/wiki/Data_degradation
|
||||
|
||||
!!!def alias:bitrot,datarot
|
||||
!!def alias:bitrot,datarot
|
||||
@@ -8,4 +8,4 @@ The quantum save storage system is zero knowledge proof compliant. The storage s
|
||||
|
||||
The zero proof knowledge compliancy comes from the fact the all the physical storage nodes (3nodes) can proof that they store a valid part of what data the quantum safe storage engine (QSSE) has stored on multiple independent devices. The QSSE can validate that all the QSSE storage devices have a valid part of the original information. The storage devices however have no idea what the original stored data is as they only have a part (description) of the origina data and have no access to the original data part or the complete origal data objects.
|
||||
|
||||
!!!def
|
||||
!!def
|
||||
@@ -1,2 +1,2 @@
|
||||
|
||||
!!!include:qsss_home
|
||||
!!wiki.include page:qsss_home
|
||||
@@ -4,7 +4,7 @@
|
||||
|
||||
Imagine a storage system with the following benefits
|
||||
|
||||
!!!include:qss_benefits_
|
||||
!!wiki.include page:qss_benefits_
|
||||
|
||||
> This is not a dream but does exist and is the underpinning of the TFGrid.
|
||||
|
||||
@@ -13,9 +13,9 @@ Our storage architecture follows the true peer-to-peer design of the TF grid. An
|
||||
Peer-to-peer provides the unique proposition of selecting storage providers that match your application and service of business criteria. For example, you might be looking to store data for your application in a certain geographic area (for governance and compliance) reasons. Also, you might want to use different "storage policies" for different types of data. Examples are live versus archived data. All of these uses cases are possible with this storage architecture and could be built by using the same building blocks produced by farmers and consumed by developers or end-users.
|
||||
|
||||
|
||||
!!!include:qsss_toc
|
||||
!!wiki.include page:qsss_toc
|
||||
|
||||
!!!def alias:qsss,quantum_safe_storage_system
|
||||
!!def alias:qsss,quantum_safe_storage_system
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -37,8 +37,8 @@ Uses [Network Units = SU](cloudunits).
|
||||
|
||||
## Zero-OS Advantages
|
||||
|
||||
!!!include:zos_advantages
|
||||
!!wiki.include page:zos_advantages
|
||||
|
||||
|
||||
!!!def alias:tfgrid_primitives,grid_primitives
|
||||
!!def alias:tfgrid_primitives,grid_primitives
|
||||
|
||||
|
||||
@@ -11,4 +11,4 @@ A major step in accepting and importing Docker images is to transpose docker ima
|
||||
- Easy import and transpose facility
|
||||
- deduplicated application deployment simplifying aplication image management and versioning
|
||||
|
||||
!!!include:zos_toc
|
||||
!!wiki.include page:zos_toc
|
||||
@@ -33,6 +33,6 @@ As a consequence, no tcp/ip is coming in AT ALL, making the full set-up reach un
|
||||
- You don’t have to worry about ‘how to secure my DB’ as my DB is not exposed, only accessible in Wireguard private network.
|
||||
- In containers you can specify to have specific IPv6 address, so deploy reverse proxy in container which has public access, = entry point in the network, deploy reverse tcp connection (=tcp router client), connects to the gateways and allows incoming connection.
|
||||
|
||||
!!!def alias:network_wall,net_wall
|
||||
!!def alias:network_wall,net_wall
|
||||
|
||||
!!!include:zos_toc
|
||||
!!wiki.include page:zos_toc
|
||||
|
||||
@@ -27,4 +27,4 @@ At Threefold, we are aware of the existence of private networks, IPsec, VPN, WAN
|
||||
|
||||
|
||||
|
||||
!!!def alias:quantumsafe_network_concept,qsn_concept
|
||||
!!def alias:quantumsafe_network_concept,qsn_concept
|
||||
@@ -34,6 +34,6 @@ The Prometheus ecosystem consists of multiple components, many of which are opti
|
||||
- ONLY for OEM partners today
|
||||
|
||||
|
||||
!!!def alias:zos_monitoring
|
||||
!!def alias:zos_monitoring
|
||||
|
||||
!!!include:zos_toc
|
||||
!!wiki.include page:zos_toc
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
|
||||
|
||||
|
||||
!!!include:whatis_zos
|
||||
!!wiki.include page:whatis_zos
|
||||
|
||||
### Imagine an operating system with the following benefits
|
||||
|
||||
@@ -28,9 +28,9 @@
|
||||
- **Simplicity**: An operating system should be simple, able to exist anywhere, for anyone, good for the planet.
|
||||
- **Stateless**. In a grid (peer-to-peer) set up, the sum of the components is providing a stable basis for single elements to fail and not bring the whole system down. Therefore, it is necessary for single elements to be stateless, and the state needs to be stored within the grid.
|
||||
|
||||
<!-- !!!include:zos_toc -->
|
||||
<!-- !!wiki.include page:zos_toc -->
|
||||
|
||||
!!!def alias:zos,zero-os,threefold_operating_system,tf_os,threefold_os
|
||||
!!def alias:zos,zero-os,threefold_operating_system,tf_os,threefold_os
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -3,4 +3,4 @@
|
||||
|
||||
|
||||
|
||||
!!!include:zos_toc
|
||||
!!wiki.include page:zos_toc
|
||||
@@ -18,4 +18,4 @@ The operating system is not installed on any local storage medium (hard disk, ss
|
||||
|
||||
The mechanism to allow this to work in a safe and efficient manner is a ThreeFold innovation called our container virtual filesystem. This is explained in more detail [here](flist)
|
||||
|
||||
!!!def alias:zero_os_install
|
||||
!!def alias:zero_os_install
|
||||
@@ -3,4 +3,4 @@
|
||||
|
||||
|
||||
|
||||
!!!include:zos_toc
|
||||
!!wiki.include page:zos_toc
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
!!!include:flist_hub_
|
||||
!!wiki.include page:flist_hub_
|
||||
|
||||
!!!def alias:tfhub,zflist_hub,flist_hub
|
||||
!!def alias:tfhub,zflist_hub,flist_hub
|
||||
|
||||
|
||||
Reference in New Issue
Block a user