Hardcore Buidl-er. Co-Founder of AU (au.cc) @aucc_official
Joined May 2019
- Tweets 2,929
- Following 200
- Followers 6,047
- Likes 5,147
120 Photos and videos
Pinned Tweet
Jun 10
This is the MOST OVERLOOKED metric costing Flare stakers & delegators rewards right now.
Anyone staking to Flare validators or delegating to providers must be aware of the “minimum conditions” introduced in the last major FTSO update. Although this system has been in place for some time.
If you're delegating FLR, understanding these conditions and their impact on your rewards is crucial.
Every reward epoch, each entity (data providers/validators), is graded on their performance and either earn or lose "passes".
This is a system that decides if the entity (and their delegators) will keep their rewards.
They are judged on four protocols (conditions):
1⃣ FTSO (anchor feeds): Submit prices close the consensus median within a 0.5% band in at least 80% of rounds.
2⃣ FTSO (block-latency feeds): Submit at least 80% of expected updates (based on entities weight, entities with <0.2% of total wait are exempt).
3⃣ FDC (data connector): Participate successfully in 60% of rewarded rounds.
4⃣ Validators (staking): Validator must maintain 80% uptime and maintain at least 1m FLR self-bond.
Passes are like "get out of jail free" cards, and each entity can have at 3 passes at most.
When an entity fails to meet any one of the previously mentioned conditions, they lose a pass. Rewards are not at risk so long as the entity finishes a reward epoch with at least 0 or more passes.
In other words, an entity may fail at most 3 of the conditions and still be eligible for rewards. But if they fail all 4 conditions or have no passes AND fail a condition, their rewards are burned for that reward epoch (again, including their delegators).
All entities start with 0 passes and can earn passes (up to 3) by meeting all conditions for a given reward epoch.
There is a small caveat for entities to earn additional passes which is that they must have 3M FLR self-bond AND 15M FLR total active stake. This applies only for earning passes and does not lose strikes (as noted, only 1M FLR self-bond is required to meet the minimal staking condition.
For clarity, a provider who doesn't meet minimal conditions and has no passes will have all their reward burned, not just for individual protocols they fail, but for ALL. This includes "delegation" to data provider AND validator delegations.
It is typically okay for a provider form time to time to lose a pass, so it is more important to view the providers HISTORY of minimum conditions.
How quickly did they regain passes? Do they often lose passes?
Where can you see this? Flare Metrics.
4
16
64
10,492
Tim Rowley ☀️ retweeted
Jun 12
Inflation, daily transaction fees, FLR burned by each protocol.
We track the progress of our ecosystem to ensure everyone in the community can stay informed: dune.com/flare/tokenomics
3
19
70
1,376
Tim Rowley ☀️ retweeted
Jun 11
New USDT0 vault on Flare!
Jun 11
Stablecoins on Flare aren't idle — they're earning.
@USDT0_to is the omnichain stablecoin powering XRPFi on Flare.
Now accessible as a USDT0 yield vault through @superformxyz, curated by @bizantinelabs.
4
72
323
12,859
Tim Rowley ☀️ retweeted
Jun 11
I think Flare users should review provider history on flaremetrics.io to assess consistency in meeting conditions, as repeated failures can lead to lost rewards even if individual protocols perform adequately.
Jun 10
This is the MOST OVERLOOKED metric costing Flare stakers & delegators rewards right now.
Anyone staking to Flare validators or delegating to providers must be aware of the “minimum conditions” introduced in the last major FTSO update. Although this system has been in place for some time.
If you're delegating FLR, understanding these conditions and their impact on your rewards is crucial.
Every reward epoch, each entity (data providers/validators), is graded on their performance and either earn or lose "passes".
This is a system that decides if the entity (and their delegators) will keep their rewards.
They are judged on four protocols (conditions):
1⃣ FTSO (anchor feeds): Submit prices close the consensus median within a 0.5% band in at least 80% of rounds.
2⃣ FTSO (block-latency feeds): Submit at least 80% of expected updates (based on entities weight, entities with <0.2% of total wait are exempt).
3⃣ FDC (data connector): Participate successfully in 60% of rewarded rounds.
4⃣ Validators (staking): Validator must maintain 80% uptime and maintain at least 1m FLR self-bond.
Passes are like "get out of jail free" cards, and each entity can have at 3 passes at most.
When an entity fails to meet any one of the previously mentioned conditions, they lose a pass. Rewards are not at risk so long as the entity finishes a reward epoch with at least 0 or more passes.
In other words, an entity may fail at most 3 of the conditions and still be eligible for rewards. But if they fail all 4 conditions or have no passes AND fail a condition, their rewards are burned for that reward epoch (again, including their delegators).
All entities start with 0 passes and can earn passes (up to 3) by meeting all conditions for a given reward epoch.
There is a small caveat for entities to earn additional passes which is that they must have 3M FLR self-bond AND 15M FLR total active stake. This applies only for earning passes and does not lose strikes (as noted, only 1M FLR self-bond is required to meet the minimal staking condition.
For clarity, a provider who doesn't meet minimal conditions and has no passes will have all their reward burned, not just for individual protocols they fail, but for ALL. This includes "delegation" to data provider AND validator delegations.
It is typically okay for a provider form time to time to lose a pass, so it is more important to view the providers HISTORY of minimum conditions.
How quickly did they regain passes? Do they often lose passes?
Where can you see this? Flare Metrics.
3
10
73
2,396
Tim Rowley ☀️ retweeted
Jun 10
This is the MOST OVERLOOKED metric costing Flare stakers & delegators rewards right now.
Anyone staking to Flare validators or delegating to providers must be aware of the “minimum conditions” introduced in the last major FTSO update. Although this system has been in place for some time.
If you're delegating FLR, understanding these conditions and their impact on your rewards is crucial.
Every reward epoch, each entity (data providers/validators), is graded on their performance and either earn or lose "passes".
This is a system that decides if the entity (and their delegators) will keep their rewards.
They are judged on four protocols (conditions):
1⃣ FTSO (anchor feeds): Submit prices close the consensus median within a 0.5% band in at least 80% of rounds.
2⃣ FTSO (block-latency feeds): Submit at least 80% of expected updates (based on entities weight, entities with <0.2% of total wait are exempt).
3⃣ FDC (data connector): Participate successfully in 60% of rewarded rounds.
4⃣ Validators (staking): Validator must maintain 80% uptime and maintain at least 1m FLR self-bond.
Passes are like "get out of jail free" cards, and each entity can have at 3 passes at most.
When an entity fails to meet any one of the previously mentioned conditions, they lose a pass. Rewards are not at risk so long as the entity finishes a reward epoch with at least 0 or more passes.
In other words, an entity may fail at most 3 of the conditions and still be eligible for rewards. But if they fail all 4 conditions or have no passes AND fail a condition, their rewards are burned for that reward epoch (again, including their delegators).
All entities start with 0 passes and can earn passes (up to 3) by meeting all conditions for a given reward epoch.
There is a small caveat for entities to earn additional passes which is that they must have 3M FLR self-bond AND 15M FLR total active stake. This applies only for earning passes and does not lose strikes (as noted, only 1M FLR self-bond is required to meet the minimal staking condition.
For clarity, a provider who doesn't meet minimal conditions and has no passes will have all their reward burned, not just for individual protocols they fail, but for ALL. This includes "delegation" to data provider AND validator delegations.
It is typically okay for a provider form time to time to lose a pass, so it is more important to view the providers HISTORY of minimum conditions.
How quickly did they regain passes? Do they often lose passes?
Where can you see this? Flare Metrics.
4
16
64
10,492
Tim Rowley ☀️ retweeted
May 26
We've seen impersonator accounts gaining traction across socials, and have been actively pursuing them.
Reminder: the following are our only official channels 👇
X — x.com/FlareNetworks
Telegram — t.me/FlareNetwork
Discord — discord.gg/flarenetwork
YouTube — youtube.com/c/Flare_Networks
GitHub — github.com/flare-foundation
LinkedIn — linkedin.com/company/flarene…
Medium — medium.com/flarenetwork
If it's not listed on flare.network/community, it's not us.
29
89
262
29,176
Tim Rowley ☀️ retweeted
Jun 10
🚨 Only 16 people have bookmarked this, but people are still DMing me almost every day after falling for fake links.
Please share this, bookmark it, and use it as a reference to stay safe in the ecosystem.
May 26
We've seen impersonator accounts gaining traction across socials, and have been actively pursuing them.
Reminder: the following are our only official channels 👇
X — x.com/FlareNetworks
Telegram — t.me/FlareNetwork
Discord — discord.gg/flarenetwork
YouTube — youtube.com/c/Flare_Networks
GitHub — github.com/flare-foundation
LinkedIn — linkedin.com/company/flarene…
Medium — medium.com/flarenetwork
If it's not listed on flare.network/community, it's not us.
1
18
88
2,434
Tim Rowley ☀️ retweeted
Jun 10
Important read if you delegate/stake on Flare and don't know what "minimum conditions" are. Visit Flare Metrics to see entities passes and min. condition history.
Jun 10
This is the MOST OVERLOOKED metric costing Flare stakers & delegators rewards right now.
Anyone staking to Flare validators or delegating to providers must be aware of the “minimum conditions” introduced in the last major FTSO update. Although this system has been in place for some time.
If you're delegating FLR, understanding these conditions and their impact on your rewards is crucial.
Every reward epoch, each entity (data providers/validators), is graded on their performance and either earn or lose "passes".
This is a system that decides if the entity (and their delegators) will keep their rewards.
They are judged on four protocols (conditions):
1⃣ FTSO (anchor feeds): Submit prices close the consensus median within a 0.5% band in at least 80% of rounds.
2⃣ FTSO (block-latency feeds): Submit at least 80% of expected updates (based on entities weight, entities with <0.2% of total wait are exempt).
3⃣ FDC (data connector): Participate successfully in 60% of rewarded rounds.
4⃣ Validators (staking): Validator must maintain 80% uptime and maintain at least 1m FLR self-bond.
Passes are like "get out of jail free" cards, and each entity can have at 3 passes at most.
When an entity fails to meet any one of the previously mentioned conditions, they lose a pass. Rewards are not at risk so long as the entity finishes a reward epoch with at least 0 or more passes.
In other words, an entity may fail at most 3 of the conditions and still be eligible for rewards. But if they fail all 4 conditions or have no passes AND fail a condition, their rewards are burned for that reward epoch (again, including their delegators).
All entities start with 0 passes and can earn passes (up to 3) by meeting all conditions for a given reward epoch.
There is a small caveat for entities to earn additional passes which is that they must have 3M FLR self-bond AND 15M FLR total active stake. This applies only for earning passes and does not lose strikes (as noted, only 1M FLR self-bond is required to meet the minimal staking condition.
For clarity, a provider who doesn't meet minimal conditions and has no passes will have all their reward burned, not just for individual protocols they fail, but for ALL. This includes "delegation" to data provider AND validator delegations.
It is typically okay for a provider form time to time to lose a pass, so it is more important to view the providers HISTORY of minimum conditions.
How quickly did they regain passes? Do they often lose passes?
Where can you see this? Flare Metrics.
3
8
644
Jun 10
This is the MOST OVERLOOKED metric costing Flare stakers & delegators rewards right now.
Anyone staking to Flare validators or delegating to providers must be aware of the “minimum conditions” introduced in the last major FTSO update. Although this system has been in place for some time.
If you're delegating FLR, understanding these conditions and their impact on your rewards is crucial.
Every reward epoch, each entity (data providers/validators), is graded on their performance and either earn or lose "passes".
This is a system that decides if the entity (and their delegators) will keep their rewards.
They are judged on four protocols (conditions):
1⃣ FTSO (anchor feeds): Submit prices close the consensus median within a 0.5% band in at least 80% of rounds.
2⃣ FTSO (block-latency feeds): Submit at least 80% of expected updates (based on entities weight, entities with <0.2% of total wait are exempt).
3⃣ FDC (data connector): Participate successfully in 60% of rewarded rounds.
4⃣ Validators (staking): Validator must maintain 80% uptime and maintain at least 1m FLR self-bond.
Passes are like "get out of jail free" cards, and each entity can have at 3 passes at most.
When an entity fails to meet any one of the previously mentioned conditions, they lose a pass. Rewards are not at risk so long as the entity finishes a reward epoch with at least 0 or more passes.
In other words, an entity may fail at most 3 of the conditions and still be eligible for rewards. But if they fail all 4 conditions or have no passes AND fail a condition, their rewards are burned for that reward epoch (again, including their delegators).
All entities start with 0 passes and can earn passes (up to 3) by meeting all conditions for a given reward epoch.
There is a small caveat for entities to earn additional passes which is that they must have 3M FLR self-bond AND 15M FLR total active stake. This applies only for earning passes and does not lose strikes (as noted, only 1M FLR self-bond is required to meet the minimal staking condition.
For clarity, a provider who doesn't meet minimal conditions and has no passes will have all their reward burned, not just for individual protocols they fail, but for ALL. This includes "delegation" to data provider AND validator delegations.
It is typically okay for a provider form time to time to lose a pass, so it is more important to view the providers HISTORY of minimum conditions.
How quickly did they regain passes? Do they often lose passes?
Where can you see this? Flare Metrics.
4
16
64
10,492
Jun 10
You can visit flaremetrics.io and click on a providers name (from FTSO or Validator page) to view their full minimum conditions history. You can also see the current passes at a glance in the tables.
13
485
May 26
RT @aucc_official: FAssets will be paused in about an hours time, for 30 minutes, due to scheduled maintenance. 👨💻
3
Tim Rowley ☀️ retweeted
May 26
Epoch 400 saw the first reduction in FTSO rewards as a result of FIP.16 changes, specifically the reduction in inflation from 5% to 3%.
This means average network delegation (FTSO rewards) APR has dropped from ~7% to ~4%.
Staking rewards have also been reduced. Some of you have already noticed, and the rest no doubt will when the next full (4 epoch) distribution is made on or around June 3rd.
We’re expecting an official announcement soon regarding the signing weight adjustment, which will see a higher weight assigned to P-chain stake, initially set at 5x relative to C-chain power.
This will further reduce delegation APR and shift a larger portion of rewards toward staking. With staking already yielding roughly 2x delegation APR, these changes will make staking considerably more lucrative relative to delegation.
Current Delegation v Staking rewards comparison;
6
15
57
5,461
May 20
RT @aucc_official: If you held an active stake during epochs 394-397 you can now claim your rewards.
Thanks to all who choose to stake wit…
3
May 19
RT @aucc_official: Our node’s been updated to 3.1.3 ahead of the deadline and our FDC attestation suite is fully operational. 👨💻
1
May 17
RT @aucc_official: Keep an eye on these numbers. We expect to see an increase in staking as more of the changes from FIP.16 are implemented…
6
Tim Rowley ☀️ retweeted
May 14
I just minted FXRP directly to Flare from @krakenfx @krakenpro
Have you?
It was super simple. Give it a go!
Buy a tag on any of the FXRP minting apps and follow the very simple instructions.
You can do this from any exchange that supports XRP.
40
172
577
25,536
Tim Rowley ☀️ retweeted
May 14
FAssets v1.3 is live on mainnet.
Minting FXRP = one XRPL transaction.
Reserve a destination tag once, and every mint after is just an XRP withdrawal. Works from any exchange — Binance, Kraken, OKX, Upbit, Bithumb, all of them.
Billions of XRP are sitting on CEXs. @FlareNetworks is the only chain that reaches them in one step.
139
217
748
166,999
May 14
RT @aucc_official: Tomorrow’s rewards will be the last at the current 5% inflation, from Monday they’ll be based on 3%.
6
Tim Rowley ☀️ retweeted
May 14
Mainnet is close.
FAssets v1.3 — direct minting, tag-based routing, governed flow.
Details land next. Read up on it on the Dev Hub.
→ dev.flare.network/fassets/di…
69
81
361
18,587
Tim Rowley ☀️ retweeted
May 10
Find your local Flare community on flare.builders. ☀️
Connect with passionate Flaresians near you and around the world!
flare.builders/communities
11
28
100
10,908
Tim Rowley ☀️ retweeted
May 8
All fixed, thanks for the prompt attention @FlareDevHub 🙏
May 7
For some reason, our 4th validator is showing 0.00 in the Flare Portal, as are several others, despite earning rewards over the last 4 epochs.
The @FlareDevHub team is looking into the issue, and hopefully it will be resolved soon.
17
2
20
1,270