Skip to content

Commit f30ace3

Browse files
magurhmagurh
committed
Merge branch 'fdc-proposals' into 'main'
Add FIP.14 and STP.11 See merge request flarenetwork/docs-team/governance-proposals!28
2 parents cc74de8 + 02b63dd commit f30ace3

File tree

3 files changed

+178
-0
lines changed

3 files changed

+178
-0
lines changed

‎FIP/FIP_14.md‎

Lines changed: 87 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,87 @@
1+
---
2+
nav_order: 10014
3+
title: FIP.14
4+
---
5+
6+
# FIP.14: Add Support for FDC Web2 Attestations
7+
8+
| Type | Flare Improvement Proposal |
9+
| :----------------- | :------------------------------------------ |
10+
| Author | Flare Foundation |
11+
| Created | 20-Nov-2025 |
12+
| Document Status | Draft |
13+
| Majority Condition | 50% (required) |
14+
15+
## 1. Brief Description
16+
17+
This proposal introduces a new FDC attestation type - `Web2Json` - and defines a standardized process for adding, updating, or removing new attestation sources (API endpoints).
18+
While [FIP.12](./FIP_12.md) allows new attestation types to be added through approval from the [Management Group](./FIP_2.md), this proposal specifies how Web2 attestation sources are governed under that framework.
19+
It also establishes a default attestation fee mechanism, with any future adjustments to the fee subject to approval by the [Management Group](./FIP_2.md).
20+
21+
As part of introducing this new attestation type, an initial set of Web2 attestation sources (API endpoints) will be included in this proposal.
22+
23+
## 2. Motivation
24+
25+
* Enable transparent and user-driven inclusion of new API endpoints into the FDC `Web2Json` attestation system.
26+
* Ensure legal and technical vetting by the Flare Foundation for each request.
27+
* Preserve decentralization and oversight by requiring the [Management Group](./FIP_2.md) to vote on both endpoint inclusion/removal and attestation fee adjustments.
28+
29+
## 3. Technical Description
30+
31+
### 3.1 Process of Adding, Updating, or Removing an API Endpoint
32+
33+
Changes to FDC attestation sources will follow the process below:
34+
35+
1. **Pull Request Submission**
36+
* Users submit pull requests with desired endpoint changes according to instructions set by the Flare Foundation in the [verifier-indexer-api](https://github.com/flare-foundation/verifier-indexer-api/blob/main/CONTRIBUTING.md#proposing-web2json-attestation-type-source-changes) repository.
37+
38+
2. **Flare Foundation Review**
39+
* The foundation reviews submissions to ensure legality, relevance, and technical feasibility.
40+
* Requests failing legal or technical validation are rejected with clear feedback.
41+
* Approved requests proceed to the next stage.
42+
43+
3. **Management Group Voting**
44+
* This is similar to the workflow described in [FIP.12](./FIP_12.md), where new attestation types are submitted, reviewed by the Foundation, and then voted on by the [Management Group](./FIP_2.md).
45+
* The Flare Foundation forwards vetted requests to the Management Group forum for formal voting.
46+
* **Voting conditions**: (Acceptance-based)
47+
* **Quorum**: at least 66% of Management Group members must cast a vote.
48+
* **Pass threshold**: >50% in favor.
49+
* Upon approval, the API endpoint is added, updated or removed per the user’s request.
50+
51+
### 3.2 Attestation Fee Structure
52+
53+
The attestation fee will be determined based on specific source requests.
54+
The default fee is set to 1 FLR.
55+
This fee is required from users to prioritize and process the attestation.
56+
57+
**Fee adjustments** (increases or decreases):
58+
59+
* May be proposed by users when a request for a new endpoint is made.
60+
* May be proposed by any Management Group member to increase or decrease this fee by initiating a discussion on [Discourse](https://forum.flare.network/) which will then be put to a vote.
61+
* Are subject to the same quorum and majority voting thresholds outlined above.
62+
63+
### 3.3 Inclusion of new Web2 attestation source
64+
65+
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.
66+
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.
67+
68+
Details of this new attestation source can be found on the [verifier-indexer-api](https://github.com/flare-foundation/verifier-indexer-api/blob/main/src/config/web2/web2-json-sources.ts#L9) Github Repository.
69+
The attestation fee for this source will be set to 100 FLR.
70+
71+
## 4. Proposed Implementation Date Range
72+
73+
This proposal includes the implementation of the following parts after the voting finishes.
74+
75+
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.
76+
2. Inclusion of a new `Web2Json` Attestation Source: implemented along with the new attestation type mentioned above.
77+
78+
New FDC attestation sources will be implemented in accordance with the steps mentioned in [Section 3.1](#31-process-of-adding-updating-or-removing-an-api-endpoint) above.
79+
80+
## 5. Voting Details
81+
82+
To pass, the proposal requires a simple majority of votes in favor of it.
83+
84+
## 6. Deadline for Voting
85+
86+
* **Notice period**: 20-November-2025 to 27-November-2025
87+
* **Voting period**: 28-November-2025 to 5-December-2025

‎STP/STP_11.md‎

Lines changed: 89 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,89 @@
1+
---
2+
nav_order: 30011
3+
title: STP.11
4+
---
5+
6+
# STP.11: Add Support for FDC Web2 Attestations
7+
8+
| Type | Songbird Test Proposal |
9+
| :------------------ | :------------------------------------------ |
10+
| Author | Flare Foundation |
11+
| Created | 20-November-2025 |
12+
| Document Status | Draft |
13+
| Threshold Condition | 75% (required to reject) |
14+
| Majority Condition | 50% (required to reject) |
15+
16+
## 1. Brief Description
17+
18+
This proposal introduces a new FDC attestation type - `Web2Json` - and defines a standardized process for adding, updating, or removing new attestation sources (API endpoints).
19+
While [STP.09](./STP_9.md) allows new attestation types to be added through approval from the [Management Group](./STP_3.md), this proposal specifies how Web2 attestation sources are governed under that framework.
20+
It also establishes a default attestation fee mechanism, with any future adjustments to the fee subject to approval by the [Management Group](./STP_3.md).
21+
22+
As part of introducing this new attestation type, an initial set of Web2 attestation sources (API endpoints) will be included in this proposal.
23+
24+
## 2. Motivation
25+
26+
* Enable transparent and user-driven inclusion of new API endpoints into the FDC `Web2Json` attestation system.
27+
* Ensure legal and technical vetting by the Flare Foundation for each request.
28+
* Preserve decentralization and oversight by requiring the [Management Group](./STP_3.md) to vote on both endpoint inclusion/removal and attestation fee adjustments.
29+
30+
## 2. Technical Description
31+
32+
### 3.1 Process of Adding, Updating, or Removing an API Endpoint
33+
34+
Changes to FDC attestation sources will follow the process below:
35+
36+
1. **Pull Request Submission**
37+
* Users submit pull requests with desired endpoint changes according to instructions set by the Flare Foundation in the [verifier-indexer-api](https://github.com/flare-foundation/verifier-indexer-api/blob/main/CONTRIBUTING.md#proposing-web2json-attestation-type-source-changes) repository.
38+
39+
2. **Flare Foundation Review**
40+
* The foundation reviews submissions to ensure legality, relevance, and technical feasibility.
41+
* Requests failing legal or technical validation are rejected with clear feedback.
42+
* Approved requests proceed to the next stage.
43+
44+
3. **Management Group Voting**
45+
* This is similar to the workflow described in [STP.09](./STP_9.md), where new attestation types are submitted, reviewed by the Foundation, and then voted on by the [Management Group](./STP_3.md).
46+
* The Flare Foundation forwards vetted requests to the Management Group forum for formal voting.
47+
* **Voting conditions**: (Acceptance-based)
48+
* **Quorum**: at least 66% of Management Group members must cast a vote.
49+
* **Pass threshold**: >50% in favor.
50+
* Upon approval, the API endpoint is added, updated or removed per the user’s request.
51+
52+
### 3.2 Attestation Fee Structure
53+
54+
The attestation fee will be determined based on specific source requests.
55+
The default fee is set to 1 SGB.
56+
This fee is required from users to prioritize and process the attestation.
57+
58+
**Fee adjustments** (increases or decreases):
59+
60+
* May be proposed by users when a request for a new endpoint is made.
61+
* May be proposed by any Management Group member to increase or decrease this fee by initiating a discussion on [Discourse](https://forum.flare.network/) which will then be put to a vote.
62+
* Are subject to the same quorum and majority voting thresholds outlined above.
63+
64+
### 3.3 Inclusion of new Web2 attestation source
65+
66+
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.
67+
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.
68+
69+
Details of this new attestation source can be found on the [verifier-indexer-api](https://github.com/flare-foundation/verifier-indexer-api/blob/main/src/config/web2/web2-json-sources.ts#L9) Github Repository.
70+
The attestation fee for this source will be set to 100 SGB.
71+
72+
## 4. Proposed Implementation Date Range
73+
74+
This proposal includes the implementation of the following parts after the voting finishes.
75+
76+
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.
77+
2. Inclusion of a new `Web2Json` Attestation Source: implemented along with the new attestation type mentioned above.
78+
79+
New FDC attestation sources will be implemented in accordance with the steps mentioned in [Section 3.1](#31-process-of-adding-updating-or-removing-an-api-endpoint) above.
80+
81+
## 5. Voting Details
82+
83+
An STP is rejection-based, meaning that it is accepted unless certain conditions are met, namely, that the quorum threshold (75%) is reached and at least half of the votes are against it.
84+
(See [Governance](https://docs.flare.network/tech/governance/#stps).)
85+
86+
## 6. Deadline for Voting
87+
88+
* **Notice period**: 20-November-2025 to 27-November-2025
89+
* **Voting period**: 28-November-2025 to 5-December-2025

‎index.markdown‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -31,6 +31,7 @@ Proposals aimed at improving the Flare network.
3131
| 11 | [Optimize Rewarding Structure and Adjust Protocol Parameters](FIP/FIP_11.md) |
3232
| 12 | [Add Support for the Flare Data Connector](FIP/FIP_12.md) |
3333
| 13 | [Add Custom Feeds to FTSO](FIP/FIP_13.md) |
34+
| 14 | [Add Support for FDC Web2 Attestations](FIP/FIP_14.md) |
3435

3536
## Songbird Improvement Proposals (SIP)
3637

@@ -61,6 +62,7 @@ Proposals aimed at improving the Flare network by being tested first on the Song
6162
| 8 | [Update FTSO Data Feeds and Define Process to Add New Ones](STP/STP_8.md) |
6263
| 9 | [Add Support for the Flare Data Connector](STP/STP_9.md) |
6364
| 10 | [Add Custom Feeds to FTSO](STP/STP_10.md) |
65+
| 11 | [Add Support for FDC Web2 Attestations](STP/STP_11.md) |
6466

6567
<style>
6668
table thead tr th:first-child {

0 commit comments

Comments
 (0)