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

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)

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

## 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.

Executed

- 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

# Farming Adjustment Proposal

This is a plan to change how farming rewards work in Bifrost. It has two parts.

- **Part 1: Change pool rewards.** The proposal edits some farming pools to change how many BNC rewards they give out. It also sends Treasury funds to pay BLP rewards to the stable pools.
- **Pools affected include:** vBNC/BNC, vDOT/DOT, vDOT-USDT, BNC/USDT, vMANTA/MANTA, and some others.
- **Total BNC involved in Part 1:** 35,619 BNC.
- **Part 2: Move BNC to the Foundation.** The proposal sends 35,619 BNC from the Treasury to the Bifrost Foundation to pay for charging.

Farming Adjustments and Charge - Nov-Dec 2026

# Bifrost Fellowship Proposal: Recovering Trapped BNC

- 4,733.514645 BNC got stuck during a transfer from Bifrost.
- The proposal asks the Bifrost Fellowship to whitelist a call that sends an XCM message to Hydration.
- The recovery call claims the trapped BNC and sends it to a Hydration account (address starts with 1got2...).
- The XCM execution fee is paid in HDX from Bifrost's sovereign account on Hydration.
- Any unused HDX goes back to that sovereign account.
- A call hash is included so the call can be whitelisted.
- This proposal only adds the call to the whitelist; actually running it needs a separate vote, Whitelisted Caller referendum #325.

[Fellows] Referendum #615-Whitelist an XCM Call to Recover Trapped BNC on Hydration

Demote and remove member in fellowship

Rejected

Deciding

Queueing

Preparing

- 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

## Recovering Trapped BNC on Hydration

- **What happened:** 4,733.514645 BNC got stuck on Hydration during a transfer from Bifrost.
- **The goal:** A proposal wants to send a special call (XCM) to claim that trapped BNC and send it to a beneficiary account on Hydration.
- **Who gets the BNC:** The beneficiary's Hydration account is `1got2QxVB1mdnWHZ5onsNaHD7u8R6G3B9wGmC5a43iCXHjr`.
- **Who pays the fee:** The XCM execution fee is paid in HDX from Bifrost's sovereign account on Hydration. Any unused HDX goes back to that account.
- **Was it tested?** Yes. A test using Chopsticks on a chain snapshot confirmed the BNC reached the beneficiary and other trapped assets were not affected.
- **Two hashes are given:** The proposal preimage hash and the recovery call hash are listed for verification.
- **One more step needed:** The recovery call must first be whitelisted by Fellowship referendum #615 before this proposal can work.

[Whitelisted Caller] Referendum #325-Recover 4,733.514645 BNC Trapped on Hydration

Bifrost Polkadot

referenda7

fellowship8

discussions3