Source References: Use Doppler deployments as the contract source of truth for deployed addresses and revisions.
Airlock Entrypoint
Requirement: every Doppler user integrates through Airlock. Direct integration to downstream modules is not the canonical user path.
When to use
- You are integrating with Doppler (all integrations are Airlock-first).
- You need to reason about how token factory, initializer, and migrator contracts are coordinated.
- You need a single source for Airlock behavior and its externally-consumable interface.
What Airlock does
- Entry point for launch creation (
create(...)path). - Lifecycle coordinator for migration (
migrate(asset)path).
Orchestration model
create(...)receives launch configuration and selects modules.- Airlock routes token deployment to the selected token factory.
- Airlock routes pool setup to the selected initializer.
- Airlock executes migration handoff through the configured liquidity migrator.
Core workflow
- Validate module addresses and config payloads.
- Execute launch creation through Airlock.
- Track status through initializer/migrator state and emitted events.
- Call
migrate(asset)when exit conditions are satisfied. - Reconcile migration outputs and downstream pool state.
Quick facts
| Item | Detail |
|---|---|
| Canonical contract | src/Airlock.sol |
| Launch entrypoint | create(...) |
| Migration entrypoint | migrate(asset) |
References
- ENTRYPOINT.md
- INTERFACE.md
- Source:
doppler/src/Airlock.sol