A: `n` (No) -Q: `Please specify a path to the offer info json file` +Q: `Please specify a path to the offer info json file`
A: `./offer-info.json` -Q: `Please specify a path to the slot info json file` +Q: `Please specify a path to the slot info json file`
A: `./slot-info.json` -Q: `Do you want to add another slot?` +Q: `Do you want to add another slot?`
A: `n` (No) Wait for the offer to be created and find a line in the output with the IDs of the offer and slot, for example: @@ -250,7 +253,7 @@ Wait for the offer to be created and find a line in the output with the IDs of t Slot 119654 for offer 18291 has been created successfully ``` -Provide Bob with these IDs. Ignore other instructions you see in the output. +Provide Alice with these IDs. Ignore other instructions you see in the output. ## Execution @@ -323,6 +326,8 @@ If the order ended up with an error, the results will contain execution logs tha ### Alice and Bob: 11. Get the order report +You can get the order report as soon as the CVM downloads the order components and starts the execution, without waiting for the order to complete: + ```shell ./spctl orders get-report
`/sp/inputs/input-0002`
etc. | Possible data locations | Read-only | -| `/sp/output` | Output directory for results | Write; read own files | -| `/sp/certs` | Contains the order certificate | Read-only | +|
**Location**
| **Purpose** | **Access**
|
+| :- | :- | :- |
+| `/sp/inputs/input-0001``/sp/inputs/input-0002`
... | Possible data locations | Read-only | +| `/sp/output` | Output directory for results | Read and write | +| `/sp/certs` | Contains the order certificate, private key, and workloadInfo | Read-only | -So, your solution must find the data in `/sp/inputs` and write the results to `/sp/output`. +When you provide multiple data inputs, they are placed in separate directories inside the CVM: the first in `/sp/inputs/input-0001`, the second in `/sp/inputs/input-0002`, and so on. Your solution must find the data in `/sp/inputs` and write the results to `/sp/output`. :::important @@ -32,7 +32,9 @@ Always use absolute paths, such as `/sp/...`. ::: -You can find several Dockerfile examples in the [Super-Protocol/solutions](https://github.com/Super-Protocol/solutions) GitHub repository. +Check the [example](/cli/guides/deploy-app/example) at the end of this guide. + +More Dockerfile examples can be found in the [Super-Protocol/solutions](https://github.com/Super-Protocol/solutions) GitHub repository. ### 1.2. Build a Docker image @@ -124,17 +126,11 @@ Place an order using the [`workflows create`](/cli/commands/workflows/create) co --data ./more-data.resource.json ``` -:::note - -When you provide multiple data inputs, they are placed in separate directories inside the CVM: the first in `/sp/inputs/input-0001`, the second in `/sp/inputs/input-0002`, and so on. - -::: - Find the order ID in the output. ## 4. Download the result -Wait a few minutes and [check the order status](/cli/commands/orders/get): +Wait a few minutes and check the order status: ```shell ./spctl orders get
+ +Carol builds a solution—a Docker image containing her training engine and script ([1](/cli/guides/multi-party-collab#carol-1-build-a-solution)). She uploads the solution using SPCTL ([2](/cli/guides/multi-party-collab#carol-2-upload-the-solution)) and grants Alice and Bob access for verification ([3](/cli/guides/multi-party-collab#carol-3-send-the-solution-to-alice-and-bob)). + +Alice and Bob download the solution ([4](/cli/guides/multi-party-collab#alice-and-bob-4-download-the-solution)) and verify that it is safe to process their data ([5](/cli/guides/multi-party-collab#alice-and-bob-5-verify-the-solution)). + +If Carol cannot share the code with Alice and Bob, and a third-party auditor is involved, the workflow will differ slightly. After uploading, Carol must also create a solution offer on Super Protocol Marketplace (similar to Bob's [Step 8](/cli/guides/multi-party-collab#bob-8-create-an-offer)). + +**Prepare the data**: + +```mermaid +sequenceDiagram + actor Alice + actor Bob + participant Storage + participant Super Protocol + + note over Alice,Super Protocol: Prepare the data + + Alice ->> Storage: 6. Upload the model + Bob ->> Storage: 7. Upload the dataset + Bob ->> Super Protocol: 8. Create an offer +``` +
+ +Alice uploads her model ([6](/cli/guides/multi-party-collab#alice-6-upload-the-model)) and Bob uploads his dataset ([7](/cli/guides/multi-party-collab#bob-7-upload-the-dataset)) to remote storage using SPCTL. Files are automatically encrypted during upload, and only the uploader holds the key. + +Bob creates an offer on the Marketplace ([8](/cli/guides/multi-party-collab#bob-8-create-an-offer)). The offer requires Bob's manual approval for use. He shares the offer's IDs with Alice. + +**Execute**: + +```mermaid +sequenceDiagram + actor Alice + actor Bob + participant Storage + participant Super Protocol / TEE + participant Blockchain + + note over Alice,Blockchain: Execute + + Alice ->>+ Super Protocol / TEE: 9. Place an order + Bob ->> Super Protocol / TEE: 10. Approve the usage of the dataset + Super Protocol / TEE ->> Storage: Download the solution, model, and dataset + Super Protocol / TEE ->> Blockchain: Publish the order report + Super Protocol / TEE ->> Super Protocol / TEE: Process the order + Super Protocol / TEE ->>- Storage: Upload the order results + Alice ->> Storage: 11. Download the order results + Alice ->> Blockchain: 12. Get the order report + Bob ->> Blockchain: 12. Get the order report +``` +
+ +Alice places an order on Super Protocol ([9](/cli/guides/multi-party-collab#alice-9-place-an-order)), adding the solution, her model, and Bob's offer. The order does not proceed automatically and remains `Blocked`. + +Bob manually approves the usage of his dataset for the image with a specific hash ([10](/cli/guides/multi-party-collab#bob-10-complete-the-data-suborder)). If this hash matches the actual solution hash, the CVM begins to process the order. If the hashes do not match, the order will be terminated with an error. + +When the order is complete, Alice downloads the result ([11](/cli/guides/multi-party-collab#alice-11-download-the-order-results)). All the data within the TEE (solution, AI model, dataset, order results, etc.) is automatically deleted. + +Both Alice and Bob can retrieve the order report ([12](/cli/guides/multi-party-collab#alice-and-bob-12-get-the-order-report)) that confirms the authenticity of the entire trusted setup. + +## Prerequisites + +**Alice**: + +- [SPCTL](/cli) + +**Bob**: + +- [SPCTL](/cli) +- [Provider Tools](/cli/guides/provider-tools) + +**Carol**: + +- [SPCTL](/cli) +- Docker + +## Prepare the solution + +### Carol: 1. Build a solution + +1.1. Write a Dockerfile that creates an image with the training engine. + +Keep in mind the special file structure inside the TEE: + +| **Location** | **Purpose** | **Access** | +| :- | :- | :- | +| `/sp/inputs/input-0001`
`/sp/inputs/input-0002`
etc. | Possible data locations
(AI model, dataset, training scripts, etc.) | Read-only | +| `/sp/output` | Output directory for results | Read and write | +| `/sp/certs` | Contains the order certificate, private key, and workloadInfo | Read-only | + +Your solution must find the data in `/sp/inputs` and write the results to `/sp/output`. + +:::important + +Always use absolute paths, such as `/sp/...`. + +::: + +You may either include the training scripts in the image or upload them separately using SPCTL. In this case, Alice will need to attach the uploaded scripts to the order as `--data` at [Step 9](/cli/guides/multi-party-collab#alice-9-place-an-order). + +You can find several Dockerfile examples in the [Super-Protocol/solutions](https://github.com/Super-Protocol/solutions) GitHub repository. + +1.2. Build an image: + +```shell +docker build --platform linux/amd64 -t
+A: `n` (No) + +Q: `Please specify a path to the offer info json file`
+A: `./offer-info.json` + +Q: `Please specify a path to the slot info json file`
+A: `./slot-info.json` + +Q: `Do you want to add another slot?`
+A: `n` (No) + +Wait for the offer to be created and find a line in the output with the IDs of the offer and slot, for example: + +```text +Slot 119654 for offer 18291 has been created successfully +``` + +Provide Alice with these IDs. Ignore other instructions you see in the output. + +## Execute + +### Alice: 9. Place an order + +9.1. Place an order with the solution, your model, and Bob's data offer. If the training scripts were uploaded separately, add them as data: + +```shell +./spctl workflows create \ + --solution ./solution.resource.json \ + --data ./model.resource.json \ + --data
+A: `y` (Yes) + +Q: `Do you need to generate a new action account?`
+A: `y` (Yes) + +Q: `Do you need to generate a new tokenReceiver account?`
+A: `y` (Yes) + +## Provider's SPCTL + +Providers need another copy of SPCTL configured to manage their offers. + +
.default})
++ +## 2. Create a Kubernetes cluster + +2.1. Go to **Kubernetes** and press **Create Cluster**: + +
.default})
++
+ +2.2. Add a GPU to the cluster, allocate resources, and press **Create Cluster**: + +
.default})
++ +## 3. Download the cluster configuration file + +
.default})
++ +## 4. Point `kubectl` to the configuration file + +Execute the following command: + +```shell +export KUBECONFIG=
.default})
++
+ +For each hostname, add a CNAME record pointing to it and a TXT record for domain verification at your DNS provider. + +## 10. Publish the cluster + +In the Super Swarm dashboard, go to **Kubernetes** and publish the cluster. + +
.default})
++ +## 11. Send test requests + +In the test requests below, replace: + +- `
`/sp/inputs/input-0002`
etc. | Possible data locations
(AI model, dataset, training scripts, etc.) | Read-only | +| `/sp/output` | Output directory for results | Read and write | +| `/sp/certs` | Contains the order certificate, private key, and `workloadInfo` | Read-only | + +Your scripts must find the data in `/sp/inputs` and write the results to `/sp/output`. + +### 2. Place an order + +2.1. Initiate a dialog to construct and place an order: + +```shell +./run-unsloth.sh +``` + +2.2. `Enter TEE offer id (number)`: Enter a compute offer ID. This determines the available compute resources and cost of your order. You can find the full list of available compute offers on the [Marketplace](https://marketplace.superprotocol.com/). + +2.3. `Choose run mode`: `1) file`. + +2.4. `Select the model option`: + +- `1) Medgemma 27b (offer 15900)`: Select this option if you need an untuned MedGemma 27B. +- `2) your model`: Select this option to use another model. Further, when prompted about `Model input`, enter one of the following: + - a path to the model's resource JSON file, if it was already uploaded with SPCTL + - model offer ID, if the model exists on the Marketplace + - a path to the local directory with the model to upload it using SPCTL. +- `3) no model`: No model will be used. + +2.5. `Enter path to a .py/.ipynb file OR a directory`: Enter the path to your training script (file or directory). For a directory, select the file to run (entrypoint) when prompted. Note that you cannot reuse resource files in this step; scripts should be uploaded every time. + +2.6. `Provide your dataset as a resource JSON path, numeric offer id, or folder path`: As with the model, enter one of the following: + +- a path to the dataset's resource JSON file, if it was already uploaded with SPCTL +- dataset offer ID, if the dataset exists on the Marketplace +- a path to the local directory with the dataset to upload it using SPCTL. + +2.7. `Upload SPCTL config file as a resource?`: Answer `N` unless you need to use SPCTL from within the TEE during the order execution. In this case, your script should run a `curl` command to download SPCTL and find the uploaded `config.json` in the `/sp/inputs/` subdirectories. + +2.8. Wait for the order to be created and find the order ID in the output, for example: + +```shell +Unsloth order id: 259126 +Done. +``` + +### 3. Check the order result + +3.1. The order will take some time to complete. Check the order status: + +```shell +./spctl orders get
→ All activity counts toward leaderboard ranking and final rewards. **Daily Reset:**
-Every day at 12:00 PM UTC, submission limits are reset, and the points’ value increases by 4%. \ No newline at end of file +Every day at 12:00 PM UTC, submission limits are reset, and the points' value increases by 4%. \ No newline at end of file diff --git a/docs/data-for-ai/Overview/support.md b/docs/data-for-ai/Overview/support.md index dcd74251..13dab134 100644 --- a/docs/data-for-ai/Overview/support.md +++ b/docs/data-for-ai/Overview/support.md @@ -5,7 +5,7 @@ slug: "/overview/support" sidebar_position: 6 --- -If you have questions, encounter issues, or need assistance during the campaign, we’re here to help. +If you have questions, encounter issues, or need assistance during the campaign, we're here to help. ## Support ticket @@ -15,4 +15,4 @@ For official support via email, please [submit a request](https://superprotocol. If you prefer real-time communication, you can also get help through our [Discord server](https://discord.com/invite/superprotocol). The channel is **#data-for-ai**. -We’re committed to supporting you throughout the campaign. \ No newline at end of file +We're committed to supporting you throughout the campaign. \ No newline at end of file diff --git a/docs/data-for-ai/Rules/referrals.md b/docs/data-for-ai/Rules/referrals.md index a2187631..07958729 100644 --- a/docs/data-for-ai/Rules/referrals.md +++ b/docs/data-for-ai/Rules/referrals.md @@ -9,9 +9,9 @@ The referral system allows you to earn additional points by inviting others to j ## How it works -- After registration, you’ll receive a unique referral link. +- After registration, you'll receive a unique referral link. - When someone signs up using your link—a *referee*—and starts submitting valid data links, you earn referral points. -- There’s no limit to how many people you can refer. +- There's no limit to how many people you can refer. - Each participant can only be referred once. - If someone signs up without your link or uses another link first, they cannot be reassigned to you. @@ -27,13 +27,13 @@ Day 3: ~37.9 points
...
Day 14 (Final Day): ~58.8 points per link -The longer the campaign runs, the more valuable each referee’s activity becomes. +The longer the campaign runs, the more valuable each referee's activity becomes. Note: While later submissions earn more per link, inviting people early gives them time to contribute more overall, resulting in higher total rewards for you. ## Referral penalty -If your referee submits an invalid data link, you’ll lose the referral reward for one previously earned link from that referee. This only affects the bonus points earned from that specific referee and does not impact your own points or rewards from other referees. +If your referee submits an invalid data link, you'll lose the referral reward for one previously earned link from that referee. This only affects the bonus points earned from that specific referee and does not impact your own points or rewards from other referees. Referral points cannot go negative, and the same rule applies individually to each referee and each invalid link. diff --git a/docs/data-for-ai/Rules/rewards.md b/docs/data-for-ai/Rules/rewards.md index 7864d0a6..7bb9f9c4 100644 --- a/docs/data-for-ai/Rules/rewards.md +++ b/docs/data-for-ai/Rules/rewards.md @@ -7,7 +7,7 @@ sidebar_position: 3 ## Reward recipients -Only the top 1,000 participants will get prizes, and the rewards will depend on the rank. The rank is determined by the user’s total points: own points plus referral points. +Only the top 1,000 participants will get prizes, and the rewards will depend on the rank. The rank is determined by the user's total points: own points plus referral points. | **Rank** | **USDT** | **Super Stakes** | | :- | :- | :- | @@ -41,7 +41,7 @@ The top 50 participants might be subject to KYC checks to verify identity and pr ## Leaderboard -To check winners, participants, referrals, rewards, and more, [read the campaign’s smart contract](https://opbnb.bscscan.com/address/0x8c77ef6ed2ee514d1754fbfc2710d70e9d6ba871#readContract) on the opBNB network. +To check winners, participants, referrals, rewards, and more, [read the campaign's smart contract](https://opbnb.bscscan.com/address/0x8c77ef6ed2ee514d1754fbfc2710d70e9d6ba871#readContract) on the opBNB network. ### Check a participant @@ -65,7 +65,7 @@ Fields in the example in order of appearance: | `0` | Number of links validated today. Always `0` because the campaign has ended. | | `true` | Flag indicating if the address is registered as a campaign participant. | | `false` | Flag indicating if the address has claimed the reward. | -| `0x8da2c62C23aEBeb1Aa8b5eE96d341d26a2edec6eB` | The referrer’s address. | +| `0x8da2c62C23aEBeb1Aa8b5eE96d341d26a2edec6eB` | The referrer's address. | | `68` | Number of referees. | | `2640` | Points the participant earned for their referrer. | | `67738` | Points the participant earned from their referees. | @@ -73,7 +73,7 @@ Fields in the example in order of appearance: | `0` | Total number of duplicate links submitted. | | `237` | Total number of valid links submitted. | | `152` | Total number of invalid links submitted. | -| `0xbF4aC1b6efd5C21e5Ce93f34c8F43C8a9bCACA3F3` | The participant’s address. | +| `0xbF4aC1b6efd5C21e5Ce93f34c8F43C8a9bCACA3F3` | The participant's address. | | `813` | Current rank in the leaderboard. | | `97280` | Total points earned. | | `10000000000000000000` | USDT reward, in denominations. 1018 = 1 USDT. | diff --git a/docs/developers/cli_guides/providers_offers.md b/docs/developers/cli_guides/providers_offers.md index 9e1941c3..4fd12887 100644 --- a/docs/developers/cli_guides/providers_offers.md +++ b/docs/developers/cli_guides/providers_offers.md @@ -600,4 +600,4 @@ If there is an error, check `error.log` in the Provider Tools directory and `err ## Support -If you have any issues or questions, contact Super Protocol on [Discord](https://discord.gg/superprotocol). The Community Managers will be happy to help you. \ No newline at end of file +If you have any issues or questions, contact Super Protocol on [Discord](https://discord.gg/superprotocol) or via the [contact form](https://superprotocol.zendesk.com/hc/en-us/requests/new). \ No newline at end of file diff --git a/docs/developers/deployment_guides/tunnels/repo.md b/docs/developers/deployment_guides/tunnels/repo.md index 101b3f1b..0f63e806 100644 --- a/docs/developers/deployment_guides/tunnels/repo.md +++ b/docs/developers/deployment_guides/tunnels/repo.md @@ -15,7 +15,7 @@ These Github Actions are automating the commands outlined in the [previous step] 1. Go to [GitHub](https://github.com) and log in to your account. -2. Click the [New Repository](https://github.com/new) button in the top-right. Enter `superprotocol-test-app` as repository name. You’ll have an option there to initialize the repository with a README file. Add `Node` as `.gitignore` template. +2. Click the [New Repository](https://github.com/new) button in the top-right. Enter `superprotocol-test-app` as repository name. You'll have an option there to initialize the repository with a README file. Add `Node` as `.gitignore` template. 3. Click the “Create repository” button. diff --git a/docs/developers/index.md b/docs/developers/index.md index c8d5c39b..d8bcab43 100644 --- a/docs/developers/index.md +++ b/docs/developers/index.md @@ -30,7 +30,7 @@ When you know the basics, try SPCTL—the Super Protocol CLI tool: ## Create your provider and offers with CLI 1. Follow the [Providers and Offers](/developers/cli_guides/providers_offers) guide to create your provider and a first offer. 2. Follow the [Moderation Guidelines](/developers/marketplace/moderation/) to approve your offer for Marketplace GUI. -3. [Update SPCTL configuration](/cli/#for-providers) as a provider to enable management of your provider and offers. +3. [Update SPCTL configuration](/cli/guides/provider-tools#providers-spctl) as a provider to enable management of your provider and offers. 4. Use [SPCTL commands](/developers/cli_guides/providers_offers#faq) to manage your provider and offers. Join us on [Discord](https://discord.gg/superprotocol). The Super Protocol team welcomes any feedback and questions! \ No newline at end of file diff --git a/docs/developers/marketplace_gui/first-steps.md b/docs/developers/marketplace_gui/first-steps.md index 1d7a5aff..60611168 100644 --- a/docs/developers/marketplace_gui/first-steps.md +++ b/docs/developers/marketplace_gui/first-steps.md @@ -214,4 +214,4 @@ Then, click the **Connect Wallet** button in the Marketplace GUI again and sel ## Support -If you have any issues or questions, contact Super Protocol on [Discord](https://discord.gg/superprotocol). Community Managers will be happy to help. \ No newline at end of file +If you have any issues or questions, contact Super Protocol on [Discord](https://discord.gg/superprotocol) or via the [contact form](https://superprotocol.zendesk.com/hc/en-us/requests/new). \ No newline at end of file diff --git a/docs/developers/marketplace_gui/walkthrough.md b/docs/developers/marketplace_gui/walkthrough.md index 60febcd1..4a25bcd8 100644 --- a/docs/developers/marketplace_gui/walkthrough.md +++ b/docs/developers/marketplace_gui/walkthrough.md @@ -7,9 +7,9 @@ sidebar_position: 2 ## 1. Introduction -To better understand how Super Protocol works, let’s take a step-by-step walkthrough through the Marketplace GUI. +To better understand how Super Protocol works, let's take a step-by-step walkthrough through the Marketplace GUI. -As an example we’ll deploy the [Super Chat](/developers/offers/superchat) app with the tunnels. Please note that for this walkthrough we'll be using [Tunnels Launcher](/developers/offers/launcher), which cuts a few corners in order to streamline the experience. For the full tunnels deployment capabilities please refer to [this guide](/developers/deployment_guides/tunnels). +As an example we'll deploy the [Super Chat](/developers/offers/superchat) app with the tunnels. Please note that for this walkthrough we'll be using [Tunnels Launcher](/developers/offers/launcher), which cuts a few corners in order to streamline the experience. For the full tunnels deployment capabilities please refer to [this guide](/developers/deployment_guides/tunnels). You might want to read up on the fundamental Super Protocol concepts - such as [offers](/fundamentals/offers), [orders](/fundamentals/orders), [requirements and configurations](/fundamentals/slots), and [tunnels](/fundamentals/tunnels) - in advance, or - just dive into it and figure it out as you go. Your choice. @@ -142,7 +142,7 @@ To create this order via CLI, click the **Copy CLI workflow** button. It will ge :::info Step 6. Set up a passphrase. -Either input your own passphrase or generate a new one. Then press the `Place Order` button. Save your passphrase! You won’t be able to access your order results without it. For testing it's easier to have a single passphrase for all orders. +Either input your own passphrase or generate a new one. Then press the `Place Order` button. Save your passphrase! You won't be able to access your order results without it. For testing it's easier to have a single passphrase for all orders. ::: diff --git a/docs/fundamentals/certification.md b/docs/fundamentals/certification.md index 611d5375..4ef4e184 100644 --- a/docs/fundamentals/certification.md +++ b/docs/fundamentals/certification.md @@ -5,37 +5,67 @@ slug: "/certification" sidebar_position: 6 --- -Super Protocol uses a certification system for signing data, verifying signatures, and ensuring applications operate within a trusted confidential computing environment. Verified data is published on the blockchain on behalf of confidential containers, allowing anyone to validate application integrity and ensure confidentiality. End users only interact with issued certificates and verify signatures, while the complexities of Remote Attestation are seamlessly managed in the background. +The Super Protocol Certification System is a hierarchical infrastructure for managing trust in confidential computing environments. The main purpose of the system is to create a valid chain of X.509 certificates for any applications running in Trusted Execution Environments (TEEs). The Certification System itself also operates within TEEs, ensuring the entire chain is rooted in hardware-based trust. -All the system components are open-source, ensuring transparency and verifiability. +The Certification System performs remote attestation under the hood, but exposes a familiar X.509-style certificate chain on the surface. This allows any verifier (a user, an auditor, or an automated service) to validate that: + +- The execution took place within a TEE. +- The certificate chain leading to the workload is valid and trusted. + +The Certification System can function as an independent, standalone service. In this capacity, it could serve external companies and users who need to establish certificate chains for their own confidential computing applications. + +Note that the system is not responsible for validating what an application does internally. Its primary role is to issue certificates to trusted confidential environments, forming a cryptographically verifiable trust chain. + +All system components are planned to be open-sourced, improving transparency and verifiability. ## Architecture -The backbone of the system is a hierarchical structure of Certification Authorities operating inside Trusted Execution Environments (TEE)—Intel SGX enclaves. +The Certification System is organized as a hierarchy of Certification Authorities (CAs) that establishes trust for TEEs through a standard certificate chain. Every CA operates within a TEE—Intel SGX enclave.
.default})
-The Root Certification Authority (*Root CA*) is located at the highest hierarchical level. At the start, Root CA generates a self-signed certificate, embedding the SGX attestation quote. +The chain consists of three levels: + +- Root CA is the top-level certificate authority that establishes the trust anchor for the entire system. At the start, it generates a self-signed certificate that embeds the SGX attestation quote. +- SubRoot CAs are intermediate certificate authorities. They submit their quotes and public keys to the Root CA and request certificates. The Root CA verifies these incoming requests and then issues and signs certificates for the SubRoot CAs. Once a SubRoot CA is certified by the Root CA, it can certify any TEE-backed environment that proves it is actually confidential. +- End certificates are issued to specific workloads, entire Confidential Virtual Machines (CVMs) running in TEEs, and in some other cases. These certificates are not CAs and cannot be used to sign or issue other certificates. + +Each level in the hierarchy receives its certificate from the level above, creating a chain of trust that ultimately traces back to the Root CA. + +## Trusted Loader -SubRoot Certification Authorities (*SubRoot CAs*) are located at the next hierarchical level. These submit their quotes and public keys to the Root CA and request certificates. The Root CA verifies these incoming requests and then issues and signs certificates for the SubRoot CAs. +Trusted Loader is a special service that prepares and launches the workload associated with an order inside a CVM running in a TEE. Loader occupies a privileged position within the execution environment, enabling it to access the platform's underlying attestation capabilities. Workloads themselves do not have such access. -The SubRoot CAs, in turn, issue and sign certificates for orders by request. +Trusted Loader also: + +- Collects hashes of the workload and its components. +- Verifies workload integrity before execution starts. +- Requests end certificates. + +All end certificates are requested and received by Trusted Loader. Other components do not interact directly with Certificate Authorities. Trusted Loader may request certificates in several cases: + +- At startup. The certificate confirms that the confidential environment is correctly configured and that the attestation challenge (TDX, SEV-SNP, etc.) matches expectations. +- When generating session keys. The certificate is included in the session key structures used during execution. +- When forming a TEE Confirmation Block (TCB). The certificate is embedded into TCB, which also includes system information and measurements. +- When deploying an order. An order-specific certificate is issued and delivered, along with cryptographic keys, to the order's execution environment. ## Order certificates -The issuing of order certificates involves [Trusted Loader](/whitepaper/tee-provider/#trusted-loader-mechanism)—a mechanism developed to load and run applications within a TEE. Trusted Loader operates inside the Confidential VM that executes the order. This Confidential VM may be deployed within a CPU-based or CPU/GPU-augmented TEE using technologies such as Intel TDX, AMD SEV-SNP, NVIDIA Confidential Computing, or others, making the system TEE-agnostic. +Trusted Loader requests a dedicated order-specific certificate when an order is prepared for execution. This certificate includes order-specific data, such as the hash of workload information. -To receive an order certificate, the Trusted Loader sends a request to a SubRoot CA providing the quote and a public key. The SubRoot CA verifies the quote, issues the order certificate, and signs it with the provided public key. +Trusted Loader places the order certificate as a file into the order's execution environment. There, it can be used by the order itself to prove that it was launched within a confidential environment. + +Note that the Certification System does not determine whether a CVM is correct or compromised. If a CVM runs in a confidential environment, it can obtain certificates. However, differences in hashes are visible in the certificate chain and can be detected by any verifying party. ### Order validation -Orders in Super Protocol are created with necessary input data. This execution environment is referred to as *Workload Info*. +Orders in Super Protocol are created with a workload description known as *Workload Info*. -The Workload Info includes an array called `runtimeInfo[]` with metadata about solutions and datasets used in the order. Each such order component has an entry in this array, which includes: +Workload Info includes an array called `runtimeInfo` that contains information about solutions and data associated with the order. Each data and solution component of the order has an entry in this array, which includes: -- Type +- Type (solution or data) - Hash - Size - Signature key hash (optional) @@ -43,9 +73,13 @@ The Workload Info includes an array called `runtimeInfo[]` with metadata about < The hash of the Workload Info is included in the order certificate. -Trusted Loader generates and publishes a report in the blockchain, allowing anyone to validate the order. This order report includes: +Before order execution begins, Trusted Loader checks the integrity of the full workload composition (solutions, data, and configuration). The order proceeds only if this verification succeeds. + +Trusted Loader also generates and publishes a report to the blockchain, allowing any verifier to validate the order. The report includes: - The public components of all the certificates in the chain - Workload Info: - Order creation date - - The `runtimeInfo[]` array \ No newline at end of file + - The `runtimeInfo` array + +The immutable nature of blockchain prevents any further alterations to the report once it is published. The report enables verifiers to confirm what exactly was launched and that the certificate corresponds to that specific workload. \ No newline at end of file diff --git a/docs/fundamentals/images/certification-system-architecture.png b/docs/fundamentals/images/certification-system-architecture.png index 4e4ffd05..32eead65 100644 Binary files a/docs/fundamentals/images/certification-system-architecture.png and b/docs/fundamentals/images/certification-system-architecture.png differ diff --git a/docs/fundamentals/orders.md b/docs/fundamentals/orders.md index 5bd30508..8532ed07 100644 --- a/docs/fundamentals/orders.md +++ b/docs/fundamentals/orders.md @@ -75,7 +75,8 @@ Statuses: - **New**: The order is waiting for the response from the compute provider. - **In Queue**: The order is waiting in the queue for the compute to become available. This status appears only if the compute is overloaded with orders. - **Processing**: The compute is executing the order inside a TEE. -- **Done**: The order is completed. +- **Done**: The order is completed successfully. +- **Error**: The order completed with an error. Note that the **Processing** and **Done** statuses may have different meanings depending on the usage scenario. For one-time orders, such as executing a Python script, **Processing** means that the machine is working with the solution and data. When this is over, the main order becomes **Done**. diff --git a/docs/guides/index.md b/docs/guides/index.md index 69d2473a..26693316 100644 --- a/docs/guides/index.md +++ b/docs/guides/index.md @@ -7,18 +7,29 @@ sidebar_position: 0 ## Marketplace GUI -|
**Guide**
| **Description**
|
+| **Guide**
| **Description**
|
| :- | :- |
| [Log In with MetaMask](/marketplace/guides/log-in) | How to log in to the [Marketplace](https://marketplace.superprotocol.com/) using MetaMask. |
| [Log In with Trust Wallet](/marketplace/guides/log-in-trustwallet) | How to log in to the Marketplace using Trust Wallet. |
| [Deploy Your Model](/marketplace/guides/deploy-model) | How to upload and deploy an AI model on Super Protocol. |
| [Publish an Offer](/marketplace/guides/publish-offer) | How to upload an AI model and publish it on the Marketplace. |
-| [Prepare a ComfyUI Workflow](/marketplace/guides/prepare-comfyui) | How to prepare a ComfyUI workflow with custom nodes. |
| [Set Up Personal Storage](/marketplace/guides/storage) | How to set up your personal Storj account. |
| [Troubleshooting](/marketplace/guides/troubleshooting) | Most common issues and ways to fix them. |
## CLI
-| **Guide**
| **Description**
|
+| **Guide**
| **Description**
|
+| :- | :- |
+| [Configure SPCTL](/cli) | How to set up SPCTL—a Super Protocol CLI tool. |
+| [Configure Provider Tools](/cli/guides/provider-tools) | How to set up Provider Tools—a Super Protocol CLI utility for registering providers and creating offers. |
+| [Quick Deployment Guide](/cli/guides/deploy-app) | Quick instructions on deploying a solution and data on Super Protocol. |
+| [Confidential Collaboration](/cli/guides/multi-party-collab) | A scenario of confidential collaboration on Super Protocol. |
+
+### Solutions
+
+| **Guide**
| **Description**
|
| :- | :- |
-| [Quick Deployment Guide](/cli/guides/quick-guide) | Quick instructions on deploying a solution and data on Super Protocol. |
\ No newline at end of file
+| [Text Generation WebUI](/cli/guides/solutions/tgwui) | How to deploy a model using Text Generation WebUI. |
+| [ComfyUI](/cli/guides/solutions/comfyui) | How to prepare a ComfyUI workflow with custom nodes. |
+| [Unsloth](/cli/guides/solutions/unsloth) | How to fine-tune an AI model using the Super Protocol packaging of Unsloth. |
+| [vLLM](/cli/guides/solutions/vllm) | How to run a model inference using the Super Protocol packaging of vLLM. |
\ No newline at end of file
diff --git a/docs/hackathon/about.md b/docs/hackathon/about.md
index 181ad43e..c1acdb32 100644
--- a/docs/hackathon/about.md
+++ b/docs/hackathon/about.md
@@ -7,7 +7,7 @@ sidebar_position: 1
## Hackathon
-The [Super Hackathon](https://hackathon.superprotocol.com/) is a global Web3 event designed to demonstrate the scalability and security of Super Protocol’s cloud under real on-chain load. Participants will migrate existing open-source dApps to opBNB, integrate confidential oracle data feeds, and generate verifiable transactions to stress-test performance. The goal is to showcase how real-world decentralized services can operate efficiently, privately, and transparently at scale.
+The [Super Hackathon](https://hackathon.superprotocol.com/) is a global Web3 event designed to demonstrate the scalability and security of Super Protocol's cloud under real on-chain load. Participants will migrate existing open-source dApps to opBNB, integrate confidential oracle data feeds, and generate verifiable transactions to stress-test performance. The goal is to showcase how real-world decentralized services can operate efficiently, privately, and transparently at scale.
## Super Protocol
@@ -15,7 +15,7 @@ The [Super Hackathon](https://hackathon.superprotocol.com/) is a global Web3 eve
## Confidential oracles
-Confidential oracles are a key showcase of Super Protocol’s architecture and the advantages of confidential execution. Built on Chainlink Data Feeds and executed inside TEEs, they keep all data and computations private while remaining verifiable on-chain.
+Confidential oracles are a key showcase of Super Protocol's architecture and the advantages of confidential execution. Built on Chainlink Data Feeds and executed inside TEEs, they keep all data and computations private while remaining verifiable on-chain.
Traditional oracles rely on thousands of untrusted nodes to reach consensus, making the whole process quite expensive. Super Protocol achieves the same trust with far fewer nodes, as each operates inside a TEE that cryptographically guarantees honest execution. A single node with 3 CPUs and 4 GB RAM can handle the workload of about 1,000 Chainlink nodes, delivering major improvements in speed and cost efficiency.
@@ -54,7 +54,7 @@ Prizes are awarded to the team as a whole, not to individual participants or pro
## Community & support
-Official discussions and support take place in Super Protocol’s [Discord server](https://discord.gg/superprotocol), channel #hackathons.
+Official discussions and support take place in Super Protocol's [Discord server](https://discord.gg/superprotocol), channel #hackathons.
Sign up for our newsletter and social media on the [Super Hackathon webpage](https://hackathon.superprotocol.com/) to keep up to date.
diff --git a/docs/hackathon/liquity.md b/docs/hackathon/liquity.md
index d51815a9..f80debef 100644
--- a/docs/hackathon/liquity.md
+++ b/docs/hackathon/liquity.md
@@ -94,7 +94,7 @@ Below is an example of partial console output:
## 6. Configure for opBNB Deployment
-Now that local deployment works, let’s prepare the project for deployment to the opBNB mainnet.
+Now that local deployment works, let's prepare the project for deployment to the opBNB mainnet.
### 6.1. Create the environment file
diff --git a/docs/hackathon/rules.md b/docs/hackathon/rules.md
index 53a72db5..6930d7c8 100644
--- a/docs/hackathon/rules.md
+++ b/docs/hackathon/rules.md
@@ -17,7 +17,7 @@ The interface methods (`latestAnswer`, `getAnswer`, `latestRound`, `getRoundData
The dApp must be open-source and have been publicly deployed before September 1, 2025, on Ethereum, Polygon, or BNB Chain.
-The chosen dApp’s original smart contracts must be verified on a public block explorer (e.g., Etherscan, BscScan, etc.).
+The chosen dApp's original smart contracts must be verified on a public block explorer (e.g., Etherscan, BscScan, etc.).
The migration should require minimal code changes—no more than 5% of the original codebase.
@@ -25,7 +25,7 @@ Teams may submit multiple unique dApps, but each must have a different original
Frontends are welcome but optional—evaluation is based solely on the deployed smart contracts and their on-chain activity.
-The project’s license must allow forking and reuse (acceptable licenses include MIT, Apache 2.0, GPL-family, or equivalent).
+The project's license must allow forking and reuse (acceptable licenses include MIT, Apache 2.0, GPL-family, or equivalent).
## Deploying to opBNB
diff --git a/docs/hackathon/venus-protocol.md b/docs/hackathon/venus-protocol.md
index d4f828a7..c0924b9c 100644
--- a/docs/hackathon/venus-protocol.md
+++ b/docs/hackathon/venus-protocol.md
@@ -141,7 +141,7 @@ For example, [opbnb.bscscan.com/address/0x6DA2Fe3A44dc2837e1ffc450339Ae107AE1AC2
## 12. Submit the migration
-To complete the migration, you’ll need both the original and new contract addresses.
+To complete the migration, you'll need both the original and new contract addresses.
### 12.1. Locate the original deployment
diff --git a/docs/marketplace/Guides/deploy-model.md b/docs/marketplace/Guides/deploy-model.md
index f5b6a77e..d3b0b389 100644
--- a/docs/marketplace/Guides/deploy-model.md
+++ b/docs/marketplace/Guides/deploy-model.md
@@ -33,7 +33,7 @@ Ensure your model meets the Super Protocol requirements:
- Text-to-Video
- Mask Generation
-If you plan to deploy a ComfyUI workflow with custom nodes, [prepare the files](/marketplace/guides/prepare-comfyui) before uploading. For security reasons, you cannot upload custom nodes directly to a deployed ComfyUI.
+If you plan to deploy a ComfyUI workflow with custom nodes, [prepare the files](/cli/guides/solutions/comfyui) before uploading. For security reasons, you cannot upload custom nodes directly to a deployed ComfyUI.
1.2. Due to [testnet limitations](/marketplace/limitations), the total size of model files should not exceed 13 GB. Support for bigger models will be available in the future.
diff --git a/docs/marketplace/Guides/storage.md b/docs/marketplace/Guides/storage.md
index 95915151..21ebb997 100644
--- a/docs/marketplace/Guides/storage.md
+++ b/docs/marketplace/Guides/storage.md
@@ -7,14 +7,12 @@ sidebar_position: 6
This guide provides step-by-step instructions on how to set up your personal Storj account.
-The guide is intended for advanced Web3 users; feel free to skip it and continue using the default recommended option—**Super Protocol cloud**. Read about [types of storage](/marketplace/account/web3#storage).
+The guide is intended for advanced users; feel free to skip it and continue using the default recommended option—**Super Protocol cloud**. Read about [types of storage](/marketplace/account#storage).
-.default})
+.default})
-Web2 users must first [log in as a Web3 user](/marketplace/guides/log-in) to be able to upload to a personal Storj account instead of the Super Protocol cloud. - ## Step 1. Register a Storj account If you don't already have a [Storj](https://www.storj.io/) account, register one. Both free Trial and Pro accounts are suitable. Note that with a Trial account, your files will become inaccessible once the trial period ends. @@ -36,7 +34,7 @@ As a result, you should have two pairs Access Key + Secret Key. ## Step 4. Set up your Super Protocol Web3 account -Open the [Marketplace web app](https://marketplace.superprotocol.com/). Log in as a Web3 user and open the **Account** window. +Open the [Marketplace web app](https://marketplace.superprotocol.com/), sign in and open the **Account** window.
.default})
diff --git a/docs/marketplace/account.md b/docs/marketplace/account.md new file mode 100644 index 00000000..99f147c1 --- /dev/null +++ b/docs/marketplace/account.md @@ -0,0 +1,52 @@ +--- +id: "account" +title: "Enter Marketplace" +slug: "/account" +sidebar_position: 3 +--- + +Super Protocol supports two login methods: + +- Web2 requires an account on one of the supported platforms: + - Google + - Hugging Face + - GitHub + - Microsoft +- Web3 requires a software wallet installed as a browser extension: + - MetaMask + - Trust Wallet + +For instructions on how to set up software wallets and connect them to the Marketplace, read [How to Log In as a Web3 User](/marketplace/guides/log-in). + +
.default})
++
+ +## Account window + +This window shows your user account settings. + +
.default})
++
+ +**User ID**: your unique user ID. + +**Login**: the OAuth2 provider and your login email address. + +The **Get SPPI** button allows you to get tokens necessary to place orders. + +### Storage + +You have two options of decentralized storage to upload files: + +- **Super Protocol cloud**: + - Recommended for most users. + - Does not require additional setup. + - Uses Super Protocol's Storj account and thus relies on Super Protocol as the storage provider. +- **Your Storj account**: + - Intended for advanced users. + - Requires creating and [setting up a Storj account](/marketplace/guides/storage). + - Gives sole control over the uploaded content and storage account. + +Read [How to Set Up Storage](/marketplace/guides/storage) for step-by-step instructions. \ No newline at end of file diff --git a/docs/marketplace/account/index.md b/docs/marketplace/account/index.md deleted file mode 100644 index e2ae472f..00000000 --- a/docs/marketplace/account/index.md +++ /dev/null @@ -1,39 +0,0 @@ ---- -id: "account" -title: "Enter Marketplace" -slug: "/account" -sidebar_position: 3 ---- - -There are two types of accounts in Super Protocol: - -- Web3 User account -- Web2 User account - -
.default})
--
- -## Web3 User account - -_Web3 User account_ provides access to all Marketplace capabilities, including: - -- Full decentralization and sole control of user's funds, models, and datasets. -- Ability to upload models and datasets to the Super Protocol cloud or a personal Storj account. -- Placement of orders using Marketplace offers or the user's own uploaded content. -- Registration of individual providers. -- Creation and monetization of model and dataset offers on the Marketplace. -- Ability to request additional SPPI tokens. - -Read [How to Log In as a Web3 User](/marketplace/guides/log-in) for step-by-step instructions. - -## Web2 User account - -_Web2 User account_ is a quick way to start with the Marketplace. It streamlines a few steps, but this comes at the expense of full decentralization, such as using OAuth2 authentication for login instead of the decentralized MetaMask. - -To log in as a Web2 user, you need an account on one of the supported platforms: - -- Google -- Hugging Face -- GitHub -- Microsoft diff --git a/docs/marketplace/account/web2.md b/docs/marketplace/account/web2.md deleted file mode 100644 index 5e2e2140..00000000 --- a/docs/marketplace/account/web2.md +++ /dev/null @@ -1,31 +0,0 @@ ---- -id: "web2" -title: "Web2 User Account" -slug: "/account/web2" -sidebar_position: 2 ---- - -This window shows the settings of your [Web2 User account](/marketplace/account#web2-user-account). - -
--
- -**User ID**: your unique user ID. - -**Login**: the OAuth2 provider and your login email address. - -## Storage - -Super Protocol supports two options of decentralized storage to upload files: - -- **Super Protocol cloud**: - - Does not require additional setup. - - Uses Super Protocol's Storj account and thus relies on Super Protocol as the storage provider. - - Costs SPPI tokens for additional storage beyond the basic free package. -- **Your Storj account**: - - Available to Web3 users only. - - Requires creating and setting up a Storj account. - - Gives sole control over the uploaded content and storage account. - -To enable uploading to your personal Storj account, [log in as a Web3 user](/marketplace/guides/log-in). \ No newline at end of file diff --git a/docs/marketplace/account/web3.md b/docs/marketplace/account/web3.md deleted file mode 100644 index dd18bbb3..00000000 --- a/docs/marketplace/account/web3.md +++ /dev/null @@ -1,36 +0,0 @@ ---- -id: "web3" -title: "Web3 User Account" -slug: "/account/web3" -sidebar_position: 1 ---- - -This window allows you to manage your [Web3 User account](/marketplace/account#web3-user-account). - -
--
- -**User ID**: your unique user ID is your EVM wallet address. - -**Login**: the Web3 login method and the EVM wallet address you are using. Currently, Super Protocol only supports MetaMask as a Web3 login method. - -**Get SPPI** and **Get BNB** buttons allow you to get tokens necessary to place orders: - -- SPPI tokens are required to pay and receive payments in Super Protocol. -- BNB tokens are required to pay for opBNB blockchain transactions. - -## Storage - -You have two options of decentralized storage to upload files: - -- **Super Protocol cloud**: - - Recommended for most users. - - Does not require additional setup. - - Uses Super Protocol's Storj account and thus relies on Super Protocol as the storage provider. -- **Your Storj account**: - - Intended for advanced users. - - Requires creating and setting up a Storj account. - - Gives sole control over the uploaded content and storage account. - -Read [How to Set Up Storage](/marketplace/guides/storage) for step-by-step instructions. \ No newline at end of file diff --git a/docs/marketplace/images/web2-account.png b/docs/marketplace/images/web2-account.png index 528db2d7..80cc8bee 100644 Binary files a/docs/marketplace/images/web2-account.png and b/docs/marketplace/images/web2-account.png differ diff --git a/docs/marketplace/images/web3-account.png b/docs/marketplace/images/web3-account.png deleted file mode 100644 index 46480abe..00000000 Binary files a/docs/marketplace/images/web3-account.png and /dev/null differ diff --git a/docs/whitepaper/abstract.md b/docs/whitepaper/abstract.md index 31c74761..6e25470f 100644 --- a/docs/whitepaper/abstract.md +++ b/docs/whitepaper/abstract.md @@ -13,7 +13,7 @@ The key Web3 concept is to create open, decentralized alternatives for all the p
.default})
-But decentralization is not the only defining feature of the Web3 concept. It is expected that the following technologies will play a key role in the future: Big Data, AI, IoT, and VR/AR. These technologies require a lot of computational capacity and access to data, know-how and specific tools for creating cutting edge products. The lion’s share of the cloud services market at the moment is [controlled by only three corporations](https://www.canalys.com/newsroom/global-cloud-market-Q121). The same corporations and a number of other similar entities also control most of the data and technologies that will be fundamental for the Internet of the future.
+But decentralization is not the only defining feature of the Web3 concept. It is expected that the following technologies will play a key role in the future: Big Data, AI, IoT, and VR/AR. These technologies require a lot of computational capacity and access to data, know-how and specific tools for creating cutting edge products. The lion's share of the cloud services market at the moment is [controlled by only three corporations](https://www.canalys.com/newsroom/global-cloud-market-Q121). The same corporations and a number of other similar entities also control most of the data and technologies that will be fundamental for the Internet of the future.
In addition to massive centralization of computational capacity, [the year 2020 also saw a serious shortage thereof](https://en.wikipedia.org/wiki/2020%E2%80%932021_global_chip_shortage). This is happening at the time when millions of GPUs are used worldwide [to mine cryptocurrencies](https://en.wikipedia.org/wiki/Proof_of_work) even though they could be deployed to help develop and promote AI solutions in such key areas as healthcare, logistics, education, etc.
diff --git a/docs/whitepaper/blockchain-solution.md b/docs/whitepaper/blockchain-solution.md
index 262c8724..0ea16595 100644
--- a/docs/whitepaper/blockchain-solution.md
+++ b/docs/whitepaper/blockchain-solution.md
@@ -21,7 +21,7 @@ To ensure order processing, the blockchain environment provides an infrastructur
* **TEE Offers**
* **Orders**
-Now let’s take a look at each smart contract in detail.
+Now let's take a look at each smart contract in detail.
### Basic smart contract for the Super Protocol Config system
@@ -257,7 +257,7 @@ The offer describes the cost of using it and the minimum order deposit. To maint
| name | string | offer name |
| description | string | offer description |
| linkage | string | linkage spec, for example, for docker |
-| restrictions | string | possible restrictions and requirements for various provider offers. Used when creating an order. E.g.: ‘{“TEE”: [GUID1, GUID2], “Storage”, “Solution”: [GUID3, GUID4]}’ |
+| restrictions | string | possible restrictions and requirements for various provider offers. Used when creating an order. E.g.: ‘{“TEE”: [GUID1, GUID2], “Storage”, “Solution”: [GUID3, GUID4]}' |
| slots | [{SlotInfo; OptionInfo; SlotUsage}] | array of provided configurations and conditions for their use |
| input | string | input data format |
| output | string | output data format |
@@ -399,7 +399,7 @@ The results of the execution or encountered errors are later added up to the ord
| **cancelOrder(guid orderId) public returns(bool)** | order.consumer | blockchain |
| Request to stop execution of the order on the consumer's side. The order status is changed to "canceling", the provider saves the end result of the order and moves the order to "canceled" status. If the offer is of cancelable type, smart contract immediately refunds the remaining deposit based on the proportion of time running or depositSpent. If the offer is of non-cancellable type, the provider sets a fee for their work after the order is complete.
This method works only when all sub-orders are stopped.
| | | | **refillOrder(guid orderId, uint256 orderAmount)** | order.consumer | blockchain | -| Replenishment of the deposit by the customer. Normally required when renewing a rental. It can also be used to obtain additional results if that is supported by the provider’s offer. | | | +| Replenishment of the deposit by the customer. Normally required when renewing a rental. It can also be used to obtain additional results if that is supported by the provider's offer. | | | | **withdrawProfit(guid orderId) public** | order.provider.tokenReceiver | SDK + blockchain | | Order profit withdrawal by the provider. Available after the order is executed. In this case, the profit is transferred to deferred payments for the number of days specified in the protocol settings (_profitWithdrawDelayDays_). | | | | **withdrawChange(guid orderId) public** | order.consumer | SDK + blockchain | diff --git a/docs/whitepaper/high-level-description.md b/docs/whitepaper/high-level-description.md index 5a660198..6f7a05fe 100644 --- a/docs/whitepaper/high-level-description.md +++ b/docs/whitepaper/high-level-description.md @@ -9,7 +9,7 @@ sidebar_position: 5.default})
-From a bird’s eye view, Super Protocol involves the interactions shown in the above diagram. The interactions include the following entities:
+From a bird's eye view, Super Protocol involves the interactions shown in the above diagram. The interactions include the following entities:
- **Provider Offers.** In a form of a provider offer, the provider offers their resources or values in exchange for a certain reward. The offer can fall into one of three categories:
- **Input.** Offers of this type are used for cooperative processing within a trusted execution environment (TEE). These can be data offers or solution offers.
diff --git a/docs/whitepaper/target-audience.md b/docs/whitepaper/target-audience.md
index 3be24d01..9e2b8787 100644
--- a/docs/whitepaper/target-audience.md
+++ b/docs/whitepaper/target-audience.md
@@ -24,7 +24,7 @@ Super Protocol is very unique in a way that it allows equipment owners to engage
Data in the modern world is being created everywhere, while new, more advanced processing algorithms allow for an ever larger number of ways to use this data. However, there are quite a few challenges here. Obviously, large volumes of data are not originally meant to be public, which means it requires anonymization or confidential computing.
-High-quality anonymization is not always possible without losing data utility. Additionally, many of today’s analytical tools enable successful [data de-anonymization](https://www.cs.utexas.edu/~shmat/shmat_oak09.pdf) under many different circumstances: “To demonstrate its effectiveness on real-world networks, we show that a third of the users who can be verified to have accounts on both Twitter, a popular microblogging service, and Flickr, an online photo-sharing site, can be re-identified in the anonymous Twitter graph with only a 12% error rate.”
+High-quality anonymization is not always possible without losing data utility. Additionally, many of today's analytical tools enable successful [data de-anonymization](https://www.cs.utexas.edu/~shmat/shmat_oak09.pdf) under many different circumstances: “To demonstrate its effectiveness on real-world networks, we show that a third of the users who can be verified to have accounts on both Twitter, a popular microblogging service, and Flickr, an online photo-sharing site, can be re-identified in the anonymous Twitter graph with only a 12% error rate.”
Almost any data owner would benefit from monetizing it—as long as it does not harm their business as a whole. This is borne out by the widespread development of technologies for analyzing big data.
diff --git a/docusaurus.config.js b/docusaurus.config.js
index aa49eaab..e38429ec 100644
--- a/docusaurus.config.js
+++ b/docusaurus.config.js
@@ -42,10 +42,18 @@ const config = {
from: "/hackathon",
to: "/hackathon/about",
},
- /*{
- from: "/colab",
- to: "/colab/jupyter",
- },*/
+ {
+ from: "/cli/guides/quick-guide",
+ to: "/cli/guides/deploy-app",
+ },
+ {
+ from: "/marketplace/account/web2",
+ to: "/marketplace/account#account-window"
+ },
+ {
+ from: "/marketplace/account/web3",
+ to: "/marketplace/account#account-window"
+ },
],
},
],
@@ -195,13 +203,13 @@ const config = {
position: "right",
label: "Developers",
},*/
- {
+ /*{
type: "doc",
docId: "index",
position: "right",
label: "Whitepaper",
docsPluginId: "whitepaper",
- },
+ },*/
],
},
prism: {
@@ -230,7 +238,7 @@ const config = {
"@easyops-cn/docusaurus-search-local",
({
hashed: true,
- docsRouteBasePath: [/*"developers", */"marketplace", "whitepaper", "fundamentals", "cli"],
+ docsRouteBasePath: [/*"developers", */"marketplace", /*"whitepaper", */"fundamentals", "cli"],
language: ["en"],
highlightSearchTermsOnTargetPage: true,
explicitSearchResultPath: true,
diff --git a/src/.DS_Store b/src/.DS_Store
deleted file mode 100644
index bdf7d604..00000000
Binary files a/src/.DS_Store and /dev/null differ
diff --git a/src/css/custom.css b/src/css/custom.css
index 56cd9594..20183983 100644
--- a/src/css/custom.css
+++ b/src/css/custom.css
@@ -34,6 +34,11 @@ ol > li::marker {
font-weight: 500;
}
+/* hide the warning on unlisted pages */
+.theme-unlisted-banner {
+ display: none !important;
+}
+
/* navbar */
.navbar__logo {
height: 1.12em;
diff --git a/src/pages/.DS_Store b/src/pages/.DS_Store
deleted file mode 100644
index d86d37c8..00000000
Binary files a/src/pages/.DS_Store and /dev/null differ
diff --git a/src/theme/Layout/index.js b/src/theme/Layout/index.js
index eeac7d18..980964c8 100644
--- a/src/theme/Layout/index.js
+++ b/src/theme/Layout/index.js
@@ -87,9 +87,21 @@ export default function Layout(props) {
ᐧ A tunnel client hosts a web server; it remains hidden behind the tunnel server and protected from external threats.
+ various hashes, device signature, and a certificate chain for signature verification.
+ + Trusted Loader generates and publishes TCB on the blockchain every 24 hours. +