All Quiet on the Songbird Front

[Seoulite]

So it's been a couple of weeks where it seems nothing is happening (publicly) with Songbird. Does anyone know if the 'testing' of the FTSO is still going on? Has the State Connector testing even started? I am impatient, as we all are, out of excitement not criticism. I haven't been following the telegram/discords as closely recently so wondering if anyone has heard rumours.

 

[brianwalden]

5 hours ago, Seoulite said:

So it's been a couple of weeks where it seems nothing is happening (publicly) with Songbird. Does anyone know if the 'testing' of the FTSO is still going on? Has the State Connector testing even started? I am impatient, as we all are, out of excitement not criticism. I haven't been following the telegram/discords as closely recently so wondering if anyone has heard rumours.

 

Seriously. The more I wait the more I find other things to get into. I'm becoming more degen every day.

[ftso_au]

6 hours ago, Seoulite said:

Does anyone know if the 'testing' of the FTSO is still going on?

There was an FTSO Monitor tool released to us about 9 days ago, I believe it’s being made public now. I think Flare Community are doing a YT video on it tonight. 

That should keep you busy for a few days. 

[inXs]

I believe each service test completion such as FTSOs is made dependent on the auditor signoff.

Edited November 11, 2021 by inXs

[Seoulite]

9 hours ago, FTSO_AU said:

There was an FTSO Monitor tool released to us about 9 days ago, I believe it’s being made public now. I think Flare Community are doing a YT video on it tonight. 

That should keep you busy for a few days. 

 

[Seoulite]

14 minutes ago, Seoulite said:

 

I welcome more data. That will always be good. And narrowing the gap between providers will also be good, though I don't imagine some of the more successful providers are too happy about that. 

I take issue with the end of the video, which says nothing but Flare will launch when it launches. I get saying this to people who care for nothing but getting their tokens as fast as possible, but for the rest of us this isn't a very satisfactory answer. Not that Flare has to satisfy us, but this is a forum for discussion so let's discuss.

We can say Hugo should never have given a timetable. OK, fair enough. But he did, and we are now well, well past it. So this raises a few possibilities:

1) Hugo, one of the leaders of the Flare team, had very little idea of the actual timeframes involved (unlikely)

2) The launch has experienced some setbacks which has caused delays - this could include anything from security to the design to legality 

Given the ever stretching timeline, it is reasonable to be curious. 

[BillyOckham]

8 minutes ago, Seoulite said:

1) Hugo, one of the leaders of the Flare team, had very little idea of the actual timeframes involved (unlikely)

We disagree on this.   I think it’s the most likely reason.

We don’t have to look far to find tons of examples of people underestimating the time required to bring a project to fruition.

But I don’t disagree that some unexpected headwinds may have popped up.  If I had to bet I would put money on regulation fears in the wake of new wells notices to other groups.

But time will tell.

[Guest]

2 hours ago, Seoulite said:

I welcome more data. That will always be good. And narrowing the gap between providers will also be good, though I don't imagine some of the more successful providers are too happy about that. 

I take issue with the end of the video, which says nothing but Flare will launch when it launches. I get saying this to people who care for nothing but getting their tokens as fast as possible, but for the rest of us this isn't a very satisfactory answer. Not that Flare has to satisfy us, but this is a forum for discussion so let's discuss.

We can say Hugo should never have given a timetable. OK, fair enough. But he did, and we are now well, well past it. So this raises a few possibilities:

1) Hugo, one of the leaders of the Flare team, had very little idea of the actual timeframes involved (unlikely)

2) The launch has experienced some setbacks which has caused delays - this could include anything from security to the design to legality 

Given the ever stretching timeline, it is reasonable to be curious. 

I think it could be #1 due to scale issues and I am comfortably okay with it. Projects get delayed all the time. When there are less severe consequences, teams choose between pushing the deadline and cutting down features. With blockchain, especially given that you cannot really patch code quickly once it is live, I can understand why they are being more deliberate.

Also, there is no good way to test scale internally. It can only be done in the real world. And people use software is the most crazy ways you’d imagine and in ways developers never intend them to. Asynchronous software is even harder to test and when there’s an issue, it’s super hard to debug. In addition, with a world wide network, there are bound to be other problems like clock synchronisation, inconsistent bandwidth challenges (high latency high speed, low latency high speed, low latency low speed and high latency low speed). Then there is the whole bridging with other networks business, availability of liquidity etc.

In conclusion, I would attribute it to “didn’t anticipate how complex it was going to be” but I wouldn’t chart it to incompetence. Path to production is always hard.