> ## Documentation Index
> Fetch the complete documentation index at: https://apidocs.bridge.xyz/llms.txt
> Use this file to discover all available pages before exploring further.

# Supported Blockchains

> Reference guide for all blockchains supported by Bridge

Bridge supports 10+ blockchains across EVM and non-EVM ecosystems. The `payment_rail` field in transfer, liquidation address, and virtual account requests is how you specify which chain to use.

<Tip>
  Check the [Route Explorer](https://apidocs.bridge.xyz/get-started/introduction/what-we-support/payment-routes#route-explorer) for the full list of supported currencies per chain.
</Tip>

## Chain-Specific Fields

### `blockchain_memo`

* Stellar, Tron, and Tempo support an optional `blockchain_memo` field on the transfer `destination` object. This is a configurable field for sending memos to blockchain destinations. The memo can be used to add additional payment details to the transaction.
* For Stellar deposits, a memo is a required field. It is returned in deposit instructions and **must be included by the sender.**

```json theme={null}
{
  "destination": {
    "currency": "usdc",
    "payment_rail": "stellar",
    "to_address": "GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5",
    "blockchain_memo": "4891237045"
  }
}
```

### `memoless_address`

* For **Stellar deposit addresses**, Bridge returns a `memoless_address` alongside the standard `blockchain_memo`. This is a **Stellar muxed account address** (M-address) that encodes the routing memo directly into the address string itself, so your customers don't need to include a separate memo field when sending.