Skip to content

feat(docs): enhance direct minting guides with clarity on recipient addresses and executor requirements #1445

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
fassko wants to merge 2 commits into
base: main
Choose a base branch
from
Open

feat(docs): enhance direct minting guides with clarity on recipient addresses and executor requirements #1445

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
49f28d2
feat(docs): enhance direct minting guides with clarity on recipient a…
fassko Jul 8, 2026
2560c83
fix(docs): improve formatting for clarity in direct minting memo fiel…
fassko Jul 8, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
27 changes: 18 additions & 9 deletions docs/fassets/developer-guides/5-fassets-direct-minting.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,23 +27,28 @@ Compared to the standard [collateral reservation flow](/fassets/developer-guides
- The recipient (and optionally the executor) is encoded in the XRPL memo or destination tag.
- An executor calls [`executeDirectMinting`](/fassets/reference/IAssetManager#executedirectminting) on Flare to finalize and receives a flat fee.

This guide demonstrates the **32-byte memo format**, where the recipient is a Flare address and any executor can finalize.
This guide demonstrates the **32-byte memo format**, where the recipient is any Flare EVM address and any executor can finalize.

Direct minting does not require a [Flare Smart Account](/smart-accounts/overview).
The recipient can be any Flare address — an EOA, a contract, or a Personal Account.
This guide uses a Personal Account linked to the XRPL sender wallet as the example recipient.

## Prerequisites

- [Flare smart account](/smart-accounts/overview) controlled by your XRPL wallet.
- Testnet XRP on the XRP Ledger Testnet usage.
- A Flare EVM recipient address.
This example resolves a [`PersonalAccount`](/smart-accounts/reference/IPersonalAccount) from the XRPL sender wallet; you can substitute any Flare address in the memo.
- Testnet XRP on the XRP Ledger Testnet.
Get testnet XRP from the [XRP Testnet Faucet](https://xrpl.org/resources/dev-tools/xrp-faucets).

## Direct Minting Memo

The memo is a packed 32-byte [`PaymentReference`](/fassets/direct-minting#memo-field):

| Bytes | Value | Meaning |
| :---- | :----------------- | :------------------------------------------------------------ |
| 0-7 | `4642505266410018` | Direct minting prefix. |
| 8-11 | `00000000` | Zero padding to fill the 32-byte memo. |
| 12-31 | 20-byte recipient | EVM address of the Flare smart account receiving FXRP tokens. |
| Bytes | Value | Meaning |
| :---- | :----------------- | :----------------------------------------------- |
| 0-7 | `4642505266410018` | Direct minting prefix. |
| 8-11 | `00000000` | Zero padding to fill the 32-byte memo. |
| 12-31 | 20-byte recipient | Flare EVM address that receives the minted FXRP. |

Because no executor is encoded, anyone can finalize this minting on Flare.
For executor-restricted minting, use the 48-byte memo format described in [Memo Field](/fassets/direct-minting#memo-field).
Expand All @@ -62,7 +67,9 @@ For executor-restricted minting, use the 48-byte memo format described in [Memo
4. Set the net FXRP amount to mint in XRP.
Minting and executor fees are added to the net amount to form the XRPL payment amount.
5. Connect to the XRPL Testnet using `XRPL_TESTNET_RPC_URL` and load the sender wallet from `XRPL_SEED`.
6. Resolve the recipient — the Flare [`PersonalAccount`](/smart-accounts/reference/IPersonalAccount) for the XRPL wallet — via [`getPersonalAccountAddress`](/smart-accounts/reference/IPersonalAccount), and look up `AssetManagerFXRP` through the [Flare Contract Registry](/network/guides/flare-contracts-registry) using [`getContractAddressByName`](/network/guides/flare-contracts-registry).
6. Resolve the example recipient — the Flare [`PersonalAccount`](/smart-accounts/reference/IPersonalAccount) for the XRPL wallet — via [`getPersonalAccountAddress`](/smart-accounts/reference/IPersonalAccount).
Replace this with any Flare recipient address when minting to an EOA or contract.
Look up `AssetManagerFXRP` through the [Flare Contract Registry](/network/guides/flare-contracts-registry) using [`getContractAddressByName`](/network/guides/flare-contracts-registry).
7. Read three values in parallel:
- `getDirectMintingPaymentAddress` — the Core Vault XRPL address that receives the payment.
- `getFxrpBalance` — the recipient's FXRP balance before minting.
Expand Down Expand Up @@ -91,6 +98,8 @@ For executor-restricted minting, use the 48-byte memo format described in [Memo
Your XRP remains at the Core Vault until an executor successfully retries.
Use `waitForDirectMintingOutcome` (see [Delayed minting flow](/fassets/direct-minting#delayed-minting-flow)) rather than waiting only for `DirectMintingExecuted`.
- **For repeat minters**, prefer the destination-tag flow via `IMintingTagManager` — it avoids constructing a memo per payment and lets you set a preferred executor.
- **Smart-account custom instructions are a separate path.** To mint FXRP and dispatch a user operation atomically from an XRPL payment, use the [`0xFE`](/smart-accounts/custom-instruction) or [`0xFF`](/smart-accounts/memo-field-custom-instruction) memo opcodes and finalize with [`executeDirectMintingWithData`](/fassets/reference/IAssetManager#executedirectmintingwithdata).
Plain 32-byte and 48-byte memos mint directly to the encoded address via [`executeDirectMinting`](/fassets/reference/IAssetManager#executedirectminting).

## Common mistakes

Expand Down
13 changes: 11 additions & 2 deletions docs/fassets/developer-guides/6-fassets-direct-minting-tag.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,9 +29,14 @@ Compared to the [memo-based direct minting](/fassets/developer-guides/fassets-di
- **Optional preferred executor**: the tag owner may restrict execution via [`setAllowedExecutor`](/fassets/reference/IMintingTagManager#setallowedexecutor).
After [`othersCanExecuteAfterSeconds`](/fassets/reference/IAssetManager#getdirectmintingotherscanexecuteafterseconds), anyone can finalize.

Direct minting does not require a [Flare Smart Account](/smart-accounts/overview).
The tag's bound recipient can be any Flare EVM address.
This guide uses a Personal Account linked to the XRPL sender wallet as the example recipient.

## Prerequisites

- [Flare smart account](/smart-accounts/overview) controlled by your XRPL wallet.
- A Flare EVM recipient address to bind with [`setMintingRecipient`](/fassets/reference/IMintingTagManager#setmintingrecipient).
This example resolves a [`PersonalAccount`](/smart-accounts/reference/IPersonalAccount) from the XRPL sender wallet; you can bind any Flare address instead.
- Native FLR (or C2FLR on Coston2) on the Flare wallet to cover the tag reservation fee.
- Testnet XRP on the XRP Ledger Testnet — get it from the [XRP Testnet Faucet](https://xrpl.org/resources/dev-tools/xrp-faucets).
- Environment variables:
Expand All @@ -57,7 +62,9 @@ Compared to the [memo-based direct minting](/fassets/developer-guides/fassets-di
5. Set the net FXRP amount to mint in XRP.
Minting and executor fees are added to the XRPL payment amount.
6. Connect to the XRPL Testnet using `XRPL_TESTNET_RPC_URL` and load the sender wallet from `XRPL_SEED`.
7. Resolve the recipient — the Flare [`PersonalAccount`](/smart-accounts/reference/IPersonalAccount) for the XRPL wallet — via [`getPersonalAccountAddress`](/smart-accounts/reference/IPersonalAccount), and look up `AssetManagerFXRP` through the [Flare Contract Registry](/network/guides/flare-contracts-registry) using [`getContractAddressByName`](/network/guides/flare-contracts-registry).
7. Resolve the example recipient — the Flare [`PersonalAccount`](/smart-accounts/reference/IPersonalAccount) for the XRPL wallet — via [`getPersonalAccountAddress`](/smart-accounts/reference/IPersonalAccount).
Replace this with any Flare recipient address when binding an EOA or contract.
Look up `AssetManagerFXRP` through the [Flare Contract Registry](/network/guides/flare-contracts-registry) using [`getContractAddressByName`](/network/guides/flare-contracts-registry).
8. Resolve the [`MintingTagManager`](/fassets/reference/IMintingTagManager) contract address from the `AssetManager` using [`getMintingTagManager`](/fassets/reference/IAssetManager#getmintingtagmanager).
9. Reserve a new tag (or reuse one from `MINTING_TAG`) and confirm the configured recipient.
10. Read three values in parallel:
Expand Down Expand Up @@ -93,6 +100,8 @@ Compared to the [memo-based direct minting](/fassets/developer-guides/fassets-di
If the amount is strictly above the [large-mint](/fassets/direct-minting#large-minting-delay) threshold, it emits [`LargeDirectMintingDelayed`](/fassets/reference/IAssetManagerEvents#largedirectmintingdelayed) instead.
Your XRP remains at the Core Vault until an executor retries.
Use `waitForDirectMintingOutcome` (see [Delayed minting flow](/fassets/direct-minting#delayed-minting-flow)) rather than waiting only for `DirectMintingExecuted`.
- **Smart-account custom instructions are a separate path.** To mint FXRP and dispatch a user operation atomically from an XRPL payment, use the [`0xFE`](/smart-accounts/custom-instruction) or [`0xFF`](/smart-accounts/memo-field-custom-instruction) memo opcodes and finalize with [`executeDirectMintingWithData`](/fassets/reference/IAssetManager#executedirectmintingwithdata).
Tag-based and plain memo mints credit FXRP directly to the bound or encoded recipient via [`executeDirectMinting`](/fassets/reference/IAssetManager#executedirectminting).

## Common Pitfalls

Expand Down
Loading