flare-smart-accounts

Encodes XRPL payment instructions for Flare Smart Accounts account abstraction workflows.

Updated Aug 10, 2026
One-click install
npx skills add https://github.com/isreal916/pistis --skill flare-smart-accounts-isreal916
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flare-smart-accounts
Source: https://github.com/isreal916/pistis/tree/main/.agents/skills/flare-smart-accounts
Command: npx skills add https://github.com/isreal916/pistis --skill flare-smart-accounts-isreal916

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? XRPL users cannot interact with Flare smart contracts without holding FLR tokens or managing a separate Flare wallet. This Skill provides the domain knowledge to build Flare Smart Accounts flows, where XRPL payments with encoded memos trigger on-chain actions like FXRP transfers, vault deposits, and arbitrary contract calls. ## Core Features & Use Cases - Instruction Encoding Reference: Complete byte-level formats for FXRP (0x0_), Firelight (0x1_), and Upshift (0x2_) instructions, plus memo opcodes (0xFE/0xFF) for EIP-4337 custom instructions. - CLI and TypeScript Guidance: Documents the smart-accounts-cli encode/bridge/decode commands and viem-based TypeScript integration for building PackedUserOperation payloads. - Failure Recovery Flows: Explains atomic revert behavior and recovery opcodes (0xE0 skip memo, 0xE1 fast-forward nonce, 0xE2 replace executor fee) for stuck direct-minting transactions. - Use Case: A developer wants to let XRPL users deposit FXRP into a Firelight yield vault. Use this Skill to construct the 32-byte payment reference, send the XRPL Payment, and verify execution via MasterAccountController. ## Quick Start Ask the assistant to encode a Firelight deposit instruction for 10 FXRP into vault 1 and explain how to submit it as an XRPL payment.

Frequently Asked Questions about flare-smart-accounts

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

FAQPage Schema
How do XRPL users interact with Flare without owning FLR?

Flare Smart Accounts give each XRPL address a deterministic personal account on Flare. Users send an XRPL Payment with an encoded instruction in the memo field, and an operator relays it on-chain using an FDC proof, covering gas on Flare.

How do I encode a smart account instruction for an XRPL payment?

Instructions are 32-byte payment references: byte 1 is the instruction ID, byte 2 the wallet ID, bytes 3-12 the value, and remaining bytes parameters. The smart-accounts-cli encode commands (e.g. fxrp-transfer, firelight-deposit) generate these payloads.

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

Opcode 0xFE commits only a keccak256 hash of the PackedUserOperation in a 42-byte memo, with full data delivered off-chain by an executor. Opcode 0xFF embeds the full abi-encoded PackedUserOperation inline in the memo, capped at roughly 1024 bytes.

Why did my smart account direct mint revert?

Common causes include a sender mismatch, stale nonce, memo hash mismatch, insufficient executor msg.value, or a failing inner call. The entire Flare transaction rolls back atomically, so no FXRP is minted, and the XRP stays at the Core Vault until recovered.

How do I recover FXRP from a stuck mint transaction?

Send an XRPL Payment with memo opcode 0xE0 referencing the stuck transaction ID, then have an executor call executeDirectMintingWithData. This mints the FXRP without running the original user operation; use 0xE1 afterward to fast-forward the nonce.

Should I use collateral reservation instructions to mint FXRP?

No. The CRT instructions (0x00, 0x10, 0x20) are legacy. The recommended mint path is FAssets minting: send an XRPL Payment to the Core Vault with a memo or destination tag, optionally carrying a custom instruction.