skills.rest
Rasslonely
RasslonelyCOMMUNITY
Explore all skills by this author →
GitHub

flare-smart-accounts

Encodes XRPL payment instructions for Flare Smart Accounts and FXRP vault operations.

Updated Jul 31, 2026
Search Tags:#cross-chain#account abstraction#smart accounts#xrpl#flare#fxrp#fassets
One-click install
npx skills add https://github.com/Rasslonely/NexusXRP --skill flare-smart-accounts-rasslonely
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: flare-smart-accounts
Source: https://github.com/Rasslonely/NexusXRP/tree/main/.agents/skills/flare-smart-accounts
Command: npx skills add https://github.com/Rasslonely/NexusXRP --skill flare-smart-accounts-rasslonely

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? XRPL users cannot natively interact with Flare smart contracts without holding FLR for gas or managing EVM wallets. This Skill provides the domain knowledge to construct, encode, and troubleshoot Flare Smart Account instructions so XRPL users can mint FXRP, transfer tokens, and interact with Firelight and Upshift vaults through simple XRPL Payment transactions. ## Core Features & Use Cases - Instruction Encoding Reference: Complete 32-byte payment reference formats for FXRP transfers, redemptions, and Firelight/Upshift vault deposits and withdrawals, plus memo opcodes (0xFE, 0xFF, 0xE0, 0xE1) for direct-minting custom instructions. - Custom Instruction Guidance: Explains how to build EIP-4337 PackedUserOperation payloads for arbitrary contract calls via the MasterAccountController, including nonce management and executor fee handling. - Failure Recovery Procedures: Documents recovery flows for stuck or reverted direct mints using skip-memo (0xE0) and fast-forward nonce (0xE1) opcodes. - Use Case: A developer building a cross-chain vault integration needs to let an XRPL user deposit FXRP into an Upshift vault; the Skill provides the exact byte layout, CLI command (smart-accounts-cli), and TypeScript/viem code to construct the instruction. ## Quick Start Ask the assistant to encode a Flare Smart Accounts instruction, for example to transfer 10 FXRP to a Flare address or deposit FXRP into a Firelight vault, and it will produce the byte format and CLI command.

Frequently Asked Questions about flare-smart-accounts

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

FAQPage Schema
How do I mint FXRP from XRPL to a Flare smart account?▼

Send an XRPL Payment to the FAssets Core Vault address with the instruction encoded in the memo field, following the FAssets minting flow. The legacy collateral-reservation (CRT) instructions like 0x00 are deprecated; direct minting via the Core Vault is the recommended path.

How do I deposit FXRP into a Firelight or Upshift vault from XRPL?▼

Encode a deposit instruction (0x11 for Firelight, 0x21 for Upshift) with the FXRP amount and vault ID in the 32-byte payment reference, then send it as an XRPL Payment memo. The smart-accounts-cli provides encode commands like firelight-deposit and upshift-deposit for this.

What is the difference between memo opcode 0xFE and 0xFF?▼

Opcode 0xFE stores only a 42-byte memo with the keccak256 hash of a PackedUserOperation delivered off-chain by an executor, keeping memos small. Opcode 0xFF embeds the full abi-encoded PackedUserOperation inline in the memo, limited by the XRPL 1024-byte memo cap.

Why did my Flare smart account direct mint transaction revert?▼

Common causes include a sender mismatch, stale nonce not matching getNonce, memo hash mismatch, insufficient executor msg.value, or a pinned executor conflict. The entire transaction rolls back atomically, so no FXRP is minted and the XRP remains at the Core Vault.

How do I recover funds from a stuck smart account mint?▼

Send an XRPL Payment with memo opcode 0xE0 referencing the stuck transaction ID, then have an executor call executeDirectMintingWithData to set the skip flag and re-mint without running the original user operation. Use opcode 0xE1 afterward to fast-forward the nonce if needed.

Can XRPL payments to smart accounts use a destination tag?▼

No. XRPL transactions targeting smart accounts must not include a destination tag, because a tag forces FAssets direct minting to credit the tag holder instead of the user's smart account.

Related Skills

Explore More Software Engineering Skills→
ThanasimosThanasimos
1

flare-smart-accounts

Implement XRPL-to-Flare smart account interactions without FLR ownership.

Community
Intermediate
Ayoub-ouederniAyoub-ouederni

flare-smart-accounts

Encodes XRPL payment instructions for Flare smart account operations and vault interactions.

Community
Intermediate
mashharukimashharuki

flare-fassets

Guide Flare FAssets minting, redemption, and integration for dApp developers.

Community
Advanced
udecodeudecode
16.5k

clawpatch

Automates semantic feature mapping, code review, finding fixes, and revalidation via the Clawpatch CLI.

Official
Advanced