Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: oasisprotocol/docs
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: main
Choose a base ref
...
head repository: deltaDAO/oasis-docs
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: main
Choose a head ref
Can’t automatically merge. Don’t worry, you can still create the pull request.
  • 4 commits
  • 2 files changed
  • 1 contributor

Commits on Feb 6, 2024

  1. Copy the full SHA
    9cd596a View commit details
  2. Copy the full SHA
    e9f6322 View commit details

Commits on Feb 7, 2024

  1. Copy the full SHA
    67b8094 View commit details

Commits on Feb 19, 2024

  1. Copy the full SHA
    74246ab View commit details
Showing with 37 additions and 1 deletion.
  1. +26 −0 docs/node/run-your-node/paratime-client-node.mdx
  2. +11 −1 docs/node/run-your-node/prerequisites/system-configuration.mdx
26 changes: 26 additions & 0 deletions docs/node/run-your-node/paratime-client-node.mdx
Original file line number Diff line number Diff line change
@@ -208,6 +208,32 @@ Before using this configuration you should collect the following information to
* You can find the current Oasis Seed Node address in the Network Parameters page ([Mainnet], [Testnet]).
* `{{ runtime_orc_path }}`: Path to the [ParaTime bundle](paratime-client-node.mdx#the-paratime-bundle) of the form `/node/runtimes/foo-paratime.orc`.
* You can find the current Oasis-supported ParaTimes in the Network Parameters page ([Mainnet], [Testnet]).
## Configuring for Confidential States

To enable access to confidential states on your ParaTime Client Node using SGX, follow these steps:

1. **Update Runtime Configuration:**
Add the following configuration to your `/node/etc/config.yml` file:

```yaml
runtime:
# Paths to ParaTime bundles for all of the supported ParaTimes.
paths:
- {{ runtime_orc_path }}
environment: sgx
config:
{{ paratime_id }}:
estimate_gas_by_simulating_contracts: true
allowed_queries:
- all_expensive: true
sgx_loader: /node/bin/oasis-core-runtime-loader
Before using this configuration you should collect the following information to replace the variables present in the configuration file:.
* `{{ paratime_id}}`: RUNTIME_ID - See runtime identifiers on how to choose a runtime identifier.
* `{{ runtime_orc_path }}`: Path to the [ParaTime bundle](paratime-client-node.mdx#the-paratime-bundle) of the form `/node/runtimes/foo-paratime.orc`.
* You can find the current Oasis-supported ParaTimes in the Network Parameters page ([Mainnet], [Testnet]).


## Starting the Oasis Node

12 changes: 11 additions & 1 deletion docs/node/run-your-node/prerequisites/system-configuration.mdx
Original file line number Diff line number Diff line change
@@ -198,7 +198,17 @@ chpst -u oasis oasis-node ...
</TabItem>
</Tabs>

5. Start your Oasis Node.
5. Adding SGX Permissions for ParaTime Node/Client

If you intend to run a ParaTime Node or a ParaTime Client Node and want to enable SGX support, you'll need to ensure that the `oasis` user has the necessary permissions to access SGX resources.

1. **Add `oasis` User to `sgx` Group:**
Ensure that the `oasis` user is added to the `sgx` group to grant it access to SGX resources. You can do this by running:

```bash
sudo usermod -aG sgx oasis
6. Start your Oasis Node.
[`User` directive]:
https://www.freedesktop.org/software/systemd/man/systemd.exec.html#User=