What is a THORChain inbound address?

An inbound address is the address on a connected chain where you send coins to THORChain, and it belongs to the active vault that THORChain’s nodes control together. It changes when the vaults change, so read the current one right before you send.

Also called vault address.

How it works

Each connected chain has an inbound address for its active Asgard vault. Coins sent to that address are processed by THORChain, and the memo tells THORChain what to do with them.

Which address you use depends on the chain you send from, because each chain has its own inbound address.

Why it changes

Churn cycles change the set of validator nodes. After each churn, the active vault becomes retiring, its funds move to a newly created vault, and the newest vault starts receiving deposits right away.

The inbound address changes along with the vault, so an address copied from an old page can be out of date.

THORChain’s documentation warns never to send funds to a retired vault address, because funds sent to a vault that has become inactive cannot be recovered.

Before you send

  • Look up the inbound address for the chain you are sending from on the inbound addresses endpoint, right before you send.
  • Send right after you read the address, because a delay can leave you sending to an outdated vault address.
  • Check that the network is not halted before you send.
  • Include the memo exactly as written, since THORChain reads the instruction from it.

In Redacted

Redacted’s core contributors run a THORNode with public, read-only endpoints, and the API at api.redacted.money lists THORChain’s inbound addresses for anyone to check.

Related terms

Sources: Sending transactions, THORChain developer docs · Bifrost, TSS and vaults, THORChain documentation

Updated November 1, 2026. All terms