Jump to content

Bug found on Flare's FTSO Reward Manager Contract: it's not the same as the one on Canary Songbird LOL


Gringo
 Share

Recommended Posts

This:

So everyone ask the OBVIOUS question:

image.thumb.png.cfedeceaed33e4ba36e9bf664719f55b.png

The WHOLE point of a Canary Network is to TEST on real live conditions so it can be later deployed to the MAIN Network.

But clowns lead by Hugo at Flare decided to "slightly change" the code on FLR and now they been found with their pants down, as the code on Flare had a bug.

So all the narrative of Songbird as the Canary Network is down the toilet.

season 6 dancing GIF

Link to comment
Share on other sites

Quote

Reality is that SGB 90% a Plan B network, 10% lets test that sh*t.

It has attracted many cool NFT's projects though (I mean the idea of using the EVM but on a fast network with AVAX tech is a winner). I still should start like 5 more topics of specific ones (unfortunately the "Forum" format is not that popular these days, so I don't want to post too many deserted topics). At current market conditions their tokenomics are acceptable ("utility" NFTs).

I feel that many programmers behind the top tier NFTs projects are more capable that the ones responsable for Flare development, kinda weird.

Link to comment
Share on other sites

1 hour ago, Gringo said:

It has attracted many cool NFT's projects though (I mean the idea of using the EVM but on a fast network with AVAX tech is a winner). I still should start like 5 more topics of specific ones (unfortunately the "Forum" format is not that popular these days, so I don't want to post too many deserted topics). At current market conditions their tokenomics are acceptable ("utility" NFTs).

I feel that many programmers behind the top tier NFTs projects are more capable that the ones responsable for Flare development, kinda weird.

And this is why it is Plan B. I will not be surprised if it also has been done to untight some undesired connections in FLR, but its just me with regular dot connections.

Link to comment
Share on other sites

As always they communicate in a very confusing way. It seems rewards for the current Songbird Epoch wont be affected as they will be distributed next Saturday using a new Rewards Manager contract.

All previous Epochs from both SGB and FLR that were not claimed are currently "kidnapped". They will try find a way to distribute those.

So far I am lucky since I was trying the "autoclaim" feature on FLR (so I got the rewards before they disabled the Rewards Manager) and had claimed all the previous Epochs from Songbird.

All of this could have been avoided if they f.... used the Canary Network as a f... Canary Network.

frustrated the wire GIF

Link to comment
Share on other sites

Update: Since the Rewards Manager on the ongoing Epoch (Epoch 71) was halted and changed for a new Rewards Manager contract, part of those pending rewards was "kidnapped" and is controlled by the deprecated RM, so I am (everyone) finally hit by this incident.

Most sites reflect the current real pending rewards on the new contract, but some seem to still be using the old contract as parameter, for example flaremetrics.io (there you still can see the amount of your kidnapped SGB for Epoch 71)

Link to comment
Share on other sites

Update, from Discord:

image.thumb.png.93940ece5a568090eaccefc7b43556cf.png

Also "expired rewards" (rewards that remain unclaimed for more than 90 days) do not really "expire". Those are sent back to the rewards pool.

Songbird had about 20 M SGB rewards unclaimed. A % of those unclaimed rewards turned into "expired" rewards each Epoch. Those "expired" rewards were then available on the rewards pool of the current Epoch.

Since the rewards manager contract was changed, the "expired" rewards from those 20 M SGB are not available on the current Epoch. Therefore since "expired" rewards from older Epochs are not being redistributed, then the current Epoch rewards are lower. So until the new rewards manager contract turns at least 90 days old, no expired (unclaimed) rewards will be redistributed.

This whole event is causing a 90-day period of "lower inflation" on Songbird. 

Link to comment
Share on other sites

 Share

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.