Platforms also deploy Conduits as distribution channels for existing strategies. See Deploy a Conduit as a platform for the platform-focused guide.
When to use a Conduit
Use a Conduit when:- Multiple Multi-Vehicles need access to the same underlying yield source
- You want a single shared position instead of separate per-Multi-Vehicle positions
- You need ERC20 transferable shares representing a pro-rata claim on the underlying Vehicle
Prerequisites
- A deployed STEAM Vehicle (e.g., an
ERC4626Vehicle) - A deployed
CoreFactoryandFreezablePausableBeaconfor the Conduit implementation - The deposit asset authorized in the AssetRegistry — the factory reads the initial deposit size from there at spawn time
- Familiarity with the STEAM standard
Deploy a Conduit
Configure spawn parameters
Define the Conduit’s configuration including the underlying Vehicle and transfer mode. The initial deposit size is read from the AssetRegistry — it is not passed here.
Spawn the Conduit
Look up the initial deposit amount in the AssetRegistry, approve the factory for that amount, then spawn.
The initial deposit protects against inflation attacks by bootstrapping the share supply. The initial shares are burned automatically. The registry also dampens cumulative rounding losses from nested vault accounting — see Asset registry for sizing guidance.
Make a deposit
After deployment, deposit into the Conduit. The Conduit handles pulling assets and creating the STEAM query in the underlying Vehicle.Redeem from a Conduit
Provide Conduit shares as input, and the Conduit handles the interaction with the underlying Vehicle.Next steps
Configure fees
Add fee structures to your Conduit.
Learn about Conduits
Understand Conduit architecture in depth.