Create an Execution Request

An execution request defines what should happen on-chain and under what constraints.

const execution = await helios.execute({
  asset: "USDC",
  amount: "4500",
  fromChain: "ethereum",
  toChain: "arbitrum",
  options: {
    slippage: 0.5,
    riskLevel: "balanced"
  }
});

Execution requests are validated before submission.
If validation fails, no transaction is sent.

Single-Chain Execution

Single-chain executions occur entirely on one blockchain.

await helios.execute({
  asset: "ETH",
  amount: "1.2",
  chain: "ethereum"
});

Helios handles routing and gas estimation, but signing and submission remain external.

Cross-Chain Execution

Cross-chain executions coordinate actions across multiple chains.

await helios.execute({
  asset: "USDC",
  amount: "4500",
  fromChain: "ethereum",
  toChain: "arbitrum"
});

Helios automatically:

• Selects bridging mechanisms

• Coordinates execution order

• Tracks confirmations across chains

Executions fail atomically if required steps cannot complete.

Transaction Lifecycle

Each execution follows a deterministic lifecycle.

created → simulated → pending → executed | failed

Lifecycle transitions reflect real execution state, not assumptions.

Status & Confirmations

You can query execution status at any time.

const status = await helios.getExecution(execution.id);

console.log(status.status);

Status values:

• created — request accepted

• pending — transaction submitted

• executed — confirmed on-chain

• failed — execution did not finalize

Confirmations are chain-specific and included in the response.

Error Handling

Errors are explicit and execution-aware.

{
  "error": {
    "code": "EXECUTION_FAILED",
    "message": "Transaction reverted during execution"
  }
}

Common execution errors include:

• INSUFFICIENT_LIQUIDITY

• RISK_THRESHOLD_EXCEEDED

• EXECUTION_FAILED

• UNSUPPORTED_CHAIN

Failed executions are safe to inspect and retry after re-simulation.