User guide

Using Oracle

Oracle separates research, proposal, authorization, broadcast, and proof. That separation is the product, not extra ceremony.

Native chatPrepare firstReceipt verified

Native chat

The bare oracle command starts Oracle's own agent loop. The selected model can change without changing the Oracle persona, sessions, or active chain.

chat commands

/sessions             list sessions
/new research ARB     create a session
/resume 2             resume by number
/chain hyperliquid    select a chain
/model                choose a model
/setup                messaging setup
/help                 all commands

Action lifecycle

Read

Resolve the asset, chain, venue, and current state. Missing evidence stays explicit.

Quote and simulate

Compare routes, include measurable gas and fees, and test the exact action where supported.

Prepare

Return an unsigned transaction, typed-data intent, ordered bridge transaction list, or PSBT plan.

Authorize

Your wallet signs by default. The optional local signer requires explicit self-hosted setup and bounded policy.

Verify

Report success only from chain evidence. A submitted hash without a successful receipt is not completion.

Best execution

The highest gross quote is not necessarily the best route. Oracle compares available sources and ranks by net received after measurable gas and fees. Unknown cost is never treated as free.

route

oracle-route swap base 0x4200...0006 0x8335...2913
oracle-route bridge arbitrum base

# prepare the winner for the real signing wallet
oracle-route prepare base <tokenIn> <tokenOut> <yourWallet>
oracle-route prepare-bridge arbitrum base <yourWallet>

Bridge completion

A confirmed origin transaction does not prove destination funds arrived. Bridge preparation may return more than one transaction and order matters.

Build and mint

Ask Oracle to scaffold or review a fungible token, NFT collection, protocol, gacha, DEX, launchpad, or capped mint workflow. Oracle classifies the target chain family, checks for a reviewed adapter, and keeps deploy, metadata, liquidity, mint, and authority changes as separate approvals.

Builder output is prepare only: plans, source, tests, simulations, and unsigned deploy or admin artifacts. Unsupported adapters fail closed. A generic transaction builder is not permission to deploy, and every wallet-signable artifact still needs chain, target, value, gas, and authority review.

Mint caps remain binding

NFT mint preparation must fit the authorized quantity, spend, gas, per-unit, and priority-fee caps. RPC acceptance is not mint success; verify the receipt and resulting ownership.

Portfolio reads

Portfolio and approval scans use public addresses. Missing address families are reported as not configured, provider failures as unavailable, and unsupported families as unsupported.

public addresses

export ORACLE_EVM_ADDRESS=0x...
export ORACLE_SOLANA_ADDRESS=...
export ORACLE_BITCOIN_ADDRESS=bc1...
export ORACLE_HYPERLIQUID_ADDRESS=0x...
oracle data serve

Receipts

Oracle does not treat an RPC acceptance response as settlement. A successful result requires coherent transaction and chain references plus included or final evidence under the configured finality rule.

Transaction hash matches the prepared action
Receipt indicates success
Sender, destination, calldata, and chain remain bound
Balance deltas are marked verified only when snapshots prove them
Unknown, dropped, replaced, or reorganized outcomes stay explicit