Call for Proposal: Fix Vault & Staking Reward Distribution After Runtime Upgrade


Each year there are calls scheduled for the rewards assigned for that year on Kintsugi for vaults and staking (the scheduled distribution of yearly rewards). These, however, need to be adjusted as in the current state they will no longer work. This is due to the change of runtime indices.


Why will the scheduled (CURRENT) distribution no longer work?
The call for this scheduled distribution relies on the runtime indices. Since these have been changed, the current out of date call will fail.
Background: reward distribution is encoded as a set of future calls (think transfers of the amounts described in the whitepaper)
Problem: we made a breaking change to the runtime, invalidating these calls (the pallets they refer to no longer exist or are in the wrong order)
Impact: Kintsugi: vault & staking rewards
Proposed solution: clear storage and re-propose all rewards from year 2 - year 4

How to fix this?

In order to fix this before the time comes when the reward distribution is called, a proposal needs to be made that clears storage and re-proposes all rewards from year 2 to year 4.

The amounts that will be used in the new scheduled calls for staking rewards are the same as specified in the initial staking rewards referendum accepted in the past:

The amounts that will be used in the new scheduled calls for vault rewards are the same as specified in the initial vault rewards referendum accepted in the past:

What to do now/next?

Any member of the community can submit this proposal by following the steps provided below and afterwards editing and adding the relevant information in the newly created proposal.

Recommended steps:

  1. Click on the link and submit the preimage using a wallet with sufficient vKINT - Submit preimage and create proposal
  2. Go to and login with the same wallet used to submit the proposal
  3. Check proposals and you should see an untitled one. Hit edit and add a title and text. Feel free to use the text form this discussion post and any links to provide context.
  4. Feel free to promote the proposal and share with the Interlay team on the official discord channel.

Proposal encode hash:

0x0202200007803db7a24cfdc9de785974746c14a99df91643f5419718219c95679ddd2d825574000000000007803db7a24cfdc9de785974746c14a99df9891ad457bf4da54990fa84a2acb148a20000000004005d413100003f0002020815036d6f646c6d6f642f7375706c00000000000000000000000000000000000000006d6f646c6573632f616e6e750000000000000000000000000000000000000000000c130080ec74d616bc011f010400fd5a5900003f0002020815036d6f646c6d6f642f7375706c00000000000000000000000000000000000000006d6f646c6573632f616e6e750000000000000000000000000000000000000000000c130080ec74d616bc011f0104009d748100003f0002020815036d6f646c6d6f642f7375706c00000000000000000000000000000000000000006d6f646c6573632f616e6e750000000000000000000000000000000000000000000c130080ec74d616bc011f01040085c13100003f0002020815036d6f646c6d6f642f7375706c00000000000000000000000000000000000000006d6f646c766c742f616e6e750000000000000000000000000000000000000000000c130000da493b717d0c2801040025db5900003f0002020815036d6f646c6d6f642f7375706c00000000000000000000000000000000000000006d6f646c766c742f616e6e750000000000000000000000000000000000000000000c1300003c31d2a0530828010400c5f48100003f0002020815036d6f646c6d6f642f7375706c00000000000000000000000000000000000000006d6f646c766c742f616e6e750000000000000000000000000000000000000000000c1300009e1869d029042801 ```

**Proposal Hash:**
``` 0x4da4c49267b4806e8929e378b2a7a7a67ff1229d298a83117d5f82ecfaad0d0a ```

Interlay/Kuntsugi 101: 
Kintsugi token economy:
Vault docs: 
There are no comments here