Resonance ☀️

248 posts

Resonance ☀️ banner
Resonance ☀️

Resonance ☀️

@resonanceoracle

Signal Provider for Flare Networks • Tune in! 🔊

Katılım Temmuz 2025
44 Takip Edilen81 Takipçiler
Sabitlenmiş Tweet
Resonance ☀️
Resonance ☀️@resonanceoracle·
What have we been up to for the last 4½ months? • Validated 6,700,000+ blocks on @FlareNetworks☀️ • Verified 500,000+ FDC attestation requests (a big chunk used for FAssets) • Submitted 8,000,000+ prices to FTSO Resonance has been busy. 💜🔥 #FlareFam #FlareCommunity
Resonance ☀️ tweet media
English
0
0
9
405
Resonance ☀️ retweetledi
amiiiii ☀️
amiiiii ☀️@_WaterAmi·
XRP fam in Vegas showed how it feels now: vindicated, eager to know what comes next. Meanwhile on Flare: @Thana_Enosys didn't ask permission, built the first keeper-free DEX limit orders on Flare, making enshrined data actually shine. @FlareDevHub teases txs running inside TEE. quietly rewriting what's possible. FIP.16 passed with the highest governance participation ever. (@resonanceoracle tracked it) 100 nodes humming, supporting the network as it expands. Community proposals coming in unprompted, asking how they can contribute. >> Not reactive. generative. Many hold XRP through cycles. These? They build on @FlareNetworks to prove XRP can be more.
English
5
24
106
3.7K
Resonance ☀️ retweetledi
Flare ☀️
Flare ☀️@FlareNetworks·
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.
Flare ☀️ tweet media
English
70
135
463
56.8K
Resonance ☀️ retweetledi
Erik Martínez - Bus Nodes
Erik Martínez - Bus Nodes@erikmartinez28·
FIP.16 passes in ~48h, a win for $FLR holders: - Inflation drops from 5% to 3% - Staking gets a 5x weight multiplier over delegation - MEV, FAssets, FCC, FDC fees all feeding into FIRE #Flare is building for the long term. Proud to be an #FTSO provider. 🔥
English
6
32
198
6.9K
Resonance ☀️ retweetledi
Darren "Thanasimos" Williams
Darren "Thanasimos" Williams@Thana_Enosys·
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.
English
8
16
71
2.4K
Resonance ☀️ retweetledi
Quantic
Quantic@0xQuantic·
Another day, another TVL ATH.
Quantic tweet media
English
4
26
150
3.5K
Flare ☀️
Flare ☀️@FlareNetworks·
A new governance proposal is live: Introduce $FLR Value Capture Framework What it’s about: • Lower inflation: Annual inflation falls from 5% to 3%, and the yearly inflation hard cap drops from 5B FLR to 3B FLR. • Stronger fee burn: the base gas fee rises 20x, from 60 gwei to 1200 gwei, resulting in est. 300M FLR burned per year at current transaction levels. • Protocol-level revenue accrual and FIRE setup: Establish a framework to collect flows from protocol fees and captured MEV from DeFi activity on Flare with scope to further reduce annual inflation. proposals.flare.network/FIP/FIP_16.html
Flare ☀️ tweet media
English
94
278
792
192.9K
Resonance ☀️ retweetledi
AU
AU@aucc_official·
We’re looking at midweek for the codename “Radical” FIP to be released. When it does, take the time to read it thoroughly, and more than once, before jumping to conclusions or asking questions. 📚
Hugo Philion@HugoPhilion

@CryptonistNord @FlareNetworks Today is Easter Monday. Tomorrow is “power and bridges day” - which seems like a poor day to choose. Wednesday or Thursday seem more sensible.

English
6
15
61
2.2K
Resonance ☀️ retweetledi
Filip Koprivec (j☀️☀️sko)
Looking forward to the next iteration of FAssets - much more user friendly, with broader wallet support and no time constraints. Imagine this: withdrawing XRP from an exchange directly mints FXRP. Users withdraw XRP, send it to a designated address with a tag, and receive FXRP straight into their Flare wallet. Who wants this?
English
10
52
185
10.2K
Resonance ☀️ retweetledi
AU
AU@aucc_official·
Lots of new data to explorer on @flaremetrics including an updated provider list which will please many of our peers. Unrealistic / unsustainable reward rates above 15% APR are no longer shown. As always, delegate and stake responsibly. Check it out … flaremetrics.io
Tim Rowley ☀️@timrowley

Flare Metrics is still alive and better than before. I've had to rebuild this platform many times due to the ever changing environment on Flare (particularly the early years). Still some work to do, but it needed a refresh to provide accurate information and it's weight off my conscious when it is providing good and trustworthy data. One of the new features is a distribution of stake between countries and ASNs (these are the cloud providers the validators use to run their infrastructure). It helps gauge the networks health as too much stake placed in a single region or ASN could impose on the networks decentralization. Additionally you for both validator and FTSO pages you will see "passes". These are tokens that allow forgiveness to providers so they can continue to earn rewards in cases of downtime or system failures. Passes are consumed on any negative behavior and only earned (max 3) for good performance. On the FTSO table you will also see a new column we are experimenting with called "Rate CV". This number represents the reward rates coefficient volatility; in other words, the intensity of the reward rate fluctuation. A lower CV indicates a more stable reward rate, while a higher one indicates large inflow and outflows of vote power (a quick note on why this is important: you may see an attractive reward rate, but if a massive amount of VP floods the provider, you will not reap the benefits of that initial reward rate). So typically a lower CV means a more stable reward rate. You can also now click onto individual providers to see more detailed information about them including historical minimum condition performance (this is what affects passes and provides an indication of past performance). There still is some work to be done, any suggestions and feedback is welcome.

English
1
8
31
1.3K
Resonance ☀️ retweetledi
Flare Devs
Flare Devs@FlareDevHub·
Flare Systems Explorer lets you analyze protocol-level activity across FTSO and FDC, and even track Smart Accounts activity tied to XRPFi. For users, it’s the go-to place to understand how Flare’s core systems are performing. For builders, it’s a live window into the data layer their dApps depend on. Learn more here: flare-systems-explorer.flare.network
Flare Devs tweet media
English
1
23
82
6.7K
Resonance ☀️
Resonance ☀️@resonanceoracle·
Network update v1.13.0 is coming soon on @FlareNetworks! We’ve already done our part and upgraded our validator and RPC nodes — ready for the rollout ✅
Resonance ☀️ tweet media
English
0
0
4
65
Resonance ☀️ retweetledi
Flare ☀️
Flare ☀️@FlareNetworks·
Intro to TEEs on Flare: how it works and why it’s core to what we’re building. Secure computation in a sealed environment. Proof that the code did what it said. Developer or not, you'll want to tune in. RSVP: luma.com/i4jzth8l
Flare ☀️ tweet media
English
8
82
298
46.2K