Bifrost Fellowship

Bifrost fellowship

In reference to the Polkadot Technical Fellowship,

“Fellowship is a self-governing body of experts and developers of Polkadot, Kusama and Parachain protocols. It operates on-chain through fellowship referenda and off-chain through the community discussion repository.”

The Bifrost Fellowship aims to promote the long-term development and growth of the Bifrost Protocol. As such, its members encompass a diverse range of expertise. This includes not only developers with technical skills but also founders of other DeFi protocols, web3 researchers, professional node operators, and ecosystem contributors, and partners. This is essential to ensuring the quality of Bifrost Governance and fostering the protocol's development and longevity.

Fellowship Referenda

The fellowship's governance model has multiple tracks, each with its own approval and support parameters, where votes are weighted according to their ranks. Members of the Fellowship can vote on any given proposal, and the aggregated vote of all members (weighted by their rank) constitute the Fellowship's collective vote.

The list of current and historic fellowship referendas can be viewed on our Subsquare.

Gov Origin of Customized Modules on Bifrost

For some modules that Bifrost has self-developed and do not involve protocol security risks, Fellowship members have the origin to directly execute the corresponding methods through Fellowship Referenda according to their rank.

Specific module calling permissions and corresponding methods can be viewed at: Runtime Extrinsics origin.


Polkadot OpenGov allows the Technical Fellowship to authorize an origin known as "Whitelisted-Caller" to execute with Root-level privileges for calls approved by the Fellowship (currently only level-three fellows and above can vote for whitelist calls). Note that the fellowship cannot unanimously change the network parameters, conduct rescues or move assets. The whitelisted proposals still have to go through the whole life cycle of an OpenGov referendum and can only be enacted when the referendum passes successfully.

The whitelisting process starts as a fellowship referenda with embedded XCM call from the collectives system chain to the Polkadot relay chain. For instance, the Bifrost Fellowship referenda 14 was used to whitelist the Bifrost OpenGov referenda 14.

Membership Management

Bifrost has the exact same membership management model as the Polkadot Fellowship. The Fellowship was initially seeded with its members and their corresponding ranks. All new membership requests will go through the fellowship governance and the procedure is outlined in the section below.

Fellowship Member Responsibilities

Technical members are defined as members who have experience with Substrate coding or Runtime construction of function calls. Non-technical members are defined as members who experts accross DeFi player, Web3 researcher, former governance member and etc. The key is who has sense on helping with Bifrost growing by advising with their prior experiences.

Technical Members

  • Review, initiate, and vote on Whitelisting proposals

  • Initiate technical proposals such as protocol-related runtime upgrades and parameter modifications

  • Handling of issues that need to be fixed urgently

  • Review all preimages with proposals

  • Remind or reject all proposals that have no proposal content

  • Promote new members

Non-technical members

  • Review and vote on Whitelisting proposals

  • Handling of issues that need to be fixed urgently

  • Propose a constructive discussion that will benefit the development of the protocol

  • Participate in the discussion of the proposal

  • Remind or reject all proposals that have no proposal content

  • Promote new members

Rank Updates

Bifrost has the exact same Rank Updates logic as Polkadot Fellowship:

  1. Any fellowship member up to rank 4 can be promoted to the next rank through a fellowship referenda that can be voted by the members who are rank 2 or higher. For instance, the fellowship referenda 64 which promotes a member from rank 1 to rank 2 can only be voted by members whose ranks are greater than or equal to 3.

  2. Promotion of the Polkadot Fellowship members from rank 5 needs to be done through an OpenGov referendum. For more information, check the rank updates section on the fellowship dashboard.

Application for Fellowship Membership

Anyone (including individuals and/or entities) interested in participating as a candidate in the Bifrost Fellowship is encouraged to inform the community of their plans to run on the discussion forum, by:

Phase 1: Self introduction - At any time

  • Background of your motivation for Fellowship membership application.

  • As a Fellowship member, how do you think you can help Bifrost grow, and what are some aspects that Bifrost needs to improve?

  • Your individual/entity background, experience and why the community & fellowship members should vote for you? (Provide your governance experience, with on-chain or off-chain proves.)

Phase 2: Discussion and evaluation by community & Fellowship - 7-14 days

During this phase, the Fellowship will mainly lead the evaluation and engagement process.This phase normally takes 7-14 days, includes time for the Fellowship to discuss internally and finalize a conclusion. Following this, the Candidate can decide whether or not to post the formal proposal on-chain in the next phase.

Phase 3: Initiate on-chain proposal - dynamic voting time

After considering the Fellowship’s suggestion in the previous phase, candidates can ask the Fellowship or self-posting the on-chain proposal, and it will start on chain referedum.

Last updated