Skip to content

Commit

Permalink
GITBOOK-741: No subject
Browse files Browse the repository at this point in the history
  • Loading branch information
Alex Hertlein authored and gitbook-bot committed May 30, 2024
1 parent 59c99fa commit 5b3f104
Show file tree
Hide file tree
Showing 97 changed files with 123 additions and 149 deletions.
163 changes: 82 additions & 81 deletions SUMMARY.md

Large diffs are not rendered by default.

Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ We will explore how to instantiate a contract on Secret Network with specific pa

Before running this command, ensure you have the following:

* A working installation of `secretcli`, see here: [installing-cli-and-creating-a-new-address.md](../../infrastructure/setting-up-a-node-validator/node-setup/installing-cli-and-creating-a-new-address.md "mention")
* A working installation of `secretcli`, see here: [installing-cli-and-creating-a-new-address.md](../../infrastructure/running-a-node-validator/setting-up-a-node-validator/node-setup/installing-cli-and-creating-a-new-address.md "mention")
* Understanding of smart contracts and Secret Network's privacy features
* The correct IBC Token denomination, see below.

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -32,8 +32,8 @@ it was later recognised that this was because of the same problem with Secpk ver

1. Firstly, a small upgrade was released which significantly improved the query node performance. This upgrade allows nodes to both serve many more requests, and lessen the impact of long block computations. This will help services like Keplr stay available during network-wide events. Reference: [https://github.com/scrtlabs/SecretNetwork/releases/tag/v1.2.5](https://github.com/scrtlabs/SecretNetwork/releases/tag/v1.2.5)
2. The execution performance for computationally expensive functions like secp256k1 verification are changed to being exposed to contracts (instead of being executed inside the contract) which made them much more efficient. New APIs were released during Shockwave Alpha which brought 500x improvements to these transactions. Reference: [https://github.com/scrtlabs/SecretNetwork/releases/tag/v1.3.0](https://github.com/scrtlabs/SecretNetwork/releases/tag/v1.3.0)
3. Introduced Seeds for solving the validator peering issues. One can reference the [validator documentation](../setting-up-a-node-validator/testnet/run-a-full-node.md) to add these seeds to their peering list.
4. We are also replacing our WASM engine with a newer, more performant one. This item is still on the [roadmap](../../../overview-ecosystem-and-technology/secret-network-overview/roadmap/) and will help with long term scalability of Secret Network.
3. Introduced Seeds for solving the validator peering issues. One can reference the [validator documentation](../running-a-node-validator/setting-up-a-node-validator/testnet/run-a-full-node.md) to add these seeds to their peering list.
4. We are also replacing our WASM engine with a newer, more performant one. This item is still on the [roadmap](../../overview-ecosystem-and-technology/secret-network-overview/roadmap/) and will help with long term scalability of Secret Network.
5. Lastly, we will also be re-evaluating gas calculation and pricing and try to adjust the gas to more accurately reflect the computational cost of each contract. This was a huge lesson learned, gas needs to equal the computational cost or nodes will not be able to handle the load.

> For some extra information on lessons learned from this event you can read this blog: [https://scrt.network/blog/scrt-labs-update-scaling-secrets](https://scrt.network/blog/scrt-labs-update-scaling-secrets)
2 changes: 2 additions & 0 deletions infrastructure/running-a-node-validator/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,2 @@
# Running a node/validator

File renamed without changes.
Original file line number Diff line number Diff line change
Expand Up @@ -4,4 +4,4 @@ description: General Overview

# Helpful commands

This section only covers some of the SecretCLI commands, for all commands please reference the [SecretCLI documentation](../../secret-cli/) instead.
This section only covers some of the SecretCLI commands, for all commands please reference the [SecretCLI documentation](../../../secret-cli/) instead.
Original file line number Diff line number Diff line change
Expand Up @@ -15,15 +15,15 @@ If you get this, generally your server has restarted erroneously. In order to fi
systemctl restart aesmd && journalctl -fu aesmd
```
![aesmd.service](<../../.gitbook/assets/Screen Shot 2022-06-27 at 5.54.36 PM.png>)
![aesmd.service](<../../../.gitbook/assets/Screen Shot 2022-06-27 at 5.54.36 PM.png>)
4\. Restart `secret-node.service`
```
systemctl restart secret-node && journalctl -fu secret-node
```
![Expected Output](<../../.gitbook/assets/Screen Shot 2022-06-27 at 5.57.39 PM.png>)
![Expected Output](<../../../.gitbook/assets/Screen Shot 2022-06-27 at 5.57.39 PM.png>)
## Blocks Aren't Being Produced
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -5,4 +5,4 @@ These pages go into detail for setting up infrastructure other than full nodes a
* [Sentry nodes](sentry-nodes.md)
* [Mantlemint](mantlemint.md)
* [Archive](archive-nodes.md)
* [IBC relayers](../ibc-relayers/)
* [IBC relayers](../../ibc-relayers/)
Original file line number Diff line number Diff line change
Expand Up @@ -4,13 +4,6 @@

An archive node keeps all the past blocks. An archive node makes it convenient to query the past state of the chain at any point in time. Finding out what an account's balance, stake size, etc at a certain block was, or which extrinsics resulted in a certain state change are fast operations when using an archive node. However, an archive node takes up a lot of disk space - nearly 2TB for `secret-4` as of Feb 1, 2023.

### Recommended Requirements <a href="#recommended-requirements" id="recommended-requirements"></a>

* 32GB RAM
* 3TB NVMe SSD
* 2 dedicated cores of any Intel Skylake processor (Intel® 6th generation) or better (Xeon gen3 (Ice Lake) NOT supported)
* Motherboard with support for SGX in the BIOS

More on hardware support [here](../setting-up-a-node-validator/hardware-setup/hardware-compliance.md).

{% hint style="info" %}
Expand All @@ -21,29 +14,7 @@ To setup your archive node you can follow the instructions below:

### Install latest `secretd`

Download the secretd .deb from the [latest release](https://github.com/scrtlabs/SecretNetwork/releases/latest).

**Note**: As of writing these lines the latest release is `v1.6.0` will be referenced as so for the rest of this document.

**Node**: Archive nodes are only available with `goleveldb`. If this doesn't mean anything to you, just proceed with this guide as usual.

```bash
# Get the v1.6.0 binaries
wget "https://github.com/scrtlabs/SecretNetwork/releases/download/v1.6.0/secretnetwork_1.6.0_mainnet_goleveldb_amd64.deb"

# Verify the v1.6.0 binaries
echo 'ce9ba85d346fa460ed3fc98871f2a254b269fafa835fc555c9184f6405d8c80a secretnetwork_1.6.0_mainnet_goleveldb_amd64.deb' | sha256sum --check
```

#### Install `secretd`

```bash
sudo dpkg -i secretnetwork_1.6.0_mainnet_goleveldb_amd64.deb

# verify installation
secretd version
# 1.6.0
```
To install `secretd`, please visit [install-secretd.md](../setting-up-a-node-validator/node-setup/install-secretd.md "mention").

### Setup the Node

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -73,7 +73,7 @@ sudo apt install -y ./secretnetwork_1.3.1_mainnet_*_amd64.deb

#### 4. Register the node

To allow Mantlemint to sync blocks and run queries that contain encrypted data, we will need to [register](../node-runners/sentry-archive-and-ibc-node-setup/broken-reference/) it.
To allow Mantlemint to sync blocks and run queries that contain encrypted data, we will need to [register](../../node-runners/sentry-archive-and-ibc-node-setup/broken-reference/) it.

```bash
export SCRT_ENCLAVE_DIR=/usr/lib
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -18,14 +18,14 @@ All cost estimates are based on the following recommendations:
Just because a VPS is cheaper it does not make it better.
{% endhint %}

| VPS Provider | Cost/month | Setup Instructions |
| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------- | -------------------------------- |
| [**Microsoft Azure**](https://azure.microsoft.com/en-us/solutions/confidential-compute/#overview) | TBD | [Here](microsoft-azure-setup.md) |
| [**Psychz**](https://www.psychz.net/dashboard/client/web/order/dedicated-server?processor=\&processorBaseFreq=\&numberOfCpu=7391\&cpuCores=\&location=) | 144 | [Here](psychz-setup.md) |
| [**nForce**](https://www.nforce.com/customserver) | 95 | [Here](nforce-setup.md) |
| [**Leaseweb**](https://www.leaseweb.com/dedicated-servers/build-your-own) | 89 | [Here](leaseweb-setup.md) |
| [**Vultr**](https://www.vultr.com/products/bare-metal/) | 185 | [Here](vultr-setup.md) |
| [**PhoenixNap**](https://admin.phoenixnap.com/wap-pncpadmin-shell/orderForm?bmbPath=/order-management/order-form?currencyCode=usd) | 210 | [Here](phoenixnap-setup.md) |
| [**OVHCloud**](https://www.ovhcloud.com/en/bare-metal/rise/rise-3/) | 144 | [Here](ovhcloud-setup.md) |
| Hetzner | \*NOT SUPPORTED\* | |
| [**IPAX**](../../../node-runners/vps-compliance/\[https:/azure.microsoft.com/en-us/solutions/confidential-compute/#overview]\(https://www.ipax.at/rootserver-mieten/dedicated-server-mieten/leistungsstarke-dedizierte-server/\)) | 160 | X1 (Professional Line) |
| VPS Provider | Cost/month | Setup Instructions |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------- | -------------------------------- |
| [**Microsoft Azure**](https://azure.microsoft.com/en-us/solutions/confidential-compute/#overview) | TBD | [Here](microsoft-azure-setup.md) |
| [**Psychz**](https://www.psychz.net/dashboard/client/web/order/dedicated-server?processor=\&processorBaseFreq=\&numberOfCpu=7391\&cpuCores=\&location=) | 144 | [Here](psychz-setup.md) |
| [**nForce**](https://www.nforce.com/customserver) | 95 | [Here](nforce-setup.md) |
| [**Leaseweb**](https://www.leaseweb.com/dedicated-servers/build-your-own) | 89 | [Here](leaseweb-setup.md) |
| [**Vultr**](https://www.vultr.com/products/bare-metal/) | 185 | [Here](vultr-setup.md) |
| [**PhoenixNap**](https://admin.phoenixnap.com/wap-pncpadmin-shell/orderForm?bmbPath=/order-management/order-form?currencyCode=usd) | 210 | [Here](phoenixnap-setup.md) |
| [**OVHCloud**](https://www.ovhcloud.com/en/bare-metal/rise/rise-3/) | 144 | [Here](ovhcloud-setup.md) |
| Hetzner | \*NOT SUPPORTED\* | |
| [**IPAX**](../../../../node-runners/vps-compliance/\[https:/azure.microsoft.com/en-us/solutions/confidential-compute/#overview]\(https://www.ipax.at/rootserver-mieten/dedicated-server-mieten/leistungsstarke-dedizierte-server/\)) | 160 | X1 (Professional Line) |
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ Secret Network has strict Hardware Requirements, see [hardware-compliance.md](..
* A public IP address, so that other nodes can connect to you.
* Open ports `TCP 26656 & 26657` _Note: If you're behind a router or firewall then you'll need to port forward on the network device._
* Reading [Tendermint: Running in production](https://docs.tendermint.com/v0.34/tendermint-core/running-in-production.html)
* RPC address of an already active node. You can use any node that exposes RPC services, please see [mainnet-secret-4.md](../../../development/resources-api-contract-addresses/connecting-to-the-network/mainnet-secret-4.md "mention").
* RPC address of an already active node. You can use any node that exposes RPC services, please see [mainnet-secret-4.md](../../../../development/resources-api-contract-addresses/connecting-to-the-network/mainnet-secret-4.md "mention").

## Installation <a href="#installation" id="installation"></a>

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ Secret Network has strict Hardware Requirements. If your machine does not meet t
* A public IP address
* Open ports `TCP 26656 & 26657` _Note: If you're behind a router or firewall then you'll need to port forward on the network device._
* Reading [Tendermint: Running in production](https://docs.tendermint.com/v0.34/tendermint-core/running-in-production.html)
* RPC address of an already active node. You can use `http://bootstrap.pulsar3.scrtlabs.com:26657`, or any other node that exposes RPC services. Alternate RPC nodes available in the [API Registry.](../../../development/resources-api-contract-addresses/connecting-to-the-network/)
* RPC address of an already active node. You can use `http://bootstrap.pulsar3.scrtlabs.com:26657`, or any other node that exposes RPC services. Alternate RPC nodes available in the [API Registry.](../../../../development/resources-api-contract-addresses/connecting-to-the-network/)
* [Install SGX](broken-reference)

## Installation <a href="#installation" id="installation"></a>
Expand All @@ -25,7 +25,7 @@ Secret Network has strict Hardware Requirements. If your machine does not meet t
This guide assumes you've already installed the latest version of secretd and SGX. To setup an archive node, you must follow the [Archive Nodes](../../sentry-archive-and-ibc-node-setup/archive-nodes.md) instructions.
{% endhint %}

For more information on SGX, see instructions for [SGX Installation](broken-reference) and [Verifying SGX](../../node-runners/testnet/broken-reference/). See [Node Registration Information](../../node-runners/testnet/broken-reference/) if you'd like a more comprehensive overview on what's happening in these steps.
For more information on SGX, see instructions for [SGX Installation](broken-reference) and [Verifying SGX](../../../node-runners/testnet/broken-reference/). See [Node Registration Information](../../../node-runners/testnet/broken-reference/) if you'd like a more comprehensive overview on what's happening in these steps.

### **Initialize Secret Network Configs**

Expand Down
2 changes: 1 addition & 1 deletion infrastructure/secret-cli/slashing.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Slashing

A user can query and interact with the `slashing` module using the CLI. For more information about how slashing works on the Secret Network go to the [Node Runners](../maintaining-a-node-validator/node-runners.md) page and look for the '[Slashing For Downtime](../maintaining-a-node-validator/node-runners.md#slashing-for-downtime)' section.
A user can query and interact with the `slashing` module using the CLI. For more information about how slashing works on the Secret Network go to the [Node Runners](../running-a-node-validator/maintaining-a-node-validator/node-runners.md) page and look for the '[Slashing For Downtime](../running-a-node-validator/maintaining-a-node-validator/node-runners.md#slashing-for-downtime)' section.

See [Slashing](https://docs.cosmos.network/main/modules/slashing/) for the official Cosmos Network module documentation.

Expand Down
4 changes: 2 additions & 2 deletions infrastructure/upgrade-instructions/shockwave-delta.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@
### ⚠️ IMPORTANT NOTES ⚠️ <a href="#important-notes" id="important-notes"></a>

* All coordination efforts will be done in the "SN Validators" Telegram group.
* Make sure to [backup your validator](../maintaining-a-node-validator/validator-backup.md) before making any chnages.
* Make sure to [backup your validator](../running-a-node-validator/maintaining-a-node-validator/validator-backup.md) before making any chnages.
* **Please read carefully before you begin the upgrade.**

## Upgrading Manually <a href="#upgrading-manually" id="upgrading-manually"></a>
Expand Down Expand Up @@ -57,7 +57,7 @@ Cosmovisor is a new process manager for cosmos blockchains. It can make low-down
⚠️ Cosmovisor is still new and best practices for using it are not yet established. If you don't feel adventurous at this time, we recommend [upgrading the manual way](shockwave-delta.md#upgrading-manually).
For instructions on how to setup Cosmovisor, go [here](../../../validators/migration/cosmovisor.md).
For instructions on how to setup Cosmovisor, go [here](../../validators/migration/cosmovisor.md).
## Details of Upgrade Time <a href="#details-of-upgrade-time" id="details-of-upgrade-time"></a>
Expand Down
4 changes: 2 additions & 2 deletions infrastructure/upgrade-instructions/shockwave-omega.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@
### ⚠️ IMPORTANT NOTES ⚠️ <a href="#important-notes" id="important-notes"></a>

* All coordination efforts will be done in the "SN Validators" Telegram group.
* Make sure to [backup your validator](../maintaining-a-node-validator/validator-backup.md) before making any chnages.
* Make sure to [backup your validator](../running-a-node-validator/maintaining-a-node-validator/validator-backup.md) before making any chnages.
* **Please read carefully before you begin the upgrade.**

## Check your hardware compatiblity before the upgrade
Expand Down Expand Up @@ -75,7 +75,7 @@ Cosmovisor is a new process manager for cosmos blockchains. It can make low-down
⚠️ Cosmovisor is still new and best practices for using it are not yet established. If you don't feel adventurous at this time, we recommend [upgrading the manual way](shockwave-omega.md#upgrading-manually).
For instructions on how to setup Cosmovisor, go [here](../../../validators/migration/cosmovisor.md).
For instructions on how to setup Cosmovisor, go [here](../../validators/migration/cosmovisor.md).
## Details of Upgrade Time <a href="#details-of-upgrade-time" id="details-of-upgrade-time"></a>
Expand Down
2 changes: 1 addition & 1 deletion infrastructure/upgrade-instructions/v1.10.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@
### ⚠️ IMPORTANT NOTES ⚠️ <a href="#important-notes" id="important-notes"></a>

* All coordination efforts will be done in the "SN Validators" Telegram group.
* Make sure to [backup your validator](../maintaining-a-node-validator/validator-backup.md) before making any changes.
* Make sure to [backup your validator](../running-a-node-validator/maintaining-a-node-validator/validator-backup.md) before making any changes.
* **Please read carefully before you begin the upgrade.**

## Upgrading Manually <a href="#upgrading-manually" id="upgrading-manually"></a>
Expand Down
Loading

0 comments on commit 5b3f104

Please sign in to comment.