Building on Permissionless
Gearbox's permissionless architecture is designed for extensibility. You can build new components that plug into the system without requiring governance approval for the integration itself.
What You Can Build
| Extension Type | Description | Guide |
|---|---|---|
| Adapter | Add support for a new DeFi protocol (DEX, vault, staking) so Credit Accounts can interact with it | Adapter Development |
| Protocol Integration | Compose with Credit Accounts from your own smart contracts — build strategies, keepers, or automated managers | Protocol Integration |
| Core Extension | Extend the protocol itself — custom interest rate models, pool hooks, Credit Manager spokes | Core Extension |
How It Fits Together
Approval Flow
While building is permissionless, deploying to production uses the BCR verification process:
- Build your adapter/integration/extension
- Test with Foundry or Hardhat against forked mainnet
- Submit for audit
- Register in the Bytecode Repository with dual signatures
- Curators enable your component in their Credit Suites
Steps 1-2 are fully permissionless. Steps 3-5 ensure production safety.