All DeFi protocols supported by Railnet — native adapters and ERC-4626 compatible vaults
In Railnet smart contracts, a Yield Source is connected via a Vehicle adapter. See Glossary for all terminology.
Railnet connects to DeFi protocols through Vehicle adapters. Some protocols have native adapters built into the protocol. Any protocol exposing an ERC-4626 vault can be connected through the generic ERC-4626 Vehicle without custom code.
Railnet supports multiple vault standards through its Vehicle abstraction layer. A “supported” standard means Railnet ships a base Vehicle implementation that handles the standard’s mechanics — you inherit from it, and Railnet handles the STEAM lifecycle, accounting, and keeper automation.ERC-4626 (synchronous vaults). The most common DeFi vault standard. ERC-4626 vaults have immediate deposits and withdrawals, making them the simplest integration path. Railnet wraps these with sync Vehicles.ERC-7540 (asynchronous vaults). The emerging standard for vaults with delayed operations — withdrawal queues, cooldown periods, and multi-step settlement. Railnet wraps these with async Vehicles and automates settlement via keepers. The same async state machine handles off-chain settlement for real-world assets, so tokenized treasuries, private credit, and trade finance integrate through the same Vehicle model as on-chain protocols.
These protocols have dedicated Vehicle implementations in the Railnet codebase, optimized for each protocol’s specific mechanics.
Protocol
Vehicle type
Deposits
Withdrawals
Factory (Base Testnet)
Aave V3
AaveV3Vehicle
Sync
Sync
0x414A9F508044B914243e91a421bf2F7D599aDc78
Compound V3
CompoundV3Vehicle
Sync
Sync
0x33450Ec8C1b1BEbD4eEe39714b5C0e18b90d0f33
Morpho Blue
MorphoBlueVehicle
Sync
Sync
0x305844AD370e202e534c80b14c2a03e00369267d
Any ERC-4626 vault
ERC4626Vehicle
Sync
Sync
0x75074d971c62B82BA8baf316dE5c4E17eBbe9cb5
Ethena (sUSDe)
EthenaVehicle
Sync
Async (cooldown)
—
Syrup (Maple Finance)
SyrupVehicle
Sync
Async (queue)
—
Factory addresses shown are for Base Testnet (chain ID 8453). Mainnet addresses will be added here as deployments are finalized. Ethena and Syrup factories are not yet deployed on testnet.
Railnet also includes a Wrapper Vehicle (WrapperVehicleFactory: 0x7567FA3332a284A96b936ed8F756F03799885EC5) that provides a 1:1 wrap of any ERC-20 token for STEAM compatibility. This is a utility adapter — it does not generate yield.
Any protocol that exposes an ERC-4626 tokenized vault can be connected to Railnet using the generic ERC4626Vehicle — no custom adapter code required. The following protocols are known to implement ERC-4626 and are theoretically compatible.
This list is not exhaustive. Any vault implementing the ERC-4626 standard can be connected using the generic ERC4626Vehicle. Check a protocol’s documentation to verify ERC-4626 compatibility before deploying.
Some protocols require async handling (withdrawal queues, cooldown periods, or per-address restrictions) and cannot use the generic ERC-4626 Vehicle. These protocols can be supported by building a custom async adapter, following the same pattern as the native Ethena and Syrup Vehicles.
Protocol
Category
Async pattern
Lido (wstETH)
Liquid staking
Withdrawal queue
Rocket Pool (rETH)
Liquid staking
Minipool exit queue
EigenLayer
Restaking
Withdrawal delay
Symbiotic
Restaking
Withdrawal delay
Karak
Restaking
Withdrawal delay
Pendle
Yield tokenization
Maturity-based settlement
Wrap an existing vault
Deploy a Vehicle that wraps any ERC-4626 vault — the plug-and-play integration path.
Build a custom adapter
Handle withdrawal delays and per-address restrictions with the async adapter pattern.