> For the complete documentation index, see [llms.txt](https://docs.daobase.ai/daobase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.daobase.ai/daobase/core-feature/dao-intelligence-layer/data-platform-integration/gov-frameworks-integration.md). # Gov frameworks integration ### 🗳️ DAO Governance Data Integration Governance is at the heart of every DAO. DAOBase provides deep and comprehensive analysis by aggregating data from both on-chain and off-chain governance frameworks used across the ecosystem. #### 📡 **Data Acquisition Methods** * **On-Chain Governance:**\ We monitor smart contract event logs to collect key governance signals, including: * Proposal lifecycle events: creation, voting, execution, cancellation, rejection * Delegation events from governance token contracts * **Off-Chain Governance (e.g., Snapshot):**\ We leverage official APIs provided by platforms like Snapshot to fetch governance activity data in real time. *** #### 📊 **Core Governance Data Collected** Our governance analytics are powered by the structured integration of the following key data points: * **Proposal Data:**\ Proposal ID, title/content, proposer address, creation time, start/end time, voting token type, quorum/threshold requirements * **Execution Data:**\ Proposal ID, executor address, execution hash, and timestamp * **Voting Data:**\ Voter address, proposal ID, selected option, voting timestamp, transaction hash * **Delegation Data:**\ Delegator address, delegatee address, delegation timestamp, transaction hash This dataset forms the backbone of DAOBase's governance intelligence layer, enabling deep insights into decision-making behaviors across DAOs. *** #### 🔗 **Integrated Governance Frameworks** DAOBase currently supports governance data integration from a wide range of both on-chain and off-chain frameworks, including: * [Snapshot](https://snapshot.org/#/) * [Aragon](https://app.aragon.org/) * [Moloch（Daohaus）](https://app.daohaus.club/explore) * [Tally](https://www.tally.xyz/) * [OpenZeppelin](https://www.openzeppelin.com/) * [Compound](https://docs.compound.finance/governance/) * [Nouns Builder](https://nouns.build/) * [Aave](https://docs.aave.com/governance/) * [Maker DAO](https://manual.makerdao.com/) * [Kyber DAO](https://kyberswap.com/kyberdao/vote) * [Element DAO](https://governance.element.fi/proposals) * [Homebase](https://tezos-homebase.io/explorer/daos) * [Syndicate](https://twitter.com/syndicateio) * [Xdao](https://www.xdao.app/) * [Colony](https://colony.io/) * *(...and more continuously being added)* --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.daobase.ai/daobase/core-feature/dao-intelligence-layer/data-platform-integration/gov-frameworks-integration.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.