Merge branch 'main' into jcs/arbitrum

celestiaorg · Dec 15, 2023 · aab6cc8 · aab6cc8
2 parents 28d16f1 + ef523d1
commit aab6cc8
Show file tree

Hide file tree

Showing 15 changed files with 91 additions and 49 deletions.
diff --git a/.vitepress/config.ts b/.vitepress/config.ts
@@ -465,6 +465,10 @@ function sidebarHome() {
                   text: "Helpful CLI commands",
                   link: "/nodes/celestia-app-commands",
                 },
+                {
+                  text: "Upgrade Monitor",
+                  link: "/nodes/celestia-app-upgrade-monitor",
+                },
                 {
                   text: "Specifications",
                   link: "https://celestiaorg.github.io/celestia-app/",

diff --git a/community/modular-meetup-intro.md b/community/modular-meetup-intro.md
@@ -42,6 +42,20 @@ participants in maintaining a safe and empowering space for everyone.
 
 - [Celestia.org Community Code of Conduct](./coc.md)
 
+### Signup form
+
+To become part of the program, please
+[complete the registration form](https://docs.google.com/forms/d/1ImYv2sOScgOb0GtWwXSv-ge8uVgO7aFYK42xutJcVtA/edit?usp=sharing_eil_m&ts=6572b6a4).
+
+Following the review and approval of your submission, you will receive
+an email confirmation and an invitation to participate in the upcoming
+Modular Meetup call. Furthermore, you will be granted access to the
+exclusive Discord channel labeled "#modular-meetup" on our Discord server.
+Please take note that [joining our Discord](https://discord.com/invite/YsnTPcSfWQ/)
+is a prerequisite for channel access. It's essential to recognize that
+this program is tailored for dedicated organizers with a genuine interest
+in nurturing their local modular ecosystem community.
+
 ### Emails
 
 As a participant in the Celestia Modular Meetup Program, you
@@ -59,10 +73,7 @@ providing an engaging platform to connect with fellow organizers:
 
 - [Discord](https://discord.com/invite/je7UVpDuDu)
 
-Make sure to join the channel #meetups where we will be also giving
-you the relevant role as a Meetup Organizer.
-
-## Materials
+### Materials
 
 As a meetup organizer, you'll gain access to the Celestia Modular Meetup
 Program's list of resources. This collection should become your trusted
@@ -73,15 +84,3 @@ to explore and learn.
 - [Modular Meetup Toolkit](./modular-meetup-toolkit.md)
 - [Speaker List](./speaker-list.md)
 - [Meetup Guide](./modular-meetup-guide.md)
-
-## Signup form
-
-In order to be added to the Modular Meetup Organizer call, please
-complete the following form:
-
-- [Signup form](https://celestia-intake.typeform.com/to/zNI5W4uI)
-
-We will then send you an email and add you to next upcoming Modular
-Meetup Organizer call. Please keep in mind, this program is meant
-for serious meetup organizers who want to build their local community
-for the modular ecosystem.
diff --git a/developers/blobstream.md b/developers/blobstream.md
@@ -99,11 +99,13 @@ You can interact with the Blobstream contracts today on testnet. The Blobstream
 smart contracts are currently deployed on the following Ethereum testnets:
 
 <!-- markdownlint-disable MD013 -->
-| Contract | EVM network | Contract address | Attested data |
-| --- | --- | --- | --- |
-| Blobstream | Sepolia | [`0x3a5cbB6EF4756DA0b3f6DAE7aB6430fD8c46d247`](https://sepolia.etherscan.io/address/0x3a5cbB6EF4756DA0b3f6DAE7aB6430fD8c46d247) | Mocha testnet |
-| Blobstream | Arbitrum Sepolia | [`0x040769edbca5218e616c8eb16e4faea49ced5e33`](https://sepolia.arbiscan.io/address/0x040769edbca5218e616c8eb16e4faea49ced5e33) | Mocha testnet |
-| Blobstream X | Goerli | [`0x67ea962864cdad3f2202118dc6f65ff510f7bb4d`](https://goerli.etherscan.io/address/0x67ea962864cdad3f2202118dc6f65ff510f7bb4d) | Mocha testnet |
+
+| Contract     | EVM network      | Contract address                                                                                                                | Attested data |
+| ------------ | ---------------- | ------------------------------------------------------------------------------------------------------------------------------- | ------------- |
+| Blobstream   | Sepolia          | [`0x3a5cbB6EF4756DA0b3f6DAE7aB6430fD8c46d247`](https://sepolia.etherscan.io/address/0x3a5cbB6EF4756DA0b3f6DAE7aB6430fD8c46d247) | Mocha testnet |
+| Blobstream   | Arbitrum Sepolia | [`0x040769edbca5218e616c8eb16e4faea49ced5e33`](https://sepolia.arbiscan.io/address/0x040769edbca5218e616c8eb16e4faea49ced5e33)  | Mocha testnet |
+| Blobstream X | Goerli           | [`0x67ea962864cdad3f2202118dc6f65ff510f7bb4d`](https://goerli.etherscan.io/address/0x67ea962864cdad3f2202118dc6f65ff510f7bb4d)  | Mocha testnet |
+
 <!-- markdownlint-enable MD013 -->
 
 ## Blobstream vs. data availability committees (DACs)

diff --git a/developers/node-tutorial.md b/developers/node-tutorial.md
@@ -55,7 +55,7 @@ If you would like to use them anyway, you can
 The following minimum hardware requirements are recommended for running a
 light node:
 
-- Memory: **2 GB RAM**
+- Memory: **500 MB RAM (minimum)**
 - CPU: **Single Core**
 - Disk: **50 GB SSD Storage**
 - Bandwidth: **56 Kbps for Download/56 Kbps for Upload**
@@ -236,10 +236,28 @@ commands:
 
 3. Build the `celestia` binary:
 
-   ```bash
-   make build
+   a. Standard build
+
+      ```bash
+      make build
+      ```
+
+   b. Experimental build
+
+   :::tip OPTIONAL
+   If you're a node operator comfortable with experimental features and
+   seeking optimal performance with minimal RAM usage, this option is
+   recommended for you.
+
+    ```bash
+   make build-jemalloc
    ```
 
+   This build option enables CGO, and downloads and installs
+   [jemalloc](https://jemalloc.net/).
+   [Learn more about the build command](https://github.com/celestiaorg/celestia-node/releases/tag/v0.12.1#:~:text=%F0%9F%8F%97%EF%B8%8F-,New%20build%20option,-%3A%20Makefile%20now%20has).
+   :::
+
 4. Install the binary:
 
    ::: code-group

diff --git a/developers/optimism.md b/developers/optimism.md
@@ -131,9 +131,11 @@ a DA server on port 26650.
 
 For the `P2P_NETWORK` variable, you'll need to supply the network of choice, either
 `celestia`, `mocha`, or `arabica`. Using `celestia`, the volume path will be just
-`.celestia-light` instead of `.celestia-light-<network>`.
+`.celestia-light` instead of `.celestia-light-<network>`. You will also need
+to provide a core.ip RPC URL for the network you are using.
 
 <!-- markdownlint-disable MD013 -->
+
 ```yaml
 da:
   image: ghcr.io/rollkit/local-celestia-devnet:v0.12.1 // [!code --]
@@ -143,7 +145,7 @@ da:
     --p2p.network=<network> // [!code ++]
     --da.grpc.namespace=000008e5f679bf7116cb // [!code ++]
     --da.grpc.listen=0.0.0.0:26650 // [!code ++]
-    --core.ip rpc.celestia.pops.one // [!code ++]
+    --core.ip <rpc-url> // [!code ++]
     --gateway // [!code ++]
   environment: // [!code ++]
       - NODE_TYPE=light // [!code ++]

diff --git a/nodes/blobstream-orchestrator.md b/nodes/blobstream-orchestrator.md
@@ -155,7 +155,7 @@ To start the orchestrator in the default home directory, run the following:
 blobstream orchestrator start --evm.account 0x966e6f22781EF6a6A82BBB4DB3df8E225DfD9488
 ```
 
-> **_NOTE:_** The above command assumes that the necessary configuration is specified in the  `<orchestrator_home>/config/config.toml` file.
+> **_NOTE:_** The above command assumes that the necessary configuration is specified in the `<orchestrator_home>/config/config.toml` file.
 
 Then, you will be prompted to enter your EVM key passphrase so that the orchestrator can use it to sign attestations. Make sure that it's the EVM address that was provided when creating the validator. If not, then the orchestrator will not sign, and you will keep seeing a "validator not part of valset" warning message. If you see such message, first verify that your validator is part of the active validator set. If so, then probably the EVM address provided to the orchestrator is not the right one, and you should check which EVM address is registered to your validator. Check the [Register EVM Address](#register-evm-address) section for more information.
 
@@ -166,7 +166,7 @@ If you no longer have access to your EVM address, you could always edit your val
 #### `transport: authentication handshake failed`
 
 ```text
-rpc error: code = Unavailable desc = connection error: desc = "transport: authentication handshake failed: tls: first record does not look like a TLS handshake" 
+rpc error: code = Unavailable desc = connection error: desc = "transport: authentication handshake failed: tls: first record does not look like a TLS handshake"
 ```
 
 Seeing this error means that the orchestrator/relayer is trying to connect to a gRPC endpoint that is not secure. To bypass this, use the `--grpc.insecure` flag. However, we recommend using secure gRPC connections.

diff --git a/nodes/blobstream-relayer.md b/nodes/blobstream-relayer.md
@@ -118,6 +118,6 @@ To start the relayer using the default home directory, run the following:
 /bin/blobstream relayer start --evm.account=0x35a1F8CE94187E4b043f4D57548EF2348Ed556c8
 ```
 
-> **_NOTE:_** The above command assumes that the necessary configuration is specified in the  `<relayer_home>/config/config.toml` file.
+> **_NOTE:_** The above command assumes that the necessary configuration is specified in the `<relayer_home>/config/config.toml` file.
 
 Then, you will be prompted to enter your EVM key passphrase for the EVM address passed using the `--evm.account` flag, so that the relayer can use it to send transactions to the target Blobstream smart contract. Make sure that it's funded.
diff --git a/nodes/bridge-node.md b/nodes/bridge-node.md
@@ -47,7 +47,7 @@ From an implementation perspective, Bridge nodes run two separate processes:
 The following hardware minimum requirements are recommended for running the
 bridge node:
 
-- Memory: **32 GB RAM**
+- Memory: **4 GB RAM (minimum)**
 - CPU: **6 cores**
 - Disk: **10 TB SSD Storage**
 - Bandwidth: **1 Gbps for Download/1 Gbps for Upload**

diff --git a/nodes/celestia-app-upgrade-monitor.md b/nodes/celestia-app-upgrade-monitor.md
@@ -0,0 +1,9 @@
+---
+description: upgrade-monitor is a tool to monitor upgrades on a Celestia network.
+---
+
+# Upgrade Monitor
+
+Upgrade monitor is a binary that monitors that status of upgrades on a Celestia
+network. See the [README](https://github.com/celestiaorg/upgrade-monitor) for
+instructions on how to install and use the binary.
diff --git a/nodes/celestia-node.md b/nodes/celestia-node.md
@@ -49,10 +49,28 @@ commands:
 
 3. Build the `celestia` binary:
 
-   ```bash
-   make build
+   a. Standard build
+
+      ```bash
+      make build
+      ```
+
+   b. Experimental build
+
+   :::tip OPTIONAL
+   If you're a node operator comfortable with experimental features and
+   seeking optimal performance with minimal RAM usage, this option is
+   recommended for you.
+
+    ```bash
+   make build-jemalloc
    ```
 
+   This build option enables CGO, and downloads and installs
+   [jemalloc](https://jemalloc.net/).
+   [Learn more about the build command](https://github.com/celestiaorg/celestia-node/releases/tag/v0.12.1#:~:text=%F0%9F%8F%97%EF%B8%8F-,New%20build%20option,-%3A%20Makefile%20now%20has).
+   :::
+
 4. Install the binary:
 
    ::: code-group

diff --git a/nodes/full-storage-node.md b/nodes/full-storage-node.md
@@ -22,7 +22,7 @@ between one another.
 The following hardware minimum requirements are recommended for running
 the full storage node:
 
-- Memory: **32 GB RAM**
+- Memory: **4 GB RAM (minimum)**
 - CPU: **6 cores**
 - Disk: **10 TB SSD Storage**
 - Bandwidth: **1 Gbps for Download/1 Gbps for Upload**

diff --git a/nodes/hardfork-process.md b/nodes/hardfork-process.md
@@ -62,18 +62,3 @@ new keys in order to have a successful upgrade.
 Those two keys will need to be added to 2 new flags on `celestia-app`:
 
 - `--evm-address`: This flag should contain a `0x` EVM address.
-
-### Blockspace race hardfork
-
-The Blockspace Race hardfork process will follow
-a different workflow than regular Tendermint and Cosmos-SDK
-network upgrades.
-
-Instead of using tools like Cosmovisor and swapping binaries at block
-activation number, validators will be upgrading to new binaries
-ahead of the hardfork block number. The new binaries will have
-the new logic and features for activating when the target block
-number for the hardfork is reached.
-
-To prepare for the hardfork, please upgrade to the new `celestia-app`
-version referenced in the Blockspace Race task.
diff --git a/nodes/light-node.md b/nodes/light-node.md
@@ -27,7 +27,7 @@ Light nodes have the following behavior:
 The following minimum hardware requirements are recommended for running
 a light node:
 
-- Memory: **2 GB RAM**
+- Memory: **500 MB RAM (minimum)**
 - CPU: **Single Core**
 - Disk: **50 GB SSD Storage**
 - Bandwidth: **56 Kbps for Download/56 Kbps for Upload**

diff --git a/nodes/mainnet.md b/nodes/mainnet.md
@@ -94,6 +94,11 @@ RPCs for DA nodes to initialise or start your celestia-node to Mainnet Beta with
   - gRPC: port 9090
   - RPC: port 26657
 
+DA full and light nodes might have troubles connecting to the networks, so you
+can checkout this
+[Grafana dashboard](https://celestia.grafana.net/public-dashboards/a10eff0043bb4bf0839004e2746e2bc6)
+to see health/uptime status of DA bootstrappers (now `celestia` network only).
+
 ### Consensus nodes
 
 - [Full consensus node](./consensus-node.md)

diff --git a/public/img/node-requirements.jpg b/public/img/node-requirements.jpg