Should Gnosis DAO fund the continuation of the validator Monitoring Telegram bot?

GIP-Draft: {title}

  • In Favour
  • Against
0 voters
GIP: <to be assigned>
title: Should Gnosis DAO fund the continuation of the validator Monitoring Telegram bot?
author: Nicolás Domínguez (nicolas@bootnode.dev), Manuel García (manu@bootnode.dev)
status: Draft
type: Funding
created: 2024-04-11
duration: 6 months
funding: 43,000 USDC + 400 GNO

TL;DR

This is a proposal by bootnode.dev to continue the conversation about the Gnosis Chain validator monitoring bot that we developed earlier this year.

Introduction

The Telegram bot functions as a monitoring tool, notifying the user of any issues and providing continuous updates on validators’ performance.

Featuring

  • Setup: requires just withdrawal addresses, and retrieves all their validators.
  • Dashboard: gives all important info in a small message automatically updated in real time.
  • Stats Updates
  • Automated Notifications: for performance < 90%, status change (active/inactive), slashing
  • Subsidized Claim

Link to set up the bot: Telegram: Contact @gbc_validators_bot

We have shipped the first version. KPIs (as of April 9, 2024):

  • Users: 67
  • Total registered validators: 56056 (~ 30% of the total Gnosis Chain 199512 active validators)
  • Validators under active monitoring: 6038 (we can only monitor 200 validators per user due to resource constraints)
  • Claimed Rewards: 100+ subsidized claims through our bot using a very convenient ‘/claim’ Telegram command (https://gnosisscan.io/txs?a=0x9683693f8164b4f8c6d804e690ac2c26f8fe56ed)

We are seeking funding to invest in building improvements. Additionally, we are applying for retroactive funding as significant work and infrastructure resources have already been invested in the solution that benefited the Gnosis community.

Motivation

We were not quite satisfied with the existing validator monitoring solutions for the following reasons.

  1. Gnosischa.in Free plan only allows monitoring up to 100 validators per account.
  2. Gnosischa.in Max paid plan (21 euro) allows monitoring up to 280 validators per account, and we (along with other community members) have more.
  3. Existing onboarding experience, including registering validators and configuring monitoring, was too complex and may deter less sophisticated users from trying.
  4. We wanted a simple dashboard with the most essential parameters, relevant notifications, and a simple way to claim rewards.
  5. We wanted to receive notifications per set of validators instead of individual validator identifiers.
  6. We didn’t want to use a native app or email. We wanted to start with a straightforward Telegram bot.
  7. We wished we had this for us, so we built the existing Prototype.
  8. We want to Open Source it.

Current monitoring tools

beaconcha.in is an excellent tool that works well for monitoring validators on the Ethereum chain. However, for Gnosis Chain, this tool is less optimal than for Ethereum. For instance, missing one attestation in Gnosis Chain, where blocks occur much faster than in Ethereum, may be less critical. We notify the operator if the validator only misses 4 or 5 attestations in a row (a feature validated with our beta testers). Another example is the absence of a method to load all validators from a withdrawal key. This limitation arises because, generally, users only have a few validators on Ethereum, which is NOT the case for Gnosis Chain.

Lastly, the most significant issue that Gnosis Chain validators face is the price of monitoring tools such as gnosischa.in service. For validating more than 100 validators, up to 280, the price is 21€ per month. This pricing structure appears unreasonable as it costs approximately 4% to 10% of a validator’s revenue to monitor 100 to 280 validators at USD300/GNO. Not even considering the operational expenses (infra, devops, bandwidth, etc).

Our solution

A Telegram bot that functions as a monitoring tool, notifying the user of any issue and providing continuous updates on the performance of their validators.

Here is the X Post announcing its beta access launch.

We have been testing the bot over the past month, and it has performed way better than expected. The bot currently utilizes the beaconcha.in API. It periodically polls requests for all validators added by users and delivers relevant statistics.

You can already test the bot: Telegram: Contact @gbc_validators_bot. The following is a screenshot of the stats provided by the bot a few days ago.

Features

Users/Operators will:

  • Connect the Telegram bot and execute the command /load_validators followed by a withdrawal address. This command can be invoked multiple times if the user has more than one withdrawal address.
  • Receive notifications when a validator misses several attestations in a row, or their overall performance falls below 90%.
  • Get updates on validator status changes such as being down, up, slashed, or exited.
  • Convenient Dashboard that showcases Total balance, Rewards stats: 1d, 7d, and 31d, Claimable rewards, as shown above.
  • Claim rewards directly from TG (subsidized).

Roadmap

After testing the bot with real validators, we received valuable feedback from the support channel Telegram: Contact @GBC_validators_bot_support. Consequently, we plan to add and improve features and increase infrastructure resources to open the bot for all Gnosis Chain validators (~200k).

For this reason, we have devised a plan to make this bot free and accessible to everyone. Below is the Roadmap for how we will make it happen:

  • Milestone 0: Already delivered

    • The bot has already been deployed and is open for anyone to join. The only temporary limitation is the number of validators that can be loaded per Telegram account (200).
  • Milestone 1: In-progress

    • The bot has been running in a testing phase for the last two months. During this time, we have collected the following feedback from different users that we plan to address:
      • Reduce alerting frequency when something goes wrong with a validator.
      • Enable tracking of xDai rewards.
      • Calculate effective APY.
      • Improve performance.
      • Improve UX for interactions such as loading validators, creating a command to check if new validators have been added for an account, specifying AM or PM for some dates, and others.
    • Open Source it.

    Timeline: 1 month.

  • Milestone 2: not-started

    • API adjustments: We will adjust the number of validators users can track while avoiding exceeding the monthly request quota.
    • Validators onboarding: Step-by-step instructions, documentation, generate a bot ”brand” identity including website with basic information about the bot’s purpose and how to interact with it.
    • Notifications (under evaluation): allow the community manager (e.g.: https://twitter.com/0xarmagan) to push notifications through the bot, like important upcoming node upgrades, links to the weekly report, etc.
    • Historical rewards per month. We can save them to the DB to facilitate tax returns.
    • Make the source code open source.

    Timeline: 1 month.

  • Milestone 3: not-started
    Our current API provider might not be the best solution due to its cost and restrictions, preventing us from scaling and minimizing the cost of monitoring/validator. We are exploring different options to offer an unrestricted service to all Gnosis validators and to provide real-time notifications. We’ve discussed this with community members like @dapplion, who recommended looking into the Dora project (a simplified version of a fork of beaconcha.in). After a thorough review, we found Dora to be a good starting point but only partially suited to our needs. To gather all the information our bot needs, we’re considering adding specific features from the beaconcha.in codebase. Other ideas involve hosting gnosischa.in Open Source stack in our infrastructure or finding an infrastructure partner (eg, those running RPCs/Nodes for Gnosis Chain). This topic requires more research.
    The result of this research will be our team’s analysis, outlining each strategy’s advantages and disadvantages. We plan to develop a proposal for the DAO aimed at securing a long-term commitment that will enable us to keep the bot open and unlimited for the entire Gnosis chain validators community.

    Timeline: 1 month.

Note:

We are aware that Pectra is optimistically aimed to arrive at the end of year. EIP-7251 will allow stakers to consolidate way more than 1 GNO into each index, up to 64 GNO. It will allow small stakers to reduce costs and make the network participation rates higher and more stable. We will have a better assessment much earlier than that on what the best solution would be from our point of view.

Benefits for the community/DAO

  1. Reduces monitoring costs for all Gnosis Chain validators, increasing performance and profitability.
  2. Simplifies validator monitoring setup, improving operator satisfaction.
  3. Built by an active validator, hence providing the most relevant features, stats, and user experience.
  4. It will be continuously supported by BootNode going forward.
  5. It is a fundamental tool for anyone running validators, and it is free to use. One of the goals of the Gnosis Chain is to be as decentralized as possible, and that won’t be possible without the appropriate tooling and low expenses.

Funding

  • Retroactive

    • Prototype Research and Development: a team has dedicated several weeks to perform the required R&D to spec out and build the initial version.
    • The initial version has already been used by 67 operators, even though there is a cap of 200 validators per account, which proves its relevance and need.
    • Official Node Management documentation was updated to include bot setup instructions (Monitoring Validators | Gnosis Chain)
    • Infrastructure (USDC 1288.72):
  • Future Development

    • Detailed in milestones 1 to 3.
  • Operation and Maintenance: 6 months, including the following costs and tasks:

    1. Gnosis Beacon Chain API plan.
    2. Infrastructure costs, monitoring, and operation.
    3. Support to validators by our team in the bot Support Telegram channel.
    4. Bug fixing, development, and maintenance.
    5. Pull Requests review and merge pipeline.

Funds requested:

  • USDC: 43,000 that already includes retroactive funding for the delivered prototype
  • GNO: 400 (lockup and running validators for 6 months).

Progress status

  • Monthly progress reports in the forum.
  • Participation in the community calls.
  • Frequent posts in X.

Gnosis Snapshot

Phase 2 Proposals: Please ignore this section, and leave as is. It is used for Phase 3 proposals.
Phase 3 Proposals: Add a link to the corresponding Gnosis Snapshot poll you’ve created.

6 Likes

thanks for this, I enjoy the bot very much! What I am not sure about is the resources needed: If it will run long term without the need of gnosischa.in api the price tag seems very reasonable to me (compared to GIP-74) and I will be glad to substitute this although we might need some other metrics for the whole chain if gnosischa.in will eventually stop and further maintenance can be payed by rewards from the 400 GNO;-)

Hey guys,

Usually I’m not one to go into the DAO processes, but I find this proposal a bit preposterous, trying to tap into the Dao Extractable Value and I’m worried that due to the amazing work you’ve already done for Gnosis, things get confusing and this proposal passes. So I’d rather voice my opinion that just letting it pass.

I think the funding requested is insanely high for a Telegram bot, specially the $GNO ask… You are asking 140k USD in todays price, or a 0.013% of the total supply, which is… a lot.

If there is a need for this kind of project in the market, I’d rather see you guys testing it out there, finding the correct pricing, etc. than the DAO paying for it’s existence. There might be an idea of the DAO subsidizing freemiums for a couple of months, but that would also be, basically, pre-seeding / sponsoring a private project. Another option, could be paying the Retroactive grant, and making it open-source moving forward.

With that being said I think the bot is awesome and just great work overall. I just don’t agree it should be sponsored with 0.013% of the total supply.

EDITED: Original post said 0.13% instead of the correct 0.013% – My point still stands.

7 Likes

Totally agree, I really think it’s too much money for a Telegram bot

1 Like

Thanks @refri for the kind words as a real user.

we might need some other metrics for the whole chain”,

This is one of the features we plan to work on.

further maintenance can be payed by rewards from the 400 GNO;-)

It’d make total sense. The long-term backend/API solution will be determined as an outcome of Milestone 3.

Regarding rewards, we consider ourselves average operators, so our costs are not negligible. Our monthly profit from running 400 validators is ~ 2 GNOs.

Hello @ged!

You are asking 140k USD in todays price, or a 0.13% of the total supply, which is… a lot.

0.13% of the total supply is 3,900 GNO (total supply is 3m. GNO would be worth ~$35. Please don’t call it)

could be paying the Retroactive grant, and making it open-source moving forward.

Yes, the plan is to open-source it once we implement the feedback provided, some more features we have in the roadmap and pay some technical debt. Thanks for bringing that up, we missed that in the proposal.

3 Likes

Editting, sorry, fast typing lmao. 0.01%.

1 Like

I’ve already seen your work in a lot of gnosis groups and a lot of them are satisfied with your service and that’s a very good thing.

I don’t have a personal node yet so I can’t speak from personal experience but I also think, as in the other comments, that 400 GNO seems really high.

You say you’re going to lock them and run validators for 6 months, what are you going to do with the GNO after that? Selling them?

I think we should get more feedback from the community.

Thank you all for the feedback, it helped us to dig deeper into specific areas.

  • We have increased the long-term commitment from 6 to 12 months, including:
    • Maintenance (QA & development: bug fixes, changes in the network and other services, etc.).
    • Infrastructure and DevOps.
    • Support to users via a telegram channel.
    • GNO locked, providing decentralization and security by running validators.
    • Open Source: the plan is to open-source it once a few new features are built and some technical debt is paid (Milestone 2).**
  • Long-term incentives: the amount was revised and adjusted accordingly.

Revised terms:

  • Support and maintenance: from 6 to 12 months.
  • Funding request:
    • 50,000 USDC.
    • 250 GNO (exclusively dedicated to running validators for at least 1 year).

If you voted against the proposal, we invite you to revise the new terms and reconsider your vote.

Thank you for the feedback: @refri, @ged, @diegodefi and @CryptosNF.

Note: Unfortunately I could not edit the current proposal (yesterday I was able to do it). So I’m closing this one and creating a new proposal.

2 Likes

First of all Hi guys i know its been a while since last i posted or anything. Whole lot of family stuff happening. Mainly surroundibg ze house/condo here in SOCAL. All is reasonably ok. Having said all that that I COMPLETELY AGREE WHOLEHEARTEDLY WITH THE SENTIMENT OF THE AUTHOR OF THIS POST.
I am planning on hosting 2 or 3 Gnosis Nodes, hopefully by the end of summer, funding contingent of course as with all things, i plan on utilizing DAPPNODEs premade Node architecture instead of building the blooming thing from scratch, just cheaper by my estimation. More to follow that is all.

Can someone explain what “…HOPR…” if I have the complete acronym right? I am computer savvy but in some areas I’m an idiot.