@@ -0,0 +5,4 @@
+- Follow [DeTEE on Twitter](https://x.com/detee_network)
+- Follow [DeTEE on Instagram](https://www.instagram.com/detee_network/)
+- Follow [DeTEE on Linkedin](https://www.linkedin.com/company/105187289)
+- Follow [Gheorghe](https://www.linkedin.com/in/ghe0/) on Linkedin. Gheorghe loves attention so this will get you extra points.

@@ -0,0 +1,136 @@
+# Advanced Features
+
+This article is oriented towards power users that would like to know more about the mechanics of the DeTEE platform and would like to experiment by adding their own kernel, their own initrd or building OS templates for their own distribution or with their own apps.

@@ -0,0 +4,4 @@
+
+## Kernel and DTRFS
+
+DeTEE VMs currently run using the latest stable version of the kernel. This is required in order to guarantee the SNP features are enabled. As the progress moves forward, we will also offer the LTS kernel as part of our default feature set.

@@ -0,0 +17,4 @@
+
+The CLI works together with the initrd (which is actually an initramfs) to enable remote attestation. The integration is based on [virtee](https://github.com/virtee/). As you probably imagined, the normal initramfs images offered by normal distributions do not offer the capabilities required for remote attestation, so we decided to build the DeTEE Init RAM FileSystem (DTRFS).
+
+The code required to build DTRFS is currently not public and will get open sourced after the project grows enough to open source the entire intellectual property. You can, however check the contents of the initramfs by downloading the images listed in the CLI:

@@ -0,0 +45,4 @@
+- As a consequence, the VM also does not need kernel modules
+- Make sure `sshd` will start and will listen on `0.0.0.0:22` after boot
+
+After creating the image, upload it to any webserver you want and add provide the URL to the CLI. Don't forget to also update the sha256sum of the image, as it gets verified during the installation process.

@@ -0,0 +47,4 @@
+
+After creating the image, upload it to any webserver you want and add provide the URL to the CLI. Don't forget to also update the sha256sum of the image, as it gets verified during the installation process.
+
+### ArchLinux example

@@ -0,0 +8,4 @@
+
+Once docker is installed, use the following command to run the CLI:
+```
+docker run -it --name detee-cli --entrypoint /usr/bin/fish $IMAGE_NAME

@@ -0,0 +25,4 @@
+detee-cli account brain-url http://164.92.249.180:31337
+```
+
+Also, list get your public key:

@@ -0,0 +37,4 @@
+SNP admin secret key path: /home/ghe0/.detee/cli/secret_detee_wallet_key
+```
+
+And give it to us on Discord so that we can give you your airdrop (assuming you have [access](./access.md)).

@@ -0,0 +41,4 @@
+
+### Deploy a VM
+
+To see options f#or deploying a VM, just write `detee-cli vm deploy --` and hit TAB. Autocompletion will show available options:

@@ -0,0 +6,4 @@
+  - [x] allows you to create contracts for VMs and containers
+  - [ ] allows you to create contracts for GPUs
+  - [ ] allows users to vote for the upgrades of the platform
+  - [x] stores ratings for users

@@ -0,0 +34,4 @@
+
+- **Orchestrator**: advanced cloud service that offers high availability and clustering for software services running on the DeTEE platform
+  - [ ] management of secrets using DeTEE encryption
+  - [x] deployment of swarms of containers across multiple nodes

@@ -0,0 +42,4 @@
+
+Future components (currently not under development):
+- **(Arm) TrustZone Daemon**: Software that powers the SNP node, allowing customers to run VMs
+- **(NVIDIA) GPU Daemon**: Software that powers the SNP node, allowing customers to run VMs

@@ -0,0 +1,7 @@
+# DeTEE Cloud
+
+The mission of DeTEE is to create a decentralized cloud solution that functions as an open market for hardware resources. The DeTEE protocol is connecting the customers (mostly software companies) and the service providers (node operators), ensuring the business activity of all participants runs smoothly. In order to make the decentralized network feel like a cloud platform, DeTEE inspired the user experience from popular cloud platforms (Kubernetes, Openstack, AWS, GCP), and optimized and simplified the flow to the benefit of the end user.

@@ -0,0 +1,69 @@
+# Token system

@@ -0,0 +1,69 @@
+# Token system
+
+> Considering how young this project is, everything on this page will probably change in the future.

@@ -0,0 +2,4 @@
+
+> Considering how young this project is, everything on this page will probably change in the future.
+
+The token payment and reward mechanism of DeTEE is based on the core concepts of the open market and the requirements of creating a TEE-based decentralized cloud platform:

@@ -0,0 +11,4 @@
+- the guest can not access the host
+- the host can not access the guest
+
+One of the first conclusions after analyzing the requirements above is that designing a mechanism was that implementing payment for resource utilization is exceptionally hard. As a consequence, DeTEE currently supports only payment for resource reservation, and different models will be considered as the project grows. This means that the user will pay for the resources he reserves, not for the resources he uses. For example, if a user reserves a VM with 4 vCPUs and 5GB of memory, however the load on the VM is minimal, the user will still pay for vCPUs and 5 GBs of memory. To compensate for this, automation and orchestration tools will be offered to users.

@@ -0,0 +13,4 @@
+
+One of the first conclusions after analyzing the requirements above is that designing a mechanism was that implementing payment for resource utilization is exceptionally hard. As a consequence, DeTEE currently supports only payment for resource reservation, and different models will be considered as the project grows. This means that the user will pay for the resources he reserves, not for the resources he uses. For example, if a user reserves a VM with 4 vCPUs and 5GB of memory, however the load on the VM is minimal, the user will still pay for vCPUs and 5 GBs of memory. To compensate for this, automation and orchestration tools will be offered to users.
+
+Though nodes get paid for resource reservation, during the testnet nodes will also receive a base reward of 100 test tokens per month. This means that all nodes will receive by default 100 test tokens per month in the testnet, no matter if they sell or not.

@@ -0,0 +19,4 @@
+
+Before calculating the price per month for a VM or a container, we must define the formula to calculate the multiplier for each hardware resource that is part of the contract. To simplify the formula, we will define “units”, each class of hardware warning units based on their own multiplier.
+
+Based on our experience when using cloud services, we decided that the price of a resource will be calculated based on the number of minutes the resource is being used. As a consequence, using a resource for 10 seconds will qualify as using that resource for 1 minute, and using the resource for 70 seconds will qualify as using the resource for 2 minutes.

@@ -0,0 +21,4 @@
+
+Based on our experience when using cloud services, we decided that the price of a resource will be calculated based on the number of minutes the resource is being used. As a consequence, using a resource for 10 seconds will qualify as using that resource for 1 minute, and using the resource for 70 seconds will qualify as using the resource for 2 minutes.
+
+A server is also free to choose the price per unit per minute for his service. This price is defined in nanotokens. The current recommended value is 20k nanotokens per unit per minute. With the current calculation, a VM with 1 vCPU, 1 GB of memory, 20 GB of storage and one public IP will cost 24.4 tokens per month.

@@ -0,0 +33,4 @@
+- 10 GB of Storage - offers 1 unit 
+- 1 public IPv4 IP - offers 10 units
+
+VMs also have an overhead for the memory due to SNP requirements.

@@ -0,0 +4,4 @@
+- DevOps engineers
+- Cloud engineers
+- Software developers
+- Cybersecurity enthusiasts

@@ -0,0 +8,4 @@
+
+Having basic understanding of operating systems, containers, virtual machines and deployment of software is required in order to use the CLI. The product was heavily inspired from existing open source cloud apps (Docker, Kubernetes, Proxmox, OpenStack).
+
+As we are currently in a testnet phase, you will first have to get some tokens in order to be able to test the app. Details on how to get access can be found in the next chapter.

@@ -0,0 +8,4 @@
+- AMD EPYC 9004 (Genoa or Bergamo)
+- AMD EPYC 9005 (Turin)
+
+More information about the capabilities of each generation can be found on the [AMD website](https://www.amd.com/en/products/processors/server/epyc/infinity-guard.html). Our focus is strictly focused on the SEV-SNP capability.

@@ -0,0 +83,4 @@
+
+You should be set.
+
+## Easy way to collect rewards

@@ -0,0 +1,12 @@
+# Node Operators
+
+DeTEE currently supports Intel SGX and AMD SNP servers. In the future, we are planning to also support Arm TrustZone and NVIDIA GPUs. Our mission is to support all hardware that offers TEEs.