# Gearbox Permissionless Overview

> Markdown export of the Gearbox Protocol documentation page for agents and retrieval systems.

Canonical page: https://docs.gearbox.finance/developers/gp-overview
Source file: content/developers/gp-overview.mdx
Section router: https://docs.gearbox.finance/developers/llms.txt
Section full export: https://docs.gearbox.finance/developers/llms-full.txt

Gearbox Permissionless is the governance and infrastructure layer that makes the entire protocol trustless, verifiable, and permissionlessly extensible across chains.

It is implemented as a collection of smart contracts that define roles, boundaries, and processes — ensuring no single entity can access user funds or override market parameters. The code is open source at [github.com/Gearbox-protocol/permissionless](https://github.com/Gearbox-protocol/permissionless).

## Design Principles

- **Non-Interference with Decisions** — the DAO cannot influence or override decisions made by Market Curators or Instance Owners
- **No Control Over Market Contracts** — market parameters allow flexible modification by Curators, but the DAO cannot alter them
- **Exclusive Control Over System Contract Versions** — only the DAO can authorize new versions of system contracts (core protocol logic). Adding adapters, price feeds, bots, or other components remains permissionless.
- **Chain Expansion Oversight** — only the DAO can activate Gearbox on new chains, ensuring the correct Treasury address and Instance Owner multisig are set

## Core Components

| Component | Purpose |
| --- | --- |
| [**Contract Types & Versioning**](https://docs.gearbox.finance/developers/gp-contract-types) | Type system for all protocol contracts. Domain-based organization, semantic versioning, module replacement (not proxies) |
| [**Cross-Chain Multisig (CCM)**](https://docs.gearbox.finance/developers/gp-ccm) | Governance synchronization across chains. Hash-linked batches, strict sequential ordering |
| [**Bytecode Repository (BCR)**](https://docs.gearbox.finance/developers/gp-bcr) | On-chain registry of audited bytecode. System vs public domains, dual-signature verification |
| [**Instances**](https://docs.gearbox.finance/developers/gp-instances) | Per-chain protocol replicas. DAO-activated, managed by Instance Owner |
| [**PriceFeed Store**](https://docs.gearbox.finance/developers/gp-pricefeed-store) | Token-to-oracle marketplace. Instance Owner managed, curator-consumed |
| [**Treasury & Insurance**](https://docs.gearbox.finance/developers/gp-treasury) | Fee distribution (curator/DAO split) and loss coverage fund |

## Roles

The protocol defines a clear hierarchy of roles, each with strictly bounded authority enforced at the smart contract level:

| Role | Scope | Can Affect Users |
| --- | --- | --- |
| DAO (token holders) | All chains | No |
| Technical Multisig | All chains | No |
| Auditors | All chains | No |
| Instance Owners | One chain | No |
| Financial Representatives | One chain | No |
| Market Curators | Market | Yes (with timelock) |
| Emergency Admin | Market | Yes (immediate) |
| Pausable/Unpausable Admins | Market | Yes |
| Emergency Liquidators | Market | Yes |

See [Roles & Permissions](https://docs.gearbox.finance/developers/gp-roles) for detailed authority tables.

## What's in This Section

- [**Concepts**](https://docs.gearbox.finance/developers/gp-concepts) — How each component works
- [**Building**](https://docs.gearbox.finance/developers/gp-building) — Create adapters, integrate protocols, extend the core