Automated Onchain Actions

Last updated: May 20, 2026

Overview

Automated Onchain Actions let you specify a smart contract call that executes automatically the moment settled funds arrive on the destination chain. Instead of simply crediting tokens to an address, Rhino.fi can execute a defined on-chain action after bridging — enabling automated interaction with vaults, protocols, exchanges, or any smart contract.

You define the target contract and action once; Rhino handles approval, encoding, execution, and error handling. No additional steps are required from your user or your system.

Automated Onchain Actions are a premium Extension. Your account must have this feature enabled before the postBridgeData field will be accepted on quote or SDA generation requests. Contact your account representative to enable it.

How Automated Onchain Actions Are Defined

An Automated Onchain Action is configured through a postBridgeData field added to your bridge quote or Smart Deposit Address generation request. The field accepts:

  • A tag (_tag) that identifies the specific action to execute

  • Optional custom parameters to specify targets such as a vault, user ID, or invoice ID

Rhino configures everything else: token approvals, amount injection, contract-specific inputs, gas estimation, and execution sequencing.

Why Use Automated Onchain Actions

Automated Onchain Actions allow clients to:

  • Define precise end-states for customer deposits

  • Offer yield, staking, vault, or protocol integrations

  • Trigger off-chain crediting systems (e.g. exchange account top-ups) via on-chain signals

  • Automate payment routing, escrow, and invoice flows

  • Avoid building and maintaining custom blockchain execution infrastructure

Your customers do not need to manage:

  • Manual swap or approval flows

  • Cross-chain bridging logic

  • Gas management for multi-step interactions

  • Direct protocol interactions

Common Use Cases

Yield and protocol integrations Deposit bridged funds directly into a vault, lending pool, or staking contract. The user's recipient address receives the protocol's output token (e.g. vault shares or staked positions).

Custodial and off-chain crediting Trigger a contract that signals an off-chain system — crediting a user's account, updating a balance, or notifying a clearing layer — without requiring the user to interact with your system directly.

Payments and holding accounts Route funds to a payment processor, holding account, or escrow. Useful for on-chain invoicing, subscription flows, or multi-party settlement.

Example: Deposit Into a Yield Vault

A user holds USDT on Arbitrum and wants exposure to a USDC vault on Base (for example, a Morpho yield vault).

Without Automated Onchain Actions, the user would need to:

  1. Swap USDT to USDC

  2. Bridge USDC from Arbitrum to Base

  3. Approve the vault contract

  4. Execute the vault deposit

This involves multiple steps, approvals, gas payments, and protocol interactions across two chains.

With Automated Onchain Actions + Smart Deposit Addresses, you generate one deposit address per user. They send USDT on Arbitrum. Rhino.fi swaps, bridges, and executes the vault deposit automatically. The user's wallet receives vault shares on Base.

From the user's perspective, the entire flow is reduced to a single transfer.

What Happens If the Action Fails

If the contract call reverts on the destination chain, funds are not lost. Depending on your account configuration, Rhino will either retry (for transient failures), credit the destination token directly to the destinationAddress, or notify you via webhook and await instructions.

Limitations

  • ERC-20 tokens only — native gas tokens (ETH, SOL, etc.) cannot currently be the input to an Automated Onchain Action

  • One action per bridge — chaining multiple contract calls in sequence is not currently supported

  • EVM destination chains only — non-EVM destinations such as Solana are on the roadmap

  • Account enablement required — the postBridgeData field is only accepted on accounts with this Extension active

For configuration and supported integration details, contact your Rhino.fi account representative or refer to the API Docs.