Quick start

A Conduit wraps an existing strategy (Multi-Vehicle or Vehicle) with your own ERC20 share token, fee structure, and access control. This guide walks you through deploying one using the ConduitFactory already deployed on each supported chain.

Before you begin

You need a strategy to wrap and an External Access Control (EAC) contract. Fee Manager and AccountList are optional.

Prerequisite	Required	How to get it
Strategy (Multi-Vehicle or Vehicle)	Yes	Use a Strategy
External Access Control (EAC)	Yes	Deploy an EAC — your central permission contract
Fee Manager	No	Deploy a Fee Manager — or pass `address(0)` for no fees
AccountList	No	Set up compliance — or pass `address(0)` for permissionless access

Already completed Use a Strategy? You already have an EAC and a Strategy-level Fee Manager deployed. You can optionally deploy a separate Fee Manager for your Conduit — see Configure fees. Skip to Choose your configuration.

Starting fresh? At minimum, deploy an EAC before proceeding — it’s a single transaction. See Compliance — Deploy and configure access control.

Choose your configuration

Before deploying, decide on three key parameters:

FeeManager — your fee structure

Deploy a FeeManager to collect fees on your Conduit. You can configure:

Management fee — annualized, prorated by time elapsed
Performance fee — charged on gains above a high water mark
Deposit fee — deducted from shares received
Redeem fee — deducted from assets received

Set to address(0) if you don’t need fees. To deploy a Fee Manager, see Configure fees.

AccountList — compliance and access control

Deploy an AccountList to control who can deposit, transfer, and hold shares. It combines an allow-list, a block-list, and an optional sanctions oracle, with one of three modes:

Mode	Behavior
`OPEN`	Allow-list ignored — block-list and sanctions only
`REGULAR`	Allow-list gates deposits; transfers only screened against the block-list and sanctions
`STRICT`	Allow-list gates deposits and transfers — both parties must be listed

Precedence is sanctions, then block-list, then the allow-list mode. Redeems are the exception: any non-sanctioned holder can always exit, even if blocked or de-listed. Sanctions screening plugs into Chainalysis-style oracles via ISanctionsList and fails closed if the oracle reverts.Set to address(0) for permissionless access. To deploy an AccountList, see Compliance.

Deploy the Conduit

Get the ConduitFactory address

Railnet deploys a ConduitFactory on each supported chain. Look up factory addresses in Supported protocols. spawn is gated on the CONDUIT_SPAWN role held in the factory’s own access control — Railnet’s, not the EAC you pass in params — so have your deployer address granted that role first.

ConduitFactory factory = ConduitFactory(CONDUIT_FACTORY_ADDRESS);

// Coming soon

Configure spawn parameters

Define your Conduit’s configuration. The vehicle parameter accepts any STEAM-compliant contract — a Multi-Vehicle or a Vehicle. The deposit asset is that Vehicle’s own asset() and the initial deposit amount is read from the AssetRegistry — neither is passed here.

ConduitFactory.SpawnParams memory params = ConduitFactory.SpawnParams({
    name: "Platform USDC Yield",                    // Your branded share token name
    symbol: "pUSDCy",                               // Your branded share token symbol
    vehicle: IVehicle(MULTI_VEHICLE_ADDRESS),       // The strategy to distribute
    feeManager: IFeeManager(feeManagerAddress),     // address(0) for no fees
    accountList: IAccountList(accountListAddress),  // address(0) for permissionless
    ownerRegistry: IOwnerRegistry(address(0)),      // address(0) for no wrapped-query NFTs
    accessControl: accessControl,                   // Your EAC contract
    transferEnabled: false,                         // One-way latch, flip with enableTransfers()
    initialInterceptions: new Interceptor.Interception[](0),
    initialExpectedSupply: 1e6,                     // Minimum cShare supply after the seed deposit
    querySalt: bytes32(0),
    deploymentSalt: keccak256("platform-conduit-v1")
});

// Coming soon

Approve and spawn

Look up the initial deposit amount in the AssetRegistry, approve the factory, then spawn the Conduit. The deployment salt travels inside params, so spawn takes a single argument.

// Read the configured initial deposit from the AssetRegistry
uint256 initialDeposit = assetRegistry.getInitialDepositAmount(USDC_ADDRESS);

// Approve the factory to spend it
IERC20(USDC_ADDRESS).approve(address(factory), initialDeposit);

// Spawn the Conduit — requires CONDUIT_SPAWN
IConduit conduit = factory.spawn(params);

// Coming soon

The initial deposit protects against inflation attacks by bootstrapping the share supply. Once the seed query settles, the factory sends the shares it received to the burn address, checks totalSupply() >= initialExpectedSupply, and calls enable(). See Asset registry for initial deposit sizing guidance.

The factory is the msg.sender of the seed deposit. If you pass an accountList, the factory address must itself satisfy canDeposit at spawn time (allow-listed under REGULAR/STRICT, never blocked or sanctioned), or the spawn reverts.

Finalize (async strategies only)

For sync yield sources, the Conduit is enabled inside spawn. For async yield sources (or strategies wrapping async sources) the seed deposit cannot settle in the same transaction: the factory records a PendingDeposit, emits PendingConduitDeposit, and returns a Conduit that is not yet enabled. Wait for the deposit to settle, then finalize:

// Burns the seed shares and enables the Conduit; reverts NoPendingDeposit if there is nothing pending
factory.finalizeConduitDeposit(conduit);

// Coming soon

Verify deployment

After deployment, confirm the Conduit is operational:

// Check the Conduit is enabled
require(conduit.ready(), "Conduit not enabled");

// Verify the underlying strategy
address vehicle = address(conduit.getVehicle());
require(vehicle == MULTI_VEHICLE_ADDRESS, "Wrong vehicle");

// Check the asset
address asset = conduit.asset();
require(asset == USDC_ADDRESS, "Wrong asset");

// Coming soon

Next steps

Deposits & withdrawals

Process deposits and withdrawals through your Conduit.

Compliance & access control

Configure roles and permissions for your Conduit.

Configure fees & revenue

Set up fee structures and revenue distribution.

Supported protocols

Look up deployed factory and infrastructure addresses per chain.

Getting started

Tutorials

How-to guides

Reference

Before you begin

Choose your configuration

Deploy the Conduit

Verify deployment

Next steps

Deposits & withdrawals

Compliance & access control

Configure fees & revenue

Supported protocols

​Before you begin

​Choose your configuration

​Deploy the Conduit

​Verify deployment

​Next steps

Deposits & withdrawals

Compliance & access control

Configure fees & revenue

Supported protocols

Before you begin

Choose your configuration

Deploy the Conduit

Verify deployment

Next steps