xrpl

Each rule under rules/ is self-contained: an incorrect example, a correct example, and links to upstream xrpl.js source, xrpl.org docs, and (where available) an XRPL Developer Portal code sample. Use the index below to jump to the rule that fits the task.

This skill is not an API reference. For exhaustive type signatures, see js.xrpl.org. For XLS protocol specs, use the companion xrpl-standards skill — when work touches AMM, MPT, NFToken, Credentials, Batch, etc., load both skills.

Read first: Security

These four rules are non-negotiable. Funds have been lost over every one of them.

• security-partial-payment — always credit delivered_amount, never Amount on incoming payments. Partial-payment inflation is the canonical XRPL exchange exploit.
• security-validate-meta — a preliminary tesSUCCESS does not mean the tx was applied. Only validated-ledger meta is authoritative.
• security-lastledgersequence — never submit without LastLedgerSequence. Without it a transaction can replay weeks later.
• security-validate-destination-tag — honor requireDestTag; a missing tag on a custodial destination loses funds.

What to read when

Map the user's task to the rules to consult before writing code.