The maximum value engine upgrade is ready - when we should deploy?

[ipaleka]

Give your suggestions about the time and eventual announcements.

Yieldly announced ASASTATS staking pools for tomorrow/Monday and we should probably time that in regard to this upgrade: what if Yieldy's staking pools are going to be deployed tomorrow and what if they aren't?

[wxivd]

Congratulations for all of us. This is another milestone and I am really excited for this. Thank you

I think Monday is ideal. 6PM London time = 1PM New York time is worth considering.

Yieldy's staking pools are going to be deployed tomorrow and what if they aren't?

These two are separate announcements. If they happen on the same day that is a plus. If not, there is still enough reason to celebrate.

In terms on magnitude, I see engine upgrade is more important.

Yieldly announcement is welcome whenever it happens. I looked at their previous announcements and there is no regular time slot as per their Twitter account.

[ipaleka]

Congratulations for all of us. This is another milestone and I am really excited for this. Thank you

Yes, this is basically a cornerstone for our API. The thing is that this involves an order of magnitude more calculations so we had to optimize before implementation. And the outcome is that the increase in speed averages above 100%. :)

I think Monday is ideal. 6PM London time = 1PM New York time is worth considering.

Yieldy's staking pools are going to be deployed tomorrow and what if they aren't?

These two are separate announcements. If they happen on the same day that is a plus. If not, there is still enough reason to celebrate.

In terms on magnitude, I see engine upgrade is more important.

Ok, so your stance is that we should go tomorrow 6PM London time regardless of Yieldly. Thanks.

Yieldly announcement is welcome whenever it happens. I looked at their previous announcements and there is no regular time slot as per their Twitter account.

Before the first delay a few months ago they used to deploy at 01:30 CET, while in the last period that seems to be 07:00 CET (15:00 in Australia).

[ipaleka]

by Mayor | CM YouTube in Discord:

---

Probably not the correct channel but - I agree with 1pm EST deployment. That’s the most active “drop” time for NFTs and there is a lot of face-to-screen activity around that time

---

[ipaleka]

We used to have these announcements on Reddit, and then we linked them to Twitter and Discord. I suppose we should switch here from now on - we already have got that "Announcements" category. :)

[ipaleka]

• Set category to “Announcements”. I can’t find this category available, I presume it has something to do with access permission?

Do you have a screen similar to this when you're trying to start a new discussion?

• Twitter card validator is a useful too to preview haw the tweet would look like before posting

Bookmarked!! Thanks.

[wxivd]

Do you have a screen similar to this when you're trying to start a new discussion?

This is how it appears to me

[ipaleka]

Ok, so the default permission (being "Triage") doesn't allow you to set that category.

I just added you only for the testing purpose under "Maintain" permission. You should check if such permission is suitable for all the DAO members or not. If it is then I'll just switch the DAO team to that permission level. If not, then I'll be the person for now who creates the announcements.

[wxivd]

I reviewed the Permissions for each role

There are some technical aspects, permission wise, that falls beyond my level of experience.

It is best for you to be the person for now who creates the announcements.

[ipaleka]

I reviewed the Permissions for each role

There are some technical aspects, permission wise, that falls beyond my level of experience.

It is best for you to be the person for now who creates the announcements.

Ok, thanks. We have a year or so in front of us to find a solution for this and other similar issues.

There will exist an entity (organization or person/people) in the DAO phase responsible for the servers administration. I guess something similar can be implemented for this if we can't manage to have the same permission to all members of the DAO.