How da0-da0/dao-contracts works
• Core Module – Represented by the “dao-dao-core” contract (found under contracts/dao-dao-core) which manages the DAO treasury.
• Voting Modules – These span several directories under contracts/voting (e.g., dao-voting-cw20-staked, dao-voting-cw4, dao-voting-cw721-staked, etc.) and are responsible for determining and managing voting power.
• Proposal Modules – Found under contracts/proposal (e.g., dao-proposal-single, dao-proposal-multiple, dao-proposal-condorcet), these modules handle proposal submission and voting processes.
• Pre-Propose Modules – Under contracts/pre-propose, these modules prepare or vet proposals before they move to the main proposal modules.
• Staking & Distribution Modules – Present in contracts/staking, contracts/distribution, and related directories; these handle reward distributions, staking logic, or other fund management features.
• External Contracts – Located in contracts/external, they provide extended functionality like token swaps, NFT staking, and other integrations.
• Libraries & Reusable Packages – The “packages” directory includes helper libraries (e.g., dao-interface, dao-hooks, dao-dao-macros, cw-denom, etc.) which encapsulate common business logic, interfacing, and testing functionality.
• CI and Testing Infrastructure – The “ci” folder (with integration tests and environment bootstrap code) and “scripts” provide automated testing, deployment, and integration management.
Relationships and Interactions
– The Core Module (treasury) is central and interacts with all other modules.
– Voting modules send queries and messages to the Core to check balances or update voting power.
– Proposal modules interact with both the voting modules and the Core to validate proposals and execute fund transfers.
– Pre-propose modules act as an intermediary layer before proposals are accepted.
Including Key Technologies and Frameworks
• That the project is written in Rust (evidenced by Cargo.toml files) and uses CosmWasm smart contracts.
• Components like “dao-dao-macros”, “dao-interface”, and “dao-hooks” from the packages directory as libraries that standardize interactions across modules.
• External integrations (e.g., bitsong, cw token swaps, NFT-related contracts) which are under the external directory.