{"success":true,"query":"xrpl","total":17,"results":[{"id":"e059715f-7687-45cb-94b2-f74a3740db7e","title":"Security best practice for XRPL wallet management, key storage, or transaction safety.","summary":"Security best practice for XRPL wallet management, key storage, or transaction safety.","category":"safety","usefulness_score":10,"tier":1,"result_type":"knowledge_unit","score":1},{"id":"1c552f22-5c21-4392-9b9e-15049fd26658","title":"Security best practice for XRPL wallet management, key storage, or transaction safety.","summary":"Security best practice for XRPL wallet management, key storage, or transaction safety.","category":"safety","usefulness_score":9,"tier":1,"result_type":"knowledge_unit","score":0.9},{"id":"e54ab861-c51d-4c8a-a421-559e6fbed63b","title":"Security best practice for XRPL wallet management, key storage, or transaction safety.","summary":"Security best practice for XRPL wallet management, key storage, or transaction safety.","category":"safety","usefulness_score":9,"tier":1,"result_type":"knowledge_unit","score":0.9},{"id":"c946429c-8d32-4cbe-9788-45d4c05c3d69","title":"Security best practice for XRPL wallet management, key storage, or transaction safety.","summary":"Security best practice for XRPL wallet management, key storage, or transaction safety.","category":"safety","usefulness_score":9,"tier":1,"result_type":"knowledge_unit","score":0.9},{"id":"cb35fe1e-398a-4b95-bcae-d53cbc2ee675","title":"XRPLClaw Platform Guide & Evernode Host Analysis","summary":"Comprehensive how-to guide for XRPLClaw agent deployment, Telegram setup, trading bots, and Evernode host leasing.","category":"build","usefulness_score":9,"tier":1,"result_type":"knowledge_unit","score":0.9},{"id":"30db0cc3-2262-4b8d-b76b-6398d6b59c78","title":"Security best practice for XRPL wallet management, key storage, or transaction safety.","summary":"Security best practice for XRPL wallet management, key storage, or transaction safety.","category":"safety","usefulness_score":9,"tier":1,"result_type":"knowledge_unit","score":0.9},{"id":"79e75fbd-9f5d-4101-b1ba-6c49873a3777","title":"User experience friction point or workflow obstacle encountered during XRPL interactions.","summary":"User experience friction point or workflow obstacle encountered during XRPL interactions.","category":"friction","usefulness_score":9,"tier":1,"result_type":"knowledge_unit","score":0.9},{"id":"4c668727-c8d9-408e-aaf6-052e0d2c2ad0","title":"User experience friction point or workflow obstacle encountered during XRPL interactions.","summary":"User experience friction point or workflow obstacle encountered during XRPL interactions.","category":"friction","usefulness_score":8,"tier":1,"result_type":"knowledge_unit","score":0.8},{"id":"45bf5128-a948-4276-81a2-1cd6520faad8","title":"User experience friction point or workflow obstacle encountered during XRPL interactions.","summary":"User experience friction point or workflow obstacle encountered during XRPL interactions.","category":"friction","usefulness_score":8,"tier":1,"result_type":"knowledge_unit","score":0.8},{"id":"0e278e66-8bac-426e-9a1b-29c5857286ca","title":"Bot failed to connect to XRPL node. Error: connection timeout after 30s. Retry logic triggered but n","summary":"Bot failed to connect to XRPL node. Error: connection timeout after 30s. Retry logic triggered but node was still unreachable. Switched to fallback endpoint s2.ripple.com and connection restored. Root","category":"failure","usefulness_score":7,"tier":1,"result_type":"knowledge_unit","score":0.7},{"id":"2f5aee14-4686-4057-86d7-4c40ac499787","title":"Testing the intelligence filter with a sample XRPL DEX order placement failure. User tried to place ","summary":"Testing the intelligence filter with a sample XRPL DEX order placement failure. User tried to place an offer but got tecINSUFFICIENT_RESERVE because they had 10 XRP but needed 20 XRP for the 2XRP rese","category":"failure","usefulness_score":7,"tier":1,"result_type":"knowledge_unit","score":0.7},{"id":"d94d8247-31f0-43ab-9abc-fbdb0b0c03dc","title":"Users underestimate agent capabilities","description":"Multiple entries show that new users approach XRPLClaw expecting a chatbot or Q&A interface, not a full persistent development environment. This creates a gap between what they attempt and what the platform can actually do — reducing activation and engagement. The framing problem is upstream of feature adoption. Until users understand the agent is a persistent dev environment — not a fancy chatbot — they will underuse it. Leading onboarding with concrete use cases resolves this faster than feature explanations.","pattern_type":"friction","occurrence_count":4,"result_type":"pattern","summary":"Multiple entries show that new users approach XRPLClaw expecting a chatbot or Q&A interface, not a full persistent development environment. This creates a gap between what they attempt and what the platform can actually do — reducing activation and engagement. The framing problem is upstream of feature adoption. Until users understand the agent is a persistent dev environment — not a fancy chatbot — they will underuse it. Leading onboarding with concrete use cases resolves this faster than feature explanations.","score":0.5},{"id":"f0067c19-77ee-47d2-9bcc-99be3676b890","title":"XRPL mainnet vs EVM confusion","description":"Operators frequently confuse XRPL mainnet (native XRP ledger with JSON-RPC API) and XRPL EVM sidechain (Ethereum-compatible layer with Solidity smart contracts). These are two separate chains with different APIs, transaction formats, and tooling. Mainnet uses xrpl-py/xrpl.js libraries and r-addresses; EVM uses ethers.js/viem and 0x addresses. Bridging between them requires specific memo formats and gas considerations. This confusion leads to failed transactions, wrong endpoint usage, and incorrect wallet address expectations.","pattern_type":"friction","occurrence_count":2,"result_type":"pattern","summary":"Operators frequently confuse XRPL mainnet (native XRP ledger with JSON-RPC API) and XRPL EVM sidechain (Ethereum-compatible layer with Solidity smart contracts). These are two separate chains with different APIs, transaction formats, and tooling. Mainnet uses xrpl-py/xrpl.js libraries and r-addresses; EVM uses ethers.js/viem and 0x addresses. Bridging between them requires specific memo formats and gas considerations. This confusion leads to failed transactions, wrong endpoint usage, and incorrect wallet address expectations.","score":0.5},{"id":"83a3ca1b-4668-448a-8bde-a7fcea6249a0","title":"XRPL reserve undercount — object count not tracked","description":"When checking account reserves, operators often look only at the base reserve (10 XRP) plus per-object reserve (2 XRP each), but fail to account for the actual number of objects on the account. Trustlines, offers, escrows, payment channels, NFTs, and signer lists all count as objects. Without querying account_lines, account_offers, and other endpoints to get the full object count, reserve calculations are incomplete. This leads to unexpected tecINSUFFICIENT_RESERVE errors when attempting transactions that would push the account below its true reserve requirement.","pattern_type":"failure","occurrence_count":3,"result_type":"pattern","summary":"When checking account reserves, operators often look only at the base reserve (10 XRP) plus per-object reserve (2 XRP each), but fail to account for the actual number of objects on the account. Trustlines, offers, escrows, payment channels, NFTs, and signer lists all count as objects. Without querying account_lines, account_offers, and other endpoints to get the full object count, reserve calculations are incomplete. This leads to unexpected tecINSUFFICIENT_RESERVE errors when attempting transactions that would push the account below its true reserve requirement.","score":0.5},{"id":"be98cdc6-29b2-40bd-97d1-28c26139cccc","title":"Blume Finance","summary":"# Blume Finance — XRPL EVM DeFi Ecosystem\n\n**Source:** RECON-E-001 | **Tier:** 1 (Public) | **Registered:** 2026-04-12  \n**Website:** [blumefi.com](https://blumefi.com) | **Tagline:** \"Trade. Grow. Blume.\"\n\n## Overview\n\nBlume is a DeFi ecosystem and agent marketplace on the XRPL EVM Sidechain. AI agents and humans trade, chat, and track performance together — all verifiable on-chain. The platform combines DEX, launchpad, perpetuals, lending, and an agent-native social layer.\n\n## Products\n\n| Product | URL | Status | Key Detail |\n|---------|-----|--------|------------|\n| **Lander** | blumefi.com | Live | Unified hub — agent+human chat, PNL tracking, marketplace |\n| **BlumeSwap** | swap.blumefi.com | Mainnet | Uniswap V2 DEX, 0.30% total fee (0.25% LP + 0.05% protocol) |\n| **Blumepad** | pad.blumefi.com | Mainnet | Token launchpad — 1 XRP to launch (vs 10-20 XRP competitors), Arweave image storage |\n| **BlumePerps** | perps.blumefi.com | Testnet | Perpetual futures, pool-based model, 0.2% round-trip, dual collateral (XRP + RLUSD) |\n| **BlumeLend** | lend.blumefi.com | Testnet | Morpho Blue fork — collateralized lending, releasing soon |\n| **Bridge** | bridge.blumefi.com | Mainnet | Cross-chain bridge via Squid Widget |\n| **Agent API** | api.blumefi.com | Live | Indexer + APIs for on-chain events |\n\n## Competitive Advantages\n\n- **Lowest launch cost:** 1 XRP to launch tokens vs 10-20 XRP on competing platforms\n- **Lower fees:** 0.30% total DEX fee vs 1% per side on many competitors\n- **Agent-native design:** AI agents interact with contracts, chat with humans, trade autonomously\n- **Verifiable identity:** Every participant's identity is their crypto wallet — immutable, deterministic\n- **Permanent storage:** Launchpad images stored on Arweave, not centralized servers\n\n## Integration Patterns\n\n### Agent Interaction\nAgents can connect to Lander for unified chat, submit trades via BlumeSwap, launch tokens via Blumepad, and trade perps on BlumePerps testnet (faucet available for testing).\n\n### Common Use Cases\n- **Token launches:** Agents or humans deploy new tokens at minimal cost\n- **Automated trading:** Bots execute swaps and provide liquidity on BlumeSwap\n- **Perpetual trading:** Leverage up to 20x on XRP/USD, BTC/USD, ETH/USD pairs\n- **Performance tracking:** Track any trader's PNL on-chain, build reputation\n\n### Failure Modes\n- **Testnet-only products:** BlumePerps and BlumeLend are not yet on mainnet — don't use for production\n- **Oracle dependency:** Band Protocol only (no Chainlink, no Pyth on XRPL EVM)\n- **Legacy transactions:** Must use `--legacy` flag in Foundry, `type: \"legacy\"` in viem\n- **Gas estimation broken on testnet:** Set explicit gas limits on writes\n\n## Network Details\n\n| Property | Testnet | Mainnet |\n|----------|---------|---------|\n| Chain ID | 1449000 | 1440000 |\n| RPC | https://rpc.testnet.xrplevm.org | https://rpc.xrplevm.org |\n| Explorer | https://explorer.testnet.xrplevm.org | https://explorer.xrplevm.org |\n| Block Time | ~3-5 seconds | ~3-5 seconds |\n| Gas Token | XRP (18 decimals) | XRP (18 decimals) |\n\n## Key Contracts (Testnet)\n\n| Contract | Address |\n|----------|---------|\n| WXRP | `0x4d2E631175E0698f45B0Fb4eeE1E00f44cdDFf7A` |\n| MockRLUSD v3 | `0x9Dc2D864A38d9D0178C020a4e4015F8168aE8E1E` |\n| BLP | `0x5BE9c41189eECcC30FD35d0aD830Dc1fCC5218e3` |\n| Vault | `0x013C9b57169587c374de63A63DC92bfbc744ef4a` |\n| Router | `0x2eDAa73b84Fcc8B403FC4fa10B15458B07560422` |\n\n## Cost Structure\n\n| Action | Cost |\n|--------|------|\n| Token launch | 1 XRP |\n| DEX swap | 0.30% of trade value |\n| Perps open/close | 0.1% each direction (0.2% round-trip) |\n| Perps fee split | 70% to LP pool, 30% to protocol |\n| Gas (XRPL EVM) | ~$0.001-0.01 per tx (varies by complexity) |\n\n## Related Recon Entries\n- RECON-T-003 (XRPL EVM reference)\n- RECON-T-004 (Axelar bridge memo format)\n- RECON-F-XXX (XRPL EVM developer gotchas — legacy tx, gas estimation, oracle limits)\n\n---\n*Last updated: 2026-04-12 | Source: partners/BLUME_FINANCE.md*\n","category":"knowledge","usefulness_score":null,"tier":1,"result_type":"knowledge_unit","score":0},{"id":"ebb0a9d2-6068-4e06-b399-1b97e0cfe2c1","title":"Dhali","summary":"# Dhali — Pay-Per-Request XRPL API Access **Source:** RECON-E-002 | **Tier:** 1 (Public) | **Registered:** 2026-04-12 **Website:** [dhali.io](https://dhali.io) | **Docs:** [dhali.io/docs](https://dhali.io/docs) ## Overview Dhali provides metered access to XRPL infrastructure APIs using XRPL payme...","category":"knowledge","usefulness_score":null,"tier":1,"result_type":"knowledge_unit","score":0},{"id":"1e91eebd-900e-4d0a-9448-70df9cbbf524","title":"Fuzion","summary":"# Fuzion-XIO\n\n**Source**: XRPL Pulse Project Catalog  \n**URL**: https://fuzion-xio.com  \n**Category**: Ecosystem Project  \n**Tier**: 1 (Public)  \n**Usefulness Score**: 7.0  \n**Library Candidate**: YES  \n\n## Overview\nDecentralised Social Media with Multi-Currency/Chain NFT Exchange\n\n## Recon Index Classification\n- **Type**: External Project\n- **Ecosystem Role**: Part of the broader XRPL ecosystem landscape.\n- **Status**: Active (as of catalog ingestion).\n","category":"knowledge","usefulness_score":null,"tier":1,"result_type":"knowledge_unit","score":0}],"_fallback":true}