Dear community,

I present to you [a proposal](https://docs.google.com/document/d/1us8glHDEaXeqNp0Ex8Z5sffy4GTfhrvHzGNzNvp-juw/edit) which aims to develop a technical solution to: 

- Monitor and report on the uptime, performance and integrity of public WSS (RPC) relay-chain endpoints. The data could be used to guide funding of said services, to encourage a service standard or to provide existing providers with a second take on key metrics from a third-party.
- Monitor and trend database growth rates for twenty-four database configurations. This is something that I started and self-funded > 16 months ago. Upon launch it gained interest by technical parties and is now referenced within the Polkadot Wiki. I would like to expand on the project to include growth charts and offer a wider range of database configurations. Further to this, I intend to monitor the restoration times of some of the more popular database configurations.

Additional: Providing that the original scope is met, I'll consider monitoring of database bloat, trend average RAM or CPU usage as well as monitor availability and integrity of bootnodes.

Both major items are not found within any existing public resources and are in my opinion well aligned to Kusama's experimental nature. Full details including budget details can be found in [the proposal document](https://docs.google.com/document/d/1us8glHDEaXeqNp0Ex8Z5sffy4GTfhrvHzGNzNvp-juw/edit). This document was circulated to members of the 1KV/IBP for a week and was open for [public discussion](https://kusama.polkassembly.io/post/2546) for > 2 weeks.

 
Disclosure: As it relates to WSS monitoring, I am presently employed by LuckyFriday which as of last week is now listed as a public RPC provider. I also share good professional relationships with most of the RPC providers. The proposed solution is open sourced such that anyone can operate in-tandem and compare/challenge results. Once up and running these `audits` will be operated and presented without any human intervention. 
 

Kind Regards, 
Will | Paradox

Propose and approve a spend of treasury funds.

- `origin`: Must be `SpendOrigin` with the `Success` value being at least `amount`.
- `amount`: The amount to be transferred from the treasury to the `beneficiary`.
- `beneficiary`: The destination account for the transfer.

NOTE: For record-keeping purposes, the proposer is deemed to be equivalent to the
beneficiary.

- The proposal is about developing a technical solution to monitor and report on the performance of public WSS relay-chain endpoints and database growth rates.
- The proposal aims to provide funding and encourage a service standard for these services.
- The proposal also includes monitoring the restoration times of popular database configurations.
- The proposal is open sourced and anyone can compare and challenge the results.
- The proposal has been discussed by the community for over two weeks.

#175 Proposal for Monitoring of public RPC/WSS Endpoints & Node Database Analytics

No Active Proposals