remove rbac to enable anonymous mcp connections

Rippled 2.6.2

@theme/plugins/blog-posts.js

@@ -47,6 +47,7 @@ export function blogPosts() {
         actions.createSharedData('blog-posts', { blogPosts: sortedPosts });
         actions.addRouteSharedData('/blog/', 'blog-posts', 'blog-posts');
         actions.addRouteSharedData('/ja/blog/', 'blog-posts', 'blog-posts');
+        actions.addRouteSharedData('/es-es/blog/', 'blog-posts', 'blog-posts');
       } catch (e) {
         console.log(e);
       }

@theme/plugins/code-samples.js

@@ -44,6 +44,7 @@ export function codeSamples() {
         });
         actions.addRouteSharedData('/resources/code-samples/', 'code-samples', 'code-samples');
         actions.addRouteSharedData('/ja/resources/code-samples/', 'code-samples', 'code-samples');
+        actions.addRouteSharedData('/es-es/resources/code-samples/', 'code-samples', 'code-samples');
       } catch (e) {
         console.log(e);
       }

_code-samples/batch/README.md

@@ -1,4 +1,5 @@
 # Batch
 
-Code samples showing how to create and submit a [Batch transaction](../../docs/concepts/transactions/batch-transactions.md).
-Both for simple and multi account batch transactions.
+Code samples showing how to create and submit a [Batch transaction](https://xrpl.org/docs/concepts/transactions/batch-transactions).
+
+Both for single and multi-account batch transactions.

_code-samples/batch/js/README.md

@@ -0,0 +1,301 @@
+# Send a Batch Transaction
+
+Code samples showing how to create and submit a [Batch transaction](https://xrpl.org/docs/concepts/transactions/batch-transactions) with Javascript.
+
+Both for single and multi-account batch transactions.
+
+## Single Account Batch Transaction
+
+Quick setup and usage:
+
+```sh
+npm install xrpl
+node singleAccountBatch.js
+```
+
+The script should output the following:
+
+```sh
+=== Funding new wallets from faucet... ===
+Sender: rP9EsVosrmx2HyrmLgWJpJacX5ZrVVQsim, Balance: 100 XRP
+Wallet1: rGx6SACvYEvX8SRrvTPD91UhBmJ16pxL94, Balance: 100 XRP
+Wallet2: r3qetgSfAtyCpGc4rvKNz4LX3F3urMSJJy, Balance: 100 XRP
+
+=== Creating Batch transaction... ===
+{
+  "TransactionType": "Batch",
+  "Account": "rP9EsVosrmx2HyrmLgWJpJacX5ZrVVQsim",
+  "Flags": 65536,
+  "RawTransactions": [
+    {
+      "RawTransaction": {
+        "TransactionType": "Payment",
+        "Account": "rP9EsVosrmx2HyrmLgWJpJacX5ZrVVQsim",
+        "Destination": "rGx6SACvYEvX8SRrvTPD91UhBmJ16pxL94",
+        "Amount": "2000000",
+        "Flags": 1073741824
+      }
+    },
+    {
+      "RawTransaction": {
+        "TransactionType": "Payment",
+        "Account": "rP9EsVosrmx2HyrmLgWJpJacX5ZrVVQsim",
+        "Destination": "r3qetgSfAtyCpGc4rvKNz4LX3F3urMSJJy",
+        "Amount": "5000000",
+        "Flags": 1073741824
+      }
+    }
+  ]
+}
+
+=== Submitting Batch transaction... ===
+
+Batch transaction submitted successfully!
+Result:
+ {
+  "close_time_iso": "2025-11-17T12:04:50Z",
+  "ctid": "C013313800030002",
+  "hash": "AE118213B0A183528418ABC5F14E3BFD6524020C5DB1C060157A0D3FDE15B900",
+  "ledger_hash": "621183809B68A794371C5EC6522105FF04E502C48EBDC8171B80224991E33394",
+  "ledger_index": 1257784,
+  "meta": {
+    "AffectedNodes": [
+      {
+        "ModifiedNode": {
+          "FinalFields": {
+            "Account": "rP9EsVosrmx2HyrmLgWJpJacX5ZrVVQsim",
+            "Balance": "99999996",
+            "Flags": 0,
+            "OwnerCount": 0,
+            "Sequence": 1257779
+          },
+          "LedgerEntryType": "AccountRoot",
+          "LedgerIndex": "42CC98AF0A28EDDDC7E359B5622CC5748BDE2A93E124AF5C32647ECA8F68D480",
+          "PreviousFields": {
+            "Balance": "100000000",
+            "Sequence": 1257778
+          },
+          "PreviousTxnID": "081C42DAE12001735AC4E9A7F027636DF612DB17B4BFA2333F4DB8EA0C9D1E9F",
+          "PreviousTxnLgrSeq": 1257778
+        }
+      }
+    ],
+    "TransactionIndex": 3,
+    "TransactionResult": "tesSUCCESS"
+  },
+  "tx_json": {
+    "Account": "rP9EsVosrmx2HyrmLgWJpJacX5ZrVVQsim",
+    "Fee": "4",
+    "Flags": 65536,
+    "LastLedgerSequence": 1257802,
+    "RawTransactions": [
+      {
+        "RawTransaction": {
+          "Account": "rP9EsVosrmx2HyrmLgWJpJacX5ZrVVQsim",
+          "Amount": "2000000",
+          "Destination": "rGx6SACvYEvX8SRrvTPD91UhBmJ16pxL94",
+          "Fee": "0",
+          "Flags": 1073741824,
+          "Sequence": 1257779,
+          "SigningPubKey": "",
+          "TransactionType": "Payment"
+        }
+      },
+      {
+        "RawTransaction": {
+          "Account": "rP9EsVosrmx2HyrmLgWJpJacX5ZrVVQsim",
+          "Amount": "5000000",
+          "Destination": "r3qetgSfAtyCpGc4rvKNz4LX3F3urMSJJy",
+          "Fee": "0",
+          "Flags": 1073741824,
+          "Sequence": 1257780,
+          "SigningPubKey": "",
+          "TransactionType": "Payment"
+        }
+      }
+    ],
+    "Sequence": 1257778,
+    "SigningPubKey": "ED7031CA5BA4EC745610AB495F5053F318C119E87567BE485A494773AD8ED4FBCE",
+    "TransactionType": "Batch",
+    "TxnSignature": "0610A277086943BC462C1A5F85BEB667B62B4BDA59525138B6014101C08297897A73D3D2D247CB37A06E1EA36267C53A51C0FDF32F3D8E974029BEDC41105B07",
+    "ctid": "C013313800030002",
+    "date": 816696290,
+    "ledger_index": 1257784
+  },
+  "validated": true
+}
+
+Batch transaction URL:
+https://devnet.xrpl.org/transactions/AE118213B0A183528418ABC5F14E3BFD6524020C5DB1C060157A0D3FDE15B900
+
+=== Verifying inner transactions... ===
+
+Transaction 1 hash: D18EA54D5653BBB5C87F116978822EAB7A26EDFB1D6C41910F36D7484D4890E3
+ - Status: tesSUCCESS (Ledger 1257784)
+ - Transaction URL: https://devnet.xrpl.org/transactions/D18EA54D5653BBB5C87F116978822EAB7A26EDFB1D6C41910F36D7484D4890E3
+
+Transaction 2 hash: 5660DB400F08EE5543C54D4D65824A2142F9D5AC17294A4ABF654260F129B44E
+ - Status: tesSUCCESS (Ledger 1257784)
+ - Transaction URL: https://devnet.xrpl.org/transactions/5660DB400F08EE5543C54D4D65824A2142F9D5AC17294A4ABF654260F129B44E
+
+=== Final balances ===
+Sender: rP9EsVosrmx2HyrmLgWJpJacX5ZrVVQsim, Balance: 92.999996 XRP
+Wallet1: rGx6SACvYEvX8SRrvTPD91UhBmJ16pxL94, Balance: 102 XRP
+Wallet2: r3qetgSfAtyCpGc4rvKNz4LX3F3urMSJJy, Balance: 105 XRP
+```
+
+## Multi-Account Batch Transaction
+
+```sh
+npm install xrpl
+node multiAccountBatch.js
+```
+
+The script should output the following:
+
+```sh
+=== Funding new wallets from faucet... ===
+Alice: rHpve1GL2ZXUs3NB5iU91BrXBSwb5PbBrG, Balance: 100 XRP
+Bob: r3ruQ92bqXwWxcR2w4cC1tW35og9h3UbBq, Balance: 100 XRP
+Charlie: rsi5D9bkczpbGykPxoGNBVVmFFFXGwm3QA, Balance: 100 XRP
+Third-party wallet: rfUpGXTzU3siTr4UovV6Wt86Vw3gQU4ttA, Balance: 100 XRP
+
+=== Creating Batch transaction... ===
+{
+  "TransactionType": "Batch",
+  "Account": "rfUpGXTzU3siTr4UovV6Wt86Vw3gQU4ttA",
+  "Flags": 65536,
+  "RawTransactions": [
+    {
+      "RawTransaction": {
+        "TransactionType": "Payment",
+        "Account": "rsi5D9bkczpbGykPxoGNBVVmFFFXGwm3QA",
+        "Destination": "rHpve1GL2ZXUs3NB5iU91BrXBSwb5PbBrG",
+        "Amount": "50000000",
+        "Flags": 1073741824
+      }
+    },
+    {
+      "RawTransaction": {
+        "TransactionType": "Payment",
+        "Account": "r3ruQ92bqXwWxcR2w4cC1tW35og9h3UbBq",
+        "Destination": "rHpve1GL2ZXUs3NB5iU91BrXBSwb5PbBrG",
+        "Amount": "50000000",
+        "Flags": 1073741824
+      }
+    }
+  ]
+}
+
+=== Submitting Batch transaction... ===
+
+Batch transaction submitted successfully!
+Result:
+ {
+  "close_time_iso": "2025-11-17T12:08:31Z",
+  "ctid": "C013317600000002",
+  "hash": "1299D20C6B489DA5C632AE4DBE49475DBF42D9444C7E9C109CC9B8DD0FD55FEC",
+  "ledger_hash": "E45ECF69057084CD02BA49A17E4D0C9154D33A98BB3C95A11B2EB9BE18F32C9B",
+  "ledger_index": 1257846,
+  "meta": {
+    "AffectedNodes": [
+      {
+        "ModifiedNode": {
+          "FinalFields": {
+            "Account": "rfUpGXTzU3siTr4UovV6Wt86Vw3gQU4ttA",
+            "Balance": "99999994",
+            "Flags": 0,
+            "OwnerCount": 0,
+            "Sequence": 1257845
+          },
+          "LedgerEntryType": "AccountRoot",
+          "LedgerIndex": "2D9E0A02007241C38A8DF679E7E62AA0B273E8B12A5430B7B9D99300424F0E1F",
+          "PreviousFields": {
+            "Balance": "100000000",
+            "Sequence": 1257844
+          },
+          "PreviousTxnID": "3153DE8DE922538A6BE54AA8F783CAD4B848A321AFF028D3E6DD0E80C4B9C237",
+          "PreviousTxnLgrSeq": 1257844
+        }
+      }
+    ],
+    "TransactionIndex": 0,
+    "TransactionResult": "tesSUCCESS"
+  },
+  "tx_json": {
+    "Account": "rfUpGXTzU3siTr4UovV6Wt86Vw3gQU4ttA",
+    "BatchSigners": [
+      {
+        "BatchSigner": {
+          "Account": "rsi5D9bkczpbGykPxoGNBVVmFFFXGwm3QA",
+          "SigningPubKey": "EDEB88C2868BD25BF03DB26050E16579FA6F8F9E3FF3172E0DC3DCBDA5408572EB",
+          "TxnSignature": "9508568084596147CFDCFC18A62DC298A78AD1148BA4B0EB99BEE1CD37E5555FE3930810790D5708F9739B0E3F79772012C154CA33C2280BDD5B72473C17A607"
+        }
+      },
+      {
+        "BatchSigner": {
+          "Account": "r3ruQ92bqXwWxcR2w4cC1tW35og9h3UbBq",
+          "SigningPubKey": "ED82F98DA6A3FC3E88D2EE3A5469D92C7070513BEF4DEE75CAB0BDAA81E8AE378D",
+          "TxnSignature": "A482C8747F79857530474F1677599766C0BE283CB7E2A05AACF76E61BECCA16DCE3802D2D8244FBF4546A1C0E5EB70691255E3EFD2F8AC80B55357BDAB9ACD05"
+        }
+      }
+    ],
+    "Fee": "6",
+    "Flags": 65536,
+    "LastLedgerSequence": 1257864,
+    "RawTransactions": [
+      {
+        "RawTransaction": {
+          "Account": "rsi5D9bkczpbGykPxoGNBVVmFFFXGwm3QA",
+          "Amount": "50000000",
+          "Destination": "rHpve1GL2ZXUs3NB5iU91BrXBSwb5PbBrG",
+          "Fee": "0",
+          "Flags": 1073741824,
+          "Sequence": 1257842,
+          "SigningPubKey": "",
+          "TransactionType": "Payment"
+        }
+      },
+      {
+        "RawTransaction": {
+          "Account": "r3ruQ92bqXwWxcR2w4cC1tW35og9h3UbBq",
+          "Amount": "50000000",
+          "Destination": "rHpve1GL2ZXUs3NB5iU91BrXBSwb5PbBrG",
+          "Fee": "0",
+          "Flags": 1073741824,
+          "Sequence": 1257841,
+          "SigningPubKey": "",
+          "TransactionType": "Payment"
+        }
+      }
+    ],
+    "Sequence": 1257844,
+    "SigningPubKey": "ED22A32B61EDF083315515831723BC18F8311F03886BBA375DFF46335BB7A75F0B",
+    "TransactionType": "Batch",
+    "TxnSignature": "156791D2DBFAEFC9B0AC29F2D8D0CDB25E13F92E70E6D5414FE31BD8573CA23D3F62F8B34FC1F117BD556B25E4F748095A24C4342108AB32F1B2BAFBF1443501",
+    "ctid": "C013317600000002",
+    "date": 816696511,
+    "ledger_index": 1257846
+  },
+  "validated": true
+}
+
+Batch transaction URL:
+https://devnet.xrpl.org/transactions/1299D20C6B489DA5C632AE4DBE49475DBF42D9444C7E9C109CC9B8DD0FD55FEC
+
+=== Verifying inner transactions ===
+
+Transaction 1 hash: 0F71979E3F641C980929F926640DCA886C30236ED0CD7C94B6CB36F0D42948AC
+ - Status: tesSUCCESS (Ledger 1257846)
+ - Transaction URL: https://devnet.xrpl.org/transactions/0F71979E3F641C980929F926640DCA886C30236ED0CD7C94B6CB36F0D42948AC
+
+Transaction 2 hash: BC124CB29334AA1079139A9BE186B69A0AC467797F147754E2406714854D2A50
+ - Status: tesSUCCESS (Ledger 1257846)
+ - Transaction URL: https://devnet.xrpl.org/transactions/BC124CB29334AA1079139A9BE186B69A0AC467797F147754E2406714854D2A50
+
+=== Final balances ===
+Alice: rHpve1GL2ZXUs3NB5iU91BrXBSwb5PbBrG, Balance: 200 XRP
+Bob: r3ruQ92bqXwWxcR2w4cC1tW35og9h3UbBq, Balance: 50 XRP
+Charlie: rsi5D9bkczpbGykPxoGNBVVmFFFXGwm3QA, Balance: 50 XRP
+Third-party wallet: rfUpGXTzU3siTr4UovV6Wt86Vw3gQU4ttA, Balance: 99.999994 XRP
+```

_code-samples/batch/js/multiAccountBatch.js

@@ -0,0 +1,143 @@
+/**
+ * XRP Ledger Batch Transactions Tutorial
+ *
+ * This tutorial demonstrates how to use the Batch transaction feature (XLS-56)
+ * to perform a multi-account batch transaction.
+ * Concept doc: https://xrpl.org/docs/concepts/transactions/batch-transactions
+ * Reference doc: https://xrpl.org/docs/references/protocol/transactions/types/batch
+*/
+
+import xrpl from "xrpl"
+
+const client = new xrpl.Client("wss://s.devnet.rippletest.net:51233/")
+await client.connect()
+
+// Create and fund wallets
+console.log("=== Funding new wallets from faucet... ===");
+const [
+  { wallet: alice },
+  { wallet: bob },
+  { wallet: charlie },
+  { wallet: thirdPartyWallet },
+] = await Promise.all([
+  client.fundWallet(),
+  client.fundWallet(),
+  client.fundWallet(),
+  client.fundWallet(),
+]);
+
+console.log(`Alice: ${alice.address}, Balance: ${await client.getXrpBalance(alice.address)} XRP`)
+console.log(`Bob: ${bob.address}, Balance: ${await client.getXrpBalance(bob.address)} XRP`)
+console.log(`Charlie: ${charlie.address}, Balance: ${await client.getXrpBalance(charlie.address)} XRP`)
+console.log(`Third-party wallet: ${thirdPartyWallet.address}, Balance: ${await client.getXrpBalance(thirdPartyWallet.address)} XRP`)
+
+// Create inner transactions  --------------------------------------------
+// REQUIRED: Inner transactions MUST have the tfInnerBatchTxn flag (0x40000000).
+// This marks them as part of a batch (requires Fee: 0 and empty SigningPubKey).
+
+// Transaction 1: Charlie pays Alice
+const charliePayment = {
+  TransactionType: "Payment",
+  Account: charlie.address,
+  Destination: alice.address,
+  Amount: xrpl.xrpToDrops(50),
+  Flags: xrpl.GlobalFlags.tfInnerBatchTxn // THIS IS REQUIRED
+}
+
+// Transaction 2: Bob pays Alice
+const bobPayment = {
+  TransactionType: "Payment",
+  Account: bob.address,
+  Destination: alice.address,
+  Amount: xrpl.xrpToDrops(50),
+  Flags: xrpl.GlobalFlags.tfInnerBatchTxn // THIS IS REQUIRED
+}
+
+// Send Batch transaction --------------------------------------------
+console.log("\n=== Creating Batch transaction... ===")
+const batchTx = {
+  TransactionType: "Batch",
+  Account: thirdPartyWallet.address,
+  Flags: xrpl.BatchFlags.tfAllOrNothing, // tfAllOrNothing: All inner transactions must succeed
+  // Must include a minimum of 2 transactions and a maximum of 8 transactions.
+  RawTransactions: [
+    { RawTransaction: charliePayment },
+    { RawTransaction: bobPayment },
+  ]
+}
+console.log(JSON.stringify(batchTx, null, 2))
+
+// Validate the transaction structure
+xrpl.validate(batchTx)
+
+// Set the expected number of signers, which is 2 (Bob and Charlie) in this case, for this transaction. 
+// "autofill" will automatically add Fee: "0" and SigningPubKey: "" to inner transactions.
+const autofilledBatchTx = await client.autofill(batchTx, 2)
+
+// Gather batch signatures --------------------------------
+// Each signer needs their own tx copy because signMultiBatch modifies the object.
+// Charlie signs the Batch transaction
+const charlieBatch = { ...autofilledBatchTx }
+xrpl.signMultiBatch(charlie, charlieBatch)
+
+// Bob signs the Batch transaction
+const bobBatch = { ...autofilledBatchTx }
+xrpl.signMultiBatch(bob, bobBatch)
+
+// Combine inner transaction signatures.
+// This returns a signed transaction blob (hex string) ready for submission.
+const combinedSignedTx = xrpl.combineBatchSigners([charlieBatch, bobBatch])
+
+// Submit the signed blob with the third-party's wallet
+console.log("\n=== Submitting Batch transaction... ===")
+const submitResponse = await client.submitAndWait(combinedSignedTx, 
+  { wallet: thirdPartyWallet }
+)
+
+// Check Batch transaction result --------------------------------
+if (submitResponse.result.meta.TransactionResult !== "tesSUCCESS") {
+  const resultCode = submitResponse.result.meta.TransactionResult
+  console.warn(`\nTransaction failed with result code ${resultCode}`)
+  await client.disconnect()
+  process.exit(1)
+}
+
+console.log("\nBatch transaction submitted successfully!")
+console.log("Result:\n", JSON.stringify(submitResponse.result, null, 2))
+// View the transaction on the XRPL Explorer 
+console.log(`\nBatch transaction URL:\nhttps://devnet.xrpl.org/transactions/${submitResponse.result.hash}`)
+
+// Calculate and verify inner transaction hashes --------------------------------------------
+console.log("\n=== Verifying inner transactions ===")
+const rawTransactions = submitResponse.result.tx_json.RawTransactions
+let hasFailure = false
+
+for (let i = 0; i < rawTransactions.length; i++) {
+  const innerTx = rawTransactions[i].RawTransaction
+  const hash = xrpl.hashes.hashSignedTx(innerTx)
+  console.log(`\nTransaction ${i + 1} hash: ${hash}`)
+
+  try {
+    const tx = await client.request({ command: 'tx', transaction: hash })
+    const status = tx.result.meta?.TransactionResult
+    console.log(` - Status: ${status} (Ledger ${tx.result.ledger_index})`)
+    console.log(` - Transaction URL: https://devnet.xrpl.org/transactions/${hash}`)
+  } catch (error) {
+    hasFailure = true
+    console.log(` - Transaction not found: ${error}`)
+  }
+}
+if (hasFailure) {
+  console.error("\n--- Error: One or more inner transactions failed. ---")
+  await client.disconnect()
+  process.exit(1)
+}
+
+// Verify balances after transaction
+console.log("\n=== Final balances ===")
+console.log(`Alice: ${alice.address}, Balance: ${await client.getXrpBalance(alice.address)} XRP`)
+console.log(`Bob: ${bob.address}, Balance: ${await client.getXrpBalance(bob.address)} XRP`)
+console.log(`Charlie: ${charlie.address}, Balance: ${await client.getXrpBalance(charlie.address)} XRP`)
+console.log(`Third-party wallet: ${thirdPartyWallet.address}, Balance: ${await client.getXrpBalance(thirdPartyWallet.address)} XRP`)
+
+await client.disconnect()

_code-samples/batch/js/package.json

@@ -0,0 +1,6 @@
+{
+  "dependencies": {
+    "xrpl": "^4.4.3"
+  },
+  "type": "module"
+}

_code-samples/batch/js/singleAccountBatch.js

@@ -0,0 +1,120 @@
+/**
+ * Single Account Batch Transaction Example
+ *
+ * This example demonstrates how to use the Batch transactions feature (XLS-56)
+ * to create a single-account batch transaction that sends payments
+ * to multiple destinations in one atomic operation.
+ * Concept doc: https://xrpl.org/docs/concepts/transactions/batch-transactions
+ * Reference doc: https://xrpl.org/docs/references/protocol/transactions/types/batch
+*/
+
+import xrpl from "xrpl"
+
+const client = new xrpl.Client("wss://s.devnet.rippletest.net:51233/")
+await client.connect()
+
+// Create and fund wallets
+console.log("=== Funding new wallets from faucet... ===");
+const [{ wallet: sender }, { wallet: wallet1 }, { wallet: wallet2 }] =
+  await Promise.all([
+    client.fundWallet(),
+    client.fundWallet(),
+    client.fundWallet(),
+  ]);
+
+console.log(`Sender: ${sender.address}, Balance: ${await client.getXrpBalance(sender.address)} XRP`)
+console.log(`Wallet1: ${wallet1.address}, Balance: ${await client.getXrpBalance(wallet1.address)} XRP`)
+console.log(`Wallet2: ${wallet2.address}, Balance: ${await client.getXrpBalance(wallet2.address)} XRP`)
+
+// Create inner transactions  --------------------------------------------
+// REQUIRED: Inner transactions MUST have the tfInnerBatchTxn flag (0x40000000).
+// This marks them as part of a batch (requires Fee: 0 and empty SigningPubKey).
+
+// Transaction 1
+const payment1 = {
+  TransactionType: "Payment",
+  Account: sender.address,
+  Destination: wallet1.address,
+  Amount: xrpl.xrpToDrops(2),
+  Flags: xrpl.GlobalFlags.tfInnerBatchTxn // THIS IS REQUIRED
+}
+
+// Transaction 2
+const payment2 = {
+  TransactionType: "Payment",
+  Account: sender.address,
+  Destination: wallet2.address,
+  Amount: xrpl.xrpToDrops(5),
+  Flags: xrpl.GlobalFlags.tfInnerBatchTxn // THIS IS REQUIRED
+}
+
+// Send Batch transaction --------------------------------------------
+console.log("\n=== Creating Batch transaction... ===")
+const batchTx = {
+  TransactionType: "Batch",
+  Account: sender.address,
+  Flags: xrpl.BatchFlags.tfAllOrNothing, // tfAllOrNothing: All inner transactions must succeed
+  // Must include a minimum of 2 transactions and a maximum of 8 transactions.
+  RawTransactions: [
+    { RawTransaction: payment1 }, 
+    { RawTransaction: payment2 }
+  ]
+}
+console.log(JSON.stringify(batchTx, null, 2))
+
+// Validate the transaction structure before submitting
+xrpl.validate(batchTx)
+
+// Submit and wait for validation
+console.log("\n=== Submitting Batch transaction... ===")
+const submitResponse = await client.submitAndWait(batchTx, {
+  wallet: sender,
+  // "autofill" will automatically add Fee: "0" and SigningPubKey: "" to inner transactions.
+  autofill: true
+})
+
+// Check Batch transaction result --------------------------------
+if (submitResponse.result.meta.TransactionResult !== "tesSUCCESS") {
+  const resultCode = submitResponse.result.meta.TransactionResult
+  console.warn(`\nTransaction failed with result code ${resultCode}`)
+  await client.disconnect()
+  process.exit(1)
+}
+console.log("\nBatch transaction submitted successfully!")
+console.log("Result:\n", JSON.stringify(submitResponse.result, null, 2))
+// View the batch transaction on the XRPL Explorer 
+console.log(`\nBatch transaction URL:\nhttps://devnet.xrpl.org/transactions/${submitResponse.result.hash}`)
+
+// Calculate and verify inner transaction hashes --------------------------------------------
+console.log("\n=== Verifying inner transactions... ===")
+const rawTransactions = submitResponse.result.tx_json.RawTransactions
+let hasFailure = false
+
+for (let i = 0; i < rawTransactions.length; i++) {
+  const innerTx = rawTransactions[i].RawTransaction
+  const hash = xrpl.hashes.hashSignedTx(innerTx)
+  console.log(`\nTransaction ${i + 1} hash: ${hash}`)
+
+  try {
+    const tx = await client.request({ command: 'tx', transaction: hash })
+    const status = tx.result.meta?.TransactionResult
+    console.log(` - Status: ${status} (Ledger ${tx.result.ledger_index})`)
+    console.log(` - Transaction URL: https://devnet.xrpl.org/transactions/${hash}`)
+  } catch (error) {
+    hasFailure = true
+    console.log(` - Transaction not found: ${error}`)
+  }
+}
+if (hasFailure) {
+  console.error("\n--- Error: One or more inner transactions failed. ---")
+  await client.disconnect()
+  process.exit(1)
+}
+
+// Verify balances after transaction
+console.log("\n=== Final balances ===")
+console.log(`Sender: ${sender.address}, Balance: ${await client.getXrpBalance(sender.address)} XRP`)
+console.log(`Wallet1: ${wallet1.address}, Balance: ${await client.getXrpBalance(wallet1.address)} XRP`)
+console.log(`Wallet2: ${wallet2.address}, Balance: ${await client.getXrpBalance(wallet2.address)} XRP`)
+
+await client.disconnect()

_code-samples/get-started/py/README.md

@@ -0,0 +1,62 @@
+# Get Started Using Python Library
+
+Connects to the XRP Ledger and gets account information using Python.
+
+To download the source code, see [Get Started Using Python Library](http://xrpl.org/docs/tutorials/python/build-apps/get-started).
+
+## Run the Code
+
+Quick setup and usage:
+
+```sh
+python -m venv .venv
+source .venv/bin/activate
+pip install -r requirements.txt
+python ./get-acct-info.py
+```
+
+You should see output similar to the following:
+
+```sh
+Creating a new wallet and funding it with Testnet XRP...
+Attempting to fund address ravbHNootpSNQkxyEFCWevSkHsFGDHfyop
+Faucet fund successful.
+Wallet: ravbHNootpSNQkxyEFCWevSkHsFGDHfyop
+Account Testnet Explorer URL: 
+ https://testnet.xrpl.org/accounts/ravbHNootpSNQkxyEFCWevSkHsFGDHfyop
+
+Getting account info...
+Response Status:  ResponseStatus.SUCCESS
+{
+    "account_data": {
+        "Account": "ravbHNootpSNQkxyEFCWevSkHsFGDHfyop",
+        "Balance": "100000000",
+        "Flags": 0,
+        "LedgerEntryType": "AccountRoot",
+        "OwnerCount": 0,
+        "PreviousTxnID": "3DACF2438AD39F294C4EFF6132D5D88BCB65D2F2261C7650F40AC1F6A54C83EA",
+        "PreviousTxnLgrSeq": 12039759,
+        "Sequence": 12039759,
+        "index": "148E6F4B8E4C14018D679A2526200C292BDBC5AB77611BC3AE0CB97CD2FB84E5"
+    },
+    "account_flags": {
+        "allowTrustLineClawback": false,
+        "defaultRipple": false,
+        "depositAuth": false,
+        "disableMasterKey": false,
+        "disallowIncomingCheck": false,
+        "disallowIncomingNFTokenOffer": false,
+        "disallowIncomingPayChan": false,
+        "disallowIncomingTrustline": false,
+        "disallowIncomingXRP": false,
+        "globalFreeze": false,
+        "noFreeze": false,
+        "passwordSpent": false,
+        "requireAuthorization": false,
+        "requireDestinationTag": false
+    },
+    "ledger_hash": "CA624D717C4FCDD03BAD8C193F374A77A14F7D2566354A4E9617A8DAD896DE71",
+    "ledger_index": 12039759,
+    "validated": true
+}
+```

_code-samples/get-started/py/get-acct-info.py

@@ -1,34 +1,39 @@
+# @chunk {"steps": ["connect-tag"]}
 # Define the network client
 from xrpl.clients import JsonRpcClient
+from xrpl.wallet import generate_faucet_wallet
+from xrpl.core import addresscodec
+from xrpl.models.requests.account_info import AccountInfo
+import json
+
 JSON_RPC_URL = "https://s.altnet.rippletest.net:51234/"
 client = JsonRpcClient(JSON_RPC_URL)
+# @chunk-end
 
 
-# Create a wallet using the testnet faucet:
+# @chunk {"steps": ["get-account-create-wallet-tag"]}
+# Create a wallet using the Testnet faucet:
 # https://xrpl.org/xrp-testnet-faucet.html
-from xrpl.wallet import generate_faucet_wallet
+print("\nCreating a new wallet and funding it with Testnet XRP...")
 test_wallet = generate_faucet_wallet(client, debug=True)
-
-# Create an account str from the wallet
-test_account = test_wallet.address
-
-# Derive an x-address from the classic address:
-# https://xrpaddress.info/
-from xrpl.core import addresscodec
-test_xaddress = addresscodec.classic_address_to_xaddress(test_account, tag=12345, is_test_network=True)
-print("\nClassic address:\n\n", test_account)
-print("X-address:\n\n", test_xaddress)
+test_account = test_wallet.classic_address
+print(f"Wallet: {test_account}")
+print(f"Account Testnet Explorer URL: ")
+print(f" https://testnet.xrpl.org/accounts/{test_account}")
+# @chunk-end
 
 
+# @chunk {"steps": ["query-xrpl-tag"]}
 # Look up info about your account
-from xrpl.models.requests.account_info import AccountInfo
+print("\nGetting account info...")
 acct_info = AccountInfo(
     account=test_account,
     ledger_index="validated",
     strict=True,
 )
+
 response = client.request(acct_info)
 result = response.result
-print("response.status: ", response.status)
-import json
+print("Response Status: ", response.status)
 print(json.dumps(response.result, indent=4, sort_keys=True))
+# @chunk-end

_code-samples/get-started/py/requirements.txt

@@ -0,0 +1 @@
+xrpl-py==4.3.0

blog/2025/rippled-2.6.2.md

@@ -0,0 +1,70 @@
+---
+category: 2025
+date: "2025-11-19"
+template: '../../@theme/templates/blogpost'
+seo:
+    title: Introducing XRP Ledger version 2.6.2
+    description: rippled version 2.6.2 is now available. This version contains a new amendment and a critical bug fix.
+labels:
+    - rippled Release Notes
+markdown:
+    editPage:
+        hide: true
+---
+# Introducing XRP Ledger version 2.6.2
+
+Version 2.6.2 of `rippled`, the reference server implementation of the XRP Ledger protocol, is now available. This release adds a new `fixDirectoryLimit` amendment and a critical bug fix.
+
+
+## Action Required
+
+If you run an XRP Ledger server, upgrade to version 2.6.2 as soon as possible to ensure service continuity.
+
+
+## Install / Upgrade
+
+On supported platforms, see the [instructions on installing or updating `rippled`](../../docs/infrastructure/installation/index.md).
+
+| Package | SHA-256 |
+|:--------|:--------|
+| [RPM for Red Hat / CentOS (x86-64)](https://repos.ripple.com/repos/rippled-rpm/stable/rippled-2.6.2-1.el9.x86_64.rpm) | `e3b041906a75c3c52cc6423219d7ba9c199a5d736d2e3978a5ce0ac5ef693fdf` |
+| [DEB for Ubuntu / Debian (x86-64)](https://repos.ripple.com/repos/rippled-deb/pool/stable/rippled_2.6.2-1_amd64.deb) | `0887b5a77c43c362ea7680b83df40b955a5748b712924acf2212b2de29e3373b` |
+
+For other platforms, please [build from source](https://github.com/XRPLF/rippled/blob/master/BUILD.md). The most recent commit in the git log should be the change setting the version:
+
+```text
+commit df24ee077438e03673a9c6661c41e8f070b90cd9
+Author: Vladislav Vysokikh <vvysokikh@gmail.com>
+Date:   Tue Nov 18 09:28:59 2025 +0000
+
+    Version 2.6.2
+```
+
+
+## Full Changelog
+
+### Amendments
+
+The following amendment is open for voting with this release:
+
+- **fixDirectoryLimit** - Removes directory page limits. Object reserve requirements provide enough incentive to avoid creating unnecessary objects on the XRP Ledger. ([#5935](https://github.com/XRPLF/rippled/pull/5935))
+
+### Bug Fixes
+
+- Fixed an assertion failure when all the inner transactions of a `Batch` transaction were invalid. ([#5670](https://github.com/XRPLF/rippled/pull/5670))
+
+
+## Credits
+
+The following GitHub users contributed to this release:
+
+- RippleX Engineering
+- RippleX Docs
+- RippleX Product
+
+
+## Bug Bounties and Responsible Disclosures
+
+We welcome reviews of the `rippled` code and urge researchers to responsibly disclose any issues they may find.
+
+To report a bug, please send a detailed report to: <bugs@xrpl.org>

blog/sidebars.yaml

@@ -10,6 +10,7 @@
     - group: '2025'
       expanded: false
       items:
+        - page: 2025/rippled-2.6.2.md
         - page: 2025/rippled-2.6.1.md
         - page: 2025/vulnerabilitydisclosurereport-bug-sep2025.md
         - page: 2025/devnet-reset-oct.md

docs/references/protocol/transactions/transaction-results/tec-codes.md

@@ -27,7 +27,7 @@ A transaction that fails with a `tec` code destroys the XRP paid as a [transacti
 | `tecCANT_ACCEPT_OWN_NFTOKEN_OFFER` | 157 | The transaction tried to accept an offer that was placed by the same account to buy or sell a [non-fungible token](../../../../concepts/tokens/nfts/index.md). {% amendment-disclaimer name="NonFungibleTokensV1_1" /%} |
 | `tecCLAIM`                 | 100   | Unspecified failure, with transaction cost destroyed. |
 | `tecCRYPTOCONDITION_ERROR` | 146   | This [EscrowCreate][] or [EscrowFinish][] transaction contained a malformed or mismatched crypto-condition. |
-| `tecDIR_FULL`              | 121   | The transaction tried to add an object (such as a trust line, Check, Escrow, or Payment Channel) to an account's owner directory, but that account cannot own any more objects in the ledger. |
+| `tecDIR_FULL`              | 121   | The transaction tried to add an object (such as a trust line, Check, Escrow, or Payment Channel) to an account's owner directory, but that account cannot own any more objects in the ledger.<br>This error is effectively impossible to receive if {% amendment-disclaimer name="fixDirectoryLimit" compact=true /%} is enabled. |
 | `tecDUPLICATE`             | 149   | The transaction tried to create an object (such as a [DepositPreauth][] authorization) that already exists. |
 | `tecDST_TAG_NEEDED`        | 143   | The [Payment transaction][] omitted a [destination tag](../../../../concepts/transactions/source-and-destination-tags.md), but the destination account has the `lsfRequireDestTag` flag enabled. |
 | `tecEMPTY_DID`             | 187   | The transaction tried to create a [DID entry][] with no contents. A DID must not be empty. {% amendment-disclaimer name="DID" /%} |

docs/references/protocol/transactions/types/batch.md

@@ -121,12 +121,12 @@ In this example, two users are atomically swapping their tokens: XRP for GKO.
 | Field             | JSON Type | [Internal Type][] | Required? | Description |
 |:------------------|:----------|:------------------|:----------|:------------|
 | `Flags`           | Number    | UInt32            | Yes       | A bit-flag for this transaction. Exactly one must be specified to represent the batch mode of the transaction. See: [Batch Flags](#batch-flags). |
-| `RawTransactions` | Array     | Array             | Yes       | The list of transactions to apply. |
+| `RawTransactions` | Array     | Array             | Yes       | The list of transactions to apply. See [RawTransactions](#rawtransactions). |
 | `BatchSigners`    | Array     | Array             | No        | The signatures authorizing a multi-account `Batch` transaction. |
 
 ### RawTransactions
 
-`RawTransactions` contains the list of inner transactions to be applied. There can be up to 8 transactions included. These transactions can come from one account or multiple accounts.
+`RawTransactions` contains the list of inner transactions to be applied. There must be a minimum of **2** transactions and a maximum of **8** transactions. These transactions can come from one account or multiple accounts.
 
 Each inner transaction:
 
@@ -169,6 +169,7 @@ A transaction is considered successful if it receives a `tesSUCCESS` result.
 
 | Error Code                | Description                                       |
 |:--------------------------|:--------------------------------------------------|
+| `temARRAY_EMPTY`          | The batch transaction contains zero or one inner transaction. You must submit at least two inner transactions. |
 | `temINVALID_INNER_BATCH`  | An inner transaction is malformed.               |
 | `temSEQ_AND_TICKET`       | The transaction contains both a `TicketSequence` field and a non-zero `Sequence` value. A transaction can't include both fields, but must have at least one. |
 

docs/references/protocol/transactions/types/checkcreate.md

@@ -40,14 +40,18 @@ Create an on-ledger [check](../../../../concepts/payment-types/checks.md), which
 
 ## Error Cases
 
-- If the `Destination` account is blocking incoming Checks, the transaction fails with the result code `tecNO_PERMISSION`. {% amendment-disclaimer name="DisallowIncoming" /%}
-- If the `Destination` is the sender of the transaction, the transaction fails with the result code `temREDUNDANT`.
-- If the `Destination` [account](../../../../concepts/accounts/index.md) does not exist in the ledger, the transaction fails with the result code `tecNO_DST`.
-- If the `Destination` account has the `RequireDest` flag enabled but the transaction does not include a `DestinationTag` field, the transaction fails with the result code `tecDST_TAG_NEEDED`.
-- If `SendMax` specifies a token which is [frozen](../../../../concepts/tokens/fungible-tokens/freezes.md), the transaction fails with the result `tecFROZEN`.
-- If the `Expiration` of the transaction is in the past, the transaction fails with the result `tecEXPIRED`.
-- If the sender does not have enough XRP to meet the [owner reserve](../../../../concepts/accounts/reserves.md#owner-reserves) after adding the Check, the transaction fails with the result `tecINSUFFICIENT_RESERVE`.
-- If either the sender or the destination of the Check cannot own more objects in the ledger, the transaction fails with the result `tecDIR_FULL`.
+Besides errors that can occur for all transactions, {% $frontmatter.seo.title %} transactions can result in the following [transaction result codes](../transaction-results/index.md):
+
+| Error Code | Description |
+|:-----------|:------------|
+| `tecNO_PERMISSION` | The `Destination` account is blocking incoming Checks. {% amendment-disclaimer name="DisallowIncoming" /%} |
+| `temREDUNDANT` | The `Destination` is the sender of the transaction. |
+| `tecNO_DST` | The `Destination` [account](../../../../concepts/accounts/index.md) does not exist in the ledger. |
+| `tecDST_TAG_NEEDED` | The `Destination` account has the `RequireDest` flag enabled but the transaction does not include a `DestinationTag` field. |
+| `tecFROZEN` | `SendMax` specifies a token which is [frozen](../../../../concepts/tokens/fungible-tokens/freezes.md). |
+| `tecEXPIRED` | The `Expiration` of the transaction is in the past. |
+| `tecINSUFFICIENT_RESERVE` | The sender does not have enough XRP to meet the [owner reserve](../../../../concepts/accounts/reserves.md#owner-reserves) after adding the Check. |
+| `tecDIR_FULL` | Either the sender or the destination of the Check cannot own more objects in the ledger.<br>This error is effectively impossible to receive if {% amendment-disclaimer name="fixDirectoryLimit" compact=true /%} is enabled. |
 
 ## See Also
 

docs/references/protocol/transactions/types/delegateset.md

@@ -65,7 +65,7 @@ Besides errors that can occur for all transactions, {% $frontmatter.seo.title %}
 
 | Error Code                | Description |
 |:--------------------------|:------------|
-| `tecDIR_FULL`             | The sender owns too many items in the ledger already. |
+| `tecDIR_FULL`             | The sender owns too many items in the ledger already.<br>This error is effectively impossible to receive if {% amendment-disclaimer name="fixDirectoryLimit" compact=true /%} is enabled. |
 | `tecINSUFFICIENT_RESERVE` | The sender does not have enough XRP to meet the [reserve requirement](/docs/concepts/accounts/reserves.md) of creating a new Delegate ledger entry. |
 | `tecNO_PERMISSION`        | At least one permission in the `Permissions` list is not delegatable. See [Permission Values](../../data-types/permission-values.md) for which permissions are not delegatable. |
 | `tecNO_TARGET`            | The account specified in the `Authorize` field does not exist in the ledger. |

docs/references/protocol/transactions/types/mptokenissuancecreate.md

@@ -24,7 +24,6 @@ This example assumes that the issuer of the token is the signer of the transacti
   "AssetScale": 4,
   "TransferFee": 0,
   "MaximumAmount": "50000000",
-  "Flags": 83659,
   "MPTokenMetadata": "7B2274223A225442494C4C222C226E223A22542D42696C6C205969656C6420546F6B656E222C2264223A2241207969656C642D62656172696E6720737461626C65636F696E206261636B65642062792073686F72742D7465726D20552E532E205472656173757269657320616E64206D6F6E6579206D61726B657420696E737472756D656E74732E222C2269223A226578616D706C652E6F72672F7462696C6C2D69636F6E2E706E67222C226163223A22727761222C226173223A227472656173757279222C22696E223A224578616D706C65205969656C6420436F2E222C227573223A5B7B2275223A226578616D706C657969656C642E636F2F7462696C6C222C2263223A2277656273697465222C2274223A2250726F647563742050616765227D2C7B2275223A226578616D706C657969656C642E636F2F646F6373222C2263223A22646F6373222C2274223A225969656C6420546F6B656E20446F6373227D5D2C226169223A7B22696E7465726573745F72617465223A22352E303025222C22696E7465726573745F74797065223A227661726961626C65222C227969656C645F736F75726365223A22552E532E2054726561737572792042696C6C73222C226D617475726974795F64617465223A22323034352D30362D3330222C226375736970223A22393132373936525830227D7D",
   "Fee": "12",
   "Flags": 122,

docs/references/protocol/transactions/types/nftokencreateoffer.md

@@ -56,7 +56,7 @@ Besides errors that can occur for all transactions, {% $frontmatter.seo.title %}
 | `temDISABLED`                    | The [NonFungibleTokensV1 amendment][] is not enabled. |
 | `temBAD_AMOUNT`                  | The `Amount` field is not valid. For example, the amount was zero for a buy offer, or the amount is denominated in fungible tokens but the `NFToken` has the [`lsfOnlyXRP` flag](../../data-types/nftoken.md#nftoken-flags) enabled. |
 | `temBAD_EXPIRATION`              | The specified `Expiration` time is invalid (for example, `0`). |
-| `tecDIR_FULL`                    | The sender already owns too many objects in the ledger, or there are already too many offers to buy or sell this token. |
+| `tecDIR_FULL`                    | The sender already owns too many objects in the ledger, or there are already too many offers to buy or sell this token.<br>This error is effectively impossible to receive if {% amendment-disclaimer name="fixDirectoryLimit" compact=true /%} is enabled. |
 | `tecEXPIRED`                     | The specified `Expiration` time has already passed. |
 | `tecFROZEN`                      | The `Amount` is denominated in fungible tokens, but one of the trust lines that would receive tokens from this offer is [frozen](../../../../concepts/tokens/fungible-tokens/freezes.md). This could be the seller's trust line or the `NFToken`'s issuer's trust line (if the `NFToken` has a transfer fee). |
 | `tecINSUFFICIENT_RESERVE`        | The sender does not have enough XRP to meet the [reserve requirement](../../../../concepts/accounts/reserves.md) after placing this offer. |

docs/references/protocol/transactions/types/offercreate.md

@@ -58,7 +58,7 @@ Transactions of the OfferCreate type support additional values in the [`Flags` f
 
 | Error Code               | Description                                       |
 |:-------------------------|:--------------------------------------------------|
-| `tecDIR_FULL`            | The owner owns too many items in the ledger, or the order book contains too many Offers at the same exchange rate already. |
+| `tecDIR_FULL`            | The owner owns too many items in the ledger, or the order book contains too many Offers at the same exchange rate already.<br>This error is effectively impossible to receive if {% amendment-disclaimer name="fixDirectoryLimit" compact=true /%} is enabled. |
 | `tecEXPIRED`             | The transaction specifies an `Expiration` time that has already passed. |
 | `tecFROZEN`              | The transaction involves a token on a [frozen](../../../../concepts/tokens/fungible-tokens/freezes.md) trust line (including local and global freezes). The `TakerPays` (buy amount) token has been deep-frozen by the issuer. |
 | `tecINSUF_RESERVE_OFFER` | The owner does not have enough XRP to meet the reserve requirement of adding a new offer ledger entry, and the transaction did not convert any currency. (If the transaction successfully traded any amount, the transaction succeeds with the result code `tesSUCCESS`, but does not create an offer ledger entry for the remainder.) |

docs/references/protocol/transactions/types/permissioneddomainset.md

@@ -55,7 +55,7 @@ Besides errors that can occur for all transactions, {% $frontmatter.seo.title %}
 
 | Error Code                | Description |
 |:--------------------------|:------------|
-| `tecDIR_FULL`             | The transaction would create a new PermissionedDomain, but the sender's owner directory is full. |
+| `tecDIR_FULL`             | The transaction would create a new PermissionedDomain, but the sender's owner directory is full.<br>This error is effectively impossible to receive if {% amendment-disclaimer name="fixDirectoryLimit" compact=true /%} is enabled. |
 | `tecINSUFFICIENT_RESERVE` | The transaction would create a new PermissionedDomain, but the sender does not have enough XRP to meet the increased owner reserve. |
 | `tecNO_ENTRY`             | The transaction attempted to modify a Domain that does not exist. Check the `DomainID` field of the transaction. |
 | `tecNO_ISSUER`            | At least one of the issuers specified in the `AcceptedCredentials` field is does not exist in the XRP Ledger. Check the `Issuer` field of each member of the array. |

docs/references/protocol/transactions/types/ticketcreate.md

@@ -43,7 +43,7 @@ Besides errors that can occur for all transactions, {% $frontmatter.seo.title %}
 | Error Code                | Description                                      |
 |:--------------------------|:-------------------------------------------------|
 | `temINVALID_COUNT`        | The `TicketCount` field is invalid. It must be an integer from 1 to 250. |
-| `tecDIR_FULL`             | This transaction would cause the account to own more than the limit of 250 Tickets at a time, or more than the maximum number of ledger objects in general. |
+| `tecDIR_FULL`             | This transaction would cause the account to own more than the limit of 250 Tickets at a time, or more than the maximum number of ledger objects in general.<br>The maximum ledger objects error is effectively impossible to receive if {% amendment-disclaimer name="fixDirectoryLimit" compact=true /%} is enabled. |
 | `tecINSUFFICIENT_RESERVE` | The sending account does not have enough XRP to meet the [owner reserve](../../../../concepts/accounts/reserves.md) of all the requested Tickets. |
 
 ## See Also

docs/tutorials/how-tos/use-batch-transactions/index.md

@@ -0,0 +1,14 @@
+---
+seo:
+    description: Batch multiple transactions together and execute them as a single unit.
+metadata:
+  indexPage: true
+labels:
+  - Batch
+  - Transactions
+---
+# Use Batch Transactions
+
+Batch multiple transactions together and execute them as a single unit.
+
+{% child-pages /%}

docs/tutorials/how-tos/use-batch-transactions/send-a-multi-account-batch-transaction.md

@@ -0,0 +1,172 @@
+---
+seo:
+    description: Send a Batch transaction containing transactions from multiple accounts. 
+metadata:
+  indexPage: true
+labels:
+  - Batch
+  - Transactions
+---
+# Send a Multi-Account Batch Transaction
+
+This tutorial shows you how to create a [Batch transaction][] containing transactions from multiple accounts, where each account must sign the `Batch` transaction. Any account, even one not involved in the inner transactions, can submit the batch.
+
+## Goals
+
+By the end of this tutorial, you will be able to:
+
+- Create a `Batch` transaction with multiple inner transactions, signed by multiple accounts, and submitted by a third party account.
+- Configure the `Batch` transaction to ensure atomicity, so that either all inner transactions succeed or they all fail.
+
+## Prerequisites
+
+To complete this tutorial, you should:
+
+- Have a basic understanding of the XRP Ledger.
+- Have an XRP Ledger client library set up in your development environment. This page provides examples for the following:
+  - **JavaScript** with the [xrpl.js library](https://github.com/XRPLF/xrpl.js). See [Get Started Using JavaScript](../../javascript/build-apps/get-started.md) for setup steps.
+
+## Source Code
+
+You can find the complete source code for this tutorial's examples in the [code samples section of this website's repository](https://github.com/XRPLF/xrpl-dev-portal/tree/master/_code-samples/batch/).
+
+## Steps
+
+The example in this tutorial demonstrates a scenario where Bob and Charlie both owe Alice 50 XRP each, and a third-party (such as a payment processor) submits the `Batch` transaction atomically to ensure Alice is paid by both parties.
+
+### 1. Install dependencies
+
+{% tabs %}
+{% tab label="Javascript" %}
+From the code sample folder, use npm to install dependencies:
+
+```bash
+npm install xrpl
+```
+
+{% /tab %}
+{% /tabs %}
+
+### 2. Set up client and accounts
+
+To get started, import the client library and instantiate a client to connect to the XRPL. Then, create the accounts for Alice, Bob, Charlie, and the third-party.
+
+{% tabs %}
+{% tab label="Javascript" %}
+{% code-snippet file="/_code-samples/batch/js/multiAccountBatch.js" language="js" from="import xrpl" before="// Create inner transactions" /%}
+{% /tab %}
+{% /tabs %}
+
+### 3. Prepare inner transactions
+
+Next, prepare the inner transactions that will be included in the batch.
+
+{% tabs %}
+{% tab label="Javascript" %}
+{% code-snippet file="/_code-samples/batch/js/multiAccountBatch.js" language="js" from="// Create inner transactions" to="// Send Batch transaction" /%}
+{% /tab %}
+{% /tabs %}
+
+The first transaction sends a payment of 50 XRP from Charlie to Alice, and the second sends a payment of 50 XRP from Bob to Alice. Both transactions must include the `tfInnerBatchTxn` (0x40000000) flag to indicate that they are inner transactions of a batch.
+
+Inner transactions must have a Fee of **0** and an empty string for the `SigningPubKey`. The outer `Batch` transaction handles the overall fee and signing for all inner transactions.
+
+{% admonition type="info" name="Note" %}
+The `Fee` and `SigningPubKey` fields are omitted as the client library's _autofill_ functionality automatically populates these when submitting the `Batch` transaction.
+
+You typically don't need to set these manually, but if you do, ensure `Fee` is set to 0 and `SigningPubKey` is an empty string.
+{% /admonition %}
+
+### 4. Prepare Batch transaction
+
+Create the `Batch` transaction and provide the inner transactions. The key fields to note are:
+
+| Field            | Value      |
+|:---------------- |:---------- |
+| TransactionType  | The type of transaction, in this case `Batch`.|
+| Account          | The wallet address of the account that is sending the `Batch` transaction. |
+| Flags            | The flags for the `Batch` transaction. For this example the transaction is configured with the `tfAllOrNothing` (0x00010000) flag to ensure that either all inner transactions succeed or they all fail atomically. See [Batch Flags](../../../references/protocol/transactions/types/batch.md#batch-flags) for other options. |
+| RawTransactions  | Contains the list of inner transactions to be applied. Must include a minimum of **2** transactions and a maximum of **8** transactions. These transactions can come from one account or multiple accounts. |
+| BatchSigners     | The list of signatures required for the `Batch` transaction. This is required because there are multiple accounts' transactions included in the batch. |
+
+{% tabs %}
+{% tab label="Javascript" %}
+{% code-snippet file="/_code-samples/batch/js/multiAccountBatch.js" language="js" from="// Send Batch transaction" before="// Gather batch signatures" /%}
+{% /tab %}
+{% /tabs %}
+
+Because we used `autofill`, the client library automatically fills in any missing fields, like `Fee` and `SigningPubKey`. Additionally, we specify the expected number of signers (2 in this case).
+
+### 5. Gather batch signatures
+
+To add the `BatchSigners` field, you need to collect signatures from each account that's sending a transaction within the batch. In this case we need two signatures, one from Charlie and one from Bob. Each sender must sign the `Batch` transaction to authorize their payment.
+
+{% tabs %}
+{% tab label="Javascript" %}
+The **xrpl.js** library provides a helper function, `signMultiBatch()`, to sign the `Batch` transaction for each account.
+
+Then, to combine the signatures into a single signed `Batch` transaction, use the `combineBatchSigners()` utility function.
+{% code-snippet file="/_code-samples/batch/js/multiAccountBatch.js" language="js" from="// Gather batch signatures" to="// Submit" /%}
+{% /tab %}
+{% /tabs %}
+
+### 6. Submit Batch transaction
+
+With all the required signatures gathered, the third-party wallet can now submit the `Batch` transaction.
+
+{% tabs %}
+{% tab label="Javascript" %}
+{% code-snippet file="/_code-samples/batch/js/multiAccountBatch.js" language="js" from="// Submit" before="// Check Batch transaction" /%}
+{% /tab %}
+{% /tabs %}
+
+### 7. Check Batch transaction result
+
+To check the result of the `Batch` transaction submission:
+
+{% tabs %}
+{% tab label="Javascript" %}
+{% code-snippet file="/_code-samples/batch/js/multiAccountBatch.js" language="js" from="// Check Batch transaction" before="// Calculate and verify" /%}
+{% /tab %}
+{% /tabs %}
+
+The code checks for a `tesSUCCESS` result and displays the response details.
+
+{% admonition type="warning" name="Warning" %}
+A `tesSUCCESS` result indicates that the `Batch` transaction was processed successfully, but does not guarantee the inner transactions succeeded. For example, see the [following transaction on the XRPL Explorer](https://devnet.xrpl.org/transactions/20CFCE5CF75E93E6D1E9C1E42F8E8C8C4CB1786A65BE23D2EA77EAAB65A455C5/simple).
+{% /admonition %}
+
+Because the `Batch` transaction is configured with a `tfAllOrNothing` flag, if any inner transaction fails, **all** inner transactions wil fail, and only the `Batch` transaction fee is deducted from the **third-party wallet**.
+
+### 8. Verify inner transactions
+
+Since there is no way to check the status of inner transactions in the `Batch` transaction result, you need to calculate the inner transaction hashes and look them up on the ledger:
+
+{% tabs %}
+{% tab label="Javascript" %}
+{% code-snippet file="/_code-samples/batch/js/multiAccountBatch.js" language="js" from="// Calculate and verify" before="// Verify balances after transaction" /%}
+{% /tab %}
+{% /tabs %}
+
+The code extracts the actual inner transactions from the batch response, calculates the hash of each inner transaction and looks up each transaction on the ledger using its hash.
+
+### 9. Verify balances
+
+You can also verify that the inner transactions executed successfully by checking the account balances to confirm the expected changes.
+
+{% tabs %}
+{% tab label="Javascript" %}
+{% code-snippet file="/_code-samples/batch/js/multiAccountBatch.js" language="js" from="// Verify balances after transaction" /%}
+{% /tab %}
+{% /tabs %}
+
+## See Also
+
+- **Concepts**:
+  - [Batch Transactions](../../../concepts/transactions/batch-transactions.md)
+- **Tutorials**:
+  - [Send a Single Account Batch Transaction](send-a-single-account-batch-transaction.md)
+- **References**:
+  - [Batch Transaction][]
+
+{% raw-partial file="/docs/_snippets/common-links.md" /%}

docs/tutorials/how-tos/use-batch-transactions/send-a-single-account-batch-transaction.md

@@ -0,0 +1,162 @@
+---
+seo:
+    description: Send a Batch transaction from a single account.
+metadata:
+  indexPage: true
+labels:
+  - Batch
+  - Transactions
+---
+# Send a Single Account Batch Transaction
+
+A [Batch transaction][] allows you to group multiple transactions together and execute them as a single atomic operation.
+
+This tutorial shows you how to create a `Batch` transaction where a single account submits multiple transactions that either all succeed together or all fail together.
+
+## Goals
+
+By the end of this tutorial, you will be able to:
+
+- Create a `Batch` transaction with multiple inner transactions, signed and submitted by a single account.
+- Configure the `Batch` transaction to ensure atomicity, so that either all inner transactions succeed or they all fail.
+
+## Prerequisites
+
+To complete this tutorial, you should:
+
+- Have a basic understanding of the XRP Ledger.
+- Have an XRP Ledger client library set up in your development environment. This page provides examples for the following:
+  - **JavaScript** with the [xrpl.js library](https://github.com/XRPLF/xrpl.js). See [Get Started Using JavaScript](../../javascript/build-apps/get-started.md) for setup steps.
+
+## Source Code
+
+You can find the complete source code for this tutorial's examples in the [code samples section of this website's repository](https://github.com/XRPLF/xrpl-dev-portal/tree/master/_code-samples/batch/).
+
+## Steps
+
+The example in this tutorial demonstrates a scenario where an account sends multiple payments that must be processed atomically in one `Batch` transaction.
+
+### 1. Install dependencies
+
+{% tabs %}
+{% tab label="Javascript" %}
+From the code sample folder, use npm to install dependencies:
+
+```bash
+npm install xrpl
+```
+
+{% /tab %}
+{% /tabs %}
+
+### 2. Set up client and accounts
+
+To get started, import the client library and instantiate a client to connect to the XRPL. For this tutorial you need a funded account for the `Batch` transaction **sender**, and two other accounts to **receive** the payments.
+
+{% tabs %}
+{% tab label="Javascript" %}
+{% code-snippet file="/_code-samples/batch/js/singleAccountBatch.js" language="js" from="import xrpl" before="// Create inner transactions" /%}
+{% /tab %}
+{% /tabs %}
+
+### 3. Prepare inner transactions
+
+Next, prepare the inner transactions that will be included in the batch.
+
+{% tabs %}
+{% tab label="Javascript" %}
+{% code-snippet file="/_code-samples/batch/js/singleAccountBatch.js" language="js" from="// Create inner transactions" to="// Send Batch transaction" /%}
+{% /tab %}
+{% /tabs %}
+
+The first transaction sends a payment of 2 XRP from the sender to `wallet1`, and the second transaction sends 5 XRP from the sender to `wallet2`. Both transactions must include the `tfInnerBatchTxn` (0x40000000) flag to indicate that they are inner transactions of a batch.
+
+Inner transactions must have a Fee of **0** and an empty string for the `SigningPubKey`. The outer `Batch` transaction handles the overall fee and signing for all inner transactions.
+
+{% admonition type="info" name="Note" %}
+The `Fee` and `SigningPubKey` fields are omitted as the client library's _autofill_ functionality automatically populates these when submitting the `Batch` transaction.
+
+You typically don't need to set these manually, but if you do, ensure `Fee` is set to 0 and `SigningPubKey` is an empty string.
+{% /admonition %}
+
+### 4. Prepare Batch transaction
+
+Create the `Batch` transaction and provide the inner transactions. The key fields to note are:
+
+| Field            | Value      |
+|:---------------- |:---------- |
+| TransactionType  | The type of transaction, in this case `Batch`.|
+| Account          | The wallet address of the account that is sending the `Batch` transaction. |
+| Flags            | The flags for the `Batch` transaction. For this example the transaction is configured with the `tfAllOrNothing` (0x00010000) flag to ensure that either all inner transactions succeed or they all fail atomically. See [Batch Flags](../../../references/protocol/transactions/types/batch.md#batch-flags) for other options. |
+| RawTransactions  | Contains the list of inner transactions to be applied. Must include a minimum of **2** transactions and a maximum of **8** transactions. These transactions can come from one account or multiple accounts. |
+
+{% tabs %}
+{% tab label="Javascript" %}
+{% code-snippet file="/_code-samples/batch/js/singleAccountBatch.js" language="js" from="// Send Batch transaction" before="// Submit" /%}
+{% /tab %}
+{% /tabs %}
+
+### 5. Submit Batch transaction
+
+Now the sender can submit the `Batch` transaction:
+
+{% tabs %}
+{% tab label="Javascript" %}
+{% code-snippet file="/_code-samples/batch/js/singleAccountBatch.js" language="js" from="// Submit" before="// Check Batch transaction" /%}
+{% /tab %}
+{% /tabs %}
+
+Because `autofill` is set to `true`, the client library automatically fills in any missing fields, like the `Fee` and `SigningPubKey`, before submitting the batch.
+
+### 6. Check Batch transaction result
+
+To check the result of the `Batch` transaction submission:
+
+{% tabs %}
+{% tab label="Javascript" %}
+{% code-snippet file="/_code-samples/batch/js/singleAccountBatch.js" language="js" from="// Check Batch transaction" before="// Calculate and verify" /%}
+{% /tab %}
+{% /tabs %}
+
+The code checks for a `tesSUCCESS` result and displays the response details.
+
+{% admonition type="warning" name="Warning" %}
+A `tesSUCCESS` result indicates that the `Batch` transaction was processed successfully, but does not guarantee the inner transactions succeeded.
+
+For example, see the [following transaction on the XRPL Explorer](https://devnet.xrpl.org/transactions/20CFCE5CF75E93E6D1E9C1E42F8E8C8C4CB1786A65BE23D2EA77EAAB65A455C5/simple).
+{% /admonition %}
+
+Because the `Batch` transaction is configured with a `tfAllOrNothing` flag, if any inner transaction fails, **all** inner transactions wil fail, and only the `Batch` transaction fee is deducted from the **third-party wallet**.
+
+### 7. Verify inner transactions
+
+Since there is no way to check the status of inner transactions in the `Batch` transaction result, you need to calculate the inner transaction hashes and look them up on the ledger:
+
+{% tabs %}
+{% tab label="Javascript" %}
+{% code-snippet file="/_code-samples/batch/js/singleAccountBatch.js" language="js" from="// Calculate and verify" before="// Verify balances after transaction" /%}
+{% /tab %}
+{% /tabs %}
+
+The code extracts the actual inner transactions from the batch response, calculates the hash of each inner transaction and looks up each transaction on the ledger using its hash.
+
+### 8. Verify balances
+
+You can also verify that the inner transactions executed successfully by checking the account balances to confirm the expected changes.
+
+{% tabs %}
+{% tab label="Javascript" %}
+{% code-snippet file="/_code-samples/batch/js/singleAccountBatch.js" language="js" from="// Verify balances after transaction" /%}
+{% /tab %}
+{% /tabs %}
+
+## See Also
+
+- **Concepts**:
+  - [Batch Transactions](../../../concepts/transactions/batch-transactions.md)
+- **Tutorials**:
+  - [Send a Multi-Account Batch Transaction](send-a-multi-account-batch-transaction.md)
+- **References**:
+  - [Batch Transaction][]
+
+{% raw-partial file="/docs/_snippets/common-links.md" /%}

docs/tutorials/python/build-apps/get-started.md

@@ -1,63 +1,97 @@
 ---
 seo:
     description: Build a Python app that interacts with the XRP Ledger.
+top_nav_name: Python
+top_nav_grouping: Get Started
 labels:
   - Development
 ---
+
+{% code-walkthrough
+  filesets=[
+    { 
+      "files": ["/_code-samples/get-started/py/get-acct-info.py"],
+      "downloadAssociatedFiles": ["/_code-samples/get-started/py/requirements.txt","/_code-samples/get-started/py/get-acct-info.py", "/_code-samples/get-started/py/README.md"]
+    }
+  ]
+%}
+
 # Get Started Using Python Library
 
-This tutorial walks you through the basics of building an XRP Ledger-connected application using [`xrpl-py`](https://github.com/XRPLF/xrpl-py), a pure [Python](https://www.python.org) library built to interact with the XRP Ledger using native Python models and methods.
+This tutorial walks you through the basics of building an XRP Ledger-connected application using the [`xrpl-py`](https://github.com/XRPLF/xrpl-py) client library, a pure [Python](https://www.python.org) library built to interact with the XRP Ledger using native Python models and methods.
 
 This tutorial is intended for beginners and should take no longer than 30 minutes to complete.
 
-## Learning Goals
+## Goals
 
 In this tutorial, you'll learn:
 
-* The basic building blocks of XRP Ledger-based applications.
-* How to connect to the XRP Ledger using `xrpl-py`.
-* How to get an account on the [Testnet](/resources/dev-tools/xrp-faucets) using `xrpl-py`.
-* How to use the `xrpl-py` library to look up information about an account on the XRP Ledger.
-* How to put these steps together to create a Python app.
+- The basic building blocks of XRP Ledger-based applications.
+- How to connect to the XRP Ledger using `xrpl-py`.
+- How to get an account on the [Testnet](/resources/dev-tools/xrp-faucets) using `xrpl-py`.
+- How to use the `xrpl-py` library to look up information about an account on the XRP Ledger.
+- How to put these steps together to create a Python app.
 
-## Requirements
+## Prerequisites
 
-The `xrpl-py` library supports [Python 3.7](https://www.python.org/downloads/) and later.
+To complete this tutorial, you should meet the following guidelines:
 
+- Have a basic understanding of Python.
+- Have installed [Python 3.7](https://www.python.org/downloads/) or later.
 
-## Installation
+## Source Code
 
-The [`xrpl-py` library](https://github.com/XRPLF/xrpl-py) is available on [PyPI](https://pypi.org/project/xrpl-py/). Install with `pip`: <!-- SPELLING_IGNORE: pypi -->
+Click **Download** on the top right of the code preview panel to download the source code.
 
+## Steps
 
-```py
-pip3 install xrpl-py
+Follow the steps to create a simple application with `xrpl-py`.
+
+{% step id="import-tag" %}
+### 1. Install Dependencies
+
+Start a new project by creating an empty folder, then move into that folder and set up a Python virtual environment with the necessary dependencies:
+
+```sh
+# Create and activate a virtual environment
+python -m venv .venv
+source .venv/bin/activate
+
+# Install the xrpl-py library
+pip install xrpl-py
 ```
 
-## Start Building
+Alternatively, if you're using the downloaded source code, you can install all dependencies from the `requirements.txt` file:
 
-When you're working with the XRP Ledger, there are a few things you'll need to manage, whether you're adding XRP to your [account](../../../concepts/accounts/index.md), integrating with the [decentralized exchange](../../../concepts/tokens/decentralized-exchange/index.md), or [issuing tokens](../../../concepts/tokens/index.md). This tutorial walks you through basic patterns common to getting started with all of these use cases and provides sample code for implementing them.
+```sh
+python -m venv .venv
+source .venv/bin/activate
+pip install -r requirements.txt
+```
+{% /step %}
 
-Here are the basic steps you'll need to cover for almost any XRP Ledger project:
+### 2. Connect to the XRP Ledger
 
-1. [Connect to the XRP Ledger.](#1-connect-to-the-xrp-ledger)
-1. [Get an account.](#2-get-account)
-1. [Query the XRP Ledger.](#3-query-the-xrp-ledger)
+{% step id="connect-tag" %}
+#### Connect to the XRP Ledger Testnet
 
+To make queries and submit transactions, you need to connect to the XRP Ledger. To do this with `xrpl-py`, use the [`xrp.clients` module](https://xrpl-py.readthedocs.io/en/latest/source/xrpl.clients.html).
 
-### 1. Connect to the XRP Ledger
+{% admonition type="info" name="Note" %}
+The standard approach with `xrpl-py` is to use the JSON-RPC client. While a WebSocket client is available, it requires you to use `async`/`await` throughout your code. For most use cases, stick with JSON-RPC to avoid the complexity of asynchronous programming.
+{% /admonition %}
 
-To make queries and submit transactions, you need to connect to the XRP Ledger. To do this with `xrpl-py`, use the [`xrp.clients` module](https://xrpl-py.readthedocs.io/en/latest/source/xrpl.clients.html):
+The sample code shows you how to connect to the Testnet, which is one of the available [parallel networks](../../../concepts/networks-and-servers/parallel-networks.md).
+{% /step %}
 
-{% code-snippet file="/_code-samples/get-started/py/get-acct-info.py" from="# Define the network client" before="# Create a wallet using the testnet faucet:" language="py" /%}
-
-#### Connect to the production XRP Ledger
+{% step id="connect-mainnet-tag"%}
+#### Connect to the XRP Ledger Mainnet
 
 The sample code in the previous section shows you how to connect to the Testnet, which is a [parallel network](../../../concepts/networks-and-servers/parallel-networks.md) for testing where the money has no real value. When you're ready to integrate with the production XRP Ledger, you'll need to connect to the Mainnet. You can do that in two ways:
 
-* By [installing the core server](../../../infrastructure/installation/index.md) (`rippled`) and running a node yourself. The core server connects to the Mainnet by default, but you can [change the configuration to use Testnet or Devnet](../../../infrastructure/configuration/connect-your-rippled-to-the-xrp-test-net.md). [There are good reasons to run your own core server](../../../concepts/networks-and-servers/index.md#reasons-to-run-your-own-server). If you run your own server, you can connect to it like so:
+- By [installing the core server](../../../infrastructure/installation/index.md) (`rippled`) and running a node yourself. The core server connects to the Mainnet by default, but you can [change the configuration to use Testnet or Devnet](../../../infrastructure/configuration/connect-your-rippled-to-the-xrp-test-net.md). [There are good reasons to run your own core server](../../../concepts/networks-and-servers/index.md#reasons-to-run-your-own-server). If you run your own server, you can connect to it like so:
 
-    ```
+    ```python
     from xrpl.clients import JsonRpcClient
     JSON_RPC_URL = "http://localhost:5005/"
     client = JsonRpcClient(JSON_RPC_URL)
@@ -65,146 +99,115 @@ The sample code in the previous section shows you how to connect to the Testnet,
 
     See the example [core server config file](https://github.com/XRPLF/rippled/blob/c0a0b79d2d483b318ce1d82e526bd53df83a4a2c/cfg/rippled-example.cfg#L1562) for more information about default values.
 
-* By using one of the available [public servers][]:
+- By using one of the available [public servers][]:
 
-    ```
+    ```python
     from xrpl.clients import JsonRpcClient
     JSON_RPC_URL = "https://s2.ripple.com:51234/"
     client = JsonRpcClient(JSON_RPC_URL)
     ```
+{% /step %}
 
-
-### 2. Get account
+{% step id="get-account-create-wallet-tag" %}
+### 3. Get account
 
 To store value and execute transactions on the XRP Ledger, you need an account: a [set of keys](../../../concepts/accounts/cryptographic-keys.md#key-components) and an [address](../../../concepts/accounts/addresses.md) that's been [funded with enough XRP](../../../concepts/accounts/index.md#creating-accounts) to meet the [account reserve](../../../concepts/accounts/reserves.md). The address is the identifier of your account and you use the [private key](../../../concepts/accounts/cryptographic-keys.md#private-key) to sign transactions that you submit to the XRP Ledger.
 
+{% admonition type="success" name="Tip" %}
 For testing and development purposes, you can use the [XRP Faucets](/resources/dev-tools/xrp-faucets) to generate keys and fund the account on the Testnet or Devnet. For production purposes, you should take care to store your keys and set up a [secure signing method](../../../concepts/transactions/secure-signing.md). Another difference in production is that XRP has real worth, so you can't get it for free from a faucet.
+{% /admonition %}
 
-To create and fund an account on the Testnet, `xrpl-py` provides the [`generate_faucet_wallet`](https://xrpl-py.readthedocs.io/en/latest/source/xrpl.wallet.html#xrpl.wallet.generate_faucet_wallet) method:
+To create and fund an account on the Testnet, `xrpl-py` provides the [`generate_faucet_wallet`](https://xrpl-py.readthedocs.io/en/latest/source/xrpl.wallet.html#xrpl.wallet.generate_faucet_wallet) method. This method returns a [`Wallet` instance](https://xrpl-py.readthedocs.io/en/latest/source/xrpl.wallet.html#xrpl.wallet.Wallet).
+{% /step %}
 
-{% code-snippet file="/_code-samples/get-started/py/get-acct-info.py" from="# Create a wallet using the testnet faucet:" before="# Create an account str from the wallet" language="py" /%}
-
-
-This method returns a [`Wallet` instance](https://xrpl-py.readthedocs.io/en/latest/source/xrpl.wallet.html#xrpl.wallet.Wallet):
-
-
-```py
-print(test_wallet)
-
-# print output
-
-public_key:: 022FA613294CD13FFEA759D0185007DBE763331910509EF8F1635B4F84FA08AEE3
-private_key:: -HIDDEN-
-classic_address: raaFKKmgf6CRZttTVABeTcsqzRQ51bNR6Q
-```
-
-#### Using the account
-
-In this tutorial we only query details about the generated account from the XRP Ledger, but you can use the values in the `Wallet` instance to prepare, sign, and submit transactions with `xrpl-py`.
-
-##### Prepare
-
-To prepare the transaction:
-
-{% code-snippet file="/_code-samples/get-started/py/prepare-payment.py" from="# Prepare payment" before="# print prepared payment" language="py" /%}
-
-
-
-##### Sign and submit
-
-To sign and submit the transaction:
-
-{% code-snippet file="/_code-samples/get-started/py/prepare-payment.py" from="# Sign and submit the transaction" before="# Print tx response" language="py" /%}
-
-
-##### Derive an X-address
-
-You can use `xrpl-py`'s [`xrpl.core.addresscodec`](https://xrpl-py.readthedocs.io/en/latest/source/xrpl.core.addresscodec.html) module to derive an [X-address](https://xrpaddress.info/) from the `Wallet.address` field:
-
-{% code-snippet file="/_code-samples/get-started/py/get-acct-info.py" from="# Derive an x-address from the classic address:" before="# Look up info about your account" language="py" /%}
-
-The X-address format [packs the address and destination tag](https://github.com/XRPLF/XRPL-Standards/issues/6) into a more user-friendly value.
-
-
-### 3. Query the XRP Ledger
+{% step id="query-xrpl-tag" %}
+### 4. Query the XRP Ledger
 
 You can query the XRP Ledger to get information about [a specific account](../../../references/http-websocket-apis/public-api-methods/account-methods/index.md), [a specific transaction](../../../references/http-websocket-apis/public-api-methods/transaction-methods/tx.md), the state of a [current or a historical ledger](../../../references/http-websocket-apis/public-api-methods/ledger-methods/index.md), and [the XRP Ledger's decentralized exchange](../../../references/http-websocket-apis/public-api-methods/path-and-order-book-methods/index.md). You need to make these queries, among other reasons, to look up account info to follow best practices for [reliable transaction submission](../../../concepts/transactions/reliable-transaction-submission.md).
 
-Here, we use `xrpl-py`'s [`xrpl.account`](https://xrpl-py.readthedocs.io/en/latest/source/xrpl.account.html) module to look up information about the [account we got](#2-get-account) in the previous step.
+Use the [account_info method][] to look up information about the account you got in the previous step. Use a request model like `AccountInfo` to validate the request format and catch errors sooner.
+{% /step %}
 
+{% step id="run-app-tag" %}
+### 5. Run the Application
 
-{% code-snippet file="/_code-samples/get-started/py/get-acct-info.py" from="# Look up info about your account" language="py" /%}
-
-
-
-### 4. Putting it all together
-
-Using these building blocks, we can create a Python app that:
-
-1. Gets an account on the Testnet.
-2. Connects to the XRP Ledger.
-3. Looks up and prints information about the account you created.
-
-
-{% code-snippet file="/_code-samples/get-started/py/get-acct-info.py" language="python" /%}
-
-To run the app, you can copy and paste the code into an editor or IDE and run it from there. Or you could download the file from the [XRP Ledger Dev Portal repo](https://github.com/XRPLF/xrpl-dev-portal/tree/master/_code-samples/get-started/py) and run it locally:
-
+Finally, in your terminal, run the application like so:
 
 ```sh
-git clone git@github.com:XRPLF/xrpl-dev-portal.git
-cd xrpl-dev-portal/_code-samples/get-started/py/get-acct-info.py
-python3 get-acct-info.py
+python get-acct-info.py
 ```
 
 You should see output similar to this example:
 
 ```sh
-Classic address:
+Creating a new wallet and funding it with Testnet XRP...
+Attempting to fund address ravbHNootpSNQkxyEFCWevSkHsFGDHfyop
+Faucet fund successful.
+Wallet: ravbHNootpSNQkxyEFCWevSkHsFGDHfyop
+Account Testnet Explorer URL: 
+ https://testnet.xrpl.org/accounts/ravbHNootpSNQkxyEFCWevSkHsFGDHfyop
 
- rnQLnSEA1YFMABnCMrkMWFKxnqW6sQ8EWk
-X-address:
-
- T7dRN2ktZGYSTyEPWa9SyDevrwS5yDca4m7xfXTGM3bqff8
-response.status:  ResponseStatus.SUCCESS
+Getting account info...
+Response Status:  ResponseStatus.SUCCESS
 {
     "account_data": {
-        "Account": "rnQLnSEA1YFMABnCMrkMWFKxnqW6sQ8EWk",
-        "Balance": "1000000000",
+        "Account": "ravbHNootpSNQkxyEFCWevSkHsFGDHfyop",
+        "Balance": "100000000",
         "Flags": 0,
         "LedgerEntryType": "AccountRoot",
         "OwnerCount": 0,
-        "PreviousTxnID": "5A5203AFF41503539D11ADC41BE4185761C5B78B7ED382E6D001ADE83A59B8DC",
-        "PreviousTxnLgrSeq": 16126889,
-        "Sequence": 16126889,
-        "index": "CAD0F7EF3AB91DA7A952E09D4AF62C943FC1EEE41BE926D632DDB34CAA2E0E8F"
+        "PreviousTxnID": "3DACF2438AD39F294C4EFF6132D5D88BCB65D2F2261C7650F40AC1F6A54C83EA",
+        "PreviousTxnLgrSeq": 12039759,
+        "Sequence": 12039759,
+        "index": "148E6F4B8E4C14018D679A2526200C292BDBC5AB77611BC3AE0CB97CD2FB84E5"
     },
-    "ledger_current_index": 16126890,
-    "queue_data": {
-        "txn_count": 0
+    "account_flags": {
+        "allowTrustLineClawback": false,
+        "defaultRipple": false,
+        "depositAuth": false,
+        "disableMasterKey": false,
+        "disallowIncomingCheck": false,
+        "disallowIncomingNFTokenOffer": false,
+        "disallowIncomingPayChan": false,
+        "disallowIncomingTrustline": false,
+        "disallowIncomingXRP": false,
+        "globalFreeze": false,
+        "noFreeze": false,
+        "passwordSpent": false,
+        "requireAuthorization": false,
+        "requireDestinationTag": false
     },
-    "validated": false
+    "ledger_hash": "CA624D717C4FCDD03BAD8C193F374A77A14F7D2566354A4E9617A8DAD896DE71",
+    "ledger_index": 12039759,
+    "validated": true
 }
 ```
 
-#### Interpreting the response
-
 The response fields that you want to inspect in most cases are:
 
-* `account_data.Sequence` — This is the sequence number of the next valid transaction for the account. You need to specify the sequence number when you prepare transactions. With `xrpl-py`, you can use the [`get_next_valid_seq_number`](https://xrpl-py.readthedocs.io/en/latest/source/xrpl.account.html#xrpl.account.get_next_valid_seq_number) to get this automatically from the XRP Ledger. See an example of this usage in the project [README](https://github.com/XRPLF/xrpl-py#serialize-and-sign-transactions).
+- `account_data.Balance` — This is the account's balance of [XRP, in drops][]. You can use this to confirm that you have enough XRP to send (if you're making a payment) and to meet the [current transaction cost](../../../concepts/transactions/transaction-cost.md#current-transaction-cost) for a given transaction.
 
-* `account_data.Balance` — This is the account's balance of [XRP, in drops][]. You can use this to confirm that you have enough XRP to send (if you're making a payment) and to meet the [current transaction cost](../../../concepts/transactions/transaction-cost.md#current-transaction-cost) for a given transaction.
-
-* `validated` — Indicates whether the returned data is from a [validated ledger](../../../concepts/ledgers/open-closed-validated-ledgers.md). When inspecting transactions, it's important to confirm that [the results are final](../../../concepts/transactions/finality-of-results/index.md) before further processing the transaction. If `validated` is `true` then you know for sure the results won't change. For more information about best practices for transaction processing, see [Reliable Transaction Submission](../../../concepts/transactions/reliable-transaction-submission.md).
+- `validated` — Indicates whether the returned data is from a [validated ledger](../../../concepts/ledgers/open-closed-validated-ledgers.md). When inspecting transactions, it's important to confirm that [the results are final](../../../concepts/transactions/finality-of-results/index.md) before further processing the transaction. If `validated` is `true` then you know for sure the results won't change. For more information about best practices for transaction processing, see [Reliable Transaction Submission](../../../concepts/transactions/reliable-transaction-submission.md).
 
 For a detailed description of every response field, see [account_info](../../../references/http-websocket-apis/public-api-methods/account-methods/account_info.md#response-format).
+{% /step %}
 
+## See Also
 
-## Keep on building
-
-Now that you know how to use `xrpl-py` to connect to the XRP Ledger, get an account, and look up information about it, you can also use `xrpl-py` to:
-
-* [Send XRP](../../how-tos/send-xrp.md).
-* [Set up secure signing](../../../concepts/transactions/secure-signing.md) for your account.
+- **Concepts:**
+    - [XRP Ledger Overview](/about/)
+    - [Client Libraries](../../../references/client-libraries.md)
+- **Tutorials:**
+    - [Send XRP](../../how-tos/send-xrp.md)
+    - [Issue a Fungible Token](../../how-tos/use-tokens/issue-a-fungible-token.md)
+    - [Set up Secure Signing](../../../concepts/transactions/secure-signing.md)
+- **References:**
+    - [`xrpl-py` Reference](https://xrpl-py.readthedocs.io/en/latest/)
+    - [Public API Methods](../../../references/http-websocket-apis/public-api-methods/index.md)
+    - [API Conventions](../../../references/http-websocket-apis/api-conventions/index.md)
+        - [base58 Encodings](../../../references/protocol/data-types/base58-encodings.md)
+    - [Transaction Formats](../../../references/protocol/transactions/index.md)
 
 {% raw-partial file="/docs/_snippets/common-links.md" /%}
+
+{% /code-walkthrough %}

redocly.yaml

@@ -42,9 +42,6 @@ metadataGlobs:
     redocly_category: Community
 seo:
   siteUrl: https://xrpl.org/
-rbac:
-  reunite:
-    xrpl-org-editors: maintain
 analytics:
   gtm:
     includeInDevelopment: true

resources/known-amendments.md

@@ -742,6 +742,19 @@ Changes the way Checks transactions affect account metadata, so that Checks are
 Without this amendment, Checks transactions ([CheckCreate][], [CheckCash][], and [CheckCancel][]) only update the account history of the sender. With this amendment, those transactions affect both the sending and receiving accounts. This amendment has no effect unless the [Checks amendment](#checks) is also enabled.
 
 
+### fixDirectoryLimit
+[fixDirectoryLimit]: #fixdirectorylimit
+
+| Amendment    | fixdirectorylimit |
+|:-------------|:----------------------|
+| Amendment ID | 41765F664A8D67FF03DDB1C1A893DE6273690BA340A6C2B07C8D29D0DD013D3A |
+| Status       | Open for Voting |
+| Default Vote (Latest stable release) | No |
+| Pre-amendment functionality retired? | No |
+
+This amendment removes the directory page limit. Object reserve requirements provide enough incentive to avoid creating unnecessary objects on the XRP Ledger.
+
+
 ### fixDisallowIncomingV1
 [fixDisallowIncomingV1]: #fixdisallowincomingv1
 

sidebars.yaml

@@ -295,6 +295,11 @@
                 - page: docs/tutorials/how-tos/manage-account-settings/require-destination-tags.md
                 - page: docs/tutorials/how-tos/manage-account-settings/offline-account-setup.md
                 - page: docs/tutorials/how-tos/manage-account-settings/use-tickets.md
+            - page: docs/tutorials/how-tos/use-batch-transactions/index.md
+              expanded: false
+              items:
+                - page: docs/tutorials/how-tos/use-batch-transactions/send-a-single-account-batch-transaction.md
+                - page: docs/tutorials/how-tos/use-batch-transactions/send-a-multi-account-batch-transaction.md
             - page: docs/tutorials/how-tos/use-specialized-payment-types/index.md
               expanded: false
               items: