Comment on page
Integrations
Offer leverage to your users with Gearbox, or fully integrate.
For the technical implementation and contracts, see:
Gearbox protocol has a flexible, adaptable, and scalable architecture.
The main business logic is encapsulated in the core layer which supports operations for both protocol sides. It allows connecting customized pools with Credit Account managers without changing the internal codebase, and thus simplifying integrations.
The goal of Gearbox is to be integrated with existing and new protocols in an open-source manner and provide leverage across many user bases. The architecture allows integration on both sides: both by protocols that are interested in granting leveraged access to their operations as well as by protocols that could provide supply-side lending liquidity like Aave, Compound, Frax, etc.
The integration process looks pretty simple: it is required to inherit an abstract contract (Credit Account Manager or Pool) and add specific business logic with set parameters. To be integrated with deployed contracts, the integration should be approved by Gearbox governance.
Simple integration processes open up new opportunities for collaborations with other protocols, providing leverage to their operations and making Gearbox protocol composable. Overall, Gearbox aims to increase capital efficiency in the DeFi space.
Gearbox core vision is that users should continue to use the DeFi protocols they love, but ... with leverage. Keeping this goal in mind, we have implemented a special library that makes it possible for any dApp to be connected with Gearbox credit account in a similar way to how Metamask or Fortmatic work. See more in the Developer Docs:
