Scaling up our efforts on Kusama Network: The Kusama Dev Team

4yrs ago
4 Comments

Kusama Network should focus most of its resources on encouraging experimentation with the technologies developed by Parity, the Web 3 Foundation and the community of Substrate developers. At the moment, developers are a scarce resource on a rapidly changing network like Kusama.

In order to scale and develop new ideas for the Network, we are searching for developers that are interested in joining our cause. The group, called "The Kusama Devs Team" should be interested in working on valuable projects, as directed by the Council and guided by part of it, in the form of a bounty or any other set up to be confirmed, treating these at first as side projects in exchange of KSM rewards.

The plan envisioned involves two steps:

A. Start a call for those who want to join, form the group with the first developers and start right away with the ideas to scale on feature tasks and show differentiation of Kusama Network. The first projects we plan to set up for work are:

  1. an implementation of a data feed to be potentially added to Kusama runtime (in process - more to be shared soon),

  2. Kusama Supreme Oracle project,

  3. Recurring Payments Mechanism.

B. The second part of the process is to set up a "Kusama Social Security Program" for those joining the team. Besides the KSM rewards for working on new features received by developers who join the group, the developers will receive on specific accounts an X amount locked in KSM on a periodic basis as a recognition for being part of the team.

These tokens, locked for a specific period of time to be defined, will be able to be used once certain conditions are met, can be a specific time, specific number of tasks developed, voting by the Council or by part of the team.

On the idea of a Kusama Social Security Program:

  • This small ongoing payment to accounts can be stopped at any time by the Council or if that account stops taking bounties it would probably not be spendable, but rather a reserved balance to be unlocked after certain conditions are met.
  • When developers leave on certain terms, the account would get unlocked. These could also be unlocked after a period of time has passed: maybe monthly, so it functions almost as a kind of "sick pay" mechanism.
  • For those developers who prefer a more stable, employee-like job relationship, this program might give them the security they need under certain terms.

We are eager to hear your input on these ideas to work on a first iteration of the second point. The team is already forming and we are looking forward to count with Kusama Dev force to help us bring Kusama further.

Up
Comments
No comments here