Skip to content

Architecture Overview

Architecture Acknowledgement

Moosh is currently built as a direct fork of the Morpho protocol.

Morpho represents one of the most mature and rigorously engineered lending architectures in DeFi. Its design emphasizes capital efficiency, deterministic risk enforcement, and minimal trust assumptions, and has been validated through extensive real-world usage and adversarial market conditions.

At this stage, Moosh does not modify Morpho's core lending logic, accounting model, interest rate mechanisms, or liquidation pathways. All critical protocol behavior remains consistent with upstream Morpho contracts. This design choice is intentional and reflects a security-first approach during the testnet phase.

Inherited Architectural Characteristics

By building on Morpho, Moosh inherits several key architectural properties:

  • Non-custodial Lending Primitives Asset ownership, collateralization, and debt positions are enforced entirely on-chain through deterministic smart contract logic.

  • Explicit and Enforceable Risk Boundaries Loan-to-value ratios, liquidation thresholds, and interest accrual are governed by transparent parameters rather than discretionary intervention.

  • Isolated Market Structure Risk is compartmentalized at the market level, reducing systemic contagion and allowing precise control over exposure.

  • Deterministic Liquidation Mechanics Liquidations follow predefined rules that are verifiable on-chain and independent of off-chain decision-making.

  • Modular and Auditable Design Core components are composable, inspectable, and designed to minimize hidden state or implicit dependencies.

These characteristics form the foundation upon which Moosh operates today.

Current Scope and Intent

During the current testnet phase, Moosh's focus is on validating deployment configurations, parameter boundaries, and system behavior under real usage, while preserving the integrity of Morpho's proven architecture.

Any future extensions or protocol-level changes, if introduced, will be explicitly documented and evaluated independently. At present, the system should be understood as a conservative, security-oriented deployment that prioritizes correctness, transparency, and predictability over experimentation.