Skip to content
Small red and white spheres form abstract hexagonal shape
Flare blog logo
Back to All News

FIP.14 and STP.11 introduce support for new FDC Web2 attestations

Flare Updates

The notice period for FIP.14 and STP.11 is now open. This proposal introduces Web2Json, a new attestation type for the Flare Data Connector (FDC). It also defines a clear process for adding, updating, or removing supported Web2 API endpoints, and establishes a default attestation fee. 

FIP.14 Proposal: https://proposals.flare.network/FIP/FIP_14.html

STP.11 Proposal: https://proposals.flare.network/STP/STP_11.html

The proposals build on the governance framework introduced in FIP.12, which established how new attestation types are added to the network.

🗓️ Notice period (same for both proposals): 20-November-2025 to 27-November-2025

🗓️ Voting period (same for both proposals): 28-November-2025 to 5-December-2025

Key aspects of the proposal

Web2Json expands the types of data the FDC can support by enabling attestations for structured JSON returned from Web2 APIs. FIP.14 also introduces a standard workflow for requesting new endpoints, ensuring that they undergo legal and technical review before being put to a Management Group vote.

Key points include:

  • A new Web2Json attestation type supporting JSON-based Web2 API data
  • A pull-request process for proposing new endpoints or updates
  • Foundation review to validate legality, relevance, and technical feasibility
  • Management Group voting to approve or reject proposed endpoint changes
  • The attestation fee will be determined based on specific source requests. Any fee adjustments will be subject to a Management Group vote. 

How Web2Json strengthens Flare’s “connect everything” vision

The Flare Data Connector is built to make Flare the blockchain for data, securely importing information from other blockchains and the internet. Web2Json extends this mission by unlocking nearly all structured data available through Web2 APIs - from sports scores and weather to finance, IoT, and social feeds.

Because FDC is secure, reliable, and decentralized, supported by ~100 independent data providers, developers can trust Web2 API data with the same assurances as other FDC-supported sources. This positions FDC as a unified gateway to any digital information, advancing Flare’s goal of connecting everything.

For example, prediction markets like Ignite Markets can use verified Web2 API data to settle outcomes such as sporting events. Web2Json broadens this capability to countless additional data-rich use cases.

How can developers request new endpoints?

Developers can request new Web2 API endpoints by submitting a pull request per the instructions in the Flare Foundation GitHub repository. 

The Foundation will review each submission. Any requests that pass validation are then forwarded to the Management Group for a formal vote. 

Voting details

Voting for this proposal which introduces a new FDC Web2 attestation type commences once the notice period has ended. The proposal will be accepted if more than 50% votes are in favor. Be sure to review the proposal and participate when the voting window opens.

Note that new Web2 source (such as endpoints) additions, updates, removals, and fee adjustments all follow the Management Group voting standards that were defined in FIP.12 and STP.11:

  • Quorum of 66% participation
  • Approval threshold of greater than 50% of votes in favor

🗓️ Notice period (same for both proposals): 20-November-2025 to 27-November-2025

🗓️ Voting period (same for both proposals): 28-November-2025 to 5-December-2025

FIP.14 Proposal: https://proposals.flare.network/FIP/FIP_14.html

STP.11 Proposal: https://proposals.flare.network/STP/STP_11.html