flare-fassets

Documents Flare FAssets minting, redemption, and contract integration flows for FXRP developers.

Updated Jul 31, 2026
One-click install
npx skills add https://github.com/Rasslonely/NexusXRP --skill flare-fassets-rasslonely
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flare-fassets
Source: https://github.com/Rasslonely/NexusXRP/tree/main/.agents/skills/flare-fassets
Command: npx skills add https://github.com/Rasslonely/NexusXRP --skill flare-fassets-rasslonely

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires ethers, xrpl, and includes scripts (resource) components.

What problem does it solve? Developers integrating Flare FAssets (FXRP, FBTC) face complex multi-step protocols—Core Vault minting, MintingTagManager destination tags, FDC payment proofs, redemption queues, and rate limits—scattered across official documentation. This Skill consolidates that domain knowledge, contract API references, and runnable TypeScript scripts into one place. ## Core Features & Use Cases - Minting & Redemption Guidance: Explains the standard single-XRPL-payment Core Vault minting flow (memo and destination-tag encoding), the legacy collateral-reservation flow, and redemption variants including redeemAmount and redeemWithTag for exchange addresses. - Contract Integration Reference: Documents IAssetManager and IMintingTagManager APIs, runtime address resolution via FlareContractsRegistry, rate-limit parameters, and gasless EIP-712 FXRP payments. - Runnable Scripts: Provides ethers/xrpl TypeScript scripts for resolving the FXRP address, reading FAssets settings, listing agents, direct minting, and redeeming—write scripts are dry-run by default. - Use Case: A developer building an XRPL-to-Flare vault integration uses the Skill to encode a 32-byte direct-minting memo, pre-flight check hourly/daily minting limits, and implement redeemWithTag for an exchange payout address. ## Quick Start Ask the assistant to explain how to mint FXRP with a single XRPL payment to the Core Vault and show the memo encoding format.

Frequently Asked Questions about flare-fassets

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I mint FXRP on Flare from XRP?

Send a single XRPL payment to the Core Vault address obtained from AssetManager.directMintingPaymentAddress(), encoding the recipient in a 32-byte memo (prefix 0x4642505266410018) or a destination tag via MintingTagManager. An executor then calls executeDirectMinting on Flare to finalize the mint.

How do I get the FXRP token contract address on Flare?

Query the FlareContractsRegistry at 0xaD67FE66660Fb8dFE9d6b1b4240d8650e30F6019 with getContractAddressByName("AssetManagerFXRP"), then call fAsset() on the returned AssetManager. Never hardcode AssetManager or FXRP addresses since they differ per network.

How do I redeem FXRP to an XRP exchange address with a destination tag?

Use redeemWithTag(amountUBA, underlyingAddress, executor, destinationTag) on the AssetManager, which supports arbitrary UBA amounts and XRP destination tags. Validate the amount against minimumRedeemAmountUBA() and confirm payment via confirmXRPRedemptionPayment.

Why is my FXRP direct mint delayed?

Direct minting enforces hourly and daily tumbling-window caps plus a large-mint threshold that delay rather than reject mints, emitting DirectMintingDelayed or LargeDirectMintingDelayed with an executionAllowedAt timestamp. The mint executes via the same finalizing call once that timestamp passes; do not resend the XRPL payment.

Does this skill execute blockchain transactions or handle private keys?

No. The skill is documentation and reference only; it never signs, broadcasts, or initiates transactions and never touches private keys. All write scripts are dry-run by default and only broadcast when DRY_RUN=false is explicitly set in a developer-controlled environment.

What is the difference between direct minting and standard minting for FAssets?

Direct minting is now the standard path: one XRPL payment to the Core Vault with no collateral reservation. The legacy standard minting flow (reserveCollateral, agent payment, FDC proof, executeMinting) is archived and kept only for historical integrations.