In Railnet smart contracts, a Yield Source is connected via a Vehicle adapter. See Glossary for all terminology.
Vault standards
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.Native Vehicle adapters
These protocols have dedicated Vehicle implementations in the Railnet codebase, optimized for each protocol’s specific mechanics.Factory addresses shown are for Base Testnet (chain ID 8453). Mainnet addresses will be added here as deployments are finalized. The Ethena factory is not yet deployed on testnet.
WrapperVehicleFactory: 0xb6Bce9ad06e26a7879dd6B6f1C39fA26E629dfa8) that provides a 1:1 wrap of any ERC-20 token for STEAM compatibility. This is a utility adapter — it does not generate yield.
ERC-4626 compatible protocols
Any protocol that exposes an ERC-4626 tokenized vault can be connected to Railnet using the genericERC4626Vehicle — no custom adapter code required. The following protocols are known to implement ERC-4626 and are theoretically compatible.