Grant of SSV.Network monitoring system

Summary of Proposal

Background: The demand for status monitoring is surging as the main network is set to sail. Reminders of the changes in the validator accounts are becoming widely anticipated.

In order to optimize the user experience of the verifiers and operators, we propose to build a system that monitors the nodes of operators and validators, and enables users to subscribe and receive reminders in time, to avoid the loss of Ethereum as much as possible.

Motivation for Proposing

We hope that a monitoring system can serve its three stakeholders, Ethereum ecosystem, ssv network and the participants (Validators and Operators) in the following ways,

  • For the Ethereum ecosystem, the network remains stable during the Ethereum POS merge so that users can participate in the network smoothly and earn profit from staking.
  • For SSV. Network, we develop tools to better coordinate operators and verifiers to lubricate the implementation of the network.
  • For users (Verifiers and Operators), the system provides monitoring and notifications to ensure the service quality and stable return.

Proposal Details

The purpose of the SSV network monitoring system is to: 1. monitor and analyze operators’ status, help verifiers to select high performance operators; 2. monitor validator accounts, offer notification services to remind validators of insufficient balance.

Detailed planning is the following:

Stage 1 (0.5 months)

Feasibility testing, technology selection, community survey, product and UI designs. The technical architecture is the demonstrated below:

Stage 2 (1.5 months)

Front and rear end development, entire platform finalized

  • Real time synchronization of operator status and account data
  • Rule engine selection or self implementation
  • Notification service development
  • API server development
  • Front end development

Data monitored by the system will include (but may not be limited to):

  • Account operational runway (balance)
  • Account liquidations
  • Operators fee changes (increase/decrease)
  • Operators status changes (active/inactive/removed)
  • Operators performance (increase/decrease)

Consider the actual demand, additional features and automations may become available. For example, valiators subscribe to the reminders of related operators by default.

Stage 3 (0.5 months)

Beta version for community testing, modify, improve and open source to the community…

Timeline and Budget

The first stage (0.5 months): feasibility test, technology selection, product, and UI design

The second stage (1.5 months): the development and implementation of the system

The third stage (0.5 months): Launch community test, open source to the community

Staffing: one product manager, one UI / UX engineer, one front-end engineer, one back-end engineer, and one operation & maintenance engineer;

Development : Hellman officially starts the development work as soon as the proposal is confirmed;

Cost: US $25000, acceptable to SSV / USDT / USDC, 50% SSV and 50% stable cryptocurrency;

Payment: 50% after the completion of the second stage;Payment of the remaining 50% upon completion of the third phase.


Hellman is a Web 3 research institute extensively focusing on Ethereum, Layer 2, NFT, DAO, and actively involved in the infrastructure development of POS projects. With rich experience in PoW and PoS pools, such as Filecoin and Swarm, Hellman is now actively engaged in the community.

Core members


6 years of experience in full stack development. Used to work at Hello Bike Inc., Eleme Inc. and Wind Information Co., Ltd. Proficient in Python and VUE.


Back-end engineer with more than 3 years of blockchain development expertise and server operation experience. Familiar with the technical architecture of the mainstream chains.


Marketing and research analyst, alumnus of BTCchina. Superior research capability in blockchain consensus and token economy.

Social media and other contributions

Please comment! :grinning:


Great initiative!
Is it a single operator/ account type of monitoring? Or would I be able to say monitor multiple nodes at the same time?

In fact, users can monitor and subscribe to all the nodes they care about, that means technically there is no limit.

But for safety reasons and to avoid abuse, we will set a larger upper limit to satisfy more people.

1 Like