Timeline and plan for both outcomes of proposals

Hello, I’d like to suggest including in new proposals a timeline and plan for what’s next if the proposal passes or fails. That would avoid some follow-up questions. For example, now that CLOUD-3 has passed, I’d love to know when the new pool on Kamino is gonna be live, roughly, etc. No paper needed - a couple of bullet points with the next steps should a proposal passes/fails would go a long way to clarify what happens after the vote. Thanks.

4 Likes

Great idea, should be doing this more often, duly noted, thanks!

3 Likes

Would it be a good idea to lock the proposal thread after it has been passed then provide an update on what the next steps are with some kind of timeline of it happening?

For example, cloud003 passed, so if the thread is locked, no additional comments can be made and the team can provide a “conclusion” with what the next steps are so that its the last thing we see - i know timeline will depend on kamino

This way, all of the info will be on research in the same thread (from proposal to discussion to conclusion), and updates etc can still be posted in discord and X - would be awesome to have the info all in one spot so people don’t have to jump around diff platforms :slight_smile:

3 Likes

So guys, any tentative ETA for the implementation of the LP on Kamino? Thanks.

2 Likes

Right on que, lol. But I’m sure you know it’s live now.

Definitely on board with this idea. Knowledge is going to be a common theme throughout many ideas we have, I believe.

3 Likes