Skip to main content
No new contracts. SODAX’s Hedera spoke contracts are already live; your entire integration is TypeScript. Your users sign ordinary EVM transactions through Hedera’s JSON-RPC relay, and SODAX coordinates cross-network execution, routing, and recovery behind the scenes.
You keep shipping on Hedera. SODAX absorbs the cross-network execution layer, so your product can offer trading and lending against every asset in the SODAX System, 166 across all supported networks, without leaving your stack. Integration happens in TypeScript, at the SDK or React layer, against Hedera’s EVM. There is nothing to deploy, audit, or maintain on-chain. Using SODAX is free. Trades carry a fixed 0.1% base fee taken by the protocol, and you set your own platform fee on top. That part is fully yours, both the rate and the revenue. See Monetize SDK.

​
Three things that differ from other EVM networks

Hedera runs the EVM, but its account and token model is its own. SODAX handles the parts it can; these three are yours to know about:
  • Accounts must use an ECDSA key. Hedera’s EVM tooling only signs with ECDSA (secp256k1). Accounts with an ED25519 key can hold HBAR and tokens but cannot sign the EVM transactions SODAX uses. MetaMask and other EVM wallets create ECDSA accounts by default.
  • HBAR has 8 decimals in the SDK, 18 on the wire. SODAX tracks HBAR in its canonical 8 decimals (tinybars) and scales msg.value and native balances for Hedera’s EVM layer, which reports 18-decimal weibars. Always build amounts from token.decimals, and do not mix SDK balances with raw eth_getBalance reads.
  • Receiving a token can require an association. Hedera tokens are native HTS tokens, addressed through their EVM address. An account receives a token only if it is associated with it or has a free automatic association slot. Accounts auto-created by sending to an EVM address have unlimited automatic associations; older or natively created accounts may not. See Receiving tokens on Hedera.

​
What you can build

Two SODAX modules are relevant to Hedera builders:

Swaps

Intent-based cross-network swaps. Users swap between HBAR or HTS tokens and assets on any supported network with one signed transaction on Hedera. Solvers fill; SODAX routes and settles.

Money Market

Cross-network lending and borrowing. Supply from Hedera, borrow to Hedera or any other supported network, and manage positions without running lending infrastructure.

​
Choose your integration path

​
Scope and build with AI

Point your AI coding assistant at the SODAX Builders MCP and it gains live access to the whole SODAX System: supported chains and tokens, real swap quotes, money market rates, intent history, and these docs. It works in Claude, Cursor, VS Code, Windsurf, and any other MCP-capable client.
Use it to scope before you commit: your assistant can read your own codebase, pull real quotes and token lists, and map exactly where SODAX fits in your product. Full tool list and per-client setup at builders.sodax.com.

​
In this section

  • Quickstart: install the SDK, connect a Hedera account, make your first cross-network swap.
  • Swaps on Hedera: approvals, quoting, fees, and receiving HTS tokens.
  • Money Market on Hedera: supply, borrow, repay, and withdraw with cross-network collateral.
  • Wallets: EVM wallets on Hedera, and every other network’s wallets through one interface.
  • Networks & Assets: what is live on Hedera today and what your users can reach.
  • Hedera FAQ: the questions Hedera engineers actually ask.

​
Hedera references

  • Hedera documentation: accounts, HTS tokens, and the EVM on Hedera.
  • Auto account creation: how EVM-address accounts are created and why they get unlimited automatic token associations.
  • Mirror nodes: public REST endpoints for account, token, and association lookups by EVM address.
  • HashScan: the Hedera mainnet explorer, for checking transactions and token associations.
Building something? Start with the Quickstart.