Adding and promoting brenzi to rank I

Fellows
1yr ago
1 Comments
Executed

Brenzi is working mainly on Encointer, a system parachain on Kusama. He has written a document outlining the contributions he has done over the years: https://hackmd.io/@brenzi5/SyEQidXan

Given his contributions and the future inclusion of encointer into the fellowship runtimes repo, I'm supporting him in joining and directly promoting him to rank I for now.

Reply
Up
Share
Status
Decision7d
Confirmation30mins
Attempts
1
Tally
100%Aye
87.9%Threshold
0%Nay
Aye36
Nay0
  • 0.0%
  • 0.0%
  • 0.0%

Threshold

Bare Aye8
Max Voters17
All Votes
Calls
  • Call
  • Metadata
  • Timeline6
Comments

Kusama Auctions: Third time’s a charm - STEP 1

Kusama auctions are scheduled using the Scheduler Pallet, and the recurring functionality that this brings. The recurrence of this pallet offers two options: every how many blocks this recurrent should be executed, and how many times. Unfortunately, Ref 72 and Ref 81 have been misconfigured and the two parameters on the scheduler pallet have been passed in the wrong way: For example, the first scheduler call will not create 2 auctions every 100_800 blocks, but rather 100_800 auctions every two blocks.

Solution: both Ref 72 and Ref 81 will have to be cancelled and re-submitted on-chain.

For this, we will work on 3 proposals:

  1. Whitelisted caller track proposal cancelling scheduled auctions + ref81;
  2. Auction admin track proposal for the first auction on Ref81: this will give us one more week to vote on the third proposal;
  3. Root track proposal for all auctions in ref72 + the last auction batch of ref81.

The first proposal on the list is now submitted as referendum 85 - this aims to cancel all scheduled auctions that are incorrect on scheduler and ref81: up for vote on Root track now. The reason why we are cancelling this last one is due to the fact the same mistake was made on submission.

Please note a Fellowship proposal is also needed to whitelist this proposal hash to make sure the proposal executes successfully. The Fellowship proposal is now up for vote as proposal 23! Please make sure to vote at your convenience!

Reply
Up