What is ORBX?
ORBX is a cross-chain execution layer designed to coordinate asset movement across multiple networks. Applications submit an intent containing the source network, destination network, asset and amount. ORBX resolves that intent into an eligible execution path and exposes a single settlement lifecycle back to the application.
Request a route
A route request contains the minimum information needed to resolve an execution path.
const route = await orbx.route({ asset: "USDC", amount: "1000", from: "ethereum", to: "robinhood" }); await route.execute();
Execution methods return route state that applications can observe until destination settlement is final.
Execution architecture
The architecture separates intent normalization, route resolution, execution and settlement observation. This keeps the application surface stable while allowing the routing layer to evolve independently.
Intent layer
Normalizes the user requirement into a consistent request containing asset, amount and network constraints.
Routing layer
Evaluates eligible source-to-destination paths and resolves execution constraints.
Settlement layer
Tracks the selected route through destination finality and returns explicit lifecycle state.
Route lifecycle
A route can move through created, ready, executing, settling and settled. Applications should respond to lifecycle changes rather than assume a fixed completion time.
Destination finality
Settlement is complete only when the destination state is resolved for the requested route. Finality conditions depend on source network, destination network and route composition.
Network adapters
Each supported network is represented behind an adapter responsible for chain-specific execution and state observation. Robinhood Chain is represented in the same routing model as other connected networks.
- Source and destination normalization
- Route capability checks
- Execution state observation
- Destination settlement reporting
SDK surface
The SDK is organized around route creation, execution and settlement observation. API signatures will remain stable as routing composition evolves.
Deployment registry
Chain-specific deployment addresses and interface metadata will be published through the canonical ORBX deployment registry as execution contracts are activated.
Security model
ORBX is designed around minimized custody assumptions, explicit route state and verifiable deployment metadata. Contract scope, operational controls and review references will be published with active deployments.