# Request a protocol \[How a protocol outside the catalog gets connected to Railnet]

The [catalog](/yield-sources) lists what Railnet connects today, not the limit of what Railnet can wrap. Any on-chain yield an address can enter and exit can be a Vehicle.

## Which path applies

| The protocol… | Path | Effort |
|---|---|---|
| Exposes an ERC-4626 vault with reliable `maxDeposit` and `maxRedeem` | [Generic ERC-4626 adapter](/yield-sources/erc-4626) | Deploy a Vehicle at the vault address |
| Exposes an ERC-4626 vault whose `max*` views are missing or misleading | [`ERC4626VehicleMaxFunctionsIgnored`](/yield-sources/erc-4626) | Same as above |
| Exposes an ERC-7540 vault (request, settle, claim) | [Generic ERC-7540 adapter](/yield-sources/erc-7540) | Configuration plus operator coordination: whitelisting, settlement cadence |
| Has its own entry points, cooldowns, per-address restrictions or maturity dates | Custom adapter, built by Railnet | New Vehicle built by Railnet |

Custom adapters cover liquid staking with withdrawal queues (Lido, Rocket Pool), restaking with delays (EigenLayer, Symbiotic) and fixed-maturity instruments (Pendle). Each follows the [Ethena](/yield-sources/ethena) and [Maple](/yield-sources/maple) pattern: synchronous deposit, keeper-driven redeem.

## What we need from you

* The protocol, network and the exact contract to deposit into (vault, pool or market address).
* The deposit asset and the expected yield mechanics (interest, staking rewards, incentive tokens).
* Exit mechanics: instant, cooldown, queue or epoch, and who settles.
* Any access requirement on the protocol side (whitelists, KYC on the vault, minimums).
* Whether you want it behind your own Conduit or inside an [Allocation Strategy](/strategies/allocation).