Wallets, custody platforms, exchanges, and fintech products typically need to add network support one integration at a time. Their teams then repeat that work for each protocol, transaction flow, and position type they want to support.
We believe network distribution should begin with reusable infrastructure.
Yield.xyz supports Arc from day one. Clients can enable support for Arc through the same normalized API and action model they already use across other networks, without maintaining a separate protocol-by-protocol integration stack.
As we support yield opportunities available through protocols on Arc, they can be surfaced through the same discovery, transaction, and position workflows clients already use with Yield.xyz.
Financial infrastructure needs predictable execution
Arc is an open, EVM-compatible Layer 1 built for financial markets, real-time value movement, and agentic economic activity.
Arc uses stablecoins as gas, starting with USDC. Fees are predictable and dollar-based, while deterministic sub-second finality gives applications a clear view of when transactions have settled.
Those properties matter for financial products. Applications need to estimate costs, communicate transaction status, and track positions without introducing unfamiliar network mechanics into the user experience.
EVM compatibility also means Arc can work with established transaction and account infrastructure. Product teams can support the network while retaining control over their interface, signing flow, and custody model.
One action model for Arc
Yield.xyz standardizes how applications discover opportunities, construct transactions, and track positions across networks.
When we elect to support an opportunity available through a protocol on Arc, clients can surface it through the same core workflows they already use with Yield.xyz. The API returns the information and unsigned transaction data the application needs, while the application retains control over signing and execution.
This means clients don't need to build and maintain a separate integration for every opportunity we support on Arc. Product teams can use the same integration patterns instead of independently mapping each protocol's contracts, actions, and position states.
Yield.xyz also separates network support from the end-user product. Each client decides which supported opportunities to make available, how to present them, and which signing infrastructure to use.
Distribution without another integration queue
Adding a network directly to one product creates one distribution surface. Supporting Arc through a shared integration layer gives Yield.xyz clients a consistent way to evaluate and enable opportunities on the network.
Applications don't have to start again with network configuration and protocol adapters each time a new supported Arc opportunity becomes available. Yield.xyz can add confirmed opportunities to the same infrastructure clients already operate, allowing coverage to expand alongside the network.
Protocol and market availability depends on deployments by protocols on Arc. We will determine which opportunities to verify and support, without requiring clients to rebuild the underlying integration for each addition.
Arc support from day one
Yield.xyz supports Arc from day one.
As we support yield opportunities available through protocols on Arc, clients will be able to access them through the same normalized discovery, transaction, and position-management workflows they already use with Yield.xyz.
This gives wallets, custody platforms, exchanges, and fintechs a reusable way to expand their Arc coverage without returning to a separate protocol-by-protocol integration process each time a new supported opportunity goes live.
