Exchanges and trading desks are constantly looking for reliable infrastructure that allows them to run complex workflows without compromising security or flexibility. OpenOcean, for example, is a leading DEX aggregator that enables trade aggregation, cross-chain swaps, and more for both institutions and individuals. One recurring question we hear from prospective clients is simple:

‍

“Can I move my existing custody integration over to io.finnet without breaking my workflows?”

‍

The short answer: yes.

‍

In fact, io.finnet was designed for this exact use case: giving institutions full self-custody, sole possession of their private key and smooth integration with the same DeFi and aggregator APIs they already rely on.

‍

From Legacy Custody Providers to io.finnet: A Common Workflow

‍

Take the example of how exchanges interact with OpenOcean, a leading DEX aggregator.
Here’s a standard workflow on a regular custodial platform today:

‍

1. Get quotes from OpenOcean’s Aggregator API.
2. Build transactions for approvals and swaps, targeting OpenOcean’s smart contract.
3. Push transactions into the custodial platform via their SDK and Web3 Provider.
4. Co-sign and broadcast via the custodial platform’s internal signing setup.

‍

With io.finnet, the flow looks familiar but with more flexibility and without the bottlenecks of a provider co-signer:

‍

1. Generate quotes from OpenOcean’s Aggregator API, exactly the same step.
2. Construct transactions against the OpenOcean proxy contract.
3. Use io.finnet’s Wallet Engine APIs (our programmatic Web3 interface) to sign and broadcast.
   
   • This works directly with our trustless MPC vaults.
   • Signatures are generated without ever exposing private keys.
4. Enforce policies and weights via io.finnet’s weighted signing power model, which lets you create manual or automated approval flows depending on the risk level of each transaction, without relying on a centralized co-signer.

‍

For teams already familiar with Fireblocks’ Web3 provider, io.finnet offers an EVM-compatible experience while removing limitations like AUC fees, transaction caps, or dependency on a single provider’s infrastructure.

‍

What About Limit Orders?

‍

OpenOcean also offers limit orders, but many institutions struggle to integrate them at scale:

‍

• The Browser Wallet SDK is front-end only, designed for individual wallets.
• The Private Key Wallet SDK assumes direct private key management, which doesn’t align with institutional custody models, where keys are never directly accessible and approvals must follow strict policies.

‍

With io.finnet, institutions can bridge this gap by:

‍

• Using Virtual Signers to run policy-based, automated signing for limit orders.
• Keeping keys fully secured inside trustless MPC vaults, never managed or exposed outside the custody framework.
• Tailoring workflows per desk or per user, ensuring security, compliance, and operational efficiency.

‍

A Practical Example: Multi-vault, Multi-Signer Workflow

‍

To make it concrete, here’s how an exchange could structure their OpenOcean workflow with io.finnet:

‍

• Vault setup: Create separate vaults for different trading desks (Spot, Derivatives, Arbitrage…). Each vault is segregated and chain agnostic (BTC, ETH, SOL…)
• Virtual Signers: Assign one or more Virtual Signers per vault. These signers enforce policies automatically, such as “auto-approve swaps below $50k” or “require dual manual approval for trades above $500k.”
• Manual Signers: For high-value transactions, weight approval toward senior managers or compliance officers. Weighted signing ensures that their input is required only when risk thresholds are crossed.
• Automated flow: When an OpenOcean quote is accepted, low-risk transactions can be executed instantly via the Virtual Signer, while higher-risk ones are automatically routed for manual approval, all within the same workflow.

‍

Why Exchanges Are Exploring io.finnet

‍

The interest in io.finnet comes down to three differentiators:

‍

• Flat pricing: Flat subscription, no AUC or bps on trades.
• True self-custody: No provider co-signer, no hidden keys.
• Programmable workflows: EVM-compatible APIs that fit directly with aggregator APIs like OpenOcean.

‍

For exchanges, this means they can migrate without disruption and expand trading functionality that wasn’t possible before.

‍

Try It Yourself

‍

We’ve prepared sample repositories that demonstrate these workflows with OpenOcean and io.finnet. If you’re an exchange or trading desk evaluating migration from your current custody setup, our team can provide access and guide you step-by-step through replicating your environment.

Book a demo to see how your existing workflows translate seamlessly to io.finnet.

‍

More About OpenOcean: OpenOcean is the leading DEX aggregator delivering best execution across AMMs, RFQ, order books, derivatives protocols, and cross-chain bridges. With comprehensive coverage spanning across major EVM chains and non-EVM chains, traders access optimal prices through their advanced routing engine. Their complete DeFi trading suite includes swaps, limit orders, DCA, gasless transactions, perpetuals, staking rewards, and lending protocol integrations. Trusted by major wallets and protocols through robust API/SDK integrations, OpenOcean provides the infrastructure powering next-generation decentralized trading with MEV protection and flash loan capabilities.