{"data":[{"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,"status":"active","first_seen":"2026-04-13T19:37:27.707721+00:00","last_seen":"2026-04-13T19:37:27.707732+00:00","tags":["onboarding","friction"]},{"id":"87ba2663-9cab-45c5-9483-a2e5627e6784","title":"Billing misconceptions at onboarding","description":"Multiple entries surface billing confusion that occurs specifically at or near onboarding: the 20 RLUSD setup fee being mistaken for a separate charge, Expert mode being left on by default, the balance floor being mistaken for the agent going offline, and background process cost being unknown. Billing confusion is not random — it clusters at four predictable points: setup cost framing, mode selection, balance floor behavior, and background process cost. Addressing all four in a single 'how billing works' explainer would eliminate the majority of billing-related friction.","pattern_type":"friction","occurrence_count":4,"status":"active","first_seen":"2026-04-13T19:37:27.707737+00:00","last_seen":"2026-04-13T19:37:27.707739+00:00","tags":["billing","friction"]},{"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,"status":"active","first_seen":"2026-04-13T19:37:27.70775+00:00","last_seen":"2026-04-13T19:37:27.707751+00:00","tags":["xrpl","reserve","failure"]},{"id":"a7183f4a-03dd-47b7-b163-7030f4ad1705","title":"Key/seed exposure via unsafe storage or sharing","description":"Multiple incidents involve operators sharing wallet seeds, private keys, or API tokens in plain text through chat, logs, or code snippets. This includes posting seeds in conversation history, storing them in unprotected files, or sending them via unencrypted channels. Once exposed, these credentials are permanently compromised since conversation context can be reviewed by anyone with access. The correct pattern is to store secrets in memory/secrets.md with restricted file permissions, reference them by path only, and never paste them into chat. For significant funds, hardware wallets should be used instead of hot wallets.","pattern_type":"safety","occurrence_count":3,"status":"active","first_seen":"2026-04-13T19:37:27.707754+00:00","last_seen":"2026-04-13T19:37:27.707755+00:00","tags":["security","seeds","safety"]},{"id":"b1a842e9-73e3-4ff0-a5c9-6ab164cb31c4","title":"Agent persistence != process persistence","description":"Agents run in isolated sessions that persist across restarts, but background processes (bash scripts, cron-like loops) do not survive session clears or gateway restarts. Operators frequently assume that starting a background task means it runs forever, leading to silent failures when the session ends. The correct pattern is to use OpenClaw's built-in cron system for recurring tasks, which survives restarts and provides automatic completion wake. Background processes should only be used for work that starts now and completes within the same session.","pattern_type":"friction","occurrence_count":2,"status":"active","first_seen":"2026-04-13T19:37:27.707742+00:00","last_seen":"2026-04-13T19:37:27.707744+00:00","tags":["architecture","friction"]},{"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,"status":"active","first_seen":"2026-04-13T19:37:27.707746+00:00","last_seen":"2026-04-13T19:37:27.707747+00:00","tags":["xrpl","evm","friction"]}],"count":6}