Custody & Infrastructure7 min read
MB
Editorial Team
·October 27, 2026

Can a Token Conversion Route Lack a Reverse Exit?

An ERC-7575 unidirectional pipe is a token converter that works in one direction only, for example deposit and mint without redeem or withdraw. An investor who entered through such a pipe can hold valid shares with no reverse route at that contract. Map and evidence the exit route before approving the conversion adapter.

TL;DR — Key Takeaways

  • ✓Specified: ERC-7575 lets a pipe be unidirectional; an entry-only pipe should offer deposit and/or mint, not redeem and/or withdraw.
  • ✓Evidence: A completed entry transaction is not evidence of an exit route. Test the reverse path separately for the specific holder.
  • ✓Three layers: Separate what the interface specifies, what the deployed contract does and what the product terms promise the investor.
  • ✓Approve the adapter only when every pipe has a documented exit, an alternative route or a named exception owner.

Ready to get started?

Join others who are already using our platform.

Can a Token Conversion Route Lack a Reverse Exit?

What does ERC-7575 allow a pipe to omit?

ERC-7575 defines a pipe as a converter between two external ERC-20 tokens that may be unidirectional or bidirectional. A unidirectional pipe should implement only deposit and/or mint, not redeem and/or withdraw.

ERC-7575 is a Final standard, created in December 2023, that adapts ERC-4626 to support several assets or entry points for one share token. Pipes are one of the vault types it enables. In a pipe, both the asset and the share are ERC-20 tokens that live outside the converter. Entry points lock or burn the asset and mint or transfer the share. Only bidirectional pipes are described as having exit points that do the reverse.

The direction is not always entry. The rationale section describes unidirectional pipes as converting assets to shares through deposit and mint, or shares to assets through redeem and withdraw. An integration must therefore record which way each deployed pipe runs, not assume a default.

“A unidirectional Pipe SHOULD implement only the entry function(s) deposit and/or mint, not redeem and/or withdraw.”

ERC-7575 specification, Pipes section

Why does a successful entry not prove an exit exists?

An entry transaction proves one conversion direction: assets in, shares out. Whether the same contract converts shares back is a separate fact, and an entry-only pipe is allowed to say no.

The specification leaves one question open. Its methods section says all ERC-7575 vaults must implement ERC-4626 without the ERC-20 methods, while the pipes section says a one-way pipe should implement only entry functions. The text does not state which rule governs a pipe. In practice, a deployment could omit redeem and withdraw entirely, or expose them and block every call. An adapter has to handle both cases.

Where the exit functions exist, ERC-4626 gives a usable signal: maxRedeem and maxWithdraw must return 0 when redemption or withdrawal is entirely disabled, even temporarily. That is a capacity reading for one owner at one moment, not a permanent statement about the route. The distinction between exit previews and executable exit limits applies here before any statement shows the position as redeemable.

What does a one-way route look like in numbers?

In an illustrative case, an investor converts 250,000 units of asset A into 250,000 shares through an entry-only pipe. The only on-chain exit pays asset B through a different entry point, so the investor cannot reverse the original trade.

Assume, for illustration only, that pipe A converts at 1.00 share per asset unit and has no redeem function. The shared share token is also connected to entry point B, which is bidirectional and denominated in asset B. If entry point B applies an assumed 0.10% exit fee, previewRedeem for 250,000 shares would show about 249,750 units of asset B. The investor leaves with a different token, at a different contract, with a 250-unit difference that the statement must explain.

None of these figures describe a live fund. They show why the exit outcome cannot be reconstructed from the entry record. The entry leg shows asset A and pipe A. The exit leg shows asset B, entry point B, the fee applied and the price at execution. If the route set changes, a third outcome appears: an off-chain redemption under the offering documents, with no on-chain conversion at all.

250,000 shares entered through an entry-only pipe in asset A can exit as about 249,750 units of asset B under an assumed 0.10% fee at a separate entry point. That is a second conversion, not a reversal of the first.

ERC-4626 previewRedeem definition; illustrative editorial calculation

Which layer decides whether an investor can exit?

Three layers decide the exit: the interface says what a pipe may omit, the deployed contract shows what it does, and the product terms say what the issuer owes. Each needs its own evidence.

LayerQuestion it answersEvidence to retain
Specified interfaceMay this route be one-way?ERC-7575 text on pipes; the version checked and the date
Implementation behaviorDoes this contract expose and honor an exit for this holder?Verified code, function list, maxRedeem and maxWithdraw readings, a test exit
Product termsWhat redemption is the investor entitled to, and how?Offering documents, redemption notice terms, administrator procedure

The layers can disagree. A fund may promise redemption in its documents while the token route is entry-only, because the exit runs through the transfer agent. The reverse also happens: a contract may expose redeem while the terms restrict who may use it. The RWA token standards guide explains why a technical interface does not by itself define issuer obligations.

What should the adapter acceptance test check?

Before approval, each pipe needs a recorded direction, a tested exit or a documented alternative, and a named owner for exceptions. A passing interface check for ERC-7575 ID 0x2f0a18c5 covers none of these.

CheckPass conditionIf it fails
Direction recordedEntry-only, exit-only or bidirectional, taken from verified codeHold the adapter; do not default to bidirectional
Exit functionsredeem and/or withdraw present, or absence documentedMark the route entry-only in the custody record
Holder capacitymaxRedeem or maxWithdraw above 0 for a test holderTreat as no current exit, even if the function exists
Shared share tokenshare() resolved; other entry points listed with their assetsExit asset cannot be stated on the statement
Controlled test exitSmall exit traced from share burn to asset receiptApprove entry only, with a written restriction
Off-chain routeAdministrator procedure and terms reference on fileEscalate to the issuer before onboarding investors

Run the capacity check per holder, not once per contract. Restrictions in a permissioned share token can return 0 for one investor and a positive value for another. These are proposed acceptance checks, not findings about a named deployment.

ERC-7575 vaults must return true for interface ID 0x2f0a18c5, and share tokens must return true for 0xf815c03d. Neither identifier states whether a pipe runs one way or both ways.

ERC-7575 specification, ERC-165 support

How should records explain a missing reverse route?

The issuer, custodian and administrator records should state the investor outcome under the exception: which route applies, which asset is paid and who approved it. A transaction hash alone does not explain that.

For each position entered through a one-way pipe, keep the entry pipe, asset and share addresses, the documented exit route and the asset that route pays. Add the terms reference and the approver. When an investor requests redemption, the record should let an auditor see why the exit used a different contract or an off-chain process, and why the amount differs from the original deposit.

This guide is for custody adapters, fund administrators and issuer operations teams onboarding ERC-7575 routes. It does not cover asynchronous request flows or legal title. Tie the exception record to the wider institutional RWA custody controls so an entry-only route is visible before the first redemption request arrives.

Sources: ERC-7575 specification (pipes, rationale, ERC-165 support); ERC-4626 maxRedeem, maxWithdraw and previewRedeem. Sources checked October 27, 2026. Numerical scenarios and acceptance procedures are editorial analysis, not reports of live fund incidents.

Frequently Asked Questions

Does ERC-7575 require every pipe to support redemption?

No. The specification says a pipe may be unidirectional or bidirectional, and a unidirectional pipe should implement only deposit and/or mint, not redeem and/or withdraw. Its rationale also describes the reverse case, a pipe that only converts shares to assets. Confirm the direction of each deployed pipe rather than inferring it from the standard name.

Does a successful deposit prove the investor can exit?

No. A deposit transaction proves that the entry route accepted assets and changed the share balance. It says nothing about whether the same contract, another entry point or an off-chain process will convert those shares back. The exit route needs its own evidence: callable functions, a non-zero limit for the holder and the product terms that apply.

Does supportsInterface reveal whether a pipe is exit-capable?

Not on its own. ERC-7575 requires a vault to return true for interface ID 0x2f0a18c5, which confirms the ERC-7575 claim. The specification does not define a separate identifier for direction. Check the verified contract code, the holder-specific maxRedeem and maxWithdraw results and a controlled test exit before treating a route as two-way.

What if the only exit pays a different asset?

Record it as a different outcome, not as a reversal. Shares entered with one asset may leave through another entry point denominated in a second asset, with its own price, fees and settlement path. The investor statement, the custody record and the administrator ledger should show both asset identities and the conversion evidence for each leg.

Ready to get started?

Join others who are already using our platform.