Add request parameters to server definitions

Updated server_definitions.md to include request parameters.
Merge pull request #3371 from XRPLF/fix_src_links_admin_apis_etc
2025-12-06 17:27:57 +00:00 · 2025-12-03 10:50:37 -05:00 · 2025-12-02 12:32:08 -08:00 · 2025-11-28 04:50:13 -08:00 · 2025-11-28 11:16:30 +00:00 · 2025-11-28 03:15:46 -08:00
38 changed files with 776 additions and 855 deletions
--- a/_code-samples/clawback/go/go.mod
+++ b/_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
 )
--- a/_code-samples/clawback/go/go.sum
+++ b/_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=
--- a/_code-samples/get-started/go/go.mod
+++ b/_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
 )
--- a/_code-samples/get-started/go/go.sum
+++ b/_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=
--- a/_code-samples/issue-a-token/go/go.mod
+++ b/_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
 )
--- a/_code-samples/issue-a-token/go/go.sum
+++ b/_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=
--- a/_code-samples/paths/go/go.mod
+++ b/_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
 )
--- a/_code-samples/paths/go/go.sum
+++ b/_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=
--- a/docs/references/http-websocket-apis/admin-api-methods/key-generation-methods/validation_create.md
+++ b/docs/references/http-websocket-apis/admin-api-methods/key-generation-methods/validation_create.md
@@ -1,6 +1,4 @@
 ---
-html: validation_create.html
-parent: key-generation-methods.html
 seo:
    description: Generate keys for a rippled server to identify itself to the network.
 labels:
@@ -8,7 +6,7 @@ labels:
    - Core Server
 ---
 # validation_create
-[[Source]](https://github.com/XRPLF/rippled/blob/315a8b6b602798a4cff4d8e1911936011e12abdb/src/ripple/rpc/handlers/ValidationCreate.cpp "Source")
+[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/rpc/handlers/ValidationCreate.cpp "Source")

 Use the `validation_create` command to generate [cryptographic keys a `rippled` server can use to identify itself to the network](../../../../concepts/networks-and-servers/peer-protocol.md#node-key-pair). Similar to the [wallet_propose method][], this method only generates a set of keys in the proper format. It does not any makes changes to the XRP Ledger data or server configuration.

@@ -16,7 +14,7 @@ _The `validation_create` method is an [admin method](../index.md) that cannot be

 You can configure your server to use the generated key pair to sign validations (validation key pair) or regular peer-to-peer communications ([node key pair](../../../../concepts/networks-and-servers/peer-protocol.md#node-key-pair)).

-{% admonition type="success" name="Tip" %}For configuring a robust validator, you should use the `validator-keys` tool (included in the `rippled` RPM) to generate validator tokens (which can be rotated) with an offline master key. For more information, see [Validator Setup](../../../../infrastructure/configuration/server-modes/run-rippled-as-a-validator.md#3-enable-validation-on-your-rippled-server).{% /admonition %}
+{% admonition type="success" name="Tip" %}For configuring a robust validator, you should use the `validator-keys` tool (included in the `rippled` package build) to generate validator tokens (which can be rotated) with an offline master key. For more information, see [Validator Setup](../../../../infrastructure/configuration/server-modes/run-rippled-as-a-validator.md#3-enable-validation-on-your-rippled-server).{% /admonition %}


 ### Request Format
--- a/docs/references/http-websocket-apis/admin-api-methods/key-generation-methods/wallet_propose.md
+++ b/docs/references/http-websocket-apis/admin-api-methods/key-generation-methods/wallet_propose.md
@@ -1,6 +1,4 @@
 ---
-html: wallet_propose.html
-parent: key-generation-methods.html
 seo:
    description: Generate keys for a new account.
 labels:
@@ -8,14 +6,12 @@ labels:
    - Accounts
 ---
 # wallet_propose
-[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/WalletPropose.cpp "Source")
+[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/rpc/handlers/WalletPropose.cpp "Source")

-Use the `wallet_propose` method to generate a key pair and XRP Ledger address. This command only generates key and address values, and does not affect the XRP Ledger itself in any way. To become a funded address stored in the ledger, the address must [receive a Payment transaction](../../../../concepts/accounts/index.md#creating-accounts) that provides enough XRP to meet the [reserve requirement](../../../../concepts/accounts/reserves.md).
+Use the `wallet_propose` method to generate a key pair and XRP Ledger address. This command only generates key and address values, and does not affect the XRP Ledger itself in any way. To become a funded account in the ledger, the address must [receive a Payment transaction](../../../../concepts/accounts/index.md#creating-accounts) that provides enough XRP to meet the [reserve requirement](../../../../concepts/accounts/reserves.md).

 *The `wallet_propose` method is an [admin method](../index.md) that cannot be run by unprivileged users!* (This command is restricted to protect against people sniffing network traffic for account secrets, since admin commands are not usually transmitted over the outside network.)

-{% badge href="https://github.com/XRPLF/rippled/releases/tag/0.31.0" %}Updated in: rippled 0.31.0{% /badge %}
-
 ### Request Format

 An example of the request format:
--- a/docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/can_delete.md
+++ b/docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/can_delete.md
@@ -1,13 +1,11 @@
 ---
-html: can_delete.html
-parent: logging-and-data-management-methods.html
 seo:
    description: Allow online deletion of ledgers up to a specific ledger.
 labels:
    - Data Retention
 ---
 # can_delete
-[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/CanDelete.cpp "Source")
+[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/rpc/handlers/CanDelete.cpp "Source")

 The `can_delete` method informs the `rippled` server of the latest ledger version which may be deleted when using [online deletion with advisory deletion enabled](../../../../infrastructure/configuration/data-retention/online-deletion.md#advisory-deletion). If advisory deletion is not enabled, this method does nothing.

--- a/docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/ledger_cleaner.md
+++ b/docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/ledger_cleaner.md
@@ -1,15 +1,13 @@
 ---
-html: ledger_cleaner.html
-parent: logging-and-data-management-methods.html
 seo:
    description: Configure the ledger cleaner service to check for corrupted data.
 labels:
    - Data Retention
 ---
 # ledger_cleaner
-[[Source]](https://github.com/XRPLF/rippled/blob/df54b47cd0957a31837493cd69e4d9aade0b5055/src/ripple/rpc/handlers/LedgerCleaner.cpp "Source")
+[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/rpc/handlers/LedgerCleanerHandler.cpp "Source")

-The `ledger_cleaner` command controls the [Ledger Cleaner](https://github.com/XRPLF/rippled/blob/f313caaa73b0ac89e793195dcc2a5001786f916f/src/ripple/app/ledger/README.md#the-ledger-cleaner), an asynchronous maintenance process that can find and repair corruption in `rippled`'s database of ledgers.
+The `ledger_cleaner` command controls the [Ledger Cleaner](https://github.com/XRPLF/rippled/tree/master/src/xrpld/app/ledger#the-ledger-cleaner), an asynchronous maintenance process that can find and repair corruption in `rippled`'s database of ledgers.

 _The `ledger_cleaner` method is an [admin method](../index.md) that cannot be run by unprivileged users._

--- a/docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/ledger_request.md
+++ b/docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/ledger_request.md
@@ -1,13 +1,11 @@
 ---
-html: ledger_request.html
-parent: logging-and-data-management-methods.html
 seo:
    description: Query peer servers for a specific ledger version.
 labels:
    - Data Retention
 ---
 # ledger_request
-[[Source]](https://github.com/XRPLF/rippled/blob/e980e69eca9ea843d200773eb1f43abe3848f1a0/src/ripple/rpc/handlers/LedgerRequest.cpp "Source")
+[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/rpc/handlers/LedgerRequest.cpp "Source")

 The `ledger_request` command tells server to fetch a specific ledger version from its connected peers. This only works if one of the server's immediately-connected peers has that ledger. You may need to run the command several times to completely fetch a ledger.

--- a/docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/log_level.md
+++ b/docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/log_level.md
@@ -1,13 +1,11 @@
 ---
-html: log_level.html
-parent: logging-and-data-management-methods.html
 seo:
   description: Get or modify log verbosity.
 labels:
   - Data Retention
 ---
 # log_level
-[[Source]](https://github.com/XRPLF/rippled/blob/155fcdbcd0b4927152892c8c8be01d9cf62bed68/src/ripple/rpc/handlers/LogLevel.cpp "Source")
+[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/rpc/handlers/LogLevel.cpp "Source")

 The `log_level` command changes the `rippled` server's logging verbosity, or returns the current logging level for each category (called a _partition_) of log messages.

--- a/docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/logrotate.md
+++ b/docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/logrotate.md
@@ -1,13 +1,11 @@
 ---
-html: logrotate.html
-parent: logging-and-data-management-methods.html
 seo:
   description: Reopen the log file.
 labels:
   - Data Retention
 ---
 # logrotate
-[[Source]](https://github.com/XRPLF/rippled/blob/743bd6c9175c472814448ea889413be79dfd1c07/src/ripple/rpc/handlers/LogRotate.cpp "Source")
+[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/rpc/handlers/LogRotate.cpp "Source")

 The `logrotate` command closes and reopens the log file. This is intended to help with log rotation on Linux file systems.

--- a/docs/references/http-websocket-apis/admin-api-methods/peer-management-methods/connect.md
+++ b/docs/references/http-websocket-apis/admin-api-methods/peer-management-methods/connect.md
@@ -1,15 +1,13 @@
 ---
-html: connect.html
-parent: peer-management-methods.html
 seo:
    description: Force the rippled server to connect to a specific peer.
 labels:
    - Core Server
 ---
 # connect
-[[Source]](https://github.com/XRPLF/rippled/blob/a61ffab3f9010d8accfaa98aa3cacc7d38e74121/src/ripple/rpc/handlers/Connect.cpp "Source")
+[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/rpc/handlers/Connect.cpp "Source")

-The `connect` command forces the `rippled` server to connect to a specific peer `rippled` server.
+The `connect` command forces the `rippled` server to connect to a specific peer server.

 *The `connect` method is an [admin method](../index.md) that cannot be run by unprivileged users!*

--- a/docs/references/http-websocket-apis/admin-api-methods/peer-management-methods/peer_reservations_add.md
+++ b/docs/references/http-websocket-apis/admin-api-methods/peer-management-methods/peer_reservations_add.md
@@ -1,13 +1,11 @@
 ---
-html: peer_reservations_add.html
-parent: peer-management-methods.html
 seo:
    description: Add a reserved slot for a specific peer server.
 labels:
    - Core Server
 ---
 # peer_reservations_add
-[[Source]](https://github.com/XRPLF/rippled/blob/4a1148eb2849513dd1e7ae080288fd47ab57a376/src/ripple/rpc/handlers/Reservations.cpp#L36 "Source")
+[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/rpc/handlers/Reservations.cpp "Source")

 The {% code-page-name /%} method adds or updates a reserved slot for a specific peer server in the XRP Ledger [peer-to-peer network](../../../../concepts/networks-and-servers/peer-protocol.md).

--- a/docs/references/http-websocket-apis/admin-api-methods/peer-management-methods/peer_reservations_del.md
+++ b/docs/references/http-websocket-apis/admin-api-methods/peer-management-methods/peer_reservations_del.md
@@ -1,13 +1,11 @@
 ---
-html: peer_reservations_del.html
-parent: peer-management-methods.html
 seo:
    description: Remove a reserved slot for a specific peer server.
 labels:
    - Core Server
 ---
 # peer_reservations_del
-[[Source]](https://github.com/XRPLF/rippled/blob/4a1148eb2849513dd1e7ae080288fd47ab57a376/src/ripple/rpc/handlers/Reservations.cpp#L89 "Source")
+[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/rpc/handlers/Reservations.cpp "Source")

 The {% code-page-name /%} method removes a specific [peer reservation][], if one exists.

--- a/docs/references/http-websocket-apis/admin-api-methods/peer-management-methods/peer_reservations_list.md
+++ b/docs/references/http-websocket-apis/admin-api-methods/peer-management-methods/peer_reservations_list.md
@@ -1,13 +1,11 @@
 ---
-html: peer_reservations_list.html
-parent: peer-management-methods.html
 seo:
    description: List reserved slots for specific peer servers.
 labels:
    - Core Server
 ---
 # peer_reservations_list
-[[Source]](https://github.com/XRPLF/rippled/blob/4a1148eb2849513dd1e7ae080288fd47ab57a376/src/ripple/rpc/handlers/Reservations.cpp#L116 "Source")
+[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/rpc/handlers/Reservations.cpp "Source")

 The {% code-page-name /%} method lists [peer reservations][].

--- a/docs/references/http-websocket-apis/admin-api-methods/peer-management-methods/peers.md
+++ b/docs/references/http-websocket-apis/admin-api-methods/peer-management-methods/peers.md
@@ -1,13 +1,11 @@
 ---
-html: peers.html
-parent: peer-management-methods.html
 seo:
    description: Get information about the peer servers connected.
 labels:
    - Core Server
 ---
 # peers
-[[Source]](https://github.com/XRPLF/rippled/blob/52f298f150fc1530d201d3140c80d3eaf781cb5f/src/ripple/rpc/handlers/Peers.cpp "Source")
+[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/rpc/handlers/Peers.cpp "Source")

 The `peers` command returns a list of all other `rippled` servers currently connected to this one over the [Peer Protocol](../../../../concepts/networks-and-servers/peer-protocol.md), including information on their connection and sync status.

--- a/docs/references/http-websocket-apis/admin-api-methods/server-control-methods/ledger_accept.md
+++ b/docs/references/http-websocket-apis/admin-api-methods/server-control-methods/ledger_accept.md
@@ -1,13 +1,11 @@
 ---
-html: ledger_accept.html
-parent: server-control-methods.html
 seo:
    description: Close and advance the ledger in stand-alone mode.
 labels:
    - Core Server
 ---
 # ledger_accept
-[[Source]](https://github.com/XRPLF/rippled/blob/a61ffab3f9010d8accfaa98aa3cacc7d38e74121/src/ripple/rpc/handlers/LedgerAccept.cpp "Source")
+[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/rpc/handlers/LedgerAccept.cpp "Source")

 The `ledger_accept` method forces the server to close the current-working ledger and move to the next ledger number. This method is intended for testing purposes only, and is only available when the `rippled` server is running stand-alone mode.

--- a/docs/references/http-websocket-apis/admin-api-methods/server-control-methods/stop.md
+++ b/docs/references/http-websocket-apis/admin-api-methods/server-control-methods/stop.md
@@ -1,13 +1,11 @@
 ---
-html: stop.html
-parent: server-control-methods.html
 seo:
    description: Shut down the rippled server.
 labels:
    - Core Server
 ---
 # stop
-[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/Stop.cpp "Source")
+[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/rpc/handlers/Stop.cpp "Source")

 Gracefully shuts down the server.

--- a/docs/references/http-websocket-apis/admin-api-methods/signing-methods/sign.md
+++ b/docs/references/http-websocket-apis/admin-api-methods/signing-methods/sign.md
@@ -1,13 +1,11 @@
 ---
-html: sign.html # watch for clashes w/ this filename
-parent: signing-methods.html
 seo:
    description: Cryptographically sign a transaction.
 labels:
    - Transaction Sending
 ---
 # sign
-[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/SignHandler.cpp "Source")
+[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/rpc/handlers/SignHandler.cpp "Source")

 The `sign` method takes a [transaction in JSON format](../../../protocol/transactions/index.md) and a [seed value](../../../../concepts/accounts/cryptographic-keys.md), and returns a signed binary representation of the transaction. To contribute one signature to a [multi-signed transaction](../../../../concepts/accounts/multi-signing.md), use the [sign_for method][] instead.

--- a/docs/references/http-websocket-apis/admin-api-methods/signing-methods/sign_for.md
+++ b/docs/references/http-websocket-apis/admin-api-methods/signing-methods/sign_for.md
@@ -1,21 +1,16 @@
 ---
-html: sign_for.html
-parent: signing-methods.html
 seo:
    description: Contribute to a multi-signature.
 labels:
    - Transaction Sending
 ---
 # sign_for
-[[Source]](https://github.com/XRPLF/rippled/blob/release/src/ripple/rpc/handlers/SignFor.cpp "Source")
+[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/rpc/handlers/SignFor.cpp "Source")

 The `sign_for` command provides one signature for a [multi-signed transaction](../../../../concepts/accounts/multi-signing.md).

 {% partial file="/docs/_snippets/public-signing-note.md" /%}

-
-This command requires the [MultiSign amendment][] to be enabled.
-
 ## Request Format
 An example of the request format:

--- a/docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/consensus_info.md
+++ b/docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/consensus_info.md
@@ -1,6 +1,4 @@
 ---
-html: consensus_info.html
-parent: status-and-debugging-methods.html
 seo:
     description: Get information about the state of consensus as it happens.
 labels:
@@ -8,7 +6,7 @@ labels:
    - Core Server
 ---
 # consensus_info
-[[Source]](https://github.com/XRPLF/rippled/blob/a61ffab3f9010d8accfaa98aa3cacc7d38e74121/src/ripple/rpc/handlers/ConsensusInfo.cpp "Source")
+[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/rpc/handlers/ConsensusInfo.cpp "Source")

 The `consensus_info` command provides information about the [consensus process](../../../../concepts/consensus-protocol/index.md) for debugging purposes.

--- a/docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/feature.md
+++ b/docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/feature.md
@@ -1,6 +1,4 @@
 ---
-html: feature.html
-parent: status-and-debugging-methods.html
 seo:
    description: Get information about protocol amendments.
 labels:
@@ -8,11 +6,11 @@ labels:
    - Core Server
 ---
 # feature
-[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/Feature1.cpp "Source")
+[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/rpc/handlers/Feature1.cpp "Source")

 The `feature` command returns information about [amendments](../../../../concepts/networks-and-servers/amendments.md) this server knows about, including whether they are enabled and whether the server is voting in favor of those amendments in the [amendment process](../../../../concepts/networks-and-servers/amendments.md#amendment-process).

-You can use the `feature` command to configure the server to vote against or in favor of an amendment. This change persists even if you restart the server. {% badge href="https://github.com/XRPLF/rippled/releases/tag/1.7.0" %}Updated in: rippled 1.7.0{% /badge %}
+You can use the `feature` command to configure the server to vote against or in favor of an amendment. This change persists even if you restart the server.

 _The `feature` method documented on this page is an [admin method](../index.md). For the non-admin version, see the [`feature` public API method](../../public-api-methods/server-info-methods/feature.md)._

--- a/docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/fetch_info.md
+++ b/docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/fetch_info.md
@@ -1,13 +1,11 @@
 ---
-html: fetch_info.html
-parent: status-and-debugging-methods.html
 seo:
    description: Get information about the server's sync with the network.
 labels:
    - Core Server
 ---
 # fetch_info
-[[Source]](https://github.com/XRPLF/rippled/blob/315a8b6b602798a4cff4d8e1911936011e12abdb/src/ripple/rpc/handlers/FetchInfo.cpp "Source")
+[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/rpc/handlers/FetchInfo.cpp "Source")

 The `fetch_info` command returns information about objects that this server is currently fetching from the network, and how many peers have that information. It can also be used to reset current fetches.

--- a/docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/get_counts.md
+++ b/docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/get_counts.md
@@ -1,13 +1,11 @@
 ---
-html: get_counts.html
-parent: status-and-debugging-methods.html
 seo:
    description: Get statistics about the server's internals and memory usage.
 labels:
    - Core Server
 ---
 # get_counts
-[[Source]](https://github.com/XRPLF/rippled/blob/c7118a183a660648aa88a3546a6b2c5bce858440/src/ripple/rpc/handlers/GetCounts.cpp "Source")
+[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/rpc/handlers/GetCounts.cpp "Source")

 The `get_counts` command provides various stats about the health of the server, mostly the number of objects of different types that it currently holds in memory.

--- a/docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/print.md
+++ b/docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/print.md
@@ -1,13 +1,11 @@
 ---
-html: print.html
-parent: status-and-debugging-methods.html
 seo:
    description: Get information about internal subsystems.
 labels:
    - Core Server
 ---
 # print
-[[Source]](https://github.com/XRPLF/rippled/blob/315a8b6b602798a4cff4d8e1911936011e12abdb/src/ripple/rpc/handlers/Print.cpp "Source")
+[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/rpc/handlers/Print.cpp "Source")

 The `print` command returns the current status of various internal subsystems, including peers, the ledger cleaner, and the resource manager.

--- a/docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/validator_info.md
+++ b/docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/validator_info.md
@@ -1,14 +1,12 @@
 ---
-html: validator_info.html
-parent: status-and-debugging-methods.html
 seo:
    description: Get the server's validation settings, if configured as a validator.
 labels:
-  - コアサーバ
-  - ブロックチェーン
+    - Core Server
+    - Blockchain
 ---
 # validator_info
-[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/ValidatorInfo.cpp "Source")
+[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/rpc/handlers/ValidatorInfo.cpp "Source")

 The {% code-page-name /%} method returns the current validator settings of the server, if it is configured as a validator.

--- a/docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/validator_list_sites.md
+++ b/docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/validator_list_sites.md
@@ -1,6 +1,4 @@
 ---
-html: validator_list_sites.html
-parent: status-and-debugging-methods.html
 seo:
    description: Get information about sites that publish validator lists.
 labels:
@@ -8,7 +6,7 @@ labels:
    - Blockchain
 ---
 # validator_list_sites
-[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/ValidatorListSites.cpp "Source")
+[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/rpc/handlers/ValidatorListSites.cpp "Source")

 The `validator_list_sites` command returns status information of sites serving validator lists.

--- a/docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/validators.md
+++ b/docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/validators.md
@@ -1,6 +1,4 @@
 ---
-html: validators.html
-parent: status-and-debugging-methods.html
 seo:
    description: Get information about the current validators.
 labels:
@@ -8,7 +6,7 @@ labels:
    - Blockchain
 ---
 # validators
-[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/Validators.cpp "Source")
+[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/rpc/handlers/Validators.cpp "Source")

 The `validators` command returns human readable information about the current list of published and [trusted validators](../../../../concepts/consensus-protocol/index.md#trust-based-validation) used by the server.

--- a/docs/references/http-websocket-apis/peer-port-methods/health-check.md
+++ b/docs/references/http-websocket-apis/peer-port-methods/health-check.md
@@ -1,13 +1,11 @@
 ---
-html: health-check.html
-parent: peer-port-methods.html
 seo:
    description: Special API method for reporting server health.
 labels:
    - Core Server
 ---
 # Health Check
-[[Source]](https://github.com/XRPLF/rippled/blob/de0c52738785de8bf837f9124da65c7905e7bb5a/src/ripple/overlay/impl/OverlayImpl.cpp#L1084-L1168 "Source")
+[[Source]](https://github.com/XRPLF/rippled/blob/70d5c624e8cf732a362335642b2f5125ce4b43c1/src/xrpld/overlay/detail/OverlayImpl.cpp#L943-L1038 "Source")

 The Health Check is a special [peer port method](index.md) for reporting on the health of an individual `rippled` server. This method is intended for use in automated monitoring to recognize outages and prompt automated or manual interventions such as restarting the server. {% badge href="https://github.com/XRPLF/rippled/releases/tag/1.6.0" %}New in: rippled 1.6.0{% /badge %}

--- a/docs/references/http-websocket-apis/peer-port-methods/validator-list.md
+++ b/docs/references/http-websocket-apis/peer-port-methods/validator-list.md
@@ -1,6 +1,4 @@
 ---
-html: validator-list.html
-parent: peer-port-methods.html
 seo:
    description: Special API method for sharing recommended validator lists.
 labels:
@@ -8,6 +6,7 @@ labels:
    - Blockchain
 ---
 # Validator List Method
+[[Source]](https://github.com/XRPLF/rippled/blob/70d5c624e8cf732a362335642b2f5125ce4b43c1/src/xrpld/overlay/detail/OverlayImpl.cpp#L875-L940 "Source")

 The validator list method is a special API endpoint that fetches a current, trusted validator list a `rippled` server is using. This often represents the exact list of validators a server trusts.

@@ -45,7 +44,7 @@ The JSON object has the following fields:
 | `public_key`     | String | The public key used to verify this validator list data, in hexadecimal. This is a 32-byte Ed25519 public key prefixed with the byte `0xED`.  |

 ### Manifest Data
-[[Source]](https://github.com/XRPLF/rippled/blob/97712107b71a8e2089d2e3fcef9ebf5362951110/src/ripple/app/misc/impl/Manifest.cpp#L43-L66 "Source")
+[[Source]](https://github.com/XRPLF/rippled/blob/8d1b3b39940eca2735a0e9279bdd92b0748fd84c/src/xrpld/app/misc/detail/Manifest.cpp#L54-L82 "Source")

 A "manifest" contains information uniquely identifying a person or organization involved in the consensus process, either a **validator** or a **list publisher**. A validator's manifest contains the _public_ information from that [validator's token](../../../infrastructure/configuration/server-modes/run-rippled-as-a-validator.md#3-enable-validation-on-your-rippled-server). A list publisher's manifest provides information about the list publisher. Both are typically encoded to binary in the XRP Ledger's standard [binary serialization format](../../protocol/binary-format.md). (There is no standard JSON representation of a manifest.)

--- a/docs/references/http-websocket-apis/public-api-methods/server-info-methods/server_definitions.md
+++ b/docs/references/http-websocket-apis/public-api-methods/server-info-methods/server_definitions.md
@@ -39,7 +39,11 @@ An example of the request format:

 {% try-it method="server_definitions" /%}

-The request does not take any parameters.
+The request includes the following parameters:
+
+| Field             | Type   | Required? | Description |
+|:------------------|:-------|:----------|-------------|
+| `hash`            | String | No        | If included and the hash matches the server's hash, the full set of definitions will not be returned. |


 ## Response Format
--- a/docs/references/protocol/binary-format.md
+++ b/docs/references/protocol/binary-format.md
@@ -189,8 +189,6 @@ Transactions and ledger entries may contain fields of any of the following types
 | [UInt256][]      | 5         | 256        | No                   | A 256-bit binary value. This usually represents the hash of a transaction, ledger version, or ledger entry. |
 | [UInt384][]      | 22        | 384        | No                   | **UNUSED.** A 384-bit binary value. |
 | [UInt512][]      | 23        | 512        | No                   | **UNUSED.** A 512-bit binary value. |
-| [Int32][]        | 10        | 32         | No                   | **UNUSED.** A 32-bit signed integer. |
-| [Int64][]        | 11        | 64         | No                   | **UNUSED.** A 64-bit signed integer. |
 | [Vector256][]    | 19        | Variable   | Yes                  | A list of 256-bit binary values. This may be a list of ledger entries or other hash values. |
 | [XChainBridge][] | 25        | Variable   | No                   | A bridge between two blockchains, identified by the door accounts and issued assets on both chains. |

@@ -396,21 +394,6 @@ The types UInt96, UInt384, and UInt512 are currently defined but not used.

 The `TransactionType` field is a special case. In JSON, this field is conventionally represented as a string with the name of the transaction type. In binary, this field is a UInt16. The `TRANSACTION_TYPES` object in the [definitions file](#definitions-file) maps these strings to the numeric values used in the binary format.

-
-### Int Fields
-[Int32]: #int-fields
-[Int64]: #int-fields
-
-The XRP Ledger supports signed 32-bit integers (Int32), which use standard big-endian binary signed integer representation with two's complement to handle negative values.
-
-In JSON format, Int32 fields can be represented as:
-
- JSON numbers (for values within JavaScript's safe integer range).
- Strings containing decimal numbers.
-
-Although the protocol supports the Int32 type, no fields currently use it. An Int64 type has also been defined, but is unsupported.
-
-
 ### Vector256 Fields
 [Vector256]: #vector256-fields

--- a/docs/tutorials/javascript/amm/trade-with-auction-slot.md
+++ b/docs/tutorials/javascript/amm/trade-with-auction-slot.md
@@ -240,7 +240,7 @@ Save the taker pays and taker gets fields; use these values to get the total amo
        }
 ```

-Use [AMM helper functions](https://github.com/XRPLF/rippled/blob/2d1854f354ff8bb2b5671fd51252c5acd837c433/src/ripple/app/misc/impl/AMMHelpers.cpp) to estimate values for:
+Implement [AMM formulas](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/misc/detail/AMMHelpers.cpp) to estimate values for:

 - Cost to swap token without an auction slot.
 - Cost to swap token with an auction slot.
@@ -534,7 +534,7 @@ Report the results.

 ## Code Walkthrough (ripplex13b-amm-formulas.js) 

-You can open `ripplex13b-amm-formulas.js` from the [Quickstart Samples](https://github.com/XRPLF/xrpl-dev-portal/tree/master/_code-samples/quickstart/js/) to view the source code. This tutorial uses three of the available [AMM helper functions](https://github.com/XRPLF/rippled/blob/2d1854f354ff8bb2b5671fd51252c5acd837c433/src/ripple/app/misc/impl/AMMHelpers.cpp).
+You can open `ripplex13b-amm-formulas.js` from the [Quickstart Samples](https://github.com/XRPLF/xrpl-dev-portal/tree/master/_code-samples/quickstart/js/) to view the source code. This code implements several core [AMM formulas](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/misc/detail/AMMHelpers.cpp) defined by the protocol.


 ### swapOut()
--- a/resources/contribute-code/create-custom-transactors.md
+++ b/resources/contribute-code/create-custom-transactors.md
@@ -1,6 +1,4 @@
 ---
-html: create-custom-transactors.html
-parent: contribute-code.html
 seo:
    description: Create custom transactors to interact with the XRP Ledger.
 labels:
@@ -78,8 +76,8 @@ The `preflight` function checks for errors in the transaction itself before acce
    {% admonition type="info" name="Note" %}The `~` symbol returns an optional type.{% /admonition %}

 - You can view ledger and transaction schemas here:
-    - [`LedgerFormats.cpp`](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/impl/LedgerFormats.cpp)
-    - [`TxFormats.cpp`](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/impl/TxFormats.cpp)
+    - [`ledger_entries.macro`](https://github.com/XRPLF/rippled/blob/master/include/xrpl/protocol/detail/ledger_entries.macro)
+    - [`transactions.macro`](https://github.com/XRPLF/rippled/blob/master/include/xrpl/protocol/detail/transactions.macro)

 - `rippled` summarizes transaction results with result codes. See: [Transaction Results](../../docs/references/protocol/transactions/transaction-results/index.md)

@@ -344,7 +342,7 @@ EscrowFinish::calculateBaseFee(ReadView const& view, STTx const& tx)

 ### `makeTxConsequences`

-`rippled` uses a [`TxConsequences`](https://github.com/XRPLF/rippled/blob/master/src/ripple/app/tx/applySteps.h#L41-L44) class to describe the outcome to an account when applying a transaction. It tracks the fee, maximum possible XRP spent, and how many sequence numbers are consumed by the transaction. There are three types of consequences:
+`rippled` uses a [`TxConsequences`](https://github.com/XRPLF/rippled/blob/70d5c624e8cf732a362335642b2f5125ce4b43c1/src/xrpld/app/tx/applySteps.h#L58) class to describe the outcome to an account when applying a transaction. It tracks the fee, maximum possible XRP spent, and how many sequence numbers are consumed by the transaction. There are three types of consequences:

 - **Normal:** The transactor doesn't affect transaction signing and _only_ consumes an XRP fee. Transactions that spend XRP beyond the fee aren't considered normal.
 - **Blocker:** The transactor affects transaction signing, preventing valid transactions from queueing behind it.
Author	SHA1	Message	Date
Mayukha Vadari	ac623ef506	Add request parameters to server definitions Updated server_definitions.md to include request parameters.	2025-12-03 10:50:37 -05:00
Rome Reginelli	d48698531c	Merge pull request #3371 from XRPLF/fix_src_links_admin_apis_etc Update source links in admin api refs & elsewhere	2025-12-02 12:32:08 -08:00
Maria Shodunke	6dce88c4f8	Merge pull request #3396 from XRPLF/dependabot/go_modules/_code-samples/issue-a-token/go/golang.org/x/crypto-0.45.0 Bump golang.org/x/crypto from 0.35.0 to 0.45.0 in /_code-samples/issue-a-token/go	2025-11-28 04:50:13 -08:00
dependabot[bot]	724c61c9e3	Bump golang.org/x/crypto in /_code-samples/issue-a-token/go Bumps [golang.org/x/crypto](https://github.com/golang/crypto) from 0.35.0 to 0.45.0. - [Commits](https://github.com/golang/crypto/compare/v0.35.0...v0.45.0) --- updated-dependencies: - dependency-name: golang.org/x/crypto dependency-version: 0.45.0 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>	2025-11-28 11:16:30 +00:00
Maria Shodunke	50f2f35b0b	Merge pull request #3394 from XRPLF/dependabot/go_modules/_code-samples/get-started/go/golang.org/x/crypto-0.45.0 Bump golang.org/x/crypto from 0.35.0 to 0.45.0 in /_code-samples/get-started/go	2025-11-28 03:15:46 -08:00
Maria Shodunke	d4cfcee8ea	Merge pull request #3395 from XRPLF/dependabot/go_modules/_code-samples/paths/go/golang.org/x/crypto-0.45.0 Bump golang.org/x/crypto from 0.35.0 to 0.45.0 in /_code-samples/paths/go	2025-11-28 03:15:29 -08:00
dependabot[bot]	e9709335a9	Bump golang.org/x/crypto in /_code-samples/paths/go Bumps [golang.org/x/crypto](https://github.com/golang/crypto) from 0.35.0 to 0.45.0. - [Commits](https://github.com/golang/crypto/compare/v0.35.0...v0.45.0) --- updated-dependencies: - dependency-name: golang.org/x/crypto dependency-version: 0.45.0 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>	2025-11-27 11:33:04 +00:00
dependabot[bot]	45f25acc3e	Bump golang.org/x/crypto in /_code-samples/get-started/go Bumps [golang.org/x/crypto](https://github.com/golang/crypto) from 0.35.0 to 0.45.0. - [Commits](https://github.com/golang/crypto/compare/v0.35.0...v0.45.0) --- updated-dependencies: - dependency-name: golang.org/x/crypto dependency-version: 0.45.0 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>	2025-11-27 11:32:06 +00:00
Maria Shodunke	61bc24b7dc	Merge pull request #3390 from XRPLF/dependabot/go_modules/_code-samples/clawback/go/golang.org/x/crypto-0.45.0 Bump golang.org/x/crypto from 0.35.0 to 0.45.0 in /_code-samples/clawback/go	2025-11-27 03:31:11 -08:00
dependabot[bot]	3a1bb9a70b	Bump golang.org/x/crypto in /_code-samples/clawback/go Bumps [golang.org/x/crypto](https://github.com/golang/crypto) from 0.35.0 to 0.45.0. - [Commits](https://github.com/golang/crypto/compare/v0.35.0...v0.45.0) --- updated-dependencies: - dependency-name: golang.org/x/crypto dependency-version: 0.45.0 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>	2025-11-24 12:21:34 +00:00
mDuo13	e3ee7bf32f	Update source links in admin api refs & elsewhere	2025-10-30 14:15:03 -07:00