0xc28a…fadf

All memos sent from and to 0xc28a…fadf.

Future project contracts should include fee routing that automatically sends a portion of mint revenue, trading taxes, or protocol fees to a CMD Buyback Contract. This contract has one clear function: periodically use received ETH or USDC to buy CMD on the open market. The bought-back CMD can be split by preset rules: part added to CMD/ETH LP, part sent to the treasury, part distributed to CMD lockers, and part removed from circulation. To reduce MEV and price impact, the buyback should use TWAP or batched execution, such as spending no more than 5%-10% of the contract balance per hour. This turns project activity directly into CMD buy pressure.
Each future TokenWorks launch should include a CMD Access Gate. To participate in a mint, prompt round, allocation, or allowlist, users must meet at least one requirement: hold a minimum amount of CMD, lock CMD for a defined period, or provide CMD/ETH LP. Implementation can be done through the launch website by checking wallet balances, lock receipts, or LP positions on-chain. Users who qualify get access to the participation flow. The system should use tiers: a basic CMD threshold grants basic eligibility, while larger holdings or longer locks grant higher allocation. This creates recurring demand for CMD before every new TokenWorks launch.
Make CMD the access asset for future TokenWorks launches CMD should become the base access asset for future TokenWorks experiments. Future prompts, mints, allocations, allowlists, or advanced permissions should require users to hold CMD, lock CMD, or provide CMD/ETH LP instead of participating only with ETH. This turns CMD from a standalone traded token into the access pass for the broader TokenWorks pipeline. Every new launch would create natural demand for holding or locking CMD, reduce circulating sell pressure, and concentrate market expectations for future TokenWorks works back into CMD.