flare-smart-accounts

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

Updated Apr 3, 2026
One-click install
npx skills add https://github.com/Ayoub-ouederni/SENTINEL --skill flare-smart-accounts-ayoub-ouederni
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flare-smart-accounts
Source: https://github.com/Ayoub-ouederni/SENTINEL/tree/main/.claude/skills/flare-smart-accounts-skill
Command: npx skills add https://github.com/Ayoub-ouederni/SENTINEL --skill flare-smart-accounts-ayoub-ouederni

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? XRPL users cannot natively interact with Flare smart contracts without holding FLR tokens, and manually constructing the 32-byte payment references required by Flare Smart Accounts is error-prone. This Skill provides the domain knowledge to encode, decode, and submit these instructions correctly. ## Core Features & Use Cases - Instruction Encoding Reference: Documents the full 32-byte payment reference format for FXRP minting, transfers, redemptions, and Firelight/Upshift vault deposits and withdrawals. - Custom Contract Calls: Explains how to register and execute arbitrary contract calls from XRPL using the MasterAccountController's custom instruction type (0xff) with keccak256 call hashes. - CLI and TypeScript Workflows: Covers the smart-accounts-cli Python tool and Viem-based TypeScript integration for reading smart account state and sending XRPL payments. - Use Case: A developer building a dApp that lets XRPL users mint FXRP and deposit it into a Firelight yield vault can use this Skill to construct the correct encode-and-bridge command pipeline without users ever holding FLR. ## Quick Start Ask the assistant to encode a Firelight deposit instruction for 1 lot with agent vault 1 and vault ID 1 using the smart-accounts CLI.

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 using Flare Smart Accounts?

Send an XRPL Payment to the operator address with a 32-byte payment reference encoding instruction 0x00 (collateral reservation), then send XRP to the agent vault. The smart-accounts-cli supports this via the encode fxrp-cr and bridge mint-tx commands chained in a pipeline.

How do I encode a custom contract call instruction for Flare?

Build a CustomCall array with target contract, value, and calldata, register it via registerCustomInstruction on MasterAccountController, then get the hash with encodeCustomInstruction. The payment reference is 0xff plus wallet ID plus the 30-byte truncated keccak256 hash.

Can XRPL users interact with Flare without holding FLR tokens?

Yes, Flare Smart Accounts provide account abstraction where each XRPL address gets a unique smart account on Flare. An operator service handles gas and execution on Flare after verifying FDC payment attestations, so users only need an XRPL wallet.

What is the difference between Firelight and Upshift vault withdrawals?

Firelight uses a redeem-then-claim flow with instructions 0x12 and 0x13. Upshift uses a time-locked two-phase process: request-redeem (0x22) starts a waiting period, then claim (0x23) completes it using a date in YYYYMMDD format as the value field.

Why does my smart account instruction fail to execute on Flare?

Common causes include malformed 32-byte payment references, incorrect lot values (1 lot equals 10 FXRP), or missing FDC payment attestation. Use the CLI decode command to inspect the encoded instruction and verify byte positions match the documented format.