Bedrock DAOWhat an audit verifies
A security review examines a defined version or set of smart contracts for classes of vulnerabilities. It does not guarantee that every later deployment, parameter change or integration is secure. Review the audit date, repository revision and stated limitations.
Where to find contract information
Bedrock has published contract-related materials through its project documentation and GitHub. Confirm whether a listed contract is deployed on testnet or mainnet before relying on it. Addresses from an unrelated environment should not be used to approve a real transaction.
Governance-specific checks
For vote escrow and rewards, inspect who can upgrade contracts or change parameters, how exit queues are implemented, how reward claims are authorized and how gauges are managed. These are relevant to both user safety and governance integrity.
Safe verification steps
Open the verified source repository and any linked audit report, compare network and deployment addresses against official listings, and use an explorer to review the contract before approving. Do not treat a webpage logo alone as evidence of authorization.
Consult the published Bedrock DAO GitHub repository for contract references and linked security reports.
Frequently asked questions
What does a smart contract audit tell me?
An audit can review specified contracts and implementation risks, but it does not guarantee that every future transaction or protocol condition is risk-free.
What should I verify in addition to an audit?
Verify the current domain, contract references, network, wallet transaction details and any governance-specific permissions before interacting.