Flare Confidential Compute awaits the STP.13 vote on Songbird, bringing verifiable confidential compute, PMWs, and FDC V2 before mainnet.
Author: Akshay
29th June 2026 – Flare announced that Flare Confidential Compute is ready for deployment on Songbird, pending a governance vote on Songbird Test Proposal STP.13.
High Signal Summary For A Quick Glance
Eli5DeFi
@Eli5defi
@FlareNetworks FCC is ☀️
Flare Confidential Compute is ready to deploy on Songbird. Pending governance, FCC brings the Flare 2.0 stack to @FlareNetworks' canary network: verifiable confidential compute, Protocol Managed Wallets, and an upgraded Flare Data Connector. STP.13 is up for review. Voting https://t.co/33DHiaR2Hp
11:54 AM·Jun 29, 2026
High attention and emotional sentiment detected.
The team shared the news on June 29 through its official channels. STP.13 is up for review now, and voting is scheduled to open on July 6, 2026. If approved, Songbird would become the proving ground for the core of Flare’s “Flare 2.0” stack.
Flare Confidential Compute extends the blockchain with Trusted Execution Environments, or TEEs. These are hardware-isolated enclaves where code and data run hidden from the host system. As a result, sensitive logic can run off-chain while still proving it ran correctly.
According to Flare’s developer documentation, the system enables secure off-chain computation, cross-chain transaction signing, and fast data attestation. In short, it stretches what a data-focused Layer 1 can do.
The June 29 announcement names three components. Together, they form the foundation of the upgrade.
First is verifiable confidential compute. Code runs inside a TEE, then produces a cryptographic attestation. That proof can be verified on-chain, so users do not have to trust the operator.
Second is Protocol Managed Wallets, known as PMW. These are protocol-governed multisig wallets that sign transactions on external chains like XRPL and Bitcoin. Because Flare smart contracts and a TEE quorum control them, protocols can act across chains without traditional bridges or user custody.
Third is the upgraded Flare Data Connector, or FDC V2. The new version uses TEE-based attestation for faster, consensus-proven data. Data providers relay instructions, then the TEEs verify thresholds and sign the result on-chain.
Relative positioning between the current Songbird architecture and the proposed Flare 2.0 (FCC) upgrade
Songbird is Flare’s canary network. It is a live, EVM-compatible chain with real economic value. For that reason, the team uses it to test new features before they reach Flare mainnet.
The network has played this role before. FAssets, for example, moved through Songbird in stages, with an open beta in December 2024 and further versions through 2025. So shipping Confidential Compute to Songbird first follows an established pattern.
The STP.13 vote decides whether that step proceeds. As of now, the proposal is not yet listed on the public proposals repository. There are also no vote tallies visible beyond the July 6 opening date.
The idea is not new. Flare first outlined the Flare 2.0 vision on March 19, 2025. That post introduced TEEs, Protocol Managed Wallets, and verifiable compute as a way to expand the network’s consensus.
Through 2025, the team ran hackathons and demos using Google Cloud Confidential Space TEEs. Then, in 2026, executives pointed to a Q3 2026 timeline at various events.
Flare CEO Hugo Philion has framed the technology around institutional privacy. In a Cryptopolitan piece from May 22, 2026, he reportedly said the system “will launch in Q3 2026,” with a focus on letting institutions trade and lend XRP-backed assets privately.
Timeline: Flare’s evolution from the State Connector to the Flare Data Connector and the rollout of Flare 2.0 confidential compute
Flare debuts the State Connector on its Songbird canary network, enabling decentralized verification of external blockchain states and laying the foundation for trust-minimized interoperability.
Flare launches its mainnet, bringing the State Connector architecture and FTSO-powered data infrastructure into the production ecosystem.
SIP.02 and the Flare Data Connector (FDC) whitepaper introduce the next-generation architecture, expanding the original State Connector into a more capable attestation system for blockchain and Web2 data.
Following approval of FIP.12, the Flare Data Connector officially goes live on Flare mainnet, providing decentralized cross-chain attestations and enabling the path toward FAssets on mainnet.
Flare publishes “Flare 2.0 Vision Part 1,” introducing Trusted Execution Environments (TEEs), Protocol Managed Wallets, and verifiable off-chain compute as the next evolution beyond the existing FTSO and FDC stack.
Major FAssets upgrades are tested and deployed on Songbird, strengthening Flare’s cross-chain asset infrastructure ahead of broader mainnet expansion.
Flare hosts multiple hackathons, including collaborations with Google Cloud Confidential Space, advancing confidential AI execution and Trusted Execution Environment technologies.
Flare announces that Flare Confidential Compute (FCC) is ready for deployment on Songbird through governance proposal STP.13, bringing the first complete implementation of the Flare 2.0 architecture to the canary network.
Songbird governance opens voting on STP.13 to determine whether Flare Confidential Compute will be activated on the network as the testing ground for Flare 2.0.
If approved, FCC will first be deployed on Songbird before progressing toward a Flare mainnet rollout, previously indicated by project leadership as part of the Flare 2.0 roadmap for Q3 2026.
Supporters argue that Flare Confidential Compute opens new design space. Private institutional DeFi, real-world asset trading, and verifiable AI agents all become more practical when private compute meets on-chain proofs.
The cross-chain angle matters too. With Protocol Managed Wallets, Flare protocols could move assets on XRPL or Bitcoin without a wrapped-token bridge. That approach may reduce a common source of hacks.
The model is not risk-free. TEEs depend on hardware vendors, and vendor exploits remain a known concern across the industry. Flare’s vision docs point to multi-TEE quorums as a mitigation, though production hardware details and audit status are still unconfirmed.
Market data stays modest for now. FLR traded near $0.00665 around June 28-29, with a market cap close to $570 million, according to CoinGecko. Flare’s total value locked sat near $117 million on DefiLlama, and no clear price spike has been tied to the announcement.
Early sentiment on X leaned bullish. Replies to the official announcement framed it as a milestone for Songbird and the wider Flare 2.0 vision.
Contributors echoed that view. One noted that private markets, autonomous agents, and cross-chain protocols all gain room to grow if the proposal passes. Community accounts also translated the news and flagged the July 6 vote.
That reaction is social signal, not independent validation. No major outlet has published a detailed review yet, and no notable skepticism has surfaced on the announcement itself. So the on-chain test still matters more than the mood.
The immediate milestone is the STP.13 vote on July 6. SGB and FLR holders can track it through the Flare governance portal once voting opens.
Beyond that, the open questions are clear. Mainnet timing, the audit outcome, and real performance metrics will only surface after a Songbird deployment. For readers following Flare Confidential Compute, the July 6 vote is the next concrete checkpoint to watch.
This article is for informational purposes only and is not financial advice. Always do your own research before making any investment decision.
Our Crypto Talk is committed to unbiased, transparent, and true reporting to the best of our knowledge. This news article aims to provide accurate information in a timely manner. However, we advise the readers to verify facts independently and consult a professional before making any decisions based on the content since our sources could be wrong too. Check our Terms and conditions for more info.
Flare
