# Mint to any Address

> Mint FXRP and transfer it to a Flare address using the Flare Smart Accounts CLI.

> For the complete documentation index, see [llms.txt](/llms.txt). Markdown versions of documentation pages are available by appending `.md` to the page URL.

Source: https://dev.flare.network/smart-accounts/guides/cli/mint-and-transfer

In this guide we will take a look at how we can mint FXRP and transfer it to a Flare address. What this allows us to do is to, effectively, **mint FXRP onto someone else's Flare address**. This guide is aimed primarily at Web3 developers who desire to engage with the FAssets system but want to sidestep holding FLR for gas.

Preferred TypeScript path

For a full programmatic mint (and optional follow-on action), use the [Cross-Chain Mint](/smart-accounts/guides/typescript-viem/cross-chain-mint-ts) guide or the [Mint FXRP](/fassets/developer-guides/fassets-mint) developer guide.

Let us suppose that we want to mint `1` lot of FXRP (10 FXRP), and transfer it to the address `0xf5488132432118596fa13800b68df4c0ff25131d`.

## Step 1: Mint FXRP[​](#step-1-mint-fxrp "Direct link to Step 1: Mint FXRP")

Minting is done via [FAssets minting](/fassets/minting): send an XRPL `Payment` to the Core Vault with a memo (or destination tag) that credits your personal account. The Smart Accounts CLI does **not** encode that payment; follow [Mint FXRP](/fassets/developer-guides/fassets-mint) (or mint-and-action via a [memo-field custom instruction](/smart-accounts/memo-field-custom-instruction)).

Legacy

Do not use `fxrp-cr` + `bridge mint-tx` as the primary mint path. Those encode the deprecated collateral-reservation (CRT) flow and may still exist in `smart_accounts.py`, but they are not the recommended user mint path.

After minting completes, your personal account holds the FXRP.

## Step 2: Transfer FXRP[​](#step-2-transfer-fxrp "Direct link to Step 2: Transfer FXRP")

Next, prepare the transfer instruction. We will send `10` FXRP (which equals `1` lot) to the address `0xf5488132432118596fa13800b68df4c0ff25131d`. The encode CLI command that does this is:

```
./smart_accounts.py encode fxrp-transfer \  --wallet-id 0 \   --value 10 \  --recipient-address "0xf5488132432118596fa13800b68df4c0ff25131d"
```

<details>
<summary>Expected output</summary>

Expected output

```
0x01000000000000000000000af5488132432118596fa13800b68df4c0ff25131d
```

</details>

Lastly, send the instruction as an XRPL Payment transaction to the operator's XRPL address. Pipe the output of the above `encode` command into a `bridge` command.

```
./smart_accounts.py encode fxrp-transfer \  --wallet-id 0 \   --value 10 \  --recipient-address "0xf5488132432118596fa13800b68df4c0ff25131d" \  | ./smart_accounts.py bridge instruction -
```

<details>
<summary>Expected output</summary>

Expected output

```
sent bridge instruction transaction: 9D5420C689DE7E0189BA15C4F874E491E4A08610A792472DF421B501DD5088AD9D5420C689DE7E0189BA15C4F874E491E4A08610A792472DF421B501DD5088AD
```

</details>

With that, we have successfully minted FXRP via FAssets minting and transferred it to the Flare address `0xf5488132432118596fa13800b68df4c0ff25131d`.