Back to motions
Treasury Proposal#109 >> Council Motion#351
Executed

#351 Proposal: Kusama RPC-node Dwellir

Proposer:
GLVe...F7wj
 
in Treasury
10th Sep '21

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.

Our full proposal can be read here.

  • 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.
  • KSM rate base onf 30 day avg tool by Subscan: Available HERE

Show More

Council Votes

Gvyf...gjKX
Aye
DWUA...TJ1j
Aye
DMF8...MSXU
Aye
H9eS...Em7y
Aye
Gth5...s5m5
Aye
DaCS...Liax
Aye
JKoS...GNC3
Aye
Hjui...vtis
Aye
J9nD...8yuK
Aye
Hh6r...8BmL
Aye
Please Log In to comment

2Comments
JLJ6...VAT9
 
 
8th Dec '21

Here is our report on Milestone 1 and Milestone 2 from this last quarter.

In summary: We successfully delivered on Milestone 1, and then we struggled with Milestone 2 for several weeks. But in the end we made the RPC-service work for the community. Please read more in the report.


Discover similar proposals


Empty Icon

No Active Proposals