flare-fassets

Documents FAssets minting, redemption, and contract integration patterns for FXRP on Flare.

Updated Aug 3, 2026
One-click install
npx skills add https://github.com/Zireaelst/Flare-Hackaton --skill flare-fassets-zireaelst
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flare-fassets
Source: https://github.com/Zireaelst/Flare-Hackaton/tree/main/.agents/skills/flare-fassets
Command: npx skills add https://github.com/Zireaelst/Flare-Hackaton --skill flare-fassets-zireaelst

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires ethers, xrpl, viem, @flarenetwork/flare-wagmi-periphery-package, @flarenetwork/flare-periphery-contracts, and includes scripts (resource) and references (resource) components.

What problem does it solve? Developers building on Flare need accurate, up-to-date guidance on the FAssets protocol—how to mint FXRP from XRP via the Core Vault, redeem FAssets back to underlying chains, resolve contract addresses at runtime, and handle agents, collateral, and rate limits—without digging through scattered documentation. ## Core Features & Use Cases - Minting and redemption reference: Covers the standard single-XRPL-payment minting flow (destination tag or memo encoding, MintingTagManager, executor rules, rate limits), the archived collateral-reservation flow, and redemption variants including redeemAmount and redeemWithTag for exchange addresses. - Runtime contract resolution: Explains how to resolve AssetManager and FXRP addresses via the FlareContractsRegistry instead of hardcoding per-network addresses. - Ready-to-run scripts: Includes TypeScript scripts for getting 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-triggered DeFi product uses the skill to encode a 32-byte direct-minting memo, send a payment to the Core Vault, and monitor DirectMintingExecuted events on Coston2. ## 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 from XRP on Flare?

Send a single XRPL payment to the Core Vault address obtained from AssetManager.directMintingPaymentAddress(), encoding the recipient via a destination tag or a 32-byte memo with prefix 0x4642505266410018. 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 addresses since they differ per network.

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

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

Can I redeem FXRP to an exchange address that requires an XRP destination tag?

Yes, use redeemWithTag(amountUBA, underlyingAddress, executor, destinationTag) on the AssetManager, which supports arbitrary amounts and XRP destination tags. It is gated by the redeemWithTagSupported flag and confirmed via confirmXRPRedemptionPayment.

Why is my direct mint delayed instead of executing immediately?

Direct minting enforces hourly and daily caps plus a large-mint threshold; exceeding them delays rather than rejects execution. Watch for DirectMintingDelayed or LargeDirectMintingDelayed events and re-execute with the same proof after executionAllowedAt passes.

Does this skill execute blockchain transactions or handle private keys?

No, the skill is documentation and reference only and never signs, broadcasts, or holds keys. Its write scripts are dry-run by default and only submit transactions when DRY_RUN=false is explicitly set in a developer-controlled environment.