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

# Stellar

> What is different about building on Stellar with Blockradar: assets, activation, memos, swaps and smart contracts

> [!NOTE]
>
> In a nutshell\\
>
> Stellar works like the other chains on Blockradar, with a few protocol rules
> of its own. Accounts must be activated and funded with XLM before they can
> hold assets, many recipients need a memo, and swaps and contract calls have
> Stellar-specific rules. This page summarizes each one and links to the full
> section.

## Supported assets

| Asset | Mainnet | Testnet |
| - | - | - |
| XLM (gas) | Yes | Yes |
| USDC | Yes | Yes |
| EURC | Yes | Yes |
| USDT | Yes | No |
| PYUSD | Yes | No |

Use the [Get Assets API](https://docs.blockradar.co/en/api-reference/miscellaneous/get-assets.md) for the
current list and each asset's `assetId`. For testnet tokens, see the faucets on
[Supported Assets](https://docs.blockradar.co/en/use-cases/supported-assets.md).

## Activation and XLM reserves

A Stellar account does not exist on-chain until it is funded, and it needs a
trustline for every non-native asset it holds. Blockradar activates each new
address automatically:

* Your master wallet funds the address with **0.5 XLM × (2 + number of
  trustlines)**, for example 2 XLM with USDC and EURC enabled.
* Trustlines are added for every Stellar asset enabled on the wallet.
* If the master wallet is short of XLM, activation is retried until it is
  funded.

Only share an address once `configurations.stellar.activated` is `true`.

[Address Activation →](https://docs.blockradar.co/en/essentials/address-activation.md#stellar)

## Memos and recipient addresses

Exchanges and custodial platforms often credit Stellar deposits by memo. Set
the memo on a withdrawal with `recipientRouting` (`memo_id`, `memo_text` or
`none`). Withdrawals accept three recipient formats:

* `G...` classic accounts
* `M...` muxed accounts, which carry the routing ID in the address, so you
  don't send `recipientRouting`
* `C...` Soroban contracts, for token withdrawals only

[Memos on Stellar →](https://docs.blockradar.co/en/use-cases/withdraw-stablecoins.md#memos-on-stellar) ·
[Stellar Recipient Addresses →](https://docs.blockradar.co/en/use-cases/withdraw-stablecoins.md#stellar-recipient-addresses)

## Swaps and bridges

* **To Stellar:** use `recipientRouting` to tell Blockradar whether the
  destination needs a memo. A `G...` recipient must already have a trustline
  for the asset.
* **From Stellar:** swap or bridge a Stellar asset to another chain on mainnet.
  Swaps from Stellar to Solana or Tempo are not supported.

Swaps on testnet are not supported for Stellar.

[Swap →](https://docs.blockradar.co/en/use-cases/swap.md#stellar-recipient-routing)

## Smart contracts

Stellar contract calls go through the [Signing API](https://docs.blockradar.co/en/essentials/signing.md):
build a Soroban transaction, simulate and assemble it, then sign and broadcast
it with Blockradar. The Smart Contracts API supports EVM and Tron only.

[Stellar Soroban Transactions →](https://docs.blockradar.co/en/essentials/signing.md#stellar-soroban-transactions)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.