Open-Sourcing the Kin Rewards Engine

Code behind the Kin Rewards Engine is now publicly available

Kik Engineering
Kin Blog
2 min readJun 30, 2020

--

The core pieces of the Kin Rewards Engine (KRE) payout code are now open-source. To have a look, visit the public repository.

For the KRE to continue to evolve and scale, it is important that the KRE payout process becomes increasingly decentralized and autonomous. Since the introduction of Kin Rewards Engine, we at Kik Inc have administered KRE payments under a service contract with the Kin Foundation. In November of 2019, the Kin Rewards Engine logic and spend guidelines were officially opened up to public contribution. Since then, members of the community have played an increasingly larger role; putting forth proposals, filing issues and discussing important economic topics. This process has been very successful with 40 issues being raised for discussion, which resulted in 3 Transaction Guidelines revisions, and 4 updates to the KRE logic. Dozens of community members have contributed directly (or indirectly via discussion) to these updates.

While the logic of the KRE has long been open-sourced and ecosystem participants are now able to see how they are doing in the KRE, the underlying code driving this payout process has not been publicly available. Today we are taking the next step by open-sourcing the core KRE code. Anyone in the community will be able to see the code, compare it to the KRE logic and raise issues as appropriate. Over the coming months, we will continue to add to this repository. Our goal is to have the resources available for anyone to be able to recreate the KRE payouts using publicly available code.

Open sourcing the KRE code is a critical next step in moving to a decentralized and more autonomous payout process. Once this is complete, we plan to work on decentralizing the payout process itself. Other community members are already offering great ideas on how this can be done. We look forward to working together with the Kin Foundation and the rest of the Kin Ecosystem on this problem.

--

--