Remove emojis from code sample

Bump golang.org/x/crypto from 0.35.0 to 0.45.0 in /_code-samples/partial-payment/go

@l10n/es-ES/docs/concepts/accounts/account-types.md

@@ -74,8 +74,8 @@ Si una dirección de reserva se ve comprometida, las consecuencias son similares
     - [Cuentas](index.md)
     - [Claves criptográficas](cryptographic-keys.md)
 - **Tutoriales:**
-    - [Asignar par de claves regulares](../../tutorials/how-tos/manage-account-settings/assign-a-regular-key-pair.md)
-    - [Cambiar o eliminar par de claves regulares](../../tutorials/how-tos/manage-account-settings/change-or-remove-a-regular-key-pair.md)
+    - [Asignar par de claves regulares](/docs/tutorials/best-practices/key-management/assign-a-regular-key-pair.md)
+    - [Cambiar o eliminar par de claves regulares](/docs/tutorials/best-practices/key-management/change-or-remove-a-regular-key-pair.md)
 - **Referencias:**
     - [metodo account_info][]
     - [Transacción SetRegularKey][]

@l10n/es-ES/docs/concepts/accounts/cryptographic-keys.md

@@ -88,7 +88,7 @@ El [metodo wallet_propose][] es una forma de generar el par de claves maestras.
 
 **Atención:** Si un actor malicioso conoce tu clave privada maestra (o semilla), tendrá control completo sobre tu cuenta, a no ser que tu par de claves maestras se inhabilite. Puedes tomar todo tu dinero de la cuenta posee y causar un daño irreparable. ¡Trata tus valores secretos con cuidado!
 
-Dado que cambiar el par de claves maestras es imposible, debes cuidarlo en proporción al valor de lo que posea. Una buena práctica es [guardar tu par de claves maestras offline](../../tutorials/how-tos/manage-account-settings/offline-account-setup.md) y configurar un par de claves normales para firmar transacciones en tu cuenta. Al mantener el par de claves maestras activadas pero offline, puedes estar razonablemente seguro de que nadie puede acceder a él a través de Internet, pero aun así deberías encontrarlo en caso de una emergencia.
+Dado que cambiar el par de claves maestras es imposible, debes cuidarlo en proporción al valor de lo que posea. Una buena práctica es [guardar tu par de claves maestras offline](/docs/tutorials/best-practices/key-management/offline-account-setup.md) y configurar un par de claves normales para firmar transacciones en tu cuenta. Al mantener el par de claves maestras activadas pero offline, puedes estar razonablemente seguro de que nadie puede acceder a él a través de Internet, pero aun así deberías encontrarlo en caso de una emergencia.
 
 Mantener tu par de claves maestras offline significa no colocar tu información secreta (passphrase, semilla, or clave privada) en cualquier sitio en que los actores maliciosos puedan tener acceso a él. En general, esto quiere decir que no está al alcance de un programa inofrmático que interactúe con Internet. Por ejemplo, puedes guardarlo en un equipo que no se conecta nunca a Internet, en un trozo de papel guardado en una caja fuerte, o tenerla completamente memorizada. (Memorizarla tiene algunos puntos inconvenientes, incluido ser imposible pasar la clave una vez muerto.)
 
@@ -119,7 +119,7 @@ Una buena práctica de seguridad es guardar tu clave privada maestra en algun si
 
 El par de claves normales tiene el mismo formato que el par de claves maestras. Las generas de la misma forma (por ejemplo, usando el [método wallet_propose][]). La única diferencia es que el par de claves normales es que el par no está intrínsicamente vinculado a la cuenta para la que firma transacciones. Es posible (pero no es buena idea) utilizar el par de claves maestras de una cuenta como lel par de claves normales para otra cuenta.
 
-La [transacción SetRegularKey][] asigna o cambia el par de claves normales de una cuenta. Para un tutorial de asignación o cambio de un par de claves normales, ver [Asignar par de claves normales](../../tutorials/how-tos/manage-account-settings/assign-a-regular-key-pair.md).
+La [transacción SetRegularKey][] asigna o cambia el par de claves normales de una cuenta. Para un tutorial de asignación o cambio de un par de claves normales, ver [Asignar par de claves normales](/docs/tutorials/best-practices/key-management/assign-a-regular-key-pair.md).
 
 
 ## Algorítmos de firma
@@ -248,8 +248,8 @@ Los pasos para derivar par de claves de cuenta XRP Ledger secp256k1 desde un val
 - **Conceptos:**
     - [Direcciones de emisión y operacionales](account-types.md)
 - **Tutoriales:**
-    - [Asignación de par de claves normales](../../tutorials/how-tos/manage-account-settings/assign-a-regular-key-pair.md)
-    - [Cambiar o eliminar par de claves normales](../../tutorials/how-tos/manage-account-settings/change-or-remove-a-regular-key-pair.md)
+    - [Asignación de par de claves normales](/docs/tutorials/best-practices/key-management/assign-a-regular-key-pair.md)
+    - [Cambiar o eliminar par de claves normales](/docs/tutorials/best-practices/key-management/change-or-remove-a-regular-key-pair.md)
 - **Referencias:**
     - [Transacción SetRegularKey][]
     - [Objeto de ledger AccountRoot](../../references/protocol/ledger-data/ledger-entry-types/accountroot.md)

@l10n/es-ES/docs/concepts/accounts/index.md

@@ -63,7 +63,7 @@ La forma típica de obtener una cuenta en el XRP Ledger es la siguiente:
     - [Transacción Payment][]
     - [Objeto AccountRoot](../../references/protocol/ledger-data/ledger-entry-types/accountroot.md)
 - **Tutoriales:**
-    - [Administrar configuración de la cuenta (Categoría)](../../tutorials/how-tos/manage-account-settings/index.md)
-    - [Monitorizar pagos entrantes con WebSocket](../../tutorials/http-websocket-apis/build-apps/monitor-incoming-payments-with-websocket.md)
+    - [Administrar configuración de la cuenta (Categoría)](/docs/tutorials/best-practices/key-management/assign-a-regular-key-pair.md)
+    - [Monitorizar pagos entrantes con WebSocket](/docs/tutorials/advanced-developer-topics/client-library-development/monitor-incoming-payments-with-websocket.md)
 
 {% raw-partial file="/docs/_snippets/common-links.md" /%}

@l10n/es-ES/docs/concepts/accounts/multi-signing.md

@@ -60,7 +60,7 @@ Podría darse el caso donde crees una lista de multi firma como "plan de respald
 
 Para enviar transacciones multi-signed de forma satisfactoria, debes de hacer todo lo siguiente:
 
-* La dirección que envía la transacción (especificada en el campo `Account`) debe tener un [objeto `SignerList` en el ledger ](../../references/protocol/ledger-data/ledger-entry-types/signerlist.md). Para instrucciones de cómo hacer esto, ver [Set Up Multi-Signing](../../tutorials/how-tos/manage-account-settings/set-up-multi-signing.md).
+* La dirección que envía la transacción (especificada en el campo `Account`) debe tener un [objeto `SignerList` en el ledger ](../../references/protocol/ledger-data/ledger-entry-types/signerlist.md). Para instrucciones de cómo hacer esto, ver [Set Up Multi-Signing](/docs/tutorials/best-practices/key-management/set-up-multi-signing.md).
 * La transacción debe incluir el campo `SigningPubKey` como un valor vacío.
 * La transacción debe incluir el [campo `Signers`](../../references/protocol/transactions/common-fields.md#signers-field) conteniendo un array de firmas.
 * Las firmas presentadas en el array `Signers` debe coincidir con los firmantes definidos en la `SignerList`.
@@ -72,8 +72,8 @@ Para enviar transacciones multi-signed de forma satisfactoria, debes de hacer to
 ## Ver también
 
 - **Tutoriales:**
-    - [Configurar Multi-Signing](../../tutorials/how-tos/manage-account-settings/set-up-multi-signing.md)
-    - [Envíar una transacción Multi-Signed](../../tutorials/how-tos/manage-account-settings/send-a-multi-signed-transaction.md)
+    - [Configurar Multi-Signing](/docs/tutorials/best-practices/key-management/set-up-multi-signing.md)
+    - [Envíar una transacción Multi-Signed](/docs/tutorials/best-practices/key-management/send-a-multi-signed-transaction.md)
 - **Conceptos:**
     - [Claves criptográficas](cryptographic-keys.md)
     - [Coste de transacción especial para transacciones Multi-signed](../transactions/transaction-cost.md#special-transaction-costs)

@l10n/es-ES/docs/concepts/accounts/reserves.md

@@ -54,7 +54,7 @@ Las aplicaciones pueden buscar los valores de las reservas base e incremental ac
 
 Para determinar las reservas de propietario de una cuenta, hay que multiplicar la reserva incremental por el número de objetos que la cuenta posee. Para mirar el número de objetos que una cuenta posee, llama al [método account_info][] y toma `account_data.OwnerCount`.
 
-Para calcular el requisito total de direcciones, multiplica `OwnerCount` por `reserve_inc_xrp`, y luego suma `reserve_base_xrp`. [Aquí tienes una demostración](../../tutorials/python/build-apps/build-a-desktop-wallet-in-python.md#codeblock-17) del cálculo en Python.
+Para calcular el requisito total de direcciones, multiplica `OwnerCount` por `reserve_inc_xrp`, y luego suma `reserve_base_xrp`. [Aquí tienes una demostración](/docs/tutorials/sample-apps/build-a-desktop-wallet-in-python.md#codeblock-17) del cálculo en Python.
 
 
 ## Quedarse por debajo del requisito de reserva
@@ -76,6 +76,6 @@ El XRP Ledger tiene un mecanismo para ajustar los requisitos de reserva. Estos a
 - [Objeto AccountRoot][]
 - [Votación de Fee](../consensus-protocol/fee-voting.md)
 - [Pseudo-transacción SetFee][]
-- [Tutorial: Calcular y mostrar los requisitos de reserva (Python)](../../tutorials/python/build-apps/build-a-desktop-wallet-in-python.md#3-display-an-account)
+- [Tutorial: Calcular y mostrar los requisitos de reserva (Python)](/docs/tutorials/sample-apps/build-a-desktop-wallet-in-python.md#3-display-an-account)
 
 {% raw-partial file="/docs/_snippets/common-links.md" /%}

@l10n/es-ES/docs/concepts/accounts/tickets.md

@@ -63,7 +63,7 @@ Cualquier cuenta puede crear y utilizar Tickets en cualquier tipo de transaccion
 - **Conceptos:**
     - [Multi-Signing](multi-signing.md)
 - **Tutoriales:**
-    - [Usar Tickets](../../tutorials/how-tos/manage-account-settings/use-tickets.md)
+    - [Usar Tickets](/docs/tutorials/best-practices/transaction-sending/use-tickets.md)
 - **Referencias:**
     - [Transacción TicketCreate][]
     - [Campos comunes de una transacción](../../references/protocol/transactions/common-fields.md)

@l10n/es-ES/docs/concepts/networks-and-servers/index.md

@@ -27,7 +27,7 @@ Necesitas confiar en el servidor que utilizas. Si te conectas a un servidor mali
 * Podría selectivamente mostrar u ocultar los caminos (o paths) de pago y las foertas de intercambio de divisas para garantizar su propio beneficio mientras no te ofrece la mejor oferta.
 * Si le enviaste la clave secreta de tu dirección, esto podría generar transacciones arbitrarias en tu nombre e incluso transferir o destruir todo el dinero que la dirección posee.
 
-Adicionalmente, ejecutar tu propio servidor te da [acceso de administrador](../../tutorials/http-websocket-apis/build-apps/get-started.md#admin-access), lo que te permite ejecutar comandos exclusivos de administrador y de carga intensa. Si utilizas un servidor compartido, debes preocuparte por los otros usuarios del mismo servidor compitiendo contra ti por el poder de computación del servidor. Muchos de los comandos en el API WebSocket puede poner mucha presión sobre el servidor, por lo que el servidor tiene la opción de reducir sus respuestas cuando lo necesite. Si compartes un servidor con otros, puede que no siempre consigas los mejores resultados posibles.
+Adicionalmente, ejecutar tu propio servidor te da [acceso de administrador](/docs/tutorials/get-started/get-started-http-websocket-apis.md#admin-access), lo que te permite ejecutar comandos exclusivos de administrador y de carga intensa. Si utilizas un servidor compartido, debes preocuparte por los otros usuarios del mismo servidor compitiendo contra ti por el poder de computación del servidor. Muchos de los comandos en el API WebSocket puede poner mucha presión sobre el servidor, por lo que el servidor tiene la opción de reducir sus respuestas cuando lo necesite. Si compartes un servidor con otros, puede que no siempre consigas los mejores resultados posibles.
 
 Finalmente, si ejecutas un servidor de validación, puedes utilizar un servidor común como proxy a la red pública mientras mantienes tu servidor de vaalidación en una red privada la cual es solo accesible desde el mundo exterior desde tu servidor común. Esto hace más difícil comprometer la integridad de tu servidor de validación.
 

@l10n/es-ES/docs/concepts/networks-and-servers/parallel-networks.md

@@ -17,8 +17,6 @@ Para ayudar a miembros de la comunidad del XRP Ledger a interactuar con la tecno
 | Mainnet | Lanzamientos estables | _El_ [XRP Ledger](/about/), un libro contable criptográfico descentralizado impulsado por una red de servidores peer-to-peer y el hogar de [XRP](../../introduction/what-is-xrp.md). |
 | Testnet | Lanzamientos estables | Una red de "universo alternativo" que actua como un campo de pruebas para el software construido en el XRP Ledger, sin impactar a los usuarios del XRP Ledger de producción y sin arriesgar dinero real. El [estado de enmienda](/resources/known-amendments.md) de Testnet está destinado a reflejar de cerca el de la Mainnet, aunque pueden ocurrir ligeras variaciones en el tiempo debido a la naturaleza impredecible de los sistemas descentralizados. |
 | Devnet  | Lanzamientos Beta   | Una vista previa de las próximas atracciones, donde cambios inestables en el software principal de XRP Ledger se pueden probar. Los desarrolladores pueden utilizar esta altnet para interactuar y aprender sobre funcionalidades nuevas planficiadas para el XRP Ledger y enmiendas que no están habilitadas en la Mainnet. |
-| [Hooks V3 Testnet](https://hooks-testnet-v3.xrpl-labs.com/) | [Servidor Hooks](https://github.com/XRPL-Labs/xrpld-hooks) | Una vista previa de la funcionalidad de smart contract en la cadena utilizando [hooks](https://xrpl-hooks.readme.io/). |
-| Sidechain-Devnet | Lanzamientos Beta | Una sidechain para probar funcionalidades en puentes cross-chain. Devnet se trata como la cadena de bloqueo y esta sidechain es la cadena de emisión.<br>Soporte a la librería:<br>- [xrpl.js 2.12.0](https://www.npmjs.com/package/xrpl/v/2.12.0)<br>- [xrpl-py 2.4.0](https://pypi.org/project/xrpl-py/2.4.0/)<br>**Nota**: También puedes usar la herramienta de línea de comandos [`xbridge-cli`](https://github.com/XRPLF/xbridge-cli) para configurar un puente entre cadenas en tu máquina local. |
 
 Cada altnet tiene su propia distribución separada de XRP de prueba, que se [regala gratis](/resources/dev-tools/xrp-faucets) a partes interesadas en experimentar con el XRP Ledger y desarrollar aplicaciones e integraciones. El XRP test no tiene valor en el mundo real y se pierde cuando la red se reinicia.
 

@l10n/es-ES/docs/concepts/networks-and-servers/rippled-server-modes.md

@@ -12,7 +12,7 @@ El software del servidor `rippled` puede ejecutarse en varios modos dependiendo
 
 - [**Modo P2P**](#modo-p2p) - Este es el modo principal del servidor: sigue la red peer-to-peer, procesa transacciones, y mantiene cierta cantidad de [histórico del ledger](ledger-history.md). Este modo se puede configurar para alguno o todos los siguientes roles:
     - [**Validador**](#validadores) - Ayuda a asegurar la red participando en el consenso.
-    - [**Servidor API**](#servidores-api) - Proporciona [acceso API](../../tutorials/http-websocket-apis/build-apps/get-started.md) para leer datos del ledger compartido, enviar transacciones, y mirar la actividad en el ledger. Opcionalmente, puede ser un [**servidor full history**](#servidores-full-history), el cual guarda un registro completo de transacciones y el histórico del ledger.
+    - [**Servidor API**](#servidores-api) - Proporciona [acceso API](/docs/tutorials/get-started/get-started-http-websocket-apis.md) para leer datos del ledger compartido, enviar transacciones, y mirar la actividad en el ledger. Opcionalmente, puede ser un [**servidor full history**](#servidores-full-history), el cual guarda un registro completo de transacciones y el histórico del ledger.
     - [**Servidor hub**](#hubs-públicos) - Transmite mensajes entre muchos otros miembros de la red peer-to-peer.
 - [**Modo solitario**](#modo-solitario) - Un modo offline para pruebas. No se conecta a la red peer-to-peer ni usa consenso.
 

@l10n/es-ES/docs/concepts/payment-types/checks.md

@@ -50,11 +50,11 @@ Para más información sobre Cheques en el XRP Ledger, ver:
     - [CheckCash][]
     - [CheckCancel][]
 - [Tutoriales de cheques](../../tutorials/how-tos/use-specialized-payment-types/use-checks/index.md)
-    - [Enviar un cheque](../../tutorials/how-tos/use-specialized-payment-types/use-checks/send-a-check.md)
-    - [Buscar cheques](../../tutorials/how-tos/use-specialized-payment-types/use-checks/look-up-checks.md)
-    - [Canjear un cheque por la cantidad exacta](../../tutorials/how-tos/use-specialized-payment-types/use-checks/cash-a-check-for-an-exact-amount.md)
-    - [Canjear un cheque por una cantidad flexible](../../tutorials/how-tos/use-specialized-payment-types/use-checks/cash-a-check-for-a-flexible-amount.md)
-    - [Cancelar un cheque](../../tutorials/how-tos/use-specialized-payment-types/use-checks/cancel-a-check.md)
+    - [Enviar un cheque](/docs/tutorials/payments/send-a-check.md)
+    - [Buscar cheques](/docs/tutorials/ /how-tos/use-specialized-payment-types/use-checks/look-up-checks.md)
+    - [Canjear un cheque por la cantidad exacta](/docs/tutorials/payments/cash-a-check-for-an-exact-amount.md)
+    - [Canjear un cheque por una cantidad flexible](/docs/tutorials/payments/cash-a-check-for-a-flexible-amount.md)
+    - [Cancelar un cheque](/docs/tutorials/payments/cancel-a-check.md)
 - [Enmienda Cheques][]
 
 Para más información sobre funciones relacionadas, ver:

@l10n/es-ES/docs/concepts/payment-types/direct-xrp-payments.md

@@ -39,8 +39,8 @@ La base de cualquier sistema financiero es la transferencia de valor. El método
 ## Ver también
 
 - **Tutoriales:**
-    - [Enviar XRP (Tutorial interactivo)](../../tutorials/how-tos/send-xrp.md)
-    - [Monitorizar pagos entrantes con WebSocket](../../tutorials/http-websocket-apis/build-apps/monitor-incoming-payments-with-websocket.md)
+    - [Enviar XRP (Tutorial interactivo)](/docs/tutorials/payments/send-xrp.md)
+    - [Monitorizar pagos entrantes con WebSocket](/docs/tutorials/advanced-developer-topics/client-library-development/monitor-incoming-payments-with-websocket.md)
 - **Referencias:**
     - [Transacción Payment][]
     - [Resultados de Transaction](../../references/protocol/transactions/transaction-results/index.md)

@l10n/es-ES/docs/concepts/payment-types/partial-payments.md

@@ -128,7 +128,7 @@ Utilizar [el campo `delivered_amount`](#the-delivered_amount-field) al procesar
     - [Transacciones](../transactions/index.md)
 - **Tutoriales:**
     - [Buscar resultados de transacciones](../transactions/finality-of-results/look-up-transaction-results.md)
-    - [Monitorear pagos recibidos con WebSocket](../../tutorials/http-websocket-apis/build-apps/monitor-incoming-payments-with-websocket.md)
+    - [Monitorear pagos recibidos con WebSocket](/docs/tutorials/advanced-developer-topics/client-library-development/monitor-incoming-payments-with-websocket.md)
     - [Usar tipos de pagos especializados](../../tutorials/how-tos/use-specialized-payment-types/index.md)
     - [Listar XRP en un Exchange](../../use-cases/defi/list-xrp-as-an-exchange.md)
 - **Referencias:**

@l10n/ja/docs/_snippets/checkcash-prereqs.md

@@ -6,4 +6,4 @@ Checkを換金するための前提条件は、正確な金額を換金する場
 - 発行済み通貨用のCheckの場合は、ご自身（受取人）にイシュアーに対するトラストラインがある必要があります。このトラストライン上のご自身の限度額は、受け取る金額を追加するための残高より十分高くなければなりません。
   - トラストラインと限度額について詳しくは、[トークン](../concepts/tokens/index.md)および[トラストラインと発行](../concepts/tokens/fungible-tokens/index.md)をご覧ください。
 - [トランザクションに安全に署名できる手段](../concepts/transactions/secure-signing.md)。
-- XRP Ledgerに接続できる[クライアントライブラリ](../references/client-libraries.md)か、それとも[HTTPライブラリ、WebSocketライブラリなど](../tutorials/http-websocket-apis/build-apps/get-started.md)。
+- XRP Ledgerに接続できる[クライアントライブラリ](../references/client-libraries.md)か、それとも[HTTPライブラリ、WebSocketライブラリなど](../tutorials/http-websocket-apis/get-started.md)。

@l10n/ja/docs/_snippets/post-rippled-install.md

@@ -2,7 +2,7 @@
 
 `rippled`ログメッセージの詳細は、[ログメッセージについて](../infrastructure/troubleshooting/understanding-log-messages.md)をご覧ください。
 
-`rippled`が残りのネットワークと同期されたら、ストック`rippled`サーバが完全に機能するようになります。このサーバを、ローカル署名やXRP LedgerへのAPIアクセスに使用できます。`rippled`サーバがネットワークと同期されているかどうかを判別するには、[`rippled`サーバの状況](../references/http-websocket-apis/api-conventions/rippled-server-states.md)を使用します。[`rippled`のコマンドラインインターフェイス](../tutorials/http-websocket-apis/build-apps/get-started.md#コマンドライン)を使用すれば、これを迅速にテストできます。
+`rippled`が残りのネットワークと同期されたら、ストック`rippled`サーバが完全に機能するようになります。このサーバを、ローカル署名やXRP LedgerへのAPIアクセスに使用できます。`rippled`サーバがネットワークと同期されているかどうかを判別するには、[`rippled`サーバの状況](../references/http-websocket-apis/api-conventions/rippled-server-states.md)を使用します。[`rippled`のコマンドラインインターフェイス](../tutorials/http-websocket-apis/get-started.md#コマンドライン)を使用すれば、これを迅速にテストできます。
 
 ```sh
 rippled server_info

@l10n/ja/docs/concepts/accounts/reserves.md

@@ -54,7 +54,7 @@ XRP Ledgerでは、スパムや悪意のある使用によって、共有グロ
 
 アカウントの所有者準備金を決定するには、増分準備金にアカウントが所有するオブジェクトの数を掛けます。アカウントが所有しているオブジェクトの数を調べるには、[account_infoメソッド][]を呼び出し、`account_data.OwnerCount`を取得します。
 
-アドレスの必要となる合計準備金を計算するには、`OwnerCount`に`reserve_inc_xrp`を掛け、次に`reserve_base_xrp`を加えます。[この計算をPythonで行うデモ](../../tutorials/python/build-apps/build-a-desktop-wallet-in-python.md#codeblock-17)があります。
+アドレスの必要となる合計準備金を計算するには、`OwnerCount`に`reserve_inc_xrp`を掛け、次に`reserve_base_xrp`を加えます。[この計算をPythonで行うデモ](/docs/tutorials/sample-apps/build-a-desktop-wallet-in-python.md#codeblock-17)があります。
 
 
 ## 必要準備金を下回る
@@ -76,6 +76,6 @@ XRP Ledgerには、準備金要件を調整する仕組みがあります。こ
 - [AccountRootオブジェクト][]
 - [手数料の投票](../consensus-protocol/fee-voting.md)
 - [SetFee疑似トランザクション][]疑似トランザクション
-- [チュートリアル: 必要準備金の計算と表示（Python）](../../tutorials/python/build-apps/build-a-desktop-wallet-in-python.md#3-display-an-account)
+- [チュートリアル: 必要準備金の計算と表示（Python）](/docs/tutorials/sample-apps/build-a-desktop-wallet-in-python.md#3-display-an-account)
 
 {% raw-partial file="/@l10n/ja/docs/_snippets/common-links.md" /%}

@l10n/ja/docs/concepts/networks-and-servers/index.md

@@ -27,7 +27,7 @@ XRP Ledgerを動かすサーバソフトウェアは、主に2種類あります
 * 選択的に支払いパスや通貨交換のオファーを表示または非表示にすることができ、最良の取引を提供せず、彼ら自身の利益を確保する可能性があります。
 * もし、アドレスの秘密鍵を送信してしまった場合、サーバの管理者はあなたに代わって任意のトランザクションを実行し、アドレスが保有するすべての資金を転送または破棄する可能性があります。
 
-さらに、独自のサーバを運営することで、[管理者アクセス権限](../../tutorials/http-websocket-apis/build-apps/get-started.md#管理者アクセス権限)が与えられ、重要な管理者専用コマンドや負荷の高いコマンドを実行することができます。共有サーバを使用する場合、同じサーバの他のユーザとサーバの計算能力を共有することを考慮しなければいけません。WebSocket APIのコマンドの多くはサーバに大きな負担をかけるので、サーバには必要なときにレスポンスを縮小するオプションがあります。サーバを他人と共有する場合、常に最良の結果を得られるとは限りません。
+さらに、独自のサーバを運営することで、[管理者アクセス権限](/docs/tutorials/get-started/get-started-http-websocket-apis.md#管理者アクセス権限)が与えられ、重要な管理者専用コマンドや負荷の高いコマンドを実行することができます。共有サーバを使用する場合、同じサーバの他のユーザとサーバの計算能力を共有することを考慮しなければいけません。WebSocket APIのコマンドの多くはサーバに大きな負担をかけるので、サーバには必要なときにレスポンスを縮小するオプションがあります。サーバを他人と共有する場合、常に最良の結果を得られるとは限りません。
 
 最後に、バリデーションサーバを運用する場合、パブリックネットワークへのプロキシとしてストックサーバを使用し、バリデーションサーバをプライベートネットワークに置いて、ストックサーバを通してのみ外部にアクセスできるようにすることができます。これにより、バリデーションサーバに侵入することがより困難になります。
 

@l10n/ja/docs/concepts/networks-and-servers/parallel-networks.md

@@ -17,8 +17,6 @@ XRP Ledgerコミュニティのメンバーが、メインネットに影響を
 | Mainnet    | 安定版リリース    | ピアツーピアサーバのネットワーク機能を備えた分散型の暗号台帳であり、[XRP](../../introduction/what-is-xrp.md)の土台となる[XRP Ledger](/about/)です。 |
 | Testnet    | 安定版リリース    | XRP Ledger上に構築したソフトウェアのテスト環境として動作する「代替環境」のネットワークです。本番環境のXRP Ledgerユーザに影響を及ぼすことも、本物の通貨をリスクにさらすこともありません。Testnetの[Amendmentのステータス](/resources/known-amendments.md)は、Mainnetを厳密に反映するようになっていますが、分散型システムが持つ予測不可能な性質により、タイミングにわずかな違いが生じることがあります。 |
 | Devnet     | ベータ版リリース  | 次期リリースのプレビューネットワークです。XRP Ledgerのコアソフトウェアへの不安定な変更がテストされます。このAltNetを使用すると、開発者はまだMainnetで有効になっていないXRPLの計画段階の新機能やAmendmentを操作したり学習したりすることができます。 |
-| [Hooks V3 Testnet](https://hooks-testnet-v3.xrpl-labs.com/) | [Hooksサーバ](https://github.com/XRPL-Labs/xrpld-hooks) | [Hooks](https://xrpl-hooks.readme.io/)を使用したオンチェーン・スマートコントラクト機能のプレビューネットワークです。 |
-| Sidechain-Devnet | ベータ版リリース | クロスチェーンブリッジ機能をテストするためのサイドチェーンです。<br>ライブラリのサポート:<br>- [xrpl.js 2.12.0](https://www.npmjs.com/package/xrpl/v/2.12.0)<br>- [xrpl-py 2.4.0](https://pypi.org/project/xrpl-py/2.4.0/)<br>**注記**: また、[`xbridge-cli`](https://github.com/XRPLF/xbridge-cli)コマンドラインツールを使用して、ローカルマシンにクロスチェーンブリッジをセットアップすることもできます。 |
 
 テスト用XRPは、XRP Ledgerの実験やアプリケーションの開発、統合に興味のある人々に[無償で提供](/resources/dev-tools/xrp-faucets)されています。テスト用のXRPは実際には価値を持たず、ネットワークがリセットされると失われます。
 

@l10n/ja/docs/concepts/networks-and-servers/rippled-server-modes.md

@@ -12,7 +12,7 @@ labels:
 
 - [**P2Pモード**](#p2pモード) - ピアツーピアネットワークをフォローし、トランザクションを処理し、ある程度の[レジャー履歴](ledger-history.md)を維持します。このモードは、以下の役割のいずれか、またはすべてを行うように設定することができます。
     - [**バリデータ**](#バリデータ) - コンセンサスに参加することで、ネットワークの安全確保に貢献します。
-    - [**APIサーバ**](#apiサーバ) - 共有レジャーからデータを読み込んだり、トランザクションを送信したり、レジャーのアクティビティを監視するための[APIアクセス](../../tutorials/http-websocket-apis/build-apps/get-started.md)を提供します。オプションとして、トランザクションやレジャーの履歴を完全に記録する [**全履歴サーバ**](#全履歴サーバ) とすることができます。
+    - [**APIサーバ**](#apiサーバ) - 共有レジャーからデータを読み込んだり、トランザクションを送信したり、レジャーのアクティビティを監視するための[APIアクセス](/docs/tutorials/get-started/get-started-http-websocket-apis.md)を提供します。オプションとして、トランザクションやレジャーの履歴を完全に記録する [**全履歴サーバ**](#全履歴サーバ) とすることができます。
     - [**ハブサーバ**](#公開ハブ) - ピアツーピアネットワークの他の多くのメンバー間のメッセージを中継します。
 - [**レポートモード**](#レポートモード) - リレーショナルデータベースからのAPIリクエストに対応するための専用モードです。ピアツーピアネットワークには参加しないため、P2Pモードサーバを実行し、信頼できるgRPC接続を使用してレポートモードサーバに接続する必要があります。 {% badge href="https://github.com/XRPLF/rippled/releases/tag/1.7.0" %}新規: rippled 1.7.0{% /badge %}
 - [**スタンドアロンモード**](#スタンドアロンモード) - テスト用のオフラインモードです。ピアツーピアネットワークに接続せず、コンセンサスも使用しません。

@l10n/ja/docs/concepts/payment-types/checks.md

@@ -97,12 +97,12 @@ XRP LedgerのChecksの詳細は、以下をご覧ください。
     - [CheckCreate][]
     - [CheckCash][]
     - [CheckCancel][]
-- [Checksのチュートリアル](../../tutorials/how-tos/use-specialized-payment-types/use-checks/index.md)
-    - [Checkの送信](../../tutorials/how-tos/use-specialized-payment-types/use-checks/send-a-check.md)
-    - [Checksの検索](../../tutorials/how-tos/use-specialized-payment-types/use-checks/look-up-checks.md)
-    - [Checkの指定された金額での換金](../../tutorials/how-tos/use-specialized-payment-types/use-checks/cash-a-check-for-an-exact-amount.md)
-    - [Checkの変動金額での換金](../../tutorials/how-tos/use-specialized-payment-types/use-checks/cash-a-check-for-a-flexible-amount.md)
-    - [Checkの取消し](../../tutorials/how-tos/use-specialized-payment-types/use-checks/cancel-a-check.md)
+- Checksのチュートリアル
+    - [Checkの送信](/docs/tutorials/payments/send-a-check.md)
+    - [Checksの検索](/docs/tutorials/payments/look-up-checks.md)
+    - [Checkの指定された金額での換金](/docs/tutorials/payments/cash-a-check-for-an-exact-amount.md)
+    - [Checkの変動金額での換金](/docs/tutorials/payments/cash-a-check-for-a-flexible-amount.md)
+    - [Checkの取消し](/docs/tutorials/payments/cancel-a-check.md)
 - [Checks Amendment][]
 
 関連機能の詳細については、以下をご覧ください。

@l10n/ja/docs/concepts/transactions/index.md

@@ -207,7 +207,7 @@ XRP Ledgerは、トランザクションオブジェクトが送信元アドレ
   - [安全な署名の設定](secure-signing.md)
   - [XRPの送金](../../tutorials/how-tos/send-xrp.md)
   - [トランザクションの結果の確認](finality-of-results/look-up-transaction-results.md)
-  - [WebSocketを使用した着信ペイメントの監視](../../tutorials/http-websocket-apis/build-apps/monitor-incoming-payments-with-websocket.md)
+  - [WebSocketを使用した着信ペイメントの監視](/docs/tutorials/advanced-developer-topics/client-library-development/monitor-incoming-payments-with-websocket.md)
   - [トランザクションの取り消しまたはスキップ](finality-of-results/canceling-a-transaction.md)
   - [信頼できるトランザクションの送信](reliable-transaction-submission.md)
 - **リファレンス:**

@l10n/ja/docs/concepts/transactions/secure-signing.md

@@ -48,7 +48,7 @@ labels:
 
     [構成ファイルの例](https://github.com/XRPLF/rippled/blob/8429dd67e60ba360da591bfa905b58a35638fda1/cfg/rippled-example.cfg#L1050-L1073)では、ローカルループバックネットワーク上（127.0.0.1）のポート5005でJSON-RPC（HTTP）、ポート6006でWebSocket（WS）の接続をリッスンし、接続されるすべてのクライアントを管理者として扱っています。
 
-    {% admonition type="warning" name="注意" %}署名に[コマンドラインAPI](../../references/http-websocket-apis/api-conventions/request-formatting.md#コマンドライン形式)を使用する場合は、コマンドラインでないクライアントで[Websocket APIやJSON-RPC APIを使用](../../tutorials/http-websocket-apis/build-apps/get-started.md)する場合よりもセキュリティが弱くなります。コマンドライン構文を使用すると、秘密鍵がシステムのプロセスリストで他のユーザに見える可能性があり、シェル履歴にプレーンテキスト形式でキーが保存される可能性があります。{% /admonition %}
+    {% admonition type="warning" name="注意" %}署名に[コマンドラインAPI](../../references/http-websocket-apis/api-conventions/request-formatting.md#コマンドライン形式)を使用する場合は、コマンドラインでないクライアントで[Websocket APIやJSON-RPC APIを使用](/docs/tutorials/get-started/get-started-http-websocket-apis.md)する場合よりもセキュリティが弱くなります。コマンドライン構文を使用すると、秘密鍵がシステムのプロセスリストで他のユーザに見える可能性があり、シェル履歴にプレーンテキスト形式でキーが保存される可能性があります。{% /admonition %}
 
 3. サーバの使用中は、稼働状態と最新状態を維持して、ネットワークと同期されるようにしておく必要があります。
 

@l10n/ja/docs/infrastructure/configuration/configure-amendment-voting.md

@@ -9,7 +9,7 @@ labels:
 ---
 # Amendment投票機能の設定
 
-バリデータとして設定されたサーバは、[featureメソッド][]を使ってXRP Ledgerプロトコルの[Amendment](../../concepts/networks-and-servers/amendments.md)に投票することができます。(この方法には[管理者アクセス](../../tutorials/http-websocket-apis/build-apps/get-started.md#管理者アクセス権限)が必要です).
+バリデータとして設定されたサーバは、[featureメソッド][]を使ってXRP Ledgerプロトコルの[Amendment](../../concepts/networks-and-servers/amendments.md)に投票することができます。(この方法には[管理者アクセス](/docs/tutorials/get-started/get-started-http-websocket-apis.md#管理者アクセス権限)が必要です).
 
 例えば、「SHAMapV2」Amendmentに反対票を投じるには、以下のコマンドを実行します。
 

@l10n/ja/docs/infrastructure/configuration/configure-grpc.md

@@ -49,7 +49,7 @@ gRPCを有効にするには、次の前提条件を満たす必要がありま
     - [XRP Ledgerの概要](/about/)
     - [`rippled`サーバのモード](../../concepts/networks-and-servers/rippled-server-modes.md)
 - **チュートリアル:**
-    - [HTTP / WebSocketAPIを使ってみる](../../tutorials/http-websocket-apis/build-apps/get-started.md)
+    - [HTTP / WebSocketAPIを使ってみる](/docs/tutorials/get-started/get-started-http-websocket-apis.md)
     - [信頼できるトランザクションの送信](../../concepts/transactions/reliable-transaction-submission.md)
     - [rippledサーバの管理](../installation/install-rippled-on-ubuntu.md)
 - **リファレンス:**

@l10n/ja/docs/infrastructure/configuration/connect-your-rippled-to-the-xrp-test-net.md

@@ -43,11 +43,6 @@ labels:
     # No [ips] stanza. Use the default hubs to connect to Mainnet.
     ```
 
-    ```{% label="Sidechain-Devnet" %}
-    [ips]
-    sidechain-net2.devnet.rippletest.net 51235
-    ```
-
     {% /tabs %}
 
 2. 以前の `[ips]`があれば、コメントアウトしてください。
@@ -78,11 +73,6 @@ labels:
     main
     ```
 
-    ```{% label="Sidechain-Devnet" %}
-    [network_id]
-    262
-    ```
-
     {% /tabs %}
 
     カスタムネットワークの場合、そのネットワークに接続する全員が、そのネットワークに固有の値を使用する必要があります。新しいネットワークを作成するときは、ネットワークIDを11から4,294,967,295までの整数からランダムに選択します。
@@ -121,14 +111,6 @@ labels:
     ED2677ABFFD1B33AC6FBC3062B71F1E8397C1505E1C42C64D11AD1B28FF73F4734
     ```
 
-    ```{% label="Sidechain-Devnet" %}
-    [validator_list_sites]
-    https://vlsidechain-net2.devnet.rippletest.net
-
-    [validator_list_keys]
-    EDA5504C7133743FADA46342229B4E9CBBE1CF9BCA19D16633574F7CBB72F79569
-    ```
-
     {% /tabs %}
 
     {% admonition type="success" name="ヒント" %}プレビュー版パッケージには必要な項目があらかじめ設定されている場合がありますが、念のため確認してください。{% /admonition %}
@@ -182,13 +164,6 @@ labels:
 ```
 {% /tab %}
 
-{% tab label="Sidechain-Devnet" %}
-```
-[features]
-XChainBridge
-```
-{% /tab %}
-
 {% /tabs %}
 
 {% admonition type="danger" name="警告" %}メインネットまたはテストネットに接続するときは、`[features]`を使用しないでください。他のネットワークと異なる機能を強制的に有効にすると、サーバがネットワークから分断される可能性があります。{% /admonition %}

@l10n/ja/docs/infrastructure/configuration/data-retention/configure-advisory-deletion.md

@@ -57,7 +57,7 @@ labels:
 
 2. サーバに対してオンライン削除を指示する[can_deleteメソッド][]の実行をテストします。
 
-    このコマンドの実行には[`rippled`コマンドラインインターフェイス](../../../tutorials/http-websocket-apis/build-apps/get-started.md#コマンドライン)を使用できます。例:
+    このコマンドの実行には[`rippled`コマンドラインインターフェイス](/docs/tutorials/get-started/get-started-http-websocket-apis.md#コマンドライン)を使用できます。例:
 
     ```
     $ rippled --conf=/etc/opt/ripple/rippled.cfg can_delete now

@l10n/ja/docs/infrastructure/configuration/enable-public-signing.md

@@ -11,7 +11,7 @@ labels:
 
 {% badge href="https://github.com/XRPLF/rippled/releases/tag/1.1.0" %}新規: rippled 1.1.0{% /badge %}デフォルトでは、`rippled`の署名メソッドは管理者接続に限定されています。v1.1.0以前のバージョンの`rippled`のように、署名メソッドをパブリックAPIメソッドとして使用できるようにするには、構成を変更することで、これを使用できるようにします。
 
-これにより、サーバが「パブリック」[JSON-RPC接続およびWebSocket接続](../../tutorials/http-websocket-apis/build-apps/get-started.md)を受け入れる場合は、これらのパブリック接続で以下のメソッドが使用できるようになります。
+これにより、サーバが「パブリック」[JSON-RPC接続およびWebSocket接続](/docs/tutorials/get-started/get-started-http-websocket-apis.md)を受け入れる場合は、これらのパブリック接続で以下のメソッドが使用できるようになります。
 
 - [sign][signメソッド]
 - [sign_for][sign_forメソッド]

@l10n/ja/docs/infrastructure/installation/install-rippled-on-rhel.md

@@ -80,7 +80,7 @@ labels:
 - **チュートリアル:**
     - [rippledの構成](../configuration/index.md)
     - [rippledのトラブルシューティング](../troubleshooting/index.md)
-    - [rippled APIの使用開始](../../tutorials/http-websocket-apis/build-apps/get-started.md)
+    - [rippled APIの使用開始](/docs/tutorials/get-started/get-started-http-websocket-apis.md)
 - **リファレンス:**
     - [rippled APIリファレンス](../../references/http-websocket-apis/index.md)
       - [`rippled`コマンドラインの使用](../commandline-usage.md)

@l10n/ja/docs/infrastructure/troubleshooting/fix-sqlite-tx-db-page-size-issue.md

@@ -182,7 +182,7 @@ Terminating thread doJob:AcquisitionDone: unhandled
 
 11. `rippled`サービスが正常に起動したかどうかを確認します。
 
-    [コマンドラインインターフェイス](../../tutorials/http-websocket-apis/build-apps/get-started.md#コマンドライン)を使用してサーバの状況を確認できます（サーバがJSON-RPCリクエストを受け入れないように設定している場合を除く）。次に例を示します。
+    [コマンドラインインターフェイス](/docs/tutorials/get-started/get-started-http-websocket-apis.md#コマンドライン)を使用してサーバの状況を確認できます（サーバがJSON-RPCリクエストを受け入れないように設定している場合を除く）。次に例を示します。
 
     ```
     /opt/ripple/bin/rippled server_info

@l10n/ja/docs/references/client-libraries.md

@@ -12,10 +12,10 @@ seo:
 
 | 言語                             | ライブラリ名             | Get Started | APIリファレンス | ソースコード |
 |---------------------------------|------------------------|--------------|---------------|-------------|
-| **Python**                      | `xrpl-py`              | [Pythonを使ってみよう](../tutorials/python/build-apps/get-started.md) | [API リファレンス](https://xrpl-py.readthedocs.io/) | [リポジトリ](https://github.com/XRPLF/xrpl-py) |
-| **JavaScript** / **TypeScript** | `xrpl.js`              | [JavaScriptを使ってみよう](../tutorials/javascript/build-apps/get-started.md) | [API リファレンス](https://js.xrpl.org/) | [リポジトリ](https://github.com/XRPLF/xrpl.js) |
+| **Python**                      | `xrpl-py`              | [Pythonを使ってみよう](/docs/tutorials/get-started/get-started-python.md) | [API リファレンス](https://xrpl-py.readthedocs.io/) | [リポジトリ](https://github.com/XRPLF/xrpl-py) |
+| **JavaScript** / **TypeScript** | `xrpl.js`              | [JavaScriptを使ってみよう](/docs/tutorials/get-started/get-started-javascript.md) | [API リファレンス](https://js.xrpl.org/) | [リポジトリ](https://github.com/XRPLF/xrpl.js) |
 | **JavaScript** / **TypeScript** | `xrpl-client`          | [触ってみる](https://jsfiddle.net/WietseWind/35az6p1b/) |  [NPM リファレンス](https://www.npmjs.com/package/xrpl-client) | [リポジトリ](https://github.com/XRPL-Labs/xrpl-client) |
 | **JavaScript** / **TypeScript** | `xrpl-accountlib`      | [触ってみる](https://jsfiddle.net/WietseWind/gkefpnu0/) |  [NPM リファレンス](https://www.npmjs.com/package/xrpl-accountlib) | [リポジトリ](https://github.com/WietseWind/xrpl-accountlib) |
 | **C++**                         | `rippled` 署名ライブラリ | [署名ライブラリを使ってみよう](https://github.com/XRPLF/rippled/tree/develop/Builds/linux#signing-library) | | ([`rippled`](https://github.com/XRPLF/rippled/))の一部 |
-| **Java**                        | `xrpl4j`               | [Javaを使ってみよう](../tutorials/java/build-apps/get-started.md) | [API リファレンス](https://javadoc.io/doc/org.xrpl/) | [リポジトリ](https://github.com/XRPLF/xrpl4j) |
-| **PHP**                         | `XRPL_PHP`             | [PHPを使ってみよう](../tutorials/php/build-apps/get-started.md) | [XRPL_PHP ドキュメント](https://alexanderbuzz.github.io/xrpl-php-docs/) | [リポジトリ](https://github.com/AlexanderBuzz/xrpl-php) |
+| **Java**                        | `xrpl4j`               | [Javaを使ってみよう](/docs/tutorials/get-started/get-started-java.md) | [API リファレンス](https://javadoc.io/doc/org.xrpl/) | [リポジトリ](https://github.com/XRPLF/xrpl4j) |
+| **PHP**                         | `XRPL_PHP`             | [PHPを使ってみよう](/docs/tutorials/get-started/get-started-php.md) | [XRPL_PHP ドキュメント](https://alexanderbuzz.github.io/xrpl-php-docs/) | [リポジトリ](https://github.com/AlexanderBuzz/xrpl-php) |

@l10n/ja/docs/references/data-api.md

@@ -14,6 +14,6 @@ nav_omit: true
 
 ## Alternatives
 
-アカウント残高や取引履歴のリクエストなど、ほとんどの一般的な操作では、[WebSocket接続](../tutorials/http-websocket-apis/get-started.md#websocket-api)または[JSON-RPC（HTTP POST）](../tutorials/http-websocket-apis/build-apps/get-started.md#json-rpc)を使用して、セルフホストまたは[公開XRP Ledgerサーバ](../tutorials/public-servers.md)にリクエストすることとができます。
+アカウント残高や取引履歴のリクエストなど、ほとんどの一般的な操作では、[WebSocket接続](/docs/tutorials/get-started/get-started-http-websocket-apis.md#websocket-api)または[JSON-RPC（HTTP POST）](/docs/tutorials/get-started/get-started-http-websocket-apis.md#json-rpc)を使用して、セルフホストまたは[公開XRP Ledgerサーバ](../tutorials/public-servers.md)にリクエストすることとができます。
 
-詳細については、[HTTP / WebSocket APIsの使用を開始する](../tutorials/http-websocket-apis/build-apps/get-started.md)ページをご覧ください。
+詳細については、[HTTP / WebSocket APIsの使用を開始する](/docs/tutorials/get-started/get-started-http-websocket-apis.md)ページをご覧ください。

@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/index.md

@@ -10,7 +10,7 @@ labels:
 
 `rippled`サーバと直接通信する際には管理APIメソッドを使用します。管理メソッドは、信頼できるサーバ運用担当者のみを対象としています。管理メソッドには、サーバの管理、監視、デバッグのためのコマンドが含まれています。
 
-管理コマンドを使用できるのは、管理者として、`rippled.cfg`ファイルに指定されているホストとポートで`rippled`サーバに接続している場合に限られます。デフォルトでは、コマンドラインクライアントが管理接続を使用します。`rippled`への接続についての詳細は、[rippled API入門](../../../tutorials/http-websocket-apis/build-apps/get-started.md)をご覧ください。
+管理コマンドを使用できるのは、管理者として、`rippled.cfg`ファイルに指定されているホストとポートで`rippled`サーバに接続している場合に限られます。デフォルトでは、コマンドラインクライアントが管理接続を使用します。`rippled`への接続についての詳細は、[rippled API入門](/docs/tutorials/get-started/get-started-http-websocket-apis.md)をご覧ください。
 
 
 ## [キー生成メソッド](key-generation-methods/index.md)

@l10n/ja/docs/references/http-websocket-apis/api-conventions/rate-limiting.md

@@ -10,7 +10,7 @@ labels:
 
 `rippled`サーバはAPIクライアントが公開APIにリクエストできるレートを制限できます。レート制限はクライアントのIPアドレスに基づいて行われるため、[ネットワークアドレス変換](https://ja.wikipedia.org/wiki/ネットワークアドレス変換)の背後にいるクライアントは公開IPアドレスに基づく制限を共有します。
 
-{% admonition type="success" name="ヒント" %}レート制限は、クライアントが[管理者](../../../tutorials/http-websocket-apis/build-apps/get-started.md#管理者アクセス権限)として接続されているときには適用されません{% /admonition %}
+{% admonition type="success" name="ヒント" %}レート制限は、クライアントが[管理者](/docs/tutorials/get-started/get-started-http-websocket-apis.md#管理者アクセス権限)として接続されているときには適用されません{% /admonition %}
 
 クライアントがレート制限に近づいている場合、サーバは[APIレスポンス](response-formatting.md)のトップレベルにフィールド`"warning"： "load"`というフィールドを[APIレスポンス](response-formatting.md)のトップレベルに追加します。この警告はすべてのレスポンスに追加されるわけではありませんが、サーバはクライアントを切断する前に何度かこのような警告を送ることがあります。
 
@@ -58,7 +58,7 @@ Server is overloaded
     - [`rippled`サーバ](../../../concepts/networks-and-servers/index.md)
     - [ソフトウェアエコシステム](../../../introduction/software-ecosystem.md)
 - **チュートリアル:**
-    - [XRP Ledger APIの使用開始](../../../tutorials/http-websocket-apis/build-apps/get-started.md)
+    - [XRP Ledger APIの使用開始](/docs/tutorials/get-started/get-started-http-websocket-apis.md)
     - [rippledのトラブルシューティング](../../../infrastructure/troubleshooting/index.md)
 - **リファレンス:**
     - [rippled APIリファレンス](../index.md)

@l10n/ja/docs/references/http-websocket-apis/api-conventions/response-formatting.md

@@ -130,7 +130,7 @@ HTTP Status: 200 OK
 
 この警告は、XRP Ledgerプロトコルの1つ以上の[Amendment](../../../concepts/networks-and-servers/amendments.md)が有効になる予定であるが、現在のサーバにはそれらのAmendmentの実装がないことを示しています。これらのAmendmentが有効になると、現在のサーバは[Amendmentブロック](../../../concepts/networks-and-servers/amendments.md#amendment-blocked-servers)されるため、できるだけ早く[最新の`rippled`バージョンにアップグレード](../../../infrastructure/installation/index.md)する必要があります。
 
-サーバは、この警告を送信するのは、クライアントが[管理者として接続している](../../../tutorials/http-websocket-apis/build-apps/get-started.md#admin-access)場合のみです。
+サーバは、この警告を送信するのは、クライアントが[管理者として接続している](/docs/tutorials/get-started/get-started-http-websocket-apis.md#admin-access)場合のみです。
 
 この警告には、以下のフィールドを含む`details`フィールドが含まれます。
 
@@ -189,7 +189,7 @@ HTTP Status: 200 OK
     - [Amendment](../../../concepts/networks-and-servers/amendments.md)
         - [既知のAmendment](/resources/known-amendments.md)
 - **チュートリアル:**
-    - [XRP LedgerのAPIを触ってみよう](../../../tutorials/http-websocket-apis/build-apps/get-started.md)
+    - [XRP LedgerのAPIを触ってみよう](/docs/tutorials/get-started/get-started-http-websocket-apis.md)
     - [`rippled`のインストールと更新](../../../infrastructure/installation/index.md)
 - **リファレンス:**
     - [featureメソッド][]

@l10n/ja/docs/tutorials/how-tos/manage-account-settings/use-tickets.md

@@ -20,7 +20,7 @@ steps: ['Generate', 'Connect', 'Check Sequence', 'Prepare & Sign', 'Submit', 'Wa
 <script type="application/javascript" src="/js/interactive-tutorial.js"></script>
 <script type="application/javascript" src="/js/tutorials/use-tickets.js"></script>
 
-このページでは、[xrpl.js](https://js.xrpl.org/)ライブラリを使用したJavaScriptのサンプルを提供しています。設定方法は、[JavaScriptを使ってみよう](../../javascript/build-apps/get-started.md)をご覧ください。
+このページでは、[xrpl.js](https://js.xrpl.org/)ライブラリを使用したJavaScriptのサンプルを提供しています。設定方法は、[JavaScriptを使ってみよう](/docs/tutorials/get-started/get-started-javascript.md)をご覧ください。
 
 JavaScriptはWebブラウザ上で動作するため、セットアップなしで読み進められ、インタラクティブな手順を利用することができます。
 

@l10n/ja/docs/tutorials/how-tos/send-xrp.md

@@ -23,7 +23,7 @@ steps: ['Generate', 'Connect', 'Prepare', 'Sign', 'Submit', 'Wait', 'Check']
 <script type="application/javascript" src="/js/interactive-tutorial.js"></script>
 <script type="application/javascript" src="/js/tutorials/send-xrp.js"></script>
 
-- このページでは、xrpl.jsライブラリーを使用するJavaScriptの例を紹介します。[xrpl.js入門ガイド](../javascript/build-apps/get-started.md)に、xrpl.jsを使用してJavaScriptからXRP Ledgerデータにアクセスする方法の説明があります。
+- このページでは、xrpl.jsライブラリーを使用するJavaScriptの例を紹介します。[xrpl.js入門ガイド](/docs/tutorials/get-started/get-started-javascript.md)に、xrpl.jsを使用してJavaScriptからXRP Ledgerデータにアクセスする方法の説明があります。
 
 - XRP Ledgerでトランザクションを送信するには、まずアドレスと秘密鍵、そしていくらかのXRPが必要となります。次のインターフェイスを使用して、XRP Test NetにあるアドレスとTestnet XRPを入手できます。
 

@l10n/ja/docs/tutorials/public-servers.md

@@ -26,7 +26,6 @@ labels:
 | Ripple[¹][]    | Testnet (Clio)   | `https://clio.altnet.rippletest.net:51234/` | `wss://clio.altnet.rippletest.net:51233/` | Clioを使用したTestnet公開サーバ |
 | Ripple[¹][]    | Devnet           | `https://s.devnet.rippletest.net:51234/` | `wss://s.devnet.rippletest.net:51233/` | Devnet 公開サーバ |
 | Ripple[¹][]    | Devnet (Clio)    | `https://clio.devnet.rippletest.net:51234/` | `wss://clio.devnet.rippletest.net:51233/` | Clioを使用したDevnet公開サーバ |
-| Ripple[¹][]    | Sidechain-Devnet | `https://sidechain-net2.devnet.rippletest.net:51234/` | `wss://sidechain-net2.devnet.rippletest.net:51233/` | クロスチェーンブリッジ機能をテストするためのサイドチェーンDevnet。Devnetはロックチェーンとして機能し、このサイドチェーンは発行チェーンとして機能します。 |
 | XRPL Labs      | Xahau Testnet     | `https://xahau-test.net/` | `wss://xahau-test.net/` | [Hooksが有効](https://hooks.xrpl.org/)なXahau Testnet |
 
 [ネットワーク]: ../concepts/networks-and-servers/parallel-networks.md

@l10n/ja/docs/use-cases/defi/algorithmic-trading.md

@@ -72,7 +72,7 @@ XRP Ledgerの分散型取引所(DEX)には、「アルゴリズムトレード
 
 ### トレードの発注
 
-XRP Ledgerの分散型取引所で _代替可能_ トークンとXRPを売買するには、通常[OfferCreateトランザクション](../../references/protocol/transactions/types/offercreate.md)を送信します。この方法でトレードを行うためのコードと技術的ステップの詳細なウォークスルーについては、[分散型取引所でのトレード](../../tutorials/how-tos/use-tokens/trade-in-the-decentralized-exchange.md)をご覧ください。[Paymentトランザクション](../../references/protocol/transactions/types/payment.md)を使用して通貨を両替することも可能です。[クロスカレンしー支払い](../../concepts/payment-types/cross-currency-payments.md)を他のユーザに送ったり、長い[パス](../../concepts/tokens/fungible-tokens/paths.md)を使って裁定取引の機会を1つの操作にまとめることで、自分自身に送り返すこともできます。
+XRP Ledgerの分散型取引所で _代替可能_ トークンとXRPを売買するには、通常[OfferCreateトランザクション](../../references/protocol/transactions/types/offercreate.md)を送信します。この方法でトレードを行うためのコードと技術的ステップの詳細なウォークスルーについては、[分散型取引所でのトレード](/docs/tutorials/dex/trade-in-the-decentralized-exchange.md)をご覧ください。[Paymentトランザクション](../../references/protocol/transactions/types/payment.md)を使用して通貨を両替することも可能です。[クロスカレンしー支払い](../../concepts/payment-types/cross-currency-payments.md)を他のユーザに送ったり、長い[パス](../../concepts/tokens/fungible-tokens/paths.md)を使って裁定取引の機会を1つの操作にまとめることで、自分自身に送り返すこともできます。
 
 NFTをトレードするためのコードと技術的な手順については、[JavaScriptを使用したNFTokenの送信](../../tutorials/javascript/nfts/transfer-nfts.md)をご覧ください。
 
@@ -89,7 +89,7 @@ XRP Ledgerのトレード活動に関する情報源は数多くあります。
 XRP Ledgerは既存の中央指値注文ベース(CLOB)の分散型取引所と連携するネイティブな自動マーケットメーカー(AMM)の機能をネイティブサポートしています。AMMはXRP Ledger上のトレードにおいて重要な要素となっています。詳しくは以下のリンクをご覧ください。
 
 - [自動マーケットメーカー](../../concepts/tokens/decentralized-exchange/automated-market-makers.md)
-- [AMMのオークションスロットを利用して低い取引手数料でトレードする](../../tutorials/javascript/amm/add-assets-to-amm.md)
+- [AMMのオークションスロットを利用して低い取引手数料でトレードする](/docs/tutorials/dex/add-assets-to-amm-in-javascript.md)
 - [XLS-30 標準規格](https://github.com/XRPLF/XRPL-Standards/tree/master/XLS-0030-automated-market-maker#readme)
 
 ## さらに詳しく

@l10n/ja/docs/use-cases/tokenization/authorized-minter.md

@@ -67,7 +67,7 @@ NFTをオークション形式で販売することができます。[NFTオー
 
 XRPL NFTの最もシンプルな支払い方法はXRPです。XRPを使ったNFTの売り買いの例については、[NFTokenの取引](../../tutorials/javascript/nfts/transfer-nfts.md)をご覧ください。
 
-他の通貨での取引は、DEXを活用してあらゆる種類の発行通貨を受け入れ、取引することができます。[分散型取引所での取引](../../tutorials/how-tos/use-tokens/trade-in-the-decentralized-exchange.md#trade-in-the-decentralized-exchange)をご覧ください。
+他の通貨での取引は、DEXを活用してあらゆる種類の発行通貨を受け入れ、取引することができます。[分散型取引所での取引](/docs/tutorials/dex/trade-in-the-decentralized-exchange.md#trade-in-the-decentralized-exchange)をご覧ください。
 
 ## NFTのインデックス
 

@l10n/ja/docs/use-cases/tokenization/digital-artist.md

@@ -64,7 +64,7 @@ NFTをオークション形式で販売することができます。[NFTオー
 
 XRPL NFTの最もシンプルな支払い方法はXRPです。XRPを使ったNFTの売り買いの例については、[NFTokenの取引](../../tutorials/javascript/nfts/transfer-nfts.md))をご覧ください。
 
-他の通貨での取引は、DEXを活用してあらゆる種類の発行通貨を受け入れ、取引することができます。[分散型取引所での取引](../../tutorials/how-tos/use-tokens/trade-in-the-decentralized-exchange.md#trade-in-the-decentralized-exchange)をご覧ください。
+他の通貨での取引は、DEXを活用してあらゆる種類の発行通貨を受け入れ、取引することができます。[分散型取引所での取引](/docs/tutorials/dex/trade-in-the-decentralized-exchange.md#trade-in-the-decentralized-exchange)をご覧ください。
 
 ## NFTのインデックス化
 

@l10n/ja/docs/use-cases/tokenization/nft-mkt-overview.md

@@ -105,7 +105,7 @@ NFTをオークション形式で販売することができます。[NFTオー
 
 XRPL NFTの最もシンプルな支払い方法はXRPです。XRPを使ったNFTの売り買いの例については、[NFTokenの取引](../../tutorials/javascript/nfts/transfer-nfts.md)をご覧ください。
 
-他の通貨での取引は、DEXを活用してあらゆる種類の発行通貨を受け入れ、取引することができます。[分散型取引所での取引](../../tutorials/how-tos/use-tokens/trade-in-the-decentralized-exchange.md#trade-in-the-decentralized-exchange)をご覧ください。
+他の通貨での取引は、DEXを活用してあらゆる種類の発行通貨を受け入れ、取引することができます。[分散型取引所での取引](/docs/tutorials/dex/trade-in-the-decentralized-exchange.md#trade-in-the-decentralized-exchange)をご覧ください。
 
 <!--
 

@l10n/ja/docs/use-cases/tokenization/nftoken-marketplace.md

@@ -67,7 +67,7 @@ NFTをオークション形式で販売することができます。[NFTオー
 
 XRPL NFTの最もシンプルな支払い方法はXRPです。XRPを使ったNFTの売り買いの例については、[NFTokenの取引](../../tutorials/javascript/nfts/transfer-nfts.md)をご覧ください。
 
-他の通貨での取引は、DEXを活用してあらゆる種類の発行通貨を受け入れ、取引することができます。[分散型取引所での取引](../../tutorials/how-tos/use-tokens/trade-in-the-decentralized-exchange.md#trade-in-the-decentralized-exchange)をご覧ください。
+他の通貨での取引は、DEXを活用してあらゆる種類の発行通貨を受け入れ、取引することができます。[分散型取引所での取引](/docs/tutorials/dex/trade-in-the-decentralized-exchange.md#trade-in-the-decentralized-exchange)をご覧ください。
 
 ## NFTのインデックス化
 

@theme/components/Amendments.tsx

@@ -326,7 +326,7 @@ export function AmendmentDisclaimer(props: {
           ) : (
             <>
             {translate("component.amendment-status.updates.1", "The ")}{link()}
-            {translate("component.amendment-status.updates.2", "updates this.")}
+            {translate("component.amendment-status.updates.2", " updates this.")}
             {" "}
             <AmendmentBadge amendment={amendmentStatus} />
             </>

@theme/plugins/blog-posts.js

@@ -1,6 +1,6 @@
 // @ts-check
 
-import { getInnerText } from '@redocly/realm/dist/shared/markdoc.js';
+import { getInnerText } from '@redocly/realm/dist/server/plugins/markdown/markdoc/helpers/get-inner-text.js';
 
 import { dirname, relative, join as joinPath } from 'path';
 import markdoc from '@markdoc/markdoc';
@@ -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

@@ -1,6 +1,6 @@
 // @ts-check
 
-import { getInnerText } from '@redocly/realm/dist/shared/markdoc.js';
+import { getInnerText } from '@redocly/realm/dist/server/plugins/markdown/markdoc/helpers/get-inner-text.js';
 
 import { dirname, relative, join as joinPath } from 'path';
 
@@ -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);
       }

_api-examples/path_find/create-followup.json

@@ -0,0 +1,15 @@
+{
+  "alternatives": [
+    // ... paths omitted from this example; same format as the initial response ...
+  ],
+  "destination_account": "r9cZA1mLK5R5Am25ArfXFmqgNwjZgnfk59",
+  "destination_amount": {
+    "currency": "USD",
+    "issuer": "rvYAfWj5gh67oV6fW32ZzP3Aw4Eubs59B",
+    "value": "0.001"
+  },
+  "full_reply": true,
+  "id": 8,
+  "source_account": "r9cZA1mLK5R5Am25ArfXFmqgNwjZgnfk59",
+  "type": "path_find"
+}

_api-examples/path_find/create-response.json

@@ -0,0 +1,75 @@
+{
+  "id": 8,
+  "result": {
+    "alternatives": [
+      {
+        "paths_computed": [
+          [
+            {
+              "currency": "USD",
+              "issuer": "rKiCet8SdvWxPXnAgYarFUXMh1zCPz432Y",
+              "type": 48
+            },
+            {
+              "account": "rKiCet8SdvWxPXnAgYarFUXMh1zCPz432Y",
+              "type": 1
+            },
+            {
+              "account": "rLzpfEnrB2Ro2LtaGd6Af7znRqGxULc4rW",
+              "type": 1
+            }
+          ],
+          [
+            {
+              "currency": "USD",
+              "issuer": "rKiCet8SdvWxPXnAgYarFUXMh1zCPz432Y",
+              "type": 48
+            },
+            {
+              "account": "rKiCet8SdvWxPXnAgYarFUXMh1zCPz432Y",
+              "type": 1
+            },
+            {
+              "account": "rQhbp2h133vD3TJGWkNY5zePHKQUq6vSVm",
+              "type": 1
+            }
+          ],
+          [
+            {
+              "currency": "USD",
+              "issuer": "rvYAfWj5gh67oV6fW32ZzP3Aw4Eubs59B",
+              "type": 48
+            }
+          ],
+          [
+            {
+              "currency": "USD",
+              "issuer": "rhub8VRN55s94qWKDv6jmDy1pUykJzF3wq",
+              "type": 48
+            },
+            {
+              "account": "rhub8VRN55s94qWKDv6jmDy1pUykJzF3wq",
+              "type": 1
+            },
+            {
+              "account": "r4cjaKtZqP2GDjwK3eT9qua4Hqk9Zk2kSy",
+              "type": 1
+            }
+          ]
+        ],
+        "source_amount": "390"
+      }
+    ],
+    "destination_account": "r9cZA1mLK5R5Am25ArfXFmqgNwjZgnfk59",
+    "destination_amount": {
+      "currency": "USD",
+      "issuer": "rvYAfWj5gh67oV6fW32ZzP3Aw4Eubs59B",
+      "value": "0.001"
+    },
+    "full_reply": false,
+    "id": 8,
+    "source_account": "r9cZA1mLK5R5Am25ArfXFmqgNwjZgnfk59"
+  },
+  "status": "success",
+  "type": "response"
+}

_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/build-a-desktop-wallet/js/0-hello/index.js

@@ -3,20 +3,19 @@ const { app, BrowserWindow } = require('electron')
 const path = require('path')
 
 /**
- * This is our main function, it creates our application window, preloads the code we will need to communicate
- * between the renderer Process and the main Process, loads a layout and performs the main logic
+ * Main function: create application window, preload the code to communicate
+ * between the renderer Process and the main Process, load a layout,
+ * and perform the main logic.
  */
 const createWindow = () => {
-
-    // Creates the application window
+    // Create the application window
     const appWindow = new BrowserWindow({
         width: 1024,
         height: 768
     })
 
-    // Loads a layout
+    // Load a layout
     appWindow.loadFile(path.join(__dirname, 'view', 'template.html'))
-
     return appWindow
 }
 

_code-samples/build-a-desktop-wallet/js/1-ledger-index/index.js

@@ -1,40 +1,37 @@
 const { app, BrowserWindow } = require('electron')
 
 const path = require('path')
-const xrpl = require("xrpl")
+// Ledger index code additions - start
+const xrpl = require('xrpl')
 
-const TESTNET_URL = "wss://s.altnet.rippletest.net:51233"
+const TESTNET_URL = 'wss://s.altnet.rippletest.net:51233'
 
 /**
- * This function creates a WebService client, which connects to the XRPL and fetches the latest ledger index.
+ * Create a WebSocket client, connect to the XRPL, and fetch the latest ledger index.
  *
  * @returns {Promise<number>}
  */
 const getValidatedLedgerIndex = async () => {
     const client = new xrpl.Client(TESTNET_URL)
-
     await client.connect()
-
-    // Reference: https://xrpl.org/ledger.html#ledger
+    // Reference: https://xrpl.org/docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger
     const ledgerRequest = {
         "command": "ledger",
         "ledger_index": "validated"
     }
-
     const ledgerResponse = await client.request(ledgerRequest)
-
     await client.disconnect()
-
     return ledgerResponse.result.ledger_index
 }
+// Ledger index code additions - end
 
 /**
- * This is our main function, it creates our application window, preloads the code we will need to communicate
- * between the renderer Process and the main Process, loads a layout and performs the main logic
+ * Main function: create application window, preload the code to communicate
+ * between the renderer Process and the main Process, load a layout,
+ * and perform the main logic.
  */
 const createWindow = () => {
-
-    // Creates the application window
+    // Create the application window
     const appWindow = new BrowserWindow({
         width: 1024,
         height: 768,
@@ -43,9 +40,8 @@ const createWindow = () => {
         },
     })
 
-    // Loads a layout
+    // Load a layout
     appWindow.loadFile(path.join(__dirname, 'view', 'template.html'))
-
     return appWindow
 }
 

_code-samples/build-a-desktop-wallet/js/2-async/index.js

@@ -24,9 +24,10 @@ const createWindow = () => {
     return appWindow
 }
 
+// Step 2 changes - main whenReady function - start
 /**
- * This function creates a XRPL client, subscribes to 'ledger' events from the XRPL and broadcasts those by
- * dispatching the 'update-ledger-data' event which will be picked up by the frontend
+ * Create an XRPL client, subscribe to 'ledger' events, and broadcast those by
+ * dispatching an 'update-ledger-data' event to the frontend.
  *
  * @returns {Promise<void>}
  */
@@ -38,7 +39,7 @@ const main = async () => {
     await client.connect()
 
     // Subscribe client to 'ledger' events
-    // Reference: https://xrpl.org/subscribe.html
+    // Reference: https://xrpl.org/docs/references/http-websocket-apis/public-api-methods/subscription-methods/subscribe
     await client.request({
         "command": "subscribe",
         "streams": ["ledger"]
@@ -51,3 +52,4 @@ const main = async () => {
 }
 
 app.whenReady().then(main)
+// Step 2 changes - main whenReady function - end

_code-samples/build-a-desktop-wallet/js/3-account/index.js

@@ -29,30 +29,30 @@ const main = async () => {
 
         await client.connect()
 
-        // Reference: https://xrpl.org/subscribe.html
+        // Reference: https://xrpl.org/docs/references/http-websocket-apis/public-api-methods/subscription-methods/subscribe
         await client.request({
             "command": "subscribe",
             "streams": ["ledger"],
             "accounts": [address]
         })
 
-        // Reference: https://xrpl.org/subscribe.html#ledger-stream
+        // Reference: https://xrpl.org/docs/references/http-websocket-apis/public-api-methods/subscription-methods/subscribe#ledger-stream
         client.on("ledgerClosed", async (rawLedgerData) => {
             const ledger = prepareLedgerData(rawLedgerData)
             appWindow.webContents.send('update-ledger-data', ledger)
         })
 
         // Initial Ledger Request -> Get account details on startup
-        // Reference: https://xrpl.org/ledger.html
+        // Reference: https://xrpl.org/docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger
         const ledgerResponse = await client.request({
             "command": "ledger"
         })
         const initialLedgerData = prepareLedgerData(ledgerResponse.result.closed.ledger)
         appWindow.webContents.send('update-ledger-data', initialLedgerData)
 
-        // Reference: https://xrpl.org/subscribe.html#transaction-streams
+        // Reference: https://xrpl.org/docs/references/http-websocket-apis/public-api-methods/subscription-methods/subscribe#transaction-streams
         client.on("transaction", async (transaction) => {
-            // Reference: https://xrpl.org/account_info.html
+            // Reference: https://xrpl.org/docs/references/http-websocket-apis/public-api-methods/account-methods/account_info
             const accountInfoRequest = {
                 "command": "account_info",
                 "account": address,
@@ -64,7 +64,7 @@ const main = async () => {
         })
 
         // Initial Account Request -> Get account details on startup
-        // Reference: https://xrpl.org/account_info.html
+        // Reference: https://xrpl.org/docs/references/http-websocket-apis/public-api-methods/account-methods/account_info
         const accountInfoResponse = await client.request({
             "command": "account_info",
             "account": address,

_code-samples/build-a-desktop-wallet/js/4-tx-history/index.js

@@ -30,14 +30,14 @@ const main = async () => {
 
         await client.connect()
 
-        // Reference: https://xrpl.org/subscribe.html
+        // Reference: https://xrpl.org/docs/references/http-websocket-apis/public-api-methods/subscription-methods/subscribe
         await client.request({
             "command": "subscribe",
             "streams": ["ledger"],
             "accounts": [address]
         })
 
-        // Reference: https://xrpl.org/subscribe.html#ledger-stream
+        // Reference: https://xrpl.org/docs/references/http-websocket-apis/public-api-methods/subscription-methods/subscribe#ledger-stream
         client.on("ledgerClosed", async (rawLedgerData) => {
             const ledger = prepareLedgerData(rawLedgerData)
             appWindow.webContents.send('update-ledger-data', ledger)
@@ -45,7 +45,7 @@ const main = async () => {
 
         // Wait for transaction on subscribed account and re-request account data
         client.on("transaction", async (transaction) => {
-            // Reference: https://xrpl.org/account_info.html
+            // Reference: https://xrpl.org/docs/references/http-websocket-apis/public-api-methods/account-methods/account_info
             const accountInfoRequest = {
                 "command": "account_info",
                 "account": address,
@@ -61,7 +61,7 @@ const main = async () => {
         })
 
         // Initial Account Request -> Get account details on startup
-        // Reference: https://xrpl.org/account_info.html
+        // Reference: https://xrpl.org/docs/references/http-websocket-apis/public-api-methods/account-methods/account_info
         const accountInfoResponse = await client.request({
             "command": "account_info",
             "account": address,
@@ -71,7 +71,7 @@ const main = async () => {
         appWindow.webContents.send('update-account-data', accountData)
 
         // Initial Transaction Request -> List account transactions on startup
-        // Reference: https://xrpl.org/account_tx.html
+        // Reference: https://xrpl.org/docs/references/http-websocket-apis/public-api-methods/account-methods/account_tx
         const txResponse = await client.request({
             "command": "account_tx",
             "account": address

_code-samples/build-a-desktop-wallet/js/5-password/index.js

@@ -23,6 +23,7 @@ const createWindow = () => {
     return appWindow
 }
 
+// Step 5 - new main function - start
 const main = async () => {
     const appWindow = createWindow()
 
@@ -51,6 +52,9 @@ const main = async () => {
         }
 
         const wallet = xrpl.Wallet.fromSeed(seed)
+        // For compatibility with seeds generated using secp256k1
+        // (the old default algorithm), use the following instead:
+        // const wallet = xrpl.Wallet.fromSeed(seed, {algorithm: "secp256k1"})
 
         const client = new xrpl.Client(TESTNET_URL)
 
@@ -80,5 +84,6 @@ const main = async () => {
         }
     })
 }
+// Step 5 - new main function - end
 
 app.whenReady().then(main)

_code-samples/build-a-desktop-wallet/js/README.md

@@ -2,7 +2,7 @@
 
 Build a non-custodial XRP Ledger wallet application in JavaScript that runs on the desktop using Electron.
 
-For the full documentation, refer to the [Build a Wallet in JavaScript tutorial](https://xrpl.org/build-a-wallet-in-javascript.html).
+For the full documentation, refer to the [Build a Desktop Wallet in JavaScript tutorial](https://xrpl.org/docs/tutorials/javascript/build-apps/build-a-desktop-wallet-in-javascript).
 
 ## TL;DR
 

_code-samples/build-a-desktop-wallet/js/library/3_helpers.js

@@ -3,7 +3,7 @@ const xrpl = require("xrpl");
 // The rippled server and its APIs represent time as an unsigned integer.
 // This number measures the number of seconds since the "Ripple Epoch" of
 // January 1, 2000 (00:00 UTC). This is like the way the Unix epoch  works,
-// Reference: https://xrpl.org/basic-data-types.html
+// Reference: https://xrpl.org/docs/references/protocol/data-types/basic-data-types#specifying-time
 const RIPPLE_EPOCH = 946684800;
 
 const prepareAccountData = (rawAccountData) => {

_code-samples/build-a-desktop-wallet/js/library/5_helpers.js

@@ -14,7 +14,7 @@ const fernet = require("fernet");
  * @returns {Promise<void>}
  */
 const initialize = async (client, wallet, appWindow) => {
-    // Reference: https://xrpl.org/account_info.html
+    // Reference: https://xrpl.org/docs/references/http-websocket-apis/public-api-methods/account-methods/account_info
     const accountInfoResponse = await client.request({
         "command": "account_info",
         "account": wallet.address,
@@ -23,7 +23,7 @@ const initialize = async (client, wallet, appWindow) => {
     const accountData = prepareAccountData(accountInfoResponse.result.account_data)
     appWindow.webContents.send('update-account-data', accountData)
 
-    // Reference: https://xrpl.org/account_tx.html
+    // Reference: https://xrpl.org/docs/references/http-websocket-apis/public-api-methods/account-methods/account_tx
     const txResponse = await client.request({
         "command": "account_tx",
         "account": wallet.address
@@ -42,14 +42,14 @@ const initialize = async (client, wallet, appWindow) => {
  */
 const subscribe = async (client, wallet, appWindow) => {
 
-    // Reference: https://xrpl.org/subscribe.html
+    // Reference: https://xrpl.org/docs/references/http-websocket-apis/public-api-methods/subscription-methods/subscribe
     await client.request({
         "command": "subscribe",
         "streams": ["ledger"],
         "accounts": [wallet.address]
     })
 
-    // Reference: https://xrpl.org/subscribe.html#ledger-stream
+    // Reference: https://xrpl.org/docs/references/http-websocket-apis/public-api-methods/subscription-methods/subscribe#ledger-stream
     client.on("ledgerClosed", async (rawLedgerData) => {
         const ledger = prepareLedgerData(rawLedgerData)
         appWindow.webContents.send('update-ledger-data', ledger)
@@ -57,7 +57,7 @@ const subscribe = async (client, wallet, appWindow) => {
 
     // Wait for transaction on subscribed account and re-request account data
     client.on("transaction", async (transaction) => {
-        // Reference: https://xrpl.org/account_info.html
+        // Reference: https://xrpl.org/docs/references/http-websocket-apis/public-api-methods/account-methods/account_info
         const accountInfoRequest = {
             "command": "account_info",
             "account": wallet.address,

_code-samples/build-a-desktop-wallet/js/library/7_helpers.js

@@ -9,7 +9,7 @@ const xrpl = require("xrpl");
  * @returns {Promise<*>}
  */
 const sendXrp = async (paymentData, client, wallet) => {
-    // Reference: https://xrpl.org/submit.html#request-format-1
+    // Reference: https://xrpl.org/docs/references/protocol/transactions/types/payment
     const paymentTx = {
         "TransactionType": "Payment",
         "Account": wallet.address,

_code-samples/build-a-desktop-wallet/js/library/8_helpers.js

@@ -39,7 +39,7 @@ async function checkDestination(accountData) {
 
 /**
  * Verify an account using a xrp-ledger.toml file.
- * https://xrpl.org/xrp-ledger-toml.html#xrp-ledgertoml-file
+ * https://xrpl.org/docs/references/xrp-ledger-toml
  *
  * @param accountData
  * @returns {Promise<{domain: string, verified: boolean}>}
@@ -89,7 +89,7 @@ async function verifyAccountDomain(accountData) {
  * @returns {Promise<{domain: string, verified: boolean}>}
  */
 async function verify(accountAddress, client) {
-    // Reference: https://xrpl.org/account_info.html
+    // Reference: https://xrpl.org/docs/references/http-websocket-apis/public-api-methods/account-methods/account_info
     const request = {
         "command": "account_info",
         "account": accountAddress,

_code-samples/build-a-desktop-wallet/js/package.json

@@ -1,6 +1,6 @@
 {
   "name": "xrpl-javascript-desktop-wallet",
-  "version": "1.0.0",
+  "version": "1.1.0",
   "license": "MIT",
   "scripts": {
     "hello": "electron 0-hello/index.js",
@@ -14,15 +14,15 @@
     "domain-verification": "electron 8-domain-verification/index.js"
   },
   "dependencies": {
-    "async": "^3.2.4",
+    "async": "^3.2.6",
     "fernet": "=0.3.3",
-    "node-fetch": "^2.6.9",
-    "pbkdf2-hmac": "^1.1.0",
+    "node-fetch": "^2.7.0",
+    "pbkdf2-hmac": "^1.2.1",
     "open": "^8.4.0",
     "toml": "^3.0.0",
-    "xrpl": "^4.3.0"
+    "xrpl": "^4.4.2"
   },
   "devDependencies": {
-    "electron": "28.3.2"
+    "electron": "38.2.0"
   }
 }

_code-samples/clawback/go/go.mod

@@ -1,8 +1,6 @@
 module github.com/XRPLF
 
-go 1.23.0
-
-toolchain go1.23.10
+go 1.24.0
 
 require github.com/Peersyst/xrpl-go v0.1.11
 
@@ -20,5 +18,5 @@ require (
 	github.com/tyler-smith/go-bip32 v1.0.0 // indirect
 	github.com/tyler-smith/go-bip39 v1.1.0 // indirect
 	github.com/ugorji/go/codec v1.2.11 // indirect
-	golang.org/x/crypto v0.35.0 // indirect
+	golang.org/x/crypto v0.45.0 // indirect
 )

_code-samples/clawback/go/go.sum

@@ -46,8 +46,8 @@ github.com/ugorji/go/codec v1.2.11/go.mod h1:UNopzCgEMSXjBc6AOMqYvWC1ktqTAfzJZUZ
 golang.org/x/crypto v0.0.0-20170613210332-850760c427c5/go.mod h1:6SG95UA2DQfeDnfUPMdvaQW0Q7yPrPDi9nlGo2tz2b4=
 golang.org/x/crypto v0.0.0-20190308221718-c2843e01d9a2/go.mod h1:djNgcEr1/C05ACkg1iLfiJU5Ep61QUkGW8qpdssI0+w=
 golang.org/x/crypto v0.0.0-20200622213623-75b288015ac9/go.mod h1:LzIPMQfyMNhhGPhUkYOs5KpL4U8rLKemX1yGLhDgUto=
-golang.org/x/crypto v0.35.0 h1:b15kiHdrGCHrP6LvwaQ3c03kgNhhiMgvlhxHQhmg2Xs=
-golang.org/x/crypto v0.35.0/go.mod h1:dy7dXNW32cAb/6/PRuTNsix8T+vJAqvuIy5Bli/x0YQ=
+golang.org/x/crypto v0.45.0 h1:jMBrvKuj23MTlT0bQEOBcAE0mjg8mK9RXFhRH6nyF3Q=
+golang.org/x/crypto v0.45.0/go.mod h1:XTGrrkGJve7CYK7J8PEww4aY7gM3qMCElcJQ8n8JdX4=
 golang.org/x/net v0.0.0-20190404232315-eb5bcb51f2a3/go.mod h1:t9HGtf8HONx5eT2rtn7q6eTqICYqUVnKs3thJo3Qplg=
 golang.org/x/sys v0.0.0-20190215142949-d0b11bdaac8a/go.mod h1:STP8DvDyc/dI5b8T5hshtkjS+E42TnysNCUPdjciGhY=
 golang.org/x/sys v0.0.0-20190412213103-97732733099d/go.mod h1:h1NjWce9XRLGQEsW7wpKNCjG9DtNlClVuFLEZdDNbEs=

_code-samples/create-amm/README.md

@@ -1,3 +1,3 @@
 # Create AMM
 
-Code samples for the [Create an Automated Market Maker tutorial](../../docs/tutorials/how-tos/use-tokens/create-an-automated-market-maker.md), showing how to make set up a new AMM.
+Code samples for the [Create an Automated Market Maker tutorial](../../docs/tutorials/dex/create-an-automated-market-maker.md), showing how to make set up a new AMM.

_code-samples/deposit-preauth/go/go.mod

@@ -1,8 +1,6 @@
 module github.com/XRPLF
 
-go 1.23.0
-
-toolchain go1.23.10
+go 1.24.0
 
 require github.com/Peersyst/xrpl-go v0.1.11
 
@@ -20,5 +18,5 @@ require (
 	github.com/tyler-smith/go-bip32 v1.0.0 // indirect
 	github.com/tyler-smith/go-bip39 v1.1.0 // indirect
 	github.com/ugorji/go/codec v1.2.11 // indirect
-	golang.org/x/crypto v0.35.0 // indirect
+	golang.org/x/crypto v0.45.0 // indirect
 )

_code-samples/deposit-preauth/go/go.sum

@@ -46,8 +46,8 @@ github.com/ugorji/go/codec v1.2.11/go.mod h1:UNopzCgEMSXjBc6AOMqYvWC1ktqTAfzJZUZ
 golang.org/x/crypto v0.0.0-20170613210332-850760c427c5/go.mod h1:6SG95UA2DQfeDnfUPMdvaQW0Q7yPrPDi9nlGo2tz2b4=
 golang.org/x/crypto v0.0.0-20190308221718-c2843e01d9a2/go.mod h1:djNgcEr1/C05ACkg1iLfiJU5Ep61QUkGW8qpdssI0+w=
 golang.org/x/crypto v0.0.0-20200622213623-75b288015ac9/go.mod h1:LzIPMQfyMNhhGPhUkYOs5KpL4U8rLKemX1yGLhDgUto=
-golang.org/x/crypto v0.35.0 h1:b15kiHdrGCHrP6LvwaQ3c03kgNhhiMgvlhxHQhmg2Xs=
-golang.org/x/crypto v0.35.0/go.mod h1:dy7dXNW32cAb/6/PRuTNsix8T+vJAqvuIy5Bli/x0YQ=
+golang.org/x/crypto v0.45.0 h1:jMBrvKuj23MTlT0bQEOBcAE0mjg8mK9RXFhRH6nyF3Q=
+golang.org/x/crypto v0.45.0/go.mod h1:XTGrrkGJve7CYK7J8PEww4aY7gM3qMCElcJQ8n8JdX4=
 golang.org/x/net v0.0.0-20190404232315-eb5bcb51f2a3/go.mod h1:t9HGtf8HONx5eT2rtn7q6eTqICYqUVnKs3thJo3Qplg=
 golang.org/x/sys v0.0.0-20190215142949-d0b11bdaac8a/go.mod h1:STP8DvDyc/dI5b8T5hshtkjS+E42TnysNCUPdjciGhY=
 golang.org/x/sys v0.0.0-20190412213103-97732733099d/go.mod h1:h1NjWce9XRLGQEsW7wpKNCjG9DtNlClVuFLEZdDNbEs=

_code-samples/get-started/go/go.mod

@@ -1,8 +1,6 @@
 module github.com/XRPLF
 
-go 1.23.0
-
-toolchain go1.23.10
+go 1.24.0
 
 require github.com/Peersyst/xrpl-go v0.1.11
 
@@ -20,5 +18,5 @@ require (
 	github.com/tyler-smith/go-bip32 v1.0.0 // indirect
 	github.com/tyler-smith/go-bip39 v1.1.0 // indirect
 	github.com/ugorji/go/codec v1.2.11 // indirect
-	golang.org/x/crypto v0.35.0 // indirect
+	golang.org/x/crypto v0.45.0 // indirect
 )

_code-samples/get-started/go/go.sum

@@ -46,8 +46,8 @@ github.com/ugorji/go/codec v1.2.11/go.mod h1:UNopzCgEMSXjBc6AOMqYvWC1ktqTAfzJZUZ
 golang.org/x/crypto v0.0.0-20170613210332-850760c427c5/go.mod h1:6SG95UA2DQfeDnfUPMdvaQW0Q7yPrPDi9nlGo2tz2b4=
 golang.org/x/crypto v0.0.0-20190308221718-c2843e01d9a2/go.mod h1:djNgcEr1/C05ACkg1iLfiJU5Ep61QUkGW8qpdssI0+w=
 golang.org/x/crypto v0.0.0-20200622213623-75b288015ac9/go.mod h1:LzIPMQfyMNhhGPhUkYOs5KpL4U8rLKemX1yGLhDgUto=
-golang.org/x/crypto v0.35.0 h1:b15kiHdrGCHrP6LvwaQ3c03kgNhhiMgvlhxHQhmg2Xs=
-golang.org/x/crypto v0.35.0/go.mod h1:dy7dXNW32cAb/6/PRuTNsix8T+vJAqvuIy5Bli/x0YQ=
+golang.org/x/crypto v0.45.0 h1:jMBrvKuj23MTlT0bQEOBcAE0mjg8mK9RXFhRH6nyF3Q=
+golang.org/x/crypto v0.45.0/go.mod h1:XTGrrkGJve7CYK7J8PEww4aY7gM3qMCElcJQ8n8JdX4=
 golang.org/x/net v0.0.0-20190404232315-eb5bcb51f2a3/go.mod h1:t9HGtf8HONx5eT2rtn7q6eTqICYqUVnKs3thJo3Qplg=
 golang.org/x/sys v0.0.0-20190215142949-d0b11bdaac8a/go.mod h1:STP8DvDyc/dI5b8T5hshtkjS+E42TnysNCUPdjciGhY=
 golang.org/x/sys v0.0.0-20190412213103-97732733099d/go.mod h1:h1NjWce9XRLGQEsW7wpKNCjG9DtNlClVuFLEZdDNbEs=

_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

_code-samples/issue-a-token/go/go.mod

@@ -1,8 +1,6 @@
 module github.com/XRPLF
 
-go 1.23.0
-
-toolchain go1.23.10
+go 1.24.0
 
 require github.com/Peersyst/xrpl-go v0.1.11
 
@@ -20,5 +18,5 @@ require (
 	github.com/tyler-smith/go-bip32 v1.0.0 // indirect
 	github.com/tyler-smith/go-bip39 v1.1.0 // indirect
 	github.com/ugorji/go/codec v1.2.11 // indirect
-	golang.org/x/crypto v0.35.0 // indirect
+	golang.org/x/crypto v0.45.0 // indirect
 )

_code-samples/issue-a-token/go/go.sum

@@ -46,8 +46,8 @@ github.com/ugorji/go/codec v1.2.11/go.mod h1:UNopzCgEMSXjBc6AOMqYvWC1ktqTAfzJZUZ
 golang.org/x/crypto v0.0.0-20170613210332-850760c427c5/go.mod h1:6SG95UA2DQfeDnfUPMdvaQW0Q7yPrPDi9nlGo2tz2b4=
 golang.org/x/crypto v0.0.0-20190308221718-c2843e01d9a2/go.mod h1:djNgcEr1/C05ACkg1iLfiJU5Ep61QUkGW8qpdssI0+w=
 golang.org/x/crypto v0.0.0-20200622213623-75b288015ac9/go.mod h1:LzIPMQfyMNhhGPhUkYOs5KpL4U8rLKemX1yGLhDgUto=
-golang.org/x/crypto v0.35.0 h1:b15kiHdrGCHrP6LvwaQ3c03kgNhhiMgvlhxHQhmg2Xs=
-golang.org/x/crypto v0.35.0/go.mod h1:dy7dXNW32cAb/6/PRuTNsix8T+vJAqvuIy5Bli/x0YQ=
+golang.org/x/crypto v0.45.0 h1:jMBrvKuj23MTlT0bQEOBcAE0mjg8mK9RXFhRH6nyF3Q=
+golang.org/x/crypto v0.45.0/go.mod h1:XTGrrkGJve7CYK7J8PEww4aY7gM3qMCElcJQ8n8JdX4=
 golang.org/x/net v0.0.0-20190404232315-eb5bcb51f2a3/go.mod h1:t9HGtf8HONx5eT2rtn7q6eTqICYqUVnKs3thJo3Qplg=
 golang.org/x/sys v0.0.0-20190215142949-d0b11bdaac8a/go.mod h1:STP8DvDyc/dI5b8T5hshtkjS+E42TnysNCUPdjciGhY=
 golang.org/x/sys v0.0.0-20190412213103-97732733099d/go.mod h1:h1NjWce9XRLGQEsW7wpKNCjG9DtNlClVuFLEZdDNbEs=

_code-samples/issue-mpt-with-metadata/js/issue-mpt-with-metadata.js

@@ -10,26 +10,26 @@ const { wallet } = await client.fundWallet()
 
 // Define metadata as JSON
 const mpt_metadata = {
-  ticker: 'TBILL',
-  name: 'T-Bill Yield Token',
-  desc: 'A yield-bearing stablecoin backed by short-term U.S. Treasuries and money market instruments.',
-  icon: 'https://example.org/tbill-icon.png',
-  asset_class: 'rwa',
-  asset_subclass: 'treasury',
-  issuer_name: 'Example Yield Co.',
-  urls: [
+  t: 'TBILL',
+  n: 'T-Bill Yield Token',
+  d: 'A yield-bearing stablecoin backed by short-term U.S. Treasuries and money market instruments.',
+  i: 'https://example.org/tbill-icon.png',
+  ac: 'rwa',
+  as: 'treasury',
+  in: 'Example Yield Co.',
+  us: [
     {
-      url: 'https://exampleyield.co/tbill',
-      type: 'website',
-      title: 'Product Page'
+      u: 'https://exampleyield.co/tbill',
+      c: 'website',
+      t: 'Product Page'
     },
     {
-      url: 'https://exampleyield.co/docs',
-      type: 'docs',
-      title: 'Yield Token Docs'
+      u: 'https://exampleyield.co/docs',
+      c: 'docs',
+      t: 'Yield Token Docs'
     }
   ],
-  additional_info: {
+  ai: {
     interest_rate: '5.00%',
     interest_type: 'variable',
     yield_source: 'U.S. Treasury Bills',

_code-samples/issue-mpt-with-metadata/py/issue-mpt-with-metadata.py

@@ -12,26 +12,26 @@ wallet = generate_faucet_wallet(client, debug=True)
 
 # Define metadata as JSON
 mpt_metadata = {
-    "ticker": "TBILL",
-    "name": "T-Bill Yield Token",
-    "desc": "A yield-bearing stablecoin backed by short-term U.S. Treasuries and money market instruments.",
-    "icon": "https://example.org/tbill-icon.png",
-    "asset_class": "rwa",
-    "asset_subclass": "treasury",
-    "issuer_name": "Example Yield Co.",
-    "urls": [
+    "t": "TBILL",
+    "n": "T-Bill Yield Token",
+    "d": "A yield-bearing stablecoin backed by short-term U.S. Treasuries and money market instruments.",
+    "i": "example.org/tbill-icon.png",
+    "ac": "rwa",
+    "as": "treasury",
+    "in": "Example Yield Co.",
+    "us": [
         {
-            "url": "https://exampleyield.co/tbill",
-            "type": "website",
-            "title": "Product Page"
+            "u": "exampleyield.co/tbill",
+            "c": "website",
+            "t": "Product Page"
         },
         {
-            "url": "https://exampleyield.co/docs",
-            "type": "docs",
-            "title": "Yield Token Docs"
+            "u": "exampleyield.co/docs",
+            "c": "docs",
+            "t": "Yield Token Docs"
         }
     ],
-    "additional_info": {
+    "ai": {
         "interest_rate": "5.00%",
         "interest_type": "variable",
         "yield_source": "U.S. Treasury Bills",

_code-samples/multisigning/go/go.mod

@@ -1,8 +1,6 @@
 module github.com/XRPLF
 
-go 1.23.0
-
-toolchain go1.23.10
+go 1.24.0
 
 require github.com/Peersyst/xrpl-go v0.1.11
 
@@ -20,5 +18,5 @@ require (
 	github.com/tyler-smith/go-bip32 v1.0.0 // indirect
 	github.com/tyler-smith/go-bip39 v1.1.0 // indirect
 	github.com/ugorji/go/codec v1.2.11 // indirect
-	golang.org/x/crypto v0.35.0 // indirect
+	golang.org/x/crypto v0.45.0 // indirect
 )

_code-samples/multisigning/go/go.sum

@@ -46,8 +46,8 @@ github.com/ugorji/go/codec v1.2.11/go.mod h1:UNopzCgEMSXjBc6AOMqYvWC1ktqTAfzJZUZ
 golang.org/x/crypto v0.0.0-20170613210332-850760c427c5/go.mod h1:6SG95UA2DQfeDnfUPMdvaQW0Q7yPrPDi9nlGo2tz2b4=
 golang.org/x/crypto v0.0.0-20190308221718-c2843e01d9a2/go.mod h1:djNgcEr1/C05ACkg1iLfiJU5Ep61QUkGW8qpdssI0+w=
 golang.org/x/crypto v0.0.0-20200622213623-75b288015ac9/go.mod h1:LzIPMQfyMNhhGPhUkYOs5KpL4U8rLKemX1yGLhDgUto=
-golang.org/x/crypto v0.35.0 h1:b15kiHdrGCHrP6LvwaQ3c03kgNhhiMgvlhxHQhmg2Xs=
-golang.org/x/crypto v0.35.0/go.mod h1:dy7dXNW32cAb/6/PRuTNsix8T+vJAqvuIy5Bli/x0YQ=
+golang.org/x/crypto v0.45.0 h1:jMBrvKuj23MTlT0bQEOBcAE0mjg8mK9RXFhRH6nyF3Q=
+golang.org/x/crypto v0.45.0/go.mod h1:XTGrrkGJve7CYK7J8PEww4aY7gM3qMCElcJQ8n8JdX4=
 golang.org/x/net v0.0.0-20190404232315-eb5bcb51f2a3/go.mod h1:t9HGtf8HONx5eT2rtn7q6eTqICYqUVnKs3thJo3Qplg=
 golang.org/x/sys v0.0.0-20190215142949-d0b11bdaac8a/go.mod h1:STP8DvDyc/dI5b8T5hshtkjS+E42TnysNCUPdjciGhY=
 golang.org/x/sys v0.0.0-20190412213103-97732733099d/go.mod h1:h1NjWce9XRLGQEsW7wpKNCjG9DtNlClVuFLEZdDNbEs=

_code-samples/partial-payment/go/go.mod

@@ -1,8 +1,6 @@
 module github.com/XRPLF
 
-go 1.23.0
-
-toolchain go1.23.10
+go 1.24.0
 
 require github.com/Peersyst/xrpl-go v0.1.11
 
@@ -20,5 +18,5 @@ require (
 	github.com/tyler-smith/go-bip32 v1.0.0 // indirect
 	github.com/tyler-smith/go-bip39 v1.1.0 // indirect
 	github.com/ugorji/go/codec v1.2.11 // indirect
-	golang.org/x/crypto v0.35.0 // indirect
+	golang.org/x/crypto v0.45.0 // indirect
 )

_code-samples/partial-payment/go/go.sum

@@ -46,8 +46,8 @@ github.com/ugorji/go/codec v1.2.11/go.mod h1:UNopzCgEMSXjBc6AOMqYvWC1ktqTAfzJZUZ
 golang.org/x/crypto v0.0.0-20170613210332-850760c427c5/go.mod h1:6SG95UA2DQfeDnfUPMdvaQW0Q7yPrPDi9nlGo2tz2b4=
 golang.org/x/crypto v0.0.0-20190308221718-c2843e01d9a2/go.mod h1:djNgcEr1/C05ACkg1iLfiJU5Ep61QUkGW8qpdssI0+w=
 golang.org/x/crypto v0.0.0-20200622213623-75b288015ac9/go.mod h1:LzIPMQfyMNhhGPhUkYOs5KpL4U8rLKemX1yGLhDgUto=
-golang.org/x/crypto v0.35.0 h1:b15kiHdrGCHrP6LvwaQ3c03kgNhhiMgvlhxHQhmg2Xs=
-golang.org/x/crypto v0.35.0/go.mod h1:dy7dXNW32cAb/6/PRuTNsix8T+vJAqvuIy5Bli/x0YQ=
+golang.org/x/crypto v0.45.0 h1:jMBrvKuj23MTlT0bQEOBcAE0mjg8mK9RXFhRH6nyF3Q=
+golang.org/x/crypto v0.45.0/go.mod h1:XTGrrkGJve7CYK7J8PEww4aY7gM3qMCElcJQ8n8JdX4=
 golang.org/x/net v0.0.0-20190404232315-eb5bcb51f2a3/go.mod h1:t9HGtf8HONx5eT2rtn7q6eTqICYqUVnKs3thJo3Qplg=
 golang.org/x/sys v0.0.0-20190215142949-d0b11bdaac8a/go.mod h1:STP8DvDyc/dI5b8T5hshtkjS+E42TnysNCUPdjciGhY=
 golang.org/x/sys v0.0.0-20190412213103-97732733099d/go.mod h1:h1NjWce9XRLGQEsW7wpKNCjG9DtNlClVuFLEZdDNbEs=

_code-samples/paths/go/go.mod

@@ -1,8 +1,6 @@
 module github.com/XRPLF
 
-go 1.23.0
-
-toolchain go1.23.10
+go 1.24.0
 
 require github.com/Peersyst/xrpl-go v0.1.11
 
@@ -20,5 +18,5 @@ require (
 	github.com/tyler-smith/go-bip32 v1.0.0 // indirect
 	github.com/tyler-smith/go-bip39 v1.1.0 // indirect
 	github.com/ugorji/go/codec v1.2.11 // indirect
-	golang.org/x/crypto v0.35.0 // indirect
+	golang.org/x/crypto v0.45.0 // indirect
 )

_code-samples/paths/go/go.sum

@@ -46,8 +46,8 @@ github.com/ugorji/go/codec v1.2.11/go.mod h1:UNopzCgEMSXjBc6AOMqYvWC1ktqTAfzJZUZ
 golang.org/x/crypto v0.0.0-20170613210332-850760c427c5/go.mod h1:6SG95UA2DQfeDnfUPMdvaQW0Q7yPrPDi9nlGo2tz2b4=
 golang.org/x/crypto v0.0.0-20190308221718-c2843e01d9a2/go.mod h1:djNgcEr1/C05ACkg1iLfiJU5Ep61QUkGW8qpdssI0+w=
 golang.org/x/crypto v0.0.0-20200622213623-75b288015ac9/go.mod h1:LzIPMQfyMNhhGPhUkYOs5KpL4U8rLKemX1yGLhDgUto=
-golang.org/x/crypto v0.35.0 h1:b15kiHdrGCHrP6LvwaQ3c03kgNhhiMgvlhxHQhmg2Xs=
-golang.org/x/crypto v0.35.0/go.mod h1:dy7dXNW32cAb/6/PRuTNsix8T+vJAqvuIy5Bli/x0YQ=
+golang.org/x/crypto v0.45.0 h1:jMBrvKuj23MTlT0bQEOBcAE0mjg8mK9RXFhRH6nyF3Q=
+golang.org/x/crypto v0.45.0/go.mod h1:XTGrrkGJve7CYK7J8PEww4aY7gM3qMCElcJQ8n8JdX4=
 golang.org/x/net v0.0.0-20190404232315-eb5bcb51f2a3/go.mod h1:t9HGtf8HONx5eT2rtn7q6eTqICYqUVnKs3thJo3Qplg=
 golang.org/x/sys v0.0.0-20190215142949-d0b11bdaac8a/go.mod h1:STP8DvDyc/dI5b8T5hshtkjS+E42TnysNCUPdjciGhY=
 golang.org/x/sys v0.0.0-20190412213103-97732733099d/go.mod h1:h1NjWce9XRLGQEsW7wpKNCjG9DtNlClVuFLEZdDNbEs=

_code-samples/remove-regular-key/README.md

@@ -0,0 +1,3 @@
+# Remove Regular Key Pair
+
+Remove the regular key pair assigned to an account.

_code-samples/remove-regular-key/js/package.json

@@ -0,0 +1,9 @@
+{
+    "name": "remove-regular-key",
+    "version": "1.0.0",
+    "license": "MIT",
+    "dependencies": {
+        "xrpl": "^4.5.0"
+    },
+    "type": "module"
+}

_code-samples/remove-regular-key/js/remove-regular-key.js

@@ -0,0 +1,109 @@
+import xrpl from 'xrpl'
+
+const client = new xrpl.Client('wss://s.altnet.rippletest.net:51233')
+await client.connect()
+
+console.log('Funding new wallet from faucet...')
+const { wallet } = await client.fundWallet()
+console.log(`Funded. Master key pair:
+  Address: ${wallet.address}
+  Seed: ${wallet.seed}
+`)
+
+// Generate a regular key and assign it to the account -------------------------
+// Skip this step if you are using a pre-existing account that already has a
+// regular key configured.
+const algorithm = 'ed25519'
+const regularKeyPair = xrpl.Wallet.generate(algorithm)
+console.log(`Generated regular key pair:
+  Address: ${regularKeyPair.address}
+  Seed: ${regularKeyPair.seed}
+  Algorithm: ${algorithm}
+`)
+const regularKeyTx = {
+  TransactionType: 'SetRegularKey',
+  Account: wallet.address,
+  RegularKey: regularKeyPair.address
+}
+xrpl.validate(regularKeyTx)
+
+console.log('Assigning regular key to the account...')
+const response = await client.submitAndWait(regularKeyTx, { wallet, autofill: true })
+const setRegularKeyResultCode = response.result.meta.TransactionResult
+if (setRegularKeyResultCode === 'tesSUCCESS') {
+  console.log('Regular Key set successfully.')
+} else {
+  console.error(`SetRegularKey failed with code ${setRegularKeyResultCode}.`)
+  client.disconnect()
+  process.exit(1)
+}
+
+// Check regular key associated with account -----------------------------------
+const accountInfoResp = await client.request({
+  command: 'account_info',
+  account: wallet.address,
+  ledger_index: 'validated'
+})
+if (accountInfoResp.error) {
+  console.error('Error looking up account:', accountInfoResp.error)
+  client.disconnect()
+  process.exit(1)
+}
+console.log(`Account info for ${wallet.address}:`)
+console.log(JSON.stringify(accountInfoResp.result.account_data, null, 2))
+if (accountInfoResp.result.account_data.RegularKey) {
+  console.log('Current regular key:',
+    accountInfoResp.result.account_data.RegularKey
+  )
+} else {
+  console.log('No regular key set.')
+  client.disconnect()
+  process.exit(1)
+}
+
+// Remove regular key from account ---------------------------------------------
+const removeRegularKeyTx = {
+  TransactionType: 'SetRegularKey',
+  Account: wallet.address
+  // Omit RegularKey field to remove existing regular key from account
+}
+xrpl.validate(removeRegularKeyTx)
+
+console.log('Removing regular key from account...')
+const removeResp = await client.submitAndWait(removeRegularKeyTx, {
+  wallet: regularKeyPair, // When removing, you can use the regular key or master key
+  autofill: true
+})
+const removeRegularKeyResultCode = removeResp.result.meta.TransactionResult
+if (removeRegularKeyResultCode === 'tesSUCCESS') {
+  console.log('Regular Key successfully removed.')
+} else {
+  console.error('SetRegularKey (removing) failed with code', 
+    removeRegularKeyResultCode
+  )
+  client.disconnect()
+  process.exit(1)
+}
+
+// Confirm that the account has no regular key ---------------------------------
+const accountInfoResp2 = await client.request({
+  command: 'account_info',
+  account: wallet.address,
+  ledger_index: 'validated'
+})
+if (accountInfoResp2.error) {
+  console.error('Error looking up account:', accountInfoResp2.error)
+  client.disconnect()
+  process.exit(1)
+}
+console.log(`Account info for ${wallet.address}:`)
+console.log(JSON.stringify(accountInfoResp2.result.account_data, null, 2))
+if (accountInfoResp2.result.account_data.RegularKey) {
+  console.log('Regular key address is:', 
+    accountInfoResp2.result.account_data.RegularKey
+  )
+} else {
+  console.log('No regular key set.')
+}
+
+client.disconnect()

_code-samples/remove-regular-key/py/remove-regular-key.py

@@ -0,0 +1,95 @@
+import json
+from xrpl.clients import JsonRpcClient
+from xrpl.wallet import generate_faucet_wallet, Wallet
+from xrpl.models.transactions import SetRegularKey
+from xrpl.models.requests import AccountInfo
+from xrpl.transaction import submit_and_wait
+
+client = JsonRpcClient("https://s.altnet.rippletest.net:51234")
+
+print("Funding new wallet from faucet...")
+wallet = generate_faucet_wallet(client)
+print(f"""Funded. Master key pair:
+  Address: {wallet.address}
+  Seed: {wallet.seed}
+""")
+
+# Generate a regular key and assign it to the account -------------------------
+# Skip this step if you are using a pre-existing account that already has a
+# regular key configured.
+algorithm = "ed25519"
+regular_key_pair = Wallet.create(algorithm)
+print(f"""Generated regular key pair:
+  Address: {regular_key_pair.address}
+  Seed: {regular_key_pair.seed}
+  Algorithm: {algorithm}
+""")
+regular_key_tx = SetRegularKey(
+    account=wallet.address, regular_key=regular_key_pair.address
+)
+
+print("Assigning regular key to the account...")
+try:
+    response = submit_and_wait(regular_key_tx, client, wallet)
+except err:
+    print("Submitting SetRegularKey transaction failed with error", err)
+    exit(1)
+set_regular_key_result_code = response.result["meta"]["TransactionResult"]
+
+if set_regular_key_result_code == "tesSUCCESS":
+    print("Regular Key set successfully.")
+else:
+    print(f"SetRegularKey failed with code {set_regular_key_result_code}.")
+    exit(1)
+
+# Check regular key associated with account -----------------------------------
+account_info_resp = client.request(
+    AccountInfo(account=wallet.address, ledger_index="validated")
+)
+if not account_info_resp.is_successful():
+    print(f"Error looking up account:", account_info_resp.result)
+    exit(1)
+
+account_data = account_info_resp.result["account_data"]
+print(f"Account info for {wallet.address}:")
+print(json.dumps(account_data, indent=2))
+
+if "RegularKey" in account_data.keys():
+    print("Current regular key:", account_data["RegularKey"])
+else:
+    print("No regular key set.")
+    exit(1)
+
+# Remove regular key from account ---------------------------------------------
+remove_regular_key_tx = SetRegularKey(
+    account=wallet.address
+    # Omit regular_key field to remove existing regular key from account
+)
+
+print("Removing regular key from account...")
+# When removing, you can sign with the regular key or master key
+remove_resp = submit_and_wait(remove_regular_key_tx, client, regular_key_pair)
+remove_regular_key_result_code = remove_resp.result["meta"]["TransactionResult"]
+
+if remove_regular_key_result_code == "tesSUCCESS":
+    print("Regular Key successfully removed.")
+else:
+    print("SetRegularKey (removing) failed with code", remove_regular_key_result_code)
+    exit(1)
+
+# Confirm that the account has no regular key ---------------------------------
+account_info_resp2 = client.request(
+    AccountInfo(account=wallet.address, ledger_index="validated")
+)
+if not account_info_resp2.is_successful():
+    print("Error looking up account:", account_info_resp2.result)
+    exit(1)
+
+account_data2 = account_info_resp2.result["account_data"]
+print(f"Account info for {wallet.address}:")
+print(json.dumps(account_data2, indent=2))
+
+if "RegularKey" in account_data2.keys():
+    print("Regular key address is:", account_data2["RegularKey"])
+else:
+    print("No regular key set.")

_code-samples/remove-regular-key/py/requirements.txt

@@ -0,0 +1 @@
+xrpl-py>=4.4.0

_code-samples/send-xrp/go/go.mod

@@ -1,8 +1,6 @@
 module github.com/XRPLF
 
-go 1.23.0
-
-toolchain go1.23.10
+go 1.24.0
 
 require github.com/Peersyst/xrpl-go v0.1.11
 
@@ -20,5 +18,5 @@ require (
 	github.com/tyler-smith/go-bip32 v1.0.0 // indirect
 	github.com/tyler-smith/go-bip39 v1.1.0 // indirect
 	github.com/ugorji/go/codec v1.2.11 // indirect
-	golang.org/x/crypto v0.35.0 // indirect
+	golang.org/x/crypto v0.45.0 // indirect
 )

_code-samples/send-xrp/go/go.sum

@@ -46,8 +46,8 @@ github.com/ugorji/go/codec v1.2.11/go.mod h1:UNopzCgEMSXjBc6AOMqYvWC1ktqTAfzJZUZ
 golang.org/x/crypto v0.0.0-20170613210332-850760c427c5/go.mod h1:6SG95UA2DQfeDnfUPMdvaQW0Q7yPrPDi9nlGo2tz2b4=
 golang.org/x/crypto v0.0.0-20190308221718-c2843e01d9a2/go.mod h1:djNgcEr1/C05ACkg1iLfiJU5Ep61QUkGW8qpdssI0+w=
 golang.org/x/crypto v0.0.0-20200622213623-75b288015ac9/go.mod h1:LzIPMQfyMNhhGPhUkYOs5KpL4U8rLKemX1yGLhDgUto=
-golang.org/x/crypto v0.35.0 h1:b15kiHdrGCHrP6LvwaQ3c03kgNhhiMgvlhxHQhmg2Xs=
-golang.org/x/crypto v0.35.0/go.mod h1:dy7dXNW32cAb/6/PRuTNsix8T+vJAqvuIy5Bli/x0YQ=
+golang.org/x/crypto v0.45.0 h1:jMBrvKuj23MTlT0bQEOBcAE0mjg8mK9RXFhRH6nyF3Q=
+golang.org/x/crypto v0.45.0/go.mod h1:XTGrrkGJve7CYK7J8PEww4aY7gM3qMCElcJQ8n8JdX4=
 golang.org/x/net v0.0.0-20190404232315-eb5bcb51f2a3/go.mod h1:t9HGtf8HONx5eT2rtn7q6eTqICYqUVnKs3thJo3Qplg=
 golang.org/x/sys v0.0.0-20190215142949-d0b11bdaac8a/go.mod h1:STP8DvDyc/dI5b8T5hshtkjS+E42TnysNCUPdjciGhY=
 golang.org/x/sys v0.0.0-20190412213103-97732733099d/go.mod h1:h1NjWce9XRLGQEsW7wpKNCjG9DtNlClVuFLEZdDNbEs=

blog/2016/multisign-available.md

@@ -25,14 +25,14 @@ The Ripple Consensus Ledger's multi-signing feature also allows signers to indep
 
 1. Include the signer's address in your SignerList.
 2. Fund the signer's address in the ledger.
-3. [Assign a Regular Key Pair](/docs/tutorials/how-tos/manage-account-settings/assign-a-regular-key-pair) to the signer's address and disable its master key. (Funded addresses can only sign using their master key pair if it's not disabled.)
+3. [Assign a Regular Key Pair](/docs/tutorials/best-practices/key-management/assign-a-regular-key-pair.md) to the signer's address and disable its master key. (Funded addresses can only sign using their master key pair if it's not disabled.)
 4. Have that signer use its regular key pair to contribute to your multi-signatures.
 
 
 ## Further Reading ##
 
 - [Multi-Signing Summary](/docs/concepts/accounts/multi-signing)
-- [How to Multi-Sign](/docs/tutorials/how-tos/manage-account-settings/send-a-multi-signed-transaction)
+- [How to Multi-Sign](/docs/tutorials/best-practices/key-management/send-a-multi-signed-transaction.md)
 - [MultiSign Amendment](/resources/known-amendments.md#multisign)
 
 

blog/2016/multisign-reminder.md

@@ -12,7 +12,7 @@ markdown:
 
 The multi-signing amendment is currently supported by the majority of voting validators on Ripple, and is scheduled to become active on the protocol on Monday, **2016-06-27**. For more information, please see the multi-signing documentation in the Ripple Developer Portal:
 
-* [How to Multi-Sign](/docs/tutorials/how-tos/manage-account-settings/send-a-multi-signed-transaction)
+* [How to Multi-Sign](/docs/tutorials/best-practices/key-management/send-a-multi-signed-transaction.md)
 * [MultiSign Amendment Information](/resources/known-amendments.md#multisign)
 
 To continue receiving updates about the `rippled` server, please subscribe to the Ripple Server Google Group:

blog/2016/rippled-0.31.2-updates.md

@@ -57,5 +57,5 @@ For more information, see the following articles:
 
 * [MultiSign Amendment](/resources/known-amendments.md#multisign)
 * [Multi-Signing Overview](/docs/concepts/accounts/multi-signing)
-* [Tutorial - Set Up Multi-Signing](/docs/tutorials/how-tos/manage-account-settings/set-up-multi-signing)
-* [Tutorial - Send a Multi-Signed Transaction](/docs/tutorials/how-tos/manage-account-settings/send-a-multi-signed-transaction)
+* [Tutorial - Set Up Multi-Signing](../../docs/tutorials/best-practices/key-management/set-up-multi-signing.md)
+* [Tutorial - Send a Multi-Signed Transaction](../../docs/tutorials/best-practices/key-management/send-a-multi-signed-transaction.md)

blog/2019/multisignreserve-enabled.md

@@ -16,7 +16,7 @@ markdown:
 
 If you are already using multi-signing, no changes are necessary to continue using it. Optionally, you can now benefit from the reduced reserve requirements by replacing your existing SignerList with an identical or updated one.
 
-If you are not using multi-signing yet, feel free to take this opportunity to [Set Up Multi-Signing](/docs/tutorials/how-tos/manage-account-settings/set-up-multi-signing) with the reduced reserve requirements.
+If you are not using multi-signing yet, feel free to take this opportunity to [Set Up Multi-Signing](/docs/tutorials/best-practices/key-management/set-up-multi-signing.md) with the reduced reserve requirements.
 
 
 ## MultiSignReserve Summary

blog/2024/get-ready-for-amm.md

@@ -30,9 +30,9 @@ If you run a tool that parses full ledgers or transaction metadata, you need to
 
 ## Using AMM
 
-If you want to use AMM after the amendment goes live, the first step is to [Create an Automated Maker](../../docs/tutorials/how-tos/use-tokens/create-an-automated-market-maker.md) for the currency pair you want to trade. Only the first user for any given currency pair needs to do this, though; other users can deposit to the existing AMM to get in on the action.
+If you want to use AMM after the amendment goes live, the first step is to [Create an Automated Maker](../../docs/tutorials/dex/create-an-automated-market-maker.md) for the currency pair you want to trade. Only the first user for any given currency pair needs to do this, though; other users can deposit to the existing AMM to get in on the action.
 
-There are no special steps to use an AMM when trading currencies on the XRP Ledger. If you follow the standard steps to [Trade in the DEX](../../docs/tutorials/how-tos/use-tokens/trade-in-the-decentralized-exchange.md), and there's an AMM for the currency pair you're trading, your transaction automatically uses the AMM when doing so produces a better rate than consuming orders from the order book.
+There are no special steps to use an AMM when trading currencies on the XRP Ledger. If you follow the standard steps to [Trade in the DEX](../../docs/tutorials/dex/trade-in-the-decentralized-exchange.md), and there's an AMM for the currency pair you're trading, your transaction automatically uses the AMM when doing so produces a better rate than consuming orders from the order book.
 
 ## Further Reading
 

blog/2024/how-to-master-xrp-transfers.md

@@ -44,7 +44,7 @@ python3 lesson1-send-xrp.py
 
 ## Transferring XRP: A Hands-on Experience
 
-With your accounts at the ready, it's time to [send XRP payments using Python](./../../docs/tutorials/python/send-payments/index.md) back and forth. Experience the thrill of moving digital currency with just a few clicks:
+With your accounts at the ready, it's time to [send XRP payments using Python](./../../docs/tutorials/payments/create-accounts-send-xrp-in-python.md) back and forth. Experience the thrill of moving digital currency with just a few clicks:
 
 - **From Standby to Operational**: Enter the XRP amount, paste the operational account's address into the destination field, and watch the magic happen.
 - **Back to Standby**: Reverse the roles and transfer XRP from the operational account back to the standby account, completing the circle.

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

community/events.page.tsx

@@ -17,6 +17,7 @@ const infoSession4 = require("../static/img/events/xrpl-builder-office-hours-04.
 const decarb = require('../static/img/events/xrpl-decarb.png')
 const townHall = require('../static/img/events/town-hall-meetup.png')
 const devBootcamp = require('../static/img/events/dev-bootcamp.png')
+const italyHackathon = require("../static/img/events/italy-hackathon.png");
 export const frontmatter = {
   seo: {
     title: "Events",
@@ -26,8 +27,8 @@ export const frontmatter = {
 };
 export const sortEvents = (arr, asc = true) => {
   return arr.sort((a, b) => {
-    const dateA = moment(a.date, "MMMM D, YYYY");
-    const dateB = moment(b.date, "MMMM D, YYYY");
+    const dateA = moment(a.end_date, "MMMM D, YYYY");
+    const dateB = moment(b.end_date, "MMMM D, YYYY");
     return asc ? dateB.diff(dateA) : dateA.diff(dateB); // Returns a negative value if dateA is before dateB, positive if after, and 0 if the same
   });
 };
@@ -1269,20 +1270,53 @@ const events = [
     link: "https://luma.com/llwjrmcx",
     location: "Rome, Italy",
     date: "November 07, 2025",
-    image: hackathon,
+    image: italyHackathon,
     end_date: "November 08, 2025",
   },
   {
     name: "Vega House Hackathon",
     description:
-      "The Vega House XRPL Hackathon is calling all developers, designers, and innovators to create incredible solutions on the XRP Ledger (XRPL).",
+      "Vega House Hackathon: Compete in two XRPL tracks—Ledger Track to build MVP financial services using payments, tokenization, RLUSD, or AMM/DEX flows, and Exploration Track to create innovative apps leveraging XRPL features and upcoming amendments. Prizes total $25,000, including track awards and bounties for best use of new XRPL features.",
     type: "hackathon",
     link: "https://xrpl.vegahacks.xyz/",
     location: "Virtual",
-    date: "October 01, 2025",
-    image: hackathon,
+    date: "Oct 01 - Nov 14, 2025",
+    image: italyHackathon,
     end_date: "November 14, 2025",
   },
+  {
+    name: "XRPL Town Hall Meeting #5",
+    description:
+      "Join Us for the 5th XRPL Town Hall Meeting!",
+    type: "info",
+    link: "https://luma.com/wo0g0fpv",
+    location: "Virtual",
+    date: "October 16, 2025",
+    image: require("../static/img/events/townhall-5.png"),
+    end_date: "October 16, 2025",    
+  },
+  {
+    name: "XRPL Aquarium Residency Demo Day #7",
+    description:
+      "The Aquarium Residency is a 12-week program for entrepreneurs & developers building on the XRP Ledger blockchain.  Join us at our Paris HQ to connect with our 11 residents, discover their projects focused on DeFi II, and engage with the XRPL community.",
+    type: "meetup",
+    link: "https://luma.com/mnby11vr",
+    location: "Paris, France",
+    image: require("../static/img/events/aquarium-residency.png"),
+    date: "December 10, 2025",
+    end_date: "December 10, 2025",
+  },
+  {
+    name: "XRPL Hackathon @ Blockchain Kaigi 2025",
+    description:
+      "This is a 3-week online hackathon culminating in demos and an awards ceremony to be held in conjunction with Blockchain Kaigi 2025 in Mumbai, India.",
+    type: "hackathon",
+    link: "https://luma.com/ypj8ecj0",
+    location: "Online (with demos at IIT Bombay)",
+    date: "Nov 14 - Dec 06, 2025",
+    image: require("../static/img/events/hackathon-kaigi.png"),
+    end_date: "December 06, 2025",
+  },
 ];
 
 

community/index.page.tsx

@@ -20,6 +20,7 @@ const brazil = require("../static/img/events/event-meetup-brazil.png");
 const infoSession2 = require("../static/img/events/xrpl-builder-office-hours-02.png");
 const infoSession3 = require("../static/img/events/xrpl-builder-office-hours-03.png");
 const infoSession4 = require("../static/img/events/xrpl-builder-office-hours-04.png");
+const italyHackathon = require("../static/img/events/italy-hackathon.png");
 const events = [
   {
     name: "New Horizon: Innovate Without Limits: New Horizons Await",
@@ -377,22 +378,34 @@ const events = [
     link: "https://luma.com/llwjrmcx",
     location: "Rome, Italy",
     date: "November 07, 2025",
-    image: hackathon,
+    image: italyHackathon,
     end_date: "November 08, 2025",
     start_date: "November 07, 2025",
   },
   {
     name: "Vega House Hackathon",
     description:
-      "The Vega House XRPL Hackathon is calling all developers, designers, and innovators to create incredible solutions on the XRP Ledger (XRPL).",
+      "Vega House Hackathon: Compete in two XRPL tracks—Ledger Track to build MVP financial services using payments, tokenization, RLUSD, or AMM/DEX flows, and Exploration Track to create innovative apps leveraging XRPL features and upcoming amendments. Prizes total $25,000, including track awards and bounties for best use of new XRPL features.",
     type: "hackathon",
     link: "https://xrpl.vegahacks.xyz/",
     location: "Virtual",
-    date: "October 01, 2025",
-    image: hackathon,
+    date: "October 01 - November 14, 2025",
+    image: italyHackathon,
     end_date: "November 14, 2025",
     start_date: "October 01, 2025",
   },
+  {
+    name: "XRPL Hackathon @ Blockchain Kaigi 2025",
+    description:
+      "This is a 3-week online hackathon culminating in demos and an awards ceremony to be held in conjunction with Blockchain Kaigi 2025 in Mumbai, India.",
+    type: "hackathon",
+    link: "https://luma.com/ypj8ecj0",
+    location: "Online (with demos at IIT Bombay)",
+    date: "November 14 - December 06, 2025",
+    image: require("../static/img/events/hackathon-kaigi.png"),
+    start_date: "November 14, 2025",
+    end_date: "December 06, 2025",
+  },
 
 ];