skills.rest
Zireaelst
ZireaelstCOMMUNITY
Explore all skills by this author →
GitHub

flare-smart-accounts

Encodes XRPL payment instructions that trigger smart account actions on Flare.

Updated Aug 3, 2026
Search Tags:#cross-chain#account abstraction#smart accounts#xrpl#flare#fxrp#eip-4337
One-click install
npx skills add https://github.com/Zireaelst/Flare-Hackaton --skill flare-smart-accounts-zireaelst
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: flare-smart-accounts
Source: https://github.com/Zireaelst/Flare-Hackaton/tree/main/.agents/skills/flare-smart-accounts
Command: npx skills add https://github.com/Zireaelst/Flare-Hackaton --skill flare-smart-accounts-zireaelst

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires viem, xrpl, and includes references (resource) components.

What problem does it solve? XRPL users cannot natively execute logic on the Flare chain without holding FLR or managing an EVM wallet. This Skill provides the domain knowledge to construct XRPL Payment instructions—payment references, memo opcodes, and EIP-4337 PackedUserOperations—that let an XRPL address control a smart account on Flare through a single payment. ## Core Features & Use Cases - Instruction Encoding: Byte-level formats for FXRP transfer/redeem, Firelight and Upshift vault deposits and withdrawals, plus legacy collateral-reservation instructions. - Custom Instructions: Build 0xFE (hash-committed) or 0xFF (inline memo) custom instructions that execute arbitrary contract calls via executeUserOp on the personal account. - Failure Recovery: Guidance for the 0xE0 skip-memo, 0xE1 fast-forward nonce, and 0xE2 replace-fee opcodes to recover FXRP from stuck or reverted direct mints. - Use Case: A developer building a DCA or take-profit product can use this Skill to encode a 42-byte XRPL memo committing a PackedUserOperation, so one XRPL payment mints FXRP and dispatches a batch of contract calls atomically. ## Quick Start Ask the assistant to encode a custom instruction that mints FXRP and deposits it into a Firelight vault using a single XRPL payment with a 0xFE memo.

Frequently Asked Questions about flare-smart-accounts

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

FAQPage Schema
How do I execute a Flare contract call from an XRPL payment?▼

Build an EIP-4337 PackedUserOperation whose sender is your personal account and nonce matches getNonce, then send an XRPL Payment to the FAssets Core Vault with a 42-byte 0xFE memo committing keccak256 of the operation. An executor delivers the operation bytes and calls executeDirectMintingWithData, which mints FXRP and runs your calls atomically.

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

Opcode 0xFE keeps the XRPL memo at a constant 42 bytes by committing only the keccak256 hash of the PackedUserOperation, with the full payload delivered off-chain by an executor. Opcode 0xFF embeds the entire abi-encoded operation inline in the memo, which is simpler for single actors but capped by the XRPL 1024-byte memo limit.

Can XRPL users interact with Flare without holding FLR?▼

Yes. Flare Smart Accounts give each XRPL address a deterministic personal account on Flare controlled only through XRPL payments. A relayer or executor service submits the Flare-side transactions and pays gas, so the user never needs FLR or an EVM wallet.

How do I recover FXRP from a stuck or reverted direct mint?▼

Send an XRPL Payment with memo opcode 0xE0 referencing the stuck transaction ID, which sets a skip flag via the IgnoreMemoSet event. The executor then re-submits the original payment's proof, minting the FXRP to your personal account without dispatching the failed user operation. Use 0xE1 afterward to fast-forward the nonce if needed.

Why does my smart account transaction fail with InvalidNonce?▼

InvalidNonce occurs when the PackedUserOperation nonce does not match the current getNonce value of the personal account, commonly from submitting two XRPL payments built with the same nonce. Read getNonce once per payment and wait for the first mint to finalize before building another operation.

Should I use collateral reservation instructions to mint FXRP?▼

No. The collateral-reservation instructions (0x00, 0x10, 0x20) are legacy and retained only for older tooling. The current mint path is an XRPL Payment to the FAssets Core Vault per the FAssets minting documentation, optionally carrying a memo-field custom instruction for mint-and-action in one payment.

Related Skills

Explore More Software Engineering Skills→
Current-cmdCurrent-cmd

quicknode

Configure QuickNode RPC endpoints, Streams, and XRPL methods for blockchain development.

Community
Intermediate
alsk1992alsk1992
650

ai-strategy

Automates creation and execution of Solana blockchain trading strategies via natural language.

Community
Advanced
Ayoub-ouederniAyoub-ouederni

flare-smart-accounts

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

Community
Intermediate
PotLockPotLock

openai-whisper

Transcribe local audio files into text using OpenAI Whisper CLI.

Official
Basic