Comet Architecture

Explain Compound V3 Comet architecture with component roles and contract mappings.

Updated Jan 28, 2026
One-click install
npx skills add https://github.com/cyotee/compound-V3-comet-skill --skill comet-architecture
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Comet Architecture
Source: https://github.com/cyotee/compound-V3-comet-skill/tree/main/.opencode/skills/comet-architecture
Command: npx skills add https://github.com/cyotee/compound-V3-comet-skill --skill comet-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Compound V3 Comet architecture information is often scattered. This skill consolidates a high-level overview to help non-experts understand the protocol structure.

Core Features & Use Cases

  • High-level diagram and component responsibilities for Comet proxy, main contract, extension, and supplementary modules.
  • Clear explanations of monolithic design, single base asset, and internal liquidation flow to support onboarding, governance discussions, and architecture reviews.
  • Use Case: A developer needs to explain the architecture to a product manager, or a reviewer needs a quick map of contracts and interactions.

Quick Start

Read the architecture overview and compare the listed core components (Comet.sol, CometExt.sol, and the supplementary contracts) to form a mental model of the protocol.

Frequently Asked Questions about Comet Architecture

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the Compound V3 Comet architecture?

The Compound V3 Comet architecture uses a monolithic design with a single base asset and internal liquidation flow. Core components include the Comet proxy, main Comet contract, CometExt extension, and supplementary modules handling protocol operations.

How does the Comet proxy interact with the main contract and extension?

The Comet proxy delegates calls to the main Comet.sol contract and CometExt.sol extension modules. This separation allows the protocol to manage core logic and supplementary features while maintaining its monolithic design and internal liquidation flow.

Can I use this overview to prepare for a Compound V3 architecture review?

Yes, this overview maps component responsibilities and data flows for protocol architects, developers, and operators. It provides a concise system diagram of Comet contracts and supplementary modules to support onboarding and architecture reviews.

Why does Compound V3 use a monolithic design with a single base asset?

Compound V3 uses a monolithic design with a single base asset to consolidate operations within the main Comet contract. This structure streamlines internal liquidation flows and protocol governance by reducing fragmented contract interactions.

What are the limitations of understanding Comet solely through a high-level architecture map?

A high-level architecture map of Comet provides a conceptual overview of component roles but lacks implementation depth. It does not cover specific Solidity code logic, security constraints, or detailed parameter configurations needed for deployment or auditing.