Built to Compound.

Solana Mainnet · Meteora Dynamic Bonding Curve · COMPD/SOL

COMPD is a Solana-native treasury accounting and authorized-execution protocol. It gives capital a defined lifecycle: verify receipts, allocate reserves, authorize bounded strategy capital and reconcile realized results.

The primary source repository is compd-solana. It contains the Anchor program, integer accounting crate, Solana Agent interfaces and Meteora integration. Solana Mainnet is the target network; source publication is not evidence of a completed mainnet deployment, live trading or an independent audit.

Source · Architecture · Program reference · Contributing

COMPD separates custody, attribution, policy, execution preparation and reconciliation. An accounting reserve is not an executed swap or holder payment.

The Rust/Anchor treasury uses separate Treasury, Run, Distribution and Claimed accounts. Its instructions cover initialization, physical revenue deposits, bounded allocation, settlement, pause control, fixed-recipient reserve release, distribution funding and holder claims.

Treasury authority remains privileged. Allocation pays only the configured executor; settlement requires authority and executor signatures. The current program limits individual allocation to 10% of liquid plus deployed strategy capital, aggregate deployment to 30%, and active runs to three. A realized loss pauses new allocation.

Instructions, constraints and accounting invariants explain what these controls enforce and where off-chain trust remains.

Meteora Dynamic Bonding Curve is COMPD's selected launch infrastructure for the COMPD/SOL pair. The source verifies configured cluster, pool, creator, config and mint identities using official SDK interfaces.

Creator-fee receipt processing binds finalized transaction evidence to the expected claim and physical SOL receipt. A receipt at the configured receiver is separate from a deposit into treasury custody; aggregate vault balances are not assumed to be COMPD revenue.

Qualified DBC-to-DAMM-v2 position-fee handling is implemented separately. Mixed asset receipts remain distinct and are not silently counted as SOL income. Integration documentation describes supported paths and migration limits.

The Agent supplies an eight-hour UTC observation scheduler, executable quote qualification, spend/exposure controls, receipt journaling and custody reconciliation. The scheduler observes; it does not automatically invoke a trading loop.

Transaction preparation remains unsigned. Exact-message approval, external wallet submission, finalized confirmation and treasury settlement are distinct stages. The repository contains no enabled signing or broadcasting service. Agent documentation maps the implemented interfaces and remaining orchestration requirements.

Returned principal is recovered before positive profit is allocated. Calculations use integer arithmetic, with rounding remainder assigned to Protocol Reserve. Unrealized price changes and executable quotes are not settled profit.

A buyback reserve release is separate from market execution. The prepared buyback path combines a bounded SOL-to-COMPD swap with a checked burn of the protected minimum output; excess output requires separate handling.

The 10% profit allocation credits a reward reserve. Snapshot tooling aggregates eligible standard-SPL balances, constructs distribution-bound Merkle proofs and reconciles funded distributions against claim accounts.

The authority reviews eligibility and funds a Distribution PDA. A holder signs a valid claim; a unique index account prevents replay. Rewards are conditional on settled profit, eligibility and funding, not a fixed yield or automatic payment for holding tokens. Holder Rewards documents exclusions and snapshot limits.

• Rust and Anchor 0.31.1: treasury custody and accounting.
• JavaScript ES modules and Node.js 24+: Agent and SDK wrappers.
• Official Solana and Meteora SDKs: account validation and unsigned transaction construction.
• SQLite and integer accounting: durable local evidence and deterministic allocation.

The client code is JavaScript, not a claimed first-party TypeScript implementation. Dependency provenance and all 14 disclosed dependency findings remain public. Source availability does not establish mainnet security approval.

Historical material is not presented as deployed Solana code. The active implementation and contributor entry point are in compd-solana.

CompdProtocol has submitted two focused documentation contributions to the Meteora DBC SDK. Both are OPEN — pending review, not merged, checked on 23 October 2026.

These are independent external contributions. They do not imply Meteora affiliation, endorsement or partnership. Linked pull requests are the authoritative source for subsequent status changes.

• Architecture and trust boundaries
• Anchor program, accounts and instructions
• Meteora DBC and migration interfaces
• Agent lifecycle and recovery
• Holder snapshots and funded claims
• Security architecture and reporting policy
• Contribution guide
• First-party license scope and third-party exclusions

COMPD — The Compounder · Built to Compound.