Zenigame
@zeni.eth
526 Following
7976 Followers
1 reply
1 recast
9 reactions
1 reply
0 recast
1 reaction
0 reply
1 recast
9 reactions
0 reply
0 recast
0 reaction
0 reply
0 recast
1 reaction
9 replies
3 recasts
19 reactions
1 reply
1 recast
1 reaction
1 reply
1 recast
4 reactions
0 reply
1 recast
8 reactions
0 reply
0 recast
0 reaction
1 reply
1 recast
1 reaction
0 reply
2 recasts
3 reactions
0 reply
0 recast
1 reaction
0 reply
1 recast
1 reaction
0 reply
0 recast
0 reaction
1 reply
2 recasts
4 reactions
0 reply
0 recast
0 reaction
1 reply
0 recast
1 reaction
0 reply
0 recast
0 reaction
Streme.fun smart contracts on @base are designed in a modular fashion. For each token deployment, it steps through (up to) 4 modules, which are deployed as separate contracts:
1. Token Factory: creates the tokens, mints the supply
2. Post Deploy Hook (optional): if configured this module can do something with part of the total supply. (In the first version, we use this to deploy Staking contracts/rewards)
3. LP Module: Takes remaining token supply and provisions liquidity.
4. Post LP Hook (optional): does something that makes sense after LP has been provisioned (not used in initial version of Streme)
Also, **multiple** modules for each of the above can be supported concurrently. Meaning that one token deploy might use one set of modules, while the next deploy might use a different combination of modules.
The initial config represents a "meme coin launcher" config, but one can imagine more serious configs that provide team allocations, vesting/locking, bonding curve, pre-buys, etc. to meet different goals 1 reply
1 recast
6 reactions
