Portals helps you find yield positions reachable from supported tokens and networks

Portals is useful when your DeFi yield search needs both cross-protocol comparison and a route from a supported token. The dashboard suits searches spanning networks, where finding a position and reaching it involve different dependencies. Filters narrow the catalog, while integrated routing connects compatible holdings to the selected destination. That combined flow fits when the exposure suits your intended holding and the available route satisfies your execution requirements.

Updated · Monday, October 19, 2026

Yield Searches With a Defined Asset Scope

Chain, protocol, asset, and yield-type filters make the dashboard useful when a broad search needs a consistent boundary. Displayed annual percentage yield (APY), total value locked (TVL), and price information support comparison within that boundary. Pools, vaults, lending markets, and staking positions can all appear in the search, so the intended type of exposure matters before ranking candidates.

Asset and Network Boundaries

An asset-specific search helps when the aim is to retain exposure to a particular asset while examining available yield positions. A network filter serves a different purpose: it limits the destination environment. Keeping those choices explicit prevents a search for yield on an existing holding from quietly becoming a decision to acquire a different asset.

Newly Discovered Opportunities

Newly indexed positions make Explorer useful for discovering additions to the available market. Their appearance supplies another candidate, not a history of dependable returns. A recent listing needs its underlying yield source understood before it belongs beside established alternatives in a shortlist.

When Is Yield Discovery Useful Without an Entry?

Yield discovery is useful without an entry when the immediate goal is a shortlist or an explanation of where returns originate. Position details expose the yield source, while sorting helps organize candidates around the search preferences. Research can finish with a decision to retain the current holding rather than establish a new position.

Cross-Network Access From Existing Holdings

Cross-network entry fits when a suitable yield position sits on a different supported chain from the asset available for entry. The integrated flow connects discovery with the swaps, transfers, and deposits needed to reach that destination.

Relay provides the cross-chain routing and settlement layer used by Explorer. Portals handles discovery and scoring, then routes the selected zap into the destination position.

Open full-size image

Compatibility concerns the actual starting token, its network, and the selected destination. Broad catalog coverage does not establish every possible route between them. The relevant question is whether the available route reaches the selected position on acceptable terms, including its proposed output and any disclosed execution costs.

If the required token or network lacks route support, stop at discovery and assess another supported access method. Keep the destination exposure unchanged when comparing access methods, so a convenience decision does not silently become a change in what you hold.

sUSDS Access Through Osero Earn

The Osero Earn integration lets you access sUSDS, the yield-bearing version of Sky's USDS stablecoin, through Explorer. The savings mechanism has no lockup and requires no active strategy management.

Savings Exposure

sUSDS represents accumulated savings through its value per token in USDS. The token count can stay unchanged as each token becomes redeemable for more USDS. Monitoring this savings position therefore involves the USDS value represented by each token, alongside the amount of sUSDS held.

The savings rate and the value represented by each token are changing inputs. A previously displayed APY does not establish the rate over a future holding period.

Network Fit

The Osero Earn integration provides sUSDS access across Ethereum, Base, Arbitrum, and Optimism. Network choice affects the entry path from existing assets, even when the intended savings exposure is similar. A suitable same-network route can avoid a cross-network transfer; moving to another network introduces that additional dependency. Existing asset location therefore belongs in the network decision alongside access to the desired sUSDS position.

Specialized Exposure and Participation Limits

Looping vaults, niche stablecoin strategies, and tokenized assets make the catalog useful for searches beyond conventional lending. Their sources of return differ, so the mechanism generating yield matters when judging each position. A shared dashboard format does not make the exposures interchangeable. Route convenience becomes relevant after the underlying strategy fits the search.

Coinbase Tokenized Stocks on Base exclude United States users, and further jurisdictional restrictions may apply. Cross-network routing changes the access path, while the destination product retains its participation conditions. This makes eligibility part of position selection before route convenience becomes decisive.

Conditions for Choosing an Entry Route

A route belongs on the shortlist only if it reaches the right position from the actual assets available for entry.

• The selected asset, network, and yield type match the position you intend to hold.
• The position details explain the source of yield sufficiently for the holding decision.
• An available route connects the actual starting token and network to the selected destination.
• The proposed output and any disclosed costs fit limits set before authorization.
• You meet the destination product's participation requirements, including any applicable jurisdictional restrictions.

Does Submission Mean the Destination Position Is Ready?

Submission does not establish a completed entry, even when the interface groups the activity into one flow. Completion requires the intended holding on the destination network. A route proposal describes an expected operation.

For cross-network entry, source-chain activity alone does not demonstrate that the destination holding is available. Check the resulting position before treating the entry as finished. A later action that needs this position must wait until the holding is available.

Open full-size image

Portfolio Monitoring and Embedded Applications

Explorer supports tracking an sUSDS position alongside the rest of a portfolio, which suits keeping savings exposure and yield discovery together. Tracking is distinct from searching for a replacement position or deciding to move assets.

The API serves a different requirement: integrating discovery and execution into another application. Cross-chain integrations can construct source-chain transactions with route context and settlement previews. This access method fits an embedded product workflow, while Explorer provides the interactive discovery surface. For execution, either interface must support the intended position and route.

Direct Protocol Access for Additional Controls

A protocol interface may be preferable when it supports a required position action the available aggregated route does not cover. Catalog presence establishes a discovery relationship; it does not establish access to every action an underlying protocol permits.

Open full-size image

For an entry-only task, discovery and a compatible route may supply the required functions. For further position management, identify the next action and check whether the integrated flow or the protocol interface supports it.