Polkadot Referendum 1913 has passed and executed, unlocking $375,777 USDC in treasury funding for the next six months of Chainflip's Asset Hub integration work. The result was decisive: 94.9% Aye, with 264.33M DOT in support against 14.19M in opposition on the Medium Spender track.
The interesting part is not the amount. It is what the vote tells you about how cross-chain infrastructure gets built and paid for when the chain doing the funding is not the same team writing the code.
What the Vote Actually Bought
For DOT holders, this was a straightforward capital-allocation question: is continued Asset Hub integration with a mature cross-chain protocol worth roughly $376K over six months? Referendum 1913 is the second treasury-funded cycle of Chainflip's work on the Polkadot Asset Hub integration. The first was delivered in September 2024 via Polkadot's DeFi and Infrastructure Bounty, in collaboration with Velocity Labs.
That work has been in production since July 30, 2025, when the integration went public through SubWallet. Users can move between Polkadot-native assets (hubUSDC, hubUSDT, DOT) and Bitcoin, Ethereum, and USDC on other chains in a single transaction, with settlement in the native asset on both ends. No wrapped tokens, no manual bridge step, no exchange account.
On the Chainflip side, the Asset Hub integration inherits the same routing, liquidity, and integrator relationships as every other route on the protocol. Chainflip has processed over $8B in cross-chain swaps since going into production two years ago. A DOT holder swapping to native BTC, or a hubUSDC holder moving to Ethereum-native USDC, uses the same JIT AMM and validator network as the rest of the book.
Referendum 1913 continues that work under Apache 2.0 licensing, so the code stays open, reviewable, and reproducible.
The Roadmap DOT Holders Signed Off On
The $375,777 USDC is not a lump sum. It is split across three milestones over six months, at a EUR 100 per hour development rate plus a EUR 30K per month baseline for ongoing maintenance (runtime upgrade adaptation, validator witnessing operations, security monitoring, and Parity liaison work).
M1: Elections-Based Witnessing Migration ($116,667)
Runs months 1 to 2 (July to August 2026). Chainflip's validator network uses a "witnessing" module to observe Asset Hub state and settle swaps accordingly. M1 migrates that module to an elections-based design, distributing verification across a rotating validator set, reducing coupling to any single node, and simplifying future runtime upgrade adaptation.
For end users, this is under-the-hood reliability work. It is the kind of change that pays for itself across the multi-year cycle of Polkadot runtime evolution rather than showing up as a new front-end feature next month.
M2: Paseo Testnet Integration ($103,101)
Runs months 3 to 4 (September to October 2026). Chainflip has historically tested Asset Hub integration on a custom test environment. M2 moves that testing onto Paseo, Polkadot's canonical community testnet, and retires the legacy setup.
The practical effect is closer alignment with Polkadot's release cadence: faster detection of breaking changes in Polkadot runtimes, lower cost to test integration changes, and less bespoke infrastructure for Chainflip validators to maintain. For DOT holders it reduces Chainflip's future maintenance surface, and by extension future treasury requests.
M3: CCM Support for pallet-revive and Extrinsic Calls ($156,009)
Runs months 5 to 6 (November to December 2026). This is the milestone with the largest user-facing implication.
Chainflip's Cross-Chain Messaging (CCM) already lets a swap recipient trigger a call on the destination chain in the same transaction as the swap itself. Today that works for EVM contracts on Ethereum and Arbitrum, and for programs on Solana. M3 extends CCM to Polkadot Hub, specifically to pallet-revive (Polkadot's next-generation smart contract environment) and native extrinsic calls.
In practice, that means a Bitcoin holder can swap to a Polkadot Hub asset and execute a smart-contract call on Polkadot in a single Chainflip transaction. Deposit into a DeFi protocol, mint a position, register a name, whatever the destination contract exposes. From the user's perspective it collapses to one signature. It is the first meaningful step toward composable one-transaction workflows between Bitcoin, Ethereum, and Polkadot smart contracts.
Why This Funding Model Matters
Cross-chain infrastructure is expensive to maintain because it is coupled to the runtime evolution of every chain it touches. Every Polkadot runtime upgrade, every Asset Hub schema change, every XCM version bump requires adaptation on the Chainflip side. That maintenance work does not stop existing just because no one is paying attention. It becomes technical debt if it is not funded, and eventually it becomes a broken integration.
The Polkadot treasury paying for Polkadot-specific integration work is a straightforward alignment of incentives:
Polkadot gets the maintenance guaranteed, in the open, at a transparent price and against defined milestones.
Chainflip funds Polkadot-specific work through Polkadot-specific revenue, rather than spreading protocol resources across long-tail maintenance for each chain.
Users of both networks get a durable, updated integration that keeps working through years of runtime evolution.
Every peer chain considering cross-chain support has a version of this question. Bounty-funded first integration, treasury-funded follow-on maintenance, community vote on renewal at each cycle. 94.9% Aye is a strong signal that this pattern works for both sides.
The alternative, where cross-chain integrations get built once by a well-funded protocol and then quietly rot as maintenance costs are not carried, is a pattern the industry has already seen enough of.
What to Watch Over the Next Six Months
The milestones deliver in sequence: M1 finishes in August 2026, M2 in October 2026, M3 in December 2026. All deliverables are due before end of 2026, with status reporting as part of the maintenance scope.
Progress and code drops will be public. Chainflip repositories continue publishing under Apache 2.0. The clearest external signal will be Chainflip Scan showing Asset Hub swap flow through the year, and the release of CCM-to-Polkadot swap paths in early 2027.
For users, the Chainflip / Asset Hub route remains live now via swap.chainflip.io and SubWallet. What arrives in December makes it materially more powerful.
Data Sources
Referendum 1913 details, vote tally, and milestone breakdown from Polkadot OpenGov on Subsquare. Chainflip protocol volume figures from Chainflip Scan. Public launch of the Chainflip / Asset Hub integration in SubWallet: July 30, 2025.
Resources
Swap - Start swapping native assets
Lending - Borrow against native Bitcoin
Blog - Product updates and announcements
Chainflip Scan - Track swaps and network activity
Website - Explore Chainflip
Earn with Chainflip:
Boost - Earn fees by providing single-sided liquidity with no IL risk
Stablecoin Strategies - Deposit stablecoins and earn optimized yields
Provide Liquidity - Supply assets to Chainflip's liquidity pools
Stake FLIP - Delegate FLIP and earn staking rewards
Find us:
What is Polkadot Referendum 1913?
A Medium Spender treasury proposal on Polkadot OpenGov that approved $375,777 USDC in funding to Chainflip Labs for continued maintenance and feature development of the Polkadot Asset Hub integration inside the Chainflip protocol. It passed with 94.9% Aye and has been executed.
What does the funding cover?
Three milestones over six months plus ongoing baseline maintenance: an elections-based witnessing migration ($116,667), Paseo testnet integration ($103,101), and CCM support for pallet-revive and extrinsic calls on Polkadot Hub ($156,009). The baseline covers validator witnessing operations, runtime upgrade adaptation, security monitoring, and status reporting at EUR 30K per month.
When did Chainflip's Asset Hub integration go live?
Public launch was July 30, 2025, integrated in SubWallet. Supported assets include hubUSDC, hubUSDT, DOT, plus native BTC, ETH, and USDC on other chains, with settlement in the native asset on both ends of every swap.
Is Chainflip's Polkadot code open source?
Yes. All Chainflip repositories, including the Polkadot Asset Hub integration, are released under Apache 2.0.
What is CCM and why does M3 matter?
Cross-Chain Messaging is Chainflip's feature for triggering a call on the destination chain in the same transaction as a swap. It works on EVM chains and Solana today. M3 extends CCM to Polkadot Hub smart contracts (pallet-revive) and native extrinsics, enabling one-transaction Bitcoin-to-Polkadot or Ethereum-to-Polkadot smart-contract workflows without a separate follow-up transaction.
Where can I follow progress on the milestones?
Status reporting is part of the maintenance scope of Referendum 1913 and will be posted publicly. Code drops will land in the open-source Chainflip repositories under Apache 2.0. Live Asset Hub swap activity is visible on Chainflip Scan.
