candidates

members

proficients

fellows

senior_fellows

experts

senior_experts

masters

senior_masters

grand_masters

root

whitelisted_caller

fellowship_admin

referendum_canceller

referendum_killer

liquid_staking

system_staking_admin

salp_admin

treasury_spend

delegated_voting_admin

Kill malicious referenda #322 and #329 via Whitelisted Caller

Upgrade Bifrost-polkadot to Runtime 0.27.0

Hyperbridge Asset Recovery — November 2026 Batch: Burn Remark-Bound vETH and MANTA for Equivalent Ethereum Distribution

Deposit bbBNC Rewards to Buyback Pool (Treasury-subsidized, 7th Batch)

Executed

Fellowship member adjustment

# DOT–vDOT Stable Swap Fee Reduction Proposal

## What is this?
This is a plan to make swapping between DOT and vDOT cheaper on Bifrost Polkadot.

## Key Facts
- It lowers the swap fee for Pool 0 from **0.30% to 0.05%**.
- The change applies to swaps in both directions (DOT to vDOT and vDOT to DOT).
- The fee drops by 25 basis points, about **83.33% less** than before.
- With a lower fee, Bifrost earns less per trade, but more people may trade.
- Only the swap fee changes. Other fees and settings stay the same.
- The new fee starts after the governance vote passes and is not applied to past trades.

Reduce the vDOT–DOT Stable Swap Fee to 0.05%

Fellowship member adjustments

# Bifrost Referendum to Cancel Two Malicious Proposals

- Two Bifrost governance proposals, #322 and #329, were reported as malicious.
- Both were submitted by the same account and had deposits paid by that account.
- This new proposal cancels both proposals and takes away their deposits, totaling 50,520 BNC.
- The taken deposits go to the Bifrost Treasury.
- The cancellation happens all at once: if one cancel fails, neither happens.
- The Fellowship must approve (whitelist) the action before it runs with full (Root) permission.
- It does not lock voters' balances or take away anyone's voting money.

**Bifrost Polkadot Runtime**

The Bifrost Polkadot Runtime is a software update for the Bifrost blockchain. This version is called bifrost_polkadot-27000. It makes the runtime file smaller when compressed and adds new features and fixes.

- The runtime is about 1.892 MB and can be compressed by 81.56%.
- It uses metadata version V14 and comes with an IPFS link for download.
- A storage migration to version 4 was added.
- Farming audit issues were fixed.
- Support was added for claiming rewards in a single currency and for SlpV2, which helps with vtoken minting.
- Reward calculation and automatic markup refresh logic were improved.
- Weights were regenerated for v0.27.0, and Frontier syncing subscriptions were cleaned up.
- One new contributor, @NaturalZz, made their first contribution.

**Bifrost November–December 2026 Budget Proposal**

Bifrost is a multichain staking yield layer. This proposal asks for money to run it for two months and to pay two one-time costs.

- **Total request:** $164,794.20, paid in DOT and vDOT.
- **Two-month operating budget:** $114,072.00 ($57,036.00 per month). This is about 5% less than the last cycle.
- **One-time costs:** $18,000.00 to help the team through a transition, and $32,722.20 for a twelve-month financing charge paid once at the start. Neither one adds to the monthly cost.
- **Two launches this window:** a stablecoin / real-world-asset yield vault going live, and a new consumer product under a new brand name.
- **Security first:** the budget includes a full outside audit of the new vault contracts and a bug bounty before launch.
- **Old work keeps running:** vDOT, vTokens, validators, and the signing service all continue without interruption.
- **New growth:** the Pharos stPROS liquid staking product launched in October 2026 and already holds about $2.2M in value.
- **Risks are managed:** the vault launches in steps, gated on the audit, and any shortfall from price changes is covered by Bifrost Foundation reserves.

Bifrost Operating Budget Proposal (November 2026 - December 2026 for 2 Months)

## Hyperbridge Recovery Batch (November)

This is a plan to **burn** (destroy) tokens on the **Bifrost Polkadot** network so they can be sent back to users on **Ethereum**.

- **What it does:** It recovers tokens for **33 Bifrost accounts** that signed up with an Ethereum receiving address.
- **Two tokens are burned:** about **34.15 vETH** (4 accounts) and about **282,509.88 MANTA** (29 accounts).
- **How amounts are fixed:** The amounts come from a saved balance snapshot (block **#14,556,243**). Two accounts were also in the first batch, but this time their amounts use the new November snapshot.
- **How the burn works:** One big batch of **35 calls** runs all at once. First, **33 `tokens.forceTransfer` calls** move each user's free tokens to the all-zero account `111111111111111111111111111111111HC1`. Then **2 `tokens.setBalance` calls** set that account's MANTA and vETH balances (free and reserved) to zero.
- **Safety:** The batch is **atomic** — if any inner call fails, the whole batch rolls back. Reserved balances of users are not moved.
- **Then on Ethereum:** After the burn is checked, the **actual burned amounts** are sent on **Ethereum mainnet** to the addresses in this batch's registry — **1:1, with no deduction**.
- **Verification details:** The call is `utility.batchAll`, calldata is **2717 bytes**, and the call hash is `0x5a85bc0f6f33e7153c39ee2052e58491b8aba83e88461e53c6e9ad9136bae484`. It was decoded with runtime version **26000** at block **#14,558,790**.
- **Not included:** Accounts outside this batch are unaffected and may come in a later recovery round.

- A plan is being made to help a user get back vASTR tokens that got stuck.
- The user sent vASTR to Bifrost, but the step that creates a redemption order failed.
- Because of the failure, no redemption order was created.
- The plan whitelists one special recovery call so it can be run later.
- Whitelisting means giving permission for that call to be executed.
- This proposal only gives permission; it does not actually create the redemption order.
- The actual recovery action will happen through a separate referendum.

[Fellows] Referendum #618-Whitelist the Soneium vASTR Redemption Recovery Call

Deciding

Preparing

Killed

- A user sent about 24,466 vASTR from Soneium to Bifrost, but one step of the transfer failed.
- This proposal fixes that problem by creating the missing order on Bifrost.
- The new order uses about 24,465.9 vASTR, the amount that actually arrived on Bifrost.
- The money will go to the user's Astar address: 0x0F2b16d3336154F2F04Db247138fC1041C3B8f2A.
- After that, the ASTR is meant to travel back through Astar to Soneium.
- The final amount and timing are not exact yet because fees and cross-chain steps can change things.
- The Astar-to-Soneium route was restricted last time it was checked, so it must be watched.
- A related proposal, Fellowship #618, must be approved first before this one can run.

[Whitelisted Caller] Referendum #327-# Recover the Failed Soneium vASTR Redemption Order

beneficiary

Bifrost Polkadot

referenda12

fellowship9

discussions4