You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The **F**lare **T**ime **S**eries **O**racle **(FTSO)** is an [enshrined oracle](/support/terminology#enshrined-oracle) that provides decentralized data feeds to the Flare network.
23
-
Since the release of FTSOv1 two years ago, users and applications on Flare have enjoyed consistent and reliable pricing, with zero downtime or failures.
23
+
Since the release of FTSOv1, users and applications on Flare have enjoyed consistent and reliable pricing.
24
24
FTSOv2 builds on the robust foundation laid by its predecessor, offering several enhancements:
25
25
26
26
-**Secure.** Enshrined into Flare's core protocol, every oracle feed in FTSOv2 inherits the economic security of the entire network.
@@ -31,7 +31,7 @@ FTSOv2 builds on the robust foundation laid by its predecessor, offering several
31
31
32
32
-**Decentralized.** Each FTSOv2 feed is supported by around 100 independent data providers, who are selected by Flare users through their delegated stake, imposing a strict economic cost for misbehavior.
33
33
34
-
-**Cost-effective.** Block-latency feeds in FTSOv2 are completely free to query. Feeds from Scaling are also free to query and verify locally, with minimal gas costs for onchain verification.
34
+
-**Cost-effective.** Block-latency feeds in FTSOv2 are free to use onchain. Feeds from Scaling are also free to query and verify locally, with minimal gas costs for onchain verification.
35
35
36
36
## Architecture
37
37
@@ -74,7 +74,7 @@ For a detailed explanation of the FTSOv2 mechanism, read the [FTSOv2 whitepaper]
74
74
75
75
Every block on Flare, generated approximately every 1.8 seconds, initiates the selection of a sample of data providers to deliver the next feed update.
76
76
This selection process leverages a stake-weighted verifiable randomness function (VRF), where the likelihood of each data provider being chosen is proportional to their stake.
77
-
The expected sample size is one, and data providers have no control over, nor knowledge of, when they will be selected.
77
+
The expected sample size (average) is `1.5`, and data providers have no control over, nor knowledge of, when they will be selected.
78
78
79
79
In detail, each block has a unique seed value, used by FTSOv2 data providers to generate a personal random score.
80
80
This score, coupled with a cryptographic proof, ensures its authenticity and verifiability.
@@ -142,7 +142,7 @@ Importantly, only the expected sample size increases, not the actual sample size
142
142
FTSOv2's block-latency feeds are designed to be statistically self-correcting.
143
143
To further ensure their long-term accuracy, FTSOv2 uses the anchor feeds from [Scaling](/ftso/scaling/overview).
144
144
Anchor feeds utilize a full commit-reveal process across all data providers with an inter-quartile range (IQR) band calculation, and update once every voting epoch (i.e. 90 seconds).
145
-
Data providers are rewarded when the block-latency feeds remains within `±0.25%` of the anchor feeds every voting epoch.
145
+
Data providers are rewarded when the block-latency feeds remain within `±0.25%` of the anchor feeds every voting epoch.
@@ -339,9 +339,8 @@ Discover suitable options for your needs on the [Flare Wallets](https://flare.ne
339
339
340
340
-**Transaction fees:**
341
341
-**Type0** (Legacy) - Fee is calculated as `gasUsed * gasPrice`.
342
-
343
342
-**Type2** (EIP-1559) - Fee is calculated as `(baseFee + priorityFee) * gas`.
344
-
- In both cases, the transaction fee is burned.
343
+
- In both cases, all transaction fees are burned.
345
344
346
345
## Smart contracts
347
346
@@ -368,15 +367,15 @@ Discover suitable options for your needs on the [Flare Wallets](https://flare.ne
368
367
-**Participants (Validators):**
369
368
- Nodes must meet a [minimum self-bond requirement](https://proposals.flare.network/FIP/FIP_5.html) (defined by governance) to become validators.
370
369
- Validators participate in consensus voting and are randomly selected as leaders to propose new blocks, weighted by their total stake (self-bond + delegated stake).
371
-
-The network currently has [over 100 validators](https://flare-systems-explorer.flare.network/validators) (median stake ≈0.6%, max stake ≈2%).
370
+
-Validator count and stake distribution are viewable live on the [Flare Systems Explorer](https://flare-systems-explorer.flare.network/validators).
372
371
373
372
-**Enshrined protocols:** In addition to consensus, Flare validators are also data providers for [FTSO](/ftso/overview) and [FDC](/fdc/overview).
374
373
375
374
## Block verification
376
375
377
-
-**Block Header Verification:**[Example Go implementation](https://github.com/flare-foundation/go-flare/blob/main/coreth/consensus/dummy/consensus.go#L187).
376
+
-**Block Header Verification:**[Example Go implementation](https://github.com/flare-foundation/go-flare/blob/main/coreth/consensus/dummy/consensus.go).
378
377
379
-
-**Block Body Validation:**[Example Go implementation](https://github.com/flare-foundation/go-flare/blob/main/coreth/core/block_validator.go#L62).
378
+
-**Block Body Validation:**[Example Go implementation](https://github.com/flare-foundation/go-flare/blob/main/coreth/core/block_validator.go).
380
379
381
380
-**Verify transaction in block:** Verified using Merkle Patricia Trie proofs against the receipts root included in the block header.
Copy file name to clipboardExpand all lines: docs/run-node/1-system-requirements.mdx
-5Lines changed: 0 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -144,8 +144,3 @@ If behind a firewall or NAT, configure port forwarding for these default TCP por
144
144
-**Port `9651` (P2P/Staking):** Required by **all nodes** for P2P peer discovery/communication. Additionally used by validators for P-Chain consensus communication. Must be publicly reachable.
145
145
146
146
A static public IP address is highly recommended for validators to ensure consistent uptime and reliability, potentially impacting rewards.
147
-
148
-
## On a Cloud Provider
149
-
150
-
Pre-configured Flare nodes are available on [Google Cloud Platform Marketplace](/run-node/gcp-marketplace-nodes).
151
-
These nodes do not require installing dependencies or managing configuration files, they also come with a local database copy which can reduces bootstrap times.
0 commit comments