You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/build-with-powerloom/snapshotter-node/lite-node-v2/Telegram Bot Setup.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,11 +24,11 @@ Introducing the `PowerloomReportingBot`! This bot service maintains an internal
24
24
25
25
- If you have a running node and would like to add the Telegram reporting feature, there are two options that you can use:
26
26
27
-
**Option 1**: Update your `.env` file with the generated `Chat ID` as seen in the image below. Once updated, run the `./build.sh` command again to restart the node.
27
+
**Option 1**: Update your `.env-mainnet-UNISWAPV2-ETH` or `.env-mainnet-AAVEV3-ETH` file with the generated `Chat ID` as seen in the image below. Once updated, run the `./build.sh` command again to restart the node.
**Option 2**: Delete your `.env`file, and then run the `./build.sh` command again to trigger a recreation of the `.env`. This will remove all values from the initial setup, so ensure that you have these available.
31
+
**Option 2**: Delete your `.env-mainnet-UNISWAPV2-ETH` or `.env-mainnet-AAVEV3-ETH`file, and then run the `./build.sh` command again to trigger a recreation of the data market specific `.env` file. This will remove all values from the initial setup, so ensure that you have these available.
32
32
33
33
### To check if the Bot is successfully running, try these:
Copy file name to clipboardExpand all lines: docs/build-with-powerloom/snapshotter-node/lite-node-v2/getting-started.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ This guide provides instructions for installing and running the Snapshotter Lite
13
13
The Snapshotter Lite Node V2 can be set up using either the Docker image or by running natively on the local machine. However, using the Docker image is the recommended approach, as it provides the simplest and most reliable method for deployment.
14
14
15
15
:::tip Node Mint
16
-
Node Mint is now live at: https://mint.powerloom.network/. For detailed information on our rewards structure, frequently asked questions, and other aspects related to node minting, please visit: https://powerloom.network/mint-docs/.
16
+
Node Mint is now live at: https://mint.powerloom.network/. For detailed information on the node mint for Mainnet, please refer to https://blog.powerloom.io/snapshotter-update-power-claims-daily-rewards-new-operator-onboarding/
17
17
18
18
:::
19
19
@@ -211,7 +211,7 @@ After initiating the process, the setup steps will differ depending on whether t
211
211
212
212
3. Optionally, you can provide to following values:
213
213
214
-
-`$TELEGRAM_CHAT_ID`: Can be provided if you would like to enable Telegram reporting for node issues. See our [Telegram Bot Setup](/docs/build-with-powerloom/snapshotter-node/lite-node/Telegram%20Bot%20Setup.md) page for instructions on how to get your Telegram Chat ID.
214
+
-`$TELEGRAM_CHAT_ID`: Can be provided if you would like to enable Telegram reporting for node issues. See our [Telegram Bot Setup](/docs/build-with-powerloom/snapshotter-node/lite-node-v2/Telegram%20Bot%20Setup.md) page for instructions on how to get your Telegram Chat ID.
215
215
216
216
After entering these details, the node will start running the background processes.
217
217
@@ -349,7 +349,7 @@ After initiating the process, the setup steps will differ depending on whether t
349
349
350
350
3. Optionally, you can provide to following values:
351
351
352
-
-`$TELEGRAM_CHAT_ID`: Can be provided if you would like to enable Telegram reporting for node issues. See our [Telegram Bot Setup](/docs/build-with-powerloom/snapshotter-node/lite-node/Telegram%20Bot%20Setup.md) page for instructions on how to get your Telegram Chat ID.
352
+
-`$TELEGRAM_CHAT_ID`: Can be provided if you would like to enable Telegram reporting for node issues. See our [Telegram Bot Setup](/docs/build-with-powerloom/snapshotter-node/lite-node-v2/Telegram%20Bot%20Setup.md) page for instructions on how to get your Telegram Chat ID.
353
353
354
354
After entering these details, the node will start running the background processes.
355
355
@@ -632,7 +632,7 @@ After initiating the process, the setup steps will differ depending on whether t
632
632
633
633
3. Optionally, you can provide to following values:
634
634
635
-
- `$TELEGRAM_CHAT_ID`: Can be provided if you would like to enable Telegram reporting for node issues. See our [Telegram Bot Setup](/docs/build-with-powerloom/snapshotter-node/lite-node/Telegram%20Bot%20Setup.md) page for instructions on how to get your Telegram Chat ID.
635
+
- `$TELEGRAM_CHAT_ID`: Can be provided if you would like to enable Telegram reporting for node issues. See our [Telegram Bot Setup](/docs/build-with-powerloom/snapshotter-node/lite-node-v2/Telegram%20Bot%20Setup.md) page for instructions on how to get your Telegram Chat ID.
636
636
637
637
After entering these details, the node will start running the background processes.
Snapshotter Lite Nodes have the capability to send Telegram messages directly to you if any issues arise during the snapshotting process. See the [Telegram Bot Setup](/docs/build-with-powerloom/snapshotter-node/lite-node/Telegram%20Bot%20Setup.md) page for instructions on how to enable this feature.
19
+
Snapshotter Lite Nodes have the capability to send Telegram messages directly to you if any issues arise during the snapshotting process. See the [Telegram Bot Setup](/docs/build-with-powerloom/snapshotter-node/lite-node-v2/Telegram%20Bot%20Setup.md) page for instructions on how to enable this feature.
20
20
21
21
### Terminal Status Check
22
22
- The primary method to verify node status is through the terminal, which displays log responses from the node.
0 commit comments