Thanks for confirming this.
The timeline’s don’t match up. @O1FTSO and Daniel himself speak of parting ways 2yrs ago yet you say he was “working for the O1 provider while with us” yet you only entered the game a year ago? When and how did you discover this?
We appreciate any information you’re willing to supply.
Oh sorry for the confusion. Mistake on writing
I am not sure if he was working for both providers.
Shortly after we announced that we were operating a provider on the Songbird network, Daniel came across our team.
I think this happened in May of last year.
Lol, I think you should check your grammar before posting.
It must be ~6am in Norway … 
While taking a look on the codebase, I found “O1” logo in the web app.
And also during those days, Daniel really disliked O1FTSO, and when I asked him why, he said that he left the team due to bad issues.
Yep. You are right.
What’s up?
He might be a night owl
24-Hour Notice - This will be put to an on-chain vote on July 3rd.
Recapping all replies denying collusion from Fly2Sonic, only to then have an admission, is a last-ditch attempt to save their cash cow, O1 FTSO.
Mikyoch, previously involved with collusion and having Flare Ocean and Fly2Sonic in their portfolio before quickly making it private and taking down their website, further confirms that these providers are all linked more deeply than they admit.
There will be 3 proposals for voting on Songbird (Fly2Sonic, O1 FTSO, Flare Ocean) and 2 proposals on Flare (Flare Ocean and O1 FTSO).
We fully support this post to be pushed towards chilling .
Despite the clear evidence presented, proceeding with the vote can only be seen as an act of discrimination against O1FTSO. I strongly urge the flare community to investigate my node and algorithm before the second chilling starts.
Evidence and responses seems fishy. Currently in support of chill and will keep eye out for last minute discussions.
Thankfully there’s upstanding guys in the community who know what’s right and wrong and don’t take these guys up on their offer.
Indeed, this proposal has been edited as the case against the providers developed and more information came to light.
Discourse saves the history and edits for everyone to see; I have nothing to hide.
Sure, I will run a new provider if O1 FTSO is chilled.
Songbird
Fly2Sonic ID 26 = Transaction 0x5cbbcdc7c37bfa02c8826db50a3bdc0203e28c0032278d9f9ad3892aa851418a - Songbird Canary-Network Explorer
O1FTSO ID 27 = Transaction 0x2c696d0836d0cc63fa41566311023a23e3514e47fa3b5d4cf0ad949f973be395 - Songbird Canary-Network Explorer
Flare Ocean ID 28 = Transaction 0xd8ea516f2d50eb693c15d6665f6d60f1f89abd23430cf78cc1f534775d43e1e1 - Songbird Canary-Network Explorer
Flare
O1FTSO ID 19 = Transaction 0xdfa180a8c4d2305967a468cf9b20096ef3112f9f8456fb951db821eab77cf4ac - Flare Mainnet Explorer
Flare Ocean ID = 20 Transaction 0x74b471c7271fad6058fe865b95ca4fc13f246c2b2ccd5e47585947312708398d - Flare Mainnet Explorer
What does it mean that you are ready to share the algorithm with the community? Please do then.
