Are you an LLM? Read llms.txt for a summary of the docs, or llms-full.txt for the full context.
Skip to content

Limitations

Heat v0.4.0 is an early release. This page lists known limitations so you can plan accordingly.

Bridging is available, but scoped

Heat now includes LI.FI-backed EVM routing and bridge execution.

Current scope is intentionally narrow:

  • supported EVM-focused routing and bridge execution
  • best fit for Ethereum, Polygon, Arbitrum, Base, and supported Optimism routes
  • not a promise of universal all-chain/all-token support
  • not non-EVM execution
  • not HyperCore support

Always preview with --dry-run first.

Hyperliquid funding is still external

Heat does not yet include a Hyperliquid deposit or funding flow. You still need to fund the Hyperliquid account externally, then return to Heat.

Polymarket deposit flow is still partly external

Heat can fetch Polymarket deposit addresses, but it does not move the funds for you into Polymarket directly.

Use:

  • heat pm bridge deposit
  • fund externally
  • heat pm bridge status

Aave scope is phase 1 only

Aave support is intentionally narrow today.

Supported:

  • markets
  • positions
  • health
  • supply
  • withdraw

Not supported yet:

  • borrow
  • repay
  • collateral toggles
  • eMode
  • rewards

DefiLlama is read-only market data

DefiLlama integration is read-only — 42 commands across 9 endpoint families (27 free + 15 pro).

Current limitations:

  • Not yet shipped: ecosystem intelligence, institutions, ETFs, and FDV performance families are planned but require live API validation before inclusion
  • No HTTP-layer integration tests yet — unit tests cover mapping and URL construction only
  • Pro API key required for bridges, some yields, some volumes, some coins, dominance, and usage commands
  • Upstream API responses are sometimes inconsistent in field types (handled gracefully)

Local key accounts only

Heat stores encrypted private keys locally in ~/.heat/keys/. There is no support for:

  • Hardware wallets (Ledger, Trezor)
  • Remote signers or KMS
  • Multisig wallets
  • WalletConnect or browser wallet integration

No TUI or interactive mode

Heat is a non-interactive CLI. There is no terminal UI, no interactive order entry, and no live dashboards. Use piping and scripting for automation.

Polymarket API key commands

The heat pm clob api-keys, heat pm clob create-api-key, and heat pm clob delete-api-key commands remain limited by an upstream SDK issue. They should not be treated as a production-ready part of the current release.

No shell completion

Shell tab-completion (bash, zsh, fish) is not yet shipped. You can rely on --help at any level:

heat --help
heat hl --help
heat lifi bridge --help

Single-account per command

Each command operates with a single resolved account. There is no batch mode or multi-account fan-out built into Heat itself. You can script around this:

for acct in alice bob charlie; do
  heat hl balance --account "$acct" --json
done

Known caveats

  • Integration tests are still thinner than the unit-test and mapping-test coverage.
  • Hyperliquid funding/deposit flows remain manual.
  • Aave is intentionally not full-surface yet.
  • LI.FI scope is honest but still deliberately narrow.
  • DefiLlama is read-only market data (42 commands, 9 families); some endpoint families not yet shipped pending live API validation; no HTTP-layer integration tests yet.
  • Heat does not do interactive password prompts yet. Use --persist-password, --password-file, --password-env, or HEAT_PASSWORD.
  • All financial amounts are handled as strings/decimals to preserve precision; never as floating point.