Most clients that need to connect to the Kusama network are dependent on RPC nodes to interact with the network. Should the set of existing registered RPC nodes be unavailable, many users will not be able to access the Kusama chain.

This proposal is about funding further development of the RPC service and to cover the maintenance costs of it. The specific development is about **deployment automation** (JuJu Charm) and using multiple **DNS registrars**. 

We have already submitted a Pull Request for our RPC service, it can be [found here](https://github.com/polkadot-js/apps/pull/6024).

Our full proposal can be [read here](https://docs.google.com/document/d/1Em6VqE0KUDfMF_o370yJXk98UVDNr7Ao4IvpU7reAnE/edit?usp=sharing).

- This proposal covers M1 improvements for the running RPC nodes and the first 3 months for maintenance while working on improvements. 
- PR to merge RPC Nodes service to Polkadot.js Apps can be found [HERE](https://github.com/polkadot-js/apps/pull/6024).
- KSM rate base onf 30 day avg tool by Subscan: Available [HERE](https://kusama.subscan.io/tools/charts?type=price) 

Problem Statement:
- Many clients depend on RPC nodes to connect to the Kusama network, and if these nodes are unavailable, users cannot access the network.

Significance:
- Funding is needed to further develop and maintain the RPC service, including deployment automation and the use of multiple DNS registrars.

Proposed Solution:
- Develop deployment automation (JuJu Charm) and utilize multiple DNS registrars for the RPC service.

Expected Outcomes:
- Improvement of running RPC nodes and maintenance for the first 3 months.
- Merge of RPC Nodes service to Polkadot.js Apps.
- Kusama rate based on a 30-day average tool by Subscan.

#109 Proposal: Kusama RPC-node Dwellir

No Active Proposals