Introduction
Compound III represents a significant evolution in decentralized finance, offering an Ethereum-based protocol that enables users to supply crypto assets as collateral to borrow base assets. This next-generation lending platform introduces architectural improvements and gas optimizations while maintaining the core principles that made Compound a foundational DeFi protocol.
The initial deployment utilizes USDC as the base asset, providing a stable foundation for borrowing and lending activities. Unlike previous versions, Compound III focuses on risk management through isolated collateral types and improved capital efficiency.
👉 Explore advanced DeFi strategies
Core Protocol Architecture
Network Deployments
Compound III operates on EVM-compatible networks, with Ethereum hosting the initial deployment. The protocol's deployment artifacts, including contract addresses, are available in the official Comet repository's deployments folder. Developers should always interact with the v3 proxy address, which remains constant regardless of future protocol upgrades.
To generate the proper Comet Interface ABI, compile the Comet project using the command yarn compile. This ensures compatibility with the latest protocol implementations.
Key Protocol Contracts
Main Proxy Contract (cUSDCv3)
The cUSDCv3 proxy contract serves as the primary interface for interacting with the first Compound III market. This address remains fixed and independent from future market upgrades, following OpenZeppelin's TransparentUpgradeableProxy pattern. Developers should direct all interactions through this proxy rather than implementation contracts.
Implementation Contracts
The cUSDCv3 Implementation contains the market logic deployed by the Comet Factory via the Configurator. The cUSDCv3 Ext contract provides auxiliary functionality without requiring space in the main protocol contract. Neither should be interacted with directly—always use the proxy address with the Comet Interface ABI.
Configuration Management
The Configurator contract, itself a proxy, manages parameter updates for Comet proxy contracts. This innovative approach enables significant gas savings by "constantizing" protocol parameters. The Configurator Implementation can be upgraded to accommodate future protocol changes.
Administrative Structure
The Proxy Admin contract oversees both Comet and Configurator proxy contracts, implementing OpenZeppelin's recommended upgradeability pattern. The Comet Factory produces instances of the Comet implementation contract when invoked by the Configurator.
Additional Components
The Rewards contract holds reward tokens (like COMP or WETH) and facilitates user claims based on protocol tracking indices. The Bulker contract, while not integral to core protocol function, enables bulk operations within single transactions—particularly useful for user interfaces.
Development Resources and Tools
The Compound community provides comprehensive resources for developers building on the protocol. These materials cover deployment processes, feature development, and implementation examples for external applications using Compound III as infrastructure.
Key resources include the Compound III Developer FAQ, which addresses common technical questions, and detailed guides covering scenarios, migrations, and workflows. Additional specialized guides explain how to create liquidators and build Comet extensions for custom functionality.
👉 Access developer tools and resources
Security Framework
Priority and Approach
Security remains the highest priority for Compound III, with the development team investing considerable effort alongside third-party auditors to create a safe and dependable protocol. All contract code and balances are publicly verifiable, enabling transparent security assessment.
The protocol embraces the philosophy that size, visibility, and time represent the true tests of smart contract security. Users should exercise appropriate caution and conduct their own security assessments before engaging with the protocol.
Audit History
Compound III has undergone comprehensive security assessments by leading blockchain security firms. OpenZeppelin and ChainSecurity have both conducted extensive audits of the protocol, with their reports publicly available for review.
These audits examine the protocol's mathematical models, implementation details, and potential vulnerability vectors. The public availability of these assessments demonstrates Compound's commitment to transparency and security best practices.
Frequently Asked Questions
What is the main difference between Compound III and previous versions?
Compound III introduces a redesigned architecture focused on risk management and capital efficiency. The protocol now uses isolated collateral assets with a single borrowable base asset (USDC), unlike v2 which allowed multiple borrowable assets. This approach reduces complexity and improves safety for lenders.
How do I interact with Compound III as a developer?
Developers should use the v3 proxy address with the Comet Interface ABI for all interactions. The proxy address remains constant despite upgrades, ensuring forward compatibility. Always compile the interface using the official repository to ensure ABI compatibility.
What networks support Compound III?
The initial deployment is on Ethereum mainnet, but the protocol is designed for EVM compatibility. Future deployments on other networks will follow similar patterns, with deployment artifacts available in the official repository.
How does the Bulker contract improve user experience?
The Bulker contract allows multiple operations within a single transaction, significantly reducing gas costs for complex interactions. Users can wrap ETH, supply multiple collateral types, and borrow assets in one atomic transaction.
What reward mechanisms does Compound III implement?
The protocol utilizes a dedicated Rewards contract that distributes COMP and potentially other tokens based on user activity and protocol tracking indices. Users must actively claim rewards through the designated interface.
How are protocol upgrades handled?
Compound III uses a transparent proxy pattern that allows for implementation upgrades while maintaining a consistent interface address. Upgrades are managed through the Proxy Admin contract following community governance procedures.
Where can I find additional technical support?
The Compound community maintains active discussions on comp.xyz forums and a dedicated Discord channel for development questions. Community members and Compound Labs team members regularly participate in these forums.