Skip to content

Commit f56cfa2

Browse files
add to docs
1 parent 38301fe commit f56cfa2

File tree

3 files changed

+24
-8
lines changed

3 files changed

+24
-8
lines changed

docs/user/staking/ethereum/lsd-pools/lido/already-node-operator.md

Lines changed: 12 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -41,25 +41,25 @@ The Lido CSM UI serves as the central interface for managing validator keys and
4141

4242
1. Access the Lido CSM UI:
4343

44-
Navigate to the Lido CSM package UI. - [Mainnet UI](http://ui.lido-csm-mainnet.dappnode/) - [Holesky UI](http://ui.lido-csm-holesky.dappnode/)
44+
Navigate to the Lido CSM package UI. - [Mainnet UI](http://ui.lido-csm-mainnet.dappnode/) - [Holesky UI](http://ui.lido-csm-holesky.dappnode/)
4545

4646
2. Connect Your Wallet:
4747

48-
Use the “I am a Node Operator” button and choose your wallet provider.
48+
Use the “I am a Node Operator” button and choose your wallet provider.
4949

50-
![Log In as already Node Operator](/img/lido-csm-log-in-already-NO.png)
50+
![Log In as already Node Operator](/img/lido-csm-log-in-already-NO.png)
5151

5252
3. Authorize the Connection:
5353

54-
- Follow the on-screen prompts to grant the necessary permissions.
54+
- Follow the on-screen prompts to grant the necessary permissions.
5555

56-
- Ensure the wallet’s network matches the intended environment (e.g., Mainnet or Holesky).
56+
- Ensure the wallet’s network matches the intended environment (e.g., Mainnet or Holesky).
5757

5858
4. Verify Connection:
5959

60-
Once connected, your wallet address will appear in the top-right corner of the interface.
60+
Once connected, your wallet address will appear in the top-right corner of the interface.
6161

62-
![Ensure wallet is connected](/img/lido-csm-wallet-connected.png)
62+
![Ensure wallet is connected](/img/lido-csm-wallet-connected.png)
6363

6464
## 3. Configuring Telegram Notifications
6565

@@ -100,7 +100,11 @@ Staying informed helps safeguard your assets, reduce risks, and maintain transpa
100100

101101
Enter the bot token and your user ID in the Lido CSM package UI and click `Update Telegram Data`.
102102
![Set up Notifications](/img/lido-csm-setup-notifications.png)
103-
103+
104+
:::warning
105+
You must start the conversation with the bot using `/start` so it can send you notifications.
106+
:::
107+
104108
:::caution
105109
To receive the notifications, is mandatory to fill both inputs, otherwise the notification system won't work
106110
:::

docs/user/staking/ethereum/lsd-pools/lido/notifications.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -24,6 +24,14 @@ You will be able to setup your notifications either during the onboarding proces
2424
- Bot token: this is the secret token from a bot that you must create. You can get it from the Telegram BotFather. See the [obtain your bot token](https://core.telegram.org/bots/tutorial#obtain-your-bot-token) section.
2525
- User ID: this is your Telegram user ID. You can get it from the [userinfobot](https://t.me/userinfobot) typing `/start`.
2626

27+
:::warning
28+
You must start the conversation with the bot using `/start` so it can send you notifications.
29+
:::
30+
31+
:::info
32+
Once you setup your notifications, you will receive a test notification to confirm that everything is working properly.
33+
:::
34+
2735
Once your notifications are setup, you will receive notificatios for the following events:
2836

2937
- Lido Smart Contract events:

docs/user/staking/ethereum/lsd-pools/lido/register.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -68,4 +68,8 @@ Do not edit the fee recipient address. Doing so will result in penalties.
6868
- Introduce your bot token and user ID and confirm
6969
- You should receive a confirmation message from the bot.
7070

71+
:::warning
72+
You must start the conversation with the bot using `/start` so it can send you notifications.
73+
:::
74+
7175
![lido-notifications-onboarding](/img/lido-notifications-onboarding.png)

0 commit comments

Comments
 (0)