updated smaller collections for manual
This commit is contained in:
parent
4806cb355b
commit
b1e98c2051
@ -50,330 +50,330 @@
|
|||||||
- [TF Token Bridge](dashboard/tfchain/tf_token_bridge.md)
|
- [TF Token Bridge](dashboard/tfchain/tf_token_bridge.md)
|
||||||
- [TF Token Transfer](dashboard/tfchain/tf_token_transfer.md)
|
- [TF Token Transfer](dashboard/tfchain/tf_token_transfer.md)
|
||||||
- [TF Minting Reports](dashboard/tfchain/tf_minting_reports.md)
|
- [TF Minting Reports](dashboard/tfchain/tf_minting_reports.md)
|
||||||
- [Developers](manual/documentation/developers/developers.md)
|
- [Developers](developers/developers.md)
|
||||||
- [Javascript Client](manual/documentation/developers/javascript/grid3_javascript_readme.md)
|
- [Javascript Client](developers/javascript/grid3_javascript_readme.md)
|
||||||
- [Installation](manual/documentation/developers/javascript/grid3_javascript_installation.md)
|
- [Installation](developers/javascript/grid3_javascript_installation.md)
|
||||||
- [Loading Client](manual/documentation/developers/javascript/grid3_javascript_loadclient.md)
|
- [Loading Client](developers/javascript/grid3_javascript_loadclient.md)
|
||||||
- [Deploy a VM](manual/documentation/developers/javascript/grid3_javascript_vm.md)
|
- [Deploy a VM](developers/javascript/grid3_javascript_vm.md)
|
||||||
- [Capacity Planning](manual/documentation/developers/javascript/grid3_javascript_capacity_planning.md)
|
- [Capacity Planning](developers/javascript/grid3_javascript_capacity_planning.md)
|
||||||
- [Deploy Multiple VMs](manual/documentation/developers/javascript/grid3_javascript_vms.md)
|
- [Deploy Multiple VMs](developers/javascript/grid3_javascript_vms.md)
|
||||||
- [Deploy CapRover](manual/documentation/developers/javascript/grid3_javascript_caprover.md)
|
- [Deploy CapRover](developers/javascript/grid3_javascript_caprover.md)
|
||||||
- [Gateways](manual/documentation/developers/javascript/grid3_javascript_vm_gateways.md)
|
- [Gateways](developers/javascript/grid3_javascript_vm_gateways.md)
|
||||||
- [Deploy a Kubernetes Cluster](manual/documentation/developers/javascript/grid3_javascript_kubernetes.md)
|
- [Deploy a Kubernetes Cluster](developers/javascript/grid3_javascript_kubernetes.md)
|
||||||
- [Deploy a ZDB](manual/documentation/developers/javascript/grid3_javascript_zdb.md)
|
- [Deploy a ZDB](developers/javascript/grid3_javascript_zdb.md)
|
||||||
- [Deploy ZDBs for QSFS](manual/documentation/developers/javascript/grid3_javascript_qsfs_zdbs.md)
|
- [Deploy ZDBs for QSFS](developers/javascript/grid3_javascript_qsfs_zdbs.md)
|
||||||
- [QSFS](manual/documentation/developers/javascript/grid3_javascript_qsfs.md)
|
- [QSFS](developers/javascript/grid3_javascript_qsfs.md)
|
||||||
- [Key Value Store](manual/documentation/developers/javascript/grid3_javascript_kvstore.md)
|
- [Key Value Store](developers/javascript/grid3_javascript_kvstore.md)
|
||||||
- [VM with Wireguard and Gateway](manual/documentation/developers/javascript/grid3_wireguard_gateway.md)
|
- [VM with Wireguard and Gateway](developers/javascript/grid3_wireguard_gateway.md)
|
||||||
- [GPU Support](manual/documentation/developers/javascript/grid3_javascript_gpu_support.md)
|
- [GPU Support](developers/javascript/grid3_javascript_gpu_support.md)
|
||||||
- [Go Client](manual/documentation/developers/go/grid3_go_readme.md)
|
- [Go Client](developers/go/grid3_go_readme.md)
|
||||||
- [Installation](manual/documentation/developers/go/grid3_go_installation.md)
|
- [Installation](developers/go/grid3_go_installation.md)
|
||||||
- [Loading Client](manual/documentation/developers/go/grid3_go_load_client.md)
|
- [Loading Client](developers/go/grid3_go_load_client.md)
|
||||||
- [Deploy a VM](manual/documentation/developers/go/grid3_go_vm.md)
|
- [Deploy a VM](developers/go/grid3_go_vm.md)
|
||||||
- [Deploy Multiple VMs](manual/documentation/developers/go/grid3_go_vms.md)
|
- [Deploy Multiple VMs](developers/go/grid3_go_vms.md)
|
||||||
- [Deploy Gateways](manual/documentation/developers/go/grid3_go_gateways.md)
|
- [Deploy Gateways](developers/go/grid3_go_gateways.md)
|
||||||
- [Deploy Kubernetes](manual/documentation/developers/go/grid3_go_kubernetes.md)
|
- [Deploy Kubernetes](developers/go/grid3_go_kubernetes.md)
|
||||||
- [Deploy a QSFS](manual/documentation/developers/go/grid3_go_qsfs.md)
|
- [Deploy a QSFS](developers/go/grid3_go_qsfs.md)
|
||||||
- [GPU and Go](manual/documentation/developers/go/grid3_go_gpu.md)
|
- [GPU and Go](developers/go/grid3_go_gpu.md)
|
||||||
- [GPU Support](manual/documentation/developers/go/grid3_go_gpu_support.md)
|
- [GPU Support](developers/go/grid3_go_gpu_support.md)
|
||||||
- [Deploy a VM with GPU](manual/documentation/developers/go/grid3_go_vm_with_gpu.md)
|
- [Deploy a VM with GPU](developers/go/grid3_go_vm_with_gpu.md)
|
||||||
- [TFCMD](manual/documentation/developers/tfcmd/tfcmd.md)
|
- [TFCMD](developers/tfcmd/tfcmd.md)
|
||||||
- [Getting Started](manual/documentation/developers/tfcmd/tfcmd_basics.md)
|
- [Getting Started](developers/tfcmd/tfcmd_basics.md)
|
||||||
- [Deploy a VM](manual/documentation/developers/tfcmd/tfcmd_vm.md)
|
- [Deploy a VM](developers/tfcmd/tfcmd_vm.md)
|
||||||
- [Deploy Kubernetes](manual/documentation/developers/tfcmd/tfcmd_kubernetes.md)
|
- [Deploy Kubernetes](developers/tfcmd/tfcmd_kubernetes.md)
|
||||||
- [Deploy ZDB](manual/documentation/developers/tfcmd/tfcmd_zdbs.md)
|
- [Deploy ZDB](developers/tfcmd/tfcmd_zdbs.md)
|
||||||
- [Gateway FQDN](manual/documentation/developers/tfcmd/tfcmd_gateway_fqdn.md)
|
- [Gateway FQDN](developers/tfcmd/tfcmd_gateway_fqdn.md)
|
||||||
- [Gateway Name](manual/documentation/developers/tfcmd/tfcmd_gateway_name.md)
|
- [Gateway Name](developers/tfcmd/tfcmd_gateway_name.md)
|
||||||
- [Contracts](manual/documentation/developers/tfcmd/tfcmd_contracts.md)
|
- [Contracts](developers/tfcmd/tfcmd_contracts.md)
|
||||||
- [TFROBOT](manual/documentation/developers/tfrobot/tfrobot.md)
|
- [TFROBOT](developers/tfrobot/tfrobot.md)
|
||||||
- [Installation](manual/documentation/developers/tfrobot/tfrobot_installation.md)
|
- [Installation](developers/tfrobot/tfrobot_installation.md)
|
||||||
- [Configuration File](manual/documentation/developers/tfrobot/tfrobot_config.md)
|
- [Configuration File](developers/tfrobot/tfrobot_config.md)
|
||||||
- [Deployment](manual/documentation/developers/tfrobot/tfrobot_deploy.md)
|
- [Deployment](developers/tfrobot/tfrobot_deploy.md)
|
||||||
- [Commands and Flags](manual/documentation/developers/tfrobot/tfrobot_commands_flags.md)
|
- [Commands and Flags](developers/tfrobot/tfrobot_commands_flags.md)
|
||||||
- [Supported Configurations](manual/documentation/developers/tfrobot/tfrobot_configurations.md)
|
- [Supported Configurations](developers/tfrobot/tfrobot_configurations.md)
|
||||||
- [ThreeFold Chain](manual/documentation/developers/tfchain/dev_tfchain.md)
|
- [ThreeFold Chain](developers/tfchain/dev_tfchain.md)
|
||||||
- [Introduction](manual/documentation/developers/tfchain/introduction.md)
|
- [Introduction](developers/tfchain/introduction.md)
|
||||||
- [Farming Policies](manual/documentation/developers/tfchain/farming_policies.md)
|
- [Farming Policies](developers/tfchain/farming_policies.md)
|
||||||
- [External Service Contract](manual/documentation/developers/tfchain/tfchain_external_service_contract.md)
|
- [External Service Contract](developers/tfchain/tfchain_external_service_contract.md)
|
||||||
- [Solution Provider](manual/documentation/developers/tfchain/tfchain_solution_provider.md)
|
- [Solution Provider](developers/tfchain/tfchain_solution_provider.md)
|
||||||
- [Grid Proxy](manual/documentation/developers/proxy/proxy_readme.md)
|
- [Grid Proxy](developers/proxy/proxy_readme.md)
|
||||||
- [Introducing Grid Proxy](manual/documentation/developers/proxy/proxy.md)
|
- [Introducing Grid Proxy](developers/proxy/proxy.md)
|
||||||
- [Setup](manual/documentation/developers/proxy/setup.md)
|
- [Setup](developers/proxy/setup.md)
|
||||||
- [DB Testing](manual/documentation/developers/proxy/db_testing.md)
|
- [DB Testing](developers/proxy/db_testing.md)
|
||||||
- [Commands](manual/documentation/developers/proxy/commands.md)
|
- [Commands](developers/proxy/commands.md)
|
||||||
- [Contributions](manual/documentation/developers/proxy/contributions.md)
|
- [Contributions](developers/proxy/contributions.md)
|
||||||
- [Explorer](manual/documentation/developers/proxy/explorer.md)
|
- [Explorer](developers/proxy/explorer.md)
|
||||||
- [Database](manual/documentation/developers/proxy/database.md)
|
- [Database](developers/proxy/database.md)
|
||||||
- [Production](manual/documentation/developers/proxy/production.md)
|
- [Production](developers/proxy/production.md)
|
||||||
- [Release](manual/documentation/developers/proxy/release.md)
|
- [Release](developers/proxy/release.md)
|
||||||
- [Flist](manual/documentation/developers/flist/flist.md)
|
- [Flist](developers/flist/flist.md)
|
||||||
- [Zero-OS Hub](manual/documentation/developers/flist/flist_hub/zos_hub.md)
|
- [Zero-OS Hub](developers/flist/flist_hub/zos_hub.md)
|
||||||
- [Generate an API Token](manual/documentation/developers/flist/flist_hub/api_token.md)
|
- [Generate an API Token](developers/flist/flist_hub/api_token.md)
|
||||||
- [Convert Docker Image Into Flist](manual/documentation/developers/flist/flist_hub/convert_docker_image.md)
|
- [Convert Docker Image Into Flist](developers/flist/flist_hub/convert_docker_image.md)
|
||||||
- [Supported Flists](manual/documentation/developers/flist/grid3_supported_flists.md)
|
- [Supported Flists](developers/flist/grid3_supported_flists.md)
|
||||||
- [Flist Case Studies](manual/documentation/developers/flist/flist_case_studies/flist_case_studies.md)
|
- [Flist Case Studies](developers/flist/flist_case_studies/flist_case_studies.md)
|
||||||
- [Case Study: Debian 12](manual/documentation/developers/flist/flist_case_studies/flist_debian_case_study.md)
|
- [Case Study: Debian 12](developers/flist/flist_case_studies/flist_debian_case_study.md)
|
||||||
- [Case Study: Nextcloud AIO](manual/documentation/developers/flist/flist_case_studies/flist_nextcloud_case_study.md)
|
- [Case Study: Nextcloud AIO](developers/flist/flist_case_studies/flist_nextcloud_case_study.md)
|
||||||
- [Internals](manual/documentation/developers/internals/internals.md)
|
- [Internals](developers/internals/internals.md)
|
||||||
- [Reliable Message Bus - RMB](manual/documentation/developers/internals/rmb/rmb_toc.md)
|
- [Reliable Message Bus - RMB](developers/internals/rmb/rmb_toc.md)
|
||||||
- [Introduction to RMB](manual/documentation/developers/internals/rmb/rmb_intro.md)
|
- [Introduction to RMB](developers/internals/rmb/rmb_intro.md)
|
||||||
- [RMB Specs](manual/documentation/developers/internals/rmb/rmb_specs.md)
|
- [RMB Specs](developers/internals/rmb/rmb_specs.md)
|
||||||
- [RMB Peer](manual/documentation/developers/internals/rmb/uml/peer.md)
|
- [RMB Peer](developers/internals/rmb/uml/peer.md)
|
||||||
- [RMB Relay](manual/documentation/developers/internals/rmb/uml/relay.md)
|
- [RMB Relay](developers/internals/rmb/uml/relay.md)
|
||||||
- [Zero-OS](manual/documentation/developers/internals/zos/readme.md)
|
- [Zero-OS](developers/internals/zos/readme.md)
|
||||||
- [Manual](manual/documentation/developers/internals/zos/manual/manual.md)
|
- [Manual](developers/internals/zos/manual/manual.md)
|
||||||
- [Workload Types](manual/documentation/developers/internals/zos/manual/workload_types.md)
|
- [Workload Types](developers/internals/zos/manual/workload_types.md)
|
||||||
- [Internal Modules](manual/documentation/developers/internals/zos/internals/internals.md)
|
- [Internal Modules](developers/internals/zos/internals/internals.md)
|
||||||
- [Identity](manual/documentation/developers/internals/zos/internals/identity/readme.md)
|
- [Identity](developers/internals/zos/internals/identity/readme.md)
|
||||||
- [Node ID Generation](manual/documentation/developers/internals/zos/internals/identity/identity.md)
|
- [Node ID Generation](developers/internals/zos/internals/identity/identity.md)
|
||||||
- [Node Upgrade](manual/documentation/developers/internals/zos/internals/identity/upgrade.md)
|
- [Node Upgrade](developers/internals/zos/internals/identity/upgrade.md)
|
||||||
- [Node](manual/documentation/developers/internals/zos/internals/node/readme.md)
|
- [Node](developers/internals/zos/internals/node/readme.md)
|
||||||
- [Storage](manual/documentation/developers/internals/zos/internals/storage/readme.md)
|
- [Storage](developers/internals/zos/internals/storage/readme.md)
|
||||||
- [Network](manual/documentation/developers/internals/zos/internals/network/readme.md)
|
- [Network](developers/internals/zos/internals/network/readme.md)
|
||||||
- [Introduction](manual/documentation/developers/internals/zos/internals/network/introduction.md)
|
- [Introduction](developers/internals/zos/internals/network/introduction.md)
|
||||||
- [Definitions](manual/documentation/developers/internals/zos/internals/network/definitions.md)
|
- [Definitions](developers/internals/zos/internals/network/definitions.md)
|
||||||
- [Mesh](manual/documentation/developers/internals/zos/internals/network/mesh.md)
|
- [Mesh](developers/internals/zos/internals/network/mesh.md)
|
||||||
- [Setup](manual/documentation/developers/internals/zos/internals/network/setup_farm_network.md)
|
- [Setup](developers/internals/zos/internals/network/setup_farm_network.md)
|
||||||
- [Flist](manual/documentation/developers/internals/zos/internals/flist/readme.md)
|
- [Flist](developers/internals/zos/internals/flist/readme.md)
|
||||||
- [Container](manual/documentation/developers/internals/zos/internals/container/readme.md)
|
- [Container](developers/internals/zos/internals/container/readme.md)
|
||||||
- [VM](manual/documentation/developers/internals/zos/internals/vmd/readme.md)
|
- [VM](developers/internals/zos/internals/vmd/readme.md)
|
||||||
- [Provision](manual/documentation/developers/internals/zos/internals/provision/readme.md)
|
- [Provision](developers/internals/zos/internals/provision/readme.md)
|
||||||
- [Capacity](manual/documentation/developers/internals/zos/internals/capacity.md)
|
- [Capacity](developers/internals/zos/internals/capacity.md)
|
||||||
- [Performance Monitor Package](manual/documentation/developers/internals/zos/performance/performance.md)
|
- [Performance Monitor Package](developers/internals/zos/performance/performance.md)
|
||||||
- [Public IPs Validation Task](manual/documentation/developers/internals/zos/performance/publicips.md)
|
- [Public IPs Validation Task](developers/internals/zos/performance/publicips.md)
|
||||||
- [CPUBenchmark](manual/documentation/developers/internals/zos/performance/cpubench.md)
|
- [CPUBenchmark](developers/internals/zos/performance/cpubench.md)
|
||||||
- [IPerf](manual/documentation/developers/internals/zos/performance/iperf.md)
|
- [IPerf](developers/internals/zos/performance/iperf.md)
|
||||||
- [Health Check](manual/documentation/developers/internals/zos/performance/healthcheck.md)
|
- [Health Check](developers/internals/zos/performance/healthcheck.md)
|
||||||
- [API](manual/documentation/developers/internals/zos/manual/api.md)
|
- [API](developers/internals/zos/manual/api.md)
|
||||||
- [Grid Deployment](manual/documentation/developers/grid_deployment/grid_deployment.md)
|
- [Grid Deployment](developers/grid_deployment/grid_deployment.md)
|
||||||
- [TFGrid Stacks](manual/documentation/developers/grid_deployment/tfgrid_stacks.md)
|
- [TFGrid Stacks](developers/grid_deployment/tfgrid_stacks.md)
|
||||||
- [Full VM Grid Deployment](manual/documentation/developers/grid_deployment/grid_deployment_full_vm.md)
|
- [Full VM Grid Deployment](developers/grid_deployment/grid_deployment_full_vm.md)
|
||||||
- [Grid Snapshots](manual/documentation/developers/grid_deployment/snapshots.md)
|
- [Grid Snapshots](developers/grid_deployment/snapshots.md)
|
||||||
- [Farmers](manual/documentation/farmers/farmers.md)
|
- [Farmers](farmers/farmers.md)
|
||||||
- [Build a 3Node](manual/documentation/farmers/3node_building/3node_building.md)
|
- [Build a 3Node](farmers/3node_building/3node_building.md)
|
||||||
- [1. Create a Farm](manual/documentation/farmers/3node_building/1_create_farm.md)
|
- [1. Create a Farm](farmers/3node_building/1_create_farm.md)
|
||||||
- [2. Create a Zero-OS Bootstrap Image](manual/documentation/farmers/3node_building/2_bootstrap_image.md)
|
- [2. Create a Zero-OS Bootstrap Image](farmers/3node_building/2_bootstrap_image.md)
|
||||||
- [3. Set the Hardware](manual/documentation/farmers/3node_building/3_set_hardware.md)
|
- [3. Set the Hardware](farmers/3node_building/3_set_hardware.md)
|
||||||
- [4. Wipe All the Disks](manual/documentation/farmers/3node_building/4_wipe_all_disks.md)
|
- [4. Wipe All the Disks](farmers/3node_building/4_wipe_all_disks.md)
|
||||||
- [5. Set the BIOS/UEFI](manual/documentation/farmers/3node_building/5_set_bios_uefi.md)
|
- [5. Set the BIOS/UEFI](farmers/3node_building/5_set_bios_uefi.md)
|
||||||
- [6. Boot the 3Node](manual/documentation/farmers/3node_building/6_boot_3node.md)
|
- [6. Boot the 3Node](farmers/3node_building/6_boot_3node.md)
|
||||||
- [Farming Optimization](manual/documentation/farmers/farming_optimization/farming_optimization.md)
|
- [Farming Optimization](farmers/farming_optimization/farming_optimization.md)
|
||||||
- [GPU Farming](manual/documentation/farmers/3node_building/gpu_farming.md)
|
- [GPU Farming](farmers/3node_building/gpu_farming.md)
|
||||||
- [Set Additional Fees](manual/documentation/farmers/farming_optimization/set_additional_fees.md)
|
- [Set Additional Fees](farmers/farming_optimization/set_additional_fees.md)
|
||||||
- [Minting Receipts](manual/documentation/farmers/3node_building/minting_receipts.md)
|
- [Minting Receipts](farmers/3node_building/minting_receipts.md)
|
||||||
- [Minting Periods](manual/documentation/farmers/farming_optimization/minting_periods.md)
|
- [Minting Periods](farmers/farming_optimization/minting_periods.md)
|
||||||
- [Room Parameters](manual/documentation/farmers/farming_optimization/farm_room_parameters.md)
|
- [Room Parameters](farmers/farming_optimization/farm_room_parameters.md)
|
||||||
- [Farming Costs](manual/documentation/farmers/farming_optimization/farming_costs.md)
|
- [Farming Costs](farmers/farming_optimization/farming_costs.md)
|
||||||
- [Calculate Your ROI](manual/documentation/farmers/farming_optimization/calculate_roi.md)
|
- [Calculate Your ROI](farmers/farming_optimization/calculate_roi.md)
|
||||||
- [Advanced Networking](manual/documentation/farmers/advanced_networking/advanced_networking_toc.md)
|
- [Advanced Networking](farmers/advanced_networking/advanced_networking_toc.md)
|
||||||
- [Networking Overview](manual/documentation/farmers/advanced_networking/networking_overview.md)
|
- [Networking Overview](farmers/advanced_networking/networking_overview.md)
|
||||||
- [Network Considerations](manual/documentation/farmers/advanced_networking/network_considerations.md)
|
- [Network Considerations](farmers/advanced_networking/network_considerations.md)
|
||||||
- [Network Setup](manual/documentation/farmers/advanced_networking/network_setup.md)
|
- [Network Setup](farmers/advanced_networking/network_setup.md)
|
||||||
- [Farmerbot](manual/documentation/farmers/farmerbot/farmerbot_intro.md)
|
- [Farmerbot](farmers/farmerbot/farmerbot_intro.md)
|
||||||
- [Quick Guide](manual/documentation/farmers/farmerbot/farmerbot_quick.md)
|
- [Quick Guide](farmers/farmerbot/farmerbot_quick.md)
|
||||||
- [Additional Information](manual/documentation/farmers/farmerbot/farmerbot_information.md)
|
- [Additional Information](farmers/farmerbot/farmerbot_information.md)
|
||||||
- [Minting and the Farmerbot](manual/documentation/farmers/farmerbot/farmerbot_minting.md)
|
- [Minting and the Farmerbot](farmers/farmerbot/farmerbot_minting.md)
|
||||||
- [System Administrators](manual/documentation/system_administrators/system_administrators.md)
|
- [System Administrators](system_administrators/system_administrators.md)
|
||||||
- [Getting Started](manual/documentation/system_administrators/getstarted/tfgrid3_getstarted.md)
|
- [Getting Started](system_administrators/getstarted/tfgrid3_getstarted.md)
|
||||||
- [SSH Remote Connection](manual/documentation/system_administrators/getstarted/ssh_guide/ssh_guide.md)
|
- [SSH Remote Connection](system_administrators/getstarted/ssh_guide/ssh_guide.md)
|
||||||
- [SSH with OpenSSH](manual/documentation/system_administrators/getstarted/ssh_guide/ssh_openssh.md)
|
- [SSH with OpenSSH](system_administrators/getstarted/ssh_guide/ssh_openssh.md)
|
||||||
- [SSH with PuTTY](manual/documentation/system_administrators/getstarted/ssh_guide/ssh_putty.md)
|
- [SSH with PuTTY](system_administrators/getstarted/ssh_guide/ssh_putty.md)
|
||||||
- [SSH with WSL](manual/documentation/system_administrators/getstarted/ssh_guide/ssh_wsl.md)
|
- [SSH with WSL](system_administrators/getstarted/ssh_guide/ssh_wsl.md)
|
||||||
- [WireGuard Access](manual/documentation/system_administrators/getstarted/ssh_guide/ssh_wireguard.md)
|
- [WireGuard Access](system_administrators/getstarted/ssh_guide/ssh_wireguard.md)
|
||||||
- [Remote Desktop and GUI](manual/documentation/system_administrators/getstarted/remote-desktop_gui/remote-desktop_gui.md)
|
- [Remote Desktop and GUI](system_administrators/getstarted/remote-desktop_gui/remote-desktop_gui.md)
|
||||||
- [Cockpit: a Web-based Interface for Servers](manual/documentation/system_administrators/getstarted/remote-desktop_gui/cockpit_guide/cockpit_guide.md)
|
- [Cockpit: a Web-based Interface for Servers](system_administrators/getstarted/remote-desktop_gui/cockpit_guide/cockpit_guide.md)
|
||||||
- [XRDP: an Open-Source Remote Desktop Protocol](manual/documentation/system_administrators/getstarted/remote-desktop_gui/xrdp_guide/xrdp_guide.md)
|
- [XRDP: an Open-Source Remote Desktop Protocol](system_administrators/getstarted/remote-desktop_gui/xrdp_guide/xrdp_guide.md)
|
||||||
- [Apache Guacamole: a Clientless Remote Desktop Gateway](manual/documentation/system_administrators/getstarted/remote-desktop_gui/guacamole_guide/guacamole_guide.md)
|
- [Apache Guacamole: a Clientless Remote Desktop Gateway](system_administrators/getstarted/remote-desktop_gui/guacamole_guide/guacamole_guide.md)
|
||||||
- [Planetary Network](manual/documentation/system_administrators/getstarted/planetarynetwork.md)
|
- [Planetary Network](system_administrators/getstarted/planetarynetwork.md)
|
||||||
- [TFGrid Services](manual/documentation/system_administrators/getstarted/tfgrid_services/tf_grid_services_readme.md)
|
- [TFGrid Services](system_administrators/getstarted/tfgrid_services/tf_grid_services_readme.md)
|
||||||
- [GPU](manual/documentation/system_administrators/gpu/gpu_toc.md)
|
- [GPU](system_administrators/gpu/gpu_toc.md)
|
||||||
- [GPU Support](manual/documentation/system_administrators/gpu/gpu.md)
|
- [GPU Support](system_administrators/gpu/gpu.md)
|
||||||
- [Terraform](manual/documentation/system_administrators/terraform/terraform_toc.md)
|
- [Terraform](system_administrators/terraform/terraform_toc.md)
|
||||||
- [Overview](manual/documentation/system_administrators/terraform/terraform_readme.md)
|
- [Overview](system_administrators/terraform/terraform_readme.md)
|
||||||
- [Installing Terraform](manual/documentation/system_administrators/terraform/terraform_install.md)
|
- [Installing Terraform](system_administrators/terraform/terraform_install.md)
|
||||||
- [Terraform Basics](manual/documentation/system_administrators/terraform/terraform_basics.md)
|
- [Terraform Basics](system_administrators/terraform/terraform_basics.md)
|
||||||
- [Full VM Deployment](manual/documentation/system_administrators/terraform/terraform_full_vm.md)
|
- [Full VM Deployment](system_administrators/terraform/terraform_full_vm.md)
|
||||||
- [GPU Support](manual/documentation/system_administrators/terraform/terraform_gpu_support.md)
|
- [GPU Support](system_administrators/terraform/terraform_gpu_support.md)
|
||||||
- [Resources](manual/documentation/system_administrators/terraform/resources/terraform_resources_readme.md)
|
- [Resources](system_administrators/terraform/resources/terraform_resources_readme.md)
|
||||||
- [Using Scheduler](manual/documentation/system_administrators/terraform/resources/terraform_scheduler.md)
|
- [Using Scheduler](system_administrators/terraform/resources/terraform_scheduler.md)
|
||||||
- [Virtual Machine](manual/documentation/system_administrators/terraform/resources/terraform_vm.md)
|
- [Virtual Machine](system_administrators/terraform/resources/terraform_vm.md)
|
||||||
- [Web Gateway](manual/documentation/system_administrators/terraform/resources/terraform_vm_gateway.md)
|
- [Web Gateway](system_administrators/terraform/resources/terraform_vm_gateway.md)
|
||||||
- [Kubernetes Cluster](manual/documentation/system_administrators/terraform/resources/terraform_k8s.md)
|
- [Kubernetes Cluster](system_administrators/terraform/resources/terraform_k8s.md)
|
||||||
- [ZDB](manual/documentation/system_administrators/terraform/resources/terraform_zdb.md)
|
- [ZDB](system_administrators/terraform/resources/terraform_zdb.md)
|
||||||
- [Quantum Safe Filesystem](manual/documentation/system_administrators/terraform/resources/terraform_qsfs.md)
|
- [Quantum Safe Filesystem](system_administrators/terraform/resources/terraform_qsfs.md)
|
||||||
- [QSFS on Micro VM](manual/documentation/system_administrators/terraform/resources/terraform_qsfs_on_microvm.md)
|
- [QSFS on Micro VM](system_administrators/terraform/resources/terraform_qsfs_on_microvm.md)
|
||||||
- [QSFS on Full VM](manual/documentation/system_administrators/terraform/resources/terraform_qsfs_on_full_vm.md)
|
- [QSFS on Full VM](system_administrators/terraform/resources/terraform_qsfs_on_full_vm.md)
|
||||||
- [CapRover](manual/documentation/system_administrators/terraform/resources/terraform_caprover.md)
|
- [CapRover](system_administrators/terraform/resources/terraform_caprover.md)
|
||||||
- [Advanced](manual/documentation/system_administrators/terraform/advanced/terraform_advanced_readme.md)
|
- [Advanced](system_administrators/terraform/advanced/terraform_advanced_readme.md)
|
||||||
- [Terraform Provider](manual/documentation/system_administrators/terraform/advanced/terraform_provider.md)
|
- [Terraform Provider](system_administrators/terraform/advanced/terraform_provider.md)
|
||||||
- [Terraform Provisioners](manual/documentation/system_administrators/terraform/advanced/terraform_provisioners.md)
|
- [Terraform Provisioners](system_administrators/terraform/advanced/terraform_provisioners.md)
|
||||||
- [Mounts](manual/documentation/system_administrators/terraform/advanced/terraform_mounts.md)
|
- [Mounts](system_administrators/terraform/advanced/terraform_mounts.md)
|
||||||
- [Capacity Planning](manual/documentation/system_administrators/terraform/advanced/terraform_capacity_planning.md)
|
- [Capacity Planning](system_administrators/terraform/advanced/terraform_capacity_planning.md)
|
||||||
- [Updates](manual/documentation/system_administrators/terraform/advanced/terraform_updates.md)
|
- [Updates](system_administrators/terraform/advanced/terraform_updates.md)
|
||||||
- [SSH Connection with Wireguard](manual/documentation/system_administrators/terraform/advanced/terraform_wireguard_ssh.md)
|
- [SSH Connection with Wireguard](system_administrators/terraform/advanced/terraform_wireguard_ssh.md)
|
||||||
- [Set a Wireguard VPN](manual/documentation/system_administrators/terraform/advanced/terraform_wireguard_vpn.md)
|
- [Set a Wireguard VPN](system_administrators/terraform/advanced/terraform_wireguard_vpn.md)
|
||||||
- [Synced MariaDB Databases](manual/documentation/system_administrators/terraform/advanced/terraform_mariadb_synced_databases.md)
|
- [Synced MariaDB Databases](system_administrators/terraform/advanced/terraform_mariadb_synced_databases.md)
|
||||||
- [Nomad](manual/documentation/system_administrators/terraform/advanced/terraform_nomad.md)
|
- [Nomad](system_administrators/terraform/advanced/terraform_nomad.md)
|
||||||
- [Nextcloud Deployments](manual/documentation/system_administrators/terraform/advanced/terraform_nextcloud_toc.md)
|
- [Nextcloud Deployments](system_administrators/terraform/advanced/terraform_nextcloud_toc.md)
|
||||||
- [Nextcloud All-in-One Deployment](manual/documentation/system_administrators/terraform/advanced/terraform_nextcloud_aio.md)
|
- [Nextcloud All-in-One Deployment](system_administrators/terraform/advanced/terraform_nextcloud_aio.md)
|
||||||
- [Nextcloud Single Deployment](manual/documentation/system_administrators/terraform/advanced/terraform_nextcloud_single.md)
|
- [Nextcloud Single Deployment](system_administrators/terraform/advanced/terraform_nextcloud_single.md)
|
||||||
- [Nextcloud Redundant Deployment](manual/documentation/system_administrators/terraform/advanced/terraform_nextcloud_redundant.md)
|
- [Nextcloud Redundant Deployment](system_administrators/terraform/advanced/terraform_nextcloud_redundant.md)
|
||||||
- [Nextcloud 2-Node VPN Deployment](manual/documentation/system_administrators/terraform/advanced/terraform_nextcloud_vpn.md)
|
- [Nextcloud 2-Node VPN Deployment](system_administrators/terraform/advanced/terraform_nextcloud_vpn.md)
|
||||||
- [Pulumi](manual/documentation/system_administrators/pulumi/pulumi_readme.md)
|
- [Pulumi](system_administrators/pulumi/pulumi_readme.md)
|
||||||
- [Introduction to Pulumi](manual/documentation/system_administrators/pulumi/pulumi_intro.md)
|
- [Introduction to Pulumi](system_administrators/pulumi/pulumi_intro.md)
|
||||||
- [Installing Pulumi](manual/documentation/system_administrators/pulumi/pulumi_install.md)
|
- [Installing Pulumi](system_administrators/pulumi/pulumi_install.md)
|
||||||
- [Deployment Examples](manual/documentation/system_administrators/pulumi/pulumi_examples.md)
|
- [Deployment Examples](system_administrators/pulumi/pulumi_examples.md)
|
||||||
- [Deployment Details](manual/documentation/system_administrators/pulumi/pulumi_deployment_details.md)
|
- [Deployment Details](system_administrators/pulumi/pulumi_deployment_details.md)
|
||||||
- [Mycelium](manual/documentation/system_administrators/mycelium/mycelium_toc.md)
|
- [Mycelium](system_administrators/mycelium/mycelium_toc.md)
|
||||||
- [Overview](manual/documentation/system_administrators/mycelium/overview.md)
|
- [Overview](system_administrators/mycelium/overview.md)
|
||||||
- [Installation](manual/documentation/system_administrators/mycelium/installation.md)
|
- [Installation](system_administrators/mycelium/installation.md)
|
||||||
- [Additional Information](manual/documentation/system_administrators/mycelium/information.md)
|
- [Additional Information](system_administrators/mycelium/information.md)
|
||||||
- [Message](manual/documentation/system_administrators/mycelium/message.md)
|
- [Message](system_administrators/mycelium/message.md)
|
||||||
- [Packet](manual/documentation/system_administrators/mycelium/packet.md)
|
- [Packet](system_administrators/mycelium/packet.md)
|
||||||
- [Data Packet](manual/documentation/system_administrators/mycelium/data_packet.md)
|
- [Data Packet](system_administrators/mycelium/data_packet.md)
|
||||||
- [API YAML](manual/documentation/system_administrators/mycelium/api_yaml.md)
|
- [API YAML](system_administrators/mycelium/api_yaml.md)
|
||||||
- [Computer and IT Basics](manual/documentation/system_administrators/computer_it_basics/computer_it_basics.md)
|
- [Computer and IT Basics](system_administrators/computer_it_basics/computer_it_basics.md)
|
||||||
- [CLI and Scripts Basics](manual/documentation/system_administrators/computer_it_basics/cli_scripts_basics.md)
|
- [CLI and Scripts Basics](system_administrators/computer_it_basics/cli_scripts_basics.md)
|
||||||
- [Docker Basics](manual/documentation/system_administrators/computer_it_basics/docker_basics.md)
|
- [Docker Basics](system_administrators/computer_it_basics/docker_basics.md)
|
||||||
- [Git and GitHub Basics](manual/documentation/system_administrators/computer_it_basics/git_github_basics.md)
|
- [Git and GitHub Basics](system_administrators/computer_it_basics/git_github_basics.md)
|
||||||
- [Firewall Basics](manual/documentation/system_administrators/computer_it_basics/firewall_basics/firewall_basics.md)
|
- [Firewall Basics](system_administrators/computer_it_basics/firewall_basics/firewall_basics.md)
|
||||||
- [UFW Basics](manual/documentation/system_administrators/computer_it_basics/firewall_basics/ufw_basics.md)
|
- [UFW Basics](system_administrators/computer_it_basics/firewall_basics/ufw_basics.md)
|
||||||
- [Firewalld Basics](manual/documentation/system_administrators/computer_it_basics/firewall_basics/firewalld_basics.md)
|
- [Firewalld Basics](system_administrators/computer_it_basics/firewall_basics/firewalld_basics.md)
|
||||||
- [File Transfer](manual/documentation/system_administrators/computer_it_basics/file_transfer.md)
|
- [File Transfer](system_administrators/computer_it_basics/file_transfer.md)
|
||||||
- [Advanced](manual/documentation/system_administrators/advanced/advanced.md)
|
- [Advanced](system_administrators/advanced/advanced.md)
|
||||||
- [Token Transfer Keygenerator](manual/documentation/system_administrators/advanced/token_transfer_keygenerator.md)
|
- [Token Transfer Keygenerator](system_administrators/advanced/token_transfer_keygenerator.md)
|
||||||
- [Cancel Contracts](manual/documentation/system_administrators/advanced/cancel_contracts.md)
|
- [Cancel Contracts](system_administrators/advanced/cancel_contracts.md)
|
||||||
- [Contract Bills Reports](manual/documentation/system_administrators/advanced/contract_bill_report.md)
|
- [Contract Bills Reports](system_administrators/advanced/contract_bill_report.md)
|
||||||
- [Listing Free Public IPs](manual/documentation/system_administrators/advanced/list_public_ips.md)
|
- [Listing Free Public IPs](system_administrators/advanced/list_public_ips.md)
|
||||||
- [Redis](manual/documentation/system_administrators/advanced/grid3_redis.md)
|
- [Redis](system_administrators/advanced/grid3_redis.md)
|
||||||
- [IPFS](manual/documentation/system_administrators/advanced/ipfs/ipfs_toc.md)
|
- [IPFS](system_administrators/advanced/ipfs/ipfs_toc.md)
|
||||||
- [IPFS on a Full VM](manual/documentation/system_administrators/advanced/ipfs/ipfs_fullvm.md)
|
- [IPFS on a Full VM](system_administrators/advanced/ipfs/ipfs_fullvm.md)
|
||||||
- [IPFS on a Micro VM](manual/documentation/system_administrators/advanced/ipfs/ipfs_microvm.md)
|
- [IPFS on a Micro VM](system_administrators/advanced/ipfs/ipfs_microvm.md)
|
||||||
- [ThreeFold Token](manual/documentation/threefold_token/threefold_token.md)
|
- [ThreeFold Token](threefold_token/threefold_token.md)
|
||||||
- [TFT Bridges](manual/documentation/threefold_token/tft_bridges/tft_bridges.md)
|
- [TFT Bridges](threefold_token/tft_bridges/tft_bridges.md)
|
||||||
- [TFChain-Stellar Bridge](manual/documentation/threefold_token/tft_bridges/tfchain_stellar_bridge.md)
|
- [TFChain-Stellar Bridge](threefold_token/tft_bridges/tfchain_stellar_bridge.md)
|
||||||
- [BSC-Stellar Bridge](manual/documentation/threefold_token/tft_bridges/bsc_stellar_bridge.md)
|
- [BSC-Stellar Bridge](threefold_token/tft_bridges/bsc_stellar_bridge.md)
|
||||||
- [BSC-Stellar Bridge Verification](manual/documentation/threefold_token/tft_bridges/bsc_stellar_bridge_verification.md)
|
- [BSC-Stellar Bridge Verification](threefold_token/tft_bridges/bsc_stellar_bridge_verification.md)
|
||||||
- [Ethereum-Stellar Bridge](manual/documentation/threefold_token/tft_bridges/tft_ethereum/tft_ethereum.md)
|
- [Ethereum-Stellar Bridge](threefold_token/tft_bridges/tft_ethereum/tft_ethereum.md)
|
||||||
- [Storing TFT](manual/documentation/threefold_token/storing_tft/storing_tft.md)
|
- [Storing TFT](threefold_token/storing_tft/storing_tft.md)
|
||||||
- [ThreeFold Connect App - Stellar](manual/documentation/threefold_token/storing_tft/tf_connect_app.md)
|
- [ThreeFold Connect App - Stellar](threefold_token/storing_tft/tf_connect_app.md)
|
||||||
- [Lobstr Wallet - Stellar](manual/documentation/threefold_token/storing_tft/lobstr_wallet.md)
|
- [Lobstr Wallet - Stellar](threefold_token/storing_tft/lobstr_wallet.md)
|
||||||
- [MetaMask - BSC & ETH](manual/documentation/threefold_token/storing_tft/metamask.md)
|
- [MetaMask - BSC & ETH](threefold_token/storing_tft/metamask.md)
|
||||||
- [Hardware Wallet](manual/documentation/threefold_token/storing_tft/hardware_wallet.md)
|
- [Hardware Wallet](threefold_token/storing_tft/hardware_wallet.md)
|
||||||
- [Buy and Sell TFT](manual/documentation/threefold_token/buy_sell_tft/buy_sell_tft.md)
|
- [Buy and Sell TFT](threefold_token/buy_sell_tft/buy_sell_tft.md)
|
||||||
- [Quick Start - Stellar](manual/documentation/threefold_token/buy_sell_tft/tft_lobstr/tft_lobstr_short_guide.md)
|
- [Quick Start - Stellar](threefold_token/buy_sell_tft/tft_lobstr/tft_lobstr_short_guide.md)
|
||||||
- [Lobstr Wallet - Stellar](manual/documentation/threefold_token/buy_sell_tft/tft_lobstr/tft_lobstr_complete_guide.md)
|
- [Lobstr Wallet - Stellar](threefold_token/buy_sell_tft/tft_lobstr/tft_lobstr_complete_guide.md)
|
||||||
- [MetaMask - BSC & ETH](manual/documentation/threefold_token/buy_sell_tft/tft_metamask/tft_metamask.md)
|
- [MetaMask - BSC & ETH](threefold_token/buy_sell_tft/tft_metamask/tft_metamask.md)
|
||||||
- [Pancake Swap - BSC](manual/documentation/threefold_token/buy_sell_tft/pancakeswap.md)
|
- [Pancake Swap - BSC](threefold_token/buy_sell_tft/pancakeswap.md)
|
||||||
- [Liquidity Provider - LP](manual/documentation/threefold_token/liquidity/liquidity_readme.md)
|
- [Liquidity Provider - LP](threefold_token/liquidity/liquidity_readme.md)
|
||||||
- [Pancake Swap LP](manual/documentation/threefold_token/liquidity/liquidity_pancake.md)
|
- [Pancake Swap LP](threefold_token/liquidity/liquidity_pancake.md)
|
||||||
- [1inch.io LP](manual/documentation/threefold_token/liquidity/liquidity_1inch.md)
|
- [1inch.io LP](threefold_token/liquidity/liquidity_1inch.md)
|
||||||
- [Albedo LP](manual/documentation/threefold_token/liquidity/liquidity_albedo.md)
|
- [Albedo LP](threefold_token/liquidity/liquidity_albedo.md)
|
||||||
- [Transaction Fees](manual/documentation/threefold_token/transaction_fees.md)
|
- [Transaction Fees](threefold_token/transaction_fees.md)
|
||||||
- [FAQ](manual/documentation/faq/faq.md)
|
- [FAQ](manual/documentation/faq/faq.md)
|
||||||
- [Knowledge Base](manual/knowledge_base.md)
|
- [Knowledge Base](manual/knowledge_base.md)
|
||||||
- [About](manual/knowledge_base/about/about.md)
|
- [About](about/about.md)
|
||||||
- [ThreeFold History](manual/knowledge_base/about/threefold_history.md)
|
- [ThreeFold History](about/threefold_history.md)
|
||||||
- [Token History](manual/knowledge_base/about/token_history.md)
|
- [Token History](about/token_history.md)
|
||||||
- [Genesis Pool](manual/knowledge_base/about/genesis_pool.md)
|
- [Genesis Pool](about/genesis_pool.md)
|
||||||
- [Genesis Pool Dubai](manual/knowledge_base/about/genesis_pool_dubai.md)
|
- [Genesis Pool Dubai](about/genesis_pool_dubai.md)
|
||||||
- [Genesis Pool Ghent](manual/knowledge_base/about/genesis_pool_ghent.md)
|
- [Genesis Pool Ghent](about/genesis_pool_ghent.md)
|
||||||
- [Genesis Pool Details](manual/knowledge_base/about/genesis_block_pool_details.md)
|
- [Genesis Pool Details](about/genesis_block_pool_details.md)
|
||||||
- [ThreeFold Tech](manual/knowledge_base/about/threefold_tech.md)
|
- [ThreeFold Tech](about/threefold_tech.md)
|
||||||
- [Organisation Structure](manual/knowledge_base/about/orgstructure.md)
|
- [Organisation Structure](about/orgstructure.md)
|
||||||
- [Governance](manual/knowledge_base/about/governance.md)
|
- [Governance](about/governance.md)
|
||||||
- [ThreeFold Companies](manual/knowledge_base/about/threefold_companies.md)
|
- [ThreeFold Companies](about/threefold_companies.md)
|
||||||
- [ThreeFold Dubai](manual/knowledge_base/about/threefold_dubai.md)
|
- [ThreeFold Dubai](about/threefold_dubai.md)
|
||||||
- [ThreeFold VZW](manual/knowledge_base/about/threefold_vzw.md)
|
- [ThreeFold VZW](about/threefold_vzw.md)
|
||||||
- [ThreeFold AG](manual/knowledge_base/about/threefold_ag.md)
|
- [ThreeFold AG](about/threefold_ag.md)
|
||||||
- [Mazraa](manual/knowledge_base/about/mazraa.md)
|
- [Mazraa](about/mazraa.md)
|
||||||
- [BetterToken](manual/knowledge_base/about/bettertoken.md)
|
- [BetterToken](about/bettertoken.md)
|
||||||
- [DAO](manual/knowledge_base/about/dao/dao.md)
|
- [DAO](about/dao/dao.md)
|
||||||
- [ThreeFold DAO](manual/knowledge_base/about/dao/tfdao.md)
|
- [ThreeFold DAO](about/dao/tfdao.md)
|
||||||
- [TFChain](manual/knowledge_base/about/org_tfchain.md)
|
- [TFChain](about/org_tfchain.md)
|
||||||
- [ThreeFold Roadmap](manual/knowledge_base/about/roadmap/roadmap_readme.md)
|
- [ThreeFold Roadmap](about/roadmap/roadmap_readme.md)
|
||||||
- [Release Notes](manual/knowledge_base/about/roadmap/releasenotes/releasenotes_readme.md)
|
- [Release Notes](about/roadmap/releasenotes/releasenotes_readme.md)
|
||||||
- [TFGrid v3.10.0](manual/knowledge_base/about/roadmap/releasenotes/tfgrid_release_3_10_0.md)
|
- [TFGrid v3.10.0](about/roadmap/releasenotes/tfgrid_release_3_10_0.md)
|
||||||
- [TFGrid v3.9.0](manual/knowledge_base/about/roadmap/releasenotes/tfgrid_release_3_9_0.md)
|
- [TFGrid v3.9.0](about/roadmap/releasenotes/tfgrid_release_3_9_0.md)
|
||||||
- [TFGrid v3.8.0](manual/knowledge_base/about/roadmap/releasenotes/tfgrid_release_3_8_0.md)
|
- [TFGrid v3.8.0](about/roadmap/releasenotes/tfgrid_release_3_8_0.md)
|
||||||
- [TFGrid v3.7.0](manual/knowledge_base/about/roadmap/releasenotes/tfgrid_release_3_7_0.md)
|
- [TFGrid v3.7.0](about/roadmap/releasenotes/tfgrid_release_3_7_0.md)
|
||||||
- [TFGrid v3.6.1](manual/knowledge_base/about/roadmap/releasenotes/tfgrid_release_3_6_1.md)
|
- [TFGrid v3.6.1](about/roadmap/releasenotes/tfgrid_release_3_6_1.md)
|
||||||
- [TFGrid v3.6.0](manual/knowledge_base/about/roadmap/releasenotes/tfgrid_release_3_6_0.md)
|
- [TFGrid v3.6.0](about/roadmap/releasenotes/tfgrid_release_3_6_0.md)
|
||||||
- [TFGrid v3.0.0 Alpha-5](manual/knowledge_base/about/roadmap/releasenotes/tfgrid_release_3_0_a5.md)
|
- [TFGrid v3.0.0 Alpha-5](about/roadmap/releasenotes/tfgrid_release_3_0_a5.md)
|
||||||
- [TFGrid v3.0.0 Alpha-4](manual/knowledge_base/about/roadmap/releasenotes/tfgrid_release_3_0_a4.md)
|
- [TFGrid v3.0.0 Alpha-4](about/roadmap/releasenotes/tfgrid_release_3_0_a4.md)
|
||||||
- [TFGrid v3.0.0 Alpha-2](manual/knowledge_base/about/roadmap/releasenotes/tfgrid_release_3_0_a2.md)
|
- [TFGrid v3.0.0 Alpha-2](about/roadmap/releasenotes/tfgrid_release_3_0_a2.md)
|
||||||
- [TFGrid v3.0.0](manual/knowledge_base/about/roadmap/releasenotes/tfgrid_release_3_0.md)
|
- [TFGrid v3.0.0](about/roadmap/releasenotes/tfgrid_release_3_0.md)
|
||||||
- [ThreeFold Token](manual/knowledge_base/about/token_overview/token_overview.md)
|
- [ThreeFold Token](about/token_overview/token_overview.md)
|
||||||
- [Special Wallets](manual/knowledge_base/about/token_overview/special_wallets/stats_special_wallets.md)
|
- [Special Wallets](about/token_overview/special_wallets/stats_special_wallets.md)
|
||||||
- [Technology](manual/knowledge_base/technology/technology_toc.md)
|
- [Technology](technology/technology_toc.md)
|
||||||
- [How It Works](manual/knowledge_base/technology/grid3_howitworks.md)
|
- [How It Works](technology/grid3_howitworks.md)
|
||||||
- [Grid Concepts](manual/knowledge_base/technology/concepts/concepts_readme.md)
|
- [Grid Concepts](technology/concepts/concepts_readme.md)
|
||||||
- [TFGrid Primitives](manual/knowledge_base/technology/concepts/grid_primitives.md)
|
- [TFGrid Primitives](technology/concepts/grid_primitives.md)
|
||||||
- [TFGrid Component List](manual/knowledge_base/technology/concepts/grid3_components.md)
|
- [TFGrid Component List](technology/concepts/grid3_components.md)
|
||||||
- [Infrastructure as Code](manual/knowledge_base/technology/concepts/grid3_iac.md)
|
- [Infrastructure as Code](technology/concepts/grid3_iac.md)
|
||||||
- [Proof of Utilization](manual/knowledge_base/technology/concepts/proof_of_utilization.md)
|
- [Proof of Utilization](technology/concepts/proof_of_utilization.md)
|
||||||
- [Contract Grace Period](manual/knowledge_base/technology/concepts/contract_grace_period.md)
|
- [Contract Grace Period](technology/concepts/contract_grace_period.md)
|
||||||
- [What's New on TFGrid v3.x](manual/knowledge_base/technology/concepts/grid3_whatsnew.md)
|
- [What's New on TFGrid v3.x](technology/concepts/grid3_whatsnew.md)
|
||||||
- [TFChain](manual/knowledge_base/technology/concepts/concepts_tfchain.md)
|
- [TFChain](technology/concepts/concepts_tfchain.md)
|
||||||
- [TFGrid by Design](manual/knowledge_base/technology/concepts/tfgrid_by_design.md)
|
- [TFGrid by Design](technology/concepts/tfgrid_by_design.md)
|
||||||
- [Primitives](manual/knowledge_base/technology/primitives/primitives_toc.md)
|
- [Primitives](technology/primitives/primitives_toc.md)
|
||||||
- [Compute](manual/knowledge_base/technology/primitives/compute/compute_toc.md)
|
- [Compute](technology/primitives/compute/compute_toc.md)
|
||||||
- [ZKube](manual/knowledge_base/technology/primitives/compute/zkube.md)
|
- [ZKube](technology/primitives/compute/zkube.md)
|
||||||
- [ZMachine](manual/knowledge_base/technology/primitives/compute/zmachine.md)
|
- [ZMachine](technology/primitives/compute/zmachine.md)
|
||||||
- [CoreX](manual/knowledge_base/technology/primitives/compute/corex.md)
|
- [CoreX](technology/primitives/compute/corex.md)
|
||||||
- [Storage](manual/knowledge_base/technology/primitives/storage/storage_toc.md)
|
- [Storage](technology/primitives/storage/storage_toc.md)
|
||||||
- [ZOS Filesystem](manual/knowledge_base/technology/primitives/storage/zos_fs.md)
|
- [ZOS Filesystem](technology/primitives/storage/zos_fs.md)
|
||||||
- [ZOS Mount](manual/knowledge_base/technology/primitives/storage/zmount.md)
|
- [ZOS Mount](technology/primitives/storage/zmount.md)
|
||||||
- [Quantum Safe File System](manual/knowledge_base/technology/primitives/storage/qsfs.md)
|
- [Quantum Safe File System](technology/primitives/storage/qsfs.md)
|
||||||
- [Zero-DB](manual/knowledge_base/technology/primitives/storage/zdb.md)
|
- [Zero-DB](technology/primitives/storage/zdb.md)
|
||||||
- [Zero-Disk](manual/knowledge_base/technology/primitives/storage/zdisk.md)
|
- [Zero-Disk](technology/primitives/storage/zdisk.md)
|
||||||
- [Network](manual/knowledge_base/technology/primitives/network/network_toc.md)
|
- [Network](technology/primitives/network/network_toc.md)
|
||||||
- [ZNET](manual/knowledge_base/technology/primitives/network/znet.md)
|
- [ZNET](technology/primitives/network/znet.md)
|
||||||
- [ZNIC](manual/knowledge_base/technology/primitives/network/znic.md)
|
- [ZNIC](technology/primitives/network/znic.md)
|
||||||
- [WebGateway](manual/knowledge_base/technology/primitives/network/webgw3.md)
|
- [WebGateway](technology/primitives/network/webgw3.md)
|
||||||
- [Zero-OS Advantages](manual/knowledge_base/technology/zos/benefits/zos_advantages.md)
|
- [Zero-OS Advantages](technology/zos/benefits/zos_advantages.md)
|
||||||
- [Quantum Safe Storage](manual/knowledge_base/technology/qsss/qsss_home.md)
|
- [Quantum Safe Storage](technology/qsss/qsss_home.md)
|
||||||
- [Smart Contract IT](manual/knowledge_base/technology/smartcontract_it/smartcontract_toc.md)
|
- [Smart Contract IT](technology/smartcontract_it/smartcontract_toc.md)
|
||||||
- [Introduction](manual/knowledge_base/technology/smartcontract_it/smartcontract_tfgrid3.md)
|
- [Introduction](technology/smartcontract_it/smartcontract_tfgrid3.md)
|
||||||
- [Infrastructure As Code - IAC](manual/knowledge_base/technology/smartcontract_it/smartcontract_iac.md)
|
- [Infrastructure As Code - IAC](technology/smartcontract_it/smartcontract_iac.md)
|
||||||
- [3Bot Integration](manual/knowledge_base/technology/smartcontract_it/smartcontract_3bot.md)
|
- [3Bot Integration](technology/smartcontract_it/smartcontract_3bot.md)
|
||||||
- [Farming](manual/knowledge_base/farming/farming_toc.md)
|
- [Farming](farming/farming_toc.md)
|
||||||
- [Farming Rewards](manual/knowledge_base/farming/farming_reward.md)
|
- [Farming Rewards](farming/farming_reward.md)
|
||||||
- [Proof-of-Capacity](manual/knowledge_base/farming/proof_of_capacity.md)
|
- [Proof-of-Capacity](farming/proof_of_capacity.md)
|
||||||
- [Proof-of-Utilization](manual/knowledge_base/farming/proof_of_utilization.md)
|
- [Proof-of-Utilization](farming/proof_of_utilization.md)
|
||||||
- [PoC DAO Rules](manual/knowledge_base/farming/poc_dao_rules.md)
|
- [PoC DAO Rules](farming/poc_dao_rules.md)
|
||||||
- [Cloud](manual/knowledge_base/cloud/cloud_toc.md)
|
- [Cloud](cloud/cloud_toc.md)
|
||||||
- [Cloud Units](manual/knowledge_base/cloud/cloudunits.md)
|
- [Cloud Units](cloud/cloudunits.md)
|
||||||
- [Pricing](manual/knowledge_base/cloud/pricing/pricing_toc.md)
|
- [Pricing](cloud/pricing/pricing_toc.md)
|
||||||
- [Pricing Overview](manual/knowledge_base/cloud/pricing/pricing.md)
|
- [Pricing Overview](cloud/pricing/pricing.md)
|
||||||
- [Staking Discounts](manual/knowledge_base/cloud/pricing/staking_discount_levels.md)
|
- [Staking Discounts](cloud/pricing/staking_discount_levels.md)
|
||||||
- [Cloud Pricing Compare](manual/knowledge_base/cloud/pricing/cloud_pricing_compare.md)
|
- [Cloud Pricing Compare](cloud/pricing/cloud_pricing_compare.md)
|
||||||
- [Grid Billing](manual/knowledge_base/cloud/grid_billing/grid_billing.md)
|
- [Grid Billing](cloud/grid_billing/grid_billing.md)
|
||||||
- [Resource Units](manual/knowledge_base/cloud/resource_units_calc_cloudunits.md)
|
- [Resource Units](cloud/resource_units_calc_cloudunits.md)
|
||||||
- [Resource Units Advanced](manual/knowledge_base/cloud/resourceunits_advanced.md)
|
- [Resource Units Advanced](cloud/resourceunits_advanced.md)
|
||||||
- [Collaboration](manual/knowledge_base/collaboration/collaboration_toc.md)
|
- [Collaboration](collaboration/collaboration_toc.md)
|
||||||
- [How to Contribute](manual/knowledge_base/collaboration/contribute.md)
|
- [How to Contribute](collaboration/contribute.md)
|
||||||
- [Development Process](manual/knowledge_base/collaboration/development_process.md)
|
- [Development Process](collaboration/development_process.md)
|
||||||
- [Feature Request](manual/knowledge_base/collaboration/feature_request.md)
|
- [Feature Request](collaboration/feature_request.md)
|
||||||
- [Bug Report](manual/knowledge_base/collaboration/bug_report.md)
|
- [Bug Report](collaboration/bug_report.md)
|
||||||
- [Issue Labels](manual/knowledge_base/collaboration/issue_labels.md)
|
- [Issue Labels](collaboration/issue_labels.md)
|
||||||
- [Development Cycle](manual/knowledge_base/collaboration/development_cycle.md)
|
- [Development Cycle](collaboration/development_cycle.md)
|
||||||
- [Release Process](manual/knowledge_base/collaboration/release_process.md)
|
- [Release Process](collaboration/release_process.md)
|
||||||
- [Pull Request Template](manual/knowledge_base/collaboration/PULL_REQUEST_TEMPLATE.md)
|
- [Pull Request Template](collaboration/PULL_REQUEST_TEMPLATE.md)
|
||||||
- [Collaboration Tools](manual/knowledge_base/collaboration/collaboration_tools/collaboration_tools.md)
|
- [Collaboration Tools](collaboration/collaboration_tools/collaboration_tools.md)
|
||||||
- [Circle Tool](manual/knowledge_base/collaboration/collaboration_tools/circle_tool.md)
|
- [Circle Tool](collaboration/collaboration_tools/circle_tool.md)
|
||||||
- [Website Deployer](manual/knowledge_base/collaboration/collaboration_tools/website_tool.md)
|
- [Website Deployer](collaboration/collaboration_tools/website_tool.md)
|
||||||
- [Website Link Checker](manual/knowledge_base/collaboration/collaboration_tools/website_link_checker.md)
|
- [Website Link Checker](collaboration/collaboration_tools/website_link_checker.md)
|
||||||
- [How to Test](manual/knowledge_base/collaboration/testing/testing_readme.md)
|
- [How to Test](collaboration/testing/testing_readme.md)
|
||||||
- [TestLodge](manual/knowledge_base/collaboration/testing/testlodge.md)
|
- [TestLodge](collaboration/testing/testlodge.md)
|
||||||
- [Code of Conduct](manual/knowledge_base/collaboration/code_conduct.md)
|
- [Code of Conduct](collaboration/code_conduct.md)
|
||||||
- [Legal](manual/knowledge_base/legal/terms_conditions_all3.md)
|
- [Legal](manual_legal/terms_conditions_all3.md)
|
||||||
- [Disclaimer](manual/knowledge_base/legal/disclaimer.md)
|
- [Disclaimer](manual_legal/disclaimer.md)
|
||||||
- [Definitions](manual/knowledge_base/legal/definitions_legal.md)
|
- [Definitions](manual_legal/definitions_legal.md)
|
||||||
- [Privacy Policy](manual/knowledge_base/legal/privacypolicy.md)
|
- [Privacy Policy](manual_legal/privacypolicy.md)
|
||||||
- [Terms & Conditions](manual/knowledge_base/legal/terms_conditions/terms_conditions_toc.md)
|
- [Terms & Conditions](manual_legal/terms_conditions/terms_conditions_toc.md)
|
||||||
- [Terms & Conditions ThreeFold Related Websites](manual/knowledge_base/legal/terms_conditions/terms_conditions_websites.md)
|
- [Terms & Conditions ThreeFold Related Websites](manual_legal/terms_conditions/terms_conditions_websites.md)
|
||||||
- [Terms & Conditions TFGrid Users TFGrid 3](manual/knowledge_base/legal/terms_conditions/terms_conditions_griduser.md)
|
- [Terms & Conditions TFGrid Users TFGrid 3](manual_legal/terms_conditions/terms_conditions_griduser.md)
|
||||||
- [TFTA to TFT](manual/knowledge_base/legal/terms_conditions/tfta_to_tft.md)
|
- [TFTA to TFT](manual_legal/terms_conditions/tfta_to_tft.md)
|
||||||
- [Terms & Conditions TFGrid Farmers TFGrid 3](manual/knowledge_base/legal/terms_conditions/terms_conditions_farmer3.md)
|
- [Terms & Conditions TFGrid Farmers TFGrid 3](manual_legal/terms_conditions/terms_conditions_farmer3.md)
|
||||||
- [Terms & Conditions Sales](manual/knowledge_base/legal/terms_conditions/terms_conditions_sales.md)
|
- [Terms & Conditions Sales](manual_legal/terms_conditions/terms_conditions_sales.md)
|
||||||
13
collections/about/about.md
Normal file
13
collections/about/about.md
Normal file
@ -0,0 +1,13 @@
|
|||||||
|
<h1> About </h1>
|
||||||
|
|
||||||
|
This section of the manual covers information about ThreeFold, its history, its roadmap, its vision and more.
|
||||||
|
|
||||||
|
It's a good place to start if you want to have an overview of ThreeFold since its beginning.
|
||||||
|
|
||||||
|
<h2> Table of Contents </h2>
|
||||||
|
|
||||||
|
- [ThreeFold History](./threefold_history.md)
|
||||||
|
- [ThreeFold Tech](./threefold_tech.md)
|
||||||
|
- [Organisation Structure](./orgstructure.md)
|
||||||
|
- [ThreeFold Roadmap](./roadmap/roadmap_readme.md)
|
||||||
|
- [ThreeFold Token](./token_overview/token_overview.md)
|
||||||
33
collections/about/bettertoken.md
Normal file
33
collections/about/bettertoken.md
Normal file
@ -0,0 +1,33 @@
|
|||||||
|
<h1> BetterToken NV </h1>
|
||||||
|
|
||||||
|
<h2> Table of Contents </h2>
|
||||||
|
|
||||||
|
- [Introduction](#introduction)
|
||||||
|
- [Income](#income)
|
||||||
|
- [Structure](#structure)
|
||||||
|
- [Expected Changes](#expected-changes)
|
||||||
|
|
||||||
|
***
|
||||||
|
|
||||||
|
## Introduction
|
||||||
|
|
||||||
|
European Farming Cooperative for the foundation:
|
||||||
|
|
||||||
|
- Operates a data center in Lochristi (Belgium) offering hosting and connectivity for TF Farmers
|
||||||
|
- Currently, 100+ nodes – many of them are owned by TF farmers
|
||||||
|
- [ThreeFold Tech](./threefold_tech.md) NV uses some of their equipment today for development
|
||||||
|
- Sale of small servers to TF Farmers, was done mainly via an online webshop
|
||||||
|
|
||||||
|
## Income
|
||||||
|
|
||||||
|
- Hosting fees for the maintenance & running of the farmer pool
|
||||||
|
|
||||||
|
## Structure
|
||||||
|
|
||||||
|
- Started 30 November 2016
|
||||||
|
- [limited liable company in belgium](http://www.ejustice.just.fgov.be/tsv_pdf/2016/11/30/16324281.pdf)
|
||||||
|
- Peter Van der Henst is the managing director
|
||||||
|
|
||||||
|
## Expected Changes
|
||||||
|
|
||||||
|
BetterToken continues to be farming cooperative for Europe. Right now there is not much happening in BetterToken.
|
||||||
55
collections/about/dao/dao.md
Normal file
55
collections/about/dao/dao.md
Normal file
@ -0,0 +1,55 @@
|
|||||||
|
<h1> DAO </h1>
|
||||||
|
|
||||||
|
<h2>Table of Contents</h2>
|
||||||
|
|
||||||
|
- [Introduction](#introduction)
|
||||||
|
- [Overview of a DAO](#overview-of-a-dao)
|
||||||
|
- [Comparisons](#comparisons)
|
||||||
|
- [DAO Rules](#dao-rules)
|
||||||
|
- [DAO and Blockchain](#dao-and-blockchain)
|
||||||
|
|
||||||
|
***
|
||||||
|
|
||||||
|
## Introduction
|
||||||
|
|
||||||
|
We present the main concept of a DAO.
|
||||||
|
|
||||||
|
A DAO is a decentralized autonomous organization. To be more precise, this means the following:
|
||||||
|
|
||||||
|
- Decentralized = Online, global, uncensorable.
|
||||||
|
- Autonomous = Self-governing.
|
||||||
|
- Organization = Coordination & collaboration around shared objectives.
|
||||||
|
|
||||||
|
## Overview of a DAO
|
||||||
|
|
||||||
|
DAOs are an effective and safe way to work with like-minded folks around the globe.
|
||||||
|
|
||||||
|
Think of them like an internet-native business that's collectively owned and managed by its members. They have built-in treasuries that no one has the authority to access without the approval of the group. Decisions are governed by proposals and voting to ensure everyone in the organization has a voice.
|
||||||
|
|
||||||
|
This opens up so many new opportunities for global collaboration and coordination.
|
||||||
|
|
||||||
|
DAOs operate using smart contracts, which are essentially chunks of code that automatically execute whenever a set of criteria are met. These smart contracts establish the DAO’s rules. Those with a stake in a DAO then get voting rights and may influence how the organization operates by deciding on or creating new governance proposals.
|
||||||
|
|
||||||
|
## Comparisons
|
||||||
|
|
||||||
|
The following table provides some comparisons between a DAO and a traditional organization.
|
||||||
|
|
||||||
|
| DAO | A traditional organization |
|
||||||
|
| ----------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------- |
|
||||||
|
| Usually flat, and fully democratized. | Usually hierarchical. |
|
||||||
|
| Voting required by members for any changes to be implemented. | Depending on structure, changes can be demanded from a sole party, or voting may be offered. |
|
||||||
|
| Votes tallied, and outcome implemented automatically without trusted intermediary. | If voting is allowed, votes are tallied internally, and the outcome of voting must be handled manually. |
|
||||||
|
| Services offered are handled automatically in a decentralized manner (for example distribution of philanthropic funds). | Requires human handling, or centrally controlled automation, prone to manipulation. |
|
||||||
|
| All activity is transparent and fully public. | Requires human handling, or centrally controlled automation, prone to manipulation. |
|
||||||
|
|
||||||
|
*Info from https://ethereum.org/en/dao/, picture from https://cointelegraph.com/ethereum-for-beginners*
|
||||||
|
|
||||||
|
## DAO Rules
|
||||||
|
|
||||||
|
Decentralized autonomous organization (DAO), is an organization represented by rules encoded as a computer program that is transparent, controlled by the organization members and not influenced by a central government. A DAO's financial and voting transaction record and program rules are maintained on a blockchain.
|
||||||
|
|
||||||
|
## DAO and Blockchain
|
||||||
|
|
||||||
|
Decentralized autonomous organizations are typified by the use of blockchain technology to provide a secure digital ledger to track financial and other community interactions across the internet, hardened against forgery by trusted timestamping and dissemination of a distributed database. This approach eliminates the need to involve a mutually acceptable trusted third party in a transaction, simplifying the transaction. The costs of a blockchain-enabled transaction and of the associated data reporting may be substantially offset by the elimination of both the trusted third party and of the need for repetitive recording of contract exchanges in different records. For example, the blockchain data could, in principle and if regulatory structures permit it, replace public documents such as deeds and titles. In theory, a blockchain approach allows multiple cloud computing users to enter a loosely coupled peer-to-peer smart contract collaboration.
|
||||||
|
|
||||||
|
*Info from [here](https://en.wikipedia.org/wiki/Decentralized_autonomous_organization)*
|
||||||
33
collections/about/dao/dao_info.md
Normal file
33
collections/about/dao/dao_info.md
Normal file
@ -0,0 +1,33 @@
|
|||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
- Decentralized = Online, global, uncensorable.
|
||||||
|
- Autonomous = Self-governing.
|
||||||
|
- Organization = Coordination & collaboration around shared objectives.
|
||||||
|
|
||||||
|
DAOs are an effective and safe way to work with like-minded folks around the globe.
|
||||||
|
|
||||||
|
Think of them like an internet-native business that's collectively owned and managed by its members. They have built-in treasuries that no one has the authority to access without the approval of the group. Decisions are governed by proposals and voting to ensure everyone in the organization has a voice.
|
||||||
|
|
||||||
|
This opens up so many new opportunities for global collaboration and coordination.
|
||||||
|
|
||||||
|
DAOs operate using smart contracts, which are essentially chunks of code that automatically execute whenever a set of criteria are met. These smart contracts establish the DAO’s rules. Those with a stake in a DAO then get voting rights and may influence how the organization operates by deciding on or creating new governance proposals.
|
||||||
|
|
||||||
|
|
||||||
|
| DAO | A traditional organization |
|
||||||
|
| ----------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------- |
|
||||||
|
| Usually flat, and fully democratized. | Usually hierarchical. |
|
||||||
|
| Voting required by members for any changes to be implemented. | Depending on structure, changes can be demanded from a sole party, or voting may be offered. |
|
||||||
|
| Votes tallied, and outcome implemented automatically without trusted intermediary. | If voting is allowed, votes are tallied internally, and the outcome of voting must be handled manually. |
|
||||||
|
| Services offered are handled automatically in a decentralized manner (for example distribution of philanthropic funds). | Requires human handling, or centrally controlled automation, prone to manipulation. |
|
||||||
|
| All activity is transparent and fully public. | Requires human handling, or centrally controlled automation, prone to manipulation. |
|
||||||
|
|
||||||
|
*Info from https://ethereum.org/en/dao/, picture from https://cointelegraph.com/ethereum-for-beginners*
|
||||||
|
|
||||||
|
Decentralized autonomous organization (DAO), is an organization represented by rules encoded as a computer program that is transparent, controlled by the organization members and not influenced by a central government. A DAO's financial and voting transaction record and program rules are maintained on a blockchain.
|
||||||
|
|
||||||
|
Decentralized autonomous organizations are typified by the use of blockchain technology to provide a secure digital ledger to track financial and other community interactions across the internet, hardened against forgery by trusted timestamping and dissemination of a distributed database. This approach eliminates the need to involve a mutually acceptable trusted third party in a transaction, simplifying the transaction. The costs of a blockchain-enabled transaction and of the associated data reporting may be substantially offset by the elimination of both the trusted third party and of the need for repetitive recording of contract exchanges in different records. For example, the blockchain data could, in principle and if regulatory structures permit it, replace public documents such as deeds and titles. In theory, a blockchain approach allows multiple cloud computing users to enter a loosely coupled peer-to-peer smart contract collaboration.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
6
collections/about/dao/dao_more_info.md
Normal file
6
collections/about/dao/dao_more_info.md
Normal file
@ -0,0 +1,6 @@
|
|||||||
|
### More Info:
|
||||||
|
|
||||||
|
- [ThreeFold DAO](@tfdao).
|
||||||
|
- [Why are DAO's important](@dao_why)
|
||||||
|
- [ThreeFold Validators](@validators_faq).
|
||||||
|
- [Decentralization Info](@decentralization).
|
||||||
97
collections/about/dao/dao_why.md
Normal file
97
collections/about/dao/dao_why.md
Normal file
@ -0,0 +1,97 @@
|
|||||||
|
# What is a decentralized autonomous organization, and how does a DAO work?
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
A decentralized autonomous organization (DAO) is an entity with no central leadership. Decisions get made from the bottom-up, governed by a community organized around a specific set of rules enforced on a blockchain.
|
||||||
|
|
||||||
|
DAOs are internet-native organizations collectively owned and managed by their members. They have built-in treasuries that are only accessible with the approval of their members. Decisions are made via proposals the group votes on during a specified period.
|
||||||
|
|
||||||
|
A DAO works without hierarchical management and can have a large number of purposes. Freelancer networks where contracts pool their funds to pay for software subscriptions, charitable organizations where members approve donations and venture capital firms owned by a group are all possible with these organizations.
|
||||||
|
|
||||||
|
Before moving on, it’s important to distinguish a DAO, an internet-native organization, from The DAO, one of the first such organizations ever created. The DAO was a project founded in 2016 that ultimately failed and led to a dramatic split of the Ethereum network.
|
||||||
|
|
||||||
|
## How does a DAO work?
|
||||||
|
|
||||||
|
As mentioned above, a DAO is an organization where decisions get made from the bottom-up; a collective of members owns the organization. There are various ways to participate in a DAO, usually through the ownership of a token.
|
||||||
|
|
||||||
|
DAOs operate using smart contracts, which are essentially chunks of code that automatically execute whenever a set of criteria are met. Smart contracts are deployed on numerous blockchains nowadays, though Ethereum was the first to use them.
|
||||||
|
|
||||||
|
These smart contracts establish the DAO’s rules. Those with a stake in a DAO then get voting rights and may influence how the organization operates by deciding on or creating new governance proposals.
|
||||||
|
|
||||||
|
This model prevents DAOs from being spammed with proposals: A proposal will only pass once the majority of stakeholders approve it. How that majority is determined varies from DAO to DAO and is specified in the smart contracts.
|
||||||
|
|
||||||
|
DAOs are fully autonomous and transparent. As they are built on open-source blockchains, anyone can view their code. Anyone can also audit their built-in treasuries, as the blockchain records all financial transactions.
|
||||||
|
|
||||||
|
Typically, a DAO launch occurs in three major steps
|
||||||
|
Smart contract creation: First, a developer or group of developers must create the smart contract behind the DAO. After launch, they can only change the rules set by these contracts through the governance system. That means they must extensively test the contracts to ensure they don’t overlook important details.
|
||||||
|
|
||||||
|
Funding: After the smart contracts have been created, the DAO needs to determine a way to receive funding and how to enact governance. More often than not, tokens are sold to raise funds; these tokens give holders voting rights.
|
||||||
|
|
||||||
|
Deployment: Once everything is set up, the DAO needs to be deployed on the blockchain. From this point on, stakeholders decide on the future of the organization. The organization’s creators — those who wrote the smart contracts — no longer influence the project any more than other stakeholders.
|
||||||
|
|
||||||
|
## Why do we need DAOs?
|
||||||
|
|
||||||
|
Being internet-native organizations, DAOs have several advantages over traditional organizations. One significant advantage of DAOs is the lack of trust needed between two parties. While a traditional organization requires a lot of trust in the people behind it — especially on behalf of investors — with DAOs, only the code needs to be trusted.
|
||||||
|
|
||||||
|
Trusting that code is easier to do as it’s publicly available and can be extensively tested before launch. Every action a DAO takes after being launched has to be approved by the community and is completely transparent and verifiable.
|
||||||
|
|
||||||
|
Such an organization has no hierarchical structure. Yet, it can still accomplish tasks and grow while being controlled by stakeholders via its native token. The lack of a hierarchy means any stakeholder can put forward an innovative idea that the entire group will consider and improve upon. Internal disputes are often easily solved through the voting system, in line with the pre-written rules in the smart contract.
|
||||||
|
|
||||||
|
By allowing investors to pool funds, DAOs also give them a chance to invest in early-stage startups and decentralized projects while sharing the risk or any profits that may come out of them.
|
||||||
|
|
||||||
|
## The principal-agent dilemma
|
||||||
|
|
||||||
|
The main advantage of DAOs is that they offer a solution to the principal-agent dilemma. This dilemma is a conflict in priorities between a person or group (the principal) and those making decisions and acting on their behalf (the agent).
|
||||||
|
|
||||||
|
Problems can occur in some situations, with a common one being in the relationship between stakeholders and a CEO. The agent (the CEO) may work in a way that’s not in line with the priorities and goals determined by the principal (the stakeholders) and instead act in their own self-interest.
|
||||||
|
|
||||||
|
Another typical example of the principal-agent dilemma occurs when the agent takes excessive risk because the principal bears the burden. For example, a trader can use extreme leverage to chase a performance bonus, knowing the organization will cover any downside.
|
||||||
|
|
||||||
|
DAOs solve the principal-agent dilemma through community governance. Stakeholders aren’t forced to join a DAO and only do so after understanding the rules that govern it. They don’t need to trust any agent acting on their behalf and instead work as part of a group whose incentives are aligned.
|
||||||
|
|
||||||
|
Token holders’ interests align as the nature of a DAO incentivizes them not to be malicious. Since they have a stake in the network, they will want to see it succeed. Acting against it would be acting against their self-interests.
|
||||||
|
|
||||||
|
## What was The DAO?
|
||||||
|
|
||||||
|
The DAO was an early iteration of modern decentralized autonomous organizations. It was launched back in 2016 and designed to be an automated organization that acted as a form of venture capital fund.
|
||||||
|
|
||||||
|
Those who owned DAO tokens could profit from the organization’s investments by either reaping dividends or benefitting from price appreciation of the tokens. The DAO was initially seen as a revolutionary project and raised $150 million in Ether (ETH), one of the greatest crowdfunding efforts of the time.
|
||||||
|
|
||||||
|
The DAO launched on April 30, 2016, after Ethereum protocol engineer Christoph Jentzsch released the open-source code for an Ethereum-based investment organization. Investors bought DAO tokens by moving Ether to its smart contracts.
|
||||||
|
|
||||||
|
A few days into the token sale, some developers expressed concerns that a bug in The DAO’s smart contracts could allow malicious actors to drain its funds. While a governance proposal was set forth to fix the bug, an attacker took advantage of it and siphoned over $60 million worth of ETH from The DAO’s wallet.
|
||||||
|
|
||||||
|
At the time, around 14% of all ETH in circulation was invested in The DAO. The hack was a significant blow to DAOs in general and the then one-year-old Ethereum network. A debate within the Ethereum community ensued as everyone scrambled to figure out what to do. Initially, Ethereum co-founder Vitalik Buterin proposed a soft fork that would blacklist the attacker’s address and prevent them from moving the funds.
|
||||||
|
|
||||||
|
The attacker or someone posing as them then responded to that proposal, claiming the funds had been obtained in a “legal” way according to the smart contract’s rules. They claimed they were ready to take legal action against anyone who tried to seize the funds.
|
||||||
|
|
||||||
|
The hacker even threatened to bribe ETH miners with some of the stolen funds to thwart a soft fork attempt. In the debate that ensued, a hard fork was determined to be the solution. That hard fork was implemented to roll back the Ethereum network’s history to before The DAO was hacked and reallocate the stolen funds to a smart contract that allowed investors to withdraw them. Those who disagreed with the move rejected the hard fork and supported an earlier version of the network, known as Ethereum Classic (ETC).
|
||||||
|
|
||||||
|
## Disadvantages of DAOs
|
||||||
|
|
||||||
|
Decentralized autonomous organizations aren’t perfect. They are an extremely new technology that has attracted much criticism due to lingering concerns regarding their legality, security and structure.
|
||||||
|
|
||||||
|
MIT Technology Review has, for example, revealed it considers it a bad idea to trust the masses with important financial decisions. While MIT shared its thoughts back in 2016, the organization appears to have never changed its mind on DAOs — at not least publicly. The DAO hack also raised security concerns, as flaws in smart contracts can be hard to fix even after they are spotted.
|
||||||
|
|
||||||
|
DAOs can be distributed across multiple jurisdictions, and there’s no legal framework for them. Any legal issues that may arise will likely require those involved to deal with numerous regional laws in a complicated legal battle.
|
||||||
|
|
||||||
|
In July 2017, for example, the United States Securities and Exchange Commission issued a report in which it determined that The DAO sold securities in the form of tokens on the Ethereum blockchain without authorization, violating portions of securities law in the country.
|
||||||
|
|
||||||
|
## Examples of DAOs
|
||||||
|
|
||||||
|
Decentralized autonomous organizations have gained traction over the last few years and are now fully incorporated into many blockchain projects. The decentralized finance (DeFi) space uses DAOs to allow applications to become fully decentralized, for example.
|
||||||
|
|
||||||
|
To some, the Bitcoin (BTC) network is the earliest example of a DAO there is. The network scales via community agreement, even though most network participants have never met each other. It also does not have an organized governance mechanism, and instead, miners and nodes have to signal support.
|
||||||
|
|
||||||
|
However, Bitcoin is not seen as a DAO by today’s standards. By current measures, Dash would be the first true DAO, as the project has a governance mechanism that allows stakeholders to vote on the use of its treasury.
|
||||||
|
|
||||||
|
Other, more advanced DAOs, including decentralized networks built on top of the Ethereum blockchain, are responsible for launching cryptocurrency-backed stablecoins. In some cases, the organizations that initially launched these DAOs slowly give away control of the project to one day become irrelevant. Token holders can actively vote on governance proposals to hire new contributors, add new tokens as collateral for their coins or adjust other parameters.
|
||||||
|
|
||||||
|
In 2020, a DeFi lending protocol launched its own governance token and distributed it through a liquidity mining process. Essentially, anyone who interacted with the protocol would receive tokens as a reward. Other projects have since replicated and adapted the model.
|
||||||
|
|
||||||
|
Now, the list of DAOs is extensive. Over time, it has become a clear concept that has been gaining traction. Some projects are still looking to achieve complete decentralization through the DAO model, but it’s worth pointing out they are only a few years old and have yet to achieve their final goals and objectives.
|
||||||
|
|
||||||
|
As internet-native organizations, DAOs have the potential to change the way corporate governance works completely. While the concept matures and the legal gray area they operate in is cleared, more and more organizations may adopt a DAO model to help govern some of their activities.
|
||||||
|
|
||||||
|
|
||||||
|
> info from: https://cointelegraph.com/ethereum-for-beginners/what-is-a-decentralized-autonomous-organization-and-how-does-a-dao-work
|
||||||
14
collections/about/dao/gep.md
Normal file
14
collections/about/dao/gep.md
Normal file
@ -0,0 +1,14 @@
|
|||||||
|
# Grid Enhancement Proposal
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
GEP stands for Grid Enhancement Proposal. A GEP is a design document providing information to the ThreeFold community, or describing a new feature for the TFGrid or its processes or environment. The GEP should provide a concise technical specification of the feature and a rationale for the feature.
|
||||||
|
|
||||||
|
- A GEP gets registered in TFChain. TFDAO makes this possible
|
||||||
|
- Community has to approve or not a GEP
|
||||||
|
- Once enough consensus achieved the GEP will be executed upon, whereas "consensus" is a variable % per GEP and will be defined when sepcs are ready.
|
||||||
|
- Validator Nodes of our L1 TFChain will make sure GEP is properly implemented and consensus also achieved on that level.
|
||||||
|
|
||||||
|
*some inspiration comes from https://www.python.org/dev/peps/pep-0001*
|
||||||
|
|
||||||
|
!!!def alias:gep
|
||||||
BIN
collections/about/dao/img/dao_whatis_.jpg
Normal file
BIN
collections/about/dao/img/dao_whatis_.jpg
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 414 KiB |
BIN
collections/about/dao/img/gep.png
Normal file
BIN
collections/about/dao/img/gep.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 50 KiB |
138
collections/about/dao/tfdao.md
Normal file
138
collections/about/dao/tfdao.md
Normal file
@ -0,0 +1,138 @@
|
|||||||
|
<h1> ThreeFold DAO </h1>
|
||||||
|
|
||||||
|
<h2>Table of Contents</h2>
|
||||||
|
|
||||||
|
- [Introduction](#introduction)
|
||||||
|
- [DAO Tasks](#dao-tasks)
|
||||||
|
- [What is a DAO?](#what-is-a-dao)
|
||||||
|
- [How does a DAO work?](#how-does-a-dao-work)
|
||||||
|
- [Why do we need DAOs?](#why-do-we-need-daos)
|
||||||
|
- [The principal-agent dilemma](#the-principal-agent-dilemma)
|
||||||
|
- [What was The DAO?](#what-was-the-dao)
|
||||||
|
- [Disadvantages of DAOs](#disadvantages-of-daos)
|
||||||
|
- [Examples of DAOs](#examples-of-daos)
|
||||||
|
|
||||||
|
***
|
||||||
|
|
||||||
|
## Introduction
|
||||||
|
|
||||||
|
The ThreeFold DAO allows autonomous operation of the TFChain and TFGrid.
|
||||||
|
|
||||||
|
## DAO Tasks
|
||||||
|
|
||||||
|
Amongst others the DAO needs to arrange
|
||||||
|
|
||||||
|
| Utility Token model | |
|
||||||
|
| -------------------------------------------- | ------------------------------------------ |
|
||||||
|
| [Proof Of Capacity](../../farming/proof_of_capacity.md) | Farming (creation) of TFT |
|
||||||
|
| [Proof Of Utilization](../../farming/proof_of_utilization.md) | Utilization (burning, distribution) of TFT |
|
||||||
|
|
||||||
|
As well as
|
||||||
|
|
||||||
|
- distribution of TFT grants
|
||||||
|
- manage code upgrade of TFChain and ZOS
|
||||||
|
- approval for changes to anything in our ecosystem, by means of GEP e.g.
|
||||||
|
- changes to tokenomics e.g. changes related to
|
||||||
|
- farming rewards
|
||||||
|
- cultivation flows
|
||||||
|
- pricing of grid capacity
|
||||||
|
- new features in TFChain
|
||||||
|
- rewards for sales channels, solution providers (v3.2+)
|
||||||
|
|
||||||
|
## What is a DAO?
|
||||||
|
|
||||||
|
A decentralized autonomous organization (DAO) is an entity with no central leadership. Decisions get made from the bottom-up, governed by a community organized around a specific set of rules enforced on a blockchain.
|
||||||
|
|
||||||
|
DAOs are internet-native organizations collectively owned and managed by their members. They have built-in treasuries that are only accessible with the approval of their members. Decisions are made via proposals the group votes on during a specified period.
|
||||||
|
|
||||||
|
A DAO works without hierarchical management and can have a large number of purposes. Freelancer networks where contracts pool their funds to pay for software subscriptions, charitable organizations where members approve donations and venture capital firms owned by a group are all possible with these organizations.
|
||||||
|
|
||||||
|
Before moving on, it’s important to distinguish a DAO, an internet-native organization, from The DAO, one of the first such organizations ever created. The DAO was a project founded in 2016 that ultimately failed and led to a dramatic split of the Ethereum network.
|
||||||
|
|
||||||
|
## How does a DAO work?
|
||||||
|
|
||||||
|
As mentioned above, a DAO is an organization where decisions get made from the bottom-up; a collective of members owns the organization. There are various ways to participate in a DAO, usually through the ownership of a token.
|
||||||
|
|
||||||
|
DAOs operate using smart contracts, which are essentially chunks of code that automatically execute whenever a set of criteria are met. Smart contracts are deployed on numerous blockchains nowadays, though Ethereum was the first to use them.
|
||||||
|
|
||||||
|
These smart contracts establish the DAO’s rules. Those with a stake in a DAO then get voting rights and may influence how the organization operates by deciding on or creating new governance proposals.
|
||||||
|
|
||||||
|
This model prevents DAOs from being spammed with proposals: A proposal will only pass once the majority of stakeholders approve it. How that majority is determined varies from DAO to DAO and is specified in the smart contracts.
|
||||||
|
|
||||||
|
DAOs are fully autonomous and transparent. As they are built on open-source blockchains, anyone can view their code. Anyone can also audit their built-in treasuries, as the blockchain records all financial transactions.
|
||||||
|
|
||||||
|
Typically, a DAO launch occurs in three major steps
|
||||||
|
Smart contract creation: First, a developer or group of developers must create the smart contract behind the DAO. After launch, they can only change the rules set by these contracts through the governance system. That means they must extensively test the contracts to ensure they don’t overlook important details.
|
||||||
|
|
||||||
|
Funding: After the smart contracts have been created, the DAO needs to determine a way to receive funding and how to enact governance. More often than not, tokens are sold to raise funds; these tokens give holders voting rights.
|
||||||
|
|
||||||
|
Deployment: Once everything is set up, the DAO needs to be deployed on the blockchain. From this point on, stakeholders decide on the future of the organization. The organization’s creators — those who wrote the smart contracts — no longer influence the project any more than other stakeholders.
|
||||||
|
|
||||||
|
## Why do we need DAOs?
|
||||||
|
|
||||||
|
Being internet-native organizations, DAOs have several advantages over traditional organizations. One significant advantage of DAOs is the lack of trust needed between two parties. While a traditional organization requires a lot of trust in the people behind it — especially on behalf of investors — with DAOs, only the code needs to be trusted.
|
||||||
|
|
||||||
|
Trusting that code is easier to do as it’s publicly available and can be extensively tested before launch. Every action a DAO takes after being launched has to be approved by the community and is completely transparent and verifiable.
|
||||||
|
|
||||||
|
Such an organization has no hierarchical structure. Yet, it can still accomplish tasks and grow while being controlled by stakeholders via its native token. The lack of a hierarchy means any stakeholder can put forward an innovative idea that the entire group will consider and improve upon. Internal disputes are often easily solved through the voting system, in line with the pre-written rules in the smart contract.
|
||||||
|
|
||||||
|
By allowing investors to pool funds, DAOs also give them a chance to invest in early-stage startups and decentralized projects while sharing the risk or any profits that may come out of them.
|
||||||
|
|
||||||
|
## The principal-agent dilemma
|
||||||
|
|
||||||
|
The main advantage of DAOs is that they offer a solution to the principal-agent dilemma. This dilemma is a conflict in priorities between a person or group (the principal) and those making decisions and acting on their behalf (the agent).
|
||||||
|
|
||||||
|
Problems can occur in some situations, with a common one being in the relationship between stakeholders and a CEO. The agent (the CEO) may work in a way that’s not in line with the priorities and goals determined by the principal (the stakeholders) and instead act in their own self-interest.
|
||||||
|
|
||||||
|
Another typical example of the principal-agent dilemma occurs when the agent takes excessive risk because the principal bears the burden. For example, a trader can use extreme leverage to chase a performance bonus, knowing the organization will cover any downside.
|
||||||
|
|
||||||
|
DAOs solve the principal-agent dilemma through community governance. Stakeholders aren’t forced to join a DAO and only do so after understanding the rules that govern it. They don’t need to trust any agent acting on their behalf and instead work as part of a group whose incentives are aligned.
|
||||||
|
|
||||||
|
Token holders’ interests align as the nature of a DAO incentivizes them not to be malicious. Since they have a stake in the network, they will want to see it succeed. Acting against it would be acting against their self-interests.
|
||||||
|
|
||||||
|
## What was The DAO?
|
||||||
|
|
||||||
|
The DAO was an early iteration of modern decentralized autonomous organizations. It was launched back in 2016 and designed to be an automated organization that acted as a form of venture capital fund.
|
||||||
|
|
||||||
|
Those who owned DAO tokens could profit from the organization’s investments by either reaping dividends or benefitting from price appreciation of the tokens. The DAO was initially seen as a revolutionary project and raised $150 million in Ether (ETH), one of the greatest crowdfunding efforts of the time.
|
||||||
|
|
||||||
|
The DAO launched on April 30, 2016, after Ethereum protocol engineer Christoph Jentzsch released the open-source code for an Ethereum-based investment organization. Investors bought DAO tokens by moving Ether to its smart contracts.
|
||||||
|
|
||||||
|
A few days into the token sale, some developers expressed concerns that a bug in The DAO’s smart contracts could allow malicious actors to drain its funds. While a governance proposal was set forth to fix the bug, an attacker took advantage of it and siphoned over $60 million worth of ETH from The DAO’s wallet.
|
||||||
|
|
||||||
|
At the time, around 14% of all ETH in circulation was invested in The DAO. The hack was a significant blow to DAOs in general and the then one-year-old Ethereum network. A debate within the Ethereum community ensued as everyone scrambled to figure out what to do. Initially, Ethereum co-founder Vitalik Buterin proposed a soft fork that would blacklist the attacker’s address and prevent them from moving the funds.
|
||||||
|
|
||||||
|
The attacker or someone posing as them then responded to that proposal, claiming the funds had been obtained in a “legal” way according to the smart contract’s rules. They claimed they were ready to take legal action against anyone who tried to seize the funds.
|
||||||
|
|
||||||
|
The hacker even threatened to bribe ETH miners with some of the stolen funds to thwart a soft fork attempt. In the debate that ensued, a hard fork was determined to be the solution. That hard fork was implemented to roll back the Ethereum network’s history to before The DAO was hacked and reallocate the stolen funds to a smart contract that allowed investors to withdraw them. Those who disagreed with the move rejected the hard fork and supported an earlier version of the network, known as Ethereum Classic (ETC).
|
||||||
|
|
||||||
|
## Disadvantages of DAOs
|
||||||
|
|
||||||
|
Decentralized autonomous organizations aren’t perfect. They are an extremely new technology that has attracted much criticism due to lingering concerns regarding their legality, security and structure.
|
||||||
|
|
||||||
|
MIT Technology Review has, for example, revealed it considers it a bad idea to trust the masses with important financial decisions. While MIT shared its thoughts back in 2016, the organization appears to have never changed its mind on DAOs — at not least publicly. The DAO hack also raised security concerns, as flaws in smart contracts can be hard to fix even after they are spotted.
|
||||||
|
|
||||||
|
DAOs can be distributed across multiple jurisdictions, and there’s no legal framework for them. Any legal issues that may arise will likely require those involved to deal with numerous regional laws in a complicated legal battle.
|
||||||
|
|
||||||
|
In July 2017, for example, the United States Securities and Exchange Commission issued a report in which it determined that The DAO sold securities in the form of tokens on the Ethereum blockchain without authorization, violating portions of securities law in the country.
|
||||||
|
|
||||||
|
## Examples of DAOs
|
||||||
|
|
||||||
|
Decentralized autonomous organizations have gained traction over the last few years and are now fully incorporated into many blockchain projects. The decentralized finance (DeFi) space uses DAOs to allow applications to become fully decentralized, for example.
|
||||||
|
|
||||||
|
To some, the Bitcoin (BTC) network is the earliest example of a DAO there is. The network scales via community agreement, even though most network participants have never met each other. It also does not have an organized governance mechanism, and instead, miners and nodes have to signal support.
|
||||||
|
|
||||||
|
However, Bitcoin is not seen as a DAO by today’s standards. By current measures, Dash would be the first true DAO, as the project has a governance mechanism that allows stakeholders to vote on the use of its treasury.
|
||||||
|
|
||||||
|
Other, more advanced DAOs, including decentralized networks built on top of the Ethereum blockchain, are responsible for launching cryptocurrency-backed stablecoins. In some cases, the organizations that initially launched these DAOs slowly give away control of the project to one day become irrelevant. Token holders can actively vote on governance proposals to hire new contributors, add new tokens as collateral for their coins or adjust other parameters.
|
||||||
|
|
||||||
|
In 2020, a DeFi lending protocol launched its own governance token and distributed it through a liquidity mining process. Essentially, anyone who interacted with the protocol would receive tokens as a reward. Other projects have since replicated and adapted the model.
|
||||||
|
|
||||||
|
Now, the list of DAOs is extensive. Over time, it has become a clear concept that has been gaining traction. Some projects are still looking to achieve complete decentralization through the DAO model, but it’s worth pointing out they are only a few years old and have yet to achieve their final goals and objectives.
|
||||||
|
|
||||||
|
As internet-native organizations, DAOs have the potential to change the way corporate governance works completely. While the concept matures and the legal gray area they operate in is cleared, more and more organizations may adopt a DAO model to help govern some of their activities.
|
||||||
|
|
||||||
|
|
||||||
|
> info from: https://cointelegraph.com/ethereum-for-beginners/what-is-a-decentralized-autonomous-organization-and-how-does-a-dao-work
|
||||||
|
|
||||||
|
|
||||||
69
collections/about/genesis_block_pool_details.md
Normal file
69
collections/about/genesis_block_pool_details.md
Normal file
@ -0,0 +1,69 @@
|
|||||||
|
<h1> Genesis Pool Details </h1>
|
||||||
|
|
||||||
|
<h2>Table of Contents </h2>
|
||||||
|
|
||||||
|
- [Genesis Pool](#genesis-pool)
|
||||||
|
- [Genesis Block](#genesis-block)
|
||||||
|
- [Genesis Block Value](#genesis-block-value)
|
||||||
|
- [Calculation](#calculation)
|
||||||
|
- [Genesis Pool Details](#genesis-pool-details)
|
||||||
|
|
||||||
|
***
|
||||||
|
|
||||||
|
## Genesis Pool
|
||||||
|
|
||||||
|
Genesis pool is the initial capacity with which the network started, was available when the project officially launched (blockchain launch March 2018).
|
||||||
|
|
||||||
|
- +-300 computer (all owned by ThreeFold_Dubai)
|
||||||
|
- Belgium: 117+30 (hosted by BetterToken)
|
||||||
|
- Dubai: 148 (hosted by TF FZC itself)
|
||||||
|
- total estimate resource/compute units
|
||||||
|
- CRU: 4800,
|
||||||
|
- HRU: 8100000
|
||||||
|
- MRU: 18600
|
||||||
|
- SRU: 106000
|
||||||
|
|
||||||
|
## Genesis Block
|
||||||
|
|
||||||
|
Genesis block is the first block registered in the blockchain. This consists of a number of TFT, in our case 695M TFT.
|
||||||
|
|
||||||
|
> Maximum amount of tokens in the ThreeFold Blockchain at launch = 100 Billion (in other words genesis pool < 1% at start of max nr TFT)
|
||||||
|
|
||||||
|
### Genesis Block Value
|
||||||
|
|
||||||
|
It's hard to define the value of the genesis block when it was calculated, there was no established TFT price.
|
||||||
|
|
||||||
|
- If TFT price = USD 0.01: +-7M USD (this token price has not been established but could be 2016-17)
|
||||||
|
- Summer 2023 the price is back on USD 0.01, which we believe is too low for the value created, lets hope for a better future.
|
||||||
|
|
||||||
|
### Calculation
|
||||||
|
|
||||||
|
To come up with a reasonable number and show the community that there was hardware available for the genesis block, we made an excel calculation.
|
||||||
|
|
||||||
|
- Servers as part of genesis pool calculation
|
||||||
|
- +-300 computer (all owned by ThreeFold_Dubai)
|
||||||
|
- Belgium: 117+30 (hosted by BetterToken)
|
||||||
|
- Dubai: 148 (hosted by TF FZC itself)
|
||||||
|
- Hardware as used in many years before token launch (March 2018)
|
||||||
|
- At least 100+ servers over quite some years
|
||||||
|
- Total estimate resource/compute units
|
||||||
|
- CRU: 4,800
|
||||||
|
- HRU: 8,100,000
|
||||||
|
- MRU: 18,600
|
||||||
|
- SRU: 106,000
|
||||||
|
- Cloud Units
|
||||||
|
- Results in 3,927 CU and 8,225 SU
|
||||||
|
- The farming rules used were farming/minting rules v1 but with no difficulty level and TFT price 0.01
|
||||||
|
- Duration
|
||||||
|
- We took +- 1.5 years in our calculation
|
||||||
|
- Averaged out, it's for sure not exact science
|
||||||
|
- But we can say that the amount of capacity listed has been available long enough for our engineers during the pre-launch period. Probably not with those exact listed servers but in general.
|
||||||
|
- Result: **695M TFT**
|
||||||
|
|
||||||
|
_The purpose of this exercise is to demonstrate there is a reasoning behind the 695M TFT and computers which have been available. It's not intended as exact proof nor defense. We believe the value given was in line with the situation at that time._
|
||||||
|
|
||||||
|
## Genesis Pool Details
|
||||||
|
|
||||||
|
- Block 0: [Block 0 on Explorer](https://explorer2.threefoldtoken.com/hash.html?hash=a2ee0aa706c9de46ec57dbba1af8d352fbcc3cc5e9626fc56337fd5e9ca44c8d)
|
||||||
|
- Genesis Block Code: [Code of Block 0](https://github.com/threefoldfoundation/tfchain/blob/master/pkg/config/config.go#L103)
|
||||||
|
|
||||||
70
collections/about/genesis_pool.md
Normal file
70
collections/about/genesis_pool.md
Normal file
@ -0,0 +1,70 @@
|
|||||||
|
<h1> Genesis Pool </h1>
|
||||||
|
|
||||||
|
<h2>Table of Contents </h2>
|
||||||
|
|
||||||
|
- [Introduction](#introduction)
|
||||||
|
- [Genesis Pool Token Usage](#genesis-pool-token-usage)
|
||||||
|
- [Remarks](#remarks)
|
||||||
|
|
||||||
|
***
|
||||||
|
|
||||||
|
## Introduction
|
||||||
|
|
||||||
|
At the end of March 2018, ThreeFold launched the public blockchain.
|
||||||
|
|
||||||
|
ThreeFold developed their own blockchain software called Rivine, which was probably the first proof of blockstake blockchain in the world. We did not like the way how the other blockchains at that time were doing proof of work, which is basically burning a lot of energy to prove the validity of their blockchain.
|
||||||
|
|
||||||
|
Rivine is a fork from the blockchain work done by the team of SIA and since then a lot of work has been done on it to fulfill our own requirements. The Rivine blockchain will no longer be used after May 2020.
|
||||||
|
|
||||||
|
ThreeFold is the result of more than 20 years of work in the Internet space, over a number of companies.
|
||||||
|
|
||||||
|
The technology used at start in March 2018 has been developed mainly out of three companies: ThreeFold_Dubai, BetterToken(bettertoken) and GreenIT Globe. Later in 2018, TF Tech was spun off from our incubator.
|
||||||
|
|
||||||
|
TF Tech is a company born out of our Incubator called [Incubaid](http://www.incubaid.com/) in Belgium.
|
||||||
|
|
||||||
|
TF Tech has a purpose to further develop the software and commercialize the capabilities on a global basis, mainly by working together with tech partners.
|
||||||
|
|
||||||
|
The public version of our blockchain was started March 2018. The servers used during development and mining tokens already started years before.
|
||||||
|
|
||||||
|
Many hundreds of servers have been used to develop the technology which now makes up our ThreeFold_Grid.
|
||||||
|
|
||||||
|
+-300 servers are the foundation of our TF Grid.
|
||||||
|
|
||||||
|
Most of the servers are in Dubai and in Ghent (Belgium).
|
||||||
|
|
||||||
|
- To see the [genesis pool in Ghent, see here](./genesis_pool_ghent.md)
|
||||||
|
- To see the [genesis pool in Dubai, see here](./genesis_pool_dubai.md)
|
||||||
|
|
||||||
|
All genesis pools were owned by the foundation. Many of those servers are at this point no longer active. The operations were done by ThreeFold_Dubai and BetterToken as Farming Cooperative.
|
||||||
|
|
||||||
|
> For information about genesis pool/block, see [here](./genesis_block_pool_details.md).
|
||||||
|
|
||||||
|
## Genesis Pool Token Usage
|
||||||
|
|
||||||
|
- A lot of the genesis pool tokens went to the original shareholders of a company who created a lot of the technology which was the basis at that time for ThreeFold.
|
||||||
|
- Most of these tokens are locked up and are not tradeable.
|
||||||
|
- This was a deal made mid 2018 and provided the ThreeFold Dubai with technology and a global engineering team.
|
||||||
|
- The other part went to ThreeFold Dubai, to allow the Foundation to promote & further grow the project.
|
||||||
|
|
||||||
|
> [See Token Overview](./token_overview/token_overview.md) for more details.
|
||||||
|
|
||||||
|
The tokens were used from out of ThreeFold_Dubai to create value for the ThreeFold Grid.
|
||||||
|
|
||||||
|
- Initial funding: sell TFT as future IT capacity
|
||||||
|
- IT capacity delivered amongst others from the computers deployed by genesis pools (+300 servers)
|
||||||
|
- grants to community, bounties for coders, evangelists, ...
|
||||||
|
- max bounty given to contributors/founders = 2.5m TFT
|
||||||
|
- funding for projects like coding, marketing, ...
|
||||||
|
- There is a token grant program, but not really active yet.
|
||||||
|
- Fund the day-to-day operation of threefold_dubai
|
||||||
|
- Fund some development projects for our open source technology
|
||||||
|
- Public exchange fees
|
||||||
|
- Operational costs of keeping the genesis pool operational (engineers, data center, bandwidth, ...)
|
||||||
|
- Reward for the ThreeFold larger community and contributors
|
||||||
|
|
||||||
|
## Remarks
|
||||||
|
|
||||||
|
- ThreeFold_Dubai is run as a [not-for-profit organization](../legal/definitions_legal.md)
|
||||||
|
- All (future) profits generated, tokens=IT capacity sold are used to promote and grow the ThreeFold Project.
|
||||||
|
- None of the potential profits generated go to the shareholders of the company.
|
||||||
|
- Investments and loans given will of course be paid back to the relevant investors.
|
||||||
7
collections/about/genesis_pool_dubai.md
Normal file
7
collections/about/genesis_pool_dubai.md
Normal file
@ -0,0 +1,7 @@
|
|||||||
|
## The Genesis Pool Dubai
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
Read more about ThreeFold Dubai [here](./threefold_dubai.md).
|
||||||
11
collections/about/genesis_pool_ghent.md
Normal file
11
collections/about/genesis_pool_ghent.md
Normal file
@ -0,0 +1,11 @@
|
|||||||
|
|
||||||
|
## The Genesis Pool (Ghent)
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
60
collections/about/governance.md
Normal file
60
collections/about/governance.md
Normal file
@ -0,0 +1,60 @@
|
|||||||
|
<h1> Governance </h1>
|
||||||
|
|
||||||
|
<h2>Table of Contents</h2>
|
||||||
|
|
||||||
|
- [Introduction](#introduction)
|
||||||
|
- [Project History](#project-history)
|
||||||
|
- [Type of Token](#type-of-token)
|
||||||
|
- [Governance Process](#governance-process)
|
||||||
|
- [Organic Growth](#organic-growth)
|
||||||
|
- [Genesis Pool](#genesis-pool)
|
||||||
|
- [Decentralized and Open-Source](#decentralized-and-open-source)
|
||||||
|
|
||||||
|
***
|
||||||
|
|
||||||
|
## Introduction
|
||||||
|
|
||||||
|
We introduce the ThreeFold governance and provide some context around ThreeFold in general.
|
||||||
|
|
||||||
|
## Project History
|
||||||
|
|
||||||
|
The project is grateful of the support of its community and the commercial entity TFTech.
|
||||||
|
|
||||||
|
ThreeFold is fundamentally a decentralized initiative. Within this framework, ThreeFold Dubai plays a pivotal role in championing and advancing the ThreeFold Grid and the broader movement.
|
||||||
|
|
||||||
|
For more information, read the [ThreeFold History](./threefold_history.md).
|
||||||
|
|
||||||
|
## Type of Token
|
||||||
|
|
||||||
|
The regulators and legal advisors believe that we are a payment token with some flavor of a utility token (hybrid).
|
||||||
|
|
||||||
|
We conducted research and obtained legal counsel in multiple jurisdictions:
|
||||||
|
|
||||||
|
- Switzerland
|
||||||
|
- Belgium
|
||||||
|
- Dubai
|
||||||
|
- Singapore
|
||||||
|
|
||||||
|
For more information, [read the legal opinions](https://drive.google.com/file/d/1kNu2cFjMkgqdadrOOQTTC5FPAM4OgKEb/view?usp=drive_link).
|
||||||
|
|
||||||
|
## Governance Process
|
||||||
|
|
||||||
|
To make sure that all our funds are used properly and that decisions are taken for the benefit of ThreeFold and its community as a whole, we make use of different tools and features, such as multi-signature wallets, the [ThreeFold DAO](./dao/tfdao.md) and the [ThreeFold Forum](https://forum.threefold.io/).
|
||||||
|
|
||||||
|
## Organic Growth
|
||||||
|
|
||||||
|
We never organized a pump and dump or any other synthetic mechanism to boost the token price and benefit from this. We believe in organic growth and TFT going up as result of utilization and grid expansion.
|
||||||
|
|
||||||
|
## Genesis Pool
|
||||||
|
|
||||||
|
The Genesis pool was based on real hardware located in Dubai and Ghent.
|
||||||
|
|
||||||
|
The tokens out of this pool are safe and well managed. We are acquiring a lot of them with ThreeFold Cloud (ThreeFold Dubai).
|
||||||
|
|
||||||
|
For more information on the Genesis pool, [read this section](./genesis_pool.md).
|
||||||
|
|
||||||
|
## Decentralized and Open-Source
|
||||||
|
|
||||||
|
In essence, ThreeFold is a decentralized and open-source project. We invite everyone to contribute and participate within the ThreeFold ecosystem.
|
||||||
|
|
||||||
|
You can read the code on the [ThreeFold Tech GitHub repository](https://github.com/threefoldtech).
|
||||||
BIN
collections/about/img/al_jadaf.jpg
Normal file
BIN
collections/about/img/al_jadaf.jpg
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 260 KiB |
BIN
collections/about/img/aljadaf2.jpg
Normal file
BIN
collections/about/img/aljadaf2.jpg
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 371 KiB |
BIN
collections/about/img/bettertoken_web.jpg
Normal file
BIN
collections/about/img/bettertoken_web.jpg
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 296 KiB |
BIN
collections/about/img/blockchain.png
Normal file
BIN
collections/about/img/blockchain.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 390 KiB |
BIN
collections/about/img/crypto_valley_zug_.jpg
Normal file
BIN
collections/about/img/crypto_valley_zug_.jpg
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 422 KiB |
BIN
collections/about/img/dubai_office1.jpg
Normal file
BIN
collections/about/img/dubai_office1.jpg
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 340 KiB |
BIN
collections/about/img/foundation_header_image.jpg
Normal file
BIN
collections/about/img/foundation_header_image.jpg
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 39 KiB |
BIN
collections/about/img/genesispool_1.jpg
Normal file
BIN
collections/about/img/genesispool_1.jpg
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 61 KiB |
BIN
collections/about/img/genesispool_2.jpg
Normal file
BIN
collections/about/img/genesispool_2.jpg
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 294 KiB |
BIN
collections/about/img/korenlei_22.jpg
Normal file
BIN
collections/about/img/korenlei_22.jpg
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 172 KiB |
BIN
collections/about/img/korenlei_old.jpg
Normal file
BIN
collections/about/img/korenlei_old.jpg
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 47 KiB |
BIN
collections/about/img/labs_it_license.jpg
Normal file
BIN
collections/about/img/labs_it_license.jpg
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 206 KiB |
BIN
collections/about/img/lochristi_1_.jpg
Normal file
BIN
collections/about/img/lochristi_1_.jpg
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 510 KiB |
BIN
collections/about/img/lochristi_2_.jpg
Normal file
BIN
collections/about/img/lochristi_2_.jpg
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 537 KiB |
BIN
collections/about/img/lochristi_3.jpg
Normal file
BIN
collections/about/img/lochristi_3.jpg
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 160 KiB |
BIN
collections/about/img/lochristi_4.jpg
Normal file
BIN
collections/about/img/lochristi_4.jpg
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 191 KiB |
BIN
collections/about/img/lochristi_5_.jpg
Normal file
BIN
collections/about/img/lochristi_5_.jpg
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 638 KiB |
BIN
collections/about/img/lochristi_6_.jpg
Normal file
BIN
collections/about/img/lochristi_6_.jpg
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 495 KiB |
BIN
collections/about/img/lochristi_7.jpg
Normal file
BIN
collections/about/img/lochristi_7.jpg
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 109 KiB |
BIN
collections/about/img/mazraa_web1.jpg
Normal file
BIN
collections/about/img/mazraa_web1.jpg
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 207 KiB |
BIN
collections/about/img/tf_companies_.jpg
Normal file
BIN
collections/about/img/tf_companies_.jpg
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 194 KiB |
BIN
collections/about/img/threefold_commodities_1_.jpg
Normal file
BIN
collections/about/img/threefold_commodities_1_.jpg
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 442 KiB |
BIN
collections/about/img/threefold_dmcc_license_certificate.jpg
Normal file
BIN
collections/about/img/threefold_dmcc_license_certificate.jpg
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 186 KiB |
BIN
collections/about/img/threefold_tech.jpg
Normal file
BIN
collections/about/img/threefold_tech.jpg
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 291 KiB |
BIN
collections/about/img/threefold_tech_location.jpg
Normal file
BIN
collections/about/img/threefold_tech_location.jpg
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 143 KiB |
BIN
collections/about/img/threefold_vzw_official_doc.jpg
Normal file
BIN
collections/about/img/threefold_vzw_official_doc.jpg
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 152 KiB |
BIN
collections/about/img/view_dubai.jpg
Normal file
BIN
collections/about/img/view_dubai.jpg
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 378 KiB |
22
collections/about/mazraa.md
Normal file
22
collections/about/mazraa.md
Normal file
@ -0,0 +1,22 @@
|
|||||||
|
<h1> Mazraa </h1>
|
||||||
|
|
||||||
|
<h2>Table of Contents</h2>
|
||||||
|
|
||||||
|
- [Introduction](#introduction)
|
||||||
|
- [History](#history)
|
||||||
|
- [Mission](#mission)
|
||||||
|
|
||||||
|
***
|
||||||
|
|
||||||
|
## Introduction
|
||||||
|
|
||||||
|
Mazraa is a brand name of [ThreeFold Dubai](./threefold_dubai.md). You can read about ThreeFold Dubai for more details.
|
||||||
|
|
||||||
|
## History
|
||||||
|
|
||||||
|
Mazraa was established in early 2016 in the United Arab Emirates and was one of the first provider's of Peer2Peer Internet capacity on the ThreeFold Grid. Currently, Mazraa's capacity pool of storage and compute capacity can be accessed for workload development on the TF Capacity Explorer.
|
||||||
|
|
||||||
|
|
||||||
|
## Mission
|
||||||
|
|
||||||
|
Mazraa supports ThreeFold Foundation's mission to create a responsible Internet for all, one that is accessible, affordable and environmentally conscious. Mazraa is a founding capacity farmer on the ThreeFold Network and actively supports the expansion and adoption of ThreeFold's P2P Cloud. Mazraa's focus is to provide P2P Cloud capacity for developers, nodes for new and existing farmers, as well as, providing over the counter access to TFT's to enable reservations of Internet capacity. Additionally, Mazraa supports the promotion and growth of the ThreeFold Network, through marketing resources and funding contributions. We believe it's time for the internet to have a major upgrade to empower people and protect our planet.
|
||||||
14
collections/about/orgstructure.md
Normal file
14
collections/about/orgstructure.md
Normal file
@ -0,0 +1,14 @@
|
|||||||
|
# Organisation Structure
|
||||||
|
|
||||||
|
<h2>Table of Contents</h2>
|
||||||
|
|
||||||
|
- [Governance](./governance.md)
|
||||||
|
- [ThreeFold Companies](./threefold_companies.md)
|
||||||
|
- [ThreeFold Dubai](./threefold_dubai.md)
|
||||||
|
- [ThreeFold VZW](./threefold_vzw.md)
|
||||||
|
- [ThreeFold AG](./threefold_ag.md)
|
||||||
|
- [Mazraa](./mazraa.md)
|
||||||
|
- [BetterToken](./bettertoken.md)
|
||||||
|
- [DAO](./dao/dao.md)
|
||||||
|
- [ThreeFold DAO](./dao/tfdao.md)
|
||||||
|
- [TFChain](./tfchain.md)
|
||||||
BIN
collections/about/roadmap/releasenotes/img/releasenotes.png
Normal file
BIN
collections/about/roadmap/releasenotes/img/releasenotes.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 743 KiB |
@ -0,0 +1,19 @@
|
|||||||
|
|
||||||
|
|
||||||
|
# ThreeFold Grid Release Notes
|
||||||
|
|
||||||
|
We're delighted to have you here as we explore the latest updates and enhancements to our decentralized grid ecosystem. In these release notes, you'll discover a wealth of information about the exciting features, bug fixes, performance optimizations, and new functionalities that have been introduced in each release.
|
||||||
|
|
||||||
|
Whether you're a developer, a farmer, a user, or simply curious about the cutting-edge advancements happening in the world of distributed computing, these release notes will provide you with valuable insights and keep you up to date with our progress. So dive in, explore the details, and join us in shaping the future of the ThreeFold Grid!
|
||||||
|
|
||||||
|
## ThreeFold TFGrid v3.x Release Notes
|
||||||
|
- [TFGrid v3.10.0](./tfgrid_release_3_10_0.md)
|
||||||
|
- [TFGrid v3.9.0](./tfgrid_release_3_9_0.md)
|
||||||
|
- [TFGrid v3.8.0](./tfgrid_release_3_8_0.md)
|
||||||
|
- [TFGrid v3.7.0](./tfgrid_release_3_7_0.md)
|
||||||
|
- [TFGrid v3.6.1](./tfgrid_release_3_6_1.md)
|
||||||
|
- [TFGrid v3.6.0](./tfgrid_release_3_6_0.md)
|
||||||
|
- [TFGrid v3.0.0 Alpha-5](./tfgrid_release_3_0_a5.md)
|
||||||
|
- [TFGrid v3.0.0 Alpha-4](./tfgrid_release_3_0_a4.md)
|
||||||
|
- [TFGrid v3.0.0 Alpha-2](./tfgrid_release_3_0_a2.md)
|
||||||
|
- [TFGrid v3.0.0](./tfgrid_release_3_0.md)
|
||||||
43
collections/about/roadmap/releasenotes/tfgrid_release_3_0.md
Normal file
43
collections/about/roadmap/releasenotes/tfgrid_release_3_0.md
Normal file
@ -0,0 +1,43 @@
|
|||||||
|
# TFGrid release 3.0
|
||||||
|
|
||||||
|
TFGrid 3.0 will be released gradually during Q3/Q4 2021.
|
||||||
|
|
||||||
|
## What's new ?
|
||||||
|
|
||||||
|
TFGrid 3.0 is a full redesign of the ThreeFold Grid architecture. The main purpose of this redesign is to decentralize all the components that the Grid is built with.
|
||||||
|
|
||||||
|
### TFChain 3.0
|
||||||
|
|
||||||
|
A decentralised chain holding all information on entities that make up the ThreeFold Grid. It runs on Parity Substrate blockchain infrastructure.
|
||||||
|
|
||||||
|
Features :
|
||||||
|
- Your identity and proofs/reputation on our blockchain
|
||||||
|
- All info about TFGrid (nodes, farmers, …)
|
||||||
|
- A Graphql interface to be able to query the blockchain
|
||||||
|
- Support of side chains (unlimited scalability, allow others to run their own blockchain)
|
||||||
|
- TFT exists now also on TFChain (allows us to work around Stellar scalability issues)
|
||||||
|
- Bridge between TFT on Stellar and TFT on TFChain (one way to start)
|
||||||
|
- Blockchain based provisioning process
|
||||||
|
- TFChain API (javascript, golang, vlang)
|
||||||
|
- Support for 'Infrastructure as Code' : IAC frameworks
|
||||||
|
- Terraform
|
||||||
|
- Kubernetes, Helm, Kubernetes
|
||||||
|
- Ansible (planned for Q4 2021)
|
||||||
|
- Use RMB = peer2peer secure Reliable Message Bus to communicate with Zero-OS
|
||||||
|
|
||||||
|
### Proof of Utilization
|
||||||
|
|
||||||
|
- Resource utilisation is captured and calculated on hourly basis
|
||||||
|
- Resource utilisation stored in TFChain
|
||||||
|
- An automated discount system has been put in place, rewarding users who pre-purchased their cloud needs. Price discounts are applied, in line with amount of TFT you have in your account and the period you are holding these TFT.
|
||||||
|
E.g. if you have 12 months worth of TFT in your account in relation to the last hour used capacity you get 40% discount, 36 months results in 60% discount.
|
||||||
|
|
||||||
|
### New Explorer UI
|
||||||
|
- An updated User Interface of the TF Grid Explorer, nicer and easier to use
|
||||||
|
- It uses the Graphql layer of TFChain
|
||||||
|
|
||||||
|
## Roadmap
|
||||||
|
|
||||||
|
The feature overview split over different releases can be found [here](https://circles.threefold.me/project/despiegk-product_tfgrid3_roadmap/wiki/roadmap).
|
||||||
|
|
||||||
|
More info and announcements on Grid 3.0 to be found on our [forum](https://forum.threefold.io/t/announcement-of-tfgrid-3-0/1132)
|
||||||
204
collections/about/roadmap/releasenotes/tfgrid_release_3_0_a2.md
Normal file
204
collections/about/roadmap/releasenotes/tfgrid_release_3_0_a2.md
Normal file
@ -0,0 +1,204 @@
|
|||||||
|
# ThreeFold Release Notes TFGrid 3.0.0 Alpha 2 (Live on testnet)
|
||||||
|
|
||||||
|
## TFChain v1.0.0
|
||||||
|
|
||||||
|
- DAO Requests
|
||||||
|
- Becoming council member
|
||||||
|
- Becoming a validator node
|
||||||
|
- Pricing changes
|
||||||
|
- Upgrading tfchain
|
||||||
|
- Changing farming rewards
|
||||||
|
|
||||||
|
## Admin Portal v3.0.1-rc1
|
||||||
|
|
||||||
|
- Terms and conditions support
|
||||||
|
- Fix reasking for activation when the balance reaches 0
|
||||||
|
- Show amount of bridge deposit/withdraw fee
|
||||||
|
- Get more TFT button when connected to devnet
|
||||||
|
|
||||||
|
## tfchain explorer v3.0.0-rc19
|
||||||
|
|
||||||
|
- certification type filter
|
||||||
|
- adding certification type to nodes
|
||||||
|
- add zos version to node details
|
||||||
|
- update map to reflect the selected node
|
||||||
|
- UX fixes for filters and data sorting
|
||||||
|
- include version of tfchain, explorer, grid proxy
|
||||||
|
- showing available resources
|
||||||
|
- showing online / offline nodes
|
||||||
|
- showing number of available IPs in a farm
|
||||||
|
- adding favicon
|
||||||
|
- statistics page improvements
|
||||||
|
|
||||||
|
## ZOS v3.0.4
|
||||||
|
|
||||||
|
- public IPv6 support
|
||||||
|
- Min rootfs for more than 1 CU = 2GB, and anything less will be 500MB
|
||||||
|
- Mainnet image
|
||||||
|
- Fix IPv6 rules that broke SLAAC
|
||||||
|
- Update SRU calculation
|
||||||
|
- bug don't wait for QSFS shutdown
|
||||||
|
- Update traefik version
|
||||||
|
- Fixing crashes caused by slow disks
|
||||||
|
- Avoid lsblk blocking for QSFS
|
||||||
|
- Decommission on too many QSFS metric fetches failure
|
||||||
|
https://github.com/threefoldtech/zos/releases
|
||||||
|
|
||||||
|
## Terraform v0.1.20
|
||||||
|
- Support for public IPv6
|
||||||
|
- Support planetary option for k8s
|
||||||
|
|
||||||
|
https://github.com/threefoldtech/tf-terraform-provider/releases
|
||||||
|
|
||||||
|
|
||||||
|
## grid3_client_ts v1.0.3
|
||||||
|
- Cert type for nodes
|
||||||
|
- public IPv6 support
|
||||||
|
- TwinServer command to be used from other langauges
|
||||||
|
|
||||||
|
|
||||||
|
## Weblets v1.2.0
|
||||||
|
|
||||||
|
- Support peertube
|
||||||
|
- Support funkwhale
|
||||||
|
- Remove rootfs specification from machine
|
||||||
|
- Support adding/deleting workers in kubernetes
|
||||||
|
- Add more images ubuntu, alpine, centos
|
||||||
|
- Updating the balance periodically
|
||||||
|
- Adding access for nodes by default for hidden nodes issues
|
||||||
|
- Resolving issues
|
||||||
|
|
||||||
|
### detailed projects list
|
||||||
|
|
||||||
|
- https://github.com/threefoldtech/grid_weblets/projects/1
|
||||||
|
- https://github.com/threefoldtech/grid_weblets/projects/4
|
||||||
|
- https://github.com/threefoldtech/grid_weblets/projects/6
|
||||||
|
- https://github.com/threefoldtech/grid_weblets/projects/6
|
||||||
|
- https://github.com/threefoldtech/grid_weblets/projects/7
|
||||||
|
- https://github.com/threefoldtech/grid_weblets/projects/8
|
||||||
|
|
||||||
|
https://github.com/threefoldtech/grid_weblets/releases
|
||||||
|
|
||||||
|
## QSFS
|
||||||
|
|
||||||
|
TODO
|
||||||
|
|
||||||
|
## gridproxy v1.0.0-rc8
|
||||||
|
|
||||||
|
- generic performance improvements
|
||||||
|
- reduce caching time
|
||||||
|
- enable CORS in version
|
||||||
|
- include certification types in nodes
|
||||||
|
- fix regression on nodes query
|
||||||
|
-
|
||||||
|
|
||||||
|
## Known Issues 3.0.0 Alpha 2
|
||||||
|
|
||||||
|
Following list is incomplete but gives some issues to think about.
|
||||||
|
|
||||||
|
- Weblets [limitations](https://library.threefold.me/info/manual/#/manual__weblets_home?id=limitations)
|
||||||
|
- QSFS integration is a work in progress
|
||||||
|
- ZOS and SSD performance [issue](https://github.com/threefoldtech/zos/issues/1467)
|
||||||
|
- Threefold Connect having [issues](https://circles.threefold.me/project/test-tfgrid3/issue/52)
|
||||||
|
- Docker & ZOS containers [differences](https://github.com/threefoldtech/zos/issues/1483)
|
||||||
|
- ZOS workloads upgrade [issue](https://github.com/threefoldtech/zos/issues/1425)
|
||||||
|
- Terraform projects [don't reflect in the weblets](https://github.com/threefoldtech/terraform-provider-grid/issues/146)
|
||||||
|
- Can't detach public IP from a VM and removing it from a contract [issue](https://github.com/threefoldtech/tfchain_pallets/issues/73), please note you can still create each in separate contracts.
|
||||||
|
|
||||||
|
# ThreeFold Release Notes TFGrid 3.0.0 Alpha 1 (Live on mainnet)
|
||||||
|
|
||||||
|
- [TFgrid 3.0 announcement](https://forum.threefold.io/t/announcement-of-tfgrid-3-0/1132)
|
||||||
|
- [Whats new in TFGrid 3.0](https://forum.threefold.io/t/what-is-new-in-tfgrid-3-0/1133)
|
||||||
|
- [Roadmap](https://circles.threefold.me/project/despiegk-product_tfgrid3_roadmap/wiki/home)
|
||||||
|
-
|
||||||
|
## TFChain
|
||||||
|
|
||||||
|
- Staking support (as the moment of this writing it's only on devnet now)
|
||||||
|
- KeyValue store support
|
||||||
|
- Bridging tokens from stellar to tfchain
|
||||||
|
- Smart contract for IT
|
||||||
|
- Billing
|
||||||
|
- Consumption Reports
|
||||||
|
- Discounts support
|
||||||
|
|
||||||
|
## Admin Portal
|
||||||
|
|
||||||
|
- Creation of twins
|
||||||
|
- Bridge from and to Stellar
|
||||||
|
- Farm Management
|
||||||
|
|
||||||
|
|
||||||
|
## Tfchain explorer
|
||||||
|
|
||||||
|
- Nodes view
|
||||||
|
- Gateways listing
|
||||||
|
- Farms information
|
||||||
|
- Resources/utilization
|
||||||
|
- Better filtering
|
||||||
|
|
||||||
|
|
||||||
|
## ZOS
|
||||||
|
- zmachine support
|
||||||
|
- Integration with latest subtsrate client event types
|
||||||
|
- public ipv6 support in VMs
|
||||||
|
- planetary support in VMs
|
||||||
|
- upgrade to new file system RFS
|
||||||
|
- support for QSFS
|
||||||
|
- support for gateways
|
||||||
|
- capacity reporting to the blockchain support
|
||||||
|
- Support of SR25519
|
||||||
|
- Improvements in .zosrc creation
|
||||||
|
- Safer mechanism for environment variables and init arguments
|
||||||
|
- improvments in cleaning unused mounts
|
||||||
|
|
||||||
|
https://github.com/threefoldtech/zos/releases
|
||||||
|
|
||||||
|
## Terraform
|
||||||
|
- Support ZMachine
|
||||||
|
- Support Kubernetes
|
||||||
|
- Support QSFS
|
||||||
|
- Support Capacity Planning
|
||||||
|
- Support Gateways
|
||||||
|
|
||||||
|
https://github.com/threefoldtech/tf-terraform-provider/releases
|
||||||
|
|
||||||
|
|
||||||
|
## grid3_client_ts
|
||||||
|
- Support ZMachine
|
||||||
|
- Support Kubernetes
|
||||||
|
- Support QSFS
|
||||||
|
- Support Capacity Planning
|
||||||
|
- Support Gateways
|
||||||
|
|
||||||
|
|
||||||
|
## Weblets
|
||||||
|
|
||||||
|
- Support Profile manager
|
||||||
|
- Support Virtual machine
|
||||||
|
- Support CapRover
|
||||||
|
- Support Kubernetes
|
||||||
|
https://github.com/threefoldtech/grid_weblets/releases
|
||||||
|
- Capacity planning deployment
|
||||||
|
|
||||||
|
## QSFS
|
||||||
|
|
||||||
|
TODO
|
||||||
|
|
||||||
|
|
||||||
|
- [TFgrid 3.0 announcement](https://forum.threefold.io/t/announcement-of-tfgrid-3-0/1132)
|
||||||
|
- [Whats new in TFGrid 3.0](https://forum.threefold.io/t/what-is-new-in-tfgrid-3-0/1133)
|
||||||
|
- [Roadmap](https://circles.threefold.me/project/despiegk-product_tfgrid3_roadmap/wiki/home)
|
||||||
|
|
||||||
|
## Known Issues 3.0.0 Alpha 1
|
||||||
|
|
||||||
|
Following list is incomplete but gives some issues to think about.
|
||||||
|
|
||||||
|
- Weblets [limitations](https://library.threefold.me/info/manual/#/manual__weblets_home?id=limitations)
|
||||||
|
- Public IP6 [support](https://github.com/threefoldtech/zos/pull/1488) in ZOS
|
||||||
|
- QSFS integration is a work in progress
|
||||||
|
- ZOS and SSD performance [issue](https://github.com/threefoldtech/zos/issues/1467)
|
||||||
|
- Threefold Connect having [issues](https://circles.threefold.me/project/test-tfgrid3/issue/52)
|
||||||
|
- Docker & ZOS containers [differences](https://github.com/threefoldtech/zos/issues/1483)
|
||||||
|
- ZOS workloads upgrade [issue](https://github.com/threefoldtech/zos/issues/1425)
|
||||||
|
- Terraform projects [don't reflect in the weblets](https://github.com/threefoldtech/terraform-provider-grid/issues/146)
|
||||||
|
- Can't detach public IP from a VM and removing it from a contract [issue](https://github.com/threefoldtech/tfchain_pallets/issues/73), please note you can still create each in separate contracts.
|
||||||
@ -0,0 +1,53 @@
|
|||||||
|
# ThreeFold Grid v3.0.0 Alpha - 4 Release Note
|
||||||
|
|
||||||
|
## TFConnect v3.4.0
|
||||||
|
|
||||||
|
### TFConnect Backend Services Migration
|
||||||
|
|
||||||
|
We moved ThreeFold Connect’s backend services from a data storage in Lochristi to TFGrid. From TF Wallet, to TF account, and TFNews, all active services are migrated by using Helm charts.
|
||||||
|
|
||||||
|
## TFPlay v1.1.4
|
||||||
|
|
||||||
|
### Listed Mattermost as Deployable Solution
|
||||||
|
|
||||||
|
On this release, we added Mattermost as one of our deployable decentralised solutions.
|
||||||
|
Mattermost is a secure, open source platform for communication, collaboration, and workflow orchestration across tools and teams.
|
||||||
|
|
||||||
|
### Separated TFPlay into 3 different networks
|
||||||
|
|
||||||
|
Node upgrades could happen anytime, and it could make solution deployments on different networks incompatible. Therefore, we separated TFPlay into 3 different networks:
|
||||||
|
|
||||||
|
- Deployment on TFGrid Mainnet: play.grid.tf
|
||||||
|
- Deployment on TFGrid Testnet: play.test.grid.tf
|
||||||
|
- Deployment on TFGrid Devnet: play.dev.grid.tf
|
||||||
|
|
||||||
|
This way, if some nodes on one network are being upgraded, deployments on the other nets should not be affected.
|
||||||
|
|
||||||
|
## Minting v3.0
|
||||||
|
|
||||||
|
### Minting V3 code
|
||||||
|
|
||||||
|
Repo: https://github.com/threefoldtech/minting_v3
|
||||||
|
|
||||||
|
There was a change the way how the CU/SU are calculated from the resource units calculations, please see https://library.threefold.me/info/threefold#/resource_units_calc_cloudunits for details.
|
||||||
|
Therefore, we updated the calculations on the minting code (minting v3), as well as adjusted price calculation for workloads on TFchain.
|
||||||
|
|
||||||
|
## GetTFT Shop v1.0.4
|
||||||
|
|
||||||
|
Story: https://github.com/threefoldtech/home/issues/1171
|
||||||
|
|
||||||
|
### Minor UX / UI improvements
|
||||||
|
|
||||||
|
On this release we created minor UX improvements on the existing GetTFT Shop website that create a better experience for our customers, such as improved interactivity, fixed embedded media, revised UX content, improved screen responsiveness, and many more.
|
||||||
|
|
||||||
|
## TF Capacity Explorer v0.1.0
|
||||||
|
|
||||||
|
### An all-in-one Unified Capacity Explorer
|
||||||
|
|
||||||
|
Currently we have a few separate capacity explorers for both TFGrid v2 Explorer and TFGrid v3 Explorer. On this release we unified all versions and networks into one explorer, where users can find capacity information on both TFGrid v2 and v3 mainnet, testnet, and devnet. This all-in-one unified Capacity Explorer will be hosted under the domain https://explorer.threefold.io.
|
||||||
|
|
||||||
|
## TF Farm Management v1.1
|
||||||
|
|
||||||
|
On TFGrid v3, node and farm management are also moved to substrate-based blockchains. A farm can be managed by making calls directly to the blockchain using objects created in TFChain called Twins. TFWallet app can reuse the wallet keypair to support a twin. A twin is also associated with a Planetary Network address that is supported by the Threefold Connect App.
|
||||||
|
|
||||||
|
Therefore we added a ‘Farm Management’ feature on the TFConnect App that would enable farmers to list their farms and create new ones directly on the mobile app. The ‘Farm Management’ feature will allow users to create new farms, list farms, as well as migrate their farms from TFGrid v2 to TFGrid v3.
|
||||||
@ -0,0 +1,72 @@
|
|||||||
|
# ThreeFold Grid v3.0.0 Alpha - 5 Release Note
|
||||||
|
|
||||||
|
This is the release note of TFGrid v3.0.0 Alpha 5. It includes updates, improvements and fixes of numerous grid components as described below.
|
||||||
|
|
||||||
|
## TFT Shop v1.1.0
|
||||||
|
|
||||||
|
On the first initial release of TFT Shop v1.0.0, we have made it easier for users to buy TFT by BTC on the [TFT Shop website](https://gettft.com/gettft/).
|
||||||
|
|
||||||
|
On this v1.1.0 release, we are giving users another **option to buy TFT by using fiat currency**. This is made possible by integrating [mercuryo.io](http://www.mercuryo.io/) (third-party) widget onto the shop. By buying TFT using TFT Shop, you confirm that you have read and agree to [ThreeFold’s terms and conditions](https://library.threefold.me/info/legal/#/legal__terms_conditions_gettft).
|
||||||
|
|
||||||
|
|
||||||
|
## ZOS v3.1.0
|
||||||
|
|
||||||
|
### Performance Improvements
|
||||||
|
|
||||||
|
This new feature release of ZOS v3.1.0 includes a lot of improvements such as **improvements on performance issues** (disk and IO), grid events handling, and improvement on the current yggdrasil network by start and maintaining our public peers.
|
||||||
|
|
||||||
|
### ZOS Supoort Dedicated Nodes
|
||||||
|
|
||||||
|
To empower community-driven decentralization on the TFGrid, we would like to soon invite anyone to deploy their own solutions on the TFGrid. This is feasible to do by allowing any external developers to** deploy their own workloads on** **dedicated nodes** and provide the deployment documentation. By choosing to deploy on dedicated nodes, a user can reserve an entire node, then use it exclusively to deploy solutions for themselves or for other customers. Therefore on this release we are happy to announce that we are supporting dedicated nodes deployment, apply the dedicated node contracts on TFChain and support mechanism on ZOS' next release.
|
||||||
|
|
||||||
|
|
||||||
|
## TF Playground v3.0.0 Alpha-5
|
||||||
|
|
||||||
|
### New community and blockchain solutions
|
||||||
|
On the last release, we have added new deployable community solutions on [TF Playground](https://play.grid.tf/#/), such as Peertube, Funkwhale and Taiga, Mattermost as well as some developer tools like CapRover, Virtual Machine, Kubernetes and Owncloud.
|
||||||
|
|
||||||
|
On this release, we have added **community and blockchain solutions** such as Discourse (forum), Presearch Node and Casperlabs validator node.
|
||||||
|
|
||||||
|
## Uhuru v1.1 (beta)
|
||||||
|
|
||||||
|
### Uhuru Backend Changes
|
||||||
|
|
||||||
|
[Uhuru](https://www.uhuru.me) is a digital product on top of a the TFGrid that enhance collaboration with features such as chat, videocall, office tools, and file storage, all in one platform.
|
||||||
|
|
||||||
|
|
||||||
|
## ThreeFold Wallet v3.0.0
|
||||||
|
|
||||||
|
### Add (substrate-based) TFChain Wallet
|
||||||
|
|
||||||
|
TFGrid v3 is powered by substrate-based blockchain. A TFT is moveable from Stellar blockchain to TFChain through the use of a bridge.ThreeFold Wallet now has successfully **added (substrate-based) TFChain Wallet in order to support the bridge transaction**.
|
||||||
|
|
||||||
|
However, TFT is still the native currency on TFChain. As such, there is no need for an external service to transfer tokens on TFChain. A transaction fee is charged (currently 0.01 TFT) for every transaction/extrinsic call.
|
||||||
|
|
||||||
|
## TF Farm Management Tool v3.0.2
|
||||||
|
|
||||||
|
### Adjust farm management for the latest TFChain upgrade
|
||||||
|
|
||||||
|
On the last release of 3 alpha-4, we have released Farm Management Tool v3.0.1 which allows farmers to migrate their farms from v2 to v3 through the TF Connect application.
|
||||||
|
|
||||||
|
Recently a change was made within the codes of TFChain, thus broke the farm management function in the wallet. Therefore, on the v3.0.2 release, code changes were done on **Farm Management Tool to adapt itself with TFChain changes**. This was done quickly in production.
|
||||||
|
|
||||||
|
## TFConnect App v3.5.0
|
||||||
|
|
||||||
|
### Generic Frontend and Backend Improvements
|
||||||
|
This new feature release of TFConnect App includes new features such as **enabling user to sign documents on the app** directly, and many other backend improvements.
|
||||||
|
|
||||||
|
### Integrate TFConnect SSO to TFPlay Solutions
|
||||||
|
|
||||||
|
We need to simplify peer-to-peer collaboration and how users interact with their TFPlay solutions. On this release, we have eliminated a complicated way of signing up to solutions (emails, username and password) by replacing it using **TFConnect app SSO login**. Therefore on this release, we successfully created TFConnect Native SSO backend environments for the following TFPlay solutions**: Discourse. Mattermost, and Gitea, that will allow users to sign in and start using the solutions with just few clicks.
|
||||||
|
|
||||||
|
## TFChain v1.2.0
|
||||||
|
|
||||||
|
### ThreeFold DAO Pt. 2: Adjoint Validator-Council member request
|
||||||
|
|
||||||
|
From version 3.0 on, [ThreeFold Grid operates as a DAO](https://library.threefold.me/info/threefold#/tfgrid/threefold__dao). On the last release of TFChain v1.0.0, we have successfully implemented The first TF-DAO that allows users to request to become DAO council members.
|
||||||
|
|
||||||
|
On this release we also have successfully implemented **ThreeFold DAO Request part 2 where any user could request to become an adjoint validator-council member**: by running a a validator node, not only that they become a validator, they would also gain a seat as DAO council member that give them the right to vote for organizational changes.
|
||||||
|
|
||||||
|
### ThreeFold DAO Pt. 2: Enable Validator Application
|
||||||
|
|
||||||
|
On this release we implemented ThreeFold DAO Request part 2 any user could **apply to become a validator **and register the validator application on-chain if they meet the validator requirements.
|
||||||
119
collections/about/roadmap/releasenotes/tfgrid_release_3_10_0.md
Normal file
119
collections/about/roadmap/releasenotes/tfgrid_release_3_10_0.md
Normal file
@ -0,0 +1,119 @@
|
|||||||
|
# ThreeFold Grid v3.10.0 Release Note
|
||||||
|
|
||||||
|
Release Note of ThreeFold Grid v3.10.0.
|
||||||
|
|
||||||
|
- Deployed on Mainnet on 3rd July 2023.
|
||||||
|
|
||||||
|
## Components and Services
|
||||||
|
|
||||||
|
The following components and services have been upgraded in this release:
|
||||||
|
|
||||||
|
- TFChain
|
||||||
|
- ZOS
|
||||||
|
- Terraform
|
||||||
|
- TFGrid-SDK-GO
|
||||||
|
- TF Gridclient
|
||||||
|
- TF Gridproxy
|
||||||
|
- RMB
|
||||||
|
- TF Weblets
|
||||||
|
- TF Playground
|
||||||
|
- TF-Grid-CLI
|
||||||
|
- Gridify
|
||||||
|
- TFGrid-SDK-TS
|
||||||
|
|
||||||
|
## Upgrades and Improvement Highlights
|
||||||
|
|
||||||
|
Below are some of the key highlights of the TFGrid v3.10.0 component upgrades and improvements.
|
||||||
|
|
||||||
|
### TFChain 2.4.0
|
||||||
|
|
||||||
|
- Addressed syncing issues.
|
||||||
|
- Introduced the attachment of solution provider IDs to contracts.
|
||||||
|
- Enabled the bonding of a stash account to a twin.
|
||||||
|
- Implemented various bug fixes.
|
||||||
|
|
||||||
|
### ZOS 3.7.1
|
||||||
|
|
||||||
|
- Restructured the capacity to enhance dynamism.
|
||||||
|
- Added support for proxying traffic to private networks using WireGuard-based gateways.
|
||||||
|
- Introduced support for cloud-based consoles.
|
||||||
|
- Resolved various issues related to error messages, user validations, and error handling.
|
||||||
|
|
||||||
|
### Terraform 1.9
|
||||||
|
|
||||||
|
- Added support for WireGuard-based gateway options.
|
||||||
|
- Implemented proper timeout handling for deployments.
|
||||||
|
- Introduced gateway node validation before submitting deployments.
|
||||||
|
- Resolved various bugs and issues.
|
||||||
|
|
||||||
|
### TFGrid-SDK-GO 0.8.0
|
||||||
|
|
||||||
|
- Consolidated multiple Go projects into a single repository for simplified administration and quicker releases.
|
||||||
|
- Extracted reusable code from the Terraform project and created a standalone library for creating new platforms or plugins.
|
||||||
|
|
||||||
|
#### Grid-Client
|
||||||
|
|
||||||
|
- Enhanced the grid client to serve as the foundation layer for the Terraform plugin, enabling deployment of networks, virtual machines, and Kubernetes.
|
||||||
|
|
||||||
|
#### Grid-Proxy
|
||||||
|
|
||||||
|
- Added support for standby status for nodes powered off by the farmerbot.
|
||||||
|
- Enabled farm filtering based on requested resources.
|
||||||
|
|
||||||
|
#### RMB
|
||||||
|
|
||||||
|
- Improved the direct client's resilience to recover from close connections.
|
||||||
|
|
||||||
|
#### TF-Grid-CLI
|
||||||
|
|
||||||
|
- Introduced a simple tool for creating virtual machines and Kubernetes clusters. Note that `TF-Grid-CLI` is now `TFCMD`.
|
||||||
|
- Get started [here](../../../../documentation/developers/tfcmd/tfcmd.md).
|
||||||
|
|
||||||
|
#### Gridify
|
||||||
|
|
||||||
|
- An experimental project that allows developers to deploy their projects on ThreeFold as a platform with a single command, "gridify," using a Procfile in their code repository.
|
||||||
|
- Currently supported platforms include:
|
||||||
|
- Go 1.18
|
||||||
|
- Python 3.10.10
|
||||||
|
- Node 16.17.1
|
||||||
|
- NPM 8.10.0
|
||||||
|
- Caddy
|
||||||
|
- Learn more [here](https://github.com/threefoldtech/tfgrid-sdk-go/tree/development/gridify).
|
||||||
|
|
||||||
|
### TFGrid-SDK-TS 2.0.0
|
||||||
|
|
||||||
|
- Consolidated all components targeting web/TypeScript developers and frontend efforts into a single repository for easier management and rapid releases.
|
||||||
|
- Moved gridclient, dashboard, statistics websites, and other TypeScript-based projects to the new repository [here](https://github.com/threefoldtech/tfgrid-sdk-ts).
|
||||||
|
|
||||||
|
#### Grid-Client
|
||||||
|
|
||||||
|
- Gateways now support WireGuard backends.
|
||||||
|
- Added support for hex secrets.
|
||||||
|
- Various fixes are detailed [here](https://github.com/orgs/threefoldtech/projects/192/views/12?filterQuery=repo%3A%22threefoldtech%2Ftfgrid-sdk-ts%22+label%3Agrid_client).
|
||||||
|
|
||||||
|
#### TF Dashboard
|
||||||
|
|
||||||
|
- Added support for IPv4 pricing in the resources calculator.
|
||||||
|
- Included TFT/USD exchange rate in the dashboard navbar.
|
||||||
|
- Introduced new standby status for nodes powered off by the farmerbot.
|
||||||
|
- In the explorer, a node monitoring page is now available.
|
||||||
|
- Fixed high CPU usage in the DAO Pages.
|
||||||
|
- Tracking improperly set serial number on nodes with a clear message.
|
||||||
|
|
||||||
|
#### TFGrid Weblets
|
||||||
|
|
||||||
|
- We are phasing out the TFGrid Weblets for a newer playground rewritten in vue3, however, we introduced some maintenance bugfixes.
|
||||||
|
- [Support umbrel on the grid](https://github.com/threefoldtech/home/issues/1394).
|
||||||
|
|
||||||
|
### TF Playground v2.0.0
|
||||||
|
|
||||||
|
This release introduces a new playground with a more consistent user experience. Some components have been reworked for consistency.
|
||||||
|
|
||||||
|
- Simplified the profile manager, requiring only the provision of a mnemonic and a password for encryption on the device. Mnemonics are never shared or sent across the network.
|
||||||
|
- Real-time calculation of deployment costs.
|
||||||
|
- Ability to generate WireGuard configurations.
|
||||||
|
- Direct link to the monitoring page of a deployment’s hosting node.
|
||||||
|
|
||||||
|
## RMB 1.0.5
|
||||||
|
|
||||||
|
- Deprecated seed flag.
|
||||||
@ -0,0 +1,67 @@
|
|||||||
|
# ThreeFold Grid v3.6 Release Note
|
||||||
|
|
||||||
|
Release Note of ThreeFold Grid v3.6. It includes updates, improvements and fixes of numerous grid components as described below.
|
||||||
|
|
||||||
|
## TFPlayground v1.4.3
|
||||||
|
- Updated Farming Calculator
|
||||||
|
- Better node-filtering mechanism by adding 'capacity' filter
|
||||||
|
- Simplified K8s solution deployment by eliminating 'add ssh key' part
|
||||||
|
- Improved UX for manual solution deployment on dedicated nodes
|
||||||
|
- Fixed solution's post-deployment bad gateway issue.
|
||||||
|
- Validation enhancements
|
||||||
|
|
||||||
|
## Uhuru v1.2 (beta)
|
||||||
|
- Tackled the UI/UX issues and bugs.
|
||||||
|
- Added many features except for main missing things such as 'logout' option.
|
||||||
|
|
||||||
|
## ThreeFold Wallet v3.1.0
|
||||||
|
- Enable token unlocking feature
|
||||||
|
- Allow users to unlock their locked tokens via TFwallet.
|
||||||
|
- Improvements and fixes included, including usability supports for iOS devices that will be greatly improved.
|
||||||
|
|
||||||
|
## TFConnect App v3.6.0
|
||||||
|
|
||||||
|
- Better usability and user experience through the app workflow improvements as well as
|
||||||
|
- Improved design and interface, look and feel.
|
||||||
|
|
||||||
|
## TF Planetary Network v0.3.0
|
||||||
|
TF Planetary Network is an application that allows users to access[ Peer To Peer end2end encrypted global network](https://library.threefold.me/info/manual/#/technology/threefold__planetary_network) which lives on top of the existing internet or other Peer To Peer networks created. This release's improvements:
|
||||||
|
|
||||||
|
- New P2P functionalities on Desktop Client
|
||||||
|
- Improved the desktop clients for planetary network by adding support for M1 version of Mac.
|
||||||
|
- Allowed the application to refresh the list of ‘peers’, allowing extra ‘peers’ to be added by TF org
|
||||||
|
- Debugged multiple account issues on Mac.
|
||||||
|
|
||||||
|
## TFTShop (GetTFT) v1.1.1
|
||||||
|
|
||||||
|
- Better usability and user experience through the app workflow improvements
|
||||||
|
- Improved design and interface, look and feel, such as Improvement on TFT purchase flows on all BTC-TFT, and FIAT-TFT transactions
|
||||||
|
|
||||||
|
## TFGrid Proxy v1.5.0
|
||||||
|
TFGrid Proxy is a REST API-based server used to interact with TFGridDB (Database) in order to access all available node-related information. This release's improvements:
|
||||||
|
|
||||||
|
- Added querying for dedicated nodes support in gridproxy API.
|
||||||
|
- Added support for twins and contracts.
|
||||||
|
- Added filter for dedicated nodes
|
||||||
|
- Added missing queries on farms
|
||||||
|
- Added country API for node distribution
|
||||||
|
|
||||||
|
## ZOS v3.1.0
|
||||||
|
- Support pausing workloads to allow grace period before canceling contract.
|
||||||
|
- Enabled log streaming from VMs/Containers to a remote logs aggregation server.
|
||||||
|
|
||||||
|
## TFNode-Pilot v0.1.0
|
||||||
|
Pocket Network is a blockchain data platform built for applications that use cost-efficient economics to coordinate and distribute data at scale, enabling seamless interactions between blockchains and applications. This release's content:
|
||||||
|
|
||||||
|
- Reverse-engineered the Pokt node pilot into Node Pilot Light.
|
||||||
|
- Deployed first version of PoktNetwork with TF Terraform Grid Provider.
|
||||||
|
|
||||||
|
## TFChain v1.12
|
||||||
|
- DAO support
|
||||||
|
- Dedicated nodes support
|
||||||
|
- General stability improvement
|
||||||
|
- Reworked farming policies
|
||||||
|
- Introduction of contract grace periods
|
||||||
|
- Farm certificaation through DAO
|
||||||
|
- New bridge code
|
||||||
|
|
||||||
103
collections/about/roadmap/releasenotes/tfgrid_release_3_6_1.md
Normal file
103
collections/about/roadmap/releasenotes/tfgrid_release_3_6_1.md
Normal file
@ -0,0 +1,103 @@
|
|||||||
|
# ThreeFold Grid v3.6.1 Release Note
|
||||||
|
|
||||||
|
Release Note of ThreeFold Grid v3.6.1 It includes updates, improvements and fixes of numerous grid components as described below.
|
||||||
|
|
||||||
|
## TFGrid 3.6.1 components
|
||||||
|
- testnet tfchain 1.12.1
|
||||||
|
- substrate client (go) release for type change
|
||||||
|
- tfchain client (JS) release for type change
|
||||||
|
- graphql 2.3.3
|
||||||
|
- tfchain bridge v2.1.0
|
||||||
|
- ZOS 3.1.0-rc1
|
||||||
|
- weblets 1.4.3-rc1
|
||||||
|
- terraform 1.2.1
|
||||||
|
- gridproxy v1.5.1
|
||||||
|
- explorer 3.2.2
|
||||||
|
- tfgrid_dashboard 1.0.6
|
||||||
|
|
||||||
|
## Component Upgrades
|
||||||
|
|
||||||
|
### TFPlayground v1.4.3
|
||||||
|
- Updated Farming Calculator
|
||||||
|
- Better node-filtering mechanism by adding 'capacity' filter
|
||||||
|
- Simplified K8s solution deployment by eliminating 'add ssh key' part
|
||||||
|
- Improved UX for manual solution deployment on dedicated nodes
|
||||||
|
- Fixed solution's post-deployment bad gateway issue.
|
||||||
|
- Validation enhancements
|
||||||
|
|
||||||
|
|
||||||
|
### ThreeFold Wallet v3.1.0
|
||||||
|
- Enable token unlocking feature
|
||||||
|
- Allow users to unlock their locked tokens via TFwallet.
|
||||||
|
- Improvements and fixes included, including usability supports for iOS devices that will be greatly improved.
|
||||||
|
|
||||||
|
### TFConnect App v3.6.0
|
||||||
|
|
||||||
|
- Better usability and user experience through the app workflow improvements as well as
|
||||||
|
- Improved design and interface, look and feel.
|
||||||
|
|
||||||
|
### TF Planetary Network v0.3.0
|
||||||
|
TF Planetary Network is an application that allows users to access[ Peer To Peer end2end encrypted global network](https://library.threefold.me/info/manual/#/technology/threefold__planetary_network) which lives on top of the existing internet or other Peer To Peer networks created. This release's improvements:
|
||||||
|
|
||||||
|
- New P2P functionalities on Desktop Client
|
||||||
|
- Improved the desktop clients for planetary network by adding support for M1 version of Mac.
|
||||||
|
- Allowed the application to refresh the list of ‘peers’, allowing extra ‘peers’ to be added by TF org
|
||||||
|
- Debugged multiple account issues on Mac.
|
||||||
|
|
||||||
|
### TFTShop (GetTFT) v1.1.1
|
||||||
|
|
||||||
|
- Better usability and user experience through the app workflow improvements
|
||||||
|
- Improved design and interface, look and feel, such as Improvement on TFT purchase flows on all BTC-TFT, and FIAT-TFT transactions
|
||||||
|
|
||||||
|
### TFGrid Proxy v1.5.0
|
||||||
|
TFGrid Proxy is a REST API-based server used to interact with TFGridDB (Database) in order to access all available node-related information. This release's improvements:
|
||||||
|
|
||||||
|
- Added querying for dedicated nodes support in gridproxy API.
|
||||||
|
- Added support for twins and contracts.
|
||||||
|
- Added filter for dedicated nodes
|
||||||
|
- Added missing queries on farms
|
||||||
|
- Added country API for node distribution
|
||||||
|
|
||||||
|
### ZOS v3.1.0
|
||||||
|
- Support pausing workloads to allow grace period before canceling contract.
|
||||||
|
- Enabled log streaming from VMs/Containers to a remote logs aggregation server.
|
||||||
|
|
||||||
|
### TFNode-Pilot v0.1.0
|
||||||
|
Pocket Network is a blockchain data platform built for applications that use cost-efficient economics to coordinate and distribute data at scale, enabling seamless interactions between blockchains and applications. This release's content:
|
||||||
|
|
||||||
|
- Optimized node pilot by Threefold.
|
||||||
|
- Deployed first version of PoktNetwork with TF Terraform Grid Provider.
|
||||||
|
|
||||||
|
### TFChain v1.12
|
||||||
|
- DAO support
|
||||||
|
- Dedicated nodes support
|
||||||
|
- General stability improvement
|
||||||
|
- Reworked farming policies
|
||||||
|
- Introduction of contract grace periods
|
||||||
|
- Farm certificaation through DAO
|
||||||
|
- New bridge code
|
||||||
|
|
||||||
|
### TFgrid Dashboard
|
||||||
|
Tfgrid Dashboard is the mainhighlight of this release. We aim to have a simpler workflow for our Threefold users and more unified experience. The supported functionalites for this release are:
|
||||||
|
- Farm management
|
||||||
|
- Twin management
|
||||||
|
- Dedicated nodes
|
||||||
|
- Tfchain DAO
|
||||||
|
- Transferring money to TFChain accounts
|
||||||
|
- Swapping tokens on Binance and stellar
|
||||||
|
- Exploring farms
|
||||||
|
- Explorring nodes
|
||||||
|
- Grid statistics
|
||||||
|
|
||||||
|
service is deployed on https://dashboard.test.grid.tf
|
||||||
|
|
||||||
|
### Uhuru v1.4.0 (beta)
|
||||||
|
- Improved mobile View
|
||||||
|
- Improved multiple screen size views
|
||||||
|
- Added support and usability for more browsers (Firefox, Safari, etc)
|
||||||
|
- Added features on chat group management
|
||||||
|
- Full backend rewrite for improved performance, stability and security
|
||||||
|
|
||||||
|
### TFConnect App v3.6.0
|
||||||
|
- UX rewrite on for userflows like the welcome screen, registration screen, planetary network and many more
|
||||||
|
- Added Planetary network for iOS users
|
||||||
101
collections/about/roadmap/releasenotes/tfgrid_release_3_7_0.md
Normal file
101
collections/about/roadmap/releasenotes/tfgrid_release_3_7_0.md
Normal file
@ -0,0 +1,101 @@
|
|||||||
|
# ThreeFold Grid v3.7.0 Release Note
|
||||||
|
|
||||||
|
Release Note of ThreeFold Grid v3.7.0.
|
||||||
|
It includes updates, improvements and fixes of numerous grid components as described below.
|
||||||
|
|
||||||
|
|
||||||
|
## Component Upgrades
|
||||||
|
|
||||||
|
### ThreeFold Wallet v3.7.0
|
||||||
|
- Include the option to show transaction details (Sender, Receiver, Memo, Blockchain hash, Amount, Asset, Date
|
||||||
|
- Added Farmer types details
|
||||||
|
- GraphQL types fix
|
||||||
|
- Enabled wallet deletion
|
||||||
|
- Wallet Cache fixes
|
||||||
|
- Bugs fixes and generic improvements
|
||||||
|
|
||||||
|
### ThreeFold Connect v3.7.0
|
||||||
|
- Improved loading of webpages
|
||||||
|
- Released the IOS version of planetary network
|
||||||
|
- Improved login flow (backend)
|
||||||
|
- Removed the concept of .3bot from the app registration and other display
|
||||||
|
- Re-enable TFChain bridge after twin changed
|
||||||
|
- Backend: Upgraded from Vue v2 to Vue v3
|
||||||
|
- Backend: Full kubernetes test deploy stack.
|
||||||
|
- Frontend: Add typescript, tailwind. Removed the use of vuetify
|
||||||
|
- Generic Bug fixes
|
||||||
|
|
||||||
|
|
||||||
|
### ThreeFold Grid Proxy Client v1.5.9
|
||||||
|
- Initial Grid Proxy Client implementation
|
||||||
|
- Includes the gridproxy API client along with API-specific information
|
||||||
|
- Includes classes that represent entities in the context of the API in the sub-module model (for making conversions between JSON objects and V objects).
|
||||||
|
- Added CI pipeline to run tests
|
||||||
|
|
||||||
|
|
||||||
|
### ThreeFold Chain v2.1.0
|
||||||
|
- Improved Validation for Public Config (Node) by Implementing a maximum size on all types that are filled in by the user or ZOS tfchain
|
||||||
|
- Improved Validation for Interfaces (Node) by Implementing a maximum size on all types that are filled in by the user or ZOS tfchain
|
||||||
|
- Improved Validationfor Public IPs (Farm)
|
||||||
|
- Improved Validation for Twin IPs
|
||||||
|
- Reworked public IPs on Contract, they are now shown as a list with the actual public IP object
|
||||||
|
- Executed billing in a transactional operation tfchain
|
||||||
|
- Added Restriction of deployment hash length (32 bytes)
|
||||||
|
|
||||||
|
### Planetary Network v.3.7.0
|
||||||
|
- Added support for M1 Mac.
|
||||||
|
- Refresh list of peers.
|
||||||
|
- Allow extra peers to be added by TF org.
|
||||||
|
- Fix UI crashing/lags
|
||||||
|
- Build for Ubuntu, Windows, Build for Mac
|
||||||
|
|
||||||
|
### Freeflow Twin Beta 1.5
|
||||||
|
- Major Rebranding from Uhuru to Freeflow Twin
|
||||||
|
- Generic Bug fixes
|
||||||
|
- Enabled tagging people in chats
|
||||||
|
- Improved dev setup
|
||||||
|
- Improved staging+production link setup.
|
||||||
|
- Self-deploy improvements.
|
||||||
|
- PWA support
|
||||||
|
- Add info labels
|
||||||
|
- HTML encoding of messages
|
||||||
|
- Overflow handling
|
||||||
|
- Remember login session
|
||||||
|
- Chat: Added File upload progress view
|
||||||
|
- Chat: Added Link preview
|
||||||
|
- Chat: Adding more search options
|
||||||
|
|
||||||
|
### TFGrid Dashboard v1.1.4
|
||||||
|
- UX/UI : Updated Color Palette
|
||||||
|
- Updated Font styles
|
||||||
|
- Updated sidebar menu UX to include TF Portal, TF Explorer
|
||||||
|
- Enabled day/night mode
|
||||||
|
- TFGrid Explorer: Added Nodes page, Statistic Page, and Farms page ON TFGrid Explorer
|
||||||
|
- TFGrid Explorer: Added category of listed nodes as (dedicated, rented, and arentable)
|
||||||
|
- TFGrid Stats: Updated Minting Details on TF Dashboard
|
||||||
|
- TFGrid Stats: show receipts of previous nodes
|
||||||
|
- TFGrid Stats: Added Calendar UI
|
||||||
|
- Clickable Live Support Chat Popup
|
||||||
|
|
||||||
|
### TF Playground v1.4.4
|
||||||
|
- UX/UI : Updated Color Palette
|
||||||
|
- Updated Fonts.
|
||||||
|
- New Deployment/Solutions Icons in the sidebar.
|
||||||
|
- New Actions Icons in the deployment list.
|
||||||
|
- Added Solution Categories
|
||||||
|
- Enabled custom ‘Presearch instance’ deployment
|
||||||
|
- New Capacity Filter
|
||||||
|
- Add IPv4 Planetary Network Filter for specific instance deployments
|
||||||
|
- Newly improved Capacity Management for solution deployment: enabling the setting of a full VM as the default Virtual Machine for deployment,
|
||||||
|
- Easily fund a deployment profile / ID by scanning your ID wallet QR Code
|
||||||
|
- Profile Manager: Avoid losing deployment with Grace Period Listing
|
||||||
|
- provide a simple list where you can select one of the online Grid gateways
|
||||||
|
- Profile Management: Add ‘Confirmation’ popup before deleting a deployment profile
|
||||||
|
- Added an Identifier for the current network in the sidebar (main/test/devnet)
|
||||||
|
- TF Playground Wallet: show unlocked/locked tokens in balance
|
||||||
|
- Profile Management: allow a user to create a profile with no SSH key.
|
||||||
|
- TFGrid Client TS supports Algorand, Stellar, and TFChain Modules.
|
||||||
|
- NEW Node Pilot Instance Deployment
|
||||||
|
- NEW Subsquid Solution
|
||||||
|
|
||||||
|
|
||||||
@ -0,0 +1,74 @@
|
|||||||
|
# ThreeFold Grid v3.8.0 Release Note
|
||||||
|
|
||||||
|
Release Note of ThreeFold Grid v3.8.0.
|
||||||
|
Live on Testnet 02/02/2023
|
||||||
|
|
||||||
|
This release note includes updates, improvements and fixes of numerous grid components as described below:
|
||||||
|
|
||||||
|
## The Components
|
||||||
|
|
||||||
|
- TFChain v2.2.0
|
||||||
|
- ZOS v3.4.0
|
||||||
|
- TF Weblets v1.6.0
|
||||||
|
- TF Dashboard v1.3.0
|
||||||
|
- TFGrid Client v1.5.0
|
||||||
|
- TFGrid Proxy v1.6.5
|
||||||
|
- Terraform v1.6.0
|
||||||
|
|
||||||
|
## Upgrades and Improvements
|
||||||
|
|
||||||
|
### TFChain v2.2.0
|
||||||
|
- Added [Third Party Billing Services](https://github.com/threefoldtech/tfchain/blob/12bc8842c7c321d22e36667a91dfc5d3c7d04ab8/substrate-node/pallets/pallet-smart-contract/service_consumer_contract_flow.md), allowing defining contracts between TFChain users for a service and the billing.
|
||||||
|
- Reworked billing flow, see [details here](https://github.com/threefoldtech/tfchain/issues/269).
|
||||||
|
- Infrastructure wise, we have integrated [Firesquid](https://docs.subsquid.io/), which is showing promising improvements in regards of the storage and data syncing.
|
||||||
|
- Added Bugfixes around data validations and improving migrations
|
||||||
|
|
||||||
|
### ZOS v3.4.0
|
||||||
|
This release was mainly focused on the stabilization of ZOS, Monitoring Support, upgrading components and fixing bugs as described below:
|
||||||
|
- Vector and Node-exporter support for [monitoring](https://metrics.grid.tf/)
|
||||||
|
- Bugfixes / hardening around uptime reports, capacity reports and QSFS workloads cleanup
|
||||||
|
- Added fixes for Grace Period regression
|
||||||
|
- Added fixes for ZOS Nodes Recovery after Network Outages
|
||||||
|
- Uptime reports rework: allowing it to happen every 40 minutes, instead of evey 2 hours
|
||||||
|
- Added Grace Period Workload Regression fixes
|
||||||
|
|
||||||
|
[3.4 milestone](https://github.com/threefoldtech/zos/milestone/11) for more details
|
||||||
|
|
||||||
|
### TF Weblets v1.6.0
|
||||||
|
- Support [Algorand](https://www.algorand.com/) solution deployment
|
||||||
|
- Simplified Weblet's Profile Manager
|
||||||
|
- Support [Mastodon](https://joinmastodon.org/) solution deployment
|
||||||
|
- Upgraded [Discourse](https://www.discourse.org/) solution deployment support
|
||||||
|
- Various bugfixes and [UI Improvements](https://github.com/orgs/threefoldtech/projects/172/views/6)
|
||||||
|
|
||||||
|
For more detailed information on this component release, please see [TF Weblets v1.6.0 Milestone](https://github.com/threefoldtech/grid_weblets/milestone/10)
|
||||||
|
|
||||||
|
### TF Dashboard v1.3.0
|
||||||
|
- Fixed broken 'Filter by Farm ID'
|
||||||
|
- Added fixes on HRU Filter
|
||||||
|
- Added Validation function on recipient's TFT address
|
||||||
|
- Added updates to sidebar icons
|
||||||
|
- Improved new farm addition function
|
||||||
|
- Added node filters validations fix
|
||||||
|
- Support filtering nodes by farm name
|
||||||
|
- Added Monitoring dashboard
|
||||||
|
|
||||||
|
For more detailed information on this component release, please see [TF Dashboard v1.3.0 Milestone](https://github.com/threefoldtech/tfgrid_dashboard/milestone/12)
|
||||||
|
|
||||||
|
### TFGrid Client 1.5.0
|
||||||
|
- Added ZLogs workload support
|
||||||
|
- Added documentation updates
|
||||||
|
|
||||||
|
### Terraform 1.6.0
|
||||||
|
- Capacity planning upgrade
|
||||||
|
- Added Kubernetes token validation function
|
||||||
|
|
||||||
|
## TFGrid Proxy v1.6.5
|
||||||
|
- Added fixes on dedicated nodes reservation
|
||||||
|
- Added fixes on TCP connection leaks
|
||||||
|
- Added Swagger Docs fixes
|
||||||
|
- Added Updates to stats endpoint
|
||||||
|
- Added new queries for total resources
|
||||||
|
- Added more parameters to /nodes enpoint for filter by twin_id and node_id
|
||||||
|
|
||||||
|
For more detailed information on this component release, please see [TFGrid Proxy v1.6.5 Milestone](https://github.com/threefoldtech/tfgridclient_proxy/milestone/5)
|
||||||
170
collections/about/roadmap/releasenotes/tfgrid_release_3_9_0.md
Normal file
170
collections/about/roadmap/releasenotes/tfgrid_release_3_9_0.md
Normal file
@ -0,0 +1,170 @@
|
|||||||
|
# ThreeFold Grid v3.9.0 Release Note
|
||||||
|
|
||||||
|
Release Note of ThreeFold Grid v3.9.0.
|
||||||
|
|
||||||
|
- Live on Mainnet 12/04/2023
|
||||||
|
- Live on Testnet 23/03/2023
|
||||||
|
|
||||||
|
|
||||||
|
This release is mainly around power management/capacity planning orchestrated by the farmerbot based on Wake-on Lan (WOL) and the reliable message bus (RMB) and the toolings update to utilize both. It also includes several other updates, improvements and fixes of numerous grid components as described below:
|
||||||
|
|
||||||
|
## The Components
|
||||||
|
|
||||||
|
- TFChain v2.3.0
|
||||||
|
- ZOS v3.6.0
|
||||||
|
- TF Farmerbot v1.0.0
|
||||||
|
- TF Weblets v1.7.0
|
||||||
|
- TF Dashboard v1.4.0
|
||||||
|
- TF Gridclient v2.0.0
|
||||||
|
- TF Gridproxy v1.7.0
|
||||||
|
- Terraform v1.8.x
|
||||||
|
- RMB-RS v1.0.2
|
||||||
|
- TFChain-GraphQL v2.9.0
|
||||||
|
|
||||||
|
## Upgrades and Improvement Highlights
|
||||||
|
|
||||||
|
Below are some of the highlights of TFGrid v3.9.0 component upgrades and improvements.
|
||||||
|
Feel free to check [TFGrid v3.9.0 Project](https://github.com/orgs/threefoldtech/projects/172) for a more detailed overview of the TFGrid v3.9.0 release.
|
||||||
|
|
||||||
|
|
||||||
|
### RMB-RS v1.0.2
|
||||||
|
|
||||||
|
Reliable Message Bus Relay (RMB-RS) is a secure communication panel that allows bots to communicate together in a chat-like way. It makes it very easy to host a service or a set of functions to be used by anyone, even if your service is running behind NAT.
|
||||||
|
|
||||||
|
- Guarantee authenticity of the messages. You are always sure that the received message is authentic from the sender.
|
||||||
|
- End-to-end encryption support.
|
||||||
|
- Support for third-party hosted Relays. Anyone can host a Relay and people can use it safely since there is no way messages can be inspected while using e2e. That's similar to home servers by matrix.
|
||||||
|
|
||||||
|
See [Specifications](https://github.com/threefoldtech/rmb-rs/blob/main/docs/readme.md) for more information.
|
||||||
|
|
||||||
|
> Below is the list of the __Public Relay Addresses__ hosted by Threefold:
|
||||||
|
|
||||||
|
- Dev: wss://relay.dev.grid.tf
|
||||||
|
- QA: wss://relay.qa.grid.tf
|
||||||
|
- Test: wss://relay.test.grid.tf
|
||||||
|
- Main: wss://relay.grid.tf
|
||||||
|
|
||||||
|
__Impacted Clients:__
|
||||||
|
|
||||||
|
- [RMB-SDK-TS](https://github.com/threefoldtech/rmb-sdk-ts/releases/tag/v1.1.1)
|
||||||
|
- [RMB-SDK-GO](https://github.com/threefoldtech/rmb-sdk-go/releases/tag/v1.0.0)
|
||||||
|
|
||||||
|
|
||||||
|
### TFChain v2.3.0
|
||||||
|
|
||||||
|
On this release, we modified the twin objects on TFChain and removed the notion of an `IP`. We added 2 fields (`Relay` and `PK`) onto the twins.
|
||||||
|
|
||||||
|
- __Relay__: an RMB Relay Address which a client can connect to (See RMB changes)
|
||||||
|
- __PK__: a public key for an encryption key which can be used to encrypt messages on the Public Relay, if not set, traffic will be unencrypted.
|
||||||
|
|
||||||
|
__Impacted Clients:__
|
||||||
|
|
||||||
|
- [Grid3_Client_RS](https://github.com/threefoldtecharchive/grid3_client_rs/releases/tag/v0.2.0)
|
||||||
|
|
||||||
|
### TFChain-GraphQL v2.9.0
|
||||||
|
|
||||||
|
An important note for users, that multiple steps would be required to upgrade your TFChain-GraphQL into the latest v2.9.0 release, as described below:
|
||||||
|
|
||||||
|
1. Restart the ingester from scratch using the new config
|
||||||
|
2. Restart the processor from scratch using the new code
|
||||||
|
|
||||||
|
Please make sure all data is wiped before restarting both services.
|
||||||
|
|
||||||
|
### TF Famerbot v1.0.0
|
||||||
|
|
||||||
|
TF Farmerbot is a new component that aim as a power management solution that would allow farmer to setup to enable Wake-on-LAN mechanism on their farms.
|
||||||
|
|
||||||
|
## Other Component Changelogs
|
||||||
|
|
||||||
|
### TFChain v2.3.0
|
||||||
|
|
||||||
|
- Fixed locked balances
|
||||||
|
- Added extra field to twin for publickey
|
||||||
|
- Fixed serial number validation was blocking nodes from registration
|
||||||
|
- Added fixes on Farming policies on Testnet
|
||||||
|
- Allow farms to Add public IP ranges
|
||||||
|
- Support power management and capacity planning
|
||||||
|
- Fixed TFT price on mainnet
|
||||||
|
- Reworked migrations
|
||||||
|
- Set node's last uptime when the node send an uptime event
|
||||||
|
- Disable twin deletion
|
||||||
|
- Bug fixes around data validations, and more.
|
||||||
|
|
||||||
|
Please follow [this milestone](https://github.com/threefoldtech/tfchain/milestone/11) for more.
|
||||||
|
|
||||||
|
### ZOS v3.6.0
|
||||||
|
|
||||||
|
- Support Switching dhcpd from udhcpd
|
||||||
|
- WOL support
|
||||||
|
- Power Management support
|
||||||
|
- Fixed gateways backend validation
|
||||||
|
- Added number of workloads and deployments to zos reported statistics
|
||||||
|
- Support the new RMB and Relay
|
||||||
|
- Provide clearer messaging during twin registration
|
||||||
|
|
||||||
|
Please follow [this milestone](https://github.com/threefoldtech/zos/milestone/12) for more details
|
||||||
|
|
||||||
|
### TF Farmerbot v1.0.0
|
||||||
|
|
||||||
|
- Initial Release
|
||||||
|
- Added Support for Power Management feature
|
||||||
|
- Added Support for Capacity Planning feature
|
||||||
|
|
||||||
|
### TF Weblets v1.7.0
|
||||||
|
|
||||||
|
- NEW Wordpress solution
|
||||||
|
- NEW Umbrel solution
|
||||||
|
- Added live button support
|
||||||
|
- Better error reporting mechanism
|
||||||
|
- Support Mnemonics field editing
|
||||||
|
- Removed flash messages after successfull deployment
|
||||||
|
|
||||||
|
Please follow [this milestone](https://github.com/threefoldtech/grid_weblets/milestone/9) for more details
|
||||||
|
|
||||||
|
### TF Dashboard v1.4.0
|
||||||
|
|
||||||
|
- Public IP validation
|
||||||
|
- RenameD 'Swap' page to 'Bridge'
|
||||||
|
- Support setting Relay and Public Key
|
||||||
|
- Added filter by Country validation
|
||||||
|
- Filter farms by pricing policy support
|
||||||
|
- Resource pricing calculator discount distinction between shared and dedicated nodes
|
||||||
|
|
||||||
|
Please follow [this milestone](https://github.com/threefoldtech/tfgrid_dashboard/milestone/13) for more details
|
||||||
|
|
||||||
|
### TF GridClient v2.0.0
|
||||||
|
|
||||||
|
- Added Support for RMB and Public Key of Twins
|
||||||
|
- Added Support for Farmerbot
|
||||||
|
- Added pricing calculator module
|
||||||
|
- Support service contracts
|
||||||
|
- Added size property to QSFS model
|
||||||
|
- HTTP server mode allows configuration file for user credentials
|
||||||
|
- Added fixes on 'Filter nodes by farmID' featue
|
||||||
|
|
||||||
|
### Terraform v1.8.x
|
||||||
|
|
||||||
|
- Added Support for RMB and RMB Relay
|
||||||
|
- Added Support for deployment using direct client
|
||||||
|
- Added Support for parallel deployment of resources
|
||||||
|
- Expand resources and data sources documentation
|
||||||
|
|
||||||
|
Please follow [this milestone](https://github.com/threefoldtech/terraform-provider-grid/milestone/16) for more details
|
||||||
|
|
||||||
|
## RMB v1.0.2
|
||||||
|
|
||||||
|
The new version of RMB written in Rust
|
||||||
|
|
||||||
|
- Added Federation support
|
||||||
|
- Added Signing and end-to-end encryption
|
||||||
|
- RMB-Peer for compatibility
|
||||||
|
- Added Ratelimiting support
|
||||||
|
|
||||||
|
## TFGrid Proxy v1.7.0
|
||||||
|
|
||||||
|
- Removed the proxying features, obsoleted by the new RMB.
|
||||||
|
|
||||||
|
Please follow [this milestone](https://github.com/threefoldtech/tfgridclient_proxy/milestone/6) for more details
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
11
collections/about/roadmap/roadmap_readme.md
Normal file
11
collections/about/roadmap/roadmap_readme.md
Normal file
@ -0,0 +1,11 @@
|
|||||||
|
# ThreeFold Grid and Product Roadmap
|
||||||
|
|
||||||
|
Welcome to ThreeFold's product roadmap! We are thrilled to have you on board as we journey towards a decentralized and sustainable future. Our product roadmap outlines the innovative solutions and technologies we are developing to revolutionize the way we compute, store data, and connect. Here, you will find a comprehensive overview of our latest and upcoming releases, enhancements, and advancements across our ecosystem.
|
||||||
|
|
||||||
|
> Click [here](../../technology/concepts/grid3_components.md) to see the complete TFGrid Component List
|
||||||
|
|
||||||
|
## Table of Contents
|
||||||
|
|
||||||
|
- [TFGrid v3.x Announcement (Aug 2021 - Forum)](https://forum.threefold.io/t/announcement-of-tfgrid-3-0/1132)
|
||||||
|
- [What's new on TFGrid v3.x](../../technology/concepts/grid3_whatsnew.md)
|
||||||
|
- [Release Notes](./releasenotes/releasenotes_readme.md)
|
||||||
30
collections/about/tfchain.md
Normal file
30
collections/about/tfchain.md
Normal file
@ -0,0 +1,30 @@
|
|||||||
|
<h1> TFChain </h1>
|
||||||
|
|
||||||
|
<h2>Table of Contents</h2>
|
||||||
|
|
||||||
|
- [Introduction](#introduction)
|
||||||
|
- [TFChain Uses](#tfchain-uses)
|
||||||
|
|
||||||
|
***
|
||||||
|
|
||||||
|
## Introduction
|
||||||
|
|
||||||
|
TFChain is a blockchain based on Parity Substrate which manages the TFGrid 3.x.
|
||||||
|
|
||||||
|
TFChain is a combination of TFChain nodes.
|
||||||
|
|
||||||
|
## TFChain Uses
|
||||||
|
|
||||||
|
This blockchain is used for:
|
||||||
|
|
||||||
|
- storing information as needed on the ThreeFold Grid
|
||||||
|
- identity information of entities (person and company)
|
||||||
|
- 3node phone book, where are the 3nodes, how much capacity, which farmer
|
||||||
|
- TF Farmer's, where are they based, how long active, reputation
|
||||||
|
- DigitalTwin Phonebook, registry of all digital_twins, where are they, public key, unique id, ... (\*1)
|
||||||
|
- Reputation information : how good is a farmer, uptime of a 3Node (\*2)
|
||||||
|
- Account_Metadata which is information about a digital currency wallet/account needed for vesting, locking, ...
|
||||||
|
- backend for Consensus_Engine.
|
||||||
|
- smartcontract_it layer (how to provision workloads on top of TFGrid)
|
||||||
|
- the backend for TFChainDB
|
||||||
|
|
||||||
30
collections/about/threefold_ag.md
Normal file
30
collections/about/threefold_ag.md
Normal file
@ -0,0 +1,30 @@
|
|||||||
|
<h1> ThreeFold Switzerland </h1>
|
||||||
|
|
||||||
|
<h2>Table of Contents</h2>
|
||||||
|
|
||||||
|
- [Introduction](#introduction)
|
||||||
|
- [Some Plans](#some-plans)
|
||||||
|
|
||||||
|
***
|
||||||
|
|
||||||
|
## Introduction
|
||||||
|
|
||||||
|
ThreeFold Switzerland is officially called ThreeFold AG.
|
||||||
|
|
||||||
|
While there are activities done at this time, we are preparing for future activities.
|
||||||
|
|
||||||
|
## Some Plans
|
||||||
|
|
||||||
|
- Promotion of ThreeFold, specifically in Zug Communities (CH).
|
||||||
|
|
||||||
|
<!--
|
||||||
|
|
||||||
|
## Structure: March 2020
|
||||||
|
|
||||||
|
TODO: need link to official doc, address, ...
|
||||||
|
|
||||||
|
<!-- TODO: are we part of https://cryptovalley.swiss/ , if yes link to it
|
||||||
|
|
||||||
|
!!!def alias:threefold_ag,tf_ag,threefold_ch,tf_ch,ThreeFold_Switzerland,TF_Switzerland -->
|
||||||
|
|
||||||
|
|
||||||
40
collections/about/threefold_companies.md
Normal file
40
collections/about/threefold_companies.md
Normal file
@ -0,0 +1,40 @@
|
|||||||
|
<h1> ThreeFold Related Companies </h1>
|
||||||
|
|
||||||
|
<h2>Table of Contents</h2>
|
||||||
|
|
||||||
|
- [Introduction](#introduction)
|
||||||
|
- [Companies Overview](#companies-overview)
|
||||||
|
|
||||||
|
***
|
||||||
|
|
||||||
|
## Introduction
|
||||||
|
|
||||||
|
The following companies are related parties to ThreeFold. Our terms and conditions apply.
|
||||||
|
|
||||||
|
## Companies Overview
|
||||||
|
|
||||||
|
| THREEFOLD RELATED COMPANIES | Description |
|
||||||
|
| --------------------------------------------------------------- | ---------------------------------------------------------------------------------- |
|
||||||
|
| [ThreeFold Dubai or ThreeFold Cloud](./threefold_dubai.md) | Promotion of TFGrid + Delivery of ThreeFold Cloud |
|
||||||
|
| [Threefold_Tech](./threefold_tech.md) | Belgium-based tech company owns IP (Intellectual Property) of tech, is open source |
|
||||||
|
| [ThreeFold_VZW](./threefold_vzw.md) | Non for profit organization in BE, intented to be used for grants work. |
|
||||||
|
| [ThreeFold_AG](./threefold_ag.md) | ThreeFold in Zug, Switzerland |
|
||||||
|
| TF Hub Limited | ThreeFold in BVI |
|
||||||
|
| Codescalers | Egypt-based software development team, creates a lot of code for ThreeFold |
|
||||||
|
|
||||||
|
|
||||||
|
| FARMING COOPERATIVES | |
|
||||||
|
| ------------------------------------ | ------------------------------------------------ |
|
||||||
|
| [Mazraa](./mazraa.md) | A farmer in Middle East who is part of ThreeFold_Dubai |
|
||||||
|
| [BetterToken](./bettertoken.md) | BetterToken is the very first ThreeFold Farming Cooperative in Europe |
|
||||||
|
|
||||||
|
|
||||||
|
| SOME LARGER FARMERS | |
|
||||||
|
| ------------------- | ---------------------------------------------------------------- |
|
||||||
|
| Green Edge | Early ThreeFold Farmer providing decentralized compute & storage |
|
||||||
|
| Bancadati | Large ThreeFold Farmer in Switzerland |
|
||||||
|
| Moresi | A neutral, technologically advanced data center in Switzerland |
|
||||||
|
| there are many more | ... |
|
||||||
|
|
||||||
|
> Please note, ThreeFold Grid 3.x operates as a [DAO](./dao/dao.md) every party who wants to participate with the ThreeFold Grid uses the [TFChain](./tfchain.md) and our Forums.
|
||||||
|
> [Click here for more info about our DAO](./dao/tfdao.md)
|
||||||
61
collections/about/threefold_dubai.md
Normal file
61
collections/about/threefold_dubai.md
Normal file
@ -0,0 +1,61 @@
|
|||||||
|
<h1> ThreeFold Dubai </h1>
|
||||||
|
|
||||||
|
<h2>Table of Contents </h2>
|
||||||
|
|
||||||
|
- [Introduction](#introduction)
|
||||||
|
- [Responsibilities](#responsibilities)
|
||||||
|
- [NEW 2023](#new-2023)
|
||||||
|
- [Some memories from 2015+](#some-memories-from-2015)
|
||||||
|
- [Structure: Oct 2021 - Dec 2022](#structure-oct-2021---dec-2022)
|
||||||
|
- [Official License](#official-license)
|
||||||
|
|
||||||
|
***
|
||||||
|
|
||||||
|
## Introduction
|
||||||
|
|
||||||
|
ThreeFold Dubai is the original team of ThreeFold operated from Dubai and Belgium. We started in 2016.
|
||||||
|
|
||||||
|
## Responsibilities
|
||||||
|
|
||||||
|
- Promote ThreeFold Grid and the ThreeFold Token
|
||||||
|
- Work with [ThreeFold Tech](./threefold_tech.md) for the creation and maintenance of the technology.
|
||||||
|
- Legal: signing party with all T&C (terms and conditions) with all future farmers
|
||||||
|
- Work with many people and companies around the world to grow the threefold ecosystem
|
||||||
|
- Look for partners who are willing to grow the threefold ecosystem
|
||||||
|
|
||||||
|
## NEW 2023
|
||||||
|
|
||||||
|
ThreeFold Dubai = ThreeFold DMCC and will launch a commercial business on top of the TFGrid.
|
||||||
|
|
||||||
|
See more info in [this google doc](https://docs.google.com/document/d/10Ieu1D00vZdVNP9nQESk4WMszAM5vqi8XoWzSBy3xPU/edit)
|
||||||
|
|
||||||
|
## Some memories from 2015+
|
||||||
|
|
||||||
|
At one point in time we had our office on the 74th floor of a building close to the Dubai International Airport. It was a cool spot with a great view, but we also realized the importance of being located closer to the ground. We only stayed there for just a little more than 1 year.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
Our main office was and still is in Al Jadaf which is, interestingly enough, a boat shipyard. This is where a lot of the ideas and work has been done to make ThreeFold possible.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
The tower on the left in the photo above is where our office was. The place behind (to the right) is called Al Jadaf. We decided to do something different compared to most. No office in a fancy office building. Instead we have our office next to the water in a very old shipyard. Very unique, and it much more cost effective as well. (-:
|
||||||
|
|
||||||
|
Still today there are more than 100 servers located there in our testlab, and the ThreeFold Dubai was run from there.
|
||||||
|
|
||||||
|
## Structure: Oct 2021 - Dec 2022
|
||||||
|
|
||||||
|
- ThreeFold Dubai is our operational HQ from where all Foundation activities are coordinated.
|
||||||
|
- ThreeFold Dubai was mainly funded from TFTech (during 2019-2022), this will now change in 2023
|
||||||
|
- ThreeFold Dubai sometimes uses ThreeFold Labs IT which is a Dubai onshore company for when we need onshore activities like visa's for our people, workpermits, invoicing, ... ThreeFold Labs IT is just a services company to deal with some of these practical elements.
|
||||||
|
|
||||||
|
Adnan Fatayerji is the managing director and shareholder, in the future the shares of ThreeFold Dubai will be 100% owned by The OurWorld Venture Creator
|
||||||
|
|
||||||
|
## Official License
|
||||||
|
|
||||||
|
Please see below the ThreeFold DMCC license:
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
59
collections/about/threefold_history.md
Normal file
59
collections/about/threefold_history.md
Normal file
@ -0,0 +1,59 @@
|
|||||||
|
<h1> ThreeFold History </h1>
|
||||||
|
|
||||||
|
<h2>Table of Contents</h2>
|
||||||
|
|
||||||
|
- [Introduction](#introduction)
|
||||||
|
- [History](#history)
|
||||||
|
- [ThreeFold Project Funding Total](#threefold-project-funding-total)
|
||||||
|
- [Status](#status)
|
||||||
|
- [Genesis Pool](#genesis-pool)
|
||||||
|
- [History of Tokens](#history-of-tokens)
|
||||||
|
|
||||||
|
***
|
||||||
|
|
||||||
|
## Introduction
|
||||||
|
|
||||||
|
The project, now in its sixth year and is gratefulf or the support of its community and commercial entity [ThreeFold Tech](https://github.com/threefoldtech).
|
||||||
|
|
||||||
|
ThreeFold is fundamentally a decentralized initiative. Within this framework, ThreeFold Dubai plays a pivotal role in championing and advancing the ThreeFold Grid and the broader movement.
|
||||||
|
|
||||||
|
Our founders have largely retained their tokens, with only minimal sales, if any. Their intent is clear: they plan to hold onto their tokens until the grid achieves global recognition and the token value surpasses 0.2 USD.
|
||||||
|
|
||||||
|
## History
|
||||||
|
|
||||||
|
In the earlier days of ThreeFold, there were multiple teams collaborating, but the two core teams were located in Dubai and Belgium.
|
||||||
|
|
||||||
|
A group of early supporters bought IT capacity (through buying TFT) from our Genesis pool and our early farmers. These buyers could use their TFT to buy IT capacity from [ThreeFold Dubai](./threefold_dubai.md) or [BetterToken](./bettertoken.md) BV until April 2020, or from the TF Grid directly in a fully decentralized way starting May 2020.
|
||||||
|
|
||||||
|
The ThreeFold Grid is the result of many farmers using the open source technology of ThreeFold Tech.
|
||||||
|
|
||||||
|
Originally, the technology used was created by three companies: GreenIT Globe, ThreeFold Dubai & ThreeFold Tech. The last two still actively participate in the creation of tech components or content as used by all ThreeFold Farmers today.
|
||||||
|
|
||||||
|
## ThreeFold Project Funding Total
|
||||||
|
|
||||||
|
How much funding was used to make the ThreeFold project possible?
|
||||||
|
|
||||||
|
> +- 50M USD
|
||||||
|
|
||||||
|
- +20M USD for all farming (thank you farmers)
|
||||||
|
- 15M USD in ThreeFold Tech as convertible loan (by 50+ investors)
|
||||||
|
- 5M USD in early IT capacity purchases (as TFT)
|
||||||
|
- +10M USD funding from Incubaid/Kristof (estimate)
|
||||||
|
- ThreeFold Tech was established Oct 2018, from out of Incubaid
|
||||||
|
- Related to people related to [Incubaid](https://www.incubaid.com)
|
||||||
|
- Over quite some years, multiple companies/projects
|
||||||
|
|
||||||
|
## Status
|
||||||
|
|
||||||
|
We have worked with multiple regions over the years to look for appropriate structures, we realize we need more funding as such we have launched a venture creator in mauritius who will hopefully invest 7.5m EUR in TFTech as well as in TF Dubai.
|
||||||
|
|
||||||
|
See our [overview of our companies](./threefold_companies.md)
|
||||||
|
|
||||||
|
|
||||||
|
## Genesis Pool
|
||||||
|
|
||||||
|
To kickstart the ThreeFold Grid back in 2017 the foundation committed large amounts of capacity to the grid. This was called the [Genesis Pool](./genesis_pool.md) and the tokens sold as mentioned could be used to use capacity from this pool and more.
|
||||||
|
|
||||||
|
## History of Tokens
|
||||||
|
|
||||||
|
For more info about history of tokens, see [token history](./token_history.md).
|
||||||
41
collections/about/threefold_tech.md
Normal file
41
collections/about/threefold_tech.md
Normal file
@ -0,0 +1,41 @@
|
|||||||
|
<h1> ThreeFold Tech </h1>
|
||||||
|
|
||||||
|
<h2>Table of Contents </h2>
|
||||||
|
|
||||||
|
- [Overview](#overview)
|
||||||
|
- [Location](#location)
|
||||||
|
|
||||||
|
***
|
||||||
|
|
||||||
|
## Overview
|
||||||
|
|
||||||
|
Company developing & promoting software for self-healing, self-driving cloud & blockchain workloads. Has developed most of the software as used in the ThreeFold_Grid.
|
||||||
|
|
||||||
|
- TFTech is working together with industry partners to sell its software
|
||||||
|
- Major partners: HPE, Solidaridad, Kleos (learn more on [threefold.io/partners](https://threefold.io/partners)
|
||||||
|
- Income - License and OEM agreements involving the TFTech technology: - License fees can be in the form of a revenue share on commercial products being developed on top of the TF platform. - With respect to the TF Grid, a fee of 10% of revenue generated is charged
|
||||||
|
for as a license fee for certified edge Internet Capacity registered on the TF Grid
|
||||||
|
network
|
||||||
|
- Investors to this point:
|
||||||
|
- Self-funded by founders & current funding round
|
||||||
|
|
||||||
|
see https://threefold.tech/
|
||||||
|
|
||||||
|
We believe that doing good for the world and growing a successful software company can go hand in hand.
|
||||||
|
|
||||||
|
ThreeFold Tech is a Belgium-based for-profit software company that believes that doing good for the world and building a successful company can go hand-in-hand. They are responsible for the technology behind the ThreeFold_Grid.
|
||||||
|
|
||||||
|
ThreeFold Tech business wise focusses on
|
||||||
|
|
||||||
|
- [X] sell licenses to companies and/or governments to deploy private versions of our cloud technology.
|
||||||
|
- [X] create an antidote for the Cyberpandemic, help customers to protect themselves against this huge threat.
|
||||||
|
|
||||||
|
The company is 80% engineering centric today.
|
||||||
|
|
||||||
|
> TFTech has no links to tokens, at this point (March 2021) does not own any of them either. All Token & TFGrid activities are coordinate from ThreeFold Dubai.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
## Location
|
||||||
|
|
||||||
|
|
||||||
48
collections/about/threefold_vzw.md
Normal file
48
collections/about/threefold_vzw.md
Normal file
@ -0,0 +1,48 @@
|
|||||||
|
<h1> ThreeFold VZW </h1>
|
||||||
|
|
||||||
|
<h2>Table of Contents</h2>
|
||||||
|
|
||||||
|
- [Introduction](#introduction)
|
||||||
|
- [Functions](#functions)
|
||||||
|
- [Some History](#some-history)
|
||||||
|
- [Belgium Official Doc](#belgium-official-doc)
|
||||||
|
|
||||||
|
***
|
||||||
|
|
||||||
|
## Introduction
|
||||||
|
|
||||||
|
ThreeFold VZW is a non for profit organization based in Belgium.
|
||||||
|
|
||||||
|
A **VZW** has no shareholders, only members.
|
||||||
|
|
||||||
|
<!-- [filename](structure/images_threefold_vzw.html ':include :type=iframe width=100% height=550px frameBorder="0" scrolling="no" align="center"')
|
||||||
|
-->
|
||||||
|
|
||||||
|
## Functions
|
||||||
|
|
||||||
|
- owner of the wisdom_council
|
||||||
|
- eventuallly ThreeFold VZW will own some decentralized organizations as operating in the ThreeFold world e.g. [TF Dubai](./threefold_dubai.md)
|
||||||
|
|
||||||
|
## Some History
|
||||||
|
|
||||||
|
We all started in Belgium from Korenlei 22, a super old building in the middle of the town. It dates back to 1731.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
Now the foundation has another address in Lochristi.
|
||||||
|
|
||||||
|
<!--
|
||||||
|
|
||||||
|
Todo: Find/create wisdom council page
|
||||||
|
|
||||||
|
The **VZW** is home to the [Wisdom Council](wisdom_council) -->
|
||||||
|
|
||||||
|
## Belgium Official Doc
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
<!-- see [threefold_vzw_be_book_20067539.pdf]() -->
|
||||||
|
|
||||||
|
See also https://trendstop.knack.be/en/detail/747872572/threefold-foundation.aspx
|
||||||
96
collections/about/token_history.md
Normal file
96
collections/about/token_history.md
Normal file
@ -0,0 +1,96 @@
|
|||||||
|
<h1> Token History </h1>
|
||||||
|
|
||||||
|
<h2>Table of Contents </h2>
|
||||||
|
|
||||||
|
- [Introduction](#introduction)
|
||||||
|
- [Quick History Overview](#quick-history-overview)
|
||||||
|
- [Organic Growth](#organic-growth)
|
||||||
|
- [Farming Model Improvements](#farming-model-improvements)
|
||||||
|
- [TFT Versions](#tft-versions)
|
||||||
|
- [Migration](#migration)
|
||||||
|
- [Migration from TFTv1 Rivine to TFTv1 Stellar (2020)](#migration-from-tftv1-rivine-to-tftv1-stellar-2020)
|
||||||
|
- [Migration from TFTv1 Stellar (Staking Pool=TFTA) to TFTv2 Stellar (Trading or Production Pool=TFT)](#migration-from-tftv1-stellar-staking-pooltfta-to-tftv2-stellar-trading-or-production-pooltft)
|
||||||
|
- [Technical Information](#technical-information)
|
||||||
|
|
||||||
|
***
|
||||||
|
|
||||||
|
## Introduction
|
||||||
|
|
||||||
|
We present the ThreeFold token history and the path from TFT v1 towards TFT v2.
|
||||||
|
|
||||||
|
## Quick History Overview
|
||||||
|
|
||||||
|
- More than 10 years ago, this project started from out of our incubator (see [Incubaid](https://www.incubaid.com))
|
||||||
|
- More than 6 years ago TF Foundation started deploying capacity for development purposes
|
||||||
|
- This became our ([our genesis pool](./genesis_pool.md)), which is the beginning of farming
|
||||||
|
- In 2017-18, value of the genesis pools were about 7m USD in TFT (tokens did not exist yet)
|
||||||
|
- Genesis pools are owned by ThreeFold Dubai (ThreeFold_Dubai).
|
||||||
|
- March 2018 our first-generation blockchain for the ThreeFold_Token saw daylight
|
||||||
|
- The TFT v1 was launched on a blockchain called Rivine (PTO)
|
||||||
|
- The genesis pool resulted in the first batch initial TFT
|
||||||
|
- The blockchain nodes were hosted by +30 different parties completely unrelated to each other
|
||||||
|
- In Q2 2019, ThreeFold_Dubai launched our generation 1 of our TF Grid
|
||||||
|
- April 2020 ThreeFold_Dubai launched the TFGrid v2.0 which is now public and usable by the world
|
||||||
|
- ThreeFold has a new website and a new wiki
|
||||||
|
- The farmers & TFT holders have at their own will upgraded their wallets, zero-nodes, ...
|
||||||
|
- May 2020: ThreeFold_Dubai launched our 2nd version of our token called TFT but this time on Stellar
|
||||||
|
- The original TFTv1 kept all same properties and benefits and is now called TFTA also on Stellar (is technology choice), anyone can move from TFTv1 to TFTv2
|
||||||
|
- TF Foundation Dubai has provisioned the TFTv1 & TFTv2 on Stellar blockchain, but has no influence or access to any of the wallets or for that matter the 3Nodes (the boxes providing IT capacity)
|
||||||
|
- See below for more info, this was the result of 12 months of work with our community and of-course consensus to do this.
|
||||||
|
|
||||||
|
## Organic Growth
|
||||||
|
|
||||||
|
We didn't artificially pump the value of the tokens.
|
||||||
|
|
||||||
|
We did not issue (print) tokens and go out onto an exchange to offer these tokens to the market. This is referred to as a public ICO. Some ICOs were not very clean in how they created hype and convinced people to invest. Because of our decision not to do a public ICO, we have not been able to raise much money, but we feel that this was more aligned with our values.
|
||||||
|
|
||||||
|
We have sold some TFT over the counter but please note every buyer could at any point in time use these TFTs to buy IT capacity, this makes these TFT purposeful, even from the very start.
|
||||||
|
|
||||||
|
## Farming Model Improvements
|
||||||
|
|
||||||
|
In Q2 2020 we were launching TF Grid 2.0 with updated minting rules. As part of these farming rules the max number of tokens became 4 billion, which changes the optics of the original size of the genesis token pool.
|
||||||
|
|
||||||
|
In Q3 2021 we launched TF Grid 3.0 which has again brought improvement to the farming model. Its up to the farmers to choose if they want to change to the new farming model or not.
|
||||||
|
|
||||||
|
### TFT Versions
|
||||||
|
|
||||||
|
| | version 1 Rivine | version 1 Stellar | version 2 Stellar |
|
||||||
|
| ------------------------------- | --------------------------- | ----------------- | --------------------------- |
|
||||||
|
| blockchain tech | Rivine, proof of blockstake | Public, Stellar | Public, Stellar |
|
||||||
|
| on public blockchain | march 2018 | 2020 May | 2020 May |
|
||||||
|
| farmed since | +-2017 | 2020 May | tbd |
|
||||||
|
| freely transferable (\*) | YES | YES | YES |
|
||||||
|
| complete blockchain feature set | YES | YES | YES |
|
||||||
|
| decentralized exchange | YES (atomic swap) | YES (Stellar) | YES (Stellar) |
|
||||||
|
| public exchange | BTC Alpha till Dec 2019 | Stellar | Stellar, BTC Alpha & Liquid (until August 2022) |
|
||||||
|
| freely tradable on exchange | YES | YES | YES |
|
||||||
|
| Name on Blockchain | TFT | TFTA | TFT |
|
||||||
|
| Purpose | v1 token | Staking Pool | Trading Pool |
|
||||||
|
|
||||||
|
## Migration
|
||||||
|
|
||||||
|
### Migration from TFTv1 Rivine to TFTv1 Stellar (2020)
|
||||||
|
|
||||||
|
- TF Tech decided to no longer support development of Rivine, at this time there are better technologies available as blockchain
|
||||||
|
- The Foundation investigated many blockchain platforms & recommended to use Stellar
|
||||||
|
- Jimber (company which maintains the wallet, which is open source code), has made the changes in the wallet to be able to support this new blockchain
|
||||||
|
- The conversation had to be a mandatory one, because otherwise there would be the potential of double-spending problems over both simultaneously-active blockchains
|
||||||
|
- What happened here can be compared to a website deciding to change the database backend (change from e.g. MS Sql to Oracle). The users of the website should not have to be aware of this migration
|
||||||
|
- Every user had to do the transaction themselves, no developer or anyone else had control over this migration step. This was an automatic step
|
||||||
|
- Everyone can use the validation scripts available to check the correct conversion between two blockchain technologies. The validation scripts prove that every transaction in the conversion happened well
|
||||||
|
|
||||||
|
### Migration from TFTv1 Stellar (Staking Pool=TFTA) to TFTv2 Stellar (Trading or Production Pool=TFT)
|
||||||
|
|
||||||
|
- See [TFTA to TFT](../legal/terms_conditions/tfta_to_tft.md)
|
||||||
|
|
||||||
|
### Technical Information
|
||||||
|
|
||||||
|
[TFTA TrustLine](https://stellar.expert/explorer/public/asset/TFTA-GBUT4GP5GJ6B3XW5PXENHQA7TXJI5GOPW3NF4W3ZIW6OOO4ISY6WNLN2)
|
||||||
|
|
||||||
|
Accounts that got initial balances migrated them from the previous blockchain, [rivine](https://explorer2.threefoldtoken.com/).
|
||||||
|
|
||||||
|
To validate this, each migration transaction contain hash of the rivine lock transaction in their memo in hex format.
|
||||||
|
|
||||||
|
[Rivine block explorer](https://explorer2.threefoldtoken.com/) can be used for validation purposes.
|
||||||
|
|
||||||
|
> Important note: The ThreeFold Token (TFT) is not an investment instrument. TFTs represent IT capacity on the ThreeFold Grid, farmers create TFT, developers use TFT.
|
||||||
BIN
collections/about/token_overview/img/token_distribution.png
Normal file
BIN
collections/about/token_overview/img/token_distribution.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 307 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 103 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 24 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 23 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 24 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 24 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 23 KiB |
@ -0,0 +1,105 @@
|
|||||||
|
<h1> ThreeFold Special Wallets </h1>
|
||||||
|
|
||||||
|
<h2>Table of Contents</h2>
|
||||||
|
|
||||||
|
- [Introduction](#introduction)
|
||||||
|
- [Exchange and OTC Wallets](#exchange-and-otc-wallets)
|
||||||
|
- [ThreeFold Contribution Wallets](#threefold-contribution-wallets)
|
||||||
|
- [Wisdom Council Wallets](#wisdom-council-wallets)
|
||||||
|
- [Important Note](#important-note)
|
||||||
|
- [Remarks](#remarks)
|
||||||
|
- [Proof-of-Utilization Wallets](#proof-of-utilization-wallets)
|
||||||
|
|
||||||
|
***
|
||||||
|
|
||||||
|
## Introduction
|
||||||
|
|
||||||
|
We present special wallets that hold a given amount of TFT.
|
||||||
|
|
||||||
|
## Exchange and OTC Wallets
|
||||||
|
|
||||||
|
| **Description** | **TFT Balance** | **Address** |
|
||||||
|
| ------------------ | ----------- | -------------------------------------------------------------------------------- |
|
||||||
|
| Liquid Exchange #1 | {{#include ./wallet_data/GA7OPN4A3JNHLPHPEWM4PJDOYYDYNZOM7ES6YL3O7NC3PRY3V3UX6ANM.md}} | [GA7OPN4A3JNHLPHPEWM4PJDOYYDYNZOM7ES6YL3O7NC3PRY3V3UX6ANM](https://stellar.expert/explorer/public/account/GA7OPN4A3JNHLPHPEWM4PJDOYYDYNZOM7ES6YL3O7NC3PRY3V3UX6ANM) |
|
||||||
|
| Liquid Exchange #2 | {{#include ./wallet_data/GDSKFYNMZWTB3V5AN26CEAQ27643Q3KB4X6MY4UTO2LIIDFND4SPQZYU.md}} | [GDSKFYNMZWTB3V5AN26CEAQ27643Q3KB4X6MY4UTO2LIIDFND4SPQZYU](https://stellar.expert/explorer/public/account/GDSKFYNMZWTB3V5AN26CEAQ27643Q3KB4X6MY4UTO2LIIDFND4SPQZYU) |
|
||||||
|
| gettft.com | {{#include ./wallet_data/GBQHN7RL4LSRPR2TT74ID2UJPZ2AXCHQY2WKGCTDLJM3NXVJ7GQHUCOD.md}} | [GBQHN7RL4LSRPR2TT74ID2UJPZ2AXCHQY2WKGCTDLJM3NXVJ7GQHUCOD](https://stellar.expert/explorer/public/account/GBQHN7RL4LSRPR2TT74ID2UJPZ2AXCHQY2WKGCTDLJM3NXVJ7GQHUCOD) |
|
||||||
|
| BTC-Alpha Exchange | {{#include ./wallet_data/GBTPAXXP6534UPC4MLNGFGJWCD6DNSRVIPPOZWXAQAWI4FKTLOJY2A2S.md}} | [GBTPAXXP6534UPC4MLNGFGJWCD6DNSRVIPPOZWXAQAWI4FKTLOJY2A2S](https://stellar.expert/explorer/public/account/GBTPAXXP6534UPC4MLNGFGJWCD6DNSRVIPPOZWXAQAWI4FKTLOJY2A2S) |
|
||||||
|
|
||||||
|
## ThreeFold Contribution Wallets
|
||||||
|
|
||||||
|
| **Description** | **TFT Balance** | **Address** |
|
||||||
|
| ------------------------------- | ----------- | -------------------------------------------------------------------------------- |
|
||||||
|
| TF DAY2DAY operations | {{#include ./wallet_data/GB2C5HCZYWNGVM6JGXDWQBJTMUY4S2HPPTCAH63HFAQVL2ALXDW7SSJ7.md}} | [GB2C5HCZYWNGVM6JGXDWQBJTMUY4S2HPPTCAH63HFAQVL2ALXDW7SSJ7](https://stellar.expert/explorer/public/account/GB2C5HCZYWNGVM6JGXDWQBJTMUY4S2HPPTCAH63HFAQVL2ALXDW7SSJ7) |
|
||||||
|
| TF Promotion Wallet | {{#include ./wallet_data/GDLVIB44LVONM5K67LUPSFZMSX7G2RLYVBM5MMHUJ4NAQJU7CH4HBJBO.md}} | [GDLVIB44LVONM5K67LUPSFZMSX7G2RLYVBM5MMHUJ4NAQJU7CH4HBJBO](https://stellar.expert/explorer/public/account/GDLVIB44LVONM5K67LUPSFZMSX7G2RLYVBM5MMHUJ4NAQJU7CH4HBJBO) |
|
||||||
|
| TF Grants Wallet | {{#include ./wallet_data/GDKXTUYNW4BJKDM2L7B5XUYFUISV52KUU4G7VPNLF4ZSIKBURM622YPZ.md}} | [GDKXTUYNW4BJKDM2L7B5XUYFUISV52KUU4G7VPNLF4ZSIKBURM622YPZ](https://stellar.expert/explorer/public/account/GDKXTUYNW4BJKDM2L7B5XUYFUISV52KUU4G7VPNLF4ZSIKBURM622YPZ) |
|
||||||
|
| ThreeFold Carbon Credit Funding | {{#include ./wallet_data/GDIJY6K2BBRIRX423ZFUYKKFDN66XP2KMSBZFQSE2PSNDZ6EDVQTRLSU.md}} | [GDIJY6K2BBRIRX423ZFUYKKFDN66XP2KMSBZFQSE2PSNDZ6EDVQTRLSU](https://stellar.expert/explorer/public/account/GDIJY6K2BBRIRX423ZFUYKKFDN66XP2KMSBZFQSE2PSNDZ6EDVQTRLSU) |
|
||||||
|
| TF Team Wallet | {{#include ./wallet_data/GCWHWDRXYPXQAOYMQKB66SZPLM6UANKGMSL4SP7LSOIA6OTTOYQ6HBIH.md}} | [GCWHWDRXYPXQAOYMQKB66SZPLM6UANKGMSL4SP7LSOIA6OTTOYQ6HBIH](https://stellar.expert/explorer/public/account/GCWHWDRXYPXQAOYMQKB66SZPLM6UANKGMSL4SP7LSOIA6OTTOYQ6HBIH) |
|
||||||
|
|
||||||
|
## Wisdom Council Wallets
|
||||||
|
|
||||||
|
| **Description** | **TFT Balance** | **Address** |
|
||||||
|
| --------------------------------------- | ----------- | -------------------------------------------------------------------------------- |
|
||||||
|
| Liquidity/Ecosystem Contribution Wisdom | {{#include ./wallet_data/GBV734I2SV4YDDPVJMYXU3IZ2AIU5GEAJRAD4E4BQG7CA2N63NXSPMD6.md}} | [GBV734I2SV4YDDPVJMYXU3IZ2AIU5GEAJRAD4E4BQG7CA2N63NXSPMD6](https://stellar.expert/explorer/public/account/GBV734I2SV4YDDPVJMYXU3IZ2AIU5GEAJRAD4E4BQG7CA2N63NXSPMD6) |
|
||||||
|
| TF Promotion Wisdom | {{#include ./wallet_data/GAI4C2BGOA3YHVQZZW7OW4FHOGGYWTUBEVNHB6MW4ZAFG7ZAA7D5IPC3.md}} | [GAI4C2BGOA3YHVQZZW7OW4FHOGGYWTUBEVNHB6MW4ZAFG7ZAA7D5IPC3](https://stellar.expert/explorer/public/account/GAI4C2BGOA3YHVQZZW7OW4FHOGGYWTUBEVNHB6MW4ZAFG7ZAA7D5IPC3) |
|
||||||
|
| TF Grants Wisdom | {{#include ./wallet_data/GCEJ7DMULFTT25UH4FAAGOZ6KER4WXAYQGJUSIITQD527DGTKSXKBQGR.md}} | [GCEJ7DMULFTT25UH4FAAGOZ6KER4WXAYQGJUSIITQD527DGTKSXKBQGR](https://stellar.expert/explorer/public/account/GCEJ7DMULFTT25UH4FAAGOZ6KER4WXAYQGJUSIITQD527DGTKSXKBQGR) |
|
||||||
|
| TF Team Wisdom | {{#include ./wallet_data/GAQXBLFG4BZGIVY6DBJVWE5EAP3UNHMIA2PYCUVLY2JUSPVWPUF36BW4.md}} | [GAQXBLFG4BZGIVY6DBJVWE5EAP3UNHMIA2PYCUVLY2JUSPVWPUF36BW4](https://stellar.expert/explorer/public/account/GAQXBLFG4BZGIVY6DBJVWE5EAP3UNHMIA2PYCUVLY2JUSPVWPUF36BW4) |
|
||||||
|
| Wisdom Council Locked | {{#include ./wallet_data/GAUGOSYLCX7JZTQYF2K7RIMHFWKSA3WSI2OQ4IRKXMDMVE6ABJIJMFQR.md}} | [GAUGOSYLCX7JZTQYF2K7RIMHFWKSA3WSI2OQ4IRKXMDMVE6ABJIJMFQR](https://stellar.expert/explorer/public/account/GAUGOSYLCX7JZTQYF2K7RIMHFWKSA3WSI2OQ4IRKXMDMVE6ABJIJMFQR) |
|
||||||
|
|
||||||
|
## Important Note
|
||||||
|
|
||||||
|
ThreeFold DMCC (Dubai) is in the process of acquiring a substantial number of tokens. While these tokens possess liquidity from a technical standpoint, they are not currently accessible or traded on the open market. This reserve of tokens has been allocated for our upcoming commercial rollout, and their governance will be managed through consensus based system with input from the community.
|
||||||
|
|
||||||
|
## Remarks
|
||||||
|
|
||||||
|
- All wisdom council wallets are protected by multisignature of the members of the wisdom council
|
||||||
|
- All foundation wallets are protected by members of the foundation (4 on 6 need to sign)
|
||||||
|
- Signatures can be checked by going to detail of account and then to the stellar link
|
||||||
|
- The foundation will never spend tokens if the markets cannot support it and all proceeds are 100% used for the benefit of the ThreeFold project.
|
||||||
|
|
||||||
|
## Proof-of-Utilization Wallets
|
||||||
|
|
||||||
|
There are some wallets associated with [proof-of-utilization](../../../farming/proof_of_utilization.md). These wallets are on TFChain.
|
||||||
|
|
||||||
|
The addresses are the following:
|
||||||
|
|
||||||
|
- Mainnet ThreeFold Foundation: 5DCaGQfz2PH35EMJTHFMjc6Tk5SkqhjekVvrycY5M5xiYzis
|
||||||
|
- Mainnet Default Solution Provider: 5Dd6adUJH8wvqb9SPC96JdZ85nK1671MeMSxkPZ6Q7rE4byc
|
||||||
|
- Testnet ThreeFold Foundation: 5H6XYX17yJyjazoLVZqxxEPwMdGn99wginjmFBKtjvk8iJ3e
|
||||||
|
- Testnet Default Solution Provider: 5Esq6iLLBGGJFsCEXpoFhxHhqcaGqTvDasdwy8jPFDH1jYaM
|
||||||
|
- Staking Pool: 5CNposRewardAccount11111111111111111111111111FSU
|
||||||
|
|
||||||
|
To check the balance of any of those wallets, follow those steps:
|
||||||
|
|
||||||
|
- Go to the Polkadot API ([Mainnet](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Ftfchain.grid.tf#/chainstate), [Testnet](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Ftfchain.test.grid.tf#/chainstate))
|
||||||
|
- Under `selected state query`, select `system`
|
||||||
|
- On the right drop down menu, select `account(AccountId32): FrameSystemAccountInfo`
|
||||||
|
- Under `Option<AccountId32>`, write the wallet address of one of the three accounts displayed above
|
||||||
|
- Click on the `plus` button on the far right of the `selected state query` line.
|
||||||
|
|
||||||
|
As a general example, here's what it looks like:
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
Here are the outputs for three wallets shown above:
|
||||||
|
|
||||||
|
- Mainnet ThreeFold Foundation
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
- Mainnet Default Solution Provider
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
- Testnet ThreeFold Foundation
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
- Testnet Default Solution Provider
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
- Staking Pool
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
> Note: To get the proper TFT amount, you need to account fo the fact that TFT uses 7 decimal places. For this reason, to get the proper quantity in TFT, move the decimal place by dividing by 1e7 (i.e. 1x10⁷).
|
||||||
@ -0,0 +1 @@
|
|||||||
|
3340735.94
|
||||||
@ -0,0 +1 @@
|
|||||||
|
258.80
|
||||||
@ -0,0 +1 @@
|
|||||||
|
5000000.00
|
||||||
@ -0,0 +1 @@
|
|||||||
|
10468506.00
|
||||||
@ -0,0 +1 @@
|
|||||||
|
12447988.00
|
||||||
@ -0,0 +1 @@
|
|||||||
|
2908686.63
|
||||||
@ -0,0 +1 @@
|
|||||||
|
1832242.73
|
||||||
@ -0,0 +1 @@
|
|||||||
|
16999920.00
|
||||||
@ -0,0 +1 @@
|
|||||||
|
10000000.00
|
||||||
@ -0,0 +1 @@
|
|||||||
|
328241.81
|
||||||
@ -0,0 +1 @@
|
|||||||
|
10110962.98
|
||||||
@ -0,0 +1 @@
|
|||||||
|
12996500.00
|
||||||
@ -0,0 +1 @@
|
|||||||
|
14181682.63
|
||||||
@ -0,0 +1 @@
|
|||||||
|
0.00
|
||||||
90
collections/about/token_overview/token_overview.md
Normal file
90
collections/about/token_overview/token_overview.md
Normal file
@ -0,0 +1,90 @@
|
|||||||
|
<h1> ThreeFold Token Overview </h1>
|
||||||
|
|
||||||
|
<h2>Table of Contents </h2>
|
||||||
|
|
||||||
|
- [Introduction to TFT](#introduction-to-tft)
|
||||||
|
- [Proof-of-Capacity](#proof-of-capacity)
|
||||||
|
- [Proof-of-Utilization](#proof-of-utilization)
|
||||||
|
- [Proof-of-Utility Distribution Flow](#proof-of-utility-distribution-flow)
|
||||||
|
- [TFT Distribution](#tft-distribution)
|
||||||
|
- [TFT Marketcap and Market Price](#tft-marketcap-and-market-price)
|
||||||
|
- [Complemetary Information](#complemetary-information)
|
||||||
|
- [Disclaimer](#disclaimer)
|
||||||
|
|
||||||
|
***
|
||||||
|
|
||||||
|
## Introduction to TFT
|
||||||
|
|
||||||
|
ThreeFold tokens, or TFTs, are exclusively generated when new capacity is added to the TF Grid. There are no centralized issuers. Tokens have not been created out of thin air.
|
||||||
|
|
||||||
|
While the ThreeFold Grid can expand, a maximum of 1 billion TFTs can ever be in circulation. This limit ensures stability of value and incentivization for all stakeholders.
|
||||||
|
|
||||||
|
TFT lives on the Stellar Blockchain. TFT holders benefit from a big ecosystem of proven wallets and mediums of exchange.
|
||||||
|
|
||||||
|
By employing Stellar technology, TFT transactions and smart contracts are powered by one of the most energy-efficient blockchains available. Furthermore, TFT is the medium of exchange on the greenest internet network in the world. The market for farming, cultivating and trading TFT is open to all.
|
||||||
|
|
||||||
|
Anyone with internet connection, power supply and necessary hardware can become a Farmer or trade ThreeFold tokens (TFT).
|
||||||
|
|
||||||
|
By farming, buying, holding, and utilizing ThreeFold Tokens, you are actively supporting the expansion of the ThreeFold Grid and its use cases — creating a more sustainable, fair, and equally accessible Internet.
|
||||||
|
|
||||||
|
## Proof-of-Capacity
|
||||||
|
|
||||||
|
ThreeFold uses proof-of-capacity to mint tokens. Since the genenis pool, all tokens that are being minted are the result of farming. Minting will stop during 2024, to keep the total amount of TFT at 1 billion, instead of the previously planned 4 billion. Read more about this [here](https://forum.threefold.io/t/end-feb-2024-update-from-the-team/4233).
|
||||||
|
|
||||||
|
> For more details, see [Proof of Capacity](../../farming/proof_of_capacity.md)
|
||||||
|
|
||||||
|
## Proof-of-Utilization
|
||||||
|
|
||||||
|
TFT is used on the TFGrid to purchase network, compute and storage resources through the proof-of-utilization protocol.
|
||||||
|
|
||||||
|
### Proof-of-Utility Distribution Flow
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
> For more details, see [Proof-of-Utilization](../../farming/proof_of_utilization.md)
|
||||||
|
|
||||||
|
## TFT Distribution
|
||||||
|
|
||||||
|
The supply distribution of TFT is as follows:
|
||||||
|
|
||||||
|
| Supply Distribution | Qty (Millions) |
|
||||||
|
| ------------------- | -------------- |
|
||||||
|
| Total supply | 942 |
|
||||||
|
| TF Foundation Supply | 162 |
|
||||||
|
| Circulating supply | 780 |
|
||||||
|
| Maximum supply | 1000 |
|
||||||
|
|
||||||
|
The total supply of TFT is distributed as follows:
|
||||||
|
|
||||||
|
| Total Supply Distribution | Qty (Millions) |
|
||||||
|
| ------------------------------------------- | -------------- |
|
||||||
|
| TF Foundation: Ecosystem Grants | 22 |
|
||||||
|
| TF Foundation: Promotion & Marketing Effort | 100 |
|
||||||
|
| TF Foundation: Ecosystem Contribution & Liquidity Exchanges | 40 |
|
||||||
|
| Genesis Pool & Farming Rewards | 780 |
|
||||||
|
|
||||||
|
## TFT Marketcap and Market Price
|
||||||
|
|
||||||
|
The TFT market price and marketcap are as follows:
|
||||||
|
|
||||||
|
| **Description** | **Value** |
|
||||||
|
| ------------------------- | ------------- |
|
||||||
|
| TFT Market Price | {{#include ../../../values/tft_value.md}} USD |
|
||||||
|
| TFT Market Cap | {{#include ../../../values/tft_marketcap.md}} USD |
|
||||||
|
|
||||||
|
The market cap is equal to the product of the TFT market price and the circulating supply.
|
||||||
|
|
||||||
|
> Market Cap = (TFT Market Price) X (TFT Circulating Supply)
|
||||||
|
|
||||||
|
The values here are subject to change. Check the current market conditions.
|
||||||
|
|
||||||
|
## Complemetary Information
|
||||||
|
|
||||||
|
- [ThreeFold History](../../about/threefold_history.md)
|
||||||
|
- [Token History](../../about/token_history.md)
|
||||||
|
- [Special Wallets](./special_wallets/stats_special_wallets.md)
|
||||||
|
|
||||||
|
## Disclaimer
|
||||||
|
|
||||||
|
> Important Note: The ThreeFold Token (TFT) is not an investment instrument.
|
||||||
|
TFTs represent IT capacity on the ThreeFold Grid, farmers create TFT, developers use TFT.
|
||||||
0
collections/cloud/.collection
Normal file
0
collections/cloud/.collection
Normal file
16
collections/cloud/cloud_toc.md
Normal file
16
collections/cloud/cloud_toc.md
Normal file
@ -0,0 +1,16 @@
|
|||||||
|
<h1> Cloud </h1>
|
||||||
|
|
||||||
|
This section covers the essential information concerning Cloud utilization.
|
||||||
|
|
||||||
|
To deploy on the ThreeFold Grid, refer to the [System Administrators](../../documentation/system_administrators/system_administrators.md) section.
|
||||||
|
|
||||||
|
<h2>Table of Contents</h2>
|
||||||
|
|
||||||
|
- [Cloud Units](./cloudunits.md)
|
||||||
|
- [Pricing](./pricing/pricing_toc.md)
|
||||||
|
- [Pricing Overview](./pricing/pricing.md)
|
||||||
|
- [Staking Discounts](./pricing/staking_discount_levels.md)
|
||||||
|
- [Cloud Pricing Compare](./pricing/cloud_pricing_compare.md)
|
||||||
|
- [Grid Billing](./grid_billing/grid_billing.md)
|
||||||
|
- [Resource Units](./resource_units_calc_cloudunits.md)
|
||||||
|
- [Resource Units Advanced](./resourceunits_advanced.md)
|
||||||
69
collections/cloud/cloudunits.md
Normal file
69
collections/cloud/cloudunits.md
Normal file
@ -0,0 +1,69 @@
|
|||||||
|
<h1>Cloud Units</h1>
|
||||||
|
|
||||||
|
<h2> Table of Contents </h2>
|
||||||
|
|
||||||
|
- [What are Cloud Units?](#what-are-cloud-units)
|
||||||
|
- [How is the price of Cloud Units (v4) calculated?](#how-is-the-price-of-cloud-units-v4-calculated)
|
||||||
|
- [Compute Capacity](#compute-capacity)
|
||||||
|
- [Storage Capacity](#storage-capacity)
|
||||||
|
- [Network](#network)
|
||||||
|
|
||||||
|
***
|
||||||
|
|
||||||
|
## What are Cloud Units?
|
||||||
|
Cloud units are the basis for price calculation for anyone intending to use/deploy on the Threefold Grid.
|
||||||
|
|
||||||
|
Cloud units are a unified way to account for virtual hardware resources on the ThreeFold Grid. They represent compute, storage and network equivalents to energy (kW - kilowatt). The are three categories of cloud units:
|
||||||
|
|
||||||
|
- Compute Unit (CU): The amount of data processing power in terms of virtual CPU (vCPU) cores (logical [CPUs](https://en.wikipedia.org/wiki/Central_processing_unit)) and Random Access Momory ([RAM](https://en.wikipedia.org/wiki/Random-access_memory)).
|
||||||
|
- Storage Unit (SU): The amount of storage capacity in terms of Hard Disk Drives (HDDs) and Solid State Drives (SSDs) in Gigabytes (GB).
|
||||||
|
- Network Unit (NU): The amount of data that travels in and out of storage units or compute units expressed in GB.
|
||||||
|
|
||||||
|
> Note: [Resource units](./resource_units_calc_cloudunits.md) are used to calculate SU & CU. Resource Units are used to measure compute and storage capacity produced by hardware.
|
||||||
|
|
||||||
|
When a solution is deployed on the ThreeFold Grid, the system automatically gathers the required amount of CU, SU, or NU. It is important to note that users are not billed upon reservation but only when utilizing the actualy CU, SU and NU. TF Certified Farmers can define the price of CU, SU, and NU they make available on the ThreeFold Grid.
|
||||||
|
|
||||||
|
## How is the price of Cloud Units (v4) calculated?
|
||||||
|
|
||||||
|
The following tables display how cloud units (v4) are calculated on the ThreeFold Grid. The 4th version of cloud units are used since Grid 2.2+ in mid 2020.
|
||||||
|
|
||||||
|
### Compute Capacity
|
||||||
|
|
||||||
|
| CU (Compute Unit) | | | | |
|
||||||
|
| ------------------------------------- | --- | --- | ---- | --------------- |
|
||||||
|
| GB Memory | 4 | 8 | 2 | |
|
||||||
|
| nr vCPU | 2 | 1 | 4 | |
|
||||||
|
| Passmark Minimum (expected is double) | 500 | 250 | 1000 | CPU performance |
|
||||||
|
|
||||||
|
The passmark (CPU benchmark or alternative) is not measured on the grid yet. It is used in simulators to check the mechanisms and ensure enough performance per CU is delivered.
|
||||||
|
|
||||||
|
Example of Compute unit:
|
||||||
|
- 4 GB memory & 2 virtual CPU (and 50GB of SSD disk space)
|
||||||
|
- Recommended price on TF Grid = 10 USD
|
||||||
|
- Alternative cloud price = between 40 USD and 180 USD
|
||||||
|
|
||||||
|
See how we compare with the market compute prices [here](./pricing/pricing.md).
|
||||||
|
|
||||||
|
### Storage Capacity
|
||||||
|
|
||||||
|
| SU (Storage Unit) | HDD | SSD |
|
||||||
|
| ------------------- | ---- | --- |
|
||||||
|
| GB Storage Capacity | 1200 | 200 |
|
||||||
|
|
||||||
|
HDD is only usable for Zero Database driven storage (e.g. ThreeFold Quantum Safe Storage). 1.2 TB of HDD is provided following the advised storage policy of 16+4 with 20% overhead. So the net usable storage would be 1TB. In other words, the SU corresponds in that case to 1TB of net usable storage and an extra 200GB for redundancy.
|
||||||
|
|
||||||
|
Example of Storage unit:
|
||||||
|
|
||||||
|
- 1TB of usable storage as provided by the Zero-DBs (the backend storage systems)
|
||||||
|
- Recommended price on TF Grid for 1 SU = 10 USD
|
||||||
|
- Alternative cloud price = between 20 USD and 200 USD
|
||||||
|
|
||||||
|
See how we compare with market storage prices [here](./pricing/pricing.md).
|
||||||
|
|
||||||
|
### Network
|
||||||
|
|
||||||
|
| NU (Network Unit = per GB) = NRU per month | GB (NRU) |
|
||||||
|
| ------------------------------------------ | -------- |
|
||||||
|
| GB transferred OUT or IN | 1 |
|
||||||
|
|
||||||
|
> We use SU-month and CU-month to show SU monthly costs. This can be compared to kilowatts (kW) to see electricity usage per month. Learn more about how this is calculated with [Resource units](./resource_units_calc_cloudunits.md), a way to measure the compute and storage capacity produced by hardware.
|
||||||
52
collections/cloud/cloudunits_advanced.md
Normal file
52
collections/cloud/cloudunits_advanced.md
Normal file
@ -0,0 +1,52 @@
|
|||||||
|
# Cloud Units Advanced
|
||||||
|
|
||||||
|
## How is the price of Cloud Units (v4) calculated?
|
||||||
|
|
||||||
|
The following tables display how cloud units (v4) are calculated on the ThreeFold Grid. The 4th version of cloud units are used since Grid 2.2+ in mid 2020.
|
||||||
|
|
||||||
|
> Note: [Resource units](resource_units.md) are used to calculate SU & CU. Resource Units are used to measure compute and storage capacity produced by hardware.
|
||||||
|
|
||||||
|
### Compute Capacity
|
||||||
|
|
||||||
|
| CU (Compute Unit) | | | | |
|
||||||
|
| ------------------------------------- | --- | --- | ---- | --------------- |
|
||||||
|
| GB Memory | 4 | 8 | 2 | |
|
||||||
|
| nr vCPU | 2 | 1 | 4 | |
|
||||||
|
| Passmark Minimum (expected is double) | 500 | 250 | 1000 | CPU performance |
|
||||||
|
|
||||||
|
The passmark (CPU benchmark or alternative) is not measured on the grid yet. It is used in simulators to check the mechanisms and ensure enough performance per CU is delivered.
|
||||||
|
|
||||||
|
Example of Compute unit:
|
||||||
|
|
||||||
|
- 4 GB memory & 2 virtual CPU (and 50GB of SSD disk space)
|
||||||
|
- Recommended price on TF Grid = 10 USD
|
||||||
|
- Alternative cloud price = between 40 USD and 180 USD
|
||||||
|
|
||||||
|
See how we compare with the market compute prices [here](pricing).
|
||||||
|
|
||||||
|
### Storage Capacity
|
||||||
|
|
||||||
|
| SU (Storage Unit) | HDD | SSD |
|
||||||
|
| ------------------- | ---- | --- |
|
||||||
|
| GB Storage Capacity | 1200 | 200 |
|
||||||
|
|
||||||
|
HDD is only usable for Zero Database driven storage (e.g. ThreeFold Quantum Safe Storage). 1.2 TB of HDD is provided following the advised storage policy of 16+4 with 20% overhead. So the net usable storage would be 1TB. In other words, the SU corresponds in that case to 1TB of net usable storage and an extra 200GB for redundancy.
|
||||||
|
|
||||||
|
Example of Storage unit:
|
||||||
|
|
||||||
|
- 1TB of usable storage as provided by the Zero-DBs (the backend storage systems)
|
||||||
|
- Recommended price on TF Grid for 1 SU = 10 USD
|
||||||
|
- Alternative cloud price = between 20 USD and 200 USD
|
||||||
|
|
||||||
|
See how we compare with market storage prices [here](pricing).
|
||||||
|
|
||||||
|
### Network
|
||||||
|
|
||||||
|
| NU (Network Unit = per GB) = NRU per month | GB (NRU) |
|
||||||
|
| ------------------------------------------ | -------- |
|
||||||
|
| GB transferred OUT or IN | 1 |
|
||||||
|
|
||||||
|
> We use SU-month and CU-month to show SU monthly costs. This can be compared to kilowatts (kW) to see electricity usage per month. Learn more about how this is calculated with [Resource units](resource_units), a way to measure the compute and storage capacity produced by hardware.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
422
collections/cloud/grid_billing/grid_billing.md
Normal file
422
collections/cloud/grid_billing/grid_billing.md
Normal file
@ -0,0 +1,422 @@
|
|||||||
|
<h1>Grid Billing</h2>
|
||||||
|
|
||||||
|
<h2>Table of Contents</h2>
|
||||||
|
|
||||||
|
- [Introduction](#introduction)
|
||||||
|
- [Resources to Update](#resources-to-update)
|
||||||
|
- [Current TFT Price](#current-tft-price)
|
||||||
|
- [Current Cloud Units Values](#current-cloud-units-values)
|
||||||
|
- [Node Contract](#node-contract)
|
||||||
|
- [Calculating the CU](#calculating-the-cu)
|
||||||
|
- [Calculating the SU](#calculating-the-su)
|
||||||
|
- [Calculating the Billing Rate for the Contract](#calculating-the-billing-rate-for-the-contract)
|
||||||
|
- [Applying the Discounts](#applying-the-discounts)
|
||||||
|
- [Rent Contract](#rent-contract)
|
||||||
|
- [Getting the Resources](#getting-the-resources)
|
||||||
|
- [Calculating the CU](#calculating-the-cu-1)
|
||||||
|
- [Calculating the SU](#calculating-the-su-1)
|
||||||
|
- [Calculating the Billing Rate for the Contract](#calculating-the-billing-rate-for-the-contract-1)
|
||||||
|
- [Applying the Dedicated Node Discount](#applying-the-dedicated-node-discount)
|
||||||
|
- [Applying the Staking Discount](#applying-the-staking-discount)
|
||||||
|
- [Name Contract](#name-contract)
|
||||||
|
- [Applying the Staking Discount](#applying-the-staking-discount-1)
|
||||||
|
- [Public IP](#public-ip)
|
||||||
|
- [Applying the Staking Discount](#applying-the-staking-discount-2)
|
||||||
|
- [Network Usage](#network-usage)
|
||||||
|
- [Data Usage](#data-usage)
|
||||||
|
- [NU Value](#nu-value)
|
||||||
|
- [Applying the Staking Discount](#applying-the-staking-discount-3)
|
||||||
|
- [Billing History](#billing-history)
|
||||||
|
|
||||||
|
***
|
||||||
|
|
||||||
|
## Introduction
|
||||||
|
|
||||||
|
In this section, we explain how the billing works on the TFGrid by showing different examples such as node, rent and name contracts as well as public IP and network usage.
|
||||||
|
|
||||||
|
<!--
|
||||||
|
|
||||||
|
(We can add this when 3.13 is released)
|
||||||
|
|
||||||
|
This documentation can be used in parallel with the [TFGrid Pricing Calculator](https://dashboard.grid.tf/#/deploy/pricing-calculator/) available on the Dashboard.
|
||||||
|
|
||||||
|
-->
|
||||||
|
|
||||||
|
## Resources to Update
|
||||||
|
|
||||||
|
Some of the used resources should be updated whenever you try to do these calculations, these resources are the TFT price and the cloud units (SU and CU).
|
||||||
|
|
||||||
|
### Current TFT Price
|
||||||
|
|
||||||
|
TFT price can be retrieved directly through [Stellar](https://stellar.expert/explorer/public/asset/TFT-GBOVQKJYHXRR3DX6NOX2RRYFRCUMSADGDESTDNBDS6CDVLGVESRTAC47-1?asset[]=TFT-GBOVQKJYHXRR3DX6NOX2RRYFRCUMSADGDESTDNBDS6CDVLGVESRTAC47-1&filter=markets&market=USDC-GA5ZSEJYB37JRC5AVCIA5MOP4RHTM335X2KGX3IHOJAPP5RE34K4KZVN-1) or from the [Dashboard](https://dashboard.grid.tf/), through the price available in the header.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
### Current Cloud Units Values
|
||||||
|
|
||||||
|
The current cloud units values can be retrieved directly from TChain with the [Polkadot UI](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Ftfchain.grid.tf#/chainstate) and the current chain state.
|
||||||
|
|
||||||
|
- On the page `Chain State`, select `tfgridModule` as the `selected state query`
|
||||||
|
- Select `pricingPolicies(u32): Option<PalletTfgridPricingPolicy>`
|
||||||
|
- Enter the value of the default pricing policy, which is `1`, or enter the value of any other policy if you need to use a custom one
|
||||||
|
- Press `Enter`
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
> Note: Values on chain are expressed as "units USD per hour", where "1 unit USD" == 10.000.000 (or 1e7)
|
||||||
|
|
||||||
|
## Node Contract
|
||||||
|
|
||||||
|
For this example, we will assume that the resources for this deployment are the following:
|
||||||
|
|
||||||
|
```
|
||||||
|
CRU: 2
|
||||||
|
MRU: 2
|
||||||
|
SRU: 15
|
||||||
|
HRU: 0
|
||||||
|
```
|
||||||
|
|
||||||
|
### Calculating the CU
|
||||||
|
|
||||||
|
Let's calculate the CU of this deployment.
|
||||||
|
|
||||||
|
For our example, the CU value is `10 mUSD/h`. Make sure that this value is updated according to the current values.
|
||||||
|
|
||||||
|
```
|
||||||
|
CU = min( max(MRU/4, CRU/2), max(MRU/8, CRU), max(MRU/2, CRU/4) )
|
||||||
|
= min( max(2/4, 2/2), max(2/8, 2), max(2/2, 2/4) )
|
||||||
|
= min( max(0.5, 1), max(0.25, 2), max(1, 0.5) )
|
||||||
|
= min( 1, 2, 1 )
|
||||||
|
= 1
|
||||||
|
CU cost/hour = CU * CU pricing
|
||||||
|
= 1 * 10 mUSD/h
|
||||||
|
= 10 mUSD/h
|
||||||
|
```
|
||||||
|
|
||||||
|
|
||||||
|
### Calculating the SU
|
||||||
|
|
||||||
|
Let's calculate the SU of this deployment.
|
||||||
|
|
||||||
|
The current SU value is `5 mUSD/h`. Make sure that this value is updated according to the current values.
|
||||||
|
|
||||||
|
```
|
||||||
|
SU = HRU/1200 + SRU/200
|
||||||
|
= 0/1200 + 15/200
|
||||||
|
= 0 + 0.075
|
||||||
|
= 0.075
|
||||||
|
SU cost/hour = SU * SU pricing
|
||||||
|
= 0.075 * 5 mUSD/h
|
||||||
|
= 0.375 mUSD/h
|
||||||
|
```
|
||||||
|
|
||||||
|
|
||||||
|
### Calculating the Billing Rate for the Contract
|
||||||
|
|
||||||
|
Let's calculate the billing rate by combining the CU and SU from above.
|
||||||
|
|
||||||
|
For this example, the current TFT value is `0.011 USD`. Make sure that this value is updated according to the current TFT value.
|
||||||
|
|
||||||
|
```
|
||||||
|
Contract cost/hour = CU cost/hour + SU cost/hour
|
||||||
|
= 10 mUSD/h + 0.375 mUSD/h
|
||||||
|
= 10.375 mUSD/h
|
||||||
|
= 0.010375 USD/h
|
||||||
|
= 0.010375 * 24 * 30
|
||||||
|
= 7.47 USD/month
|
||||||
|
= 679.090909 TFT/month
|
||||||
|
= 0.943182 TFT/hour
|
||||||
|
```
|
||||||
|
|
||||||
|
### Applying the Discounts
|
||||||
|
|
||||||
|
Before assuming that the price above is the final price, check first if your twin is eligible for any of the available staking discount levels. To understand more about discount levels, please read [this section](../pricing/staking_discount_levels.md).
|
||||||
|
|
||||||
|
For this example, we assume that this twin has 18 months worth of TFTs staked, so the user will be eligible for a Gold discount level (60% discount).
|
||||||
|
|
||||||
|
The 60% discount is thus equivalent to paying only 40% of the total price, as shown below:
|
||||||
|
|
||||||
|
```
|
||||||
|
Cost with 60% discount = 0.943182 * 0.4
|
||||||
|
= 0.377273 TFT/hour
|
||||||
|
```
|
||||||
|
|
||||||
|
|
||||||
|
## Rent Contract
|
||||||
|
|
||||||
|
|
||||||
|
### Getting the Resources
|
||||||
|
|
||||||
|
You can get the resources of a node using different methods. You can use Grid Proxy, GraphQL and the Polkadot UI.
|
||||||
|
|
||||||
|
- Using Grid Proxy
|
||||||
|
- Grid Proxy API
|
||||||
|
- Go to the section [nodes endpoint](https://gridproxy.grid.tf/swagger/index.html#/GridProxy/get_nodes__node_id_)
|
||||||
|
- Click on `Try it out`
|
||||||
|
- Write the node ID
|
||||||
|
- Click on `Execute`
|
||||||
|
- Grid Proxy URL
|
||||||
|
- You can use the following URL and replace <node_id> by the node ID:
|
||||||
|
```
|
||||||
|
https://gridproxy.grid.tf/nodes/<node_id>
|
||||||
|
```
|
||||||
|
|
||||||
|
- Using GraphQL
|
||||||
|
|
||||||
|
Navigate to [ThreeFold's GraphQL](https://graphql.grid.tf/graphql), then use the following query and replace the node id with the desired node id.
|
||||||
|
|
||||||
|
```
|
||||||
|
query MyQuery {
|
||||||
|
nodes(where: {nodeID_eq: 83}) {
|
||||||
|
id
|
||||||
|
farmingPolicyId
|
||||||
|
resourcesTotal {
|
||||||
|
cru
|
||||||
|
mru
|
||||||
|
sru
|
||||||
|
hru
|
||||||
|
}
|
||||||
|
}
|
||||||
|
}
|
||||||
|
|
||||||
|
```
|
||||||
|
|
||||||
|
- TFChain and Polkadot UI
|
||||||
|
- On the page Chain State of the [polakdot UI](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Ftfchain.grid.tf#/chainstate), select `tfgridModule` as the `selected state query`
|
||||||
|
- Select `nodes(u32): Option<TfchainSupportNode>`
|
||||||
|
- Enter the node ID
|
||||||
|
- Press `Enter`
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
For our example, these are the resources for node `83` that will be used for the calculations.
|
||||||
|
|
||||||
|
```
|
||||||
|
CRU = 4
|
||||||
|
SRU = 119.24
|
||||||
|
HRU = 1863
|
||||||
|
MRU = 15.55
|
||||||
|
```
|
||||||
|
|
||||||
|
### Calculating the CU
|
||||||
|
|
||||||
|
Let's calculate the CU of this deployment.
|
||||||
|
|
||||||
|
For our example, the CU value is `10 mUSD/h`. Make sure that this value is updated according to the current values.
|
||||||
|
|
||||||
|
```
|
||||||
|
CU = min( max(MRU/4, CRU/2), max(MRU/8, CRU), max(MRU/2, CRU/4) )
|
||||||
|
= min( max(15.55/4, 4/2), max(15.55/8, 4), max(15.55/2, 4/4) )
|
||||||
|
= min( max(3.8875, 2), max(1.94375, 4), max(7.775, 1) )
|
||||||
|
= min( 3.8875, 4, 7.775 )
|
||||||
|
= 3.8875
|
||||||
|
CU cost/hour = CU * CU pricing
|
||||||
|
= 3.8875 * 10 mUSD/h
|
||||||
|
= 38.875 mUSD/h
|
||||||
|
```
|
||||||
|
|
||||||
|
|
||||||
|
### Calculating the SU
|
||||||
|
|
||||||
|
For our example, the SU value is `5 mUSD/h`. Make sure that this value is updated according to the current values.
|
||||||
|
|
||||||
|
```
|
||||||
|
SU = HRU/1200 + SRU/200
|
||||||
|
= 1863/1200 + 119.24/200
|
||||||
|
= 1.5525 + 0.5962
|
||||||
|
= 2.1487
|
||||||
|
SU cost/hour = SU * SU pricing
|
||||||
|
= 2.1487 * 5 mUSD/h
|
||||||
|
= 10.7435 mUSD/h
|
||||||
|
```
|
||||||
|
|
||||||
|
### Calculating the Billing Rate for the Contract
|
||||||
|
|
||||||
|
For our example, the current TFT value is `0.011 USD`. Make sure that this value is updated according to the current values.
|
||||||
|
|
||||||
|
```
|
||||||
|
Contract cost/hour = CU cost/hour + SU cost/hour
|
||||||
|
= 38.875 mUSD/h + 10.7435 mUSD/h
|
||||||
|
= 49.6185 mUSD/h
|
||||||
|
= 0.0496185 USD/h
|
||||||
|
= (0.0496185 * 24 * 30)
|
||||||
|
= 35.72532 USD/month
|
||||||
|
= 3247.75636 TFT/month
|
||||||
|
```
|
||||||
|
|
||||||
|
### Applying the Dedicated Node Discount
|
||||||
|
|
||||||
|
There's a default `50%` discount for renting a node, this discount is not related to the staking discount. For more information on dedicated node discounts, please [read this section](../../../documentation/dashboard/deploy/node_finder.md#dedicated-nodes).
|
||||||
|
|
||||||
|
```
|
||||||
|
Cost with 50% discount = 35.72532 * 0.5
|
||||||
|
= 17.86266 TFT/month
|
||||||
|
```
|
||||||
|
|
||||||
|
### Applying the Staking Discount
|
||||||
|
|
||||||
|
Before assuming that the price above is the final price, check first if your twin is eligible for any of the available staking discount levels. To understand more about discount levels, please read [this section](../pricing/staking_discount_levels.md).
|
||||||
|
|
||||||
|
For this example, let's assume that this twin has 18 months worth of TFTs staked, so the user will be eligible for a Gold discount level (60% discount).
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
```
|
||||||
|
Cost with 60% discount = 17.86266 * 0.4
|
||||||
|
= 7.145064 TFT/month
|
||||||
|
```
|
||||||
|
|
||||||
|
## Name Contract
|
||||||
|
|
||||||
|
Let's calculate the cost of a name contract.
|
||||||
|
|
||||||
|
For our example, we use the following value from the Pricing Policy.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
This value can then be converted to USD.
|
||||||
|
|
||||||
|
```
|
||||||
|
uniqueName in USD = 2500 / 10000000
|
||||||
|
= 0.00025 USD/hour
|
||||||
|
|
||||||
|
```
|
||||||
|
Since the current TFT conversion rate is `1 USD = 100 TFT`, we have the following:
|
||||||
|
|
||||||
|
```
|
||||||
|
uniqueName in TFT = 0.00025 * 100
|
||||||
|
= 0.025 TFT/hour
|
||||||
|
```
|
||||||
|
|
||||||
|
### Applying the Staking Discount
|
||||||
|
|
||||||
|
Before assuming that the price above is the final price, check first if your twin is eligible for any of the available staking discount levels. To understand more about discount levels, please read [this section](../pricing/staking_discount_levels.md).
|
||||||
|
|
||||||
|
For this example, let's assume that this twin has 18 months worth of TFTs staked, so the user will be eligible for a Gold discount level (60% discount).
|
||||||
|
|
||||||
|
```
|
||||||
|
Cost with 60% discount = 0.025 * 0.4
|
||||||
|
= 0.01 TFT/hour
|
||||||
|
|
||||||
|
```
|
||||||
|
|
||||||
|
## Public IP
|
||||||
|
|
||||||
|
Let's calculate the cost of public IPs.
|
||||||
|
|
||||||
|
For our example, we use the following value from the Pricing Policy.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
This value can then be converted to USD.
|
||||||
|
|
||||||
|
```
|
||||||
|
Public IP in USD = 40000 / 10000000
|
||||||
|
= 0.004 USD/hour
|
||||||
|
|
||||||
|
```
|
||||||
|
|
||||||
|
Since the current TFT conversion rate is `1 USD = 100 TFT`, we have the following:
|
||||||
|
|
||||||
|
```
|
||||||
|
Public IP in TFT = 0.004 * 100
|
||||||
|
= 0.4 TFT/hour
|
||||||
|
```
|
||||||
|
|
||||||
|
### Applying the Staking Discount
|
||||||
|
|
||||||
|
Before assuming that the price above is the final price, check first if your twin is eligible for any of the available staking discount levels. To understand more about discount levels, please read [this section](../pricing/staking_discount_levels.md).
|
||||||
|
|
||||||
|
For this example, let's assume that this twin has 18 months worth of TFTs staked, so the user will be eligible for a Gold discount level (60% discount).
|
||||||
|
|
||||||
|
```
|
||||||
|
Cost with 60% discount = 0.4 * 0.4
|
||||||
|
= 0.16 TFT/hour
|
||||||
|
|
||||||
|
```
|
||||||
|
|
||||||
|
> Note: This value gets added to the billing rate of your deployment.
|
||||||
|
|
||||||
|
|
||||||
|
## Network Usage
|
||||||
|
|
||||||
|
Network Usage is calculated for deployments with public IPs. It's reported every hour and its cost can be calculated approximately as follows, where the data usage is the value of data sent and received:
|
||||||
|
|
||||||
|
```
|
||||||
|
network usage = data usage * NU value
|
||||||
|
```
|
||||||
|
|
||||||
|
### Data Usage
|
||||||
|
|
||||||
|
To start, let's calculate the data usage. This can be tracked with a network tool like [nload](https://github.com/rolandriegel/nload), where the total amount of data sent and received can be displayed.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
### NU Value
|
||||||
|
|
||||||
|
Let's find the NU value of this deployment.
|
||||||
|
|
||||||
|
For our example, we use the following value from the Pricing Policy.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
This value can then be converted to USD.
|
||||||
|
|
||||||
|
```
|
||||||
|
NU price in USD = 15000 / 10000000
|
||||||
|
= 0.0015 USD/hour
|
||||||
|
|
||||||
|
```
|
||||||
|
Since in our example the current TFT conversion rate is `1 USD = 100 TFT`, we have the following:
|
||||||
|
|
||||||
|
```
|
||||||
|
NU price in TFT = 0.0015 * 100
|
||||||
|
= 0.15 TFT/hour
|
||||||
|
```
|
||||||
|
|
||||||
|
### Applying the Staking Discount
|
||||||
|
|
||||||
|
Before assuming that the price above is the final price, check first if your twin is eligible for any of the available staking discount levels. To understand more about discount levels, please read [this section](../pricing/staking_discount_levels.md).
|
||||||
|
|
||||||
|
For this example, let's assume that this twin has 18 months worth of TFTs staked, so the user will be eligible for a Gold discount level (60% discount).
|
||||||
|
|
||||||
|
```
|
||||||
|
Cost with 60% discount = 0.15 * 0.4
|
||||||
|
= 0.06 TFT/hour
|
||||||
|
|
||||||
|
```
|
||||||
|
|
||||||
|
As an example, let's assume that we used a total of 10GB in the last hour, so the next hour the billing rate should be updated to:
|
||||||
|
|
||||||
|
```
|
||||||
|
Total network usage = 10GB * 0.06 TFT/hour
|
||||||
|
= 0.6 TFT/hour
|
||||||
|
```
|
||||||
|
|
||||||
|
The billing rate in the next hour should be the following:
|
||||||
|
|
||||||
|
```
|
||||||
|
hourly billing rate = actual cost of the deployment + total network usage
|
||||||
|
```
|
||||||
|
|
||||||
|
|
||||||
|
> Note: The calculated value will always be an approximation since it's not possible to manually calculate the exact value of the data used.
|
||||||
|
|
||||||
|
|
||||||
|
## Billing History
|
||||||
|
|
||||||
|
Since the billing rate gets updated hourly, you can check the billing history from [GraphQL](https://graphql.grid.tf/graphql) using the following query. Make sure to enter the proper contract ID.
|
||||||
|
|
||||||
|
```
|
||||||
|
query MyQuery {
|
||||||
|
contractBillReports(where: {contractID_eq: ""}) {
|
||||||
|
contractID
|
||||||
|
amountBilled
|
||||||
|
discountReceived
|
||||||
|
timestamp
|
||||||
|
}
|
||||||
|
}
|
||||||
|
|
||||||
|
```
|
||||||
BIN
collections/cloud/grid_billing/img/grid_billing_1.png
Normal file
BIN
collections/cloud/grid_billing/img/grid_billing_1.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 25 KiB |
BIN
collections/cloud/grid_billing/img/grid_billing_2.png
Normal file
BIN
collections/cloud/grid_billing/img/grid_billing_2.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 105 KiB |
BIN
collections/cloud/grid_billing/img/grid_billing_3.png
Normal file
BIN
collections/cloud/grid_billing/img/grid_billing_3.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 98 KiB |
BIN
collections/cloud/grid_billing/img/grid_billing_4.png
Normal file
BIN
collections/cloud/grid_billing/img/grid_billing_4.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 91 KiB |
BIN
collections/cloud/grid_billing/img/grid_billing_5.png
Normal file
BIN
collections/cloud/grid_billing/img/grid_billing_5.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 78 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