LightFTSO ☀️ (@lightFTSO) header
LightFTSO ☀️ (@lightFTSO) profile picture

OG Flare Data Provider. Facilitating passive income for Flare participants. Helping connect everything. [email protected] [email protected] 🇲🇽☀️

Mexico
Joined October 2021
Photo by LightFTSO ☀️ (@lightFTSO)Photo by LightFTSO ☀️ (@lightFTSO)Photo by LightFTSO ☀️ (@lightFTSO)Photo by LightFTSO ☀️ (@lightFTSO)Photo by LightFTSO ☀️ (@lightFTSO)Photo by LightFTSO ☀️ (@lightFTSO)Photo by LightFTSO ☀️ (@lightFTSO)Photo by LightFTSO ☀️ (@lightFTSO)Photo by LightFTSO ☀️ (@lightFTSO)Photo by LightFTSO ☀️ (@lightFTSO)
I've run the numbers on a cross section of providers that scored high on example provider usage. Using the original canonical median calculation according to their vp weights for epoch 416 and pre fip16 and the new 5x staking vp weighted formula for 418. The data confirms widespread abuse is detrimental to the FTSO where low effort providers concentrate 32% of the total valid VP around the example provider introducing severe instability to the overall system that now heavily depends on one subset of data injected by far too many providers. Any provider bragging about a huge jump from 20-30% to nearly 50% post fip16 is effectively bragging about having deployed the example provider to mainnet.
2
5
31
926
LightFTSO ☀️ retweeted
Cycles are interesting in that they have zero regard for reality. Vs even 1 year ago Flare is in an inconceivably better utility position. More is coming with Flare 2.0, further expansion of XRPFi, the coming onboarding of meaningful institutional partners (finally), FSA is working to abstract away complexity, FIRE and FIP16 change the token economics for the (vastly) better. And those are just the things that we can discuss publicly. Almost everything we have set out to do is being done (barring adding more FAssets - in the works) and by and large it’s working. But if you look at the whole crypto market you would think the whole industry is finished - despite more institutional interest and greater clarity than ever before. Unfortunately cycles are a fact of life, even Amazon had a 94% peak to trough drawdown when the .com cycle burst - but the internet didn’t go away nor did Amazon and neither will crypto and certainly not Flare - which presents more utility than almost anything else in the market. Every cycle teaches the same lesson, and every time we forget it: near the bottom it always feels like the end, but it never is. I believe that we're closer to the turn than the mood would have you believe. The roadmap ahead is the thing we're here for. At Flare we trust in the process to ship great product - knowing that is the only true path to winning. Flare will emerge from this brutal winter fighting fit and offering more than ever for the next cycle.
94
217
31
829
92,335
LightFTSO ☀️ retweeted
FAssets v1.3 is live on Songbird. Minting no longer goes through agents — users initiate it directly on XRPL with a labelled payment. FXRP routes via destination tags and memo. The same paths $XRP already uses. What changes for users: – No agent selection – No reservation step – No lots. Mint any amount – Aligned with how exchanges and wallets already send XRP XRPFi doesn't scale on new apps alone. It scales when getting into those apps feels like sending $XRP. v1.3 is that step. First the rails. Then the rush.
75
126
33
455
58,864
Recent discussions by some providers on Flare about how the FIP.16 changes would destroy FTO accuracy are absurd, overwrought, and reek of narcissistic arrogance. The current primary price band is absurdly tight, and even the secondary bands are incredibly tight when talking about consensus pricing for assets that trade on hundreds of exchanges across all time-zones, with incredible variance in volumes (especially when considering true volume vs wash trade volume). Let's take the XRP price feed on a random round - Round 1306230. The Finalized price for that round was $1.33355 In order to be in the primary band, a DP had to supply a price of $1.33354-$1.33359. Now also, remember that border prices receive only 50% primary credit, so in reality to be considered a 100% primary band winner for that round, you would have to have supplied a price of $1.33355-$1.33358. That is a $0.00003 band width. Now, compare that to the TRUE price of XRP at that time...Oh wait, there is no true price of XRP at that time. Because every single price you see for an asset anywhere is based on either last trade, or an aggregation. So how important is it that a provider supply a price within that $0.00003 price range? 0% important. That exact finalized price could have been derived from any spread of provided prices, although the wider the actual submission spread, the more chance of "true" price drift. However the difference between $1.33354 and $1.33355 when it comes to actual applications of these price feeds is nonexistent. Yet, some incredibly arrogant providers would have you believe that anyone not providing a finalized price within that band is poisoning the oracle. This is ridiculously stupid. This also ignores the fact that if everyone provided exactly the same price, then every provider would only have 50% primary band accuracy because then every provider would be on the edge, just like happens often on the stablecoin feeds.. You see, believing that being in the primary band makes you superior is a fundamental misunderstanding of what makes a good oracle system. Chasing the perfect consensus price is actually worse for stability and reliability. A good oracle system needs a little diversity in methodology. Demanding that every single provider continue to progressively iterate and expand while incurring greater and greater costs is absurd. The secondary band for that Round on XRP was $1.33235-$1.33475 which is a spread of $0.0024 meaning that providers had to supply a price within $0.0012 of the consensus price to receive any rewards. That is HIGHLY accurate. As someone who runs products that actually use these price feeds, an "accuracy" within 0.09% of the consensus price is far far beyond the necessary accuracy for price feeds. Almost every single provider is hitting that secondary band over 90% of the time across all feeds. Not every provider needs to be a no-life enthusiast. Good enough is, in fact, good enough, and stability counts for far more than "accuracy." The FTSO system created by @FlareNetworks and @HugoPhilion is working incredibly well, with a proven track record of accuracy and stability. Don't listen to the alarmists. FIP.16 will in no way damage the FTSO.
8
16
2
71
2,434
LightFTSO ☀️ retweeted
Im working with the content team to create material to thoroughly explain the governance proposal. Will release both after the Easter break so as not to send it out into a period where many are not paying attention.
46
127
18
538
25,849
LightFTSO ☀️ retweeted
The Flaredev account has been compromised. Do not interact. Do not click any links.
218
18
493
30,236
LightFTSO ☀️ retweeted
¿Pensabas que no íbamos a sumar más criptos? 🤔 ¡Para nada! Tú lo pediste y a partir de hoy tenemos +130 criptos en Bitso. 🚀 Hoy le damos la bienvenida a 20 criptos 👉 XCN, 1INCH, IMX, SUPER, STRK, FLOW, XTZ, MINA, MORPHO, HNT, AIOZ, EGLD, KSM, CVX, ROSE, AKT, FLR, GNO, VTHO y AXL. Tu próxima inversión está más cerca que nunca: encuentra estas criptos y muchas más en la app. ¿Lo mejor? Puedes comprarlas al instante con tus pesos.
34
12
3
96
6,961
LightFTSO ☀️ retweeted
It's fast. It's liquid. Now it's yield hungry. XRP on Flare.
79
390
30
2,031
124,137
The recent issue has been identified. To restore full network functionality, all validators and observer nodes must upgrade to the latest version v1.11.0 as soon as possible. hub.docker.com/layers/flaref… github.com/flare-foundation/… Thank you for your swift action and continued support.
9
38
12
133
20,001
LightFTSO ☀️ retweeted
If your not happy about the wait for FTSO rewards on @FlareNetworks post who you delegate or stake to below and I will tell you if your part of the problem.
61
15
4
75
11,328
LightFTSO ☀️ retweeted
The data must flow! Flare Foundation proposes updates to enhance the FTSO reward system, ensuring sustainability and fairness for all data providers. Learn about these changes and be ready to vote on Nov 18th: proposals.flare.network/FIP/…
9
93
9
301
32,033
LightFTSO ☀️ retweeted
FTSOv1 is now deprecated on Songbird. Starting today, all inflation rewards will transition to v2. Data providers can submit updates until the end of the reward epoch on Saturday, October 26th, after which they can claim rewards and cease providing prices for v1. For v2, 70% of the rewards will go towards anchor feeds, while 30% will be allocated to block-latency feeds. Providers should switch to the FTSOv2 contract on both Songbird and Flare as soon as possible. Users are advised to delegate to providers supporting v2. Please check registered entities at our systems explorers. ▸ songbird-systems-explorer.fl… ▸ flare-systems-explorer.flare… Learn more about the upgrade of FTSO and the benefits it brings to the Flare ecosystem: flare.network/ftsov2-more-da…
8
105
12
374
30,180
LightFTSO ☀️ retweeted
Introducing Flare Time Series Oracle v2 More data, delivered faster. Free to query any crypto feeds that are as secure as the network. Now on @FlareNetworks mainnet ☀️ bit.ly/4gtazY0
113
539
58
1,867
8,332,287
LightFTSO ☀️ retweeted
Get ready for FIP.09, a proposal to fuel the growth of the Flare ecosystem ☀️ Flare Foundation introduces a framework to distribute an initial 510 million $FLR from the 20 billion incentive pool to attract builders & support liquidity on @FlareNetworks. flare.network/fip-09-introdu…
33
211
22
543
38,771
LightFTSO ☀️ retweeted
Top performing providers on v2 over the past 6 hours. #FTSOv2 #Flare
3
6
1
26
1,750
LightFTSO ☀️ retweeted
flare.network/list-of-data-p… This list shows all FTSO data providers that are already supporting the upgraded FTSO and therefore have the maximum amount of rewards available to them and their delegators. We will update the list as new data providers add their support. For more details on the upgrade and its implications, please refer to the full proposal: proposals.flare.network/STP/…
11
75
11
211
39,046
LightFTSO ☀️ retweeted
The FTSO is undergoing a significant upgrade. The first step is the implementation of the Flare Systems Protocol and FTSO scaling on #Songbird, which started with the approval of STP.06 on March 5. This will enable the FTSO to provide developers with up to 1000 data feeds, updated every 90 seconds. The implementation has three phases. 1. We are currently in the trial phase where all inflation rewards are still allocated to data providers supporting the previous version of the FTSO. 2. On Thursday June 6th, we will transition to phase 2. FTSO rewards will be shared equally between data providers supporting the previous and the upgraded versions of the FTSO - 50% for each group. 3. In the final phase, all rewards will be provided to data providers supporting the upgraded FTSO. Action required for FTSO data providers: To receive the full available Songbird reward amount, FTSO data providers must update their systems to also support the upgraded FTSO and FTSO scaling. Impact on delegators: If your $SGB tokens are delegated to a data provider that does not support the upgraded FTSO, you will receive 50% fewer rewards. We will maintain a list of FTSO data providers that have upgraded to allow delegations to be moved if desired. Reminder: As described in STP.06, epoch times for the upgraded FTSO on Songbird are now aligned with Flare. This means there are two reward epochs per week instead of one.
20
142
19
568
61,882
LightFTSO ☀️ retweeted
We're not fans of announcements of announcements. But FAssets is something special. Updates coming next week. ☀️
90
285
87
1,129
229,115
LightFTSO ☀️ retweeted
Replying to @4DadsFtso
You can thank @lightFTSO for the enums.. he didn’t like our prefix ideas
1
1
2
172