Coffee FTSO Flare address: 0xf5bD8783dEb2c729B46eF2cF031e96FFe57a3a2F and Songbird address: 0x0E6BF04a77b8480D93d32A19Ff1ea63c315A60C2 (not submitting)
The evidence produced relates common spikes on Flare network across all pairs, many more examples exist.
Coffee FTSO will be invited and asked to provide feedback.
5 Likes
Wow those are pretty damning. Hopefully coffee joins to give an explanation.
3 Likes
Good charts, thanks for compiling, agree with @Brent-4Dads — we support a chill
3 Likes
Sirius
June 25, 2023, 3:56pm
4
As I wanted in the past, I support chilling these providers.
3 Likes
We support chilling these providers also.
2 Likes
I support the chilling of these providers.
1 Like
The collusion between these providers is largely apparent based on the presented evidence. Will wait for response from CoffeFTSO
1 Like
I agree with both FTSOs being chilled.
1 Like
The evidence is undeniable.
1 Like
I support chilling these providers
1 Like
Chilling for both ftsos supported by our team.
1 Like
I support the chill for these providers.
1 Like
We also agree with chilling these FTSO’s.
1 Like
O1FTSO
June 27, 2023, 1:19am
16
I support chilling both providers
1 Like
nortso
June 27, 2023, 6:35am
17
I support this. It’s clear that this provider is running an existing high-performance algorithm and the provider has made no effort to make it look like an independent one
1 Like
We Support chilling both providers.
2 Likes
we support chilling both providers.
2 Likes
bushi supports chilling both providers.
2 Likes