Removal of the Web2Json ‘Ignite` API Endpoint
Subject: Flare Foundation proposal to the Infrastructure Provider Management Group (MG) to remove the `Ignite` API endpoint registered for the `Web2Json` FDC attestation type on both Flare and Songbird
​The Foundation additionally requests that the MG proceed with rejection-based on-chain voting, in place of the acceptance-based conditions in FIP.14 / STP.11 section 3.1, for the reasons outlined below.
Background:
The Ignite Market project is winding down and the `Ignite` endpoint is no longer available
​Per FIP.14 / STP.11 section 3.1, which covers adding, updating, or removing an API endpoint, we ask the MG to review, comment, and vote
​Proposed Change:
​Remove the `Ignite` endpoint from the `Web2Json` source allowlist on both networks, and remove its associated fee configuration via `removeTypeAndSourceFee` on `FdcRequestFeeConfigurations`. Once removed, `requestAttestation` reverts for `Web2Json` / `Ignite` and no further requests can be submitted
This proposal covers removal of the endpoint only. Any future Web2 attestation capability would be proposed separately under the applicable process
​Motivation:
​- Requests can no longer be fulfilled. The endpoint is unreachable, so attestation requests against it cannot be confirmed by the provider set
- The base fee is non-refundable. Requests are still accepted on chain, and `FdcHub` forwards the fee to the reward manager before any verifier is consulted. A user submitting a `Web2Json` request today pays the base fee for a result that can never be produced
​Impact on Infrastructure Providers:
​With no other `Web2Json` sources currently active, the `web2-verifier` service has nothing further to serve once this change executes, and providers can shut it down
​Providers will be notified once the removal has been executed and can stop the service at their convenience thereafter. There is no deadline. Follow-up `flare-systems-deployment` and `fdc-suite-deployment` releases will remove the configuration entries and the service definition
​Voting Exception Justification:
​The acceptance-based conditions in section 3.1 were written for adding or modifying a live endpoint, where an affirmative mandate establishes a new capability and a corresponding obligation on providers. This proposal establishes no new obligation — it removes one. For as long as the fee configuration remains in place against an endpoint that is no longer available, users remain exposed to spending a non-refundable base fee on requests that cannot be fulfilled. The Foundation considers these extenuating circumstances sufficient to expedite the removal by way of a rejection-based vote, with the MG’s concurrence
​Any MG member who would prefer the acceptance-based conditions to apply is invited to comment such in this thread, in which case the Foundation could pivot if the MG had any glaring concerns
​Voting Details:
​Comment Period - Continuing now through 3 September, 2026 at 12:00 UTC
​The Flare Foundation will then initiate transactions from the polling contracts on both Flare and Songbird for MG members to cast on-chain votes, via the MG tab on the Flare Portal
​Anticipated Voting Date: 3 September, 2026 at 12:00 UTC. The voting period is 48 hours, closing 5 September at 12:00 UTC
​Voting is rejection-based and would require 66% participation amongst all eligible MG members and more than 50% of the votes going against the proposal for it to be rejected. Otherwise, the Foundation will proceed with removing the `Web2Json` / `Ignite` endpoint on both Flare and Songbird after the voting period expires, anticipated 7 September, 2026 at 12:00 UTC.