candidates

members

proficients

fellows

senior_fellows

experts

senior_experts

masters

senior_masters

grand_masters

Origin commanded by any members of the Polkadot Fellowship (no Dan grade needed)

Origin commanded by rank 1 of the Polkadot Fellowship and with a success of 1

Origin commanded by rank 2 of the Polkadot Fellowship and with a success of 2

Origin commanded by Polkadot Fellows (3rd Dan fellows or greater)

Origin commanded by rank 4 of the Polkadot Fellowship and with a success of 4

Origin commanded by Polkadot Experts (5th Dan fellows or greater)

Origin commanded by rank 6 of the Polkadot Fellowship and with a success of 6

Origin commanded by Polkadot Masters (7th Dan fellows of greater)

Origin commanded by rank 8 of the Polkadot Fellowship and with a success of 8

Origin commanded by rank 9 of the Polkadot Fellowship and with a success of 9

- The proposal has three main goals for farming adjustments.
- It plans to move 45,730 BNC from the Treasury to the Bifrost Foundation.
- It will edit pools to change how rewards are given out.
- It will send Treasury funds to charge BLP rewards to stable pools.
- Different pools like vBNC/BNC and vDOT/DOT will have their BNC and BLP amounts adjusted.
- The total BNC to be moved is 45,730.
- The changes aim to make farming rewards fair and stable.

Rejected

Farming Adjustments and Charge - Jan-Feb

- There was a bug in the channel-commission pallet.
- The bug stopped users from getting their commissions.
- The bug is fixed now.
- The sovereign account needs more tokens for users to claim commissions.
- A proposal suggests adding tokens equal to the total amount users can withdraw.
- This will help users get their commissions without problems.

Executed

[Fellows] Referendum #215-Proposal to Replenish Channel-Commission Sovereign Account

Initialize bbBNC revenue flow

- Bifrost Polkadot Runtime is a big file, 2.277 MB in size.
- It is compressed to save space.
- The metadata version is V14.
- The core version is bifrost_polkadot-16001.
- It has special codes called hashes for different actions.
- You can find it on IPFS with a special link.
- Many updates were made, like changing how commissions are calculated.
- Dependencies were updated to make it work better.

Upgrade Bifrost-polkadot to Runtime 0.16.1

- A plan to create trading pairs for vToken and BNC to help with future BNC buybacks.
- Four trading pairs will be made: vDOT-BNC, vGLMR-BNC, vASTR-BNC, and vMANTA-BNC.
- Liquidity will be added to each pair using funds from the Bifrost treasury.
- The amounts for each pair are:
  - vDOT-BNC: 2,397.18 vDOT and 95,687.435 BNC.
  - vGLMR-BNC: 301.1 vGLMR and 361.32 BNC.
  - vASTR-BNC: 13,994.73 vASTR and 4,121.447985 BNC.
  - vMANTA-BNC: 3,849.9 vMANTA and 16,041.25 BNC.

Proposal: Create vToken-BNC trading pair and add liquidity to Bifrost Swap

Add Sonus Exchange in RSP

- Bifrost Polkadot Runtime is a big file (2.281 MB) and is compressed.
- It has a special code called "Metadata version V14."
- Many updates were made to improve how things work, like moving from version 1 to version 2 in different parts.
- Some changes include fixing bugs, adding new features, and making things faster.
- The team also worked on making sure the system pays out rewards automatically.
- They updated the system to use native tokens for gas fees in EVM.
- The full list of changes can be found on GitHub.

Upgrade Bifrost-polkadot to Runtime 0.16.0

Repair BNCS cross-chain

Set delegatorActiveStakingMaximum

- The Kusama chain has a total account balance of 80,763,731,286,926,555,647, with an excess of 763,731,286,926,555,647.
- The Polkadot chain has a total account balance of 79,999,995,154,039,829,347, with a decrease of 4,845,960,170,653.
- The cross-chain governance bridge totals 80,000,000,923,080,910,000, with an excess of 923,080,910,000.
- Excluding the bridge, the total is 80,763,725,517,885,474,994, with an excess of 763,725,517,885,474,994.
- To fix the totals:
  - Decrease Kusama's special address and treasury.
  - Increase Polkadot's treasury.
  - Adjust both chains' cross-chain governance bridges.
- After adjustments, both chains and the bridge will have totals of 80,000,000,000,000,000,000.

TotalIssuance Fix Step 2

TotalIssuance Fix Step 1

Configure cross-chain transaction fees related to the vTokenVoting method

**Summary**

- The proposal updates minting shares for RSP members whose vToken shares were not updated due to recent vToken redemptions.
- It includes data for vDOT and vMANTA shares across different channels.
- Channels like Talisman, Staking Reward, Subscan, and Subsquare have specific vDOT and vMANTA percentages and permill values.
- The total issuance for vDOT is 4,799,847.06, and for vMANTA is 6,263,658.21.
- This update ensures accurate distribution of shares after the surge in redemptions.

Set RSP Minting Shares

### Bifrost Polkadot Runtime
- Runtime size: 2.259 MB (large)
- Compressed: Yes, 76.81% smaller
- Metadata version: V14
- Core version: bifrost_polkadot-15003
- Changes include adjusting vtoken voting storage
- Full changelog: [bifrost-v0.15.2 to bifrost-v0.15.3](https://github.com/bifrost-io/bifrost/compare/bifrost-v0.15.2...bifrost-v0.15.3)

Upgrade Bifrost-polkadot to Runtime 0.15.3

Update vBNC in RSP Module

Register Kyo Finance in RSP

Fuel BNC Liquidty in CEXs

Top up vBNC-BNC by using migrated farming issuer

### Bifrost Polkadot Runtime
- **Runtime Size**: 2.257 MB (2,366,317 bytes)
- **Compressed**: Yes, 76.83%
- **Metadata Version**: V14
- **Core Version**: bifrost_polkadot-15002
- **IPFS Link**: [IPFS](https://www.ipfs.io/ipfs/QmU8Da9fR9LuV6gnxYH4D72nzdT8FTxe5sd6urFMsAfK2W)

### Recent Changes
- Separated logic for retrieving current block for different tokens.
- Fixed vtoken voting.

**Full Changelog**: [GitHub](https://github.com/bifrost-io/bifrost/compare/bifrost-v0.15.1...bifrost-v0.15.2)

Upgrade Bifrost-polkadot to Runtime 0.15.2

Create BNC/USDT LP + Farming

Create vBNC-BNC Farm, Request Incentive From Treasury

### Call Data Summary

- **Hexadecimal Data**: The provided data is a series of hexadecimal values.
- **Length**: The data consists of multiple 16-byte segments.
- **Structure**: Each segment starts with "0x4000" followed by a sequence of hexadecimal characters.
- **Purpose**: This type of data is often used in telecommunications or networking for encoding information.
- **Complexity**: The data is highly technical and would typically be interpreted by specialized software or hardware.
- **Example Segment**: One segment is "0x40008508742b00013c0001010028ea206ff421d348f50e0b8e8c3ccfed4a117f7c78c04b2e7be3f2c7e8fcaa40000101001a89383d87cc3147a6aad36f38005b4d4a793fdc7863934d5c44119f2d28de5100010100c83b0bba37f25f365e26efbe6c9ecfa7905dbdc0b0e3ae60b29980b42c509c6f00010100606b0aad375ae1715fbe6a07315136a8e9c1c84a91230f6a0c296c29535813350001010056895e148116ffe3390a47214d49496c7bb3578060c006ca4044b978b70db50100010100d2eb07f02043788e254d9e2df57be11566d241c56302b91199b4647947af302000010100b6ba81e73bd39203e006fc99cc1e41976745de2ea2007bf62ed7c9a48ccc5b1d00010100ce42cea2dd0d4ac87ccdd5f0f2e1010955467f5a37587cf6af8ee2b4ba781034000101005ecc1d4e60a92262c1bec62d034c979f42cbd3fb1c28570d5baed6e5ed20d53300010100acaf0dd9b394a13a94645f478b03bea77cf7615e879fccfda11c889d30e4d05f00010100a471c7aa909cc665212bb36003c52c5d3eeec39f96556a8242e861c5dd7dde4100010100a24a2f3c8775bd264d9b00195ad5345b88c6abc694c4d51ec5bb267452020d7000010100164ff8a4203cbc72e6b393abccd95384ad7dbe59712342e63e569509d64c887800010100749e69d5dd17b0b54f904c80ad768a036586f125e9e92ea6ff15b099a76f1102000101005c7e9ccd1045cac7f8c5c77a79c87f44019d1dda4f5032713bda89c5d73cb36b".
- **Interpretation**: Without specific context, the data's exact meaning is unclear, but it likely represents encoded information such as network packets, sensor data, or system logs.

Fellowship Referenda