Idle XRP isn’t a strategy; keeping custody on XRPL while letting automation hunt yield on Flare is. That’s the whole point of @moremarketsxyz FXRP flow custody stays native, strategies rotate under the hood, and payouts settle back in XRP without you playing bridge roulette. Flare’s own update confirms the XRP Earn Account design and why XRPFi works here, not as a marketing slogan but as infra built for on-chain yield. NEAR’s write-up on Chain Signatures adds the missing piece: MPC-driven control that lets execution hop chains while assets remain where you parked them. ❯ Control first: self-custody on XRPL; automated deployment inside Flare’s markets (FXRP), then convert yield back to native XRP. ❯ Less chasing, more outcomes: strategy rotation (lending/liquid staking/DEX fees) without juggling wallets or routes. ❯ Proof of traction matters: Flare’s XRPFi posts and partner comms have been consistent since Q3’25 this isn’t a “new button,” it’s shipped infra. I pulled the Flare announcement + NEAR chainsig post and mapped them against the live XRPFi model; the separation of custody (XRPL) and execution (Flare) is what reduces user friction without introducing another wrapped-custody risk. Versus CEX earn, you keep keys; versus classic bridges, you avoid permanent wrap risk. Dev note: expose a public “policy view” (venues + limits) so power users can audit routes. User step: test a small FXRP deposit, let it run a week, then withdraw to confirm timing and fees in practice. Net/net: this is how you make XRP work without babysitting it. Tagging STBL here since they’ve been vocal on infra quality and self-custody standards