
π£οΈRoadmap
SLAG's project roadmap.
Phase 1: In the beginning, ...
Backend Implementation
Frontend Implementation
Deploy custom next.js website,
Deploy documentation
Add fully illustrated version of Starfall: Lost Age of Giants to website
Add story engine dashboard
Add web3 wallet connect functionality
Logistics
Create social accounts
Create SLAG DAO
Create Core Team Multisig Wallet
Deploy $SLAG Token
Post-TGE
Complete transfers to SLAG DAO treasury and team multisig
Pay DexScreener
Pay Dextools.io
Submit listing for:
CoinGecko
CMC
Moonshot
Cookie.fun
Phase 2: Enter the DAO
DAO: Council Era
During the early stages of the DAO (while market cap and # of holders are relatively low), a Council comprised of core team members will be used to configure and safeguard which proposals can be voted on.
Token holders are still the ones to decide if a proposal will pass/not pass, however, this guardrail ensures that a 51% attack cannot be carried out by malicious actors.
Once the distribution of liquid tokens has dispersed to where a 51% attack becomes unlikely, the Council will be dissolved, allowing anyone to submit DAO Treasury proposals.
Set up proposals for:
additional locked LP to deepen liquidity and earn LP fees for DAO;
potential listings;
set up multi-chain support on frontend by:
bridging a portion of supply to Base through Wormhole;
exchanging a portion of SOL for Base ETH;
establish locked LP on Uniswap v3 pool.
Monitor and approve/reject community proposals.
Prepare and configure the SLAG DAO for full autonomy
provide documentation and guidance for community
configure DAO to ensure robust safeguards against 51% attacks
revoke council member tokens to end the 'Council Era'
DAO: Full Decentralization
At this stage, the DAO and it's treasury will be fully ran by $SLAG token holders on a 1 token:1 vote basis.
All $SLAG token holders will have the freedome to submit proposals to the DAO.
All $SLAG token holders will have the responsibility of voting on proposals.
Phase 3: vGutenberg
Phase 1 includes the development and release of Story Engine vMini, our project's MVP. This engine will be capable of crafting rich short stories (5-10k words in length) from a single prompt. Development for Story Engine vGutenberg, our flagship product, has already begun. Aside from being more powerful (produce 100k word length), this model will allow greater control and fine tuning over the story creation process.
Our target release date for vGutenberg is Q1 of 2025.
For more details on our Story Engine's features and capabilities, see Story Engine.
Last updated
Was this helpful?

