-
Notifications
You must be signed in to change notification settings - Fork 10
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
4 changed files
with
92 additions
and
3 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,67 @@ | ||
--- | ||
sidebar_position: 2 | ||
title: Node Operators | ||
--- | ||
|
||
## Releases | ||
|
||
At the moment, there are no downloadable binary releases available of the Blobs node. We recommend building a binary from source. | ||
|
||
## Node Architecture | ||
|
||
Blobs is a standard Polkadot-SDK parachain node, which means that it actually runs two nodes: | ||
1. A node for the Parachain (Blobs) on Polkadot or Kusama | ||
2. A node for the Relay Chain, Polkadot or Kusama. | ||
|
||
You can pass arguments to each one of these underlying nodes with the following approach: | ||
|
||
```sh | ||
./sugondat-node --arg-for-blobs --arg2-for-blobs -- --arg-for-relay --arg2-for-relay | ||
``` | ||
|
||
## Blobs and Storage Usage | ||
|
||
Blobs can potentially use enormous amounts of disk space under heavy usage. This is because all historical blobs are stored within the blobchain's history. While the Polkadot and Kusama expunge ancient blobs after 24 hours, any full node of the blobchain will have all the blobs going back to the genesis, as well as all of the other block data. | ||
|
||
To avoid this issue, run with `--blocks-pruning <number>`, where `number` is some relatively small value such as `1000` to avoid keeping all historical blobs. | ||
|
||
However, there is still a need for archival nodes. The main reason is that many rollup SDKs do not have any form of p2p and their nodes synchronize by downloading ancient blobs from the data availability layer's p2p network. Without someone keeping all ancient blocks, those SDKs | ||
would unfortunately stop working. | ||
|
||
## Hardware Requirements | ||
|
||
For full nodes, we currently recommend: | ||
- 4 vCPUs | ||
- 8GB RAM | ||
- 512G Free Disk Space (1TB preferred) | ||
- Stable and fast internet connection. For collators, we recommend 500mbps. | ||
|
||
The disk space requirements can be reduced by | ||
1. Running with `--blocks-pruning` on both | ||
|
||
## Building From Source | ||
|
||
Building from source requires some familiarity with the terminal and your system's package manager. | ||
|
||
First, ensure you have an up-to-date Rust installation. If not, visit https://rustup.rs . | ||
|
||
Building from source requires a few packages to be installed on your system. On Debian or Ubuntu, these are: | ||
|
||
```sh | ||
apt install libssl-dev protobuf-compiler cmake make pkg-config llvm clang | ||
``` | ||
|
||
On other linux distros or Mac, use your package manager's equivalents. | ||
|
||
|
||
Building the node: | ||
```bash | ||
git clone https://github.com/thrumdev/blobs | ||
cd blobs | ||
cargo build --release -p sugondat-node | ||
``` | ||
|
||
Running the node: | ||
```bash | ||
target/release/sugondat-node --chain sugondat-kusama | ||
``` |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters