Summary

As outlined in the recent community update and AMA, the community and the team need to decide when to launch the StackOS token.

There are pros and cons to both options that have been discussed, and this proposal is structured as a simple choice.

Launch StackOS token as soon as possible (ASAP). OR Plan the token launch with Skynet

Detailed breakdown of the positives and negatives of both options

Launch StackOS token as soon as possible (ASAP)

Pros

• The token becomes tradeable!
• Opportunity for the token to organically grow attention earlier in the cycle while building and show casing adoption.
• Several NEW decentralized cloud projects are launching this cycle that are capitalized (most still need a working product), and they will also have a token launch at some time- so getting out ahead of them would be beneficial.
• When Skynet launches later in the cycle, StackOS can still benefit from Skynet's ‘hype’, being part of its ecosystem.

Cons

• No CEX at launch (DEX only).
• Organic marketing rather than paid campaigns.
• Some lower-tier KOL engagement via token incentives.
• There will be no initial hype with Skynet, only follow-on hype when Skynet launches.

Plan the token launch with Skynet.

Pros

• Benefits from cross-marketing spend of Skynet and hype during launch.
• Launch with deeper liquidity due to Ecosystem fund backing (This can't be quantified at this point).
• Better chance of CEXs at the launch.
• More significant KOL marketing push as part of Skynet’s broader marketing campaign.

Cons

• We cannot commit when Skynet launches (it might not have a token at all), so making the launch of StackOS dependent on Skynet would make dates highly uncertain.
• There is an outside chance the lead investor will not want DeCloud Labs to launch a Skynet token this cycle because they hold equity rather than tokens.
• StackOS will not get ahead of other competing projects’ launches.
• There is a risk that the StackOS token is absent during the current market cycle.