Offchain Infrastructure

To maintain composability the Perennial protocol is design to be fully operational with onchain transactions. However, abstractions of particular parts of the protocol have enabled usability enhancements for Takers and Makers alike. Here are some of examples of offchain infrastructure that works with Perennial:

Keepers

Here are a list of services that receive a fee for certain functions related to the Perennial protocol:

1. Oracle Keeper - Responsible for committing requested price updates to the Oracles

2. Liquidation Keeper - Responsible for liquidating undercollateralized positions

3. Order Keeper - Responsible for executing executable orders

4. Settlement Keeper - Responsible for calling per-user settlement callbacks for position updates

5. Intent Relayer - Responsible for forwarding intents to Controller.sol. Sponsoring the transaction through Alchemy Account Abstraction

NOTE: If you are running liquidator or order execution keepers, you can to deploy the BatchKeeper smart contract. This contract is responsible for batching transactions to reduce gas costs.

Intents API

With the 2.3 upgrade, Perennial supports Intents. As signed messages they need a counterparty to execute these transactions. The Perennial protocol doesn't specify who or how these offchain messages are handled so it's up to market actors to design & implement a system.