React Native

React Native partners should use the same API and SDK flow as web partners, with a wallet provider compatible with EIP-1193 or an adapter that can send the returned transaction objects.

Mobile requirements

Use the hosted API for state and action quotes.
Use SDK readiness helpers.
Use prepared-action helpers before opening the wallet.
Do not scan chain history from the device.
Rebuild expired quotes.
Handle chain switching explicitly.
Treat typed API error codes as product states.

Suggested screen states

State	Behavior
Loading	Fetch health, vault, config, and position
Read-only	Show product if display readiness is true
Deposit unavailable	Show reason from readiness code
Approval required	Present approval as step 1 of 2
Deposit	Present deposit as step 2 of 2
Queued redeem pending	Show cancel if request is cancelable
Queued redeem claimable	Show claim as primary action

Prepared actions

import { parseUsdc, preparePartnerDeposit } from "@arc/shlp-sdk";

const prepared = await preparePartnerDeposit(shlp, {
  amount: parseUsdc("100"),
  account: userAddress,
  receiver: userAddress,
  slippageBps: 50,
});

if (!prepared.canAskForSignature || !prepared.flow) {
  showBlockedState(prepared.title, prepared.description);
  return;
}

for (const step of prepared.flow.steps) {
  const hash = await wallet.sendTransaction(step.tx);
  await waitForReceipt(hash);
  if (step.refreshQuoteAfterConfirm) {
    // Approval confirmed. Re-run preparePartnerDeposit before deposit.
    return;
  }
}

Network selection

Withdraw receive-network selection chooses the user’s final USDC destination. The Signalite tx still executes on HyperEVM. For non-HyperEVM instant redeems and claims, the tx receiver is the Relay deposit address returned in action metadata. For queued redeems, the Relay deposit address is not available until the later claim action. For Partner Actions, pass receiveChainId on withdrawal creation:

await partnerBackend.createQueuedRedeemAction({
  sharesRaw,
  userAddress,
  receiveChainId: 8453,
});

await partnerBackend.createClaimAction({
  redeemId,
  userAddress,
  receiver: userAddress,
  receiveChainId: 8453,
});

If omitted, the receive chain defaults to HyperEVM 999. Valid values come from config.withdraw.supportedDestinations. For non-HyperEVM destinations:

redeem_instant and claim_redeem should include postSettlementBridge.mode="deposit-address" and postSettlementBridge.relay.depositAddress.
redeem_async should include postSettlementBridge.mode="post-claim-quote" and postSettlementBridge.relay=null. This is valid; show the queued state.

Execute the HyperEVM tx returned by Signalite, wait for a successful receipt, then poll Relay with metadata.withdrawal.postSettlementBridge.relay.requestId only when Relay metadata is present. Do not execute a separate Relay bridge transaction and do not submit Relay hashes to Signalite. After submitting the final HyperEVM action tx hash to Signalite, treat status: "indexed" as the fast success state. Signalite has verified the receipt and inserted the decoded V2 action event into canonical activity, so the app does not need to wait for the cron indexer before showing confirmation. If indexingPending is true, keep polling the action and bootstrap endpoints. Persist the selected receiveChainId for queued redeems and reuse it when the claim becomes available. Queue fulfillment is FIFO; do not let a later smaller withdrawal jump an earlier larger pending withdrawal. For deposits, non-HyperEVM source networks are pre-deposit funding routes, not Signalite vault transactions. The mobile app should:

Use Relay or an equivalent partner funding route to move source USDC into HyperEVM USDC for the user’s EVM wallet.
Wait for the HyperEVM USDC balance to update.
Create/refresh the Signalite Partner Action deposit.
Execute only the returned HyperEVM wallet steps.

EVM sources such as Ethereum, Base, Arbitrum, Optimism, Polygon, and Avalanche can use a Viem-compatible Relay wallet adapter. Solana requires Relay’s SVM/Solana wallet adapter and must settle proceeds to the user’s associated EVM wallet on HyperEVM before the Signalite Partner Action starts.

Start

Build flows

SDK

Operations

Mobile requirements

Suggested screen states

Prepared actions

Network selection

​Mobile requirements

​Suggested screen states

​Prepared actions

​Network selection

Mobile requirements

Suggested screen states

Prepared actions

Network selection