FIP.14: Add Support for FDC Web2 Attestations

Type Flare Improvement Proposal
Author Flare Foundation
Created 20-Nov-2025
Document Status Draft
Majority Condition 50% (required)

1. Brief Description

This proposal introduces a new FDC attestation type - Web2Json - and defines a standardized process for adding, updating, or removing new attestation sources (API endpoints). While FIP.12 allows new attestation types to be added through approval from the Management Group, this proposal specifies how Web2 attestation sources are governed under that framework. It also establishes a default attestation fee mechanism, with any future adjustments to the fee subject to approval by the Management Group.

As part of introducing this new attestation type, an initial set of Web2 attestation sources (API endpoints) will be included in this proposal.

2. Motivation

  • Enable transparent and user-driven inclusion of new API endpoints into the FDC Web2Json attestation system.
  • Ensure legal and technical vetting by the Flare Foundation for each request.
  • Preserve decentralization and oversight by requiring the Management Group to vote on both endpoint inclusion/removal and attestation fee adjustments.

3. Technical Description

3.1 Process of Adding, Updating, or Removing an API Endpoint

Changes to FDC attestation sources will follow the process below:

  1. Pull Request Submission
    • Users submit pull requests with desired endpoint changes according to instructions set by the Flare Foundation in the verifier-indexer-api repository.
  2. Flare Foundation Review
    • The foundation reviews submissions to ensure legality, relevance, and technical feasibility.
    • Requests failing legal or technical validation are rejected with clear feedback.
    • Approved requests proceed to the next stage.
  3. Management Group Voting
    • This is similar to the workflow described in FIP.12, where new attestation types are submitted, reviewed by the Foundation, and then voted on by the Management Group.
    • The Flare Foundation forwards vetted requests to the Management Group forum for formal voting.
    • Voting conditions: (Acceptance-based)
      • Quorum: at least 66% of Management Group members must cast a vote.
      • Pass threshold: >50% in favor.
    • Upon approval, the API endpoint is added, updated or removed per the user’s request.

3.2 Attestation Fee Structure

The attestation fee will be determined based on specific source requests. The default fee is set to 1 FLR. This fee is required from users to prioritize and process the attestation.

Fee adjustments (increases or decreases):

  • May be proposed by users when a request for a new endpoint is made.
  • May be proposed by any Management Group member to increase or decrease this fee by initiating a discussion on Discourse which will then be put to a vote.
  • Are subject to the same quorum and majority voting thresholds outlined above.

3.3 Inclusion of new Web2 attestation source

This proposal introduces a new Web2 attestation source requested by Ignite Markets, a prediction market utilizing Web2 API data for settling outcomes such as sporting events. The addition of the FDC Web2Json attestation type significantly expands this capability, enabling countless additional data-rich use cases through the provision of decentralized consensus on the outcome of such events.

Details of this new attestation source can be found on the verifier-indexer-api Github Repository. The attestation fee for this source will be set to 100 FLR.

4. Proposed Implementation Date Range

This proposal includes the implementation of the following parts after the voting finishes.

  1. FDC Web2Json Attestation Type: expected to start shortly after the voting finishes, providing sufficient time for data providers to update and redeploy their infrastructure.
  2. Inclusion of a new Web2Json Attestation Source: implemented along with the new attestation type mentioned above.

New FDC attestation sources will be implemented in accordance with the steps mentioned in Section 3.1 above.

5. Voting Details

To pass, the proposal requires a simple majority of votes in favor of it.

6. Deadline for Voting

  • Notice period: 20-November-2025 to 27-November-2025
  • Voting period: 28-November-2025 to 5-December-2025