Monad Spaces

What I built: A DAO framework where the treasury (the group's money) and the governance rules (how decisions get made) are two separate, swappable pieces — not locked together forever. A DAO's treasury can stay exactly where it is, holding the same funds at the same address, while the group change how they vote and make decisions at any time, without ever having to move their money to a new treasury. Over time, new governance styles can be built and added as options, so DAOs aren't stuck with whatever rules they started with; they can switch to a better one later, on the fly, fully on-chain. What problem it solves: Right now, most EVM chains handle DAO voting one of two ways: they use Snapshot, which is off-chain, meaning votes aren't actually binding; someone still has to manually carry out what was voted on, and nothing is enforced by the blockchain itself. Or teams build their own governance system from scratch, which is hard, and once it's built, it's usually locked in for good; if the DAO wants different rules later, they'd need to migrate their entire treasury to a new setup, which is risky and disruptive. This framework solves both problems: everything happens on-chain automatically, and a DAO's governance can evolve over time without ever touching or moving the treasury. What I Learnt: Building Monad Spaces taught me that good DAO architecture is about more than writing governance logic—it's about designing systems that can evolve safely over time. I gained a deeper understanding of modular smart contract design, contract composition, upgradeable governance patterns, treasury isolation, on-chain voting mechanisms, timelocks, factory deployment patterns, and secure permission management. I also learned the importance of separating responsibilities between contracts to improve maintainability, extensibility, and long-term usability without compromising security.