diff --git a/@l10n/es-ES/about/faq.md b/@l10n/es-ES/about/faq.md index e4289598754..b48c7853414 100644 --- a/@l10n/es-ES/about/faq.md +++ b/@l10n/es-ES/about/faq.md @@ -130,7 +130,7 @@ Ripple se compromete a monitorear e informar cualquier indicador AML en la red X #### ¿Cuál es el proceso para revisar las contribuciones de código de terceros? -El proceso de contribución de código comienza cuando un desarrollador abre una [pull request](https://docs.github.com/en/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests) a un repositorio de código fuente como el [repositorio `rippled`](https://github.com/xrplf/rippled/), que contiene la implementación de referencia de Ripple del núcleo del servidor y del protocolo de XRP Ledger. +El proceso de contribución de código comienza cuando un desarrollador abre una [pull request](https://docs.github.com/en/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests) a un repositorio de código fuente como el [repositorio `rippled`](https://github.com/XRPLF/rippled/), que contiene la implementación de referencia de Ripple del núcleo del servidor y del protocolo de XRP Ledger. Este pull request activa pruebas unitarias y de integración automatizadas, así como revisiones de código por parte de varios desarrolladores que, por lo general, tienen experiencia significativa en el área de código a la que afecta al pull request. @@ -141,7 +141,7 @@ Una vez que el pull request pasa las pruebas automatizadas y recibe la aprobaci No, Ripple no posee ni controla el XRP Ledger o la red XRP Ledger. -Ripple contribuye a una implementación de referencia del nucleo del servidor de XRP Ledger ([`rippled`](https://github.com/xrplf/rippled)) y emplea un equipo de ingenieros que contribuyen al código base de código abierto. Ripple publica periodicamente paquetes binarios precompilados. Cualquiera puede [descargar y compilar el software desde la fuente](../docs/infrastructure/installation/index.md). +Ripple contribuye a una implementación de referencia del nucleo del servidor de XRP Ledger ([`rippled`](https://github.com/XRPLF/rippled)) y emplea un equipo de ingenieros que contribuyen al código base de código abierto. Ripple publica periodicamente paquetes binarios precompilados. Cualquiera puede [descargar y compilar el software desde la fuente](../docs/infrastructure/installation/index.md). Varias entidades publican listas de validadores recomndadados (UNLs). Desde julio de 2023, Ripple mantiene solo uno de los 35 validadores que están en la UNL por defecto. diff --git a/@l10n/es-ES/docs/concepts/accounts/addresses.md b/@l10n/es-ES/docs/concepts/accounts/addresses.md index 4237382846b..a5fc8e4d57d 100644 --- a/@l10n/es-ES/docs/concepts/accounts/addresses.md +++ b/@l10n/es-ES/docs/concepts/accounts/addresses.md @@ -24,7 +24,7 @@ Algunas direcciones tienen un significado especial, o usos históricos, en el XR |-------------------------------|--------|-------------|--------------| | `rrrrrrrrrrrrrrrrrrrrrhoLvTp` | ACCOUNT\_ZERO | Una dirección que es la codificación en [base58][] en el XRP Ledger del valor `0`. En comunicaciones peer-to-peer, `rippled` utiliza esta dirección como el emisor de XRP. | Sí | | `rrrrrrrrrrrrrrrrrrrrBZbvji` | ACCOUNT\_ONE | Una dirección que es la codificación en [base58][] en el XRP Ledger del valor `1`. En el ledger, las [entradas RippleState](../../references/protocol/ledger-data/ledger-entry-types/ripplestate.md) utilizan esta dirección como marcador de posición para el emisor de un balance de una trust line. | Sí | -| `rHb9CJAWyB4rj91VRWn96DkukG4bwdtyTh` | La cuenta génesis | Cuando `rippled` inicia un nuevo ledger génesis desde el principio (por ejemplo, en modo solitario), esta cuenta contiene todo el XRP. Esta cuenta es generada con el valor semilla `masterpassphrase` el cual está [hard-coded](https://github.com/XRPLF/rippled/blob/94ed5b3a53077d815ad0dd65d490c8d37a147361/src/ripple/app/ledger/Ledger.cpp#L184). | No | +| `rHb9CJAWyB4rj91VRWn96DkukG4bwdtyTh` | La cuenta génesis | Cuando `rippled` inicia un nuevo ledger génesis desde el principio (por ejemplo, en modo solitario), esta cuenta contiene todo el XRP. Esta cuenta es generada con el valor semilla `masterpassphrase` el cual está [hard-coded](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/ledger/Ledger.cpp#L184). | No | | `rrrrrrrrrrrrrrrrrNAMEtxvNvQ` | black hole de reserva de nombre de Ripple | En el pasado, Ripple pedía a los usuarios enviar XRP a esta cuenta para reservar nombres Ripple.| Sí | | `rrrrrrrrrrrrrrrrrrrn5RM1rHd` | Dirección NaN | Versiones previas de [ripple-lib](https://github.com/XRPLF/xrpl.js) generaban esta dirección cuando se codificaba el valor [NaN](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/NaN) utilizan el formato de codificación [base58][] del XRP Ledger. | Sí | @@ -33,7 +33,7 @@ Algunas direcciones tienen un significado especial, o usos históricos, en el XR **Consejo:** ¡Estos detalles técnicos son solo relevantse para personas que crean librerias de software de bajo nivel para la compatibilidad con el XRP Ledger! -[[Fuente]](https://github.com/XRPLF/rippled/blob/35fa20a110e3d43ffc1e9e664fc9017b6f2747ae/src/ripple/protocol/impl/AccountID.cpp#L109-L140 "Fuente") +[[Fuente]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/libxrpl/protocol/AccountID.cpp#L134-L165 "Fuente") Las direcciones XRP Ledger están codificadas utilizando [base58][] con el _diccionario_ `rpshnaf39wBUDNEGHJKLM4PQRST7VWXYZ2bcdeCg65jkm8oFqi1tuvAxyz`. Como el XRP Ledger codifica varios tipos de claves con base58, antepone los datos codificados con un-byte de "prefijo de tipo" (también conocido como "prefijo de versión") para distinguirlos. El prefijo de tipo hace que las direcciones normalmente comiencen con diferentes letras en formato base58. @@ -41,7 +41,7 @@ El siguiente diagrama muestra la relación entre las claves y las direcciones: [{% inline-svg file="/docs/img/address-encoding.svg" /%}](/docs/img/address-encoding.svg "Clave pública maestra + Prefijo Tipo → ID de cuenta + Checksum → Dirección") -La fórmula para calcular direcciones XRP Ledger desde una clave pública es la siguiente. Para ver el código de ejemplo completo, consulta [`encode_address.js`](https://github.com/XRPLF/xrpl-dev-portal/blob/master/content/_code-samples/address_encoding/js/encode_address.js). Para el proceso de derivar la clave pública desde una passphrase a un valor semilla, consulta [Derivación de clave](cryptographic-keys.md#key-derivation). +La fórmula para calcular direcciones XRP Ledger desde una clave pública es la siguiente. Para ver el código de ejemplo completo, consulta [`encode_address.js`](https://github.com/XRPLF/xrpl-dev-portal/blob/master/_code-samples/address_encoding/js/encode_address.js). Para el proceso de derivar la clave pública desde una passphrase a un valor semilla, consulta [Derivación de clave](cryptographic-keys.md#key-derivation). 1. Importa los algoritmos necesarios: SHA-256, RIPEMD160, y base58. Configura el diccionario para base58. diff --git a/@l10n/es-ES/docs/concepts/accounts/cryptographic-keys.md b/@l10n/es-ES/docs/concepts/accounts/cryptographic-keys.md index 1fff2858689..a62cfc94f1e 100644 --- a/@l10n/es-ES/docs/concepts/accounts/cryptographic-keys.md +++ b/@l10n/es-ES/docs/concepts/accounts/cryptographic-keys.md @@ -152,14 +152,14 @@ El proceso de derivar un par de claves depende del algoritmo de firma. En todos Los procesos de derivación de claves descritos aquí están implementados en múltiples lugares y lenguajes de programación: - En C++ en el código base de `rippled`: - - [Definición de semilla](https://github.com/XRPLF/rippled/blob/develop/src/ripple/protocol/Seed.h) - - [Derivación de clave general & Ed25519](https://github.com/XRPLF/rippled/blob/develop/src/ripple/protocol/impl/SecretKey.cpp) - - [Derivación de clave secp256k1](https://github.com/XRPLF/rippled/blob/develop/src/ripple/protocol/impl/SecretKey.cpp) + - [Definición de semilla](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/Seed.h) + - [Derivación de clave general & Ed25519](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/libxrpl/protocol/SecretKey.cpp) + - [Derivación de clave secp256k1](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/libxrpl/protocol/SecretKey.cpp) - En Python 3 en {% repo-link path="_code-samples/key-derivation/py/key_derivation.py" %}esta sección de códigos de ejemplo del repositorio{% /repo-link %}. - En JavaScript en el paquete [`ripple-keypairs`](https://github.com/XRPLF/xrpl.js/tree/main/packages/ripple-keypairs). ### Derivación de clave Ed25519 -[[Fuente]](https://github.com/XRPLF/rippled/blob/fc7ecd672a3b9748bfea52ce65996e324553c05f/src/ripple/protocol/impl/SecretKey.cpp#L203 "Fuente") +[[Fuente]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/libxrpl/protocol/SecretKey.cpp#L313 "Fuente") [{% inline-svg file="/docs/img/key-derivation-ed25519.svg" /%}](/docs/img/key-derivation-ed25519.svg "Passphrase → Semilla → Clave secreta → Prefijo + Clave pública") @@ -180,7 +180,7 @@ Los procesos de derivación de claves descritos aquí están implementados en m Las claves efímeras de validador no pueden ser Ed25519. ### Derivación de clave secp256k1 -[[Fuente]](https://github.com/XRPLF/rippled/blob/develop/src/ripple/protocol/impl/SecretKey.cpp "Fuente") +[[Fuente]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/libxrpl/protocol/SecretKey.cpp "Fuente") [{% inline-svg file="/docs/img/key-derivation-secp256k1.svg" /%}](/docs/img/key-derivation-secp256k1.svg "Passphrase → Semilla → Par de claves inicial (Root Key Pair) → Par de claves intermedias → Par de claves maestras") diff --git a/@l10n/es-ES/docs/concepts/consensus-protocol/consensus-structure.md b/@l10n/es-ES/docs/concepts/consensus-protocol/consensus-structure.md index 8380ea60779..10be14053c6 100644 --- a/@l10n/es-ES/docs/concepts/consensus-protocol/consensus-structure.md +++ b/@l10n/es-ES/docs/concepts/consensus-protocol/consensus-structure.md @@ -107,7 +107,7 @@ Cuando el proceso de consenso se completa, cada servidor independientemente comp 2. Colocar el conjunto de transacciones acordado en _orden canónico_ para que cada servidor la procese de la misma forma. - [Orden canónico](https://github.com/XRPLF/rippled/blob/8429dd67e60ba360da591bfa905b58a35638fda1/src/ripple/app/misc/CanonicalTXSet.cpp#L25-L36) no es el orden de cómo las transacciones fueron recibidas, porque los servidores pueden recibir las mismas transacciones en diferente orden. Para prevenir a los participantes de competir sobre el orden de las trnasacciones, el orden canónico es difícil de manipular. + [Orden canónico](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/misc/CanonicalTXSet.cpp#L24-L40) no es el orden de cómo las transacciones fueron recibidas, porque los servidores pueden recibir las mismas transacciones en diferente orden. Para prevenir a los participantes de competir sobre el orden de las trnasacciones, el orden canónico es difícil de manipular. 3. Procesar cada transacción según sus instrucciones, en orden. Actualizar el estado del dato del ledger en consecuencia. diff --git a/@l10n/es-ES/docs/concepts/consensus-protocol/invariant-checking.md b/@l10n/es-ES/docs/concepts/consensus-protocol/invariant-checking.md index 774991aadea..dafeb58d0c7 100644 --- a/@l10n/es-ES/docs/concepts/consensus-protocol/invariant-checking.md +++ b/@l10n/es-ES/docs/concepts/consensus-protocol/invariant-checking.md @@ -38,39 +38,39 @@ Para incluir la transacción en el ledger con un código de clase `tec`, es nece El XRP Ledger comprueba todas las siguientes invariantes en cada transación: -[[Fuente]](https://github.com/XRPLF/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h#L92 "Fuente") +[[Fuente]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/InvariantCheck.h#L92 "Fuente") - [Comprobación de coste de transacción](#comprobación-de-coste-de-transacción) -[[Fuente]](https://github.com/XRPLF/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h#L118 "Fuente") +[[Fuente]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/InvariantCheck.h#L118 "Fuente") - [XRP no creado](#xrp-no-creado) -[[Fuente]](https://github.com/XRPLF/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h#L146 "Fuente") +[[Fuente]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/InvariantCheck.h#L146 "Fuente") - [Account Roots no eliminadas](#account-roots-no-eliminadas) -[[Fuente]](https://github.com/XRPLF/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h#L173 "Fuente") +[[Fuente]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/InvariantCheck.h#L203 "Fuente") - [Comprobaciones de balance XRP](#comprobaciones-de-balance-XRP) -[[Fuente]](https://github.com/XRPLF/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h#L197 "Fuente") +[[Fuente]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/InvariantCheck.h#L227 "Fuente") - [Coincidencia de tipos de entradas ledger](#coincidencia-de-tipos-de-entradas-de-ledger) -[[Fuente]](https://github.com/XRPLF/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h#L224 "Fuente") +[[Fuente]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/InvariantCheck.h#L254 "Fuente") - [No XRP Trust Lines](#no-xrp-trust-lines) -[[Fuente]](https://github.com/XRPLF/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h#L251 "Fuente") +[[Fuente]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/InvariantCheck.h#L389 "Fuente") - [No malas ofertas](#no-malas-ofertas) -[[Fuente]](https://github.com/XRPLF/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h#L275 "Fuente") +[[Fuente]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/InvariantCheck.h#L413 "Fuente") - [No escrow cero](#no-escrow-cero) -[[Fuente]](https://github.com/XRPLF/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h#L300 "Fuente") +[[Fuente]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/InvariantCheck.h#L438 "Fuente") - [Nueva Account Root válida](#nueva-account-root-válida) @@ -158,11 +158,11 @@ El XRP Ledger comprueba todas las siguientes invariantes en cada transación: - [Protegiendo el ledger: Comprobación de invariantes](https://xrpl.org/blog/2017/invariant-checking.html) - **Repositorio:** - - [Invariant Check.h](https://github.com/XRPLF/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h) - - [Invariant Check.cpp](https://github.com/XRPLF/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.cpp) - - [Parámetros del sistema](https://github.com/XRPLF/rippled/blob/develop/src/ripple/protocol/SystemParameters.h#L43) - - [Cantidad XRP](https://github.com/XRPLF/rippled/blob/develop/src/ripple/basics/XRPAmount.h#L244) - - [Formatos de ledger](https://github.com/XRPLF/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/protocol/LedgerFormats.h#L36-L94) + - [Invariant Check.h](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/InvariantCheck.h) + - [Invariant Check.cpp](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/InvariantCheck.cpp) + - [Parámetros del sistema](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/SystemParameters.h#L44) + - [Cantidad XRP](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/XRPAmount.h#L252) + - [Formatos de ledger](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/LedgerFormats.h#L53-L117) - **Otros:** diff --git a/@l10n/es-ES/docs/concepts/networks-and-servers/peer-protocol.md b/@l10n/es-ES/docs/concepts/networks-and-servers/peer-protocol.md index d70f958c7d3..64f64264592 100644 --- a/@l10n/es-ES/docs/concepts/networks-and-servers/peer-protocol.md +++ b/@l10n/es-ES/docs/concepts/networks-and-servers/peer-protocol.md @@ -18,11 +18,11 @@ El protocolo de pares es el modo principal de comunicación entre servidores en - Solicitar datos de ledger de ledgers históricos, o proporcionar esos datos. - Proponer una conjunto de transacciones para el consenso, o compartir el resultado calculado de aplicar el conjunto de transacciones de consenso. -Para establecer una conexión peer-to-peer, un servidor se conecta a otro usando HTTPS y solicita una [actualización HTTP](https://tools.ietf.org/html/rfc7230#section-6.7) para cambiar al protocolo `XRPL/2.0` (anteriormente `RTXP/1.2`). (Para más información, consultar el artículo [Red de superposición](https://github.com/XRPLF/rippled/blob/96bbabbd2ece106779bb544aa0e4ce174e99fdf6/src/ripple/overlay/README.md#handshake) en el [repositorio `rippled`](https://github.com/XRPLF/rippled).) +Para establecer una conexión peer-to-peer, un servidor se conecta a otro usando HTTPS y solicita una [actualización HTTP](https://tools.ietf.org/html/rfc7230#section-6.7) para cambiar al protocolo `XRPL/2.0` (anteriormente `RTXP/1.2`). (Para más información, consultar el artículo [Red de superposición](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/overlay/README.md#handshake) en el [repositorio `rippled`](https://github.com/XRPLF/rippled).) ## Descubrimiento de pares -El XRP Ledger utiliza el protocolo del "chismorreo" para ayudar a servidores a encontrar otros servidores para conectarse en la red XRP Ledger. Cuando un servidor se inicia, se reconecta a cualquier otro par al que se haya conectado anteriormente. Como alternativa, utiliza los [hubs públicos hardcodeados](https://github.com/XRPLF/rippled/blob/fa57859477441b60914e6239382c6fba286a0c26/src/ripple/overlay/impl/OverlayImpl.cpp#L518-L525). Después de que un servidor se conecte correctamente a un par, le pregunta a ese par por información de contacto (generalmente, dirección IP y puerto) de otros servidores XRP Ledger que también pueden estar buscando pares. El servidor puede conectarse entonces a esos servidores, y preguntarles por información de contacto de todavía más servidores a los que conectarse. A través de este proceso, el servior hace suficientes conexiones de pares para que pueda permanecer contectado con el resto de la red incluso si pierde la conexión con cualquier par en particular. +El XRP Ledger utiliza el protocolo del "chismorreo" para ayudar a servidores a encontrar otros servidores para conectarse en la red XRP Ledger. Cuando un servidor se inicia, se reconecta a cualquier otro par al que se haya conectado anteriormente. Como alternativa, utiliza los [hubs públicos hardcodeados](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/overlay/detail/OverlayImpl.h#L494-L509). Después de que un servidor se conecte correctamente a un par, le pregunta a ese par por información de contacto (generalmente, dirección IP y puerto) de otros servidores XRP Ledger que también pueden estar buscando pares. El servidor puede conectarse entonces a esos servidores, y preguntarles por información de contacto de todavía más servidores a los que conectarse. A través de este proceso, el servior hace suficientes conexiones de pares para que pueda permanecer contectado con el resto de la red incluso si pierde la conexión con cualquier par en particular. Normalmente, un servidor necesita conectarse a un hub público solo una vez, durante un corto período de tiempo, para encontrar otros pares. Después de hacerlo, el servidor puede o no permanecer conectado al hub, dependiendo de la estabilidad de su conexión de red, de lo ocupado que esté el hub y de cuántos otros pares de alta calidad encuentre el servidor. El servidor guarda las direcciones de estos otros pares para poder intentar reconectarse directamente a esos pares más tarde, después de una interrupción en la red o un reinicio. @@ -37,7 +37,7 @@ Para participar en el XRP Ledger, los servidores `rippled` conectan con pares ar Idealmente, el servidor debería poder enviar _y_ recibir conexiones en el puerto de pares. Debes [redireccionar el puerto utilizado por el protocolo de pares a través de tu firewall](../../infrastructure/configuration/peering/forward-ports-for-peering.md) para el servidor `rippled`. -IANA [ha asignado el puerto **2459**](https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml?search=2459) para el protocolo de pares del XRP Ledger, pero para la compatibilidad con sistemas antiguos, el [fichero de configuración por defecto de `rippled`](https://github.com/XRPLF/rippled/blob/master/cfg/rippled-example.cfg) escucha las conexiones entrantes de pares con el **port 51235** en todas las interfaces de la red. Si ejecutas un servidor, puedes configurar qué puerto(s) escucha tu servidor utilizando el fichero `rippled.cfg`. +IANA [ha asignado el puerto **2459**](https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml?search=2459) para el protocolo de pares del XRP Ledger, pero para la compatibilidad con sistemas antiguos, el [fichero de configuración por defecto de `rippled`](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/cfg/rippled-example.cfg) escucha las conexiones entrantes de pares con el **port 51235** en todas las interfaces de la red. Si ejecutas un servidor, puedes configurar qué puerto(s) escucha tu servidor utilizando el fichero `rippled.cfg`. Ejemplo: diff --git a/@l10n/es-ES/docs/concepts/tokens/decentralized-exchange/offers.md b/@l10n/es-ES/docs/concepts/tokens/decentralized-exchange/offers.md index 3b00dfb4977..98463a23bc9 100644 --- a/@l10n/es-ES/docs/concepts/tokens/decentralized-exchange/offers.md +++ b/@l10n/es-ES/docs/concepts/tokens/decentralized-exchange/offers.md @@ -85,7 +85,7 @@ Los límites de la trust line te protegen de recibir más de un token como pago Las Ofertas existentes se agrupan por tipo de cambio, que se mide como la relación entre `TakerGets` y `TakerPays`. Las Ofertas con un tipo de cambio más alto se toman preferentemente. (Es decir, la persona que acepta la oferta recibe tanto como sea posible por la cantidad de moneda que paga). Las Ofertas con el mismo tipo de cambio se toman en función de cuál se colocó primero. -Cuando las Ofertas se ejecutan en el mismo bloque del ledger, el orden en que se ejecutan se determina por el [orden canónico](https://github.com/XRPLF/rippled/blob/release/src/ripple/app/misc/CanonicalTXSet.cpp "Código fuente: Ordenación de transacciones") en el que las transacciones fueron [aplicadas en el ledger](https://github.com/XRPLF/rippled/blob/5425a90f160711e46b2c1f1c93d68e5941e4bfb6/src/ripple/app/consensus/LedgerConsensus.cpp#L1435-L1538 "Código fuente: Aplicando transacciones"). Este comportamiento está diseñado para ser determinista, eficiente y difícil de manipular. +Cuando las Ofertas se ejecutan en el mismo bloque del ledger, el orden en que se ejecutan se determina por el [orden canónico](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/misc/CanonicalTXSet.cpp "Código fuente: Ordenación de transacciones") en el que las transacciones fueron [aplicadas en el ledger](https://github.com/XRPLF/rippled/blob/5425a90f160711e46b2c1f1c93d68e5941e4bfb6/src/ripple/app/consensus/LedgerConsensus.cpp#L1435-L1538 "Código fuente: Aplicando transacciones"). Este comportamiento está diseñado para ser determinista, eficiente y difícil de manipular. ## Caducidad de la oferta diff --git a/@l10n/es-ES/docs/introduction/software-ecosystem.md b/@l10n/es-ES/docs/introduction/software-ecosystem.md index dc5db67d64a..795edc051ab 100644 --- a/@l10n/es-ES/docs/introduction/software-ecosystem.md +++ b/@l10n/es-ES/docs/introduction/software-ecosystem.md @@ -24,7 +24,7 @@ El XRP Ledger alberga un ecosistema profundo de varias capas de proyectos de sof ### Servidores principales -La red peer-to-peer en el corazón del XRP Ledger requiere de un servidor altamente confiable y eficiente para hacer cumplir las reglas de consenso y el procesamiento de las transacciones. La Fundación XRP Ledger publica una implementación de referencia de este software de sevidor, llamada [**`rippled`**](../concepts/networks-and-servers/index.md) (pronunciado en inglés como "ripple-dee"). El servidor está disponible bajo [una licencia permisiva de código abierto](https://github.com/XRPLF/rippled/blob/develop/LICENSE.md), por lo que cualquiera puede inspeccionar y modificar su propia instancia del servidor, y volver a publicar con pocas restricciones. +La red peer-to-peer en el corazón del XRP Ledger requiere de un servidor altamente confiable y eficiente para hacer cumplir las reglas de consenso y el procesamiento de las transacciones. La Fundación XRP Ledger publica una implementación de referencia de este software de sevidor, llamada [**`rippled`**](../concepts/networks-and-servers/index.md) (pronunciado en inglés como "ripple-dee"). El servidor está disponible bajo [una licencia permisiva de código abierto](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/LICENSE.md), por lo que cualquiera puede inspeccionar y modificar su propia instancia del servidor, y volver a publicar con pocas restricciones. ![Servidores principales](/docs/img/ecosystem-peer-to-peer.svg) diff --git a/@l10n/ja/about/faq.md b/@l10n/ja/about/faq.md index b482cf31490..c8b4d14b736 100644 --- a/@l10n/ja/about/faq.md +++ b/@l10n/ja/about/faq.md @@ -134,7 +134,7 @@ Rippleは Ledgerネットワーク全体のAMLフラグを監視・報告し、 #### サードパーティにより提供されたコードは審査プロセスはどのようになっていますか？ -コードへの貢献のプロセスは、開発者が[`rippled`リポジトリ](https://github.com/xrplf/rippled/)のようなソースコードリポジトリに[プルリクエスト](https://docs.github.com/ja/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)を行うことから始まります。 +コードへの貢献のプロセスは、開発者が[`rippled`リポジトリ](https://github.com/XRPLF/rippled/)のようなソースコードリポジトリに[プルリクエスト](https://docs.github.com/ja/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)を行うことから始まります。 このプルリクエストは、自動化された単体テストと統合テスト、そしてプルリクエストが影響するコード領域で重要な専門知識を持つ複数の開発者によりコードレビューが行われます。 @@ -145,7 +145,7 @@ Rippleは Ledgerネットワーク全体のAMLフラグを監視・報告し、 いいえ、RippleはXRP LedgerまたはXRP Ledgerネットワークを所有も管理もしていません。 -Rippleは、コアとなるXRP Ledgerサーバ（[`rippled`](https://github.com/xrplf/rippled)）のリファレンス実装へ貢献し、オープンソースコードベースに貢献しているエンジニアチームを雇用しています。Rippleはまた、利用可能なソフトウェアのプリコンパイル済みバイナリーパッケージを定期的に公開しています。必要に応じて、誰でも自由に[ソースからソフトウェアをダウンロードしてコンパイル](../docs/infrastructure/installation/index.md)できます。 +Rippleは、コアとなるXRP Ledgerサーバ（[`rippled`](https://github.com/XRPLF/rippled)）のリファレンス実装へ貢献し、オープンソースコードベースに貢献しているエンジニアチームを雇用しています。Rippleはまた、利用可能なソフトウェアのプリコンパイル済みバイナリーパッケージを定期的に公開しています。必要に応じて、誰でも自由に[ソースからソフトウェアをダウンロードしてコンパイル](../docs/infrastructure/installation/index.md)できます。 いくつかの団体が推奨バリデータリスト（UNL）を公開しています。2023年7月現在、RippleはデフォルトのUNLにある35のバリデータのうち1つのみを実行しています。 diff --git a/@l10n/ja/docs/_snippets/clawback-disclaimer.md b/@l10n/ja/docs/_snippets/clawback-disclaimer.md index bc3139d57b4..48a930422a0 100644 --- a/@l10n/ja/docs/_snippets/clawback-disclaimer.md +++ b/@l10n/ja/docs/_snippets/clawback-disclaimer.md @@ -1 +1 @@ -_[Clawback amendment](https://github.com/XRPLF/XRPL-Standards/tree/master/XLS-0039d-clawback)が必要です。_ +_[Clawback amendment](https://github.com/XRPLF/XRPL-Standards/tree/master/XLS-0039-clawback)が必要です。_ diff --git a/@l10n/ja/docs/_snippets/post-rippled-install.md b/@l10n/ja/docs/_snippets/post-rippled-install.md index e6525ae1ea2..3492228a0bf 100644 --- a/@l10n/ja/docs/_snippets/post-rippled-install.md +++ b/@l10n/ja/docs/_snippets/post-rippled-install.md @@ -20,7 +20,7 @@ rippled APIを使用した`rippled`サーバとの通信について詳しくは {% partial file="/@l10n/ja/docs/_snippets/conf-file-location.md" /%} -すべての構成オプションの説明については、[`rippled` GitHubリポジトリー](https://github.com/XRPLF/rippled/blob/master/cfg/rippled-example.cfg)をご覧ください。 +すべての構成オプションの説明については、[`rippled` GitHubリポジトリー](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/cfg/rippled-example.cfg)をご覧ください。 構成の変更を有効にするには、`rippled`を再起動する必要があります。 diff --git a/@l10n/ja/docs/concepts/accounts/addresses.md b/@l10n/ja/docs/concepts/accounts/addresses.md index 09040f28cdb..7ca1bc1edc1 100644 --- a/@l10n/ja/docs/concepts/accounts/addresses.md +++ b/@l10n/ja/docs/concepts/accounts/addresses.md @@ -23,7 +23,7 @@ XRP Ledgerでは、特別な意味や歴史的な役割を持つアドレスが |-------------------------------|-----|-----|----------------| | `rrrrrrrrrrrrrrrrrrrrrhoLvTp` | ACCOUNT\_ZERO | 値0を[base58][]形式にエンコードしたXRP Ledgerのアドレス。ピアツーピア通信では、このアドレスは、XRPの発行者として`rippled`で使用されます。 | はい | | `rrrrrrrrrrrrrrrrrrrrBZbvji` | ACCOUNT\_ONE | 値1を[base58][]形式にエンコードしたXRP Ledgerのアドレス。レジャーの[RippleStateエントリ](../../references/protocol/ledger-data/ledger-entry-types/ripplestate.md)では、このアドレスは、トラストライン残高の発行者のプレースホルダーとして使用されます。 | はい | -| `rHb9CJAWyB4rj91VRWn96DkukG4bwdtyTh` | ジェネシスアカウント | `rippled`で(スタンドアロンモードなど)新しいジェネシスレジャーが一から開始される場合、このアカウントはすべてのXRPを保持します。このアドレスは、シード値`masterpassphrase`から生成されており、この値は[ハードコーディング](https://github.com/XRPLF/rippled/blob/94ed5b3a53077d815ad0dd65d490c8d37a147361/src/ripple/app/ledger/Ledger.cpp#L184)されています。 | いいえ | +| `rHb9CJAWyB4rj91VRWn96DkukG4bwdtyTh` | ジェネシスアカウント | `rippled`で(スタンドアロンモードなど)新しいジェネシスレジャーが一から開始される場合、このアカウントはすべてのXRPを保持します。このアドレスは、シード値`masterpassphrase`から生成されており、この値は[ハードコーディング](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/ledger/Ledger.cpp#L184)されています。 | いいえ | | `rrrrrrrrrrrrrrrrrNAMEtxvNvQ` | Ripple Namesの登録用ブラックホール | 以前、Ripple社は、Ripple Namesを登録するために、このアカウントにXRPを送金するようユーザに求めていました。| はい | | `rrrrrrrrrrrrrrrrrrrn5RM1rHd` | NaNアドレス | 以前のバージョンの[ripple-lib](https://github.com/XRPLF/xrpl.js)では、XRP Ledgerの[base58][]文字列エンコード形式を使用して、値[NaN](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/NaN)をエンコードするときにこのアドレスを生成しました。 | はい | @@ -32,7 +32,7 @@ XRP Ledgerでは、特別な意味や歴史的な役割を持つアドレスが {% admonition type="success" name="ヒント" %}これらの技術的な詳細は、XRP Ledgerとの互換性を保つために低レベルのライブラリソフトウェアを構築しているユーザのみを対象としています!{% /admonition %} -[[ソース]](https://github.com/XRPLF/rippled/blob/35fa20a110e3d43ffc1e9e664fc9017b6f2747ae/src/ripple/protocol/impl/AccountID.cpp#L109-L140 "ソース") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/libxrpl/protocol/AccountID.cpp#L134-L165 "ソース") XRP Ledgerのアドレスは、[base58][]形式の _ディクショナリ_ `rpshnaf39wBUDNEGHJKLM4PQRST7VWXYZ2bcdeCg65jkm8oFqi1tuvAxyz`を使用してエンコードされています。XRP Ledgerはbase58でいくつかのタイプのキーをエンコードするため、それらを区別するためにエンコードされたデータの前に1バイトの「タイプ接頭辞」（「バージョン接頭辞」とも呼ばれます）を付けます。タイプ接頭辞によりアドレスは通常、base58形式の異なる文字で始まります。 diff --git a/@l10n/ja/docs/concepts/accounts/cryptographic-keys.md b/@l10n/ja/docs/concepts/accounts/cryptographic-keys.md index 6ff82314090..3422d0b5d69 100644 --- a/@l10n/ja/docs/concepts/accounts/cryptographic-keys.md +++ b/@l10n/ja/docs/concepts/accounts/cryptographic-keys.md @@ -154,14 +154,14 @@ XRP Ledgerでは、サポートされているさまざまなタイプのキー ここで説明する鍵導出プロセスは、さまざまなプログラミング言語で複数の場所に実装されています。 - C++: `rippled`コードベース: - - [シード定義](https://github.com/XRPLF/rippled/blob/develop/src/ripple/protocol/Seed.h) - - [汎用キー & Ed25519鍵導出](https://github.com/XRPLF/rippled/blob/develop/src/ripple/protocol/impl/SecretKey.cpp) - - [secp256k1鍵導出](https://github.com/XRPLF/rippled/blob/develop/src/ripple/protocol/impl/SecretKey.cpp) + - [シード定義](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/Seed.h) + - [汎用キー & Ed25519鍵導出](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/libxrpl/protocol/SecretKey.cpp) + - [secp256k1鍵導出](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/libxrpl/protocol/SecretKey.cpp) - Python 3: {% repo-link path="_code-samples/key-derivation/py/key_derivation.py" %}このリポジトリのコードサンプルセクション{% /repo-link %} - JavaScript: [`ripple-keypairs`](https://github.com/XRPLF/xrpl.js/tree/main/packages/ripple-keypairs)パッケージ ### Ed25519鍵導出 -[[ソース]](https://github.com/XRPLF/rippled/blob/fc7ecd672a3b9748bfea52ce65996e324553c05f/src/ripple/protocol/impl/SecretKey.cpp#L203 "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/libxrpl/protocol/SecretKey.cpp#L313 "Source") [{% inline-svg file="/docs/img/key-derivation-ed25519.ja.svg" /%}](/docs/img/key-derivation-ed25519.ja.svg "パスフレーズ → シード → 秘密鍵 → プレフィクス + 公開鍵") @@ -182,7 +182,7 @@ XRP Ledgerでは、サポートされているさまざまなタイプのキー バリデータの一時キーにEd25519を使用することはできません。 ### secp256k1鍵導出 -[[ソース]](https://github.com/XRPLF/rippled/blob/develop/src/ripple/protocol/impl/SecretKey.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/libxrpl/protocol/SecretKey.cpp "Source") [{% inline-svg file="/docs/img/key-derivation-secp256k1.ja.svg" /%}](/docs/img/key-derivation-secp256k1.ja.svg "パスフレーズ → シード → ルートキーペア → 仲介銀行（機関）キーペア → マスターキーペア") diff --git a/@l10n/ja/docs/concepts/consensus-protocol/consensus-structure.md b/@l10n/ja/docs/concepts/consensus-protocol/consensus-structure.md index 69e6731f407..f19905cc2dd 100644 --- a/@l10n/ja/docs/concepts/consensus-protocol/consensus-structure.md +++ b/@l10n/ja/docs/concepts/consensus-protocol/consensus-structure.md @@ -107,7 +107,7 @@ _図5: バリデータによるトランザクションセットの提案と修 2. すべてのサーバが同じ方法で処理できるように、合意済みのトランザクションセットを _正規順序_ で並べ変えます。 - [正規順序](https://github.com/XRPLF/rippled/blob/8429dd67e60ba360da591bfa905b58a35638fda1/src/ripple/app/misc/CanonicalTXSet.cpp#L25-L36)は、トランザクションを受け取った順序ではありません（サーバが同じトランザクションを異なる順序で受け取る可能性があるため）。参加者がトランザクションの順序付けで競合しないように、故意に操作するのが困難な正規順序を使います。 + [正規順序](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/misc/CanonicalTXSet.cpp#L24-L40)は、トランザクションを受け取った順序ではありません（サーバが同じトランザクションを異なる順序で受け取る可能性があるため）。参加者がトランザクションの順序付けで競合しないように、故意に操作するのが困難な正規順序を使います。 3. 指示に従って、各トランザクションを順番に処理します。それに応じてレジャーの状態データを更新します。 diff --git a/@l10n/ja/docs/concepts/consensus-protocol/invariant-checking.md b/@l10n/ja/docs/concepts/consensus-protocol/invariant-checking.md index f192613a611..4a462cb21c1 100644 --- a/@l10n/ja/docs/concepts/consensus-protocol/invariant-checking.md +++ b/@l10n/ja/docs/concepts/consensus-protocol/invariant-checking.md @@ -38,39 +38,39 @@ labels: XRP Ledgerは、各トランザクションについて、以下のすべての不変条件をチェックします。 -[[ソース]](https://github.com/XRPLF/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h#L92 "ソース") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/InvariantCheck.h#L92 "ソース") - [トランザクション手数料チェック](#トランザクション手数料チェック) -[[ソース]](https://github.com/XRPLF/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h#L118 "ソース") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/InvariantCheck.h#L118 "ソース") - [XRPは作成されません](#xrpは作成されません) -[[ソース]](https://github.com/XRPLF/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h#L146 "ソース") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/InvariantCheck.h#L146 "ソース") - [アカウントルートが削除されていない](#アカウントルートが削除されていない) -[[ソース]](https://github.com/XRPLF/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h#L173 "ソース") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/InvariantCheck.h#L203 "ソース") - [XRPの残高確認](#xrpの残高確認) -[[ソース]](https://github.com/XRPLF/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h#L197 "ソース") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/InvariantCheck.h#L227 "ソース") - [レジャーエントリ形式の一致](#レジャーエントリ形式の一致) -[[ソース]](https://github.com/XRPLF/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h#L224 "ソース") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/InvariantCheck.h#L254 "ソース") - [XRPのトラストラインはありません](#xrpのトラストラインはありません) -[[ソース]](https://github.com/XRPLF/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h#L251 "ソース") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/InvariantCheck.h#L389 "ソース") - [不正なオファーでない](#不正なオファーでない) -[[ソース]](https://github.com/XRPLF/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h#L275 "ソース") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/InvariantCheck.h#L413 "ソース") - [0のエスクローでない](#0のエスクローでない) -[[ソース]](https://github.com/XRPLF/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h#L300 "ソース") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/InvariantCheck.h#L438 "ソース") - [有効な新規アカウントルート](#有効な新規アカウントルート) @@ -138,11 +138,11 @@ XRP Ledgerは、各トランザクションについて、以下のすべての - [レジャーの保護: 不変性チェック](https://xrpl.org/blog/2017/invariant-checking.html) - **リポジトリ:** - - [Invariant Check.h](https://github.com/XRPLF/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h) - - [Invariant Check.cpp](https://github.com/XRPLF/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.cpp) - - [System Parameters](https://github.com/XRPLF/rippled/blob/develop/src/ripple/protocol/SystemParameters.h#L43) - - [XRP Amount](https://github.com/XRPLF/rippled/blob/develop/src/ripple/basics/XRPAmount.h#L244) - - [Ledger Formats](https://github.com/XRPLF/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/protocol/LedgerFormats.h#L36-L94) + - [Invariant Check.h](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/InvariantCheck.h) + - [Invariant Check.cpp](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/InvariantCheck.cpp) + - [System Parameters](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/SystemParameters.h#L44) + - [XRP Amount](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/XRPAmount.h#L252) + - [Ledger Formats](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/LedgerFormats.h#L53-L117) - **その他:** diff --git a/@l10n/ja/docs/concepts/networks-and-servers/peer-protocol.md b/@l10n/ja/docs/concepts/networks-and-servers/peer-protocol.md index 4a7d15d01a5..b4e01a5487d 100644 --- a/@l10n/ja/docs/concepts/networks-and-servers/peer-protocol.md +++ b/@l10n/ja/docs/concepts/networks-and-servers/peer-protocol.md @@ -18,11 +18,11 @@ XRP Ledgerのサーバは、XRP Ledgerピアプロトコル（RTXP）を使用 - 履歴レジャーへのレジャーデータのリクエスト、またはレジャーデータの提供。 - コンセンサスのための一連のトランザクションの提示、またはコンセンサストランザクションセットの適用に関する算出結果の共有。 -ピアツーピア接続を確立するには、サーバどうしをHTTPSで接続し、一方のサーバはRTXPへの切り替えのために[HTTPアップグレード](https://tools.ietf.org/html/rfc7230#section-6.7)をリクエストします。（詳細は、[`rippled`リポジトリ](https://github.com/XRPLF/rippled)の[Overlay Network](https://github.com/XRPLF/rippled/blob/906ef761bab95f80b0a7e0cab3b4c594b226cf57/src/ripple/overlay/README.md#handshake)をご覧ください。） +ピアツーピア接続を確立するには、サーバどうしをHTTPSで接続し、一方のサーバはRTXPへの切り替えのために[HTTPアップグレード](https://tools.ietf.org/html/rfc7230#section-6.7)をリクエストします。（詳細は、[`rippled`リポジトリ](https://github.com/XRPLF/rippled)の[Overlay Network](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/overlay/README.md#handshake)をご覧ください。） ## ピアの検出 -XRP Ledgerでは、「ゴシップ」プロトコルを使用して、XRP Ledgerネットワーク内でサーバが互いを識別できるようにします。サーバは、起動するたびに、以前に接続したその他のあらゆるピアに再接続します。フォールバックとして、[ハードコーディングされた公開ハブ](https://github.com/XRPLF/rippled/blob/fa57859477441b60914e6239382c6fba286a0c26/src/ripple/overlay/impl/OverlayImpl.cpp#L518-L525)を使用します。サーバがピアに正常に接続されると、ピアを探している他のXRP Ledgerサーバの接続情報（通常はIPアドレスとポート）をそのピアにリクエストします。その後、サーバはそれらのサーバに接続し、ピア接続するXRP Ledgerサーバの接続情報をさらにリクエストできます。このプロセスにより、サーバは十分なピア接続を確立し、単一のピアへの接続が失われた場合でも、ネットワークの残りの部分にその後も接続されます。 +XRP Ledgerでは、「ゴシップ」プロトコルを使用して、XRP Ledgerネットワーク内でサーバが互いを識別できるようにします。サーバは、起動するたびに、以前に接続したその他のあらゆるピアに再接続します。フォールバックとして、[ハードコーディングされた公開ハブ](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/overlay/detail/OverlayImpl.h#L494-L509)を使用します。サーバがピアに正常に接続されると、ピアを探している他のXRP Ledgerサーバの接続情報（通常はIPアドレスとポート）をそのピアにリクエストします。その後、サーバはそれらのサーバに接続し、ピア接続するXRP Ledgerサーバの接続情報をさらにリクエストできます。このプロセスにより、サーバは十分なピア接続を確立し、単一のピアへの接続が失われた場合でも、ネットワークの残りの部分にその後も接続されます。 通常、サーバが公開ハブに接続する必要があるのは1回のみです。他のピアを見つけるために、短時間のみ接続します。そうすることで、ネットワーク接続の安定性、ハブのビジー状態、およびサーバが検出する他の高品質ピアの数に応じて、ハブにサーバを引き続き接続するかどうかが異なります。サーバでは、これらの他のピアのアドレスを保存するため、ネットワークの停止後または再起動後、それらのピアへの直接再接続を試行できます。 @@ -37,7 +37,7 @@ XRP Ledgerに参加するため、`rippled`サーバはピアプロトコルを サーバがピアポートで接続を送信 _かつ_ 受信できることが理想的です。`rippled`サーバに、[ファイアウォール経由でピアプロトコルに使用するポートを転送する](../../infrastructure/configuration/peering/forward-ports-for-peering.md)必要があります。 -[デフォルトの`rippled`構成ファイル](https://github.com/XRPLF/rippled/blob/master/cfg/rippled-example.cfg)は、すべてのネットワークインターフェイスにおいて、ポート51235で着信ピアプロトコル接続をリッスンします。使用するポートを変更するには、`rippled.cfg`ファイル内の該当するスタンザを編集します。 +[デフォルトの`rippled`構成ファイル](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/cfg/rippled-example.cfg)は、すべてのネットワークインターフェイスにおいて、ポート51235で着信ピアプロトコル接続をリッスンします。使用するポートを変更するには、`rippled.cfg`ファイル内の該当するスタンザを編集します。 例: diff --git a/@l10n/ja/docs/concepts/tokens/decentralized-exchange/offers.md b/@l10n/ja/docs/concepts/tokens/decentralized-exchange/offers.md index 7f486ccfb4d..3412a1d378b 100644 --- a/@l10n/ja/docs/concepts/tokens/decentralized-exchange/offers.md +++ b/@l10n/ja/docs/concepts/tokens/decentralized-exchange/offers.md @@ -81,7 +81,7 @@ Offerオブジェクトは、他のオファーやクロスカレンシー決済 台帳内のOfferオブジェクトは取引レートによってグループにまとめられます。取引レートは、`TakerGets`と`TakerPays`の比率として計算されます。取引レートが高いOfferオブジェクトが優先的に処理されます。（つまり、オファーを約定する人は、支払われる通貨額に対して可能な限り多くの額を受領します。）同じ取引レートのオファーは、オファーの作成タイミングを基準にして処理されます。 -同じ取引レートのOfferオブジェクトが同じ台帳ブロックに記録されている場合、オファーの処理順序は[レジャーへトランザクションを適用する](https://github.com/XRPLF/rippled/blob/5425a90f160711e46b2c1f1c93d68e5941e4bfb6/src/ripple/app/consensus/LedgerConsensus.cpp#L1435-L1538 "Source Code: Applying transactions")ための[正規順序](https://github.com/XRPLF/rippled/blob/release/src/ripple/app/misc/CanonicalTXSet.cpp "Source Code: Transaction ordering")によって決定します。この動作は確定的かつ効率的であり、操作することが困難であるように設計されています。 +同じ取引レートのOfferオブジェクトが同じ台帳ブロックに記録されている場合、オファーの処理順序は[レジャーへトランザクションを適用する](https://github.com/XRPLF/rippled/blob/5425a90f160711e46b2c1f1c93d68e5941e4bfb6/src/ripple/app/consensus/LedgerConsensus.cpp#L1435-L1538 "Source Code: Applying transactions")ための[正規順序](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/misc/CanonicalTXSet.cpp "Source Code: Transaction ordering")によって決定します。この動作は確定的かつ効率的であり、操作することが困難であるように設計されています。 ## オファーの有効期限 diff --git a/@l10n/ja/docs/concepts/tokens/fungible-tokens/index.md b/@l10n/ja/docs/concepts/tokens/fungible-tokens/index.md index dbb35ea5545..f2a7545ce00 100644 --- a/@l10n/ja/docs/concepts/tokens/fungible-tokens/index.md +++ b/@l10n/ja/docs/concepts/tokens/fungible-tokens/index.md @@ -72,7 +72,7 @@ labels: **Authorized** の設定は、一度オンにするとオフにできないため、トラストラインの初期状態にはカウントされません。 ## 無料のトラストライン -[[Source]](https://github.com/XRPLF/rippled/blob/72377e7bf25c4eaee5174186d2db3c6b4210946f/src/ripple/app/tx/impl/SetTrust.cpp#L148-L168) +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/SetTrust.cpp#L387-L407) トラストラインはXRP Ledgerの強力な機能であるため、アカウントの最初の2つのトラストラインを「無料」にする特別な機能が用意されています。 diff --git a/@l10n/ja/docs/concepts/transactions/secure-signing.md b/@l10n/ja/docs/concepts/transactions/secure-signing.md index bf66fd8b172..e761cc98745 100644 --- a/@l10n/ja/docs/concepts/transactions/secure-signing.md +++ b/@l10n/ja/docs/concepts/transactions/secure-signing.md @@ -46,7 +46,7 @@ labels: 2. トランザクションに署名する必要がある場合は、`localhost`または`127.0.0.1`のサーバに接続します。シングル署名の場合は[signメソッド][]、マルチシグの場合は[sign_forメソッド][]を使用します。 - [構成ファイルの例](https://github.com/XRPLF/rippled/blob/8429dd67e60ba360da591bfa905b58a35638fda1/cfg/rippled-example.cfg#L1050-L1073)では、ローカルループバックネットワーク上（127.0.0.1）のポート5005でJSON-RPC（HTTP）、ポート6006でWebSocket（WS）の接続をリッスンし、接続されるすべてのクライアントを管理者として扱っています。 + [構成ファイルの例](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/cfg/rippled-example.cfg#L1414-L1448)では、ローカルループバックネットワーク上（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 %} diff --git a/@l10n/ja/docs/concepts/transactions/transaction-cost.md b/@l10n/ja/docs/concepts/transactions/transaction-cost.md index b15471ded49..0481b715a20 100644 --- a/@l10n/ja/docs/concepts/transactions/transaction-cost.md +++ b/@l10n/ja/docs/concepts/transactions/transaction-cost.md @@ -64,7 +64,7 @@ XRP LedgerをスパムやDoS攻撃から守るため、各トランザクショ オープンレジャーコストの水準は、絶対的なトランザクションコストではなく[標準的なトランザクションコストに比例](#手数料レベル)しています。標準よりも高い要件を持つトランザクションタイプ（[マルチシグトランザクション](../accounts/multi-signing.md)など）は、オープンレジャーコストを満たすために最低限のトランザクションコスト要件を持つトランザクションよりも多く支払う必要があります。 -関連項目: [`rippled`リポジトリー内のFee Escalationの説明](https://github.com/XRPLF/rippled/blob/release/src/ripple/app/misc/FeeEscalation.md)。 +関連項目: [`rippled`リポジトリー内のFee Escalationの説明](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/misc/FeeEscalation.md)。 ### キューに入れられたトランザクション diff --git a/@l10n/ja/docs/infrastructure/configuration/data-retention/configure-history-sharding.md b/@l10n/ja/docs/infrastructure/configuration/data-retention/configure-history-sharding.md index 24792d2b7cc..c6b94f21722 100644 --- a/@l10n/ja/docs/infrastructure/configuration/data-retention/configure-history-sharding.md +++ b/@l10n/ja/docs/infrastructure/configuration/data-retention/configure-history-sharding.md @@ -46,7 +46,7 @@ max_size_gb=50 {% admonition type="warning" name="注意" %}`rippled`がシャードストアーパスで不適切なデータを検出すると、[起動できない](../../troubleshooting/server-wont-start.md)可能性があります。シャードストアーには新しいフォルダーを使用する必要があります。以前にRocksDBシャードストアー（`rippled` 1.2.x以前）を使用していた場合は、別のパスを使用するか、RocksDBシャードデータを削除します。{% /admonition %} -詳細は、[rippled.cfgの設定例](https://github.com/XRPLF/rippled/blob/master/cfg/rippled-example.cfg)の`[shard_db]`の例をご覧ください。 +詳細は、[rippled.cfgの設定例](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/cfg/rippled-example.cfg)の`[shard_db]`の例をご覧ください。 ## 3. サーバの再起動 diff --git a/@l10n/ja/docs/infrastructure/configuration/data-retention/online-deletion.md b/@l10n/ja/docs/infrastructure/configuration/data-retention/online-deletion.md index 4cc043aac77..d50d4e29605 100644 --- a/@l10n/ja/docs/infrastructure/configuration/data-retention/online-deletion.md +++ b/@l10n/ja/docs/infrastructure/configuration/data-retention/online-deletion.md @@ -8,7 +8,7 @@ labels: - コアサーバ --- # オンライン削除 -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/app/misc/SHAMapStoreImp.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/misc/SHAMapStoreImp.cpp "Source") オンライン削除機能により、`rippled`サーバはレジャーの古いバージョンのローカルコピーを削除できます。これにより、時間とともにディスク使用量が急増しないようにできます。デフォルトの構成ファイルにはオンライン削除の自動実行が設定されていますが、指示があった場合にのみオンライン削除を実行するようにも設定できます。{% badge href="https://github.com/XRPLF/rippled/releases/tag/0.27.0" %}新規: rippled 0.27.0{% /badge %} diff --git a/@l10n/ja/docs/infrastructure/configuration/peering/cluster-rippled-servers.md b/@l10n/ja/docs/infrastructure/configuration/peering/cluster-rippled-servers.md index 080ec654e35..e24429513e4 100644 --- a/@l10n/ja/docs/infrastructure/configuration/peering/cluster-rippled-servers.md +++ b/@l10n/ja/docs/infrastructure/configuration/peering/cluster-rippled-servers.md @@ -33,7 +33,7 @@ labels: 各レスポンスの`validation_seed`パラメーターと`validation_public_key`パラメーターを安全な場所に保存します。 -3. 各サーバで[構成ファイル](https://github.com/XRPLF/rippled/blob/master/cfg/rippled-example.cfg)を編集し、以下のセクションを変更します。 +3. 各サーバで[構成ファイル](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/cfg/rippled-example.cfg)を編集し、以下のセクションを変更します。 1. `[ips_fixed]`セクションに、クラスターの _その他の_ 各メンバーのIPアドレスとポートを記入します。各サーバのポート番号は、サーバの `rippled.cfg`に指定されている`protocol = peer`ポート（通常は51235）と一致している必要があります。例: diff --git a/@l10n/ja/docs/infrastructure/configuration/server-modes/run-rippled-as-a-validator.md b/@l10n/ja/docs/infrastructure/configuration/server-modes/run-rippled-as-a-validator.md index 71e23bd1616..cebe9a756f5 100644 --- a/@l10n/ja/docs/infrastructure/configuration/server-modes/run-rippled-as-a-validator.md +++ b/@l10n/ja/docs/infrastructure/configuration/server-modes/run-rippled-as-a-validator.md @@ -51,7 +51,7 @@ top_nav_name: UNLに参加しよう 優れたバリデータには、身元が明確な所有者が存在します。[ドメイン検証](#6-ドメイン検証の提供)を提供することは、その第一歩になります。XRP LedgerネットワークのUNLに、多くの法的な管轄域および地域のさまざまな所有者によって運営されているバリデータが含まれていると理想的です。結果として、信頼できるバリデータの公正な運用が地域特有の事象によって損なわれるおそれが低減されます。 -運用者は[exampleファイル](https://github.com/XRPLF/rippled/blob/develop/cfg/validators-example.txt)に存在するバリデータリストを使用することを強くお勧めします。 +運用者は[exampleファイル](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/cfg/validators-example.txt)に存在するバリデータリストを使用することを強くお勧めします。 @@ -162,7 +162,7 @@ top_nav_name: UNLに参加しよう この構成では、[検出されたピア](../../../concepts/networks-and-servers/peer-protocol.md#ピアの検出)を使用してバリデータをXRP Ledgerネットワークに接続します。これは`rippled`サーバのデフォルトの動作です。 -_**検出されたピアを使用してバリデータをXRP Ledgerネットワークに接続するには、**_ バリデータの`rippled.cfg`ファイルで`[peer_private]`スタンザを省略するか、それを`0`に設定します。この構成の[サンプルのrippled.cfgファイル](https://github.com/XRPLF/rippled/blob/develop/cfg/rippled-example.cfg)が提供されています。 +_**検出されたピアを使用してバリデータをXRP Ledgerネットワークに接続するには、**_ バリデータの`rippled.cfg`ファイルで`[peer_private]`スタンザを省略するか、それを`0`に設定します。この構成の[サンプルのrippled.cfgファイル](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/cfg/rippled-example.cfg)が提供されています。 ### プロキシを使用した接続 diff --git a/@l10n/ja/docs/infrastructure/installation/build-on-linux-mac-windows.md b/@l10n/ja/docs/infrastructure/installation/build-on-linux-mac-windows.md index 27b69344614..a6fc115b13d 100644 --- a/@l10n/ja/docs/infrastructure/installation/build-on-linux-mac-windows.md +++ b/@l10n/ja/docs/infrastructure/installation/build-on-linux-mac-windows.md @@ -12,6 +12,6 @@ top_nav_grouping: 人気ページ Windows、Linux、macOSなど様々なプラットフォームで`rippled`をビルドするには、C++開発環境が必要です。Git、Python、Conan、CMake、そして適切なC++コンパイラなどのツールが必要です。 -続きを読むには、[GitHubの最新の`rippled`ビルド手順](https://github.com/XRPLF/rippled/blob/develop/BUILD.md)をご覧ください。 +続きを読むには、[GitHubの最新の`rippled`ビルド手順](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/BUILD.md)をご覧ください。 {% raw-partial file="/docs/_snippets/common-links.md" /%} diff --git a/@l10n/ja/docs/infrastructure/installation/build-run-rippled-in-reporting-mode.md b/@l10n/ja/docs/infrastructure/installation/build-run-rippled-in-reporting-mode.md index e0bc5e5e6ca..112a8b016ac 100644 --- a/@l10n/ja/docs/infrastructure/installation/build-run-rippled-in-reporting-mode.md +++ b/@l10n/ja/docs/infrastructure/installation/build-run-rippled-in-reporting-mode.md @@ -113,7 +113,7 @@ NuDBは`rippled`ビルドセットアップの一部としてインストール ### 手順 -1. [UbuntuまたはmacOS](https://github.com/XRPLF/rippled/blob/release/BUILD.md)のレポートモード用に`rippled`をビルド。 +1. [UbuntuまたはmacOS](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/BUILD.md)のレポートモード用に`rippled`をビルド。 {% tabs %} diff --git a/@l10n/ja/docs/infrastructure/installation/capacity-planning.md b/@l10n/ja/docs/infrastructure/installation/capacity-planning.md index 6da47b480a6..42356a7ba26 100644 --- a/@l10n/ja/docs/infrastructure/installation/capacity-planning.md +++ b/@l10n/ja/docs/infrastructure/installation/capacity-planning.md @@ -21,7 +21,7 @@ XRP Ledgerのサーバの負荷は、複数の要因によって変化します デフォルトの設定ファイルには、一般的なユースケースを幅広くカバーする設定が含まれています。お使いのハードウェアや使用目的に合わせて設定をカスタマイズすることで、より良いパフォーマンスを得ることができます。 -本セクションでの設定は、`rippled.cfg`ファイルのパラメータです。設定ファイルの例である `rippled-example.cfg` は、`rippled` GitHubリポジトリ の [`cfg` ディレクトリ](https://github.com/XRPLF/rippled/blob/develop/cfg/rippled-example.cfg)からアクセスできます。サンプル設定ファイルの設定は、サーバと一緒にインストールされたデフォルトの設定と一致しています。 +本セクションでの設定は、`rippled.cfg`ファイルのパラメータです。設定ファイルの例である `rippled-example.cfg` は、`rippled` GitHubリポジトリ の [`cfg` ディレクトリ](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/cfg/rippled-example.cfg)からアクセスできます。サンプル設定ファイルの設定は、サーバと一緒にインストールされたデフォルトの設定と一致しています。 ### ノードサイズ diff --git a/@l10n/ja/docs/infrastructure/installation/install-clio-on-ubuntu.md b/@l10n/ja/docs/infrastructure/installation/install-clio-on-ubuntu.md index 57be1c6f1f0..fc40f2023f9 100644 --- a/@l10n/ja/docs/infrastructure/installation/install-clio-on-ubuntu.md +++ b/@l10n/ja/docs/infrastructure/installation/install-clio-on-ubuntu.md @@ -138,7 +138,7 @@ Clioをインストールする前に、以下の条件を満たしている必 {% admonition type="info" name="注記" %}`etl_sources`セクションに項目を追加することで、複数の`rippled`サーバをデータソースとして使用することができます。そうすると、Clioはリスト内のすべてのサーバでリクエストを負荷分散し、少なくとも`rippled`サーバの一つが同期している限り、ネットワークに追いつくことができます。{% /admonition %} - [設定ファイル例](https://github.com/XRPLF/clio/blob/develop/example-config.json)は、ローカルのループバックネットワーク(127.0.0.1)上で動作している`rippled`サーバに、ポート6006のWebSocket(WS)とポート50051のgRPCでアクセスします。 + [設定ファイル例](https://github.com/XRPLF/clio/blob/develop/docs/examples/config/example-config.json)は、ローカルのループバックネットワーク(127.0.0.1)上で動作している`rippled`サーバに、ポート6006のWebSocket(WS)とポート50051のgRPCでアクセスします。 2. Clioサーバが接続できるように`rippled`サーバの設定ファイルを更新します。パッケージはこのファイルを`/etc/opt/ripple/rippled.cfg`にインストールします。 diff --git a/@l10n/ja/docs/infrastructure/testing-and-auditing/start-a-new-genesis-ledger-in-stand-alone-mode.md b/@l10n/ja/docs/infrastructure/testing-and-auditing/start-a-new-genesis-ledger-in-stand-alone-mode.md index e94b78b30c4..82b8aa4b4d8 100644 --- a/@l10n/ja/docs/infrastructure/testing-and-auditing/start-a-new-genesis-ledger-in-stand-alone-mode.md +++ b/@l10n/ja/docs/infrastructure/testing-and-auditing/start-a-new-genesis-ledger-in-stand-alone-mode.md @@ -18,7 +18,7 @@ rippled -a --start --conf=/path/to/rippled.cfg スタンドアロンモードで`rippled`を起動時に使用できるオプションについての詳細は、[コマンドラインの使用リファレンスのスタンドアロンモードのオプション](../commandline-usage.md#スタンドアロンモードのオプション)をご覧ください。 -ジェネシスレジャーの[ジェネシスアドレス](../../concepts/accounts/addresses.md#特別なアドレス)は1,000億XRPすべてを保有しています。ジェネシスアドレスのキーは以下のように[ハードコーディング](https://github.com/XRPLF/rippled/blob/94ed5b3a53077d815ad0dd65d490c8d37a147361/src/ripple/app/ledger/Ledger.cpp#L184)されています。 +ジェネシスレジャーの[ジェネシスアドレス](../../concepts/accounts/addresses.md#特別なアドレス)は1,000億XRPすべてを保有しています。ジェネシスアドレスのキーは以下のように[ハードコーディング](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/ledger/Ledger.cpp#L184)されています。 **アドレス:** `rHb9CJAWyB4rj91VRWn96DkukG4bwdtyTh` diff --git a/@l10n/ja/docs/infrastructure/troubleshooting/diagnosing-problems.md b/@l10n/ja/docs/infrastructure/troubleshooting/diagnosing-problems.md index f8d03a2c424..94bc5e090c6 100644 --- a/@l10n/ja/docs/infrastructure/troubleshooting/diagnosing-problems.md +++ b/@l10n/ja/docs/infrastructure/troubleshooting/diagnosing-problems.md @@ -90,7 +90,7 @@ rippled server_info - ピアの数が0の場合、サーバがネットワークに接続できないか、またはシステムクロックが正しくない可能性があります。（サーバのクロックを同期するため、すべてのサーバで[NTP](http://www.ntp.org/)デーモンを実行することが推奨されます。） - - ピアの数が10の場合、`rippled`が[NAT](https://en.wikipedia.org/wiki/Network_address_translation)を使用したルーター経由での着信接続を受信できていない可能性があります。接続を改善するには、ルーターのファイアウォールがピアツーピア接続に使用するポート（[デフォルトでは](https://github.com/XRPLF/rippled/blob/8429dd67e60ba360da591bfa905b58a35638fda1/cfg/rippled-example.cfg#L1065)ポート51235）を転送するように設定します。 + - ピアの数が10の場合、`rippled`が[NAT](https://en.wikipedia.org/wiki/Network_address_translation)を使用したルーター経由での着信接続を受信できていない可能性があります。接続を改善するには、ルーターのファイアウォールがピアツーピア接続に使用するポート（[デフォルトでは](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/cfg/rippled-example.cfg#L1432)ポート51235）を転送するように設定します。 ### サーバからレスポンスがない場合 @@ -113,7 +113,7 @@ rippled server_info ## サーバログの確認 -[デフォルトでは](https://github.com/XRPLF/rippled/blob/master/cfg/rippled-example.cfg#L1139-L1142)`rippled`はサーバのデバッグログを`/var/log/rippled/debug.log`ファイルに書き込みます。このデバッグログの位置は、サーバの構成ファイルにより異なる可能性があります。`rippled`サービスを（`systemctl`または`service`を使用して開始するのではなく）直接開始した場合、デフォルトではログメッセージはコンソールにも出力されます。 +[デフォルトでは](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/cfg/rippled-example.cfg#L1481-L1484)`rippled`はサーバのデバッグログを`/var/log/rippled/debug.log`ファイルに書き込みます。このデバッグログの位置は、サーバの構成ファイルにより異なる可能性があります。`rippled`サービスを（`systemctl`または`service`を使用して開始するのではなく）直接開始した場合、デフォルトではログメッセージはコンソールにも出力されます。 デフォルトの構成ファイルでは、起動時に[log_levelメソッド][]を内部で使用して、すべてのログメッセージカテゴリでログレベルの重大度は「警告」に設定されています。デバッグログの詳細レベルを制御するには、[起動時に`--silent`コマンドラインオプションを使用し](../commandline-usage.md#詳細レベルのオプション)、サーバの稼働中に[log_levelメソッド][]を使用します。（設定については構成ファイルの`[rpc_startup]`スタンザをご覧ください。） diff --git a/@l10n/ja/docs/infrastructure/troubleshooting/fix-sqlite-tx-db-page-size-issue.md b/@l10n/ja/docs/infrastructure/troubleshooting/fix-sqlite-tx-db-page-size-issue.md index 42c17d2385e..4ee809210bc 100644 --- a/@l10n/ja/docs/infrastructure/troubleshooting/fix-sqlite-tx-db-page-size-issue.md +++ b/@l10n/ja/docs/infrastructure/troubleshooting/fix-sqlite-tx-db-page-size-issue.md @@ -28,7 +28,7 @@ SQLiteデータベースの容量は、データベースの _ページサイズ いずれの場合でも、問題を検出するには`rippled`のサーバログへのアクセスが必要です。 -{% admonition type="success" name="ヒント" %}このデバッグログの位置は、`rippled`サーバの構成ファイルの設定に応じて異なる可能性があります。[デフォルトの構成](https://github.com/XRPLF/rippled/blob/master/cfg/rippled-example.cfg#L1139-L1142)では、サーバのデバッグログは`/var/log/rippled/debug.log`ファイルに書き込まれます。{% /admonition %} +{% admonition type="success" name="ヒント" %}このデバッグログの位置は、`rippled`サーバの構成ファイルの設定に応じて異なる可能性があります。[デフォルトの構成](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/cfg/rippled-example.cfg#L1481-L1484)では、サーバのデバッグログは`/var/log/rippled/debug.log`ファイルに書き込まれます。{% /admonition %} ### 事前の検出 diff --git a/@l10n/ja/docs/infrastructure/troubleshooting/server-wont-start.md b/@l10n/ja/docs/infrastructure/troubleshooting/server-wont-start.md index 8cad238be24..ffbe9f017b3 100644 --- a/@l10n/ja/docs/infrastructure/troubleshooting/server-wont-start.md +++ b/@l10n/ja/docs/infrastructure/troubleshooting/server-wont-start.md @@ -68,7 +68,7 @@ Aborted (core dumped) - `rippled`ユーザが読み取ることができる構成ファイルを`$HOME/.config/ripple/rippled.cfg`に作成します（`$HOME`は`rippled`ユーザのホームディレクトリを指しています）。 - {% admonition type="success" name="ヒント" %}`rippled`リポジトリには、パケージのインストール時にデフォルトの構成として提供される[`rippled.cfg`サンプルファイル](https://github.com/XRPLF/rippled/blob/master/cfg/rippled-example.cfg)が含まれています。このファイルがない場合は、上記のリンク先からコピーできます。{% /admonition %} + {% admonition type="success" name="ヒント" %}`rippled`リポジトリには、パケージのインストール時にデフォルトの構成として提供される[`rippled.cfg`サンプルファイル](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/cfg/rippled-example.cfg)が含まれています。このファイルがない場合は、上記のリンク先からコピーできます。{% /admonition %} - `--conf`[コマンドラインオプション](../commandline-usage.md)を使用して、使用する構成ファイルのパスを指定します。 @@ -86,7 +86,7 @@ Aborted (core dumped) - `validators.txt`ファイルが存在し、`rippled`ユーザにこのファイルの読み取り権限があることを確認します。 - {% admonition type="success" name="ヒント" %}`rippled`リポジトリには、パケージのインストール時にデフォルトの構成として提供される[`validators.txt`サンプルファイル](https://github.com/XRPLF/rippled/blob/master/cfg/validators-example.txt)が含まれています。このファイルがない場合は、上記のリンク先からコピーできます。{% /admonition %} + {% admonition type="success" name="ヒント" %}`rippled`リポジトリには、パケージのインストール時にデフォルトの構成として提供される[`validators.txt`サンプルファイル](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/cfg/validators-example.txt)が含まれています。このファイルがない場合は、上記のリンク先からコピーできます。{% /admonition %} - `rippled.cfg`ファイルを編集し、`[validators_file]`設定を変更して、`validators.txt`ファイル（またはこれに相当するファイル）の正しいパスを指定します。ファイル名の前後に余分な空白があるかどうかを確認します。 diff --git a/@l10n/ja/docs/introduction/software-ecosystem.md b/@l10n/ja/docs/introduction/software-ecosystem.md index a4701d7c0bf..75972150165 100644 --- a/@l10n/ja/docs/introduction/software-ecosystem.md +++ b/@l10n/ja/docs/introduction/software-ecosystem.md @@ -24,7 +24,7 @@ XRP Ledgerは、価値のインターネットを実現するソフトウェア ### コアサーバ -XRP Ledgerの中心であるピアツーピアネットワークは、コンセンサスとトランザクションプロセスのルールを実行するために、信頼性が高く、効率のよいサーバを必要とします。XRP Ledger財団では、このサーバソフトウェアのリファレンス実装である[**`rippled`**](../concepts/networks-and-servers/index.md)(発音は「リップルディー」)を公開しています。このサーバは、[一般利用が可能なオープンソースライセンス](https://github.com/XRPLF/rippled/blob/develop/LICENSE.md)の下で使用できるため、誰でもこのサーバの自身のインスタンスを検証し、変更することができます。また、いくつかの制限の下でそれを再公開することができます。 +XRP Ledgerの中心であるピアツーピアネットワークは、コンセンサスとトランザクションプロセスのルールを実行するために、信頼性が高く、効率のよいサーバを必要とします。XRP Ledger財団では、このサーバソフトウェアのリファレンス実装である[**`rippled`**](../concepts/networks-and-servers/index.md)(発音は「リップルディー」)を公開しています。このサーバは、[一般利用が可能なオープンソースライセンス](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/LICENSE.md)の下で使用できるため、誰でもこのサーバの自身のインスタンスを検証し、変更することができます。また、いくつかの制限の下でそれを再公開することができます。 ![コアサーバ](/docs/img/ecosystem-peer-to-peer.svg) diff --git a/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/key-generation-methods/validation_create.md b/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/key-generation-methods/validation_create.md index 43db59909b2..84b76a575de 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/key-generation-methods/validation_create.md +++ b/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/key-generation-methods/validation_create.md @@ -8,7 +8,7 @@ labels: - コアサーバ --- # validation_create -[[ソース]](https://github.com/XRPLF/rippled/blob/315a8b6b602798a4cff4d8e1911936011e12abdb/src/ripple/rpc/handlers/ValidationCreate.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/ValidationCreate.cpp "Source") `validation_create`コマンドキーを使用して、[`rippled`サーバがネットワークに対して自身の身元を識別させるのに使用できる暗号鍵](../../../../concepts/networks-and-servers/peer-protocol.md#ノードキーペア)を生成します。[wallet_proposeメソッド][]と同様に、このメソッドでは適切なフォーマットで一連のキーが単に生成されるだけです。XRP Ledgerのデータやサーバ構成は変更されません。 diff --git a/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/key-generation-methods/wallet_propose.md b/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/key-generation-methods/wallet_propose.md index adfb10b59dd..22a5a0d6346 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/key-generation-methods/wallet_propose.md +++ b/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/key-generation-methods/wallet_propose.md @@ -8,7 +8,7 @@ labels: - アカウント --- # wallet_propose -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/WalletPropose.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/WalletPropose.cpp "Source") `wallet_propose`メソッドを使用して、キーペアとXRP Ledgerアドレスを生成します。このコマンドは単にキーとアドレス値を生成し、XRP Ledger自体には何ら影響しません。レジャー上で資金供給済みのアドレスになるには、そのアドレスで、[必要準備金](../../../../concepts/accounts/reserves.md)を満たすのに十分なXRPの[Paymentトランザクションを受け取る](../../../../concepts/accounts/index.md#アカウントの作成)必要があります。 diff --git a/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/can_delete.md b/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/can_delete.md index 9832dd214fd..08f75fd1dc4 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/can_delete.md +++ b/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/can_delete.md @@ -7,7 +7,7 @@ labels: - データ保持 --- # can_delete -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/CanDelete.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/CanDelete.cpp "Source") `can_delete`メソッドは[指示による削除が有効なオンライン削除](../../../../infrastructure/configuration/data-retention/online-deletion.md#指示による削除)を使用する`rippled`サーバに削除が可能のレジャーバージョンを通知します。指定したレジャーバージョン以前が削除可能になります。指示による削除が有効ではない場合、このメソッドは何も行いません。 diff --git a/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/crawl_shards.md b/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/crawl_shards.md deleted file mode 100644 index 4eca2d1f68c..00000000000 --- a/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/crawl_shards.md +++ /dev/null @@ -1,140 +0,0 @@ ---- -html: crawl_shards.html -parent: logging-and-data-management-methods.html -seo: - description: ピアが持つ履歴シャードについての情報をリクエストします。 -labels: - - データ保持 ---- -# crawl_shards - -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/CrawlShards.cpp "Source") - -使用可能な[履歴レジャーデータのシャード](../../../../infrastructure/configuration/data-retention/history-sharding.md)に関するピアサーバからの情報をリクエストします。{% badge href="https://github.com/XRPLF/rippled/releases/tag/1.2.0" %}新規: rippled 1.2.0{% /badge %} - -_`crawl_shards`メソッドは、権限のないユーザは実行できない[管理メソッド](../index.md)です。_ - -### リクエストのフォーマット - -リクエストのフォーマットの例: - -{% tabs %} - -{% tab label="WebSocket" %} -```json -{ - "command": "crawl_shards", - "pubkey": true, - "limit": 0 -} -``` -{% /tab %} - -{% tab label="JSON-RPC" %} -```json -{ - "method": "crawl_shards", - "params": [ - { - "pubkey": true, - "limit": 0 - } - ] -} -``` -{% /tab %} - -{% /tabs %} - -{% admonition type="info" name="注記" %}このメソッドのコマンドライン構文はありません。コマンドラインからアクセスするには[jsonメソッド][]を使用してください。{% /admonition %} - -リクエストには以下のフィールドが含まれます。 - -| `Field` | 型 | 説明 | -|:---------|:--------|:--------------------------------------------------------| -| `pubkey` | ブール値 | _（省略可）_ `true`の場合、レスポンスには、クロールされたサーバのノード公開鍵（ピアツーピア通信用）が含まれます。デフォルトは`false`です。 | -| `limit` | 数値 | _（省略可）_ 検索の深さを示すホップ数。デフォルトは0で、ダイレクトピアのみを検索します。`1`を制限値にすると、ピアのピアも検索します。最大値は`3`です。 | - -{% admonition type="warning" name="注意" %}`limit`が増加すると、検索される可能性のあるピアの数は、指数関数的に増加します。2または3を制限値にすると、サーバがAPIリクエストにレスポンスするのに数秒かかる場合があります。{% /admonition %} - - -### レスポンスのフォーマット - -処理が成功したレスポンスの例: - -{% tabs %} - -{% tab label="WebSocket" %} -```json -{ - "result": { - "complete_shards": "1-2,5,8-9,584,1973,2358", - "peers": [ - { - "complete_shards": "1-2,8,47,371,464,554,653,857,1076,1402,1555,1708,1813,1867", - "public_key": "n9LxFZiySnfDSvfh23N94UxsFkCjWyrchTeKHcYE6tJJQL5iejb2" - }, - { - "complete_shards": "8-9,584", - "ip": "192.168.1.132", - "public_key": "n9MN5xwYqbrj64rtfZAXQy7Y3sNxXZJeLt7Lj61a9DYEZ4SE2tQQ" - } - ] - }, - "status": "success", - "type": "response" -} -``` -{% /tab %} - -{% tab label="JSON-RPC" %} -```json -200 OK - -{ - "result": { - "complete_shards": "1-2,5,8-9,584,1973,2358", - "peers": [ - { - "complete_shards": "1-2,8,47,371,464,554,653,857,1076,1402,1555,1708,1813,1867", - "public_key": "n9LxFZiySnfDSvfh23N94UxsFkCjWyrchTeKHcYE6tJJQL5iejb2" - }, - { - "complete_shards": "8-9,584", - "ip": "192.168.1.132", - "public_key": "n9MN5xwYqbrj64rtfZAXQy7Y3sNxXZJeLt7Lj61a9DYEZ4SE2tQQ" - } - ], - "status": "success" - } -} -``` -{% /tab %} - -{% /tabs %} - -このレスポンスは[標準フォーマット][]に従っており、正常に完了した場合は結果に次のフィールドが含まれます。 - -| `Field` | 型 | 説明 | -|:------------------|:-------|:------------------------------------------------| -| `complete_shards` | 文字列 | _（省略可）_ ローカルサーバで利用可能な[履歴シャード](../../../../infrastructure/configuration/data-retention/history-sharding.md)の範囲。これは、空の文字列か、または連続していない範囲である場合があります。たとえば、`1-2,5,7-9`は、シャード1、2、5、7、8、9が利用可能であることを示します。このサーバで履歴シャーディングが有効になっていない場合は省略されます。 | -| `peers` | 配列 | 各ピアが使用可能な履歴シャードを表す**ピアシャードオブジェクト**のリスト（以下を参照）。 | - -#### ピアシャードオブジェクト - -レスポンスの`peers`配列のメンバーはそれぞれ、ピアツーピアネットワーク内の1つのサーバを表すオブジェクトです。リストには、少なくとも1つの完全な[履歴シャード](../../../../infrastructure/configuration/data-retention/history-sharding.md)が使用可能なピアのみが含まれます。配列の各オブジェクトには以下のフィールドが含まれます。 - - -| `Field` | 型 | 説明 | -|:----------|:-------|:--------------------------------------------------------| -| `complete_shards` | 文字列 | このピアが使用可能な履歴シャードの範囲。連続していない場合があります。たとえば、`1-2,5,7-9`は、シャード1、2、5、7、8、9が利用可能であることを示します。 | -| `ip` | 文字列 | _（省略される場合があります）_ このオブジェクトが表すピアのIPアドレス。IPv4アドレスまたはIPv6アドレスを指定できます。[プライベートピア](../../../../concepts/networks-and-servers/peer-protocol.md#プライベートピア)の場合は省略されます。 | -| `public_key` | 文字列 | _(リクエストで`"pubkey": true`が指定されている場合を除き省略)_ XRP Ledgerの[base58フォーマット](../../../protocol/data-types/base58-encodings.md)で、このピアでピアツーピア通信に使用される公開鍵。 | - - -### 考えられるエラー - -- いずれかの[汎用エラータイプ][]。 -- `invalidParams` - リクエストで1つ以上の必須フィールドが省略されていたか、または指定されたフィールドのデータタイプが誤っています。 - -{% raw-partial file="/docs/_snippets/common-links.md" /%} diff --git a/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/download_shard.md b/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/download_shard.md deleted file mode 100644 index 7d333f6a3ea..00000000000 --- a/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/download_shard.md +++ /dev/null @@ -1,122 +0,0 @@ ---- -html: download_shard.html -parent: logging-and-data-management-methods.html -seo: - description: レジャー履歴の特定のシャードをダウンロードします。 -labels: - - データ保持 ---- -# download_shard -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/DownloadShard.cpp "Source") - -サーバに対し、外部ソースから特定の[履歴レジャーデータのシャード](../../../../infrastructure/configuration/data-retention/history-sharding.md)をダウンロードするように指示します。`rippled`サーバで[履歴シャードが保管されるように設定する](../../../../infrastructure/configuration/data-retention/configure-history-sharding.md)必要があります。{% badge href="https://github.com/XRPLF/rippled/releases/tag/1.1.0" %}新規: rippled 1.1.0{% /badge %} - -_`download_shard`メソッドは、権限のないユーザは実行できない[管理メソッド](../index.md)です。_ - -外部ソースからHTTPSを使用してシャードが[lz4圧縮](https://lz4.github.io/lz4/) [tarアーカイブ](https://en.wikipedia.org/wiki/Tar_(computing))として提供される必要があります。アーカイブには、NuDB形式のシャードディレクトリとデータファイルが含まれている必要があります。 - -通常、このメソッドを使用してシャードをダウンロードしてインポートすれば、ピアツーピアネットワークからシャードを個別に取得するよりも短い時間で取得できます。また、サーバから提供される特定範囲のシャードまたはシャードのセットを選択する場合にもこのメソッドを使用できます。 - -### リクエストのフォーマット - -リクエストのフォーマットの例: - -{% tabs %} - -{% tab label="WebSocket" %} -```json -{ - "command": "download_shard", - "shards": [ - {"index": 1, "url": "https://example.com/1.tar.lz4"}, - {"index": 2, "url": "https://example.com/2.tar.lz4"}, - {"index": 5, "url": "https://example.com/5.tar.lz4"} - ] -} -``` -{% /tab %} - -{% tab label="JSON-RPC" %} -```json -{ - "method": "download_shard", - "params": [ - { - "shards": [ - {"index": 1, "url": "https://example.com/1.tar.lz4"}, - {"index": 2, "url": "https://example.com/2.tar.lz4"}, - {"index": 5, "url": "https://example.com/5.tar.lz4"} - ] - } - ] -} -``` -{% /tab %} - -{% /tabs %} - - -リクエストには以下のフィールドが含まれます。 - -| `Field` | 型 | 説明 | -|:-----------|:--------|:------------------------------------------------------| -| `shards` | 配列 | ダウンロードするシャードとダウンロード元を記述したShard Descriptorオブジェクト（以下の説明を参照）のリスト。 | - -`validate`のフィールドは廃止予定であり、今後予告なしに削除される可能性があります。`rippled`は全てのシャードの検証を実行します。{% badge href="https://github.com/XRPLF/rippled/releases/tag/1.6.0" %}更新: rippled 1.6.0{% /badge %} - -`shards`配列の各**Shard Descriptorオブジェクト**には以下のフィールドが含まれています。 - -| `Field` | 型 | 説明 | -|:--------|:-------|:----------------------------------------------------------| -| `index` | 数値 | 取得するシャードのインデックス。本番環境のXRP Ledgerでは、最も古いシャードのインデックスは1であり、このシャードにはレジャー32750～32768が含まれています。次のシャードのインデックスは2であり、このシャードにはレジャー32769～49152が含まれています。 | -| `url` | 文字列 | このシャードをダウンロードできるURL。このURLは`https://`か`http://`かで始まり`.tar.lz4`（大文字小文字の区別なし）で終わる必要があります。このダウンロードを提供するWebサーバは、信頼できる認証局（CA）によって署名された有効なTLS証明書を使用する必要があります。（`rippled`はオペレーティングシステムのCAストアーを使用します。） {% badge href="https://github.com/XRPLF/rippled/releases/tag/1.7.0" %}更新: rippled 1.7.0{% /badge %} | - -### レスポンスのフォーマット - -処理が成功したレスポンスの例: - -{% tabs %} - -{% tab label="WebSocket" %} -```json -{ - "result": { - "message": "downloading shards 1-2,5" - }, - "status": "success", - "type": "response" -} -``` -{% /tab %} - -{% tab label="JSON-RPC" %} -```json -200 OK - -{ - "result": { - "message": "downloading shards 1-2,5", - "status": "success" - } -} -``` -{% /tab %} - -{% /tabs %} - -このレスポンスは[標準フォーマット][]に従っており、正常に完了した場合は結果に次のフィールドが含まれます。 - -| `Field` | 型 | 説明 | -|:----------|:-------|:--------------------------------------------------------| -| `message` | 文字列 | このリクエストに対応して実行されたアクションを説明するメッセージ。 | - -{% admonition type="success" name="ヒント" %}サーバで使用可能なシャードを確認するには、[crawl_shardsメソッド][]を使用します。または、シャードストアーとして設定されたロケーションのサブフォルダー（`rippled.cfg`の`[shard_db]`の`path`パラメーター）を調べます。フォルダーには、シャードの番号に対応する名前が付いています。これらのフォルダーの1つに、シャードが未完了であることを示す`control.txt`ファイルが含まれていることがあります。{% /admonition %} - -### 考えられるエラー - -- いずれかの[汎用エラータイプ][]。 -- `notEnabled` - サーバでシャードストアーを使用するように設定されていません。 -- `tooBusy` - サーバはすでに、ピアツーピアネットワークから、または以前の`download_shard`リクエストの結果として、シャードをダウンロード中です。 -- `invalidParams` - リクエストで1つ以上の必須フィールドが省略されていたか、または指定されたフィールドのデータタイプが誤っています。 - -{% raw-partial file="/docs/_snippets/common-links.md" /%} diff --git a/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/ledger_cleaner.md b/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/ledger_cleaner.md index 877ac9f0050..b015a78a6c6 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/ledger_cleaner.md +++ b/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/ledger_cleaner.md @@ -7,9 +7,9 @@ labels: - データ保持 --- # ledger_cleaner -[[ソース]](https://github.com/XRPLF/rippled/blob/df54b47cd0957a31837493cd69e4d9aade0b5055/src/ripple/rpc/handlers/LedgerCleaner.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/ledger/detail/LedgerCleaner.cpp "Source") -`ledger_cleaner`コマンドは[レジャークリーナー](https://github.com/XRPLF/rippled/blob/f313caaa73b0ac89e793195dcc2a5001786f916f/src/ripple/app/ledger/README.md#the-ledger-cleaner)を制御します。レジャークリーナーは、`rippled`のレジャーデータベースの破損を検出して修復できる非同期メンテナンスプロセスです。 +`ledger_cleaner`コマンドは[レジャークリーナー](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/ledger/README.md#the-ledger-cleaner)を制御します。レジャークリーナーは、`rippled`のレジャーデータベースの破損を検出して修復できる非同期メンテナンスプロセスです。 _`ledger_cleaner`メソッドは、権限のないユーザは実行できない[管理メソッド](../index.md)です。_ diff --git a/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/ledger_request.md b/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/ledger_request.md index 36951e409f3..4d662a9644d 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/ledger_request.md +++ b/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/ledger_request.md @@ -7,7 +7,7 @@ labels: - データ保持 --- # ledger_request -[[ソース]](https://github.com/XRPLF/rippled/blob/e980e69eca9ea843d200773eb1f43abe3848f1a0/src/ripple/rpc/handlers/LedgerRequest.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/LedgerRequest.cpp "Source") `ledger_request`コマンドは、サーバに対し接続しているピアから特定のレジャーバージョンを取得するように指示します。これは、サーバが直接接続しているピアの1つにそのレジャーが存在している場合にのみ機能します。場合によっては、レジャーを完全に取得するにはこのコマンドを繰り返し実行する必要があります。 diff --git a/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/log_level.md b/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/log_level.md index e00253d34c2..93b0cd45bf0 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/log_level.md +++ b/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/log_level.md @@ -7,7 +7,7 @@ labels: - データ保持 --- # log_level -[[ソース]](https://github.com/XRPLF/rippled/blob/155fcdbcd0b4927152892c8c8be01d9cf62bed68/src/ripple/rpc/handlers/LogLevel.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/LogLevel.cpp "Source") `log_level`コマンドは`rippled`サーバのログ詳細レベルを変更するか、各ログメッセージカテゴリ（_パーティション_）の現在のログレベルを返します。 diff --git a/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/logrotate.md b/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/logrotate.md index d87cfe06fc7..c5981ae091c 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/logrotate.md +++ b/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/logrotate.md @@ -7,7 +7,7 @@ labels: - データ保持 --- # logrotate -[[ソース]](https://github.com/XRPLF/rippled/blob/743bd6c9175c472814448ea889413be79dfd1c07/src/ripple/rpc/handlers/LogRotate.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/LogRotate.cpp "Source") `logrotate`コマンドは、ログファイルを閉じて再度開きます。これは、Linuxファイルシステムでのログローテーションを促進することを目的としています。 diff --git a/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/node_to_shard.md b/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/node_to_shard.md deleted file mode 100644 index 89a94024832..00000000000 --- a/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/node_to_shard.md +++ /dev/null @@ -1,120 +0,0 @@ ---- -html: node_to_shard.html -parent: logging-and-data-management-methods.html -seo: - description: レジャーストアからシャードストアにデータをコピーします。 -labels: - - データ保持 ---- -# node_to_shard -[[ソース]](https://github.com/XRPLF/rippled/blob/develop/src/ripple/rpc/handlers/NodeToShard.cpp "Source") - -{% code-page-name /%}メソッドは、レジャーストアから[シャードストア](../../../../infrastructure/configuration/data-retention/history-sharding.md)へのデータコピーを管理します。データコピーの開始、停止、状態チェックが可能です。 - -_{% code-page-name /%}メソッドは、権限のないユーザには実行できない[管理メソッド](../index.md)です。_ - - -### リクエストのフォーマット - -リクエストのフォーマット例: - -{% tabs %} - -{% tab label="WebSocket" %} -```json -{ - "command": "{% $frontmatter.seo.title %}", - "action": "start" -} -``` -{% /tab %} - -{% tab label="JSON-RPC" %} -```json -{ - "method": "{% $frontmatter.seo.title %}", - "params": [{ - "action": "start" - }] -} -``` -{% /tab %} - -{% tab label="Commandline" %} -```sh -#Syntax: {% $frontmatter.seo.title %} start|stop|status -rippled {% $frontmatter.seo.title %} start -``` -{% /tab %} - -{% /tabs %} - -リクエストは、以下のパラメータを含みます: - -| `項目` | 型 | 説明 -|:---------|:-------|:---------------------------------------------------------| -| `action` | String | どのような動作をさせるかによって、 `start`、`stop` または `status` のいずれかを指定します。 | - - -### レスポンスのフォーマット - -正常レスポンス例: - -{% tabs %} - -{% tab label="WebSocket" %} -```json -{ - "result": { - "message": "Database import initiated..." - }, - "status": "success", - "type": "response" -} -``` -{% /tab %} - -{% tab label="JSON-RPC" %} -```json -{ - "result" : { - "message" : "Database import initiated...", - "status" : "success" - } -} - -``` -{% /tab %} - -{% tab label="Commandline" %} -```json -Loading: "/etc/rippled.cfg" -Connecting to 127.0.0.1:5005 - -{ - "result" : { - "message" : "Database import initiated...", - "status" : "success" - } -} - -``` -{% /tab %} - -{% /tabs %} - -レスポンスは、[標準フォーマット][]に従っており、成功した場合は、以下の項目を含みます: - -| `項目` | 型 | 説明 | -|:----------|:-------|:--------------------------------------------------------| -| `message` | 文字列 | コマンドにレスポンスして実行されたアクションを示す、可読性の高いメッセージ。 | - - -### 起こり得るエラー - -- いずれかの[汎用エラータイプ][]。 -- `internal` - コピーが実行されていない時にコピーの状態チェックをするといったような無効な操作の場合。 -- `notEnabled` - サーバが[履歴シャード](../../../../infrastructure/configuration/data-retention/history-sharding.md)を保存するように環境設定されていない場合。 -- `invalidParams` - 1つ以上の項目が誤って定義されている、もしくは、1つ以上の必須項目が抜けている。 - -{% raw-partial file="/docs/_snippets/common-links.md" /%} diff --git a/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/peer-management-methods/connect.md b/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/peer-management-methods/connect.md index 5f70e920a2c..5a6bccef2cc 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/peer-management-methods/connect.md +++ b/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/peer-management-methods/connect.md @@ -7,7 +7,7 @@ labels: - コアサーバ --- # connect -[[ソース]](https://github.com/XRPLF/rippled/blob/a61ffab3f9010d8accfaa98aa3cacc7d38e74121/src/ripple/rpc/handlers/Connect.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/Connect.cpp "Source") `connect`コマンドは、`rippled`サーバを特定のピア`rippled`サーバに強制的に接続します。 diff --git a/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/peer-management-methods/peer_reservations_add.md b/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/peer-management-methods/peer_reservations_add.md index 11bbd646504..659890814c7 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/peer-management-methods/peer_reservations_add.md +++ b/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/peer-management-methods/peer_reservations_add.md @@ -7,7 +7,7 @@ labels: - コアサーバ --- # peer_reservations_add -[[ソース]](https://github.com/XRPLF/rippled/blob/4a1148eb2849513dd1e7ae080288fd47ab57a376/src/ripple/rpc/handlers/Reservations.cpp#L36 "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/Reservations.cpp#L36 "Source") この{% code-page-name /%}メソッドは、XRP Ledger[ピアツーピアネットワーク](../../../../concepts/networks-and-servers/peer-protocol.md)内の特定のピアサーバの予約済みスロットを追加または更新します。{% badge href="https://github.com/XRPLF/rippled/releases/tag/1.4.0" %}新規: rippled 1.4.0{% /badge %} diff --git a/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/peer-management-methods/peer_reservations_del.md b/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/peer-management-methods/peer_reservations_del.md index c47628903d3..56884a6dfe3 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/peer-management-methods/peer_reservations_del.md +++ b/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/peer-management-methods/peer_reservations_del.md @@ -8,7 +8,7 @@ labels: --- # peer_reservations_del -[[ソース]](https://github.com/XRPLF/rippled/blob/4a1148eb2849513dd1e7ae080288fd47ab57a376/src/ripple/rpc/handlers/Reservations.cpp#L89 "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/Reservations.cpp#L89 "Source") {% code-page-name /%}メソッドは、特定の[ピアリザベーション][]を削除します（存在する場合）。{% badge href="https://github.com/XRPLF/rippled/releases/tag/1.4.0" %}新規: rippled 1.4.0{% /badge %} diff --git a/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/peer-management-methods/peer_reservations_list.md b/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/peer-management-methods/peer_reservations_list.md index 5ca11b0ac43..00b9de66339 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/peer-management-methods/peer_reservations_list.md +++ b/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/peer-management-methods/peer_reservations_list.md @@ -7,7 +7,7 @@ labels: - コアサーバ --- # peer_reservations_list -[[ソース]](https://github.com/XRPLF/rippled/blob/4a1148eb2849513dd1e7ae080288fd47ab57a376/src/ripple/rpc/handlers/Reservations.cpp#L116 "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/Reservations.cpp#L116 "Source") {% code-page-name /%}メソッドは、[ピアリザベーション][]を一覧表示します。{% badge href="https://github.com/XRPLF/rippled/releases/tag/1.4.0" %}新規: rippled 1.4.0{% /badge %} diff --git a/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/peer-management-methods/peers.md b/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/peer-management-methods/peers.md index edbfb2106e3..2296a565dfc 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/peer-management-methods/peers.md +++ b/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/peer-management-methods/peers.md @@ -7,7 +7,7 @@ labels: - コアサーバ --- # peers -[[ソース]](https://github.com/XRPLF/rippled/blob/52f298f150fc1530d201d3140c80d3eaf781cb5f/src/ripple/rpc/handlers/Peers.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/Peers.cpp "Source") `peers`コマンドは、[ピアプロトコル](../../../../concepts/networks-and-servers/peer-protocol.md)でこのサーバに現在接続されているその他のすべての`rippled`サーバのリスト（各サーバの接続状況と同期状況を含む）を返します。 diff --git a/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/server-control-methods/ledger_accept.md b/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/server-control-methods/ledger_accept.md index 3b5bf71e7e5..b88a97ab875 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/server-control-methods/ledger_accept.md +++ b/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/server-control-methods/ledger_accept.md @@ -7,7 +7,7 @@ labels: - コアサーバ --- # ledger_accept -[[ソース]](https://github.com/XRPLF/rippled/blob/a61ffab3f9010d8accfaa98aa3cacc7d38e74121/src/ripple/rpc/handlers/LedgerAccept.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/LedgerAccept.cpp "Source") `ledger_accept`メソッドは、サーバが現在処理中のレジャーを強制的に終了し、次のレジャー番号に進むようにします。このメソッドはテスト専用であり、`rippled`サーバがスタンドアロンモードで実行されている場合にのみ使用できます。 diff --git a/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/server-control-methods/stop.md b/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/server-control-methods/stop.md index becd719beaf..229bba26497 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/server-control-methods/stop.md +++ b/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/server-control-methods/stop.md @@ -7,7 +7,7 @@ labels: - コアサーバ --- # stop -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/Stop.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/Stop.cpp "Source") サーバのグレースフルシャットダウンを行います。 diff --git a/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/server-control-methods/validation_seed.md b/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/server-control-methods/validation_seed.md index 9b31a530979..024cf5f06e9 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/server-control-methods/validation_seed.md +++ b/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/server-control-methods/validation_seed.md @@ -8,7 +8,7 @@ labels: - コアサーバ --- # validation_seed -[[ソース]](https://github.com/XRPLF/rippled/blob/a61ffab3f9010d8accfaa98aa3cacc7d38e74121/src/ripple/rpc/handlers/ValidationSeed.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/ValidationCreate.cpp "Source") `validation_seed`コマンドは、rippledが検証の署名に使用するシークレット値を一時的に設定します。サーバを再起動すると、この値は構成ファイルに基づいてリセットされます。{% badge href="https://github.com/XRPLF/rippled/releases/tag/0.29.1-rc1" %}rippled 0.29.1 以降では無効{% /badge %} diff --git a/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/signing-methods/sign.md b/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/signing-methods/sign.md index e6d5cca56b6..cc5d98b36fa 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/signing-methods/sign.md +++ b/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/signing-methods/sign.md @@ -7,7 +7,7 @@ labels: - トランザクション送信 --- # sign -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/SignHandler.cpp "ソース") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/SignHandler.cpp "ソース") `sign`メソッドは[JSONフォーマットのトランザクション](../../../protocol/transactions/index.md)と[シード値](../../../../concepts/accounts/cryptographic-keys.md)を受け取り、トランザクションの署名済みバイナリー表現を返します。[マルチシグトランザクション](../../../../concepts/accounts/multi-signing.md)に署名を付与する場合は、代わりに[sign_forメソッド][]を使用します。 diff --git a/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/signing-methods/sign_for.md b/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/signing-methods/sign_for.md index 89ce4753021..b0464677a14 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/signing-methods/sign_for.md +++ b/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/signing-methods/sign_for.md @@ -7,7 +7,7 @@ labels: - トランザクション送信 --- # sign_for -[[ソース]](https://github.com/XRPLF/rippled/blob/release/src/ripple/rpc/handlers/SignFor.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/SignFor.cpp "Source") `sign_for`コマンドは、[マルチシグトランザクション](../../../../concepts/accounts/multi-signing.md)の署名を1つ提供します。 diff --git a/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/consensus_info.md b/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/consensus_info.md index 188d05dedbb..d2a04dabb0c 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/consensus_info.md +++ b/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/consensus_info.md @@ -8,7 +8,7 @@ labels: - コアサーバ --- # consensus_info -[[ソース]](https://github.com/XRPLF/rippled/blob/a61ffab3f9010d8accfaa98aa3cacc7d38e74121/src/ripple/rpc/handlers/ConsensusInfo.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/ConsensusInfo.cpp "Source") `consensus_info`メソッドは、デバッグのための[コンセンサスプロセス](../../../../concepts/consensus-protocol/index.md)に関する情報を返します。 diff --git a/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/feature.md b/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/feature.md index 06b4c67dd65..28d964538a1 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/feature.md +++ b/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/feature.md @@ -8,7 +8,7 @@ labels: - コアサーバ --- # feature -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/Feature1.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/Feature1.cpp "Source") `feature`コマンドは、[Amendment](../../../../concepts/networks-and-servers/amendments.md)に関してこのサーバが認識している情報（Amendmentが有効であるかどうか、サーバが[Amendmentプロセス](../../../../concepts/networks-and-servers/amendments.md#amendmentプロセス)でこれらのAmendmentに賛成票を投じたかどうかなど）を返します。{% badge href="https://github.com/XRPLF/rippled/releases/tag/0.31.0" %}新規: rippled 0.31.0{% /badge %} diff --git a/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/fetch_info.md b/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/fetch_info.md index 270a6775cc9..8eca5a6fb50 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/fetch_info.md +++ b/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/fetch_info.md @@ -7,7 +7,7 @@ labels: - コアサーバ --- # fetch_info -[[ソース]](https://github.com/XRPLF/rippled/blob/315a8b6b602798a4cff4d8e1911936011e12abdb/src/ripple/rpc/handlers/FetchInfo.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/FetchInfo.cpp "Source") `fetch_info`コマンドは、このサーバが現在ネットワークからフェッチしているオブジェクトに関する情報と、その情報を所有しているピアの数を返します。これは現在の取得操作をリセットする場合にも使用できます。 diff --git a/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/get_counts.md b/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/get_counts.md index 66b620b4413..f107a5afe56 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/get_counts.md +++ b/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/get_counts.md @@ -7,7 +7,7 @@ labels: - コアサーバ --- # get_counts -[[ソース]](https://github.com/XRPLF/rippled/blob/c7118a183a660648aa88a3546a6b2c5bce858440/src/ripple/rpc/handlers/GetCounts.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/GetCounts.cpp "Source") `get_counts`コマンドは、サーバの健全性に関するさまざまな統計情報を提供します。そのほとんどは、現在メモリーに格納されている各種オブジェクトの数です。 diff --git a/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/print.md b/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/print.md index 502df925389..c36bd925403 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/print.md +++ b/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/print.md @@ -7,7 +7,7 @@ labels: - コアサーバ --- # print -[[ソース]](https://github.com/XRPLF/rippled/blob/315a8b6b602798a4cff4d8e1911936011e12abdb/src/ripple/rpc/handlers/Print.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/Print.cpp "Source") `print`コマンドは、さまざまな内部サブシステム（ピア、レジャークリーナー、リソースマネージャーなど）の現在の状況を返します。 diff --git a/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/validator_info.md b/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/validator_info.md index ab3254791fd..780a2e3e3f6 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/validator_info.md +++ b/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/validator_info.md @@ -8,7 +8,7 @@ labels: - ブロックチェーン --- # validator_info -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/ValidatorInfo.cpp "ソース") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/ValidatorInfo.cpp "ソース") {% code-page-name /%}メソッドは、サーバがバリデータとして設定されている場合に、現在のバリデータの設定を返します。 diff --git a/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/validator_list_sites.md b/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/validator_list_sites.md index 29f7bab4761..d7690545aca 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/validator_list_sites.md +++ b/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/validator_list_sites.md @@ -8,7 +8,7 @@ labels: - コアサーバ --- # validator_list_sites -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/ValidatorListSites.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/ValidatorListSites.cpp "Source") `validator_list_sites`コマンドは、バリデータリストを処理するサイトのステータス情報を返します。{% badge href="https://github.com/XRPLF/rippled/releases/tag/0.80.1" %}新規: rippled 0.80.1{% /badge %} @@ -130,7 +130,7 @@ Connecting to 127.0.0.1:5005 | `Field` | 型 | 説明 | |:-----------------------|:-----------------|:--------------------------------| -| `last_refresh_status` | 文字列 | 存在する場合は、サイトの最終更新の[`ListDisposition`](https://github.com/XRPLF/rippled/blob/master/src/ripple/app/misc/ValidatorList.h)です。存在しない場合は、サイトに対するクエリーがまだ成功していません。 | +| `last_refresh_status` | 文字列 | 存在する場合は、サイトの最終更新の[`ListDisposition`](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/misc/ValidatorList.h)です。存在しない場合は、サイトに対するクエリーがまだ成功していません。 | | `last_refresh_time` | 文字列 | サイトの最終照会時刻を人間が読み取れる形式で表示します。存在しない場合は、サイトに対するクエリーがまだ成功していません。 | | `refresh_interval_min` | 符号なし整数 | 更新試行間隔の分数。 | | `uri` | 文字列 | サイトのURI。 | diff --git a/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/validators.md b/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/validators.md index d2bc3663287..1524ac51ca8 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/validators.md +++ b/@l10n/ja/docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/validators.md @@ -8,7 +8,7 @@ labels: - コアサーバ --- # validators -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/Validators.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/Validators.cpp "Source") `validators`コマンドは、サーバが使用する公開済みの信頼できるバリデータの最新リストに関する情報を、人間が読み取れる形式で返します。{% badge href="https://github.com/XRPLF/rippled/releases/tag/0.80.1" %}新規: rippled 0.80.1{% /badge %} diff --git a/@l10n/ja/docs/references/http-websocket-apis/api-conventions/rate-limiting.md b/@l10n/ja/docs/references/http-websocket-apis/api-conventions/rate-limiting.md index 50cf79d7ba5..9db711fa176 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/api-conventions/rate-limiting.md +++ b/@l10n/ja/docs/references/http-websocket-apis/api-conventions/rate-limiting.md @@ -46,7 +46,7 @@ Server is overloaded ``` ## リクエストあたりのレート -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/resource/Fees.h "ソース") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/resource/Fees.h "ソース") サーバは時間の経過とともに行われるリクエストの数に基づいてクライアントの使用率を計算し、サーバがリクエストにレスポンスするためにどれだけの作業をしなければならないかに基づいて、異なるタイプのリクエストに重みをつけます。[subscribeメソッド][]と[path_findメソッド][]に対するサーバからの後続メッセージもクライアントの使用率にカウントされます。 diff --git a/@l10n/ja/docs/references/http-websocket-apis/peer-port-methods/health-check.md b/@l10n/ja/docs/references/http-websocket-apis/peer-port-methods/health-check.md index fbfbb1de568..0c9dbd2fde1 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/peer-port-methods/health-check.md +++ b/@l10n/ja/docs/references/http-websocket-apis/peer-port-methods/health-check.md @@ -7,7 +7,7 @@ labels: - コアサーバ --- # ヘルスチェック -[[ソース]](https://github.com/XRPLF/rippled/blob/de0c52738785de8bf837f9124da65c7905e7bb5a/src/ripple/overlay/impl/OverlayImpl.cpp#L1084-L1168 "ソース") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/overlay/detail/OverlayImpl.cpp#L944-L1039 "ソース") ヘルスチェックは、個々の`rippled`サーバの状態を報告するための特別な[peer portメソッド](index.md)です。このメソッドは、自動化された監視において、機能停止を認識し、サーバの再起動のような自動または手動による介入を促すために使用することを意図しています。{% badge href="https://github.com/XRPLF/rippled/releases/tag/1.6.0" %}新規: rippled 1.6.0{% /badge %} diff --git a/@l10n/ja/docs/references/http-websocket-apis/peer-port-methods/validator-list.md b/@l10n/ja/docs/references/http-websocket-apis/peer-port-methods/validator-list.md index 57cc27dec09..74f14d72544 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/peer-port-methods/validator-list.md +++ b/@l10n/ja/docs/references/http-websocket-apis/peer-port-methods/validator-list.md @@ -45,7 +45,7 @@ JSONオブジェクトには以下のフィールドがあります。 | `public_key` | 文字列 | このバリデータリストのデータを検証するために使用する公開鍵。これは32バイトのEd25519公開鍵で、先頭に`0xED`というバイトが付きます。{% badge href="https://github.com/XRPLF/rippled/releases/tag/1.7.0" %}新規: rippled 1.7.0{% /badge %}. | ### マニフェストデータ -[[ソース]](https://github.com/XRPLF/rippled/blob/97712107b71a8e2089d2e3fcef9ebf5362951110/src/ripple/app/misc/impl/Manifest.cpp#L43-L66 "ソース") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/misc/detail/Manifest.cpp#L59-L82 "ソース") "マニフェスト"には、コンセンサスプロセスに関与する個人または組織（***バリデータ**または**リスト発行者**）を一意に識別する情報が含まれます。バリデータのマニフェストには、その[バリデータのトークン](../../../infrastructure/configuration/server-modes/run-rippled-as-a-validator.md#3-enable-validation-on-your-rippled-server)の _公開_ 情報が含まれます。リスト発行者のマニフェストはリスト発行者に関する情報を提供します。どちらも通常、XRP Ledgerの標準的な[バイナリフォーマット](../../protocol/binary-format.md)でバイナリにエンコードされます。(マニフェストの標準的なJSON形式はありません)。 diff --git a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/account-methods/account_channels.md b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/account-methods/account_channels.md index f2e4befc2dc..d929e5d21dc 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/account-methods/account_channels.md +++ b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/account-methods/account_channels.md @@ -7,7 +7,7 @@ labels: - Payment Channel --- # account_channels -[[ソース]](https://github.com/XRPLF/rippled/blob/release/src/ripple/rpc/handlers/AccountChannels.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/AccountChannels.cpp "Source") _（[PayChan Amendment][]が有効になっている必要があります。{% badge href="https://github.com/XRPLF/rippled/releases/tag/0.33.0" %}新規: rippled 0.33.0{% /badge %}）_ diff --git a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/account-methods/account_currencies.md b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/account-methods/account_currencies.md index ba52802c1bd..41f9a6e12d3 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/account-methods/account_currencies.md +++ b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/account-methods/account_currencies.md @@ -7,7 +7,7 @@ labels: - トークン --- # account_currencies -[[ソース]](https://github.com/XRPLF/rippled/blob/df966a9ac6dd986585ecccb206aff24452e41a30/src/ripple/rpc/handlers/AccountCurrencies.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/paths/AccountCurrencies.cpp "Source") `account_currencies`コマンドは、アカウントのトラストラインに基づいてそのアカウントが送金または受領できる通貨のリストを返します。（このリストは完全に確認されたリストではありませんが、ユーザインターフェイスへの入力に使用できます。） diff --git a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/account-methods/account_info.md b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/account-methods/account_info.md index 1841b59e595..e5e2ef6fef0 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/account-methods/account_info.md +++ b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/account-methods/account_info.md @@ -8,7 +8,7 @@ labels: - XRP --- # account_info -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/AccountInfo.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/AccountInfo.cpp "Source") `account_info`コマンドは、アカウントとそのアクティビティおよびXRP残高についての情報を取得します。取得されたすべての情報は、特定バージョンのレジャーに関連付けられています。 diff --git a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/account-methods/account_lines.md b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/account-methods/account_lines.md index 2caf41f5616..20ab17f0b17 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/account-methods/account_lines.md +++ b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/account-methods/account_lines.md @@ -7,7 +7,7 @@ labels: - トークン --- # account_lines -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/AccountLines.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/AccountLines.cpp "Source") `account_lines`メソッドは、アカウントのトラストラインに関する情報（XRP以外のあらゆる通貨の残高と資産など）を返します。取得された情報はすべて、特定バージョンのレジャーに関連付けられています。 diff --git a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/account-methods/account_nfts.md b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/account-methods/account_nfts.md index 1244760607f..69b3089c183 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/account-methods/account_nfts.md +++ b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/account-methods/account_nfts.md @@ -7,7 +7,7 @@ labels: - 非代替性トークン, NFT --- # account_nfts -[[ソース]](https://github.com/xrplf/rippled/blob/master/src/ripple/rpc/handlers/AccountObjects.cpp "ソース") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/AccountObjects.cpp "ソース") `account_nfts`メソッドは、指定したアカウントの`NFToken`オブジェクトの一覧を返します。 diff --git a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/account-methods/account_objects.md b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/account-methods/account_objects.md index 9209ee3a681..c28a49fc4b1 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/account-methods/account_objects.md +++ b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/account-methods/account_objects.md @@ -8,7 +8,7 @@ labels: - データ保持 --- # account_objects -[[ソース]](https://github.com/XRPLF/rippled/blob/399c43cae6e90a428e9ce6a988123972b0f03c99/src/ripple/rpc/handlers/AccountObjects.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/AccountObjects.cpp "Source") `account_objects`コマンドは、アカウントが所有するすべてのレジャーエントリの生[レジャーフォーマット][]を返します。アカウントのトラストラインと残高の概要については、[account_linesメソッド][]をご覧ください。 diff --git a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/account-methods/account_offers.md b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/account-methods/account_offers.md index db073cf73b1..629eb4ef4c4 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/account-methods/account_offers.md +++ b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/account-methods/account_offers.md @@ -7,7 +7,7 @@ labels: - 分散型取引所 --- # account_offers -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/AccountOffers.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/AccountOffers.cpp "Source") `account_offers`メソッドは、特定の[アカウント](../../../../concepts/accounts/index.md)から出された[オファー](../../../../concepts/tokens/decentralized-exchange/offers.md)のうち、特定の[レジャーバージョン](../../../../concepts/ledgers/index.md)で未処理であったオファーのリストを取得します。 diff --git a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/account-methods/account_tx.md b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/account-methods/account_tx.md index 8c04c22600a..87eef1fd107 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/account-methods/account_tx.md +++ b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/account-methods/account_tx.md @@ -8,7 +8,7 @@ labels: - 支払い --- # account_tx -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/AccountTx.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/AccountTx.cpp "Source") `account_tx`メソッドは、指定したアカウントに関連するトランザクションのリストを取得します。 diff --git a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/account-methods/gateway_balances.md b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/account-methods/gateway_balances.md index 82481ba745d..d8b4bdb915e 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/account-methods/gateway_balances.md +++ b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/account-methods/gateway_balances.md @@ -8,7 +8,7 @@ labels: - アカウント --- # gateway_balances -[[ソース]](https://github.com/XRPLF/rippled/blob/9111ad1a9dc37d49d085aa317712625e635197c0/src/ripple/rpc/handlers/GatewayBalances.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/GatewayBalances.cpp "Source") `gateway_balances`コマンドは、特定のアカウントから発行された残高の合計を計算します。オプションで、[運用アドレス](../../../../concepts/accounts/account-types.md)が保有する額を除外できます。{% badge href="https://github.com/XRPLF/rippled/releases/tag/0.28.2" %}新規: rippled 0.28.2{% /badge %} diff --git a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/account-methods/noripple_check.md b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/account-methods/noripple_check.md index 5224936c14c..077aa05d58c 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/account-methods/noripple_check.md +++ b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/account-methods/noripple_check.md @@ -7,7 +7,7 @@ labels: - トークン --- # noripple_check -[[ソース]](https://github.com/XRPLF/rippled/blob/9111ad1a9dc37d49d085aa317712625e635197c0/src/ripple/rpc/handlers/NoRippleCheck.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/NoRippleCheck.cpp "Source") `noripple_check`コマンドを使用すると、[アカウントのDefaultRippleフィールドとそのトラストラインのNoRippleフラグ](../../../../concepts/tokens/fungible-tokens/rippling.md)の状態を、推奨される設定と比較して迅速にチェックできます。 diff --git a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/clio-methods/nft_history.md b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/clio-methods/nft_history.md index e0891573c41..919b75704c8 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/clio-methods/nft_history.md +++ b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/clio-methods/nft_history.md @@ -8,7 +8,7 @@ labels: --- # nft_history -[[ソース]](https://github.com/XRPLF/clio/blob/4a5cb962b6971872d150777881801ce27ae9ed1a/src/rpc/handlers/NFTHistory.cpp "ソース") +[[ソース]](https://github.com/XRPLF/clio/blob/develop/src/rpc/handlers/NFTHistory.cpp "ソース") `nft_history`コマンドはクエリ対象の[NFT](../../../../concepts/tokens/nfts/index.md)の過去のトランザクションメタデータをClioサーバに問い合わせます。{% badge href="https://github.com/XRPLF/clio/releases/tag/1.1.0" %}新規: Clio v1.1.0{% /badge %} diff --git a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger.md b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger.md index 1f473b9d293..832c9a89d1e 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger.md +++ b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger.md @@ -7,7 +7,7 @@ label: - ブロックチェーン --- # ledger -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/LedgerHandler.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/LedgerHandler.cpp "Source") 公開レジャーに関する情報を取得します。 diff --git a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_closed.md b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_closed.md index 944b5478302..4d4e9783648 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_closed.md +++ b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_closed.md @@ -7,7 +7,7 @@ label: - ブロックチェーン --- # ledger_closed -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/LedgerClosed.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/LedgerClosed.cpp "Source") `ledger_closed`メソッドは、最新の決済済みレジャーの一意のIDを返します。（このレジャーは必ずしも検証済みで変更不可能ではありません。） diff --git a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_current.md b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_current.md index d8a1833574c..b5291879c41 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_current.md +++ b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_current.md @@ -7,7 +7,7 @@ label: - ブロックチェーン --- # ledger_current -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/LedgerCurrent.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/LedgerCurrent.cpp "Source") `ledger_current`メソッドは、現在進行中のレジャーの一意のIDを返します。このコマンドで返されるレジャーは確定されたものではないため、このコマンドは主にテストに有用です。 diff --git a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_data.md b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_data.md index 6917ac447d3..200dbf9f77c 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_data.md +++ b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_data.md @@ -8,7 +8,7 @@ label: - データ保持 --- # ledger_data -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/LedgerData.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/LedgerData.cpp "Source") `ledger_data`メソッドは指定されたレジャーの内容を取得します。1つのレジャーバージョンの内容全体を取得するため、複数のコールを繰り返し実行できます。 diff --git a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_entry.md b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_entry.md index 053501e7a51..285320551f9 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_entry.md +++ b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_entry.md @@ -8,7 +8,7 @@ label: - データ保持 --- # ledger_entry -[[ソース]](https://github.com/xrplf/rippled/blob/master/src/ripple/rpc/handlers/LedgerEntry.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/LedgerEntry.cpp "Source") `ledger_entry`メソッドは、XRP Ledgerの1つのレジャーエントリを生フォーマットで返します。取得可能な各種エントリについては、[レジャーフォーマット][]をご覧ください。 diff --git a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/amm_info.md b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/amm_info.md index ff8a24b0423..97b0ef52217 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/amm_info.md +++ b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/amm_info.md @@ -10,7 +10,7 @@ labels: - AMM --- # amm_info -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/AMMInfo.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/AMMInfo.cpp "Source") {% code-page-name /%}メソッドは、自動マーケットメーカー（AMM）インスタンスに関する情報を取得します。 diff --git a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/book_changes.md b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/book_changes.md index dfde649f9f8..8805cacfd6b 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/book_changes.md +++ b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/book_changes.md @@ -6,7 +6,7 @@ labels: - クロスカレンシー --- # book_changes -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/BookChanges.h "ソース") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/BookChanges.h "ソース") {% code-page-name /%} メソッドは、[分散型取引所（DEX）](../../../../concepts/tokens/decentralized-exchange/index.md) のオーダーブックの変更に関する情報を、以前のレジャーバージョンと比較して提供します。これは「ローソク足」チャートの作成に役立つ場合があります。 diff --git a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/book_offers.md b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/book_offers.md index c32ab594b56..445f0f574fe 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/book_offers.md +++ b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/book_offers.md @@ -8,7 +8,7 @@ labels: - クロスカレンシー --- # book_offers -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/BookOffers.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/BookOffers.cpp "Source") `book_offers`メソッドは、[オーダーブック](http://www.investopedia.com/terms/o/order-book.asp)と呼ばれる、2つの通貨間のオファーのリストを取得します。結果が非常に大きい場合、結果の一部がマーカー付きで返されます。これにより、その後のリクエストは前回のリクエストで終わった箇所から再開できます。 diff --git a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/deposit_authorized.md b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/deposit_authorized.md index d278e14578f..69f19bb3608 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/deposit_authorized.md +++ b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/deposit_authorized.md @@ -6,7 +6,7 @@ labels: - セキュリティ --- # deposit_authorized -[[ソース]](https://github.com/XRPLF/rippled/blob/817d2339b8632cb2f97d3edd6f7af33aa7631744/src/ripple/rpc/handlers/DepositAuthorized.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/DepositAuthorized.cpp "Source") `deposit_authorized`コマンドは、あるアカウントに別のアカウントへ支払を直接送金する権限があるかどうかを示します。アカウントへの送金に承認を義務付ける方法については、[Deposit Authorization](../../../../concepts/accounts/depositauth.md)をご覧ください。 diff --git a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/get_aggregate_price.md b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/get_aggregate_price.md index a1460a42a6d..f2b581c2e79 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/get_aggregate_price.md +++ b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/get_aggregate_price.md @@ -9,7 +9,7 @@ labels: _([PriceOracle amendment][])_ -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/GetAggregatePrice.cpp "ソース") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/GetAggregatePrice.cpp "ソース") `get_aggregate_price`メソッドは、指定された`Oracle`オブジェクトの集計価格を取得し、平均値、中央値、整形された平均値の3つの価格情報を返します。 diff --git a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/nft_buy_offers.md b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/nft_buy_offers.md index a76dfdb295f..36c93608d6d 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/nft_buy_offers.md +++ b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/nft_buy_offers.md @@ -7,7 +7,7 @@ labels: - 非代替性トークン, NFT, NFToken --- # nft_buy_offers -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/NFTOffers.cpp "ソース") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/NFTOffers.cpp "ソース") `nft_buy_offers`メソッドは、与えられた[NFToken][]オブジェクトに対する購入オファーのリストを返します。 diff --git a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/nft_sell_offers.md b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/nft_sell_offers.md index 8ef97598949..0a5607ee4f4 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/nft_sell_offers.md +++ b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/nft_sell_offers.md @@ -7,7 +7,7 @@ labels: - 非代替性トークン, NFT, NFToken --- # nft_sell_offers -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/NFTOffers.cpp "ソース") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/NFTOffers.cpp "ソース") `nft_sell_offers`メソッドは、与えられた[NFToken][]オブジェクトに対する売却オファーのリストを返します。 diff --git a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/path_find.md b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/path_find.md index 76a9b539379..f37e6e3d78f 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/path_find.md +++ b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/path_find.md @@ -8,7 +8,7 @@ labels: - トークン --- # path_find -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/PathFind.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/PathFind.cpp "Source") *WebSocket APIのみ。*`path_find`メソッドは、トランザクションが実行される可能性のある[パス](../../../../concepts/tokens/fungible-tokens/paths.md)を探索し、時間の経過とともにパスが変化する場合に更新を定期的に送信します。JSON-RPCでサポートされているシンプルなバージョンについては、[ripple_path_findメソッド][]をご覧ください。完全にXRPで行われる支払いの場合、XRPはどのアカウントにも直接送金できるためパスを探索する必要はありません。 @@ -21,7 +21,7 @@ path_findコマンドには3種類のモード（サブコマンド）があり `rippled`サーバは支払いを行うにあたり最も安価なパスまたはパスの組み合わせを探索しますが、このメソッドで返されるパスが最良のパスであることは保証されません。サーバの負荷が原因で、Pathfindingで最良のパスを検出できないことがあります。また、信頼できないサーバからのPathfindingの結果には注意する必要があります。オペレーターの収益となるように、最良ではないパスを返すようにサーバが改ざんされる可能性があります。Pathfindingについて信頼できる独自サーバがない場合は、1つのサーバから不適切な結果が返されるリスクを最小限に抑えるため、異なる当事者が実行する複数のサーバからのPathfindingの結果を比較してください。（**注記:** サーバから最良ではない結果が返されても、必ずしも悪意のある振る舞いの証拠とはなりません。サーバの負荷が高い場合の症状である可能性もあります。） ## path_find create -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/PathFind.cpp#L50-L56 "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/PathFind.cpp#L53-L59 "Source") `path_find`の`create`サブコマンドは、指定された特定アカウントから支払トランザクションを実行できるパスを探索する継続的なリクエストを作成し、別のアカウントが何らかの通貨で希望する額を受領できるようにします。初期レスポンスには2つのアドレス間で提案されるパスが含まれています。このパスにより、希望する額を受領できます。その後サーバは、`"type": "path_find"`で有効なパスの更新を含む追加メッセージを送信します。更新の頻度はサーバにより決定されますが、新しいレジャーバージョンがある場合には通常、数秒間に1回です。 @@ -498,7 +498,7 @@ path_find createリクエストからの非同期フォローアップの例を {% /tabs %} ## path_find close -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/PathFind.cpp#L58-L67 "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/PathFind.cpp#L61-L70 "Source") `path_find`の`close`サブコマンドは、サーバに対して現在実行中のPathfindingリクエストに関する情報の送信を停止するように指示します。 @@ -543,7 +543,7 @@ Pathfindingリクエストが正常にクローズされた場合、レスポン * `noPathRequest` - Pathfindingリクエストをクローズしようとしましたが、実行中のリクエストがありませんでした。 ## path_find status -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/PathFind.cpp#L69-L77 "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/PathFind.cpp#L72-L80 "Source") `path_find`の`status`サブコマンドは、現在実行中のクライアントのPathfindingリクエストの即時更新をリクエストします。 diff --git a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/ripple_path_find.md b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/ripple_path_find.md index 568b867e316..75c0fc79105 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/ripple_path_find.md +++ b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/ripple_path_find.md @@ -8,7 +8,7 @@ labels: - トークン --- # ripple_path_find -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/RipplePathFind.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/RipplePathFind.cpp "Source") `ripple_path_find`メソッドは、[path_findメソッド][]のシンプルなバージョンであり、すぐに利用できる[ペイメントパス](../../../../concepts/tokens/fungible-tokens/paths.md)を含む1つのレスポンスを返します。WebSocket APIとJSON-RPC APIの両方で使用できます。ただし、結果は時間の経過とともに古くなる傾向にあります。最新の状態を維持するために複数のコールを実行する代わりに、可能な場合には[path_findメソッド][]を使用して、継続的な更新をサブスクライブします。 diff --git a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/payment-channel-methods/channel_authorize.md b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/payment-channel-methods/channel_authorize.md index e1827da1c39..30f8136a7fb 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/payment-channel-methods/channel_authorize.md +++ b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/payment-channel-methods/channel_authorize.md @@ -7,7 +7,7 @@ labels: - Payment Channel --- # channel_authorize -[[ソース]](https://github.com/XRPLF/rippled/blob/d4a56f223a3b80f64ff70b4e90ab6792806929ca/src/ripple/rpc/handlers/PayChanClaim.cpp#L41 "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/PayChanClaim.cpp#L41 "Source") _（[PayChan Amendment][]が有効になっている必要があります。{% badge href="https://github.com/XRPLF/rippled/releases/tag/0.33.0" %}新規: rippled 0.33.0{% /badge %}）_ diff --git a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/payment-channel-methods/channel_verify.md b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/payment-channel-methods/channel_verify.md index b673b93bc01..63add76a958 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/payment-channel-methods/channel_verify.md +++ b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/payment-channel-methods/channel_verify.md @@ -7,7 +7,7 @@ labels: - Payment Channel --- # channel_verify -[[ソース]](https://github.com/XRPLF/rippled/blob/d4a56f223a3b80f64ff70b4e90ab6792806929ca/src/ripple/rpc/handlers/PayChanClaim.cpp#L89 "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/PayChanClaim.cpp#L111 "Source") _（[PayChan Amendment][]が有効になっている必要があります。{% badge href="https://github.com/XRPLF/rippled/releases/tag/0.33.0" %}新規: rippled 0.33.0{% /badge %}）_ diff --git a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/server-info-methods/fee.md b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/server-info-methods/fee.md index 004e02908ce..30c12e2cd28 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/server-info-methods/fee.md +++ b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/server-info-methods/fee.md @@ -7,7 +7,7 @@ labels: - 手数料 --- # fee -[[ソース]](https://github.com/XRPLF/rippled/blob/release/src/ripple/rpc/handlers/Fee1.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/Fee1.cpp "Source") `fee`コマンドは、[トランザクションコスト](../../../../concepts/transactions/transaction-cost.md)に関するオープンレジャーの要件の現在の状態を報告します。このコマンドを使用するには、[FeeEscalation Amendment][]が有効になっている必要があります。{% badge href="https://github.com/XRPLF/rippled/releases/tag/0.31.0" %}新規: rippled 0.31.0{% /badge %} diff --git a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/server-info-methods/manifest.md b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/server-info-methods/manifest.md index e3d85bbd520..f51a3cadec7 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/server-info-methods/manifest.md +++ b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/server-info-methods/manifest.md @@ -7,7 +7,7 @@ labels: - ブロックチェーン --- # manifest -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/Manifest.cpp "ソース") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/misc/detail/Manifest.cpp "ソース") {% code-page-name /%}メソッドは、指定したバリデータ公開鍵の現在の"マニフェスト"情報を報告します。"マニフェスト"は、バリデータのマスターキーペアから署名付きの公開鍵(ephemeral signing key)を認証するためのデータブロックです。{% badge href="https://github.com/XRPLF/rippled/releases/tag/1.7.0" %}更新: rippled 1.7.0{% /badge %}. diff --git a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/server-info-methods/server_definitions.md b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/server-info-methods/server_definitions.md index 64e0debe1c4..c93c39420e7 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/server-info-methods/server_definitions.md +++ b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/server-info-methods/server_definitions.md @@ -8,7 +8,7 @@ labels: --- # server_definitions -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/ServerInfo.cpp#L43 "ソース") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/ServerInfo.cpp#L43 "ソース") `server_definitions`コマンドは実行中の`rippled`インスタンスから生成されたSDK互換の`definitions.json`を返します。これを使用してネットワーク上のノードにアクセスし、そのバイナリデータをシリアライズ/デシリアライズするために必要な定義を受け取ることができます。 diff --git a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/server-info-methods/server_info.md b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/server-info-methods/server_info.md index f24302e9d62..51162b42ace 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/server-info-methods/server_info.md +++ b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/server-info-methods/server_info.md @@ -7,7 +7,7 @@ labels: - コアサーバ --- # server_info (rippled) -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/ServerInfo.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/ServerInfo.cpp "Source") `server_info`コマンドは、問い合わせ中の`rippled`サーバについての各種情報を、人間が読めるフォーマットでサーバにリクエストします。[Clioサーバ](../../../../concepts/networks-and-servers/the-clio-server.md)については、[`server_info` (Clio)](../clio-methods/server_info-clio.md)をご覧ください。 diff --git a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/server-info-methods/server_state.md b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/server-info-methods/server_state.md index 63b9e9bc997..7e2d987c629 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/server-info-methods/server_state.md +++ b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/server-info-methods/server_state.md @@ -8,7 +8,7 @@ labels: --- # server_state -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/ServerState.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/ServerState.cpp "Source") `server_state`コマンドは、サーバに対し`rippled`サーバの現在の状態に関するさまざまな機械可読の情報を問い合わせます。レスポンスは[server_infoメソッド][]の場合とほぼ同じですが、読み取りやすい単位ではなく処理しやすい単位を使用します。（たとえば、XRP値は科学的記数法や10進数値の代わりに整数のdrop数で示され、時刻は秒単位ではなくミリ秒単位で示されます。） diff --git a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/subscription-methods/subscribe.md b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/subscription-methods/subscribe.md index 088c03150be..11e35f145b1 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/subscription-methods/subscribe.md +++ b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/subscription-methods/subscribe.md @@ -10,7 +10,7 @@ labels: - スマートコントラクト --- # subscribe -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/Subscribe.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/Subscribe.cpp "Source") `subscribe`メソッドは、特定のイベントが発生した場合に、定期的に通知するようサーバにリクエストします。 diff --git a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/subscription-methods/unsubscribe.md b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/subscription-methods/unsubscribe.md index 1b22cae0b34..6970a1c3ecc 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/subscription-methods/unsubscribe.md +++ b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/subscription-methods/unsubscribe.md @@ -10,7 +10,7 @@ labels: - スマートコントラクト --- # unsubscribe -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/Unsubscribe.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/Unsubscribe.cpp "Source") `unsubscribe`コマンドはサーバに対して、特定のサブスクリプションまたは一連のサブスクリプションへのメッセージ送信の停止を指示します。 diff --git a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/transaction-methods/simulate.md b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/transaction-methods/simulate.md index a453900cc38..012495f5914 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/transaction-methods/simulate.md +++ b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/transaction-methods/simulate.md @@ -5,7 +5,7 @@ labels: - トランザクション送信 --- # simulate -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/rpc/handlers/Simulate.cpp "ソース") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/Simulate.cpp "ソース") `simulate` メソッドは、あらゆる トランザクションを仮実行し、XRP Ledger に反映することなく、その結果やメタデータを事前に確認できます。このコマンドはネットワークにトランザクションを送信しないため、手数料は発生しません。 diff --git a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/transaction-methods/submit.md b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/transaction-methods/submit.md index 49a3850ca62..82a7a812dcf 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/transaction-methods/submit.md +++ b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/transaction-methods/submit.md @@ -8,7 +8,7 @@ labels: - 支払い --- # submit -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/Submit.cpp "ソース") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/Submit.cpp "ソース") `submit`メソッドは[トランザクション](../../../protocol/transactions/index.md)を適用し、トランザクションの確認と将来のレジャーへの記録が行われるように、ネットワークに送信します。 diff --git a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/transaction-methods/submit_multisigned.md b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/transaction-methods/submit_multisigned.md index 95505faa64d..a1ad7635f35 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/transaction-methods/submit_multisigned.md +++ b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/transaction-methods/submit_multisigned.md @@ -7,7 +7,7 @@ labels: - トランザクション送信 --- # submit_multisigned -[[ソース]](https://github.com/XRPLF/rippled/blob/release/src/ripple/rpc/handlers/SubmitMultiSigned.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/SubmitMultiSigned.cpp "Source") `submit_multisigned`コマンドは[マルチシグ](../../../../concepts/accounts/multi-signing.md)トランザクションを適用し、このトランザクションをネットワークに送信して、今後のレジャーに追加します。（[`submit`コマンドを送信専用モードで](submit.md#送信専用モード)使用して、マルチシグトランザクションをバイナリー形式で送信することもできます。) diff --git a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/transaction-methods/transaction_entry.md b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/transaction-methods/transaction_entry.md index bf4eae16b01..7049f8a4864 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/transaction-methods/transaction_entry.md +++ b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/transaction-methods/transaction_entry.md @@ -7,7 +7,7 @@ labels: - トランザクション送信 --- # transaction_entry -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/TransactionEntry.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/TransactionEntry.cpp "Source") `transaction_entry`メソッドは、特定のレジャーバージョンから1つのトランザクションに関する情報を取得します。（これに対して、[txメソッド][]はすべてのレジャーから指定のトランザクションを検索します。txメソッドの使用をお勧めします。） diff --git a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/transaction-methods/tx.md b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/transaction-methods/tx.md index 66dbb00fc16..83c4bd7cc2b 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/transaction-methods/tx.md +++ b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/transaction-methods/tx.md @@ -9,7 +9,7 @@ labels: --- # tx -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/Tx.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/Tx.cpp "Source") `tx`メソッドは1つのトランザクションに関する情報を取得します。 diff --git a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/transaction-methods/tx_history.md b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/transaction-methods/tx_history.md index 463d8d6a925..5ba00816e72 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/transaction-methods/tx_history.md +++ b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/transaction-methods/tx_history.md @@ -5,7 +5,7 @@ seo: description: 直近に作成されたトランザクションの一部を取得します。 --- # tx_history -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/TxHistory.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/TxHistory.cpp "Source") `tx_history`メソッドは、直近に作成されたトランザクションの一部を取得します。 diff --git a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/utility-methods/ping.md b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/utility-methods/ping.md index 0e8fc509e4a..d93c3f985bc 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/utility-methods/ping.md +++ b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/utility-methods/ping.md @@ -7,7 +7,7 @@ labels: - コアサーバ --- # ping -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/Ping.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/Ping.cpp "Source") `ping`コマンドは確認レスポンスを返します。これにより、クライアントは接続のステータスと遅延をテストできます。 diff --git a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/utility-methods/random.md b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/utility-methods/random.md index c00071e4ab0..80a3d054577 100644 --- a/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/utility-methods/random.md +++ b/@l10n/ja/docs/references/http-websocket-apis/public-api-methods/utility-methods/random.md @@ -7,7 +7,7 @@ labels: - コアサーバ --- # random -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/Random.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/Random.cpp "Source") `random`コマンドは、クライアントが乱数生成のエントロピー生成源として使用する乱数を提供します。 diff --git a/@l10n/ja/docs/references/protocol/binary-format.md b/@l10n/ja/docs/references/protocol/binary-format.md index 57baf3c5a08..7217b505489 100644 --- a/@l10n/ja/docs/references/protocol/binary-format.md +++ b/@l10n/ja/docs/references/protocol/binary-format.md @@ -15,7 +15,7 @@ curated_anchors: anchor: "#タイプリスト" --- # バイナリフォーマット -[[ソース]](https://github.com/XRPLF/rippled/blob/develop/src/ripple/protocol/impl/STObject.cpp#L696-L718 "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/SField.h "Source") このページでは、XRP Ledgerのトランザクションとその他のデータの正規バイナリフォーマットについて説明します。このバイナリフォーマットは、トランザクションの内容のデジタル署名を作成および検証するために必要であり、[サーバ間のピアツーピア通信](../../concepts/networks-and-servers/peer-protocol.md)を含む他の用途にも使用されます。通常、[`rippled` API](../http-websocket-apis/index.md)は、JSONを使用してクライアントアプリケーションと通信します。ただしJSONは、同じデータをさまざまな同等の方法で表現できるため、デジタル署名を付与するトランザクションをシリアル化するのに適したフォーマットではありません。 @@ -55,7 +55,7 @@ curated_anchors: ここで説明するシリアル化プロセスは複数の場所にさまざまなプログラミング言語で実装されています。 -- C++: [`rippled`コードベース](https://github.com/XRPLF/rippled/blob/develop/src/ripple/protocol/impl/STObject.cpp) +- C++: [`rippled`コードベース](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/libxrpl/protocol/STObject.cpp) - JavaScript: [`ripple-binary-codec`](https://github.com/ripple/ripple-binary-codec/)パッケージ - Python 3: {% repo-link path="_code-samples/tx-serialization/" %}このリポジトリのコードサンプルセクション{% /repo-link %} @@ -65,7 +65,7 @@ curated_anchors: ## 内部フォーマット -各フィールドには「内部」バイナリフォーマットがあります。このフォーマットは、`rippled`ソースコードで署名時に（およびその他のほとんどの場合に）そのフィールドを表示するのに使用されます。すべてのフィールドの内部フォーマットは、[`SField.cpp`](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/impl/SField.cpp)のソースコードに定義されています。（このフィールドには、トランザクションフィールド以外のフィールドも含まれています。）[トランザクションフォーマットリファレンス](transactions/index.md)にも、すべてのトランザクションフィールドの内部フォーマットが記載されています。 +各フィールドには「内部」バイナリフォーマットがあります。このフォーマットは、`rippled`ソースコードで署名時に（およびその他のほとんどの場合に）そのフィールドを表示するのに使用されます。すべてのフィールドの内部フォーマットは、[`SField.cpp`](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/libxrpl/protocol/SField.cpp)のソースコードに定義されています。（このフィールドには、トランザクションフィールド以外のフィールドも含まれています。）[トランザクションフォーマットリファレンス](transactions/index.md)にも、すべてのトランザクションフィールドの内部フォーマットが記載されています。 たとえば`Flags`[共通トランザクションフィールド](transactions/common-fields.md)はUInt32（32ビット符号なし整数）になります。 @@ -99,8 +99,8 @@ curated_anchors: ### フィールドID -[[ソース - エンコード]](https://github.com/seelabs/rippled/blob/cecc0ad75849a1d50cc573188ad301ca65519a5b/src/ripple/protocol/impl/Serializer.cpp#L117-L148 "Source") -[[ソース - デコード]](https://github.com/seelabs/rippled/blob/cecc0ad75849a1d50cc573188ad301ca65519a5b/src/ripple/protocol/impl/Serializer.cpp#L484-L509 "Source") +[[ソース - エンコード]](https://github.com/XRPLF/rippled/blob/cecc0ad75849a1d50cc573188ad301ca65519a5b/src/ripple/protocol/impl/Serializer.cpp#L117-L148 "Source") +[[ソース - デコード]](https://github.com/XRPLF/rippled/blob/cecc0ad75849a1d50cc573188ad301ca65519a5b/src/ripple/protocol/impl/Serializer.cpp#L484-L509 "Source") フィールドのタイプコードとフィールドコードを結合すると、フィールドの一意のIDになります。このIDは、最終的なシリアル化Blobでこのフィールドの前に付加されます。フィールドIDのサイズは、タイプコードとその結合対象のフィールドコードに応じて1～3バイトとなります。以下の表をご覧ください。 @@ -155,17 +155,17 @@ curated_anchors: ### タイプコード -各フィールドタイプには任意のタイプコードが含まれており、番号が小さいコードから最初にソートされます。これらのコードは[`SField.h`](https://github.com/XRPLF/rippled/blob/master/include/xrpl/protocol/SField.h#L60-L98)で定義されています。 +各フィールドタイプには任意のタイプコードが含まれており、番号が小さいコードから最初にソートされます。これらのコードは[`SField.h`](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/SField.h#L60-L98)で定義されています。 -たとえば [UInt32のタイプコードが2である](https://github.com/XRPLF/rippled/blob/master/include/xrpl/protocol/SField.h#L67)ので、すべてのUInt32フィールドは、すべての[Amountフィールド（タイプコード6）](https://github.com/XRPLF/rippled/blob/master/include/xrpl/protocol/SField.h#L71)よりも前に位置します。 +たとえば [UInt32のタイプコードが2である](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/SField.h#L67)ので、すべてのUInt32フィールドは、すべての[Amountフィールド（タイプコード6）](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/SField.h#L71)よりも前に位置します。 [定義ファイル](#定義ファイル)には、`TYPES`マップの各タイプのタイプコードがリストされています。 ### フィールドコード -各フィールドにはフィールドコードが含まれています。フィールドコードは、同じタイプのフィールドをソートするときに使用され、番号が小さいコードが最初になるようにソートされます。これらのフィールドは[`sfields/macro`](https://github.com/XRPLF/rippled/blob/master/include/xrpl/protocol/detail/sfields.macro)で定義されています。 +各フィールドにはフィールドコードが含まれています。フィールドコードは、同じタイプのフィールドをソートするときに使用され、番号が小さいコードが最初になるようにソートされます。これらのフィールドは[`sfields/macro`](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/detail/sfields.macro)で定義されています。 -たとえば[Paymentトランザクション][]の`Account`フィールドの[ソートコードが1である](https://github.com/XRPLF/rippled/blob/master/include/xrpl/protocol/detail/sfields.macro#L269)場合、このフィールドは`Destination`フィールド（[ソートコードが3である](https://github.com/XRPLF/rippled/blob/master/include/xrpl/protocol/detail/sfields.macro#L271)フィールド）よりも前に位置します。 +たとえば[Paymentトランザクション][]の`Account`フィールドの[ソートコードが1である](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/detail/sfields.macro#L269)場合、このフィールドは`Destination`フィールド（[ソートコードが3である](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/detail/sfields.macro#L271)フィールド）よりも前に位置します。 フィールドコードは異なるフィールドタイプのフィールドで再利用されますが、同じタイプのフィールドに同じフィールドコードが含まれることはありません。タイプコードとフィールドコードを組み合わせると、フィールドの一意の[フィールドID](#フィールドid)になります。 @@ -239,7 +239,7 @@ curated_anchors: [{% inline-svg file="/docs/img/serialization-amount.ja.svg" /%}](/docs/img/serialization-amount.ja.svg "「非XRP」ビット、符号ビット、および62ビットの精度で構成されるXRPの額。「非XRP」ビット、符号ビット、指数（8ビット）、仮数（54ビット）、通貨コード（160ビット）、イシュアー（160ビット）で構成されるトークンの額。") #### トークンの数量フォーマット -[[ソース]](https://github.com/XRPLF/rippled/blob/35fa20a110e3d43ffc1e9e664fc9017b6f2747ae/src/ripple/protocol/impl/STAmount.cpp "ソース") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/libxrpl/protocol/STAmount.cpp "ソース") [{% inline-svg file="/docs/img/currency-number-format.ja.svg" /%}](/docs/img/currency-number-format.ja.svg "トークンの数量フォーマットの図") @@ -328,12 +328,12 @@ XRP LedgerのハッシュタイプにはHash128、Hash160、Hash256がありま クロスカレンシーの[Paymentトランザクション][]の`Paths`フィールドは、JSONで配列からなる配列として表される「PathSet」です。使用されるパスについての詳細は、[パス](../../concepts/tokens/fungible-tokens/paths.md)をご覧ください。 -PathSetは、**1～6**の個別パスとして順序どおりにシリアル化されます[[ソース]](https://github.com/XRPLF/rippled/blob/4cff94f7a4a05302bdf1a248515379da99c5bcd4/src/ripple/app/tx/impl/Payment.h#L35-L36 "Source")。それぞれの完全なパスの後には、パスの後に続く内容を示すバイトが配置されます。 +PathSetは、**1～6**の個別パスとして順序どおりにシリアル化されます[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/Payment.h#L29-L30 "Source")。それぞれの完全なパスの後には、パスの後に続く内容を示すバイトが配置されます。 - `0xff`は別のパスが続くことを示します。 - `0x00`はPathSetの終わりを示します。 -各パスには**1～8**のパスステップがこの順序で含まれています[[ソース]](https://github.com/XRPLF/rippled/blob/4cff94f7a4a05302bdf1a248515379da99c5bcd4/src/ripple/app/tx/impl/Payment.h#L38-L39 "Source")。各ステップは**タイプ**を示すバイトで始まり、その後にパスステップを記述する1つ以上のフィールドが続きます。タイプは、ビット単位のフラグを使用してそのパスステップに含まれるフィールドを示します。（たとえば値が`0x30`の場合、通貨とイシュアーの両方が変更されます。）複数のフィールドが含まれている場合、フィールドは常に特定の順序で配置されます。 +各パスには**1～8**のパスステップがこの順序で含まれています[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/Payment.h#L38-L39 "Source")。各ステップは**タイプ**を示すバイトで始まり、その後にパスステップを記述する1つ以上のフィールドが続きます。タイプは、ビット単位のフラグを使用してそのパスステップに含まれるフィールドを示します。（たとえば値が`0x30`の場合、通貨とイシュアーの両方が変更されます。）複数のフィールドが含まれている場合、フィールドは常に特定の順序で配置されます。 以下の表に、有効なフィールドと、タイプバイトでフィールドを示すために設定されるビット単位のフラグを示します。 diff --git a/@l10n/ja/docs/references/protocol/data-types/basic-data-types.md b/@l10n/ja/docs/references/protocol/data-types/basic-data-types.md index c69273a48e1..d2c251192a6 100644 --- a/@l10n/ja/docs/references/protocol/data-types/basic-data-types.md +++ b/@l10n/ja/docs/references/protocol/data-types/basic-data-types.md @@ -28,7 +28,7 @@ seo: ### ハッシュプレフィクス -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/HashPrefix.h "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/HashPrefix.h "Source") 多くの場合、XRP Ledgerではオブジェクトのバイナリデータに4バイトのプレフィクスを付けてからハッシュを計算するため、異なるタイプのオブジェクトが同じバイナリフォーマットである場合でも、異なるハッシュが設定されます。既存の4バイトコードは、ASCIIでエンコードされた英字3文字の後に0バイトが続く構成となっています。 diff --git a/@l10n/ja/docs/references/protocol/ledger-data/common-fields.md b/@l10n/ja/docs/references/protocol/ledger-data/common-fields.md index b0cb458ee1d..7a9ed1e5256 100644 --- a/@l10n/ja/docs/references/protocol/ledger-data/common-fields.md +++ b/@l10n/ja/docs/references/protocol/ledger-data/common-fields.md @@ -4,7 +4,7 @@ seo: description: これらの共通フィールドは、すべてのレジャーエントリの一部です。 --- # Ledger Entryの共通フィールド -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/impl/LedgerFormats.cpp) +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/libxrpl/protocol/LedgerFormats.cpp) [レジャー](../../../concepts/ledgers/index.md)の状態データの各エントリは、同じ共通フィールドのセットと、[レジャーエントリのタイプ](ledger-entry-types/index.md)に基づく追加フィールドを持ちます。フィールド名は大文字と小文字を区別します。すべてのレジャーエントリの共通フィールドは以下の通りです。 @@ -19,9 +19,9 @@ seo: ## Ledger Entry ID -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/impl/Indexes.cpp) +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/libxrpl/protocol/Indexes.cpp) -各レジャーエントリには一意のIDがあります。IDは、エントリの重要な内容と[名前空間識別子](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/LedgerFormats.h)をハッシュすることで得られます。[レジャーエントリのタイプ](ledger-entry-types/index.md)は、使用する名前空間識別子と、ハッシュに含めるコンテンツを決定します。これにより、すべてのIDが一意になります。ハッシュ関数は[SHA-512Half][]です。 +各レジャーエントリには一意のIDがあります。IDは、エントリの重要な内容と[名前空間識別子](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/LedgerFormats.h)をハッシュすることで得られます。[レジャーエントリのタイプ](ledger-entry-types/index.md)は、使用する名前空間識別子と、ハッシュに含めるコンテンツを決定します。これにより、すべてのIDが一意になります。ハッシュ関数は[SHA-512Half][]です。 一般的に、レジャーエントリのIDはJSONの`index`フィールドとして、オブジェクトの内容と同じレベルで返されます。[トランザクションのメタデータ](../transactions/metadata.md)では、JSONにおけるレジャーオブジェクトのIDは`LedgerIndex`です。 diff --git a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/accountroot.md b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/accountroot.md index 3b7a11618e7..1bca0e945e6 100644 --- a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/accountroot.md +++ b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/accountroot.md @@ -8,7 +8,7 @@ labels: - XRP --- # AccountRoot -[[ソース]](https://github.com/xrplf/rippled/blob/5d2d88209f1732a0f8d592012094e345cbe3e675/src/ripple/protocol/impl/LedgerFormats.cpp#L27 "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/detail/ledger_entries.macro#L147-L170 "Source") `AccountRoot`オブジェクトタイプは、1つの[アカウント](../../../../concepts/accounts/index.md)、そのアカウントの設定、XRP残高を記述します。 @@ -44,7 +44,7 @@ labels: | `AMMID` | 文字列 | UInt256 | いいえ | _([AMM amendment][]により追加されました。)_ 対応するAMMレジャーエントリのレジャーエントリID。アカウント作成時に設定します。AMM以外のアカウントでは常に省略されます。 | | `Balance` | 文字列 | Amount | いいえ | アカウントの現在の[drop単位のXRP残高][XRP、drop単位]で、文字列で表現されます。 | | `BurnedNFTokens` | 数値 | UInt32 | いいえ | このアカウントで発行された [非代替性トークン](../../../../concepts/tokens/nfts/index.md) のうち、バーンしたトークンの総数を表します。この数値は常に `MintedNFTokens` と同じかそれ以下となります。 | -| `Domain` | 文字列 | VariableLength | いいえ | このアカウントに関連付けられたドメイン。JSONでは、ドメインのASCII表現を16進数で表現します。[256バイトを超える長さは使用できません](https://github.com/xrplf/rippled/blob/55dc7a252e08a0b02cd5aa39e9b4777af3eafe77/src/ripple/app/tx/impl/SetAccount.h#L34) | +| `Domain` | 文字列 | VariableLength | いいえ | このアカウントに関連付けられたドメイン。JSONでは、ドメインのASCII表現を16進数で表現します。[256バイトを超える長さは使用できません](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/SetAccount.h#L34) | | `EmailHash` | 文字列 | Hash128 | いいえ | メールアドレスのmd5ハッシュ。クライアントはこれを使用してサービス内で[Gravatar](https://ja.gravatar.com/)などのアバターを検索できます。 | | [`Flags`](#accountrootのフラグ) | 数値 | UInt32 | はい | このアカウントに対して有効になっているブールフラグのビットマップ。 | | `LedgerEntryType` | 文字列 | UInt16 | はい | 値`0x0061`で文字列`AccountRoot`にマッピングされ、AccountRootオブジェクトであることを示します。 | diff --git a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/amendments.md b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/amendments.md index 82f16a6c80a..77463d66950 100644 --- a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/amendments.md +++ b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/amendments.md @@ -7,7 +7,7 @@ labels: - ブロックチェーン --- # Amendments -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/impl/LedgerFormats.cpp#L110-L113 "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/detail/ledger_entries.macro#L200-L205 "Source") `Amendments`オブジェクトタイプには、現在アクティブな[Amendment](../../../../concepts/networks-and-servers/amendments.md)のリストが含まれています。各レジャーバージョンには**最大で1つの**`Amendments`オブジェクトが含まれています。 diff --git a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/amm.md b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/amm.md index f55322cfd08..57caeedb560 100644 --- a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/amm.md +++ b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/amm.md @@ -7,7 +7,7 @@ labels: - AMM --- # AMM -[[ソース]](https://github.com/xrplf/rippled/blob/c1e4bfb08bcc9f187d794a71d653003a6148dc68/src/ripple/protocol/impl/LedgerFormats.cpp#L265-L275 "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/detail/ledger_entries.macro#L386-L397 "Source") _([AMM amendment][]により追加されました。)_ diff --git a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/bridge.md b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/bridge.md index 2aaf48a7d4c..a08ce4d9b1e 100644 --- a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/bridge.md +++ b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/bridge.md @@ -10,7 +10,7 @@ status: not_enabled # Bridge _（[XChainBridge Amendment][] {% not-enabled /%} が必要です）_ -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/impl/LedgerFormats.cpp#L286-L300 "ソース") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/detail/ledger_entries.macro#L225-L236 "ソース") `Bridge`レジャーエントリは、XRP Ledgerをサイドチェーンなどの別のブロックチェーンと接続し、XRPやその他のトークン(IOU)の形で2つのブロックチェーン間を効率的に移動することを可能にする、1つのクロスチェーンブリッジを表します。 diff --git a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/check.md b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/check.md index f04e2209a88..7455b0266d7 100644 --- a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/check.md +++ b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/check.md @@ -7,7 +7,7 @@ labels: - Checks --- # Check -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/impl/LedgerFormats.cpp#L157-L170 "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/detail/ledger_entries.macro#L61-L74 "Source") _（[Checks Amendment][]が必要です）_ @@ -65,7 +65,7 @@ _（[Checks Amendment][]が必要です）_ ## Check IDのフォーマット -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/impl/Indexes.cpp#L193-L200 "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/libxrpl/protocol/Indexes.cpp#L195-L201 "Source") `Check`オブジェクトのIDは、以下の値がこの順序で連結されている[SHA-512ハーフ][]です。 diff --git a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/depositpreauth.md b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/depositpreauth.md index 56479b3a3f5..8e38379c132 100644 --- a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/depositpreauth.md +++ b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/depositpreauth.md @@ -7,7 +7,7 @@ labels: - セキュリティ --- # DepositPreauth -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/impl/LedgerFormats.cpp#L172-L178 "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/detail/ledger_entries.macro#L261-L268 "Source") `DepositPreauth`エントリは、1つのアカウントからの事前承認を追跡します。常に[DepositPreauthトランザクション][]を送信することで事前承認を作成できますが、[Deposit Authorization](../../../../concepts/accounts/depositauth.md)を使用していない限り、効果はありません。 diff --git a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/did.md b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/did.md index ed0136374c8..77d022cec84 100644 --- a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/did.md +++ b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/did.md @@ -7,7 +7,7 @@ labels: - DID --- # DID -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/impl/LedgerFormats.cpp#L330-L341 "ソース) +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/detail/ledger_entries.macro#L80-L88 "ソース) _([DID Amendment][])_ diff --git a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/directorynode.md b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/directorynode.md index 3f6a7b3f2b5..72e32460db3 100644 --- a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/directorynode.md +++ b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/directorynode.md @@ -6,7 +6,7 @@ labels: - 分散型取引所 --- # DirectoryNode -[[ソース]](https://github.com/XRPLF/rippled/blob/5d2d88209f1732a0f8d592012094e345cbe3e675/src/ripple/protocol/impl/LedgerFormats.cpp#L44 "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/detail/ledger_entries.macro#L177-L192 "Source") `DirectoryNode`オブジェクトタイプは、レジャーの状態ツリー内の他オブジェクトへのリンクのリストを提供します。概念上の1つの _ディレクトリ_ は、1つ以上の各DirectoryNodeオブジェクトが含まれる二重リンクリストの形式になっています。各DirectoryNodeオブジェクトには、他オブジェクトの[ID](../common-fields.md)が最大32個まで含まれています。1番目のオブジェクトはディレクトリのルートと呼ばれ、ルートオブジェクト以外のオブジェクトはすべて必要に応じて自由に追加または削除できます。 diff --git a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/escrow.md b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/escrow.md index 351399b79da..71564890376 100644 --- a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/escrow.md +++ b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/escrow.md @@ -7,7 +7,7 @@ labels: - Escrow --- # Escrow -[[ソース]](https://github.com/XRPLF/rippled/blob/c6b6d82a754fe449cc533e18659df483c10a5c98/src/ripple/protocol/impl/LedgerFormats.cpp#L90-L101 "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/detail/ledger_entries.macro#L344-L359 "Source") _（[Escrow Amendment][]により追加されました。）_ diff --git a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/feesettings.md b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/feesettings.md index 66143d69a67..6ba347d4342 100644 --- a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/feesettings.md +++ b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/feesettings.md @@ -7,7 +7,7 @@ labels: - 手数料 --- # FeeSettings -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/impl/LedgerFormats.cpp#L115-L120 "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/detail/ledger_entries.macro#L312-L324 "Source") `FeeSettings`オブジェク トタイプには、現在の基本[トランザクションコスト](../../../../concepts/transactions/transaction-cost.md)と、[手数料投票](../../../../concepts/consensus-protocol/fee-voting.md)により決定する[準備金の額](../../../../concepts/accounts/reserves.md)が含まれています。各レジャーバージョンには**最大で1つの** `FeeSettings`オブジェクトが含まれています。 diff --git a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/ledgerhashes.md b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/ledgerhashes.md index 90ef7b96902..d3031789712 100644 --- a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/ledgerhashes.md +++ b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/ledgerhashes.md @@ -7,7 +7,7 @@ labels: - ブロックチェーン --- # LedgerHashes -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/impl/LedgerFormats.cpp#L104-L108 "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/detail/ledger_entries.macro#L215-L219 "Source") （レジャーバージョンを一意に示す[「ledger hash」文字列データ型][ハッシュ]と混同しないでください。このセクションでは、`LedgerHashes`レジャーオブジェクトタイプについて説明します。） @@ -65,7 +65,7 @@ labels: 「過去の履歴」`LedgerHashes`オブジェクトは[スキップリスト](https://en.wikipedia.org/wiki/Skip_list)として機能するので、任意の履歴フラッグレジャーのハッシュをそのインデックスから取得できます。さらに、フラッグレジャーの「最近の履歴」オブジェクトを使用してその他のレジャーのハッシュを取得できます。 ## LedgerHashes IDのフォーマット -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/impl/Indexes.cpp#L26-L42) +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/libxrpl/protocol/Indexes.cpp#L26-L42) `LedgerHashes`オブジェクトIDには2種類のフォーマットがあります。これは、オブジェクトのサブタイプが「最近の履歴」と「過去の履歴」のいずれであるかに応じて決まります。 diff --git a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/offer.md b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/offer.md index d38cd51b081..7a67ad1f9d6 100644 --- a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/offer.md +++ b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/offer.md @@ -7,7 +7,7 @@ labels: - 分散型取引所 --- # Offer -[[ソース]](https://github.com/XRPLF/rippled/blob/5d2d88209f1732a0f8d592012094e345cbe3e675/src/ripple/protocol/impl/LedgerFormats.cpp#L57 "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/detail/ledger_entries.macro#L242-L255 "Source") 台帳の`Offer`エントリは、XRP Ledgerの[分散型取引所](../../../../concepts/tokens/decentralized-exchange/index.md)で通貨を交換する[オファー](../../../../concepts/tokens/decentralized-exchange/offers.md)を表しています。（金融ではより伝統的に _オーダー_ として知られています）。[OfferCreateトランザクション][]は台帳にある他のOfferを全額約定できない場合、台帳に`Offer`エントリを作成します。 diff --git a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/oracle.md b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/oracle.md index 0c654008708..c05ebaf7566 100644 --- a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/oracle.md +++ b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/oracle.md @@ -2,7 +2,7 @@ _([PriceOracle Amendment][])_ -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/impl/LedgerFormats.cpp#L353-L366 "ソース") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/detail/ledger_entries.macro#L385-L395 "ソース") Oracleのレジャーエントリには、単一資産の価格オラクルオブジェクトに関連するデータが格納されています。 diff --git a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/paychannel.md b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/paychannel.md index 68f9ebd4717..8cdd96c2818 100644 --- a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/paychannel.md +++ b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/paychannel.md @@ -7,7 +7,7 @@ labels: - Payment Channel --- # PayChannel -[[ソース]](https://github.com/XRPLF/rippled/blob/c0a0b79d2d483b318ce1d82e526bd53df83a4a2c/src/ripple/protocol/impl/LedgerFormats.cpp#L180-L198 "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/detail/ledger_entries.macro#L365-L380 "Source") _（[PayChan Amendment][]により追加されました。）_ diff --git a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/ripplestate.md b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/ripplestate.md index ec713794374..ec46bb4ae60 100644 --- a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/ripplestate.md +++ b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/ripplestate.md @@ -7,7 +7,7 @@ labels: - トークン --- # RippleState -[[ソース]](https://github.com/XRPLF/rippled/blob/5d2d88209f1732a0f8d592012094e345cbe3e675/src/ripple/protocol/impl/LedgerFormats.cpp#L70 "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/detail/ledger_entries.macro#L292-L304 "Source") `RippleState`のレジャーエントリは、2つのアカウント間の[トラストライン](../../../../concepts/tokens/fungible-tokens/index.md)を表します。各アカウントは限度額やその他の設定を変更できますが、残高は共通の値です。完全にデフォルトのトラストラインは、存在しないトラストラインと同じとみなされ、自動的に削除されます。 diff --git a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/signerlist.md b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/signerlist.md index 930a9a99076..fdabe8e177b 100644 --- a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/signerlist.md +++ b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/signerlist.md @@ -7,7 +7,7 @@ labels: - セキュリティ --- # SignerList -[[ソース]](https://github.com/XRPLF/rippled/blob/6d2e3da30696bd10e3bb11a5ff6d45d2c4dae90f/src/ripple/protocol/impl/LedgerFormats.cpp#L127 "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/detail/ledger_entries.macro#L122-L129 "Source") _（[MultiSign Amendment][]により追加されました。）_ diff --git a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/ticket.md b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/ticket.md index 4cdaee975eb..bb1dd4bfe9f 100644 --- a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/ticket.md +++ b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/ticket.md @@ -8,7 +8,7 @@ labels: --- # Ticket -[[ソース]](https://github.com/XRPLF/rippled/blob/76a6956138c4ecd156c5c408f136ed3d6ab7d0c1/src/ripple/protocol/impl/LedgerFormats.cpp#L155-L164) +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/detail/ledger_entries.macro#L135-L141 "Source") _([TicketBatch amendment][]が必要です)_ diff --git a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/xchainownedclaimid.md b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/xchainownedclaimid.md index 838e9eafcb2..e59ea8b3fdd 100644 --- a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/xchainownedclaimid.md +++ b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/xchainownedclaimid.md @@ -10,7 +10,7 @@ status: not_enabled # XChainOwnedClaimID _（[XChainBridge Amendment][] {% not-enabled /%} が必要です）_ -[[ソース]](https://github.com/seelabs/rippled/blob/xbridge/src/ripple/protocol/impl/LedgerFormats.cpp#L281-L293 "ソース") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/detail/ledger_entries.macro#L274-L284 "ソース") `XChainOwnedClaimID`オブジェクトはクロスチェーンでの価値の移転の*1つ*を表し、送金元チェーン上の資金をロックまたはバーンする送金元チェーン上のアカウントの情報を含みます。 diff --git a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/xchainownedcreateaccountclaimid.md b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/xchainownedcreateaccountclaimid.md index f2f69edb5f2..2d42196d9b8 100644 --- a/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/xchainownedcreateaccountclaimid.md +++ b/@l10n/ja/docs/references/protocol/ledger-data/ledger-entry-types/xchainownedcreateaccountclaimid.md @@ -10,7 +10,7 @@ status: not_enabled # XChainOwnedCreateAccountClaimID _（[XChainBridge Amendment][] {% not-enabled /%} が必要です）_ -[[ソース]](https://github.com/seelabs/rippled/blob/xbridge/src/ripple/protocol/impl/LedgerFormats.cpp#L296-L306 "ソース") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/detail/ledger_entries.macro#L330-L338 "ソース") `XChainOwnedCreateAccountClaimID`レジャーオブジェクトは、クロスチェーン送金でアカウントを作成するための証明を収集するために使用されます。 diff --git a/@l10n/ja/docs/references/protocol/ledger-data/ledger-header.md b/@l10n/ja/docs/references/protocol/ledger-data/ledger-header.md index de6b766ae8e..2834c03fbc3 100644 --- a/@l10n/ja/docs/references/protocol/ledger-data/ledger-header.md +++ b/@l10n/ja/docs/references/protocol/ledger-data/ledger-header.md @@ -8,7 +8,7 @@ labels: - ブロックチェーン --- # レジャーヘッダー -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/ledger/ReadView.h#L71 "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/ledger/ReadView.h#L51 "Source") すべてのレジャーバージョンには、その内容を記述する一意のヘッダーが含まれています。[ledgerメソッド][]を使用してレジャーのヘッダー情報を検索できます。レジャーヘッダーの内容を以下に示します。 diff --git a/@l10n/ja/docs/references/protocol/transactions/transaction-results/index.md b/@l10n/ja/docs/references/protocol/transactions/transaction-results/index.md index 99bb776b6e6..6c8d32253d7 100644 --- a/@l10n/ja/docs/references/protocol/transactions/transaction-results/index.md +++ b/@l10n/ja/docs/references/protocol/transactions/transaction-results/index.md @@ -8,7 +8,7 @@ labels: --- # トランザクションの結果 -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/TER.h "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/TER.h "Source") `rippled`サーバは、トランザクション結果の要約を結果コードで示し、結果コードは`engine_result`や`meta.TransactionResult`などのフィールドに記述されます。これらのコードは、それぞれ異なるプレフィクスを付加した複数のカテゴリに分類されます。 diff --git a/@l10n/ja/docs/references/protocol/transactions/transaction-results/tec-codes.md b/@l10n/ja/docs/references/protocol/transactions/transaction-results/tec-codes.md index 10b483ee1a8..4e7319fde56 100644 --- a/@l10n/ja/docs/references/protocol/transactions/transaction-results/tec-codes.md +++ b/@l10n/ja/docs/references/protocol/transactions/transaction-results/tec-codes.md @@ -7,7 +7,7 @@ labels: - トランザクション送信 --- # tecコード -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/impl/TER.cpp "ソース") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/libxrpl/protocol/TER.cpp "ソース") これらのコードは、トランザクションは失敗したものの、[トランザクションコスト](../../../../concepts/transactions/transaction-cost.md)を適用するために、このトランザクションがレジャーに適用されたことを示します。100から199までの数値が含まれています。数値ではなくテキストコードの使用が推奨されます。 diff --git a/@l10n/ja/docs/references/protocol/transactions/types/accountdelete.md b/@l10n/ja/docs/references/protocol/transactions/types/accountdelete.md index dae0411cca4..896bac5fac6 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/accountdelete.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/accountdelete.md @@ -8,7 +8,7 @@ labels: --- # AccountDelete -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/DeleteAccount.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/DeleteAccount.cpp "Source") _[DeletableAccounts Amendment](/resources/known-amendments.md#deletableaccounts)が必要です_ diff --git a/@l10n/ja/docs/references/protocol/transactions/types/accountset.md b/@l10n/ja/docs/references/protocol/transactions/types/accountset.md index aa629b5bab0..79d37759d40 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/accountset.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/accountset.md @@ -8,7 +8,7 @@ labels: --- # AccountSet -[[ソース]](https://github.com/XRPLF/rippled/blob/f65cea66ef99b1de149c02c15f06de6c61abf360/src/ripple/app/transactors/SetAccount.cpp "ソース") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/SetAccount.cpp "ソース") AccountSetトランザクションは、[XRP Ledgerのアカウント](../../ledger-data/ledger-entry-types/accountroot.md)のプロパティーを修正します。 @@ -33,7 +33,7 @@ AccountSetトランザクションは、[XRP Ledgerのアカウント](../../led | フィールド | JSONの型 | [内部の型][] | 説明 | |:-----------------|:-----------------|:------------------|:-------------------| | [`ClearFlag`](#accountsetのフラグ) | 数値 | UInt32 | _（省略可）_ このアカウントについてオプションを無効にするためのフラグの一意識別子。 | -| [`Domain`](#domain) | 文字列 | Blob | _（省略可）_ このアカウントを保有するドメインのASCII小文字を表現する16進文字列。[256バイトを超える長さは使用できません。](https://github.com/XRPLF/rippled/blob/55dc7a252e08a0b02cd5aa39e9b4777af3eafe77/src/ripple/app/tx/impl/SetAccount.h#L34) | +| [`Domain`](#domain) | 文字列 | Blob | _（省略可）_ このアカウントを保有するドメインのASCII小文字を表現する16進文字列。[256バイトを超える長さは使用できません。](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/SetAccount.h#L34) | | `EmailHash` | 文字列 | Hash128 | _（省略可）_ アバターイメージの生成に使用されるメールアドレスのハッシュ。一般的に、クライアントは[Gravatar](http://en.gravatar.com/site/implement/hash/)を使用してこのイメージを表示しています。 | | `MessageKey` | 文字列 | Blob | _（省略可）_ 暗号化されたメッセージをこのアカウントに送信するための公開鍵です。キーを設定するには、正確に33バイトである必要があり、最初のバイトはキーの種類を示します。secp256k1鍵の場合は`0x02`または`0x03`、Ed25519鍵の場合は`0xED`です。キーを削除するには、空の値を使用します。 | | `NFTokenMinter` | 文字列 | Blob | _(省略可)_ あなたのために[NFTokensをミントする](../../../../tutorials/javascript/nfts/assign-an-authorized-minter.md)ことができる別のアカウント。 _([NonFungibleTokensV1_1 amendment][]により追加されました.)_ | diff --git a/@l10n/ja/docs/references/protocol/transactions/types/ammbid.md b/@l10n/ja/docs/references/protocol/transactions/types/ammbid.md index 6a72a781aed..d223a3e8196 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/ammbid.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/ammbid.md @@ -7,7 +7,7 @@ labels: - AMM --- # AMMBid -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/AMMBid.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/AMMBid.cpp "Source") _([AMM amendment][]により追加されました。)_ diff --git a/@l10n/ja/docs/references/protocol/transactions/types/ammcreate.md b/@l10n/ja/docs/references/protocol/transactions/types/ammcreate.md index 993a1f87f27..c3f39c8830e 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/ammcreate.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/ammcreate.md @@ -7,7 +7,7 @@ labels: - AMM --- # AMMCreate -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/AMMCreate.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/AMMCreate.cpp "Source") _([AMM amendment][]により追加されました。)_ diff --git a/@l10n/ja/docs/references/protocol/transactions/types/ammdelete.md b/@l10n/ja/docs/references/protocol/transactions/types/ammdelete.md index 43a6dbde74e..189cb798b69 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/ammdelete.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/ammdelete.md @@ -7,7 +7,7 @@ labels: - AMM --- # AMMDelete -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/AMMDelete.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/AMMDelete.cpp "Source") _([AMM amendment][]により追加されました。)_ diff --git a/@l10n/ja/docs/references/protocol/transactions/types/ammdeposit.md b/@l10n/ja/docs/references/protocol/transactions/types/ammdeposit.md index 4942f812266..ff556d2fbf0 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/ammdeposit.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/ammdeposit.md @@ -7,7 +7,7 @@ labels: - AMM --- # AMMDeposit -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/AMMDeposit.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/AMMDeposit.cpp "Source") _([AMM amendment][]により追加されました。)_ diff --git a/@l10n/ja/docs/references/protocol/transactions/types/ammvote.md b/@l10n/ja/docs/references/protocol/transactions/types/ammvote.md index 65d7779f7d7..7f63806e1d2 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/ammvote.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/ammvote.md @@ -7,7 +7,7 @@ labels: - AMM --- # AMMVote -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/AMMVote.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/AMMVote.cpp "Source") _([AMM amendment][]により追加されました。)_ diff --git a/@l10n/ja/docs/references/protocol/transactions/types/ammwithdraw.md b/@l10n/ja/docs/references/protocol/transactions/types/ammwithdraw.md index 4ea09812b2a..890eef2180a 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/ammwithdraw.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/ammwithdraw.md @@ -7,7 +7,7 @@ labels: - AMM --- # AMMWithdraw -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/AMMWithdraw.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/AMMWithdraw.cpp "Source") _([AMM amendment][]により追加されました。)_ diff --git a/@l10n/ja/docs/references/protocol/transactions/types/batch.md b/@l10n/ja/docs/references/protocol/transactions/types/batch.md index 678956260e2..5cd4c3029a2 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/batch.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/batch.md @@ -7,7 +7,7 @@ labels: status: not_enabled --- # Batch -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/Batch.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/Batch.cpp "Source") `Batch`トランザクションは、最大8つのトランザクションを単一のバッチで送信します。各トランザクションは、4つのモード(全て成功または全て失敗（All or Nothing）、一つのみ成功（Only One）、失敗まで継続（Until Failure）、および独立実行（Independent）)のいずれかでアトミックに実行されます。 diff --git a/@l10n/ja/docs/references/protocol/transactions/types/checkcancel.md b/@l10n/ja/docs/references/protocol/transactions/types/checkcancel.md index 3b0eb19bb14..df7eefb3afa 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/checkcancel.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/checkcancel.md @@ -7,7 +7,7 @@ labels: - Checks --- # CheckCancel -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/CancelCheck.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/CancelCheck.cpp "Source") _（[Checks Amendment][]が必要です）_ diff --git a/@l10n/ja/docs/references/protocol/transactions/types/checkcash.md b/@l10n/ja/docs/references/protocol/transactions/types/checkcash.md index 8d56f100048..a4f74bf9958 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/checkcash.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/checkcash.md @@ -7,7 +7,7 @@ labels: - Checks --- # CheckCash -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/CashCheck.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/CashCheck.cpp "Source") _（[Checks Amendment][]が必要です）_ diff --git a/@l10n/ja/docs/references/protocol/transactions/types/checkcreate.md b/@l10n/ja/docs/references/protocol/transactions/types/checkcreate.md index 856564ba415..f847932df4e 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/checkcreate.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/checkcreate.md @@ -7,7 +7,7 @@ labels: - Checks --- # CheckCreate -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/CreateCheck.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/CreateCheck.cpp "Source") _（[Checks Amendment][]が必要です）_ diff --git a/@l10n/ja/docs/references/protocol/transactions/types/clawback.md b/@l10n/ja/docs/references/protocol/transactions/types/clawback.md index 79297b4e095..49c1f8e9f1d 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/clawback.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/clawback.md @@ -8,7 +8,7 @@ labels: --- # Clawback -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/Clawback.cpp "ソース") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/Clawback.cpp "ソース") {% partial file="/@l10n/ja/docs/_snippets/clawback-disclaimer.md" /%} diff --git a/@l10n/ja/docs/references/protocol/transactions/types/depositpreauth.md b/@l10n/ja/docs/references/protocol/transactions/types/depositpreauth.md index 5d524017099..1ef69ac2aef 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/depositpreauth.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/depositpreauth.md @@ -7,7 +7,7 @@ labels: - セキュリティ --- # DepositPreauth -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/DepositPreauth.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/DepositPreauth.cpp "Source") _[DepositPreauth Amendment][]により追加されました。_ diff --git a/@l10n/ja/docs/references/protocol/transactions/types/diddelete.md b/@l10n/ja/docs/references/protocol/transactions/types/diddelete.md index aa441686b74..f14771aa081 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/diddelete.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/diddelete.md @@ -8,7 +8,7 @@ labels: --- # DIDDelete -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/DID.cpp "ソース") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/DID.cpp "ソース") _([DID Amendment][])_ diff --git a/@l10n/ja/docs/references/protocol/transactions/types/didset.md b/@l10n/ja/docs/references/protocol/transactions/types/didset.md index 7aa41bdc736..aa0714a33d9 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/didset.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/didset.md @@ -8,7 +8,7 @@ labels: --- # DIDSet -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/DID.cpp "ソース") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/DID.cpp "ソース") _([DID Amendment][])_ diff --git a/@l10n/ja/docs/references/protocol/transactions/types/escrowcancel.md b/@l10n/ja/docs/references/protocol/transactions/types/escrowcancel.md index 8dd6289f366..0a29b40483e 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/escrowcancel.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/escrowcancel.md @@ -8,7 +8,7 @@ labels: --- # EscrowCancel -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/Escrow.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/Escrow.cpp "Source") _[Escrow Amendment][]により追加されました。_ diff --git a/@l10n/ja/docs/references/protocol/transactions/types/escrowcreate.md b/@l10n/ja/docs/references/protocol/transactions/types/escrowcreate.md index c2ac28fe8ed..8e61181ad44 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/escrowcreate.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/escrowcreate.md @@ -8,7 +8,7 @@ labels: --- # EscrowCreate -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/Escrow.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/Escrow.cpp "Source") _[Escrow Amendment][]により追加されました。_ diff --git a/@l10n/ja/docs/references/protocol/transactions/types/escrowfinish.md b/@l10n/ja/docs/references/protocol/transactions/types/escrowfinish.md index c62a3e04bfe..f5f51a98642 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/escrowfinish.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/escrowfinish.md @@ -8,7 +8,7 @@ labels: --- # EscrowFinish -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/Escrow.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/Escrow.cpp "Source") エスクロー(保留中の支払い)から受取人へXRPを送金します。 diff --git a/@l10n/ja/docs/references/protocol/transactions/types/mptokenauthorize.md b/@l10n/ja/docs/references/protocol/transactions/types/mptokenauthorize.md index c2fa2e0c8c1..9031d06450c 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/mptokenauthorize.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/mptokenauthorize.md @@ -7,7 +7,7 @@ labels: --- # MPTokenAuthorize -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/MPTokenAuthorize.cpp "ソース") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/MPTokenAuthorize.cpp "ソース") {% partial file="/@l10n/ja/docs/_snippets/mpts-disclaimer.md" /%} diff --git a/@l10n/ja/docs/references/protocol/transactions/types/mptokenissuancecreate.md b/@l10n/ja/docs/references/protocol/transactions/types/mptokenissuancecreate.md index 393027a8dc5..bcf546b9205 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/mptokenissuancecreate.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/mptokenissuancecreate.md @@ -7,7 +7,7 @@ labels: --- # MPTokenIssuanceCreate -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/MPTokenIssuanceCreate.cpp "ソース") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/MPTokenIssuanceCreate.cpp "ソース") {% partial file="/@l10n/ja/docs/_snippets/mpts-disclaimer.md" /%} diff --git a/@l10n/ja/docs/references/protocol/transactions/types/mptokenissuancedestroy.md b/@l10n/ja/docs/references/protocol/transactions/types/mptokenissuancedestroy.md index f4340bd6bed..0652449b6d4 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/mptokenissuancedestroy.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/mptokenissuancedestroy.md @@ -6,7 +6,7 @@ labels: - Multi-Purpose Token, MPT --- # MPTokenIssuanceDestroy -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/MPTokenIssuanceDestroy.cpp "ソース") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/MPTokenIssuanceDestroy.cpp "ソース") {% partial file="/@l10n/ja/docs/_snippets/mpts-disclaimer.md" /%} diff --git a/@l10n/ja/docs/references/protocol/transactions/types/mptokenissuanceset.md b/@l10n/ja/docs/references/protocol/transactions/types/mptokenissuanceset.md index db158dcdca4..2ec27732e9e 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/mptokenissuanceset.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/mptokenissuanceset.md @@ -6,7 +6,7 @@ labels: - Multi-Purpose Token, MPT --- # MPTokenIssuanceSet -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/MPTokenIssuanceSet.cpp "ソース") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/MPTokenIssuanceSet.cpp "ソース") {% partial file="/@l10n/ja/docs/_snippets/mpts-disclaimer.md" /%} diff --git a/@l10n/ja/docs/references/protocol/transactions/types/nftokenacceptoffer.md b/@l10n/ja/docs/references/protocol/transactions/types/nftokenacceptoffer.md index 6081d43deba..669edbe5939 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/nftokenacceptoffer.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/nftokenacceptoffer.md @@ -7,7 +7,7 @@ labels: - NFT, 非代替性トークン --- # NFTokenAcceptOffer -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/NFTokenAcceptOffer.cpp "ソース") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/NFTokenAcceptOffer.cpp "ソース") `NFTokenAcceptOffer`トランザクションは`NFToken`の購入または売却のオファーを受け入れるために使用されます。トランザクションは次のいずれかになります。 diff --git a/@l10n/ja/docs/references/protocol/transactions/types/nftokencreateoffer.md b/@l10n/ja/docs/references/protocol/transactions/types/nftokencreateoffer.md index cf9db3169c3..29cc8f19e31 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/nftokencreateoffer.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/nftokencreateoffer.md @@ -7,7 +7,7 @@ labels: - 非代替性トークン, NFT --- # NFTokenCreateOffer -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/NFTokenCreateOffer.cpp "ソース") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/NFTokenCreateOffer.cpp "ソース") トランザクションを送信するアカウントが所有する`NFToken`に対する新しい _売却_ オファー、または別のアカウントが所有する`NFToken`に対する新しい _購入_ オファーを作成します。 diff --git a/@l10n/ja/docs/references/protocol/transactions/types/nftokenmint.md b/@l10n/ja/docs/references/protocol/transactions/types/nftokenmint.md index d1cf633eaf4..c4c9d036cb0 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/nftokenmint.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/nftokenmint.md @@ -5,7 +5,7 @@ labels: - 非代替性トークン, NFT --- # NFTokenMint -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/NFTokenMint.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/NFTokenMint.cpp "Source") `NFTokenMint`トランザクションは非代替性トークンを作成し、`NFTokenMinter`に紐付く[NFTokenPageオブジェクト][]に[NFToken][]オブジェクトとして追加します。このトランザクションは`NFTokenMinter`にとって、不変と定義されているトークンフィールド(例えば`Flags`)を設定することができる唯一の方法です。 diff --git a/@l10n/ja/docs/references/protocol/transactions/types/nftokenmodify.md b/@l10n/ja/docs/references/protocol/transactions/types/nftokenmodify.md index 2a894c4e6ee..8c80c86e992 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/nftokenmodify.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/nftokenmodify.md @@ -7,7 +7,7 @@ title: - NFTokenModify --- # NFTokenModify -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/NFTokenModify.cpp "ソース") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/NFTokenModify.cpp "ソース") `NFTokenModify`は、NFTの`URI`フィールドを別のURIに変更し、NFTのサポートデータを更新するために使用されます。NFTは、`tfMutable`フラグが設定された状態でミントされている必要があります。[ダイナミックNFT](../../../../concepts/tokens/nfts/dynamic-nfts.md)をご覧ください。 diff --git a/@l10n/ja/docs/references/protocol/transactions/types/offercancel.md b/@l10n/ja/docs/references/protocol/transactions/types/offercancel.md index 65e0a07c9de..4ed622be7de 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/offercancel.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/offercancel.md @@ -8,7 +8,7 @@ labels: --- # OfferCancel -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/CancelOffer.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/CancelOffer.cpp "Source") OfferCancelトランザクションは、XRP LedgerからOfferオブジェクトを削除します。 diff --git a/@l10n/ja/docs/references/protocol/transactions/types/offercreate.md b/@l10n/ja/docs/references/protocol/transactions/types/offercreate.md index 2f0a0d862ea..63d2ccb4be0 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/offercreate.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/offercreate.md @@ -8,7 +8,7 @@ labels: --- # OfferCreate -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/CreateOffer.cpp "ソース") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/CreateOffer.cpp "ソース") OfferCreateトランザクションは[分散型取引所](../../../../concepts/tokens/decentralized-exchange/index.md)で[注文](../../../../concepts/tokens/decentralized-exchange/offers.md)を作成します。 diff --git a/@l10n/ja/docs/references/protocol/transactions/types/oracledelete.md b/@l10n/ja/docs/references/protocol/transactions/types/oracledelete.md index d6272bf994e..c86e19a9be7 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/oracledelete.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/oracledelete.md @@ -8,7 +8,7 @@ labels: # OracleDelete _([PriceOracle Amendment][])_ -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/DeleteOracle.cpp "ソース") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/DeleteOracle.cpp "ソース") 既存の`Oracle`レジャーエントリを削除します。 diff --git a/@l10n/ja/docs/references/protocol/transactions/types/oracleset.md b/@l10n/ja/docs/references/protocol/transactions/types/oracleset.md index 3a0f0902f6d..b7ec45f5117 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/oracleset.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/oracleset.md @@ -8,7 +8,7 @@ labels: # OracleSet _([PriceOracle Amendment][])_ -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/SetOracle.cpp "ソース") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/SetOracle.cpp "ソース") Oracle Document ID を使用して、新しい`Oracle`レジャーエントリを作成するか、既存のフィールドを更新します。 diff --git a/@l10n/ja/docs/references/protocol/transactions/types/payment.md b/@l10n/ja/docs/references/protocol/transactions/types/payment.md index c7c9a9adda6..aa01fc91e5d 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/payment.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/payment.md @@ -10,7 +10,7 @@ labels: - トークン --- # Payment -[[ソース]](https://github.com/XRPLF/rippled/blob/5425a90f160711e46b2c1f1c93d68e5941e4bfb6/src/ripple/app/transactors/Payment.cpp "ソース") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/Payment.cpp "ソース") Paymentトランザクションは、アカウント間での価値の移動を表現するものです(通過するパスによっては、非可分的に発生する追加的な価値交換を伴うことがあります)。このトランザクションタイプはいくつかの[支払いの種類](#paymentの種類)に使用することがでできます。 diff --git a/@l10n/ja/docs/references/protocol/transactions/types/paymentchannelclaim.md b/@l10n/ja/docs/references/protocol/transactions/types/paymentchannelclaim.md index b985ba9f9dc..f2a7347d581 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/paymentchannelclaim.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/paymentchannelclaim.md @@ -7,7 +7,7 @@ labels: - Payment Channel --- # PaymentChannelClaim -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/PayChan.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/PayChan.cpp "Source") _[PayChan Amendment][]により追加されました。_ diff --git a/@l10n/ja/docs/references/protocol/transactions/types/paymentchannelcreate.md b/@l10n/ja/docs/references/protocol/transactions/types/paymentchannelcreate.md index 005fbce8188..4cc8a1d1d62 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/paymentchannelcreate.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/paymentchannelcreate.md @@ -7,7 +7,7 @@ labels: - Payment Channel --- # PaymentChannelCreate -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/PayChan.cpp "ソース") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/PayChan.cpp "ソース") _[PayChan Amendment][]により追加されました。_ diff --git a/@l10n/ja/docs/references/protocol/transactions/types/paymentchannelfund.md b/@l10n/ja/docs/references/protocol/transactions/types/paymentchannelfund.md index e36f5a0f75f..4a488ee235e 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/paymentchannelfund.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/paymentchannelfund.md @@ -7,7 +7,7 @@ labels: - Payment Channel --- # PaymentChannelFund -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/PayChan.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/PayChan.cpp "Source") _[PayChan Amendment][]により追加されました。_ diff --git a/@l10n/ja/docs/references/protocol/transactions/types/setregularkey.md b/@l10n/ja/docs/references/protocol/transactions/types/setregularkey.md index 5ca9813ba4e..81570558e99 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/setregularkey.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/setregularkey.md @@ -8,7 +8,7 @@ labels: --- # SetRegularKey -[[ソース]](https://github.com/XRPLF/rippled/blob/4239880acb5e559446d2067f00dabb31cf102a23/src/ripple/app/transactors/SetRegularKey.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/SetRegularKey.cpp "Source") `SetRegularKey`トランザクションは、アカウントに関連付けられているレギュラーキーペアの割り当て、変更、削除を行います。 diff --git a/@l10n/ja/docs/references/protocol/transactions/types/signerlistset.md b/@l10n/ja/docs/references/protocol/transactions/types/signerlistset.md index 58019a67192..4925c28df6d 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/signerlistset.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/signerlistset.md @@ -7,7 +7,7 @@ labels: - セキュリティ --- # SignerListSet -[[ソース]](https://github.com/XRPLF/rippled/blob/ef511282709a6a0721b504c6b7703f9de3eecf38/src/ripple/app/tx/impl/SetSignerList.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/SetSignerList.cpp "Source") SignerListSetトランザクションは、トランザクションの[マルチシグ](../../../../concepts/accounts/multi-signing.md)に使用できる署名者のリストを作成、置換、削除します。このトランザクションタイプは[MultiSign Amendment][]により導入されました。{% badge href="https://github.com/XRPLF/rippled/releases/tag/0.31.0" %}新規: rippled 0.31.0{% /badge %} diff --git a/@l10n/ja/docs/references/protocol/transactions/types/ticketcreate.md b/@l10n/ja/docs/references/protocol/transactions/types/ticketcreate.md index d40e2374b65..08c8a4e60c1 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/ticketcreate.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/ticketcreate.md @@ -8,7 +8,7 @@ labels: --- # TicketCreate -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/CreateTicket.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/CreateTicket.cpp "Source") _([TicketBatch amendment][]が必要です)_ diff --git a/@l10n/ja/docs/references/protocol/transactions/types/trustset.md b/@l10n/ja/docs/references/protocol/transactions/types/trustset.md index a406884511e..98662a7d98e 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/trustset.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/trustset.md @@ -8,7 +8,7 @@ labels: --- # TrustSet -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/SetTrust.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/SetTrust.cpp "Source") 2つのアカウントをリンクする[トラストライン](../../../../concepts/tokens/fungible-tokens/index.md)を作成または変更します。 diff --git a/@l10n/ja/docs/references/protocol/transactions/types/xchainaccountcreatecommit.md b/@l10n/ja/docs/references/protocol/transactions/types/xchainaccountcreatecommit.md index d0c4f62426f..5c5928e90a3 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/xchainaccountcreatecommit.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/xchainaccountcreatecommit.md @@ -8,7 +8,7 @@ labels: status: not_enabled --- # XChainAccountCreateCommit -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/impl/TxFormats.cpp#L466-L474 "ソース") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/XChainBridge.h#L254 "ソース") _（[XChainBridge Amendment][] {% not-enabled /%} が必要です）_ diff --git a/@l10n/ja/docs/references/protocol/transactions/types/xchainaddaccountcreateattestation.md b/@l10n/ja/docs/references/protocol/transactions/types/xchainaddaccountcreateattestation.md index c864aec9c9f..7aad46d10e4 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/xchainaddaccountcreateattestation.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/xchainaddaccountcreateattestation.md @@ -8,7 +8,7 @@ labels: status: not_enabled --- # XChainAddAccountCreateAttestation -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/impl/TxFormats.cpp#L447-L464 "ソース") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/XChainBridge.h#L189-L208 "ソース") _（[XChainBridge Amendment][] {% not-enabled /%} が必要です）_ diff --git a/@l10n/ja/docs/references/protocol/transactions/types/xchainaddclaimattestation.md b/@l10n/ja/docs/references/protocol/transactions/types/xchainaddclaimattestation.md index f624a6438f5..782e643c190 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/xchainaddclaimattestation.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/xchainaddclaimattestation.md @@ -8,7 +8,7 @@ labels: status: not_enabled --- # XChainAddClaimAttestation -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/impl/TxFormats.cpp#L429-L445 "ソース") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/XChainBridge.h#L169-L187 "ソース") _（[XChainBridge Amendment][] {% not-enabled /%} が必要です）_ diff --git a/@l10n/ja/docs/references/protocol/transactions/types/xchainclaim.md b/@l10n/ja/docs/references/protocol/transactions/types/xchainclaim.md index 13aec807115..2f88eadc10c 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/xchainclaim.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/xchainclaim.md @@ -8,7 +8,7 @@ labels: status: not_enabled --- # XChainClaim -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/impl/TxFormats.cpp#L418-L427 "ソース") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/XChainBridge.h#L84-L102 "ソース") _（[XChainBridge Amendment][] {% not-enabled /%} が必要です）_ diff --git a/@l10n/ja/docs/references/protocol/transactions/types/xchaincommit.md b/@l10n/ja/docs/references/protocol/transactions/types/xchaincommit.md index 0bb104c82aa..eb0d1d8a2d3 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/xchaincommit.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/xchaincommit.md @@ -8,7 +8,7 @@ labels: status: not_enabled --- # XChainCommit -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/impl/TxFormats.cpp#L408-L416 "ソース") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/XChainBridge.h#L109-L129 "ソース") _（[XChainBridge Amendment][] {% not-enabled /%} が必要です）_ diff --git a/@l10n/ja/docs/references/protocol/transactions/types/xchaincreatebridge.md b/@l10n/ja/docs/references/protocol/transactions/types/xchaincreatebridge.md index e21a9d31404..8b8877bb587 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/xchaincreatebridge.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/xchaincreatebridge.md @@ -8,7 +8,7 @@ labels: status: not_enabled --- # XChainCreateBridge -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/impl/TxFormats.cpp#L381-L388 "ソース") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/XChainBridge.h#L33-L50 "ソース") _（[XChainBridge Amendment][] {% not-enabled /%} が必要です）_ diff --git a/@l10n/ja/docs/references/protocol/transactions/types/xchaincreateclaimid.md b/@l10n/ja/docs/references/protocol/transactions/types/xchaincreateclaimid.md index 96c0eb9e121..2410209a245 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/xchaincreateclaimid.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/xchaincreateclaimid.md @@ -8,7 +8,7 @@ labels: status: not_enabled --- # XChainCreateClaimID -[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/impl/TxFormats.cpp#L399-L406 "ソース") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/XChainBridge.h#L141-L158 "ソース") _（[XChainBridge Amendment][] {% not-enabled /%} が必要です）_ diff --git a/@l10n/ja/docs/references/protocol/transactions/types/xchainmodifybridge.md b/@l10n/ja/docs/references/protocol/transactions/types/xchainmodifybridge.md index 4507ba997de..dbbcf97b208 100644 --- a/@l10n/ja/docs/references/protocol/transactions/types/xchainmodifybridge.md +++ b/@l10n/ja/docs/references/protocol/transactions/types/xchainmodifybridge.md @@ -8,7 +8,7 @@ labels: status: not_enabled --- # XChainModifyBridge -[[ソース]](https://github.com/XRPLF/rippled/blob/develop/src/ripple/protocol/impl/TxFormats.cpp#L390-L397 "ソース") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/XChainBridge.h#L71 "ソース") _（[XChainBridge Amendment][] {% not-enabled /%} が必要です）_ diff --git a/@l10n/ja/docs/tutorials/http-websocket-apis/get-started.md b/@l10n/ja/docs/tutorials/http-websocket-apis/get-started.md index 3fca397c589..504b3e76ba9 100644 --- a/@l10n/ja/docs/tutorials/http-websocket-apis/get-started.md +++ b/@l10n/ja/docs/tutorials/http-websocket-apis/get-started.md @@ -30,7 +30,7 @@ JSON-RPCとWebSocketはどちらもHTTPベースのプロトコルであり、 `rippled`サーバの[管理メソッド](../../references/http-websocket-apis/admin-api-methods/index.md)を使用するには、次のように行います。この場合、サーバのバインド用として設定したIPアドレスとポートを使用する必要があります（例えば`127.0.0.1:54321`）。また、管理機能にアクセスするには、構成ファイルで**管理用としてマークされているポートおよびIPアドレス**から接続しなければなりません。 -[構成ファイルの例](https://github.com/XRPLF/rippled/blob/8429dd67e60ba360da591bfa905b58a35638fda1/cfg/rippled-example.cfg#L1050-L1073)では、ローカルループバックネットワーク上（127.0.0.1）のポート5005でJSON-RPC（HTTP）、ポート6006でWebSocket（WS）の接続をリッスンし、接続されるすべてのクライアントを管理者として扱っています。 +[構成ファイルの例](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/cfg/rippled-example.cfg#L1414-L1448)では、ローカルループバックネットワーク上（127.0.0.1）のポート5005でJSON-RPC（HTTP）、ポート6006でWebSocket（WS）の接続をリッスンし、接続されるすべてのクライアントを管理者として扱っています。 ## WebSocket API diff --git a/@l10n/ja/docs/tutorials/javascript/get-started.md b/@l10n/ja/docs/tutorials/javascript/get-started.md index 410cfbecf13..6276e9be156 100644 --- a/@l10n/ja/docs/tutorials/javascript/get-started.md +++ b/@l10n/ja/docs/tutorials/javascript/get-started.md @@ -104,7 +104,7 @@ const xrpl = require("xrpl") await client.connect() ``` - デフォルト値の詳細については、[コアサーバ設定ファイル](https://github.com/XRPLF/rippled/blob/c0a0b79d2d483b318ce1d82e526bd53df83a4a2c/cfg/rippled-example.cfg#L1562)の例をご覧ください。 + デフォルト値の詳細については、[コアサーバ設定ファイル](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/cfg/rippled-example.cfg#L1423)の例をご覧ください。 * 利用可能な[公開サーバ][]を利用する: diff --git a/@l10n/ja/resources/contribute-code/create-custom-transactors.md b/@l10n/ja/resources/contribute-code/create-custom-transactors.md index ac3a558990d..4ed2425d89e 100644 --- a/@l10n/ja/resources/contribute-code/create-custom-transactors.md +++ b/@l10n/ja/resources/contribute-code/create-custom-transactors.md @@ -21,8 +21,8 @@ _トランザクタ_ はトランザクションを処理し、XRP Ledgerを変 このチュートリアルでは、既存の`CreateCheck`トランザクションを例として使用します。ソースファイルはここで確認できます。 -- [ヘッダファイル](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/CreateCheck.h) -- [CPPファイル](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/CreateCheck.cpp) +- [ヘッダファイル](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/CreateCheck.h) +- [CPPファイル](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/CreateCheck.cpp) ## ヘッダファイル @@ -78,8 +78,8 @@ public: {% admonition type="info" name="注記" %}`~`記号は optional型を返します。{% /admonition %} - レジャーとトランザクションのスキーマはこちらから確認できます。 - - [`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) + - [`LedgerFormats.cpp`](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/libxrpl/protocol/LedgerFormats.cpp) + - [`TxFormats.cpp`](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/libxrpl/protocol/TxFormats.cpp) -` rippled` はトランザクションの結果を結果コードで表します。[トランザクションの結果](../../docs/references/protocol/transactions/transaction-results/index.md)をご覧ください。 @@ -344,7 +344,7 @@ EscrowFinish::calculateBaseFee(ReadView const& view, STTx const& tx) ### `makeTxConsequences` -`rippled`は[`TxConsequences`](https://github.com/XRPLF/rippled/blob/master/src/ripple/app/tx/applySteps.h#L41-L44)クラスを使用して、トランザクション適用時のアカウントへの結果を記述します。このクラスは手数料、使用可能な最大XRP、トランザクションによって消費されたシーケンス番号の数を追跡します。結果には次の3つのタイプがあります。 +`rippled`は[`TxConsequences`](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/applySteps.h#L54-L57)クラスを使用して、トランザクション適用時のアカウントへの結果を記述します。このクラスは手数料、使用可能な最大XRP、トランザクションによって消費されたシーケンス番号の数を追跡します。結果には次の3つのタイプがあります。 - **ノーマル:**トランザクションは署名に影響を与えず、XRP手数料を消費するのみです。手数料を超えてXRPを消費するトランザクションは正常とはみなされません。 - **ブロッカー:**トランザクションの署名に影響を与え、有効なトランザクションがその後ろにキューイングされるのを防ぎます。 diff --git a/@l10n/ja/resources/contribute-code/index.md b/@l10n/ja/resources/contribute-code/index.md index 76b3fb66757..b63c81962ee 100644 --- a/@l10n/ja/resources/contribute-code/index.md +++ b/@l10n/ja/resources/contribute-code/index.md @@ -17,7 +17,7 @@ XRP Ledgerを動かすソフトウェアはオープンソースです。コミ | XRP Ledger ソースコード | | |:-----------------------|:----------------------------------------------------| | リポジトリ | | -| ライセンス | [Multiple; ISC (permissive)](https://github.com/XRPLF/rippled/blob/develop/LICENSE.md) | +| ライセンス | [Multiple; ISC (permissive)](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/LICENSE.md) | | プログラム言語 | C++ | 何から始めたらいいか分からないという方のために、Dev Null Productionsは、XRP Ledgerサーバ(`rippled`)のコア実装の仕組みや機能を説明した、詳細かつ充実した[**ソースコード・ガイド**](https://xrpintel.com/source)を提供しています。 diff --git a/@l10n/ja/resources/known-amendments.md b/@l10n/ja/resources/known-amendments.md index 61f52f39f29..1387199db54 100644 --- a/@l10n/ja/resources/known-amendments.md +++ b/@l10n/ja/resources/known-amendments.md @@ -5,7 +5,7 @@ labels: - ブロックチェーン --- # 既知のAmendment -[[ソース]](https://github.com/xrplf/rippled/blob/master/src/ripple/protocol/impl/Feature.cpp "Source") +[[ソース]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/libxrpl/protocol/Feature.cpp "Source") ## メインネットの既知のAmendment @@ -272,7 +272,7 @@ XRP Ledgerを使用して資格情報およびコンプライアンス要件を `deposit_authorized` APIメソッドを修正し、Credentialに基づく認証をチェックするようにします。また、`ledger_entry`メソッドを修正し、Credentialエントリの検索を許可します。 -詳細については、[XLS-70: Credentials specification](https://github.com/XRPLF/XRPL-Standards/tree/master/XLS-0070d-credentials)をご覧ください。 +詳細については、[XLS-70: Credentials specification](https://github.com/XRPLF/XRPL-Standards/tree/master/XLS-0070-credentials)をご覧ください。 ### CryptoConditions diff --git a/_code-samples/auction-slot/js/amm-formulas.js b/_code-samples/auction-slot/js/amm-formulas.js index 82c89923d0d..1701f9cafc2 100644 --- a/_code-samples/auction-slot/js/amm-formulas.js +++ b/_code-samples/auction-slot/js/amm-formulas.js @@ -35,7 +35,7 @@ function feeDecimal(tFee) { /* Implement the AMM SwapOut formula, as defined in XLS-30 section 2.4 AMM * Swap, formula 10. The asset weights WA/WB are currently always 1/1 so * they're canceled out. - * C++ source: https://github.com/XRPLF/rippled/blob/2d1854f354ff8bb2b5671fd51252c5acd837c433/src/ripple/app/misc/AMMHelpers.h#L253-L258 + * C++ source: https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/misc/AMMHelpers.h#L591-L596 * @param asset_out_bn BigNumber - The target amount to receive from the AMM. * @param pool_in_bn BigNumber - The amount of the input asset in the AMM's * pool before the swap. @@ -69,7 +69,7 @@ function solveQuadraticEq(a,b,c) { /* Implement the AMM single-asset deposit formula to calculate how much to * put in so that you receive a specific number of LP Tokens back. - * C++ source: https://github.com/XRPLF/rippled/blob/2d1854f354ff8bb2b5671fd51252c5acd837c433/src/ripple/app/misc/impl/AMMHelpers.cpp#L55-L83 + * C++ source: https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/misc/detail/AMMHelpers.cpp#L68-L105 * @param pool_in string - Quantity of input asset the pool already has * @param lpt_balance string - Quantity of LP Tokens already issued by the AMM * @param desired_lpt string - Quantity of new LP Tokens you want to receive diff --git a/_code-samples/build-a-browser-wallet/js/src/transaction-history/transaction-history.js b/_code-samples/build-a-browser-wallet/js/src/transaction-history/transaction-history.js index c1c8d933dd4..b4cb16fe1ee 100644 --- a/_code-samples/build-a-browser-wallet/js/src/transaction-history/transaction-history.js +++ b/_code-samples/build-a-browser-wallet/js/src/transaction-history/transaction-history.js @@ -51,7 +51,7 @@ function getTokenName(currencyCode) { return text_code; } // Other hex format, return as-is. - // For parsing other rare formats, see https://github.com/XRPLF/xrpl-dev-portal/blob/master/content/_code-samples/normalize-currency-codes/js/normalize-currency-code.js + // For parsing other rare formats, see https://github.com/XRPLF/xrpl-dev-portal/blob/master/_code-samples/normalize-currency-codes/js/normalize-currency-code.js return currencyCode; } return ""; diff --git a/_code-samples/quickstart/js/ripplex13b-amm-formulas.js b/_code-samples/quickstart/js/ripplex13b-amm-formulas.js index 282dc750f70..6f2d9849af5 100644 --- a/_code-samples/quickstart/js/ripplex13b-amm-formulas.js +++ b/_code-samples/quickstart/js/ripplex13b-amm-formulas.js @@ -33,7 +33,7 @@ function feeDecimal(tFee) { /* Implement the AMM SwapOut formula, as defined in XLS-30 section 2.4 AMM * Swap, formula 10. The asset weights WA/WB are currently always 1/1 so * they're canceled out. - * C++ source: https://github.com/XRPLF/rippled/blob/2d1854f354ff8bb2b5671fd51252c5acd837c433/src/ripple/app/misc/AMMHelpers.h#L253-L258 + * C++ source: https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/misc/AMMHelpers.h#L591-L596 * @param asset_out_bn BigNumber - The target amount to receive from the AMM. * @param pool_in_bn BigNumber - The amount of the input asset in the AMM's * pool before the swap. @@ -67,7 +67,7 @@ function solveQuadraticEq(a,b,c) { /* Implement the AMM single-asset deposit formula to calculate how much to * put in so that you receive a specific number of LP Tokens back. - * C++ source: https://github.com/XRPLF/rippled/blob/2d1854f354ff8bb2b5671fd51252c5acd837c433/src/ripple/app/misc/impl/AMMHelpers.cpp#L55-L83 + * C++ source: https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/misc/detail/AMMHelpers.cpp#L68-L105 * @param pool_in string - Quantity of input asset the pool already has * @param lpt_balance string - Quantity of LP Tokens already issued by the AMM * @param desired_lpt string - Quantity of new LP Tokens you want to receive diff --git a/about/faq.md b/about/faq.md index 13912603d5b..66b3d556d21 100644 --- a/about/faq.md +++ b/about/faq.md @@ -126,7 +126,7 @@ Ripple is committed to monitoring and reporting any AML flags across the XRP Led #### What is the process for reviewing third-party code contributions? -The code contribution process starts with a developer opening a [pull request](https://docs.github.com/en/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests) to a source code repository such as the [`rippled` repository](https://github.com/xrplf/rippled/), which contains Ripple's reference implementation of the core XRP Ledger server and protocol. +The code contribution process starts with a developer opening a [pull request](https://docs.github.com/en/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests) to a source code repository such as the [`rippled` repository](https://github.com/XRPLF/rippled/), which contains Ripple's reference implementation of the core XRP Ledger server and protocol. This pull request triggers automated unit and integration tests, as well as code reviews by several developers who, typically, have significant expertise in the area of code that the pull request affects. @@ -137,7 +137,7 @@ Once the pull request passes automated tests and receives approvals from reviewe No, Ripple does not own or control the XRP Ledger or XRP Ledger network. -Ripple contributes to a reference implementation of the core XRP Ledger server ([`rippled`](https://github.com/xrplf/rippled)) and employs a team of engineers who contribute to the open-source codebase. Ripple periodically publishes pre-compiled binary packages of the software for convenience. Anyone can [download and compile the software from source](../docs/infrastructure/installation/index.md). +Ripple contributes to a reference implementation of the core XRP Ledger server ([`rippled`](https://github.com/XRPLF/rippled)) and employs a team of engineers who contribute to the open-source codebase. Ripple periodically publishes pre-compiled binary packages of the software for convenience. Anyone can [download and compile the software from source](../docs/infrastructure/installation/index.md). Several entities publish recommended validator lists (UNLs). As of July 2023, Ripple runs only 1 of the 35 validators in the default UNL. diff --git a/blog/2025/defi-use-cases-exploring-the-potential.md b/blog/2025/defi-use-cases-exploring-the-potential.md index 264ee32fae8..833ef7ce98b 100644 --- a/blog/2025/defi-use-cases-exploring-the-potential.md +++ b/blog/2025/defi-use-cases-exploring-the-potential.md @@ -39,7 +39,7 @@ The Lending Protocol is represented on the ledger by a LoanBroker entry created, Yield farming, or liquidity farming, is a DeFi strategy where cryptocurrency holders earn passive income by providing liquidity to DeFi protocols. Users lock up their assets in liquidity pools, forming trading pairs, and receive liquidity provider (LP) tokens in return. These LP tokens can be staked or deposited into other protocols to earn additional rewards such as transaction fees and governance tokens. Yield farming carries risks, including impermanent loss and smart contract vulnerabilities, requiring participants to conduct thorough research before engaging in this potentially lucrative but risky activity. -Established protocols like Yearn.Finance, Balancer, and Curve optimize yield farming strategies for users seeking returns. More is already on the way for the XRPL too! The lending portion of the earlier mentioned XRPL-native [Lending Protocol spec](https://github.com/XRPLF/XRPL-Standards/discussions/190) is built on top of another specification, which brings a [single asset vault](https://github.com/XRPLF/XRPL-Standards/tree/master/XLS-0065d-single-asset-vault) to the XRP Ledger. This will unlock further use cases beyond lending in the future - such as yield farming, escrow, and more! +Established protocols like Yearn.Finance, Balancer, and Curve optimize yield farming strategies for users seeking returns. More is already on the way for the XRPL too! The lending portion of the earlier mentioned XRPL-native [Lending Protocol spec](https://github.com/XRPLF/XRPL-Standards/discussions/190) is built on top of another specification, which brings a [single asset vault](https://github.com/XRPLF/XRPL-Standards/tree/master/XLS-0065-single-asset-vault) to the XRP Ledger. This will unlock further use cases beyond lending in the future - such as yield farming, escrow, and more! ### Decentralized Exchanges (DEXs) diff --git a/docs/_snippets/clawback-disclaimer.md b/docs/_snippets/clawback-disclaimer.md index 0037aac4295..12cd1ec1b0b 100644 --- a/docs/_snippets/clawback-disclaimer.md +++ b/docs/_snippets/clawback-disclaimer.md @@ -1 +1 @@ -_Requires the [Clawback amendment](https://github.com/XRPLF/XRPL-Standards/tree/master/XLS-0039d-clawback)._ +_Requires the [Clawback amendment](https://github.com/XRPLF/XRPL-Standards/tree/master/XLS-0039-clawback)._ diff --git a/docs/_snippets/post-rippled-install.md b/docs/_snippets/post-rippled-install.md index 3b8b087558a..5d839df0879 100644 --- a/docs/_snippets/post-rippled-install.md +++ b/docs/_snippets/post-rippled-install.md @@ -20,7 +20,7 @@ Having trouble getting your server started? See [rippled Server Won't Start](../ {% partial file="/docs/_snippets/conf-file-location.md" /%} -See [the `rippled` GitHub repository](https://github.com/XRPLF/rippled/blob/master/cfg/rippled-example.cfg) for a description of all configuration options. +See [the `rippled` GitHub repository](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/cfg/rippled-example.cfg) for a description of all configuration options. You must restart `rippled` for any configuration changes to take effect. diff --git a/docs/concepts/accounts/addresses.md b/docs/concepts/accounts/addresses.md index a3c7a2f841f..839b333be7c 100644 --- a/docs/concepts/accounts/addresses.md +++ b/docs/concepts/accounts/addresses.md @@ -24,7 +24,7 @@ Some addresses have special meaning, or historical uses, in the XRP Ledger. In m |-------------------------------|------|---------|-------------| | `rrrrrrrrrrrrrrrrrrrrrhoLvTp` | ACCOUNT\_ZERO | An address that is the XRP Ledger's [base58][] encoding of the value `0`. In peer-to-peer communications, `rippled` uses this address as the issuer for XRP. | Yes | | `rrrrrrrrrrrrrrrrrrrrBZbvji` | ACCOUNT\_ONE | An address that is the XRP Ledger's [base58][] encoding of the value `1`. In the ledger, [RippleState entries](../../references/protocol/ledger-data/ledger-entry-types/ripplestate.md) use this address as a placeholder for the issuer of a trust line balance. | Yes | -| `rHb9CJAWyB4rj91VRWn96DkukG4bwdtyTh` | The genesis account | When `rippled` starts a new genesis ledger from scratch (for example, in stand-alone mode), this account holds all the XRP. This address is generated from the seed value `masterpassphrase` which is [hard-coded](https://github.com/XRPLF/rippled/blob/94ed5b3a53077d815ad0dd65d490c8d37a147361/src/ripple/app/ledger/Ledger.cpp#L184). | No | +| `rHb9CJAWyB4rj91VRWn96DkukG4bwdtyTh` | The genesis account | When `rippled` starts a new genesis ledger from scratch (for example, in stand-alone mode), this account holds all the XRP. This address is generated from the seed value `masterpassphrase` which is [hard-coded](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/ledger/Ledger.cpp#L184). | No | | `rrrrrrrrrrrrrrrrrNAMEtxvNvQ` | Ripple Name reservation black-hole | In the past, Ripple asked users to send XRP to this account to reserve Ripple Names.| Yes | | `rrrrrrrrrrrrrrrrrrrn5RM1rHd` | NaN Address | Previous versions of [ripple-lib](https://github.com/XRPLF/xrpl.js) generated this address when encoding the value [NaN](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/NaN) using the XRP Ledger's [base58][] string encoding format. | Yes | @@ -33,7 +33,7 @@ Some addresses have special meaning, or historical uses, in the XRP Ledger. In m {% admonition type="success" name="Tip" %}These technical details are only relevant for people building low-level library software for XRP Ledger compatibility!{% /admonition %} -[[Source]](https://github.com/XRPLF/rippled/blob/35fa20a110e3d43ffc1e9e664fc9017b6f2747ae/src/ripple/protocol/impl/AccountID.cpp#L109-L140 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/libxrpl/protocol/AccountID.cpp#L134-L165 "Source") XRP Ledger addresses are encoded using [base58][] with the _dictionary_ `rpshnaf39wBUDNEGHJKLM4PQRST7VWXYZ2bcdeCg65jkm8oFqi1tuvAxyz`. Since the XRP Ledger encodes several types of keys with base58, it prefixes the encoded data with a one-byte "type prefix" (also called a "version prefix") to distinguish them. The type prefix causes addresses to usually start with different letters in base58 format. diff --git a/docs/concepts/accounts/cryptographic-keys.md b/docs/concepts/accounts/cryptographic-keys.md index dc34d80e18c..403191faa35 100644 --- a/docs/concepts/accounts/cryptographic-keys.md +++ b/docs/concepts/accounts/cryptographic-keys.md @@ -154,14 +154,14 @@ The process of deriving a key pair depends on the signing algorithm. In all case The key derivation processes described here are implemented in multiple places and programming languages: - In C++ in the `rippled` code base: - - [Seed definition](https://github.com/XRPLF/rippled/blob/develop/src/ripple/protocol/Seed.h) - - [General & Ed25519 key derivation](https://github.com/XRPLF/rippled/blob/develop/src/ripple/protocol/impl/SecretKey.cpp) - - [secp256k1 key derivation](https://github.com/XRPLF/rippled/blob/develop/src/ripple/protocol/impl/SecretKey.cpp) + - [Seed definition](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/Seed.h) + - [General & Ed25519 key derivation](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/libxrpl/protocol/SecretKey.cpp) + - [secp256k1 key derivation](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/libxrpl/protocol/SecretKey.cpp) - In Python 3 in {% repo-link path="_code-samples/key-derivation/py/key_derivation.py" %}this repository's code samples section{% /repo-link %}. - In JavaScript in the [`ripple-keypairs`](https://github.com/XRPLF/xrpl.js/tree/main/packages/ripple-keypairs) package. ### Ed25519 Key Derivation -[[Source]](https://github.com/XRPLF/rippled/blob/fc7ecd672a3b9748bfea52ce65996e324553c05f/src/ripple/protocol/impl/SecretKey.cpp#L203 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/libxrpl/protocol/SecretKey.cpp#L313 "Source") [{% inline-svg file="/docs/img/key-derivation-ed25519.svg" /%}](/docs/img/key-derivation-ed25519.svg "Passphrase → Seed → Secret Key → Prefix + Public Key") @@ -182,7 +182,7 @@ The key derivation processes described here are implemented in multiple places a Validator ephemeral keys cannot be Ed25519. ### secp256k1 Key Derivation -[[Source]](https://github.com/XRPLF/rippled/blob/develop/src/ripple/protocol/impl/SecretKey.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/libxrpl/protocol/SecretKey.cpp "Source") [{% inline-svg file="/docs/img/key-derivation-secp256k1.svg" /%}](/docs/img/key-derivation-secp256k1.svg "Passphrase → Seed → Root Key Pair → Intermediate Key Pair → Master Key Pair") diff --git a/docs/concepts/consensus-protocol/consensus-structure.md b/docs/concepts/consensus-protocol/consensus-structure.md index 790f235b918..bff9d92d168 100644 --- a/docs/concepts/consensus-protocol/consensus-structure.md +++ b/docs/concepts/consensus-protocol/consensus-structure.md @@ -107,7 +107,7 @@ When the consensus process completes, each server independently computes a new l 2. Place the agreed-upon transaction set in _canonical order_ so that every server processes them the same way. - [Canonical order](https://github.com/XRPLF/rippled/blob/8429dd67e60ba360da591bfa905b58a35638fda1/src/ripple/app/misc/CanonicalTXSet.cpp#L25-L36) is not the order the transactions were received, because servers may receive the same transactions in different order. To prevent participants from competing over transaction ordering, canonical order is hard to manipulate. + [Canonical order](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/misc/CanonicalTXSet.cpp#L24-L40) is not the order the transactions were received, because servers may receive the same transactions in different order. To prevent participants from competing over transaction ordering, canonical order is hard to manipulate. 3. Process each transaction according to its instructions, in order. Update the ledger's state data accordingly. diff --git a/docs/concepts/consensus-protocol/invariant-checking.md b/docs/concepts/consensus-protocol/invariant-checking.md index 9dff55c3aae..154b25ceefb 100644 --- a/docs/concepts/consensus-protocol/invariant-checking.md +++ b/docs/concepts/consensus-protocol/invariant-checking.md @@ -38,39 +38,39 @@ To include the transaction in the ledger with a `tec`-class code, some minimal p The XRP Ledger checks all the following invariants on each transaction: -[[Source]](https://github.com/XRPLF/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h#L92 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/InvariantCheck.h#L92 "Source") - [Transaction Fee Check](#transaction-fee-check) -[[Source]](https://github.com/XRPLF/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h#L118 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/InvariantCheck.h#L118 "Source") - [XRP Not Created](#xrp-not-created) -[[Source]](https://github.com/XRPLF/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h#L146 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/InvariantCheck.h#L146 "Source") - [Account Roots Not Deleted](#account-roots-not-deleted) -[[Source]](https://github.com/XRPLF/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h#L173 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/InvariantCheck.h#L203 "Source") - [XRP Balance Checks](#xrp-balance-checks) -[[Source]](https://github.com/XRPLF/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h#L197 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/InvariantCheck.h#L227 "Source") - [Ledger Entry Types Match](#ledger-entry-types-match) -[[Source]](https://github.com/XRPLF/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h#L224 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/InvariantCheck.h#L254 "Source") - [No XRP Trust Lines](#no-xrp-trust-lines) -[[Source]](https://github.com/XRPLF/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h#L251 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/InvariantCheck.h#L389 "Source") - [No Bad Offers](#no-bad-offers) -[[Source]](https://github.com/XRPLF/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h#L275 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/InvariantCheck.h#L413 "Source") - [No Zero Escrow](#no-zero-escrow) -[[Source]](https://github.com/XRPLF/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h#L300 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/InvariantCheck.h#L438 "Source") - [Valid New Account Root](#valid-new-account-root) @@ -158,11 +158,11 @@ The XRP Ledger checks all the following invariants on each transaction: - [Protecting the Ledger: Invariant Checking](https://xrpl.org/blog/2017/invariant-checking.html) - **Repository:** - - [Invariant Check.h](https://github.com/XRPLF/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h) - - [Invariant Check.cpp](https://github.com/XRPLF/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.cpp) - - [System Parameters](https://github.com/XRPLF/rippled/blob/develop/src/ripple/protocol/SystemParameters.h#L43) - - [XRP Amount](https://github.com/XRPLF/rippled/blob/develop/src/ripple/basics/XRPAmount.h#L244) - - [Ledger Formats](https://github.com/XRPLF/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/protocol/LedgerFormats.h#L36-L94) + - [Invariant Check.h](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/InvariantCheck.h) + - [Invariant Check.cpp](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/InvariantCheck.cpp) + - [System Parameters](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/SystemParameters.h#L44) + - [XRP Amount](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/XRPAmount.h#L252) + - [Ledger Formats](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/LedgerFormats.h#L53-L117) - **Other:** diff --git a/docs/concepts/networks-and-servers/peer-protocol.md b/docs/concepts/networks-and-servers/peer-protocol.md index ce488187c3e..661ffe189a3 100644 --- a/docs/concepts/networks-and-servers/peer-protocol.md +++ b/docs/concepts/networks-and-servers/peer-protocol.md @@ -18,11 +18,11 @@ The peer protocol is the main mode of communication between servers in the XRP L - Requesting ledger data from historical ledgers, or providing that data. - Proposing a set of transactions for consensus, or sharing the calculated outcome of applying a consensus transaction set. -To set up a peer-to-peer connection, one server connects to another using HTTPS and requests an [HTTP upgrade](https://tools.ietf.org/html/rfc7230#section-6.7) to switch to the `XRPL/2.0` protocol (formerly `RTXP/1.2`). (For more information, see the [Overlay Network](https://github.com/XRPLF/rippled/blob/96bbabbd2ece106779bb544aa0e4ce174e99fdf6/src/ripple/overlay/README.md#handshake) article in the [`rippled` repository](https://github.com/ripple/rippled).) +To set up a peer-to-peer connection, one server connects to another using HTTPS and requests an [HTTP upgrade](https://tools.ietf.org/html/rfc7230#section-6.7) to switch to the `XRPL/2.0` protocol (formerly `RTXP/1.2`). (For more information, see the [Overlay Network](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/overlay/README.md#handshake) article in the [`rippled` repository](https://github.com/ripple/rippled).) ## Peer Discovery -The XRP Ledger uses a "gossip" protocol to help find servers find others to connect to in the XRP Ledger network. Whenever a server starts up, it reconnects to any other peers it previously connected to. As a fallback, it uses the [hardcoded public hubs](https://github.com/XRPLF/rippled/blob/fa57859477441b60914e6239382c6fba286a0c26/src/ripple/overlay/impl/OverlayImpl.cpp#L518-L525). After a server successfully connects to a peer, it asks that peer for the contact information (generally, IP address and port) of other XRP Ledger servers that may also be seeking peers. The server can then connect to those servers, and ask them for the contact information of yet more XRP Ledger servers to peer with. Through this process, the server makes enough peer connections that it can remain reliably connected to the rest of the network even if it loses a connection to any single peer. +The XRP Ledger uses a "gossip" protocol to help find servers find others to connect to in the XRP Ledger network. Whenever a server starts up, it reconnects to any other peers it previously connected to. As a fallback, it uses the [hardcoded public hubs](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/overlay/detail/OverlayImpl.h#L494-L509). After a server successfully connects to a peer, it asks that peer for the contact information (generally, IP address and port) of other XRP Ledger servers that may also be seeking peers. The server can then connect to those servers, and ask them for the contact information of yet more XRP Ledger servers to peer with. Through this process, the server makes enough peer connections that it can remain reliably connected to the rest of the network even if it loses a connection to any single peer. Typically, a server needs to connect to a public hub only once, for a short amount of time, to find other peers. After doing so, the server may or may not remain connected to the hub, depending on how stable its network connection is, how busy the hub is, and how many other high-quality peers the server finds. The server saves the addresses of these other peers so it can try reconnecting directly to those peers later, after a network outage or a restart. @@ -37,7 +37,7 @@ To participate in the XRP Ledger, `rippled` servers connect to arbitrary peers u Ideally, the server should be able to send _and_ receive connections on the peer port. You should [forward the port used for the peer protocol through your firewall](../../infrastructure/configuration/peering/forward-ports-for-peering.md) to the `rippled` server. -IANA [has assigned port **2459**](https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml?search=2459) for the XRP Ledger peer protocol, but for compatibility with legacy systems, the [default `rippled` config file](https://github.com/XRPLF/rippled/blob/master/cfg/rippled-example.cfg) listens for incoming peer protocol connections on **port 51235** on all network interfaces. If you run a server, you can configure which port(s) your server listens on using the `rippled.cfg` file. +IANA [has assigned port **2459**](https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml?search=2459) for the XRP Ledger peer protocol, but for compatibility with legacy systems, the [default `rippled` config file](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/cfg/rippled-example.cfg) listens for incoming peer protocol connections on **port 51235** on all network interfaces. If you run a server, you can configure which port(s) your server listens on using the `rippled.cfg` file. Example: diff --git a/docs/concepts/tokens/decentralized-exchange/offers.md b/docs/concepts/tokens/decentralized-exchange/offers.md index 04b6af8f196..f031070d316 100644 --- a/docs/concepts/tokens/decentralized-exchange/offers.md +++ b/docs/concepts/tokens/decentralized-exchange/offers.md @@ -85,7 +85,7 @@ Trust line limits protect you from receiving more of a token as payment than you Existing Offers are grouped by exchange rate, which is measured as the ratio between `TakerGets` and `TakerPays`. Offers with a higher exchange rate are taken preferentially. (That is, the person accepting the offer receives as much as possible for the amount of currency they pay out.) Offers with the same exchange rate are taken on the basis of which offer was placed first. -When Offers execute in the same ledger block, the order in which they execute is determined by the [canonical order](https://github.com/XRPLF/rippled/blob/release/src/ripple/app/misc/CanonicalTXSet.cpp "Source code: Transaction ordering") in which the transactions were [applied to the ledger](https://github.com/XRPLF/rippled/blob/5425a90f160711e46b2c1f1c93d68e5941e4bfb6/src/ripple/app/consensus/LedgerConsensus.cpp#L1435-L1538 "Source code: Applying transactions"). This behavior is designed to be deterministic, efficient, and hard to game. +When Offers execute in the same ledger block, the order in which they execute is determined by the [canonical order](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/misc/CanonicalTXSet.cpp "Source code: Transaction ordering") in which the transactions were [applied to the ledger](https://github.com/XRPLF/rippled/blob/5425a90f160711e46b2c1f1c93d68e5941e4bfb6/src/ripple/app/consensus/LedgerConsensus.cpp#L1435-L1538 "Source code: Applying transactions"). This behavior is designed to be deterministic, efficient, and hard to game. ## Offer Expiration diff --git a/docs/concepts/tokens/fungible-tokens/index.md b/docs/concepts/tokens/fungible-tokens/index.md index f5f2e42bb3c..6175613723a 100644 --- a/docs/concepts/tokens/fungible-tokens/index.md +++ b/docs/concepts/tokens/fungible-tokens/index.md @@ -72,7 +72,7 @@ If your balance is negative (you are the issuer) or the other side's settings ar Since the **Authorized** setting cannot be turned off after it has been turned on, it does not count toward the trust line's default state. ### Free Trust Lines -[[Source]](https://github.com/XRPLF/rippled/blob/72377e7bf25c4eaee5174186d2db3c6b4210946f/src/ripple/app/tx/impl/SetTrust.cpp#L148-L168) +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/SetTrust.cpp#L387-L407) Since trust lines are a powerful feature of the XRP Ledger, there is a special feature to make an account's first two trust lines "free". diff --git a/docs/concepts/transactions/secure-signing.md b/docs/concepts/transactions/secure-signing.md index 4b258a48938..4bee362af85 100644 --- a/docs/concepts/transactions/secure-signing.md +++ b/docs/concepts/transactions/secure-signing.md @@ -45,7 +45,7 @@ In this configuration, you run `rippled` on the machine that generates the trans 2. When you need to sign transactions, connect to your server on `localhost` or `127.0.0.1`. Use the [sign method][] (for single signatures) or [sign_for method][] (for multi-signatures). - The [example config file](https://github.com/XRPLF/rippled/blob/8429dd67e60ba360da591bfa905b58a35638fda1/cfg/rippled-example.cfg#L1050-L1073) listens for connections on the local loopback network (127.0.0.1), with JSON-RPC (HTTP) on port 5005 and WebSocket (WS) on port 6006, and treats all connected clients as admin. + The [example config file](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/cfg/rippled-example.cfg#L1414-L1448) listens for connections on the local loopback network (127.0.0.1), with JSON-RPC (HTTP) on port 5005 and WebSocket (WS) on port 6006, and treats all connected clients as admin. {% admonition type="warning" name="Caution" %}Using the [commandline API](../../references/http-websocket-apis/api-conventions/request-formatting.md#commandline-format) for signatures is less secure than [using the Websocket or JSON-RPC APIs](../../tutorials/http-websocket-apis/build-apps/get-started.md) through non-commandline clients. When using the commandline syntax, your secret key may be visible to other users in the system's process listing, and your shell history may save the key in plain text.{% /admonition %} diff --git a/docs/concepts/transactions/transaction-cost.md b/docs/concepts/transactions/transaction-cost.md index b5475a1fd34..26dafce8741 100644 --- a/docs/concepts/transactions/transaction-cost.md +++ b/docs/concepts/transactions/transaction-cost.md @@ -64,7 +64,7 @@ For each new ledger version, the server picks a soft limit on the number of tran The open ledger cost requirement is [proportional to the normal cost of the transaction](#fee-levels), not the absolute transaction cost. Transaction types that have a higher-than-normal requirement, such as [multi-signed transactions](../accounts/multi-signing.md) must pay more to meet the open ledger cost than transactions which have minimum transaction cost requirements. -See also: [Fee Escalation explanation in `rippled` repository](https://github.com/XRPLF/rippled/blob/release/src/ripple/app/misc/FeeEscalation.md). +See also: [Fee Escalation explanation in `rippled` repository](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/misc/FeeEscalation.md). ### Queued Transactions diff --git a/docs/infrastructure/configuration/data-retention/configure-history-sharding.md b/docs/infrastructure/configuration/data-retention/configure-history-sharding.md index 4c947020447..09303ba133a 100644 --- a/docs/infrastructure/configuration/data-retention/configure-history-sharding.md +++ b/docs/infrastructure/configuration/data-retention/configure-history-sharding.md @@ -53,7 +53,7 @@ The `type` field of `[shard_db]` can be omitted. If present, it _MUST_ be `NuDB` {% admonition type="warning" name="Caution" %}If `rippled` detects the wrong type of data in the shard store path, it may [fail to start](../../troubleshooting/server-wont-start.md). You should use a new folder for the shard store. If you previously used a RocksDB shard store (`rippled` 1.2.x and lower), use a different path or delete the RocksDB shard data.{% /admonition %} -For more information, reference the `[shard_db]` example in the [rippled.cfg configuration example](https://github.com/XRPLF/rippled/blob/master/cfg/rippled-example.cfg). +For more information, reference the `[shard_db]` example in the [rippled.cfg configuration example](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/cfg/rippled-example.cfg). ## 3. Restart the server diff --git a/docs/infrastructure/configuration/data-retention/online-deletion.md b/docs/infrastructure/configuration/data-retention/online-deletion.md index ce63815dcef..6a4e156eb0e 100644 --- a/docs/infrastructure/configuration/data-retention/online-deletion.md +++ b/docs/infrastructure/configuration/data-retention/online-deletion.md @@ -8,7 +8,7 @@ labels: - Core Server --- # Online Deletion -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/app/misc/SHAMapStoreImp.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/misc/SHAMapStoreImp.cpp "Source") The online deletion feature lets the `rippled` server delete the server's local copy of old ledger versions to keep disk usage from rapidly growing over time. The default config file sets online deletion to run automatically, but online deletion can also be configured to run only when prompted. diff --git a/docs/infrastructure/configuration/peering/cluster-rippled-servers.md b/docs/infrastructure/configuration/peering/cluster-rippled-servers.md index 75c9e698c44..b0df1f39af8 100644 --- a/docs/infrastructure/configuration/peering/cluster-rippled-servers.md +++ b/docs/infrastructure/configuration/peering/cluster-rippled-servers.md @@ -33,7 +33,7 @@ If you run multiple [`rippled` servers](../../../concepts/networks-and-servers/i Save the `validation_seed` and `validation_public_key` parameters from each response somewhere secure. -3. On each server, edit the [config file](https://github.com/XRPLF/rippled/blob/master/cfg/rippled-example.cfg), modifying the following sections: +3. On each server, edit the [config file](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/cfg/rippled-example.cfg), modifying the following sections: 1. In the `[ips_fixed]` section, list the IP address and port of each _other_ member of the cluster. For each of those servers, the port number should match the `protocol = peer` port (usually 51235) from that server's `rippled.cfg`. For example: diff --git a/docs/infrastructure/configuration/server-modes/run-rippled-as-a-validator.md b/docs/infrastructure/configuration/server-modes/run-rippled-as-a-validator.md index 3f57208c4ef..df2d6edefa0 100644 --- a/docs/infrastructure/configuration/server-modes/run-rippled-as-a-validator.md +++ b/docs/infrastructure/configuration/server-modes/run-rippled-as-a-validator.md @@ -51,7 +51,7 @@ Strive to have your validator embody the following properties. Being a good vali A good validator has a clearly identified owner. Providing [domain verification](#6-provide-domain-verification) is a good start. Ideally, XRP Ledger network UNLs include validators run by different owners in multiple legal jurisdictions and geographic areas. This reduces the chance that any localized events could interfere with the impartial operations of trusted validators. -It is strongly recommended that operators use the list providers that are present in this [example file](https://github.com/XRPLF/rippled/blob/develop/cfg/validators-example.txt). +It is strongly recommended that operators use the list providers that are present in this [example file](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/cfg/validators-example.txt). @@ -163,7 +163,7 @@ For a comparison of these approaches, see [Pros and Cons of Peering Configuratio This configuration connects your validator to the XRP Ledger network using [discovered peers](../../../concepts/networks-and-servers/peer-protocol.md#peer-discovery). This is the default behavior for `rippled` servers. -_**To connect your validator to the XRP Ledger network using discovered peers,**_ omit the `[peer_private]` stanza or set it to `0` in your validator's `rippled.cfg` file. The [example `rippled.cfg` file](https://github.com/XRPLF/rippled/blob/develop/cfg/rippled-example.cfg) is delivered with this configuration. +_**To connect your validator to the XRP Ledger network using discovered peers,**_ omit the `[peer_private]` stanza or set it to `0` in your validator's `rippled.cfg` file. The [example `rippled.cfg` file](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/cfg/rippled-example.cfg) is delivered with this configuration. ### Connect using proxies @@ -218,7 +218,7 @@ _**To connect your validator to the network using public hubs:**_ ``` {% admonition type="info" name="Note" %} -The above list may evolve over time. To ensure you're using the most current set of public hubs, refer to the official [`rippled-example.cfg`](https://github.com/XRPLF/rippled/blob/develop/cfg/rippled-example.cfg) maintained by XRPLF. +The above list may evolve over time. To ensure you're using the most current set of public hubs, refer to the official [`rippled-example.cfg`](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/cfg/rippled-example.cfg) maintained by XRPLF. {% /admonition %} diff --git a/docs/infrastructure/installation/build-on-linux-mac-windows.md b/docs/infrastructure/installation/build-on-linux-mac-windows.md index 40c9685750e..62723dc4d4b 100644 --- a/docs/infrastructure/installation/build-on-linux-mac-windows.md +++ b/docs/infrastructure/installation/build-on-linux-mac-windows.md @@ -12,6 +12,6 @@ top_nav_grouping: Popular Pages Building `rippled` across various platforms such as Windows, Linux, or macOS requires a C++ development environment. You will need tools like Git, Python, Conan, CMake, and a suitable C++ compiler. -To continue, proceed to [the latest `rippled` build instructions on GitHub](https://github.com/XRPLF/rippled/blob/develop/BUILD.md). +To continue, proceed to [the latest `rippled` build instructions on GitHub](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/BUILD.md). {% raw-partial file="/docs/_snippets/common-links.md" /%} diff --git a/docs/infrastructure/installation/build-run-rippled-in-reporting-mode.md b/docs/infrastructure/installation/build-run-rippled-in-reporting-mode.md index 5f2ff16c061..a048219caec 100644 --- a/docs/infrastructure/installation/build-run-rippled-in-reporting-mode.md +++ b/docs/infrastructure/installation/build-run-rippled-in-reporting-mode.md @@ -113,7 +113,7 @@ NuDB is installed as part of your `rippled` build setup and does not require any ### Steps -1. Build `rippled` for reporting mode on [Ubuntu or macOS](https://github.com/XRPLF/rippled/blob/release/BUILD.md). +1. Build `rippled` for reporting mode on [Ubuntu or macOS](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/BUILD.md). {% tabs %} diff --git a/docs/infrastructure/installation/capacity-planning.md b/docs/infrastructure/installation/capacity-planning.md index 10bea0551b9..1ace156d811 100644 --- a/docs/infrastructure/installation/capacity-planning.md +++ b/docs/infrastructure/installation/capacity-planning.md @@ -21,7 +21,7 @@ You should consider these factors to ensure that your server has the capacity to The default configuration file contains settings for a broad range of common use cases. You can get better performance by customizing the settings for your specific hardware and intended usage pattern. -The settings in this section are parameters in the `rippled.cfg` file. You can access an example config file, `rippled-example.cfg`, in the [`cfg` directory](https://github.com/XRPLF/rippled/blob/develop/cfg/rippled-example.cfg) in the `rippled` GitHub repo. The settings in the example config file match the default config installed alongside the server. +The settings in this section are parameters in the `rippled.cfg` file. You can access an example config file, `rippled-example.cfg`, in the [`cfg` directory](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/cfg/rippled-example.cfg) in the `rippled` GitHub repo. The settings in the example config file match the default config installed alongside the server. ### Node Size diff --git a/docs/infrastructure/testing-and-auditing/start-a-new-genesis-ledger-in-stand-alone-mode.md b/docs/infrastructure/testing-and-auditing/start-a-new-genesis-ledger-in-stand-alone-mode.md index 7774771fae5..b2c52d2fc89 100644 --- a/docs/infrastructure/testing-and-auditing/start-a-new-genesis-ledger-in-stand-alone-mode.md +++ b/docs/infrastructure/testing-and-auditing/start-a-new-genesis-ledger-in-stand-alone-mode.md @@ -18,7 +18,7 @@ rippled -a --start --conf=/path/to/rippled.cfg For more information on the options you can use when starting `rippled` in stand-alone mode, see [Commandline Usage: Stand-Alone Mode Options](../commandline-usage.md#stand-alone-mode-options). -In a genesis ledger, the [genesis address](../../concepts/accounts/addresses.md#special-addresses) holds all 100 billion XRP. The keys of the genesis address are [hardcoded](https://github.com/XRPLF/rippled/blob/94ed5b3a53077d815ad0dd65d490c8d37a147361/src/ripple/app/ledger/Ledger.cpp#L184) as follows: +In a genesis ledger, the [genesis address](../../concepts/accounts/addresses.md#special-addresses) holds all 100 billion XRP. The keys of the genesis address are [hardcoded](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/ledger/Ledger.cpp#L184) as follows: **Address:** `rHb9CJAWyB4rj91VRWn96DkukG4bwdtyTh` diff --git a/docs/infrastructure/troubleshooting/diagnosing-problems.md b/docs/infrastructure/troubleshooting/diagnosing-problems.md index f03d8cd5ca2..92994bd1550 100644 --- a/docs/infrastructure/troubleshooting/diagnosing-problems.md +++ b/docs/infrastructure/troubleshooting/diagnosing-problems.md @@ -94,7 +94,7 @@ For troubleshooting purposes, the most important fields are (from most commonly - If you have 0 peers, your server may be unable to contact the network, or your system clock may be wrong. (Ripple recommends running an [NTP](http://www.ntp.org/) daemon on all servers to keep their clocks synced.) - - If you have exactly 10 peers, that may indicate that your `rippled` is unable to receive incoming connections through a router using [NAT](https://en.wikipedia.org/wiki/Network_address_translation). You can improve connectivity by configuring your router's firewall to forward the port used for peer-to-peer connections (port 51235 [by default](https://github.com/XRPLF/rippled/blob/8429dd67e60ba360da591bfa905b58a35638fda1/cfg/rippled-example.cfg#L1065)). + - If you have exactly 10 peers, that may indicate that your `rippled` is unable to receive incoming connections through a router using [NAT](https://en.wikipedia.org/wiki/Network_address_translation). You can improve connectivity by configuring your router's firewall to forward the port used for peer-to-peer connections (port 51235 [by default](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/cfg/rippled-example.cfg#L1432)). ### No Response from Server @@ -118,7 +118,7 @@ This generally indicates one of several problems: ## Check the server log -[By default,](https://github.com/XRPLF/rippled/blob/master/cfg/rippled-example.cfg#L1139-L1142) `rippled` writes the server's debug log to the file `/var/log/rippled/debug.log`. The location of the debug log can differ based on your server's config file. If you start the `rippled` service directly (instead of using `systemctl` or `service` to start it), it also prints log messages to the console by default. +[By default,](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/cfg/rippled-example.cfg#L1481-L1484) `rippled` writes the server's debug log to the file `/var/log/rippled/debug.log`. The location of the debug log can differ based on your server's config file. If you start the `rippled` service directly (instead of using `systemctl` or `service` to start it), it also prints log messages to the console by default. The default config file sets the log level to severity "warning" for all categories of log messages by internally using the [log_level method][] during startup. You can control the verbosity of the debug log [using the `--silent` commandline option during startup](../commandline-usage.md#verbosity-options) and with the [log_level method][] while the server is running. (See the `[rpc_startup]` stanza of the config file for settings.) @@ -131,7 +131,7 @@ For a more thorough explanation of various types of log messages, see [Understan If you have problems diagnosing the problem, or you are unable to resolve the problem with any of the common fixes, you may want to ask for help in a support forum or the [GitHub issues](https://github.com/XRPLF/rippled/issues). When asking for help, you can use an info collection script to gather information about your system to help others diagnose the issue. -The official package installation (for [Ubuntu/Debian](../installation/install-rippled-on-ubuntu.md) or [CentOS/RedHat](../installation/install-rippled-on-centos-rhel-with-yum.md)) installs such a script by default, to `/opt/ripple/bin/getRippledInfo`. If you compiled `rippled` yourself, you can find the same script [in the `rippled` source code repository](https://github.com/XRPLF/rippled/blob/develop/bin/getRippledInfo). +The official package installation (for [Ubuntu/Debian](../installation/install-rippled-on-ubuntu.md) or [CentOS/RedHat](../installation/install-rippled-on-centos-rhel-with-yum.md)) installs such a script by default, to `/opt/ripple/bin/getRippledInfo`. If you compiled `rippled` yourself, you can find the same script [in the `rippled` source code repository](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/bin/getRippledInfo). To use the script: diff --git a/docs/infrastructure/troubleshooting/fix-sqlite-tx-db-page-size-issue.md b/docs/infrastructure/troubleshooting/fix-sqlite-tx-db-page-size-issue.md index b09b263378f..3437a485567 100644 --- a/docs/infrastructure/troubleshooting/fix-sqlite-tx-db-page-size-issue.md +++ b/docs/infrastructure/troubleshooting/fix-sqlite-tx-db-page-size-issue.md @@ -29,7 +29,7 @@ If your server is vulnerable to this problem, you can detect it two ways: In both cases, detection of the problem requires access to `rippled`'s server logs. -{% admonition type="success" name="Tip" %}The location of the debug log depends on your `rippled` server's config file. The [default configuration](https://github.com/XRPLF/rippled/blob/master/cfg/rippled-example.cfg#L1139-L1142) writes the server's debug log to the file `/var/log/rippled/debug.log`.{% /admonition %} +{% admonition type="success" name="Tip" %}The location of the debug log depends on your `rippled` server's config file. The [default configuration](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/cfg/rippled-example.cfg#L1481-L1484) writes the server's debug log to the file `/var/log/rippled/debug.log`.{% /admonition %} ### Proactive Detection diff --git a/docs/infrastructure/troubleshooting/server-wont-start.md b/docs/infrastructure/troubleshooting/server-wont-start.md index 235d2d9fbd0..75ab5ae62ec 100644 --- a/docs/infrastructure/troubleshooting/server-wont-start.md +++ b/docs/infrastructure/troubleshooting/server-wont-start.md @@ -69,7 +69,7 @@ Possible solutions: - Create a config file that can be read by the `rippled` user at `$HOME/.config/ripple/rippled.cfg` (where `$HOME` points to the `rippled` user's home directory). - {% admonition type="success" name="Tip" %}The `rippled` repository contains [an example `rippled.cfg` file](https://github.com/XRPLF/rippled/blob/master/cfg/rippled-example.cfg) which is provided as the default config when you do an installation from a binary package. If you do not have the file, you can copy it from there.{% /admonition %} + {% admonition type="success" name="Tip" %}The `rippled` repository contains [an example `rippled.cfg` file](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/cfg/rippled-example.cfg) which is provided as the default config when you do an installation from a binary package. If you do not have the file, you can copy it from there.{% /admonition %} - Specify the path to your preferred config file using the `--conf` [commandline option](../commandline-usage.md). @@ -87,7 +87,7 @@ Possible solutions: - Check that the `validators.txt` file exists and the `rippled` user has permissions to read it. - {% admonition type="success" name="Tip" %}The `rippled` repository contains [an example `validators.txt` file](https://github.com/XRPLF/rippled/blob/master/cfg/validators-example.txt) which is provided as the default config when you do an installation from a binary package. If you do not have the file, you can copy it from there.{% /admonition %} + {% admonition type="success" name="Tip" %}The `rippled` repository contains [an example `validators.txt` file](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/cfg/validators-example.txt) which is provided as the default config when you do an installation from a binary package. If you do not have the file, you can copy it from there.{% /admonition %} - Edit your `rippled.cfg` file and modify the `[validators_file]` setting to have the correct path to your `validators.txt` (or equivalent) file. Check for extra whitespace before or after the filename. diff --git a/docs/infrastructure/troubleshooting/understanding-log-messages.md b/docs/infrastructure/troubleshooting/understanding-log-messages.md index db1f98cdcbd..6c0f72ccc56 100644 --- a/docs/infrastructure/troubleshooting/understanding-log-messages.md +++ b/docs/infrastructure/troubleshooting/understanding-log-messages.md @@ -125,7 +125,7 @@ The following log message indicates that a client to the server's public API has Resource:WRN Consumer entry 169.55.164.21 dropped with balance 15970 at or above drop threshold 15000 ``` -The entry contains the IP address of the client that exceeded its rate limit, and the client's "balance", which is a score estimating the rate at which the client has been using the API. The threshold for dropping a client is [hardcoded to a score of 15000](https://github.com/XRPLF/rippled/blob/06c371544acc3b488b9d9c057cee4e51f6bef7a2/src/ripple/resource/impl/Tuning.h#L34-L35). +The entry contains the IP address of the client that exceeded its rate limit, and the client's "balance", which is a score estimating the rate at which the client has been using the API. The threshold for dropping a client is [hardcoded to a score of 15000](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/resource/detail/Tuning.h#L34-L35). If you see frequent messages from the same IP address, you may want to block those IP addresses from your network to reduce the load on your server's public API. (For example, you may be able to configure your firewall to block those IP addresses.) diff --git a/docs/introduction/software-ecosystem.md b/docs/introduction/software-ecosystem.md index a0997489cc5..0ab953a2f73 100644 --- a/docs/introduction/software-ecosystem.md +++ b/docs/introduction/software-ecosystem.md @@ -24,7 +24,7 @@ The XRP Ledger is home to a deep, layered ecosystem of software projects powerin ### Core Servers -The peer-to-peer network at the heart of the XRP Ledger requires a highly-reliable, efficient server to enforce the rules of consensus and transaction processing. The XRP Ledger Foundation publishes a reference implementation of this server software, called [**`rippled`**](../concepts/networks-and-servers/index.md) (pronounced "ripple-dee"). The server is available under [a permissive open-source license](https://github.com/XRPLF/rippled/blob/develop/LICENSE.md), so anyone can inspect and modify their own instance of the server, and re-publish with few restrictions. +The peer-to-peer network at the heart of the XRP Ledger requires a highly-reliable, efficient server to enforce the rules of consensus and transaction processing. The XRP Ledger Foundation publishes a reference implementation of this server software, called [**`rippled`**](../concepts/networks-and-servers/index.md) (pronounced "ripple-dee"). The server is available under [a permissive open-source license](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/LICENSE.md), so anyone can inspect and modify their own instance of the server, and re-publish with few restrictions. ![Core Servers](/docs/img/ecosystem-peer-to-peer.svg) diff --git 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 index e508bb358aa..8099bff466d 100644 --- 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 @@ -8,7 +8,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/1e01cd34f7a216092ed779f291b43324c167167a/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. diff --git 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 index d12159fea75..ff4fda84929 100644 --- 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 @@ -8,7 +8,7 @@ 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/1e01cd34f7a216092ed779f291b43324c167167a/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). diff --git 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 index 6983bf562a2..a4019c1f939 100644 --- 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 @@ -7,7 +7,7 @@ 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/1e01cd34f7a216092ed779f291b43324c167167a/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. diff --git a/docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/crawl_shards.md b/docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/crawl_shards.md deleted file mode 100644 index 7528c02e2f1..00000000000 --- a/docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/crawl_shards.md +++ /dev/null @@ -1,141 +0,0 @@ ---- -html: crawl_shards.html -parent: logging-and-data-management-methods.html -seo: - description: Request information about which history shards peers have. -labels: - - Data Retention ---- -# crawl_shards -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/CrawlShards.cpp "Source") - -Requests information from peer servers about which [shards of historical ledger data](../../../../infrastructure/configuration/data-retention/history-sharding.md) they have available. - -_The `crawl_shards` method is an [admin method](../index.md) that cannot be run by unprivileged users._ - -### Request Format - -An example of the request format: - -{% tabs %} - -{% tab label="WebSocket" %} -```json -{ - "command": "crawl_shards", - "public_key": true, - "limit": 0 -} -``` -{% /tab %} - -{% tab label="JSON-RPC" %} -```json -{ - "method": "crawl_shards", - "params": [ - { - "public_key": true, - "limit": 0 - } - ] -} -``` -{% /tab %} - -{% /tabs %} - -{% admonition type="info" name="Note" %}There is no command-line syntax for this method. Use the [json method][] to access this from the command line.{% /admonition %} - -The request includes the following fields: - -| `Field` | Type | Description | -|:---------|:--------|:--------------------------------------------------------| -| `public_key` | Boolean | _(Optional)_ If `true`, the response includes the node public keys (for peer-to-peer communications) of servers that were crawled. The default is `false`. | -| `limit` | Number | _(Optional)_ How many hops deep to search. The default is 0, which searches direct peers only. With a limit of `1`, searches peers' peers also. The maximum value is `3`. | - -{% admonition type="warning" name="Caution" %}The number of peers potentially searched grows exponentially as `limit` increases. With a limit of 2 or 3, it can take several seconds for the server to respond to the API request.{% /admonition %} - - -### Response Format - -An example of a successful response: - -{% tabs %} - -{% tab label="WebSocket" %} -```json -{ - "result": { - "complete_shards": "1-2,5,8-9,584,1973,2358", - "peers": [ - { - "complete_shards": "1-2,8,47,371,464,554,653,857,1076,1402,1555,1708,1813,1867", - "public_key": "n9LxFZiySnfDSvfh23N94UxsFkCjWyrchTeKHcYE6tJJQL5iejb2" - }, - { - "complete_shards": "8-9,584", - "ip": "192.168.1.132", - "public_key": "n9MN5xwYqbrj64rtfZAXQy7Y3sNxXZJeLt7Lj61a9DYEZ4SE2tQQ" - } - ] - }, - "status": "success", - "type": "response" -} -``` -{% /tab %} - -{% tab label="JSON-RPC" %} -```json -200 OK - -{ - "result": { - "complete_shards": "1-2,5,8-9,584,1973,2358", - "peers": [ - { - "complete_shards": "1-2,8,47,371,464,554,653,857,1076,1402,1555,1708,1813,1867", - "public_key": "n9LxFZiySnfDSvfh23N94UxsFkCjWyrchTeKHcYE6tJJQL5iejb2" - }, - { - "complete_shards": "8-9,584", - "ip": "192.168.1.132", - "public_key": "n9MN5xwYqbrj64rtfZAXQy7Y3sNxXZJeLt7Lj61a9DYEZ4SE2tQQ" - } - ], - "status": "success" - } -} -``` -{% /tab %} - -{% /tabs %} - -The response follows the [standard format][], with a successful result containing the following fields: - -| `Field` | Type | Description | -|:------------------|:-------|:------------------------------------------------| -| `complete_shards` | String | _(May be omitted)_ The range of [history shards](../../../../infrastructure/configuration/data-retention/history-sharding.md) that are available on the local server. This may be an empty string, or a disjointed range. For example, `1-2,5,7-9` indicates that shards 1, 2, 5, 7, 8, and 9 are available. Omitted if this server does not have history sharding enabled. | -| `peers` | Array | _(May be omitted)_ List of **Peer Shard Objects** (see below) describing which history shards each peer has available. The response omits this field if no peers within the number of hops specified by `limit` have any shards. | - -#### Peer Shard Objects - -Each member of the `peers` array of the response is an object that describes one server in the peer-to-peer network. The list only includes peers that have at least one complete [history shard](../../../../infrastructure/configuration/data-retention/history-sharding.md) available. Each object in the array has the following fields: - -| `Field` | Type | Description | -|:----------|:-------|:--------------------------------------------------------| -| `complete_shards` | String | The range of complete history shards this peer has available. This may be disjointed. For example, `1-2,5,7-9` indicates that shards 1, 2, 5, 7, 8, and 9 are available. | -| `incomplete_shards` | String | _(May be omitted)_ A comma-separated list of history shards this peer has partially downloaded, and percent completion for each. For example, `1:50,2:25` indicates that shard 1 is 50% downloaded and shard 2 is 25% downloaded. {% badge href="https://github.com/XRPLF/rippled/releases/tag/1.8.1" %}New in: rippled 1.8.1{% /badge %} | -| `public_key` | String | _(Omitted unless the request specified `"public_key": true`)_ The public key this peer uses for peer-to-peer communications, in the XRP Ledger's [base58 format](../../../protocol/data-types/base58-encodings.md). | - -The `ip` field is no longer provided. {% badge href="https://github.com/XRPLF/rippled/releases/tag/1.8.1" %}Removed in: rippled 1.8.1{% /badge %} - - -### Possible Errors - -- Any of the [universal error types][]. -- `invalidParams` - One or more required fields were omitted from the request, or a provided field was specified as the wrong data type. -- `reportingUnsupported` - ([Reporting Mode][] servers only) This method is not available in Reporting Mode. - -{% raw-partial file="/docs/_snippets/common-links.md" /%} diff --git a/docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/download_shard.md b/docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/download_shard.md deleted file mode 100644 index 84c6a6f1d6e..00000000000 --- a/docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/download_shard.md +++ /dev/null @@ -1,144 +0,0 @@ ---- -html: download_shard.html -parent: logging-and-data-management-methods.html -seo: - description: Download a specific shard of ledger history. -labels: - - Data Retention ---- -# download_shard -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/DownloadShard.cpp "Source") - -Instructs the server to download a specific [shard of historical ledger data](../../../../infrastructure/configuration/data-retention/history-sharding.md) from an external source. Your `rippled` server must be [configured to store history shards](../../../../infrastructure/configuration/data-retention/configure-history-sharding.md). {% badge href="https://github.com/XRPLF/rippled/releases/tag/1.6.0" %}Updated in: rippled 1.6.0{% /badge %} - -_The `download_shard` method is an [admin method](../index.md) that cannot be run by unprivileged users._ - -The external source must provide the shard as an [lz4-compressed](https://lz4.github.io/lz4/) [tar archive](https://en.wikipedia.org/wiki/Tar_(computing)) served via HTTPS. The archive must contain the shard directory and data files in NuDB format. - -Downloading and importing shards using this method is usually faster than acquiring the shards individually from the peer-to-peer network. You can also use this method to choose a specific range or set of shards to provide from your server. - -### Request Format - -An example of the request format: - -{% tabs %} - -{% tab label="WebSocket" %} -```json -{ - "command": "download_shard", - "shards": [ - {"index": 1, "url": "https://example.com/1.tar.lz4"}, - {"index": 2, "url": "https://example.com/2.tar.lz4"}, - {"index": 5, "url": "https://example.com/5.tar.lz4"} - ] -} -``` -{% /tab %} - -{% tab label="JSON-RPC" %} -```json -{ - "method": "download_shard", - "params": [ - { - "shards": [ - {"index": 1, "url": "https://example.com/1.tar.lz4"}, - {"index": 2, "url": "https://example.com/2.tar.lz4"}, - {"index": 5, "url": "https://example.com/5.tar.lz4"} - ] - } - ] -} -``` -{% /tab %} - -{% tab label="Commandline" %} -```sh -# Syntax: download_shard [[ ]] -rippled download_shard 1 https://example.com/1.tar.lz4 2 https://example.com/2.tar.lz4 5 https://example.com/5.tar.lz4 -``` -{% /tab %} - -{% /tabs %} - - -The request includes the following field: - -| `Field` | Type | Description | -|:-----------|:--------|:------------------------------------------------------| -| `shards` | Array | List of Shard Descriptor objects (see below) describing shards to download and where to download them from. | - -The `validate` field is deprecated and may be removed in a future version. (The server always checks the integrity of shards when it imports them.) {% badge href="https://github.com/XRPLF/rippled/releases/tag/1.6.0" %}Updated in: rippled 1.6.0{% /badge %} - -Each **Shard Descriptor object** in the `shards` array has the following fields: - -| `Field` | Type | Description | -|:--------|:-------|:----------------------------------------------------------| -| `index` | Number | The index of the shard to retrieve. In the production XRP Ledger, the oldest shard has index 1 and contains ledgers 32750-32768. The next shard has index 2 and contains ledgers 32769-49152, and so on. | -| `url` | String | The URL where this shard can be downloaded. The URL must start with `http://` or `https://` and must end with `.tar.lz4` (not case-sensitive). The web server providing this download must use a valid TLS certificate signed by a trusted Certificate Authority (CA). (`rippled` uses the operating system's CA store.) {% badge href="https://github.com/XRPLF/rippled/releases/tag/1.7.0" %}Updated in: rippled 1.7.0{% /badge %} | - -### Response Format - -An example of a successful response: - -{% tabs %} - -{% tab label="WebSocket" %} -```json -{ - "result": { - "message": "downloading shards 1-2,5" - }, - "status": "success", - "type": "response" -} -``` -{% /tab %} - -{% tab label="JSON-RPC" %} -```json -200 OK - -{ - "result": { - "message": "downloading shards 1-2,5", - "status": "success" - } -} -``` -{% /tab %} - -{% tab label="Commandline" %} -```json -Loading: "/etc/rippled.cfg" -Connecting to 127.0.0.1:5005 - -{ - "result": { - "message": "downloading shards 1-2,5", - "status": "success" - } -} -``` -{% /tab %} - -{% /tabs %} - -The response follows the [standard format][], with a successful result containing the following fields: - -| `Field` | Type | Description | -|:----------|:-------|:--------------------------------------------------------| -| `message` | String | A message describing the actions taken in response to this request. | - -{% admonition type="success" name="Tip" %}To see which shards your server has available, use the [crawl_shards method][]. Alternatively, you can look at the subfolders in your configured location for the shard store (the `path` parameter of `[shard_db]` in your `rippled.cfg`). The folders are named to match the numbers of the shards; up to one of those folders may contain a `control.txt` file indicating that the shard is incomplete.{% /admonition %} - -### Possible Errors - -- Any of the [universal error types][]. -- `notEnabled` - The server is not configured with a shard store. -- `tooBusy` - The server is already downloading the shard, either from the peer-to-peer network or as the result of a previous `download_shard` request. -- `invalidParams` - One or more required fields were omitted from the request, or a provided field was specified as the wrong data type. -- `reportingUnsupported` - ([Reporting Mode][] servers only) This method is not available in Reporting Mode. - -{% raw-partial file="/docs/_snippets/common-links.md" /%} diff --git 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 index 58fcea0fcdb..b9a1420ac41 100644 --- 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 @@ -7,9 +7,9 @@ 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/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/ledger/detail/LedgerCleaner.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/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/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` method is an [admin method](../index.md) that cannot be run by unprivileged users._ diff --git 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 index 1622917bbb8..1b9bd63996a 100644 --- 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 @@ -7,7 +7,7 @@ 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/1e01cd34f7a216092ed779f291b43324c167167a/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. diff --git 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 index 9dfddb02aa9..d197b119954 100644 --- 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 @@ -7,7 +7,7 @@ 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/1e01cd34f7a216092ed779f291b43324c167167a/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. diff --git 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 index a695559a7ed..6f266f4c34c 100644 --- 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 @@ -7,7 +7,7 @@ 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/1e01cd34f7a216092ed779f291b43324c167167a/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. diff --git a/docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/node_to_shard.md b/docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/node_to_shard.md deleted file mode 100644 index e1d13bacb87..00000000000 --- a/docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/node_to_shard.md +++ /dev/null @@ -1,120 +0,0 @@ ---- -html: node_to_shard.html -parent: logging-and-data-management-methods.html -seo: - description: Copy data from the ledger store into the shard store. -labels: - - Data Retention ---- -# node_to_shard -[[Source]](https://github.com/XRPLF/rippled/blob/develop/src/ripple/rpc/handlers/NodeToShard.cpp "Source") - -The {% code-page-name /%} method manages copying data from the ledger store to the [shard store](../../../../infrastructure/configuration/data-retention/history-sharding.md). It can start, stop, or check the status of copying the data. - -_The {% code-page-name /%} method is an [admin method](../index.md) that cannot be run by unprivileged users._ - - -### Request Format - -An example of the request format: - -{% tabs %} - -{% tab label="WebSocket" %} -```json -{ - "command": "{% $frontmatter.seo.title %}", - "action": "start" -} -``` -{% /tab %} - -{% tab label="JSON-RPC" %} -```json -{ - "method": "{% $frontmatter.seo.title %}", - "params": [{ - "action": "start" - }] -} -``` -{% /tab %} - -{% tab label="Commandline" %} -```sh -#Syntax: {% $frontmatter.seo.title %} start|stop|status -rippled {% $frontmatter.seo.title %} start -``` -{% /tab %} - -{% /tabs %} - -The request includes the following parameters: - -| `Field` | Type | Description | -|:---------|:-------|:---------------------------------------------------------| -| `action` | String | Either `start`, `stop` or `status` depending on what action to take. | - - -### Response Format - -An example of a successful response: - -{% tabs %} - -{% tab label="WebSocket" %} -```json -{ - "result": { - "message": "Database import initiated..." - }, - "status": "success", - "type": "response" -} -``` -{% /tab %} - -{% tab label="JSON-RPC" %} -```json -{ - "result" : { - "message" : "Database import initiated...", - "status" : "success" - } -} - -``` -{% /tab %} - -{% tab label="Commandline" %} -```json -Loading: "/etc/rippled.cfg" -Connecting to 127.0.0.1:5005 - -{ - "result" : { - "message" : "Database import initiated...", - "status" : "success" - } -} - -``` -{% /tab %} - -{% /tabs %} - -The response follows the [standard format][], with a successful result containing the following fields: - -| `Field` | Type | Description | -|:----------|:-------|:--------------------------------------------------------| -| `message` | String | A human-readable message indicating the action taken in response to the command. | - - -### Possible Errors - -- Any of the [universal error types][]. -- `internal` - If you attempt an invalid operation like checking the status of a copy when one isn't running. -- `notEnabled` - If the server is not configured to store [history shards](../../../../infrastructure/configuration/data-retention/history-sharding.md). -- `invalidParams` - One or more fields are specified incorrectly, or one or more required fields are missing. - -{% raw-partial file="/docs/_snippets/common-links.md" /%} diff --git 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 index 12a5ab9090f..f71e01c1aa5 100644 --- 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 @@ -7,7 +7,7 @@ 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/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/Connect.cpp "Source") The `connect` command forces the `rippled` server to connect to a specific peer `rippled` server. diff --git 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 index 4689326f431..5e1818d92ce 100644 --- 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 @@ -7,7 +7,7 @@ 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/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/Reservations.cpp#L36 "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). diff --git 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 index 5c5d0bd5f4a..11e85c5594c 100644 --- 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 @@ -7,7 +7,7 @@ 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/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/Reservations.cpp#L89 "Source") The {% code-page-name /%} method removes a specific [peer reservation][], if one exists. diff --git 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 index c3d6d8acd44..8efb63a2789 100644 --- 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 @@ -7,7 +7,7 @@ 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/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/Reservations.cpp#L116 "Source") The {% code-page-name /%} method lists [peer reservations][]. diff --git 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 index a54a6cec5da..9c30803e5f8 100644 --- 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 @@ -7,7 +7,7 @@ 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/1e01cd34f7a216092ed779f291b43324c167167a/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. diff --git 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 index 9a55de12487..611ccec89bb 100644 --- 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 @@ -7,7 +7,7 @@ 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/1e01cd34f7a216092ed779f291b43324c167167a/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. diff --git 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 index 403f7df1370..bc2c8af91c5 100644 --- 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 @@ -7,7 +7,7 @@ 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/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/Stop.cpp "Source") Gracefully shuts down the server. diff --git 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 index b34231f3ae8..414aaf25b14 100644 --- 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 @@ -7,7 +7,7 @@ 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/1e01cd34f7a216092ed779f291b43324c167167a/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. diff --git 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 index cf56a8454dc..202be47ea76 100644 --- 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 @@ -7,7 +7,7 @@ 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/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/SignFor.cpp "Source") The `sign_for` command provides one signature for a [multi-signed transaction](../../../../concepts/accounts/multi-signing.md). diff --git 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 index e6dd985402a..ba2aa57f82e 100644 --- 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 @@ -8,7 +8,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/1e01cd34f7a216092ed779f291b43324c167167a/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. diff --git 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 index c36708c43a6..2e8e4647674 100644 --- 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 @@ -8,7 +8,7 @@ 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/1e01cd34f7a216092ed779f291b43324c167167a/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). diff --git 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 index 9dac21b0032..88aedba04d2 100644 --- 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 @@ -7,7 +7,7 @@ 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/1e01cd34f7a216092ed779f291b43324c167167a/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. diff --git 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 index 2a49b13f5f9..49c9b181938 100644 --- 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 @@ -7,7 +7,7 @@ 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/1e01cd34f7a216092ed779f291b43324c167167a/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. diff --git 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 index 95cfe674aa8..7d187f02301 100644 --- 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 @@ -7,7 +7,7 @@ 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/1e01cd34f7a216092ed779f291b43324c167167a/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. diff --git 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 index 11c5087e994..ad80ba9fd07 100644 --- 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 @@ -8,7 +8,7 @@ labels: - ブロックチェーン --- # validator_info -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/ValidatorInfo.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/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. diff --git 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 index aa4a19623a8..f437781b07a 100644 --- 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 @@ -8,7 +8,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/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/ValidatorListSites.cpp "Source") The `validator_list_sites` command returns status information of sites serving validator lists. diff --git 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 index 703920f2e33..10de4ef4c54 100644 --- 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 @@ -8,7 +8,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/1e01cd34f7a216092ed779f291b43324c167167a/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. diff --git a/docs/references/http-websocket-apis/api-conventions/rate-limiting.md b/docs/references/http-websocket-apis/api-conventions/rate-limiting.md index 48e81ad8123..4cd134d3840 100644 --- a/docs/references/http-websocket-apis/api-conventions/rate-limiting.md +++ b/docs/references/http-websocket-apis/api-conventions/rate-limiting.md @@ -46,7 +46,7 @@ Server is overloaded ``` ## Rate Per Request -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/libxrpl/resource/Fees.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/libxrpl/resource/Fees.cpp "Source") The server calculates a client's usage rate based on the number of requests made over time, and weighs different types of requests based on approximately how much work the server must do to serve them. Follow-up messages from the server for the [subscribe method][] and [path_find method][] also count towards a client's usage rate. diff --git a/docs/references/http-websocket-apis/index.md b/docs/references/http-websocket-apis/index.md index d41901a4f83..c1f5eddb00a 100644 --- a/docs/references/http-websocket-apis/index.md +++ b/docs/references/http-websocket-apis/index.md @@ -12,7 +12,7 @@ Currently, there are two API versions: `1` and `2` {% badge href="https://github Separate API requests can use different API versions even on the same persistent connection. For example, if you connect through WebSocket to a server that supports API versions 1 and 2, you can make an `account_tx` request using API version 2 and then make another `account_tx` request using API version 1 from the same connection. -For a full list of the differences between API versions, see [API-CHANGELOG on GitHub](https://github.com/xrplf/rippled/blob/develop/API-CHANGELOG.md). +For a full list of the differences between API versions, see [API-CHANGELOG on GitHub](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/API-CHANGELOG.md). ## Default API Versions diff --git a/docs/references/http-websocket-apis/peer-port-methods/health-check.md b/docs/references/http-websocket-apis/peer-port-methods/health-check.md index 9b1a8ae3450..086710e87b1 100644 --- a/docs/references/http-websocket-apis/peer-port-methods/health-check.md +++ b/docs/references/http-websocket-apis/peer-port-methods/health-check.md @@ -7,7 +7,7 @@ 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/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/overlay/detail/OverlayImpl.cpp#L944-L1039 "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 %} diff --git a/docs/references/http-websocket-apis/peer-port-methods/validator-list.md b/docs/references/http-websocket-apis/peer-port-methods/validator-list.md index 69873f3739c..99a7501fa58 100644 --- a/docs/references/http-websocket-apis/peer-port-methods/validator-list.md +++ b/docs/references/http-websocket-apis/peer-port-methods/validator-list.md @@ -45,7 +45,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/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/misc/detail/Manifest.cpp#L59-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.) diff --git a/docs/references/http-websocket-apis/public-api-methods/account-methods/account_channels.md b/docs/references/http-websocket-apis/public-api-methods/account-methods/account_channels.md index e09a6cf1665..0fefe29dd2e 100644 --- a/docs/references/http-websocket-apis/public-api-methods/account-methods/account_channels.md +++ b/docs/references/http-websocket-apis/public-api-methods/account-methods/account_channels.md @@ -7,7 +7,7 @@ labels: - Payment Channels --- # account_channels -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/AccountChannels.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/AccountChannels.cpp "Source") _(Added by the [PayChan amendment][].)_ diff --git a/docs/references/http-websocket-apis/public-api-methods/account-methods/account_currencies.md b/docs/references/http-websocket-apis/public-api-methods/account-methods/account_currencies.md index 14085db5ddd..3798eaa328d 100644 --- a/docs/references/http-websocket-apis/public-api-methods/account-methods/account_currencies.md +++ b/docs/references/http-websocket-apis/public-api-methods/account-methods/account_currencies.md @@ -7,7 +7,7 @@ labels: - Tokens --- # account_currencies -[[Source]](https://github.com/XRPLF/rippled/blob/df966a9ac6dd986585ecccb206aff24452e41a30/src/ripple/rpc/handlers/AccountCurrencies.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/paths/AccountCurrencies.cpp "Source") The `account_currencies` command retrieves a list of currencies that an account can send or receive, based on its trust lines. (This is not a thoroughly confirmed list, but it can be used to populate user interfaces.) diff --git a/docs/references/http-websocket-apis/public-api-methods/account-methods/account_info.md b/docs/references/http-websocket-apis/public-api-methods/account-methods/account_info.md index 3f462b93895..c125d7c2b25 100644 --- a/docs/references/http-websocket-apis/public-api-methods/account-methods/account_info.md +++ b/docs/references/http-websocket-apis/public-api-methods/account-methods/account_info.md @@ -8,7 +8,7 @@ labels: - XRP --- # account_info -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/AccountInfo.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/AccountInfo.cpp "Source") The `account_info` command retrieves information about an account, its activity, and its XRP balance. All information retrieved is relative to a particular version of the ledger. diff --git a/docs/references/http-websocket-apis/public-api-methods/account-methods/account_lines.md b/docs/references/http-websocket-apis/public-api-methods/account-methods/account_lines.md index 1ff39ac46bf..928d630582f 100644 --- a/docs/references/http-websocket-apis/public-api-methods/account-methods/account_lines.md +++ b/docs/references/http-websocket-apis/public-api-methods/account-methods/account_lines.md @@ -8,7 +8,7 @@ labels: --- # account_lines -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/rpc/handlers/AccountLines.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/AccountLines.cpp "Source") The `account_lines` method returns information about an account's trust lines, which contain balances in all non-XRP currencies and assets. All information retrieved is relative to a particular version of the ledger. diff --git a/docs/references/http-websocket-apis/public-api-methods/account-methods/account_nfts.md b/docs/references/http-websocket-apis/public-api-methods/account-methods/account_nfts.md index 33870f0257a..6915777be0f 100644 --- a/docs/references/http-websocket-apis/public-api-methods/account-methods/account_nfts.md +++ b/docs/references/http-websocket-apis/public-api-methods/account-methods/account_nfts.md @@ -7,7 +7,7 @@ labels: - Non-fungible Tokens, NFTs --- # account_nfts -[[Source]](https://github.com/xrplf/rippled/blob/master/src/ripple/rpc/handlers/AccountObjects.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/AccountObjects.cpp "Source") The `account_nfts` method returns a list of `NFToken` objects for the specified account. diff --git a/docs/references/http-websocket-apis/public-api-methods/account-methods/account_objects.md b/docs/references/http-websocket-apis/public-api-methods/account-methods/account_objects.md index b59a9199016..3c5c7bad07b 100644 --- a/docs/references/http-websocket-apis/public-api-methods/account-methods/account_objects.md +++ b/docs/references/http-websocket-apis/public-api-methods/account-methods/account_objects.md @@ -8,7 +8,7 @@ labels: - Data Retention --- # account_objects -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/AccountObjects.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/AccountObjects.cpp "Source") The `account_objects` command returns the raw [ledger format][] for all ledger entries owned by an account. For a higher-level view of an account's trust lines and balances, see the [account_lines method][] instead. diff --git a/docs/references/http-websocket-apis/public-api-methods/account-methods/account_offers.md b/docs/references/http-websocket-apis/public-api-methods/account-methods/account_offers.md index c866fef3ebf..982bc807bf6 100644 --- a/docs/references/http-websocket-apis/public-api-methods/account-methods/account_offers.md +++ b/docs/references/http-websocket-apis/public-api-methods/account-methods/account_offers.md @@ -7,7 +7,7 @@ labels: - Decentralized Exchange --- # account_offers -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/AccountOffers.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/AccountOffers.cpp "Source") The `account_offers` method retrieves a list of [offers](../../../../concepts/tokens/decentralized-exchange/offers.md) made by a given [account](../../../../concepts/accounts/index.md) that are outstanding as of a particular [ledger version](../../../../concepts/ledgers/index.md). diff --git a/docs/references/http-websocket-apis/public-api-methods/account-methods/account_tx.md b/docs/references/http-websocket-apis/public-api-methods/account-methods/account_tx.md index 8b2aafa4e2e..ca5134821cf 100644 --- a/docs/references/http-websocket-apis/public-api-methods/account-methods/account_tx.md +++ b/docs/references/http-websocket-apis/public-api-methods/account-methods/account_tx.md @@ -8,7 +8,7 @@ labels: - Accounts --- # account_tx -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/AccountTx.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/AccountTx.cpp "Source") The `account_tx` method retrieves a list of validated transactions that involve a given account. diff --git a/docs/references/http-websocket-apis/public-api-methods/account-methods/gateway_balances.md b/docs/references/http-websocket-apis/public-api-methods/account-methods/gateway_balances.md index 1717b0f7622..bab68445530 100644 --- a/docs/references/http-websocket-apis/public-api-methods/account-methods/gateway_balances.md +++ b/docs/references/http-websocket-apis/public-api-methods/account-methods/gateway_balances.md @@ -8,7 +8,7 @@ labels: - Accounts --- # gateway_balances -[[Source]](https://github.com/XRPLF/rippled/blob/9111ad1a9dc37d49d085aa317712625e635197c0/src/ripple/rpc/handlers/GatewayBalances.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/GatewayBalances.cpp "Source") The `gateway_balances` command calculates the total balances issued by a given account, optionally excluding amounts held by [operational addresses](../../../../concepts/accounts/account-types.md). diff --git a/docs/references/http-websocket-apis/public-api-methods/account-methods/noripple_check.md b/docs/references/http-websocket-apis/public-api-methods/account-methods/noripple_check.md index bc796c55079..c47f6861718 100644 --- a/docs/references/http-websocket-apis/public-api-methods/account-methods/noripple_check.md +++ b/docs/references/http-websocket-apis/public-api-methods/account-methods/noripple_check.md @@ -7,7 +7,7 @@ labels: - Tokens --- # noripple_check -[[Source]](https://github.com/XRPLF/rippled/blob/9111ad1a9dc37d49d085aa317712625e635197c0/src/ripple/rpc/handlers/NoRippleCheck.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/NoRippleCheck.cpp "Source") The `noripple_check` command provides a quick way to check the status of [the Default Ripple field for an account and the No Ripple flag of its trust lines](../../../../concepts/tokens/fungible-tokens/rippling.md), compared with the recommended settings. diff --git a/docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger.md b/docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger.md index 56f708d56b8..3b3b906c5f5 100644 --- a/docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger.md +++ b/docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger.md @@ -7,7 +7,7 @@ labels: - Blockchain --- # ledger -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/LedgerHandler.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/LedgerHandler.cpp "Source") Retrieve information about the public [ledger](../../../../concepts/ledgers/index.md). diff --git a/docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_closed.md b/docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_closed.md index 01b489f67fb..768172286a7 100644 --- a/docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_closed.md +++ b/docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_closed.md @@ -7,7 +7,7 @@ labels: - Blockchain --- # ledger_closed -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/LedgerClosed.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/LedgerClosed.cpp "Source") The `ledger_closed` method returns the unique identifiers of the most recently closed ledger. (This ledger is not necessarily validated and immutable yet.) diff --git a/docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_current.md b/docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_current.md index 546a92b4171..1fb56f7b2f9 100644 --- a/docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_current.md +++ b/docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_current.md @@ -7,7 +7,7 @@ labels: - Blockchain --- # ledger_current -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/LedgerCurrent.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/LedgerCurrent.cpp "Source") The `ledger_current` method returns the unique identifiers of the current in-progress [ledger](../../../../concepts/ledgers/index.md). This command is mostly useful for testing, because the ledger returned is still in flux. diff --git a/docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_data.md b/docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_data.md index 9a580b393ee..e201ab32025 100644 --- a/docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_data.md +++ b/docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_data.md @@ -8,7 +8,7 @@ labels: - Data Retention --- # ledger_data -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/LedgerData.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/LedgerData.cpp "Source") The `ledger_data` method retrieves contents of the specified ledger. You can iterate through several calls to retrieve the entire contents of a single ledger version. diff --git a/docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_entry.md b/docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_entry.md index 91ad737e820..ef2bbbaebd3 100644 --- a/docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_entry.md +++ b/docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_entry.md @@ -8,7 +8,7 @@ labels: - Data Retention --- # ledger_entry -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/LedgerEntry.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/LedgerEntry.cpp "Source") The `ledger_entry` method returns a single ledger entry from the XRP Ledger in its raw format. See [ledger format][] for information on the different types of entries you can retrieve. diff --git a/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/amm_info.md b/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/amm_info.md index 0916b98bd3e..3742fe5f544 100644 --- a/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/amm_info.md +++ b/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/amm_info.md @@ -9,7 +9,7 @@ labels: - AMM --- # amm_info -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/AMMInfo.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/AMMInfo.cpp "Source") The {% code-page-name /%} method gets information about an [Automated Market Maker (AMM)](/docs/concepts/tokens/decentralized-exchange/automated-market-makers) instance. diff --git a/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/book_changes.md b/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/book_changes.md index d1511a01219..c487d4cd189 100644 --- a/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/book_changes.md +++ b/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/book_changes.md @@ -6,7 +6,7 @@ labels: - Cross-Currency --- # book_changes -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/BookChanges.h "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/BookChanges.h "Source") The {% code-page-name /%} method reports information about changes to the order books in the [decentralized exchange (DEX)](../../../../concepts/tokens/decentralized-exchange/index.md) compared with the previous ledger version. This may be useful for building "candlestick" charts. diff --git a/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/book_offers.md b/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/book_offers.md index 1c60cdae1e2..299a7278fa1 100644 --- a/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/book_offers.md +++ b/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/book_offers.md @@ -6,7 +6,7 @@ labels: - Cross-Currency --- # book_offers -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/BookOffers.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/BookOffers.cpp "Source") The `book_offers` method retrieves a list of [offers](../../../../concepts/tokens/decentralized-exchange/offers.md) between two currencies, also known as an _order book_. The response omits [unfunded offers](../../../../concepts/tokens/decentralized-exchange/offers.md#lifecycle-of-an-offer) and reports how much of each remaining offer's total is currently funded. diff --git a/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/deposit_authorized.md b/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/deposit_authorized.md index 2f62caabc54..14813a76867 100644 --- a/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/deposit_authorized.md +++ b/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/deposit_authorized.md @@ -6,7 +6,7 @@ labels: - Security --- # deposit_authorized -[[Source]](https://github.com/XRPLF/rippled/blob/817d2339b8632cb2f97d3edd6f7af33aa7631744/src/ripple/rpc/handlers/DepositAuthorized.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/DepositAuthorized.cpp "Source") The `deposit_authorized` command indicates whether one account is authorized to send payments directly to another. See [Deposit Authorization](../../../../concepts/accounts/depositauth.md) for information on how to require authorization to deliver money to your account. diff --git a/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/get_aggregate_price.md b/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/get_aggregate_price.md index c896ba703d6..3321924fff0 100644 --- a/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/get_aggregate_price.md +++ b/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/get_aggregate_price.md @@ -9,7 +9,7 @@ labels: _(Requires the [PriceOracle amendment][])_ -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/GetAggregatePrice.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/GetAggregatePrice.cpp "Source") The `get_aggregate_price` method retrieves the aggregate price of specified `Oracle` objects, returning three price statistics: mean, median, and trimmed mean. diff --git a/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/nft_buy_offers.md b/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/nft_buy_offers.md index a7dcf8f37cb..a872c4006fc 100644 --- a/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/nft_buy_offers.md +++ b/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/nft_buy_offers.md @@ -7,7 +7,7 @@ labels: - Non-fungible Tokens, NFTs, NFTokens --- # nft_buy_offers -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/NFTOffers.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/NFTOffers.cpp "Source") The `nft_buy_offers` method returns a list of buy offers for a given [NFToken][] object. diff --git a/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/nft_sell_offers.md b/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/nft_sell_offers.md index a73786b8046..71adc354285 100644 --- a/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/nft_sell_offers.md +++ b/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/nft_sell_offers.md @@ -7,7 +7,7 @@ labels: - Non-fungible Tokens, NFTs, NFTokens --- # nft_sell_offers -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/NFTOffers.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/NFTOffers.cpp "Source") The `nft_sell_offers` method returns a list of sell offers for a given [NFToken][] object. diff --git a/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/path_find.md b/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/path_find.md index bd8ecce7648..fd117dcf26c 100644 --- a/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/path_find.md +++ b/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/path_find.md @@ -8,7 +8,7 @@ labels: - Tokens --- # path_find -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/PathFind.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/PathFind.cpp "Source") *WebSocket API only!* The `path_find` method searches for a [path](../../../../concepts/tokens/fungible-tokens/paths.md) along which a transaction can possibly be made, and periodically sends updates when the path changes over time. For a simpler version that is supported by JSON-RPC, see the [ripple_path_find method][]. For payments occurring strictly in XRP, it is not necessary to find a path, because XRP can be sent directly to any account. @@ -21,7 +21,7 @@ There are three different modes, or sub-commands, of the path_find command. Spec Although the `rippled` server tries to find the cheapest path or combination of paths for making a payment, it is not guaranteed that the paths returned by this method are, in fact, the best paths. Due to server load, pathfinding may not find the best results. Additionally, you should be careful with the pathfinding results from untrusted servers. A server could be modified to return less-than-optimal paths to earn money for its operators. If you do not have your own server that you can trust with pathfinding, you should compare the results of pathfinding from multiple servers run by different parties, to minimize the risk of a single server returning poor results. (**Note:** A server returning less-than-optimal results is not necessarily proof of malicious behavior; it could also be a symptom of heavy server load.) ## path_find create -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/PathFind.cpp#L50-L56 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/PathFind.cpp#L53-L59 "Source") The `create` sub-command of `path_find` creates an ongoing request to find possible paths along which a payment transaction could be made from one specified account such that another account receives a desired amount of some currency. The initial response contains a suggested path between the two addresses that would result in the desired amount being received. After that, the server sends additional messages, with `"type": "path_find"`, with updates to the potential paths. The frequency of updates is left to the discretion of the server, but it usually means once every few seconds when there is a new ledger version. @@ -500,7 +500,7 @@ Here is an example of an asynchronous follow-up from a path_find create request: {% /tabs %} ## path_find close -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/PathFind.cpp#L58-L67 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/PathFind.cpp#L61-L70 "Source") The `close` sub-command of `path_find` instructs the server to stop sending information about the current open pathfinding request. @@ -545,7 +545,7 @@ If there was no outstanding pathfinding request, an error is returned instead. * `noPathRequest` - You tried to close a pathfinding request when there is not an open one. ## path_find status -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/PathFind.cpp#L69-L77 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/PathFind.cpp#L72-L80 "Source") The `status` sub-command of `path_find` requests an immediate update about the client's currently-open pathfinding request. diff --git a/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/ripple_path_find.md b/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/ripple_path_find.md index 1dc0bf439c5..6f9af5f4422 100644 --- a/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/ripple_path_find.md +++ b/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/ripple_path_find.md @@ -8,7 +8,7 @@ labels: - Tokens --- # ripple_path_find -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/RipplePathFind.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/RipplePathFind.cpp "Source") The `ripple_path_find` method is a simplified version of the [path_find method][] that provides a single response with a [payment path](../../../../concepts/tokens/fungible-tokens/paths.md) you can use right away. It is available in both the WebSocket and JSON-RPC APIs. However, the results tend to become outdated as time passes. Instead of making multiple calls to stay updated, you should instead use the [path_find method][] to subscribe to continued updates where possible. diff --git a/docs/references/http-websocket-apis/public-api-methods/payment-channel-methods/channel_authorize.md b/docs/references/http-websocket-apis/public-api-methods/payment-channel-methods/channel_authorize.md index f057876f24d..dc8b22e045d 100644 --- a/docs/references/http-websocket-apis/public-api-methods/payment-channel-methods/channel_authorize.md +++ b/docs/references/http-websocket-apis/public-api-methods/payment-channel-methods/channel_authorize.md @@ -7,7 +7,7 @@ labels: - Payment Channels --- # channel_authorize -[[Source]](https://github.com/XRPLF/rippled/blob/d4a56f223a3b80f64ff70b4e90ab6792806929ca/src/ripple/rpc/handlers/PayChanClaim.cpp#L41 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/PayChanClaim.cpp#L41 "Source") _(Added by the [PayChan amendment][] to be enabled.)_ diff --git a/docs/references/http-websocket-apis/public-api-methods/payment-channel-methods/channel_verify.md b/docs/references/http-websocket-apis/public-api-methods/payment-channel-methods/channel_verify.md index 9ec605ec349..c2b985d7b61 100644 --- a/docs/references/http-websocket-apis/public-api-methods/payment-channel-methods/channel_verify.md +++ b/docs/references/http-websocket-apis/public-api-methods/payment-channel-methods/channel_verify.md @@ -7,7 +7,7 @@ labels: - Payment Channels --- # channel_verify -[[Source]](https://github.com/XRPLF/rippled/blob/d4a56f223a3b80f64ff70b4e90ab6792806929ca/src/ripple/rpc/handlers/PayChanClaim.cpp#L89 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/PayChanClaim.cpp#L111 "Source") _(Added by the [PayChan amendment][] to be enabled.)_ diff --git a/docs/references/http-websocket-apis/public-api-methods/server-info-methods/feature.md b/docs/references/http-websocket-apis/public-api-methods/server-info-methods/feature.md index f38ff976cbd..458f63940a2 100644 --- a/docs/references/http-websocket-apis/public-api-methods/server-info-methods/feature.md +++ b/docs/references/http-websocket-apis/public-api-methods/server-info-methods/feature.md @@ -10,7 +10,7 @@ labels: # feature -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/rpc/handlers/Feature1.cpp "Source")
+[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/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 if the server knows how to apply the amendments. diff --git a/docs/references/http-websocket-apis/public-api-methods/server-info-methods/fee.md b/docs/references/http-websocket-apis/public-api-methods/server-info-methods/fee.md index b36c6059cb2..e5846635b36 100644 --- a/docs/references/http-websocket-apis/public-api-methods/server-info-methods/fee.md +++ b/docs/references/http-websocket-apis/public-api-methods/server-info-methods/fee.md @@ -7,7 +7,7 @@ labels: - Fees --- # fee -[[Source]](https://github.com/XRPLF/rippled/blob/release/src/ripple/rpc/handlers/Fee1.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/Fee1.cpp "Source") The `fee` command reports the current state of the open-ledger requirements for the [transaction cost](../../../../concepts/transactions/transaction-cost.md). This requires the [FeeEscalation amendment][] to be enabled. diff --git a/docs/references/http-websocket-apis/public-api-methods/server-info-methods/manifest.md b/docs/references/http-websocket-apis/public-api-methods/server-info-methods/manifest.md index 5b741d5324e..c8e247e5c34 100644 --- a/docs/references/http-websocket-apis/public-api-methods/server-info-methods/manifest.md +++ b/docs/references/http-websocket-apis/public-api-methods/server-info-methods/manifest.md @@ -7,7 +7,7 @@ labels: - Blockchain --- # manifest -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/Manifest.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/misc/detail/Manifest.cpp "Source") The {% code-page-name /%} method reports the current "manifest" information for a given validator public key. The "manifest" is a block of data that authorizes an ephemeral signing key with a signature from the validator's master key pair. {% badge href="https://github.com/XRPLF/rippled/releases/tag/1.7.0" %}Updated in: rippled 1.7.0{% /badge %} diff --git 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 index 324843238ee..b7c050f10ae 100644 --- 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 @@ -8,7 +8,7 @@ labels: --- # server_definitions -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/rpc/handlers/ServerInfo.cpp#L42 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/ServerInfo.cpp#L41 "Source") The `server_definitions` command returns an SDK-compatible `definitions.json`, generated from the `rippled` instance currently running. You can use this to query a node in a network, quickly receiving the definitions necessary to serialize/deserialize its binary data. diff --git a/docs/references/http-websocket-apis/public-api-methods/server-info-methods/server_info.md b/docs/references/http-websocket-apis/public-api-methods/server-info-methods/server_info.md index 4f9ac003d6e..350cef28ea2 100644 --- a/docs/references/http-websocket-apis/public-api-methods/server-info-methods/server_info.md +++ b/docs/references/http-websocket-apis/public-api-methods/server-info-methods/server_info.md @@ -7,7 +7,7 @@ labels: - Core Server --- # server_info (rippled) -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/ServerInfo.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/ServerInfo.cpp "Source") The `server_info` command asks the server for a human-readable version of various information about [the `rippled` server](../../../../concepts/networks-and-servers/index.md) being queried. For [Clio servers](../../../../concepts/networks-and-servers/the-clio-server.md), see [`server_info` (Clio)](../clio-methods/server_info-clio.md) instead. diff --git a/docs/references/http-websocket-apis/public-api-methods/server-info-methods/server_state.md b/docs/references/http-websocket-apis/public-api-methods/server-info-methods/server_state.md index 3e5fd8465df..051c4b09917 100644 --- a/docs/references/http-websocket-apis/public-api-methods/server-info-methods/server_state.md +++ b/docs/references/http-websocket-apis/public-api-methods/server-info-methods/server_state.md @@ -8,7 +8,7 @@ labels: --- # server_state -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/ServerState.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/ServerState.cpp "Source") The `server_state` command asks the server for various machine-readable information about the `rippled` server's current state. The response is almost the same as the [server_info method][], but uses units that are easier to process instead of easier to read. (For example, XRP values are given in integer drops instead of scientific notation or decimal values, and time is given in milliseconds instead of seconds.) diff --git a/docs/references/http-websocket-apis/public-api-methods/server-info-methods/version.md b/docs/references/http-websocket-apis/public-api-methods/server-info-methods/version.md index d7e1d9de866..f8f8cd5b23c 100644 --- a/docs/references/http-websocket-apis/public-api-methods/server-info-methods/version.md +++ b/docs/references/http-websocket-apis/public-api-methods/server-info-methods/version.md @@ -6,7 +6,7 @@ labels: --- # version -[[Source]](https://github.com/XRPLF/rippled/blob/develop/src/ripple/beast/core/SemanticVersion.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/libxrpl/beast/core/SemanticVersion.cpp "Source") The `version` command retrieves the API version information for the rippled server. For `Clio` servers, see [`version` (`clio`)](../clio-methods/version.md) instead. diff --git a/docs/references/http-websocket-apis/public-api-methods/subscription-methods/subscribe.md b/docs/references/http-websocket-apis/public-api-methods/subscription-methods/subscribe.md index b592f11ca23..4ef740ffe2e 100644 --- a/docs/references/http-websocket-apis/public-api-methods/subscription-methods/subscribe.md +++ b/docs/references/http-websocket-apis/public-api-methods/subscription-methods/subscribe.md @@ -10,7 +10,7 @@ labels: - Smart Contracts --- # subscribe -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/rpc/handlers/Subscribe.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/Subscribe.cpp "Source") The `subscribe` method requests periodic notifications from the server when certain events happen. diff --git a/docs/references/http-websocket-apis/public-api-methods/subscription-methods/unsubscribe.md b/docs/references/http-websocket-apis/public-api-methods/subscription-methods/unsubscribe.md index 0b0a7eafd88..6bc3407891b 100644 --- a/docs/references/http-websocket-apis/public-api-methods/subscription-methods/unsubscribe.md +++ b/docs/references/http-websocket-apis/public-api-methods/subscription-methods/unsubscribe.md @@ -11,7 +11,7 @@ labels: --- # unsubscribe -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/Unsubscribe.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/Unsubscribe.cpp "Source") The `unsubscribe` command tells the server to stop sending messages for a particular subscription or set of subscriptions. diff --git a/docs/references/http-websocket-apis/public-api-methods/transaction-methods/simulate.md b/docs/references/http-websocket-apis/public-api-methods/transaction-methods/simulate.md index 4f6c20b64ec..5e57e54967a 100644 --- a/docs/references/http-websocket-apis/public-api-methods/transaction-methods/simulate.md +++ b/docs/references/http-websocket-apis/public-api-methods/transaction-methods/simulate.md @@ -5,7 +5,7 @@ labels: - Transaction Sending --- # simulate -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/rpc/handlers/Simulate.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/Simulate.cpp "Source") The `simulate` method executes a dry run of _any_ transaction type, enabling you to preview the results and metadata of a transaction without committing them to the XRP Ledger. Since this command never submits a transaction to the network, it doesn't incur any fees. diff --git a/docs/references/http-websocket-apis/public-api-methods/transaction-methods/submit.md b/docs/references/http-websocket-apis/public-api-methods/transaction-methods/submit.md index 0a0aaf7aed6..aff701ffe96 100644 --- a/docs/references/http-websocket-apis/public-api-methods/transaction-methods/submit.md +++ b/docs/references/http-websocket-apis/public-api-methods/transaction-methods/submit.md @@ -8,7 +8,7 @@ labels: - Payments --- # submit -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/Submit.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/Submit.cpp "Source") The `submit` method applies a [transaction](../../../protocol/transactions/index.md) and sends it to the network to be confirmed and included in future ledgers. diff --git a/docs/references/http-websocket-apis/public-api-methods/transaction-methods/submit_multisigned.md b/docs/references/http-websocket-apis/public-api-methods/transaction-methods/submit_multisigned.md index f27c0c3607b..f1fee91a028 100644 --- a/docs/references/http-websocket-apis/public-api-methods/transaction-methods/submit_multisigned.md +++ b/docs/references/http-websocket-apis/public-api-methods/transaction-methods/submit_multisigned.md @@ -7,7 +7,7 @@ labels: - Transaction Sending --- # submit_multisigned -[[Source]](https://github.com/XRPLF/rippled/blob/release/src/ripple/rpc/handlers/SubmitMultiSigned.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/SubmitMultiSigned.cpp "Source") The `submit_multisigned` command applies a [multi-signed](../../../../concepts/accounts/multi-signing.md) transaction and sends it to the network to be included in future ledgers. (You can also submit multi-signed transactions in binary form using the [`submit` command in submit-only mode](submit.md#submit-only-mode).) diff --git a/docs/references/http-websocket-apis/public-api-methods/transaction-methods/transaction_entry.md b/docs/references/http-websocket-apis/public-api-methods/transaction-methods/transaction_entry.md index 5b6cee92b19..450af3126f4 100644 --- a/docs/references/http-websocket-apis/public-api-methods/transaction-methods/transaction_entry.md +++ b/docs/references/http-websocket-apis/public-api-methods/transaction-methods/transaction_entry.md @@ -7,7 +7,7 @@ labels: - Transaction Sending --- # transaction_entry -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/TransactionEntry.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/TransactionEntry.cpp "Source") The `transaction_entry` method retrieves information on a single transaction from a specific ledger version. (The [tx method][], by contrast, searches all ledgers for the specified transaction. We recommend using that method instead.) diff --git a/docs/references/http-websocket-apis/public-api-methods/transaction-methods/tx.md b/docs/references/http-websocket-apis/public-api-methods/transaction-methods/tx.md index a5835af244b..43b3158dcbb 100644 --- a/docs/references/http-websocket-apis/public-api-methods/transaction-methods/tx.md +++ b/docs/references/http-websocket-apis/public-api-methods/transaction-methods/tx.md @@ -9,7 +9,7 @@ labels: --- # tx -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/Tx.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/Tx.cpp "Source") The `tx` method retrieves information on a single [transaction](../../../protocol/transactions/index.md), by its [identifying hash][] or its [CTID](../../api-conventions/ctid.md). diff --git a/docs/references/http-websocket-apis/public-api-methods/transaction-methods/tx_history.md b/docs/references/http-websocket-apis/public-api-methods/transaction-methods/tx_history.md index e17c527c61f..114c98639cf 100644 --- a/docs/references/http-websocket-apis/public-api-methods/transaction-methods/tx_history.md +++ b/docs/references/http-websocket-apis/public-api-methods/transaction-methods/tx_history.md @@ -5,7 +5,7 @@ seo: description: Retrieve info about all recent transactions. --- # tx_history -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/TxHistory.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/TxHistory.cpp "Source") The `tx_history` method retrieves some of the most recent transactions made. diff --git a/docs/references/http-websocket-apis/public-api-methods/utility-methods/ping.md b/docs/references/http-websocket-apis/public-api-methods/utility-methods/ping.md index c790915926c..32dc71a3f7f 100644 --- a/docs/references/http-websocket-apis/public-api-methods/utility-methods/ping.md +++ b/docs/references/http-websocket-apis/public-api-methods/utility-methods/ping.md @@ -7,7 +7,7 @@ labels: - Core Server --- # ping -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/Ping.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/Ping.cpp "Source") The `ping` command returns an acknowledgement, so that clients can test the connection status and latency. diff --git a/docs/references/http-websocket-apis/public-api-methods/utility-methods/random.md b/docs/references/http-websocket-apis/public-api-methods/utility-methods/random.md index 77672631ac3..f364763178c 100644 --- a/docs/references/http-websocket-apis/public-api-methods/utility-methods/random.md +++ b/docs/references/http-websocket-apis/public-api-methods/utility-methods/random.md @@ -8,7 +8,7 @@ labels: --- # random -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/Random.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/rpc/handlers/Random.cpp "Source") The `random` command provides a random number to be used as a source of entropy for random number generation by clients. diff --git a/docs/references/protocol/binary-format.md b/docs/references/protocol/binary-format.md index 6efb50805cd..e659b31df81 100644 --- a/docs/references/protocol/binary-format.md +++ b/docs/references/protocol/binary-format.md @@ -15,7 +15,7 @@ curated_anchors: anchor: "#type-list" --- # Binary Format -[[Source]](https://github.com/XRPLF/rippled/blob/develop/include/xrpl/protocol/SField.h "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/SField.h "Source") This page describes the XRP Ledger's canonical binary format for transactions and other data. This binary format is necessary to create and verify digital signatures of those transactions' contents, and is also used in other places including in the [peer-to-peer communications between servers](../../concepts/networks-and-servers/peer-protocol.md). The [`rippled` APIs](../http-websocket-apis/index.md) typically use JSON to communicate with client applications. However, JSON is unsuitable as a format for serializing transactions for being digitally signed, because JSON can represent the same data in many different but equivalent ways. @@ -55,7 +55,7 @@ Both signed and unsigned transactions can be represented in both JSON and binary The serialization processes described here are implemented in multiple places and programming languages: -- In C++ [in the `rippled` code base](https://github.com/XRPLF/rippled/blob/develop/src/ripple/protocol/impl/STObject.cpp). +- In C++ [in the `rippled` code base](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/libxrpl/protocol/STObject.cpp). - In JavaScript in {% repo-link path="_code-samples/tx-serialization/" %}this repository's code samples section{% /repo-link %}. - In Python 3 in {% repo-link path="_code-samples/tx-serialization/" %}this repository's code samples section{% /repo-link %}. @@ -65,7 +65,7 @@ Additionally, many [client libraries](../client-libraries.md) provide serializat ## Internal Format -Each field has an canonical binary format, or _internal format_ used in the XRP Ledger protocol to represent that field in transactions and ledger data. The binary format is needed for signing, but it is also used in peer-to-peer communications, in ledger storage, and in other places. The binary formats for all fields are defined in the source code of [`SField.h`](https://github.com/XRPLF/rippled/blob/develop/include/xrpl/protocol/SField.h). The JSON format for transactions and ledger data is standardized for convenience, but JSON is only used in APIs and client libraries: strictly speaking, only the binary format exists at the level of the XRP Ledger protocol. +Each field has an canonical binary format, or _internal format_ used in the XRP Ledger protocol to represent that field in transactions and ledger data. The binary format is needed for signing, but it is also used in peer-to-peer communications, in ledger storage, and in other places. The binary formats for all fields are defined in the source code of [`SField.h`](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/SField.h). The JSON format for transactions and ledger data is standardized for convenience, but JSON is only used in APIs and client libraries: strictly speaking, only the binary format exists at the level of the XRP Ledger protocol. The [Transaction Format Reference](transactions/index.md) and [Ledger Data Reference](ledger-data/index.md) list both the JSON and the internal (binary) formats for all fields. For example, the `Flags` [common transaction field](transactions/common-fields.md) is a Number in JSON and a UInt32 in binary. Even though the JSON representation uses a data type that can contain decimal places or very large values, the field is limited to values that can be represented as a 32-bit unsigned integer. @@ -101,8 +101,8 @@ The field definition objects in the `FIELDS` array have the following fields: ### Field IDs -[[Source - Encoding]](https://github.com/XRPLF/rippled/blob/edb4f0342c65bd739fee60b74566f3e771134c6c/src/libxrpl/protocol/Serializer.cpp#L120-L153 "Source") -[[Source - Decoding]](https://github.com/XRPLF/rippled/blob/edb4f0342c65bd739fee60b74566f3e771134c6c/src/libxrpl/protocol/Serializer.cpp#L429-L452 "Source") +[[Source - Encoding]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/libxrpl/protocol/Serializer.cpp#L120-L153 "Source") +[[Source - Decoding]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/libxrpl/protocol/Serializer.cpp#L429-L452 "Source") When you combine a field's type code and field code, you get the field's unique identifier, which is prefixed before the field in the final serialized blob. The size of the Field ID is one to three bytes depending on the type code and field codes it combines. See the following table: @@ -157,17 +157,17 @@ All fields in a transaction are sorted in a specific order based first on the fi ### Type Codes -Each field type has an arbitrary type code, with lower codes sorting first. These codes are defined in [`SField.h`](https://github.com/XRPLF/rippled/blob/master/include/xrpl/protocol/SField.h#L60-L98). +Each field type has an arbitrary type code, with lower codes sorting first. These codes are defined in [`SField.h`](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/SField.h#L60-L98). -For example, [UInt32 has type code 2](https://github.com/XRPLF/rippled/blob/master/include/xrpl/protocol/SField.h#L67), so all UInt32 fields come before all [Amount fields, which have type code 6](https://github.com/XRPLF/rippled/blob/master/include/xrpl/protocol/SField.h#L71). +For example, [UInt32 has type code 2](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/SField.h#L67), so all UInt32 fields come before all [Amount fields, which have type code 6](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/SField.h#L71). The [definitions file](#definitions-file) lists the type codes for each type in the `TYPES` map. ### Field Codes -Each field has a field code, which is used to sort fields that have the same type as one another, with lower codes sorting first. These fields are defined in [`sfields.macro`](https://github.com/XRPLF/rippled/blob/master/include/xrpl/protocol/detail/sfields.macro). +Each field has a field code, which is used to sort fields that have the same type as one another, with lower codes sorting first. These fields are defined in [`sfields.macro`](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/detail/sfields.macro). -For example, the `Account` field of a [Payment transaction][] [has sort code 1](https://github.com/XRPLF/rippled/blob/master/include/xrpl/protocol/detail/sfields.macro#L269), so it comes before the `Destination` field which [has sort code 3](https://github.com/XRPLF/rippled/blob/master/include/xrpl/protocol/detail/sfields.macro#L271). +For example, the `Account` field of a [Payment transaction][] [has sort code 1](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/detail/sfields.macro#L269), so it comes before the `Destination` field which [has sort code 3](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/detail/sfields.macro#L271). Field codes are reused for fields of different field types, but fields of the same type never have the same field code. When you combine the type code with the field code, you get the field's unique [Field ID](#field-ids). @@ -265,7 +265,7 @@ The following diagram shows the serialization formats for all three amount forma [{% inline-svg file="/docs/img/serialization-amount.svg" /%}](/docs/img/serialization-amount.svg 'The first bit is an amount type bit (0 = XRP or MPT, 1 = fungible token). XRP has a sign bit (always 1 for positive), an MPT indicator bit (0=XRP) and 61 bits of precision. MPTs have a sign bit (always 1 for positive), an MPT indicator bit (1=MPT), 5 reserved bits, 64 bit integer quantity, and a 192 bit MPT Issuance ID which consists of the 32-bit Sequence number followed by 160-bit issuer AccountID. Fungible Token amounts consist start with an amount type bit of 1, a sign bit which can be 1 or 0, an exponent (8 bits), significant digits (54 bits), currency code (160 bits), and issuer (160 bits).') #### Token Amount Format -[[Source]](https://github.com/XRPLF/rippled/blob/35fa20a110e3d43ffc1e9e664fc9017b6f2747ae/src/ripple/protocol/impl/STAmount.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/libxrpl/protocol/STAmount.cpp "Source") [{% inline-svg file="/docs/img/currency-number-format.svg" /%}](/docs/img/currency-number-format.svg "Token Amount Format diagram") @@ -354,12 +354,12 @@ The following example shows the serialization format for an object (a single `Me The `Paths` field of a cross-currency [Payment transaction][] is a "PathSet", represented in JSON as an array of arrays. For more information on what paths are used for, see [Paths](../../concepts/tokens/fungible-tokens/paths.md). -A PathSet is serialized as **1 to 6** individual paths in sequence[[Source]](https://github.com/XRPLF/rippled/blob/4cff94f7a4a05302bdf1a248515379da99c5bcd4/src/ripple/app/tx/impl/Payment.h#L35-L36 "Source"). Each complete path is followed by a byte that indicates what comes next: +A PathSet is serialized as **1 to 6** individual paths in sequence[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/Payment.h#L29-L30 "Source"). Each complete path is followed by a byte that indicates what comes next: - `0xff` indicates another path follows - `0x00` indicates the end of the PathSet -Each path consists of **1 to 8** path steps in order[[Source]](https://github.com/XRPLF/rippled/blob/4cff94f7a4a05302bdf1a248515379da99c5bcd4/src/ripple/app/tx/impl/Payment.h#L38-L39 "Source"). Each step starts with a **type** byte, followed by one or more fields describing the path step. The type indicates which fields are present in that path step through bitwise flags. (For example, the value `0x30` indicates changing both currency and issuer.) If more than one field is present, the fields are always placed in a specific order. +Each path consists of **1 to 8** path steps in order[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/Payment.h#L38-L39 "Source"). Each step starts with a **type** byte, followed by one or more fields describing the path step. The type indicates which fields are present in that path step through bitwise flags. (For example, the value `0x30` indicates changing both currency and issuer.) If more than one field is present, the fields are always placed in a specific order. The following table describes the possible fields and the bitwise flags to set in the type byte to indicate them: diff --git a/docs/references/protocol/data-types/basic-data-types.md b/docs/references/protocol/data-types/basic-data-types.md index f28b6023e1c..8e57bc59881 100644 --- a/docs/references/protocol/data-types/basic-data-types.md +++ b/docs/references/protocol/data-types/basic-data-types.md @@ -28,7 +28,7 @@ Each closed [Ledger](../ledger-data/index.md) has a [Ledger Index][] and a [Hash ### Hash Prefixes -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/HashPrefix.h "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/HashPrefix.h "Source") In many cases, the XRP Ledger prefixes an object's binary data with a 4-byte code before calculating its hash, so that objects of different types have different hashes even if their binary formats are the same. The existing 4-byte codes are structured as three alphabetic characters, encoded as ASCII, followed by a zero byte. diff --git a/docs/references/protocol/ledger-data/common-fields.md b/docs/references/protocol/ledger-data/common-fields.md index bc4d17fceba..940b6cfa5e3 100644 --- a/docs/references/protocol/ledger-data/common-fields.md +++ b/docs/references/protocol/ledger-data/common-fields.md @@ -4,7 +4,7 @@ seo: description: These common fields are part of every ledger entry. --- # Ledger Entry Common Fields -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/impl/LedgerFormats.cpp) +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/libxrpl/protocol/LedgerFormats.cpp) Every entry in a [ledger](../../../concepts/ledgers/index.md)'s state data has the same set of common fields, plus additional fields based on the [ledger entry type](ledger-entry-types/index.md). Field names are case-sensitive. The common fields for all ledger entries are: @@ -19,9 +19,9 @@ Every entry in a [ledger](../../../concepts/ledgers/index.md)'s state data has t ## Ledger Entry ID -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/impl/Indexes.cpp) +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/libxrpl/protocol/Indexes.cpp) -Each ledger entry has a unique ID. The ID is derived by hashing important contents of the entry, along with a [namespace identifier](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/LedgerFormats.h). The [ledger entry type](ledger-entry-types/index.md) determines the namespace identifier to use and which contents to include in the hash. This ensures every ID is unique. The hash function is [SHA-512Half][]. +Each ledger entry has a unique ID. The ID is derived by hashing important contents of the entry, along with a [namespace identifier](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/LedgerFormats.h). The [ledger entry type](ledger-entry-types/index.md) determines the namespace identifier to use and which contents to include in the hash. This ensures every ID is unique. The hash function is [SHA-512Half][]. Generally, a ledger entry's ID is returned as the `index` field in JSON, at the same level as the object's contents. In [transaction metadata](../transactions/metadata.md), the ledger object's ID in JSON is `LedgerIndex`. diff --git a/docs/references/protocol/ledger-data/ledger-entry-types/accountroot.md b/docs/references/protocol/ledger-data/ledger-entry-types/accountroot.md index 66616ba75f3..600d3c515d6 100644 --- a/docs/references/protocol/ledger-data/ledger-entry-types/accountroot.md +++ b/docs/references/protocol/ledger-data/ledger-entry-types/accountroot.md @@ -6,7 +6,7 @@ labels: - XRP --- # AccountRoot -[[Source]](https://github.com/XRPLF/rippled/blob/f64cf9187affd69650907d0d92e097eb29693945/include/xrpl/protocol/detail/ledger_entries.macro#L136-L158 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/detail/ledger_entries.macro#L147-L170 "Source") An `AccountRoot` ledger entry type describes a single [account](../../../../concepts/accounts/index.md), its settings, and XRP balance. You can create a new account by sending a [Payment transaction][] with enough XRP to a mathematically-valid address. diff --git a/docs/references/protocol/ledger-data/ledger-entry-types/amendments.md b/docs/references/protocol/ledger-data/ledger-entry-types/amendments.md index e5f119600f9..edfd6f352fa 100644 --- a/docs/references/protocol/ledger-data/ledger-entry-types/amendments.md +++ b/docs/references/protocol/ledger-data/ledger-entry-types/amendments.md @@ -5,7 +5,7 @@ labels: - Blockchain --- # Amendments -[[Source]](https://github.com/XRPLF/rippled/blob/f64cf9187affd69650907d0d92e097eb29693945/include/xrpl/protocol/detail/ledger_entries.macro#L187-L192 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/detail/ledger_entries.macro#L200-L205 "Source") The `Amendments` ledger entry type contains a list of [Amendments](../../../../concepts/networks-and-servers/amendments.md) that are currently active. Each ledger version contains **at most one** `Amendments` entry. diff --git a/docs/references/protocol/ledger-data/ledger-entry-types/amm.md b/docs/references/protocol/ledger-data/ledger-entry-types/amm.md index 5c89e903257..b2c37ea3829 100644 --- a/docs/references/protocol/ledger-data/ledger-entry-types/amm.md +++ b/docs/references/protocol/ledger-data/ledger-entry-types/amm.md @@ -5,7 +5,7 @@ labels: - AMM --- # AMM -[[Source]](https://github.com/XRPLF/rippled/blob/f64cf9187affd69650907d0d92e097eb29693945/include/xrpl/protocol/detail/ledger_entries.macro#L369-L380 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/detail/ledger_entries.macro#L386-L397 "Source") An `AMM` ledger entry describes a single [Automated Market Maker](../../../../concepts/tokens/decentralized-exchange/automated-market-makers.md) (AMM) instance. This is always paired with a [special AccountRoot entry](accountroot.md#special-amm-accountroot-entries). You can create an AMM by sending an [AMMCreate transaction][]. diff --git a/docs/references/protocol/ledger-data/ledger-entry-types/bridge.md b/docs/references/protocol/ledger-data/ledger-entry-types/bridge.md index 74456f234be..1f1a57423ec 100644 --- a/docs/references/protocol/ledger-data/ledger-entry-types/bridge.md +++ b/docs/references/protocol/ledger-data/ledger-entry-types/bridge.md @@ -6,7 +6,7 @@ labels: status: not_enabled --- # Bridge -[[Source]](https://github.com/XRPLF/rippled/blob/f64cf9187affd69650907d0d92e097eb29693945/include/xrpl/protocol/detail/ledger_entries.macro#L212-L223 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/detail/ledger_entries.macro#L225-L236 "Source") The `Bridge` ledger entry represents a single cross-chain bridge that connects the XRP Ledger with another blockchain, such as its sidechain, and enables value in the form of XRP and other tokens (IOUs) to move efficiently between the two blockchains. You can create a bridge by sending an [XChainCreateBridge transaction][]. diff --git a/docs/references/protocol/ledger-data/ledger-entry-types/check.md b/docs/references/protocol/ledger-data/ledger-entry-types/check.md index 57e5e8ba655..c43f8847940 100644 --- a/docs/references/protocol/ledger-data/ledger-entry-types/check.md +++ b/docs/references/protocol/ledger-data/ledger-entry-types/check.md @@ -5,7 +5,7 @@ labels: - Checks --- # Check -[[Source]](https://github.com/XRPLF/rippled/blob/f64cf9187affd69650907d0d92e097eb29693945/include/xrpl/protocol/detail/ledger_entries.macro#L50-L63 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/detail/ledger_entries.macro#L61-L74 "Source") A `Check` entry describes a [check](../../../../concepts/payment-types/checks.md), similar to a paper personal check, which can be cashed by its destination to get money from its sender. You can create a check by sending a [CheckCreate transaction][]. @@ -64,7 +64,7 @@ There are no flags defined for {% code-page-name /%} entries. ## Check ID Format -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/impl/Indexes.cpp#L193-L200 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/libxrpl/protocol/Indexes.cpp#L195-L201 "Source") The ID of a `Check` entry is the [SHA-512Half][] of the following values, concatenated in order: diff --git a/docs/references/protocol/ledger-data/ledger-entry-types/depositpreauth.md b/docs/references/protocol/ledger-data/ledger-entry-types/depositpreauth.md index 169f0204231..68a7155db94 100644 --- a/docs/references/protocol/ledger-data/ledger-entry-types/depositpreauth.md +++ b/docs/references/protocol/ledger-data/ledger-entry-types/depositpreauth.md @@ -5,7 +5,7 @@ labels: - Security --- # DepositPreauth -[[Source]](https://github.com/XRPLF/rippled/blob/f64cf9187affd69650907d0d92e097eb29693945/include/xrpl/protocol/detail/ledger_entries.macro#L246-L253 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/detail/ledger_entries.macro#L261-L268 "Source") A `DepositPreauth` entry tracks a preauthorization from one account. You can create a preauthorization by sending a [DepositPreauth transaction][], but it has no effect unless you are using [Deposit Authorization](../../../../concepts/accounts/depositauth.md). diff --git a/docs/references/protocol/ledger-data/ledger-entry-types/did.md b/docs/references/protocol/ledger-data/ledger-entry-types/did.md index e79a529dab1..5b05845ac75 100644 --- a/docs/references/protocol/ledger-data/ledger-entry-types/did.md +++ b/docs/references/protocol/ledger-data/ledger-entry-types/did.md @@ -5,7 +5,7 @@ labels: - DID --- # DID -[[Source]](https://github.com/XRPLF/rippled/blob/f64cf9187affd69650907d0d92e097eb29693945/include/xrpl/protocol/detail/ledger_entries.macro#L69-L77 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/detail/ledger_entries.macro#L80-L88 "Source") A `DID` ledger entry holds references to, or data associated with, a single [Decentralized Identifier (DID)](../../../../concepts/decentralized-storage/decentralized-identifiers.md). You can create or modify a DID by sending a [DIDSet transaction][]. diff --git a/docs/references/protocol/ledger-data/ledger-entry-types/directorynode.md b/docs/references/protocol/ledger-data/ledger-entry-types/directorynode.md index 671c5b64c7e..f5afda5bb36 100644 --- a/docs/references/protocol/ledger-data/ledger-entry-types/directorynode.md +++ b/docs/references/protocol/ledger-data/ledger-entry-types/directorynode.md @@ -6,7 +6,7 @@ labels: - Decentralized Exchange --- # DirectoryNode -[[Source]](https://github.com/XRPLF/rippled/blob/7e24adbdd0b61fb50967c4c6d4b27cc6d81b33f3/include/xrpl/protocol/detail/ledger_entries.macro#L177-L192 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/detail/ledger_entries.macro#L177-L192 "Source") The `DirectoryNode` ledger entry type provides a list of links to other entries in the ledger's state data. A single conceptual _Directory_ takes the form of a doubly linked list, with one or more DirectoryNode entries each containing up to 32 [IDs of other entries](../common-fields.md). The first DirectoryNode entry is called the root of the directory, and all entries other than the root can be added or deleted as necessary. diff --git a/docs/references/protocol/ledger-data/ledger-entry-types/escrow.md b/docs/references/protocol/ledger-data/ledger-entry-types/escrow.md index 99f9a421254..f7633405221 100644 --- a/docs/references/protocol/ledger-data/ledger-entry-types/escrow.md +++ b/docs/references/protocol/ledger-data/ledger-entry-types/escrow.md @@ -5,7 +5,7 @@ labels: - Escrow --- # Escrow -[[Source]](https://github.com/XRPLF/rippled/blob/f64cf9187affd69650907d0d92e097eb29693945/include/xrpl/protocol/detail/ledger_entries.macro#L329-L342 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/detail/ledger_entries.macro#L344-L359 "Source") An `Escrow` ledger entry represents an [escrow](../../../../concepts/payment-types/escrow.md), which holds XRP until specific conditions are met. You can create an escrow by sending an [EscrowCreate transaction][]. diff --git a/docs/references/protocol/ledger-data/ledger-entry-types/feesettings.md b/docs/references/protocol/ledger-data/ledger-entry-types/feesettings.md index 869dbbef320..35d2b77b3c2 100644 --- a/docs/references/protocol/ledger-data/ledger-entry-types/feesettings.md +++ b/docs/references/protocol/ledger-data/ledger-entry-types/feesettings.md @@ -5,7 +5,7 @@ labels: - Fees --- # FeeSettings -[[Source]](https://github.com/XRPLF/rippled/blob/f64cf9187affd69650907d0d92e097eb29693945/include/xrpl/protocol/detail/ledger_entries.macro#L297-L309 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/detail/ledger_entries.macro#L312-L324 "Source") The `FeeSettings` entry contains the current base [transaction cost](../../../../concepts/transactions/transaction-cost.md) and [reserve amounts](../../../../concepts/accounts/reserves.md) as determined by [fee voting](../../../../concepts/consensus-protocol/fee-voting.md). Each ledger version contains **at most one** `FeeSettings` entry. diff --git a/docs/references/protocol/ledger-data/ledger-entry-types/ledgerhashes.md b/docs/references/protocol/ledger-data/ledger-entry-types/ledgerhashes.md index 074ab3f8044..ebfa1934495 100644 --- a/docs/references/protocol/ledger-data/ledger-entry-types/ledgerhashes.md +++ b/docs/references/protocol/ledger-data/ledger-entry-types/ledgerhashes.md @@ -5,7 +5,7 @@ labels: - Blockchain --- # LedgerHashes -[[Source]](https://github.com/XRPLF/rippled/blob/f64cf9187affd69650907d0d92e097eb29693945/include/xrpl/protocol/detail/ledger_entries.macro#L202-L206 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/detail/ledger_entries.macro#L215-L219 "Source") (Not to be confused with the ["ledger hash" string data type][Hash], which uniquely identifies a ledger version. This page describes the `LedgerHashes` ledger entry type.) @@ -72,7 +72,7 @@ There are no flags defined for {% code-page-name /%} entries. ## LedgerHashes ID Formats -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/impl/Indexes.cpp#L26-L42) +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/libxrpl/protocol/Indexes.cpp#L195-L201) There are two formats for `LedgerHashes` ledger entry IDs, depending on whether the entry is a "recent history" sub-type or a "previous history" sub-type. diff --git a/docs/references/protocol/ledger-data/ledger-entry-types/negativeunl.md b/docs/references/protocol/ledger-data/ledger-entry-types/negativeunl.md index 6ad068e2599..229658a4b29 100644 --- a/docs/references/protocol/ledger-data/ledger-entry-types/negativeunl.md +++ b/docs/references/protocol/ledger-data/ledger-entry-types/negativeunl.md @@ -5,7 +5,7 @@ labels: - Blockchain --- # NegativeUNL -[[Source]](https://github.com/XRPLF/rippled/blob/f64cf9187affd69650907d0d92e097eb29693945/include/xrpl/protocol/detail/ledger_entries.macro#L85-L91 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/detail/ledger_entries.macro#L96-L102 "Source") _(Added by the [NegativeUNL amendment][].)_ diff --git a/docs/references/protocol/ledger-data/ledger-entry-types/nftokenoffer.md b/docs/references/protocol/ledger-data/ledger-entry-types/nftokenoffer.md index eaf9cabc2c9..ccf63b99309 100644 --- a/docs/references/protocol/ledger-data/ledger-entry-types/nftokenoffer.md +++ b/docs/references/protocol/ledger-data/ledger-entry-types/nftokenoffer.md @@ -5,7 +5,7 @@ labels: - Non-fungible Tokens, NFTs --- # NFTokenOffer -[[Source]](https://github.com/XRPLF/rippled/blob/f64cf9187affd69650907d0d92e097eb29693945/include/xrpl/protocol/detail/ledger_entries.macro#L34-L44 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/detail/ledger_entries.macro#L45-L55 "Source") An `NFTokenOffer` entry represents an offer to buy, sell or transfer an [NFT](../../../../concepts/tokens/nfts/index.md). You can create an NFT buy or sell offer by sending an [NFTokenCreateOffer transaction][]. diff --git a/docs/references/protocol/ledger-data/ledger-entry-types/nftokenpage.md b/docs/references/protocol/ledger-data/ledger-entry-types/nftokenpage.md index 22bd0f87730..f0020470521 100644 --- a/docs/references/protocol/ledger-data/ledger-entry-types/nftokenpage.md +++ b/docs/references/protocol/ledger-data/ledger-entry-types/nftokenpage.md @@ -5,7 +5,7 @@ labels: - Non-fungible Tokens, NFTs --- # NFTokenPage -[[Source]](https://github.com/XRPLF/rippled/blob/f64cf9187affd69650907d0d92e097eb29693945/include/xrpl/protocol/detail/ledger_entries.macro#L97-L103 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/detail/ledger_entries.macro#L108-L114 "Source") An `NFTokenPage` entry represents a collection of [NFTs](../../../../concepts/tokens/nfts/index.md) owned by the same account. An account can have multiple `NFTokenPage` entries, which form a doubly linked list. NFT directories are automatically updated when an account mints, burns, buys, or sells NFTs. diff --git a/docs/references/protocol/ledger-data/ledger-entry-types/offer.md b/docs/references/protocol/ledger-data/ledger-entry-types/offer.md index 51cdabfd32b..cba11c132eb 100644 --- a/docs/references/protocol/ledger-data/ledger-entry-types/offer.md +++ b/docs/references/protocol/ledger-data/ledger-entry-types/offer.md @@ -5,7 +5,7 @@ labels: - Decentralized Exchange --- # Offer -[[Source]](https://github.com/XRPLF/rippled/blob/7e24adbdd0b61fb50967c4c6d4b27cc6d81b33f3/include/xrpl/protocol/detail/ledger_entries.macro#L242-L255 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/detail/ledger_entries.macro#L242-L255 "Source") An `Offer` ledger entry describes an [offer](../../../../concepts/tokens/decentralized-exchange/offers.md) to exchange currencies in the XRP Ledger's [decentralized exchange](../../../../concepts/tokens/decentralized-exchange/index.md). (In finance, this is more traditionally known as an _order_.) You an create a new offer entry by sending an [OfferCreate transaction][] that is not fully executed immediately. diff --git a/docs/references/protocol/ledger-data/ledger-entry-types/oracle.md b/docs/references/protocol/ledger-data/ledger-entry-types/oracle.md index 44325f5d17e..6a0b2c20875 100644 --- a/docs/references/protocol/ledger-data/ledger-entry-types/oracle.md +++ b/docs/references/protocol/ledger-data/ledger-entry-types/oracle.md @@ -5,7 +5,7 @@ labels: - Decentralized Exchange --- # Oracle -[[Source]](https://github.com/XRPLF/rippled/blob/f64cf9187affd69650907d0d92e097eb29693945/include/xrpl/protocol/detail/ledger_entries.macro#L385-L395 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/detail/ledger_entries.macro#L385-L395 "Source") An `Oracle` ledger entry holds data associated with a single [price oracle](../../../../concepts/decentralized-storage/price-oracles.md), which can store information on up to 10 asset pairs. You can create or modify a price oracle with an [OracleSet transaction][]. diff --git a/docs/references/protocol/ledger-data/ledger-entry-types/paychannel.md b/docs/references/protocol/ledger-data/ledger-entry-types/paychannel.md index b129e3ffe03..0ac7eb6293e 100644 --- a/docs/references/protocol/ledger-data/ledger-entry-types/paychannel.md +++ b/docs/references/protocol/ledger-data/ledger-entry-types/paychannel.md @@ -5,7 +5,7 @@ labels: - Payment Channels --- # PayChannel -[[Source]](https://github.com/XRPLF/rippled/blob/f64cf9187affd69650907d0d92e097eb29693945/include/xrpl/protocol/detail/ledger_entries.macro#L348-L363 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/detail/ledger_entries.macro#L365-L380 "Source") A `PayChannel` entry represents a [payment channel](../../../../concepts/payment-types/payment-channels.md). You can create a payment channel with a [PaymentChannelCreate transaction][]. diff --git a/docs/references/protocol/ledger-data/ledger-entry-types/permissioneddomain.md b/docs/references/protocol/ledger-data/ledger-entry-types/permissioneddomain.md index ab451f19a62..8f74058186e 100644 --- a/docs/references/protocol/ledger-data/ledger-entry-types/permissioneddomain.md +++ b/docs/references/protocol/ledger-data/ledger-entry-types/permissioneddomain.md @@ -6,7 +6,7 @@ labels: - Permissioned Domains --- # PermissionedDomain -[[Source]](https://github.com/XRPLF/rippled/blob/master/include/xrpl/protocol/detail/ledger_entries.macro#L451-L461 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/detail/ledger_entries.macro#L463-L470 "Source") A `PermissionedDomain` ledger entry describes a single [permissioned domain][] instance. You can create a permissioned domain by sending a [PermissionedDomainSet transaction][]. diff --git a/docs/references/protocol/ledger-data/ledger-entry-types/ripplestate.md b/docs/references/protocol/ledger-data/ledger-entry-types/ripplestate.md index 85afdb7fcbc..0a2d5fab0f6 100644 --- a/docs/references/protocol/ledger-data/ledger-entry-types/ripplestate.md +++ b/docs/references/protocol/ledger-data/ledger-entry-types/ripplestate.md @@ -5,7 +5,7 @@ labels: - Tokens --- # RippleState -[[Source]](https://github.com/XRPLF/rippled/blob/f64cf9187affd69650907d0d92e097eb29693945/include/xrpl/protocol/detail/ledger_entries.macro#L277-L289 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/detail/ledger_entries.macro#L292-L304 "Source") A `RippleState` ledger entry represents a [trust line](../../../../concepts/tokens/fungible-tokens/index.md) between two accounts. Each account can change its own limit and other settings, but the balance is a single shared value. A trust line that is entirely in its default state is considered the same as a trust line that does not exist and is automatically deleted. You can create or modify a trust line with a [TrustSet transaction][]. diff --git a/docs/references/protocol/ledger-data/ledger-entry-types/signerlist.md b/docs/references/protocol/ledger-data/ledger-entry-types/signerlist.md index acce6a35afc..b31af06d1ee 100644 --- a/docs/references/protocol/ledger-data/ledger-entry-types/signerlist.md +++ b/docs/references/protocol/ledger-data/ledger-entry-types/signerlist.md @@ -5,7 +5,7 @@ labels: - Security --- # SignerList -[[Source]](https://github.com/XRPLF/rippled/blob/f64cf9187affd69650907d0d92e097eb29693945/include/xrpl/protocol/detail/ledger_entries.macro#L111-L118 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/detail/ledger_entries.macro#L122-L129 "Source") A `SignerList` entry represents a list of parties that, as a group, are authorized to sign a transaction in place of an individual account by [multi-signing](../../../../concepts/accounts/multi-signing.md). You can create, replace, or remove a signer list using a [SignerListSet transaction][]. diff --git a/docs/references/protocol/ledger-data/ledger-entry-types/ticket.md b/docs/references/protocol/ledger-data/ledger-entry-types/ticket.md index fdb6cbd34ba..d3defecdc12 100644 --- a/docs/references/protocol/ledger-data/ledger-entry-types/ticket.md +++ b/docs/references/protocol/ledger-data/ledger-entry-types/ticket.md @@ -7,7 +7,7 @@ labels: - Transaction Sending --- # Ticket -[[Source]](https://github.com/XRPLF/rippled/blob/f64cf9187affd69650907d0d92e097eb29693945/include/xrpl/protocol/detail/ledger_entries.macro#L124-L130 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/detail/ledger_entries.macro#L135-L141 "Source") A `Ticket` entry type represents a [Ticket](../../../../concepts/accounts/tickets.md), which tracks an account [sequence number][Sequence Number] that has been set aside for future use. You can create new tickets with a [TicketCreate transaction][]. diff --git a/docs/references/protocol/ledger-data/ledger-entry-types/xchainownedclaimid.md b/docs/references/protocol/ledger-data/ledger-entry-types/xchainownedclaimid.md index 88d7c82b11a..ab676a4a885 100644 --- a/docs/references/protocol/ledger-data/ledger-entry-types/xchainownedclaimid.md +++ b/docs/references/protocol/ledger-data/ledger-entry-types/xchainownedclaimid.md @@ -6,7 +6,7 @@ labels: status: not_enabled --- # XChainOwnedClaimID -[[Source]](https://github.com/XRPLF/rippled/blob/f64cf9187affd69650907d0d92e097eb29693945/include/xrpl/protocol/detail/ledger_entries.macro#L259-L269 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/detail/ledger_entries.macro#L274-L284 "Source") An `XChainOwnedClaimID` entry represents *one* cross-chain transfer of value and includes information of the account on the source chain that locks or burns the funds on the source chain. diff --git a/docs/references/protocol/ledger-data/ledger-entry-types/xchainownedcreateaccountclaimid.md b/docs/references/protocol/ledger-data/ledger-entry-types/xchainownedcreateaccountclaimid.md index 0559a0425d7..2f298da2e74 100644 --- a/docs/references/protocol/ledger-data/ledger-entry-types/xchainownedcreateaccountclaimid.md +++ b/docs/references/protocol/ledger-data/ledger-entry-types/xchainownedcreateaccountclaimid.md @@ -6,7 +6,7 @@ labels: status: not_enabled --- # XChainOwnedCreateAccountClaimID -[[Source]](https://github.com/XRPLF/rippled/blob/f64cf9187affd69650907d0d92e097eb29693945/include/xrpl/protocol/detail/ledger_entries.macro#L315-L323 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/detail/ledger_entries.macro#L330-L338 "Source") An `XChainOwnedCreateAccountClaimID` ledger entry collects attestations for creating an account via a cross-chain transfer. diff --git a/docs/references/protocol/ledger-data/ledger-header.md b/docs/references/protocol/ledger-data/ledger-header.md index 3ff04cf09cc..18644e4bbe4 100644 --- a/docs/references/protocol/ledger-data/ledger-header.md +++ b/docs/references/protocol/ledger-data/ledger-header.md @@ -8,7 +8,7 @@ labels: - Blockchain --- # Ledger Header -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/ledger/ReadView.h#L71 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/ledger/ReadView.h#L51 "Source") Every [ledger version](../../../concepts/ledgers/index.md) has a unique header that describes the contents. You can look up a ledger's header information with the [ledger method][]. The contents of the ledger header are as follows: diff --git a/docs/references/protocol/transactions/pseudo-transaction-types/enableamendment.md b/docs/references/protocol/transactions/pseudo-transaction-types/enableamendment.md index 8cca8021981..1b72419ce6a 100644 --- a/docs/references/protocol/transactions/pseudo-transaction-types/enableamendment.md +++ b/docs/references/protocol/transactions/pseudo-transaction-types/enableamendment.md @@ -5,7 +5,7 @@ labels: - Blockchain --- # EnableAmendment -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/Change.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/Change.cpp "Source") An `EnableAmendment` pseudo-transaction marks a change in the status of a proposed amendment. The possible status changes are: diff --git a/docs/references/protocol/transactions/pseudo-transaction-types/setfee.md b/docs/references/protocol/transactions/pseudo-transaction-types/setfee.md index 78d0d852312..b44fcea802e 100644 --- a/docs/references/protocol/transactions/pseudo-transaction-types/setfee.md +++ b/docs/references/protocol/transactions/pseudo-transaction-types/setfee.md @@ -5,7 +5,7 @@ labels: - Fees --- # SetFee -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/Change.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/Change.cpp "Source") A `SetFee` [pseudo-transaction](pseudo-transaction-types.md) marks a change in [transaction cost](../../../../concepts/transactions/transaction-cost.md) or [reserve requirements](../../../../concepts/accounts/reserves.md) as a result of [Fee Voting](../../../../concepts/consensus-protocol/fee-voting.md). diff --git a/docs/references/protocol/transactions/pseudo-transaction-types/unlmodify.md b/docs/references/protocol/transactions/pseudo-transaction-types/unlmodify.md index 4f92cec549c..d1f02d07119 100644 --- a/docs/references/protocol/transactions/pseudo-transaction-types/unlmodify.md +++ b/docs/references/protocol/transactions/pseudo-transaction-types/unlmodify.md @@ -7,7 +7,7 @@ labels: - Blockchain --- # UNLModify -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/Change.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/Change.cpp "Source") _(Added by the [NegativeUNL amendment][].)_ diff --git a/docs/references/protocol/transactions/transaction-results/index.md b/docs/references/protocol/transactions/transaction-results/index.md index e2ef7912b91..2c4eef53903 100644 --- a/docs/references/protocol/transactions/transaction-results/index.md +++ b/docs/references/protocol/transactions/transaction-results/index.md @@ -8,7 +8,7 @@ labels: --- # Transaction Results -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/TER.h "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/TER.h "Source") The `rippled` server summarizes transaction results with result codes, which appear in fields such as `engine_result` and `meta.TransactionResult`. These codes are grouped into several categories of with different prefixes: diff --git a/docs/references/protocol/transactions/transaction-results/tec-codes.md b/docs/references/protocol/transactions/transaction-results/tec-codes.md index 8cea3a03d40..c242ce9f90b 100644 --- a/docs/references/protocol/transactions/transaction-results/tec-codes.md +++ b/docs/references/protocol/transactions/transaction-results/tec-codes.md @@ -7,7 +7,7 @@ labels: - Transaction Sending --- # tec Codes -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/impl/TER.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/libxrpl/protocol/TER.cpp "Source") These codes indicate that the transaction did not succeed, but it was applied to a ledger to apply the [transaction cost](../../../../concepts/transactions/transaction-cost.md) and may have had other side effects to the ledger. The `tec` codes have numerical values in the range 100 to 199. It is recommended to use the text code, not the numeric value. diff --git a/docs/references/protocol/transactions/types/accountdelete.md b/docs/references/protocol/transactions/types/accountdelete.md index e9284f854e5..49dd7683d70 100644 --- a/docs/references/protocol/transactions/types/accountdelete.md +++ b/docs/references/protocol/transactions/types/accountdelete.md @@ -6,7 +6,7 @@ labels: --- # AccountDelete -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/DeleteAccount.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/DeleteAccount.cpp "Source") An AccountDelete transaction deletes an [account](../../ledger-data/ledger-entry-types/accountroot.md) and any objects it owns in the XRP Ledger, if possible, sending the account's remaining XRP to a specified destination account. See [Deleting Accounts](../../../../concepts/accounts/deleting-accounts.md) for the requirements to delete an account. @@ -57,7 +57,7 @@ Besides errors that can occur for all transactions, {% $frontmatter.seo.title %} | `tecNO_DST` | Occurs if the `Destination` account is not a funded account in the ledger. | | `tecNO_PERMISSION` | Occurs if the `Destination` account requires [deposit authorization](../../../../concepts/accounts/depositauth.md) and the sender is not preauthorized. | | `tecTOO_SOON` | Occurs if the sender's `Sequence` number is too high. The transaction's `Sequence` number plus 256 must be less than the current [Ledger Index][]. This prevents replay of old transactions if this account is resurrected after it is deleted. | -| `tecHAS_OBLIGATIONS` | Occurs if the account to be deleted is connected to objects that cannot be deleted in the ledger. (This includes objects created by other accounts, such as [escrows](../../../../concepts/payment-types/escrow.md) and for example [NFT's minted](nftokenmint.md), [even if owned by another account](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/DeleteAccount.cpp#L197).) | +| `tecHAS_OBLIGATIONS` | Occurs if the account to be deleted is connected to objects that cannot be deleted in the ledger. (This includes objects created by other accounts, such as [escrows](../../../../concepts/payment-types/escrow.md) and for example [NFT's minted](nftokenmint.md), [even if owned by another account](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/DeleteAccount.cpp#L197).) | | `tefTOO_BIG` | Occurs if the sending account is linked to more than 1000 objects in the ledger. The transaction could succeed on retry if some of those objects were deleted separately first. | {% raw-partial file="/docs/_snippets/common-links.md" /%} diff --git a/docs/references/protocol/transactions/types/accountset.md b/docs/references/protocol/transactions/types/accountset.md index 289cfc2fca1..a9c7020e3e5 100644 --- a/docs/references/protocol/transactions/types/accountset.md +++ b/docs/references/protocol/transactions/types/accountset.md @@ -6,7 +6,7 @@ labels: --- # AccountSet -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/SetAccount.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/SetAccount.cpp "Source") An AccountSet transaction modifies the properties of an [account in the XRP Ledger](../../ledger-data/ledger-entry-types/accountroot.md). diff --git a/docs/references/protocol/transactions/types/ammbid.md b/docs/references/protocol/transactions/types/ammbid.md index dac81a865b3..08341d3f303 100644 --- a/docs/references/protocol/transactions/types/ammbid.md +++ b/docs/references/protocol/transactions/types/ammbid.md @@ -7,7 +7,7 @@ labels: - AMM --- # AMMBid -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/AMMBid.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/AMMBid.cpp "Source") Bid on an [Automated Market Maker](../../../../concepts/tokens/decentralized-exchange/automated-market-makers.md)'s (AMM's) auction slot. If you win, you can trade against the AMM at a discounted fee until you are outbid or 24 hours have passed. If you are outbid before 24 hours have passed, you are refunded part of the cost of your bid based on how much time remains. If the AMM's trading fee is zero, you can still bid, but the auction slot provides no benefit unless the trading fee changes. diff --git a/docs/references/protocol/transactions/types/ammclawback.md b/docs/references/protocol/transactions/types/ammclawback.md index 6ffbd8d9d3a..eb02a74189d 100644 --- a/docs/references/protocol/transactions/types/ammclawback.md +++ b/docs/references/protocol/transactions/types/ammclawback.md @@ -1,6 +1,6 @@ # AMMClawback -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/AMMClawback.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/AMMClawback.cpp "Source") Claw back tokens from a holder who has deposited your issued tokens into an AMM pool. diff --git a/docs/references/protocol/transactions/types/ammcreate.md b/docs/references/protocol/transactions/types/ammcreate.md index b89ec9e2877..a4276ce3dda 100644 --- a/docs/references/protocol/transactions/types/ammcreate.md +++ b/docs/references/protocol/transactions/types/ammcreate.md @@ -7,7 +7,7 @@ labels: - AMM --- # AMMCreate -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/AMMCreate.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/AMMCreate.cpp "Source") Create a new [Automated Market Maker](../../../../concepts/tokens/decentralized-exchange/automated-market-makers.md) (AMM) instance for trading a pair of assets ([fungible tokens](../../../../concepts/tokens/index.md) or [XRP](../../../../introduction/what-is-xrp.md)). diff --git a/docs/references/protocol/transactions/types/ammdelete.md b/docs/references/protocol/transactions/types/ammdelete.md index 3550b4d25c7..b893dcb405d 100644 --- a/docs/references/protocol/transactions/types/ammdelete.md +++ b/docs/references/protocol/transactions/types/ammdelete.md @@ -7,7 +7,7 @@ labels: - AMM --- # AMMDelete -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/AMMDelete.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/AMMDelete.cpp "Source") Delete an empty [Automated Market Maker](../../../../concepts/tokens/decentralized-exchange/automated-market-makers.md) (AMM) instance that could not be fully deleted automatically. diff --git a/docs/references/protocol/transactions/types/ammdeposit.md b/docs/references/protocol/transactions/types/ammdeposit.md index 254f576dea3..6723c7da984 100644 --- a/docs/references/protocol/transactions/types/ammdeposit.md +++ b/docs/references/protocol/transactions/types/ammdeposit.md @@ -7,7 +7,7 @@ labels: - AMM --- # AMMDeposit -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/AMMDeposit.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/AMMDeposit.cpp "Source") Deposit funds into an [Automated Market Maker](../../../../concepts/tokens/decentralized-exchange/automated-market-makers.md) (AMM) instance and receive the AMM's liquidity provider tokens (_LP Tokens_) in exchange. You can deposit one or both of the assets in the AMM's pool. diff --git a/docs/references/protocol/transactions/types/ammvote.md b/docs/references/protocol/transactions/types/ammvote.md index 9900723c164..35575f8d934 100644 --- a/docs/references/protocol/transactions/types/ammvote.md +++ b/docs/references/protocol/transactions/types/ammvote.md @@ -7,7 +7,7 @@ labels: - AMM --- # AMMVote -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/AMMVote.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/AMMVote.cpp "Source") Vote on the trading fee for an [Automated Market Maker](../../../../concepts/tokens/decentralized-exchange/automated-market-makers.md) instance. Up to 8 accounts can vote in proportion to the amount of the AMM's LP Tokens they hold. Each new vote re-calculates the AMM's trading fee based on a weighted average of the votes. diff --git a/docs/references/protocol/transactions/types/ammwithdraw.md b/docs/references/protocol/transactions/types/ammwithdraw.md index ff80631c9ee..cf4188706a4 100644 --- a/docs/references/protocol/transactions/types/ammwithdraw.md +++ b/docs/references/protocol/transactions/types/ammwithdraw.md @@ -7,7 +7,7 @@ labels: - AMM --- # AMMWithdraw -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/AMMWithdraw.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/AMMWithdraw.cpp "Source") Withdraw assets from an [Automated Market Maker](../../../../concepts/tokens/decentralized-exchange/automated-market-makers.md) (AMM) instance by returning the AMM's liquidity provider tokens (LP Tokens). diff --git a/docs/references/protocol/transactions/types/batch.md b/docs/references/protocol/transactions/types/batch.md index 25f1d3d65e2..de2905e0341 100644 --- a/docs/references/protocol/transactions/types/batch.md +++ b/docs/references/protocol/transactions/types/batch.md @@ -6,7 +6,7 @@ labels: status: not_enabled --- # Batch -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/Batch.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/Batch.cpp "Source") The `Batch` transaction submits up to eight transactions as a single unit. `Batch` transactions are executed atomically in one of four modes: All or Nothing, Only One, Until Failure, and Independent. diff --git a/docs/references/protocol/transactions/types/checkcancel.md b/docs/references/protocol/transactions/types/checkcancel.md index a4c4c2c17ae..90465dada92 100644 --- a/docs/references/protocol/transactions/types/checkcancel.md +++ b/docs/references/protocol/transactions/types/checkcancel.md @@ -7,7 +7,7 @@ labels: - Checks --- # CheckCancel -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/CancelCheck.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/CancelCheck.cpp "Source") Cancels an unredeemed Check, removing it from the ledger without sending any money. The source or the destination of the check can cancel a Check at any time using this transaction type. If the Check has expired, any address can cancel it. diff --git a/docs/references/protocol/transactions/types/checkcash.md b/docs/references/protocol/transactions/types/checkcash.md index f517d6fd62f..3f7712a3b71 100644 --- a/docs/references/protocol/transactions/types/checkcash.md +++ b/docs/references/protocol/transactions/types/checkcash.md @@ -7,7 +7,7 @@ labels: - Checks --- # CheckCash -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/CashCheck.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/CashCheck.cpp "Source") Attempts to redeem a Check object in the ledger to receive up to the amount authorized by the corresponding [CheckCreate transaction][]. Only the `Destination` address of a Check can cash it with a CheckCash transaction. Cashing a check this way is similar to executing a [Payment][] initiated by the destination. diff --git a/docs/references/protocol/transactions/types/checkcreate.md b/docs/references/protocol/transactions/types/checkcreate.md index eac5fcd0ad0..59ee50c5104 100644 --- a/docs/references/protocol/transactions/types/checkcreate.md +++ b/docs/references/protocol/transactions/types/checkcreate.md @@ -7,7 +7,7 @@ labels: - Checks --- # CheckCreate -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/CreateCheck.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/CreateCheck.cpp "Source") Create a Check object in the ledger, which is a deferred payment that can be cashed by its intended destination. The sender of this transaction is the sender of the Check. diff --git a/docs/references/protocol/transactions/types/clawback.md b/docs/references/protocol/transactions/types/clawback.md index c28ae0aa6f9..f45772d0d92 100644 --- a/docs/references/protocol/transactions/types/clawback.md +++ b/docs/references/protocol/transactions/types/clawback.md @@ -5,7 +5,7 @@ labels: - Tokens --- # Clawback -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/Clawback.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/Clawback.cpp "Source") Claw back tokens issued by your account. diff --git a/docs/references/protocol/transactions/types/depositpreauth.md b/docs/references/protocol/transactions/types/depositpreauth.md index 790ae3acacb..c79d0eaa4ef 100644 --- a/docs/references/protocol/transactions/types/depositpreauth.md +++ b/docs/references/protocol/transactions/types/depositpreauth.md @@ -5,7 +5,7 @@ labels: - Security --- # DepositPreauth -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/DepositPreauth.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/DepositPreauth.cpp "Source") A DepositPreauth transaction grants preauthorization to deliver payments to your account. This is only useful if you are using (or plan to use) [Deposit Authorization](../../../../concepts/accounts/depositauth.md). diff --git a/docs/references/protocol/transactions/types/diddelete.md b/docs/references/protocol/transactions/types/diddelete.md index cd39f960ba1..a1144581d0c 100644 --- a/docs/references/protocol/transactions/types/diddelete.md +++ b/docs/references/protocol/transactions/types/diddelete.md @@ -8,7 +8,7 @@ labels: --- # DIDDelete -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/DID.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/DID.cpp "Source") Delete the [DID ledger entry](../../ledger-data/ledger-entry-types/did.md) associated with the specified `Account` field. diff --git a/docs/references/protocol/transactions/types/didset.md b/docs/references/protocol/transactions/types/didset.md index ff3dc750db0..fa3a5828f80 100644 --- a/docs/references/protocol/transactions/types/didset.md +++ b/docs/references/protocol/transactions/types/didset.md @@ -6,7 +6,7 @@ labels: --- # DIDSet -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/DID.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/DID.cpp "Source") Creates a new [DID ledger entry](../../ledger-data/ledger-entry-types/did.md) or updates the fields of an existing one. diff --git a/docs/references/protocol/transactions/types/escrowcancel.md b/docs/references/protocol/transactions/types/escrowcancel.md index b9a37e5c858..6d9dabef961 100644 --- a/docs/references/protocol/transactions/types/escrowcancel.md +++ b/docs/references/protocol/transactions/types/escrowcancel.md @@ -6,7 +6,7 @@ labels: --- # EscrowCancel -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/Escrow.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/Escrow.cpp "Source") Return escrowed XRP to the sender. diff --git a/docs/references/protocol/transactions/types/escrowcreate.md b/docs/references/protocol/transactions/types/escrowcreate.md index 7d5b54219d0..ad698a83ec1 100644 --- a/docs/references/protocol/transactions/types/escrowcreate.md +++ b/docs/references/protocol/transactions/types/escrowcreate.md @@ -6,7 +6,7 @@ labels: --- # EscrowCreate -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/Escrow.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/Escrow.cpp "Source") Sequester XRP until the escrow process either finishes or is canceled. diff --git a/docs/references/protocol/transactions/types/escrowfinish.md b/docs/references/protocol/transactions/types/escrowfinish.md index 3b7e25fffd8..e2faab456fe 100644 --- a/docs/references/protocol/transactions/types/escrowfinish.md +++ b/docs/references/protocol/transactions/types/escrowfinish.md @@ -6,7 +6,7 @@ labels: --- # EscrowFinish -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/Escrow.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/Escrow.cpp "Source") Deliver XRP from an escrow (held payment) to the recipient. diff --git a/docs/references/protocol/transactions/types/ledgerstatefix.md b/docs/references/protocol/transactions/types/ledgerstatefix.md index 375c2a0317d..05ea47bda5f 100644 --- a/docs/references/protocol/transactions/types/ledgerstatefix.md +++ b/docs/references/protocol/transactions/types/ledgerstatefix.md @@ -6,7 +6,7 @@ labels: - Troubleshooting --- # LedgerStateFix -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/LedgerStateFix.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/LedgerStateFix.cpp "Source") `LedgerStateFix` is a general purpose transaction used to fix specific issues affecting the XRP ledger. You submit the transaction with the `LedgerFixType` value set to indicate the particular error state to correct. diff --git a/docs/references/protocol/transactions/types/mptokenauthorize.md b/docs/references/protocol/transactions/types/mptokenauthorize.md index 26b188c1cde..e5b46aca7cf 100644 --- a/docs/references/protocol/transactions/types/mptokenauthorize.md +++ b/docs/references/protocol/transactions/types/mptokenauthorize.md @@ -5,7 +5,7 @@ labels: --- # MPTokenAuthorize -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/MPTokenAuthorize.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/MPTokenAuthorize.cpp "Source") An MPTokenAuthorize transaction controls whether an account can hold a given [Multi-purpose Token (MPT)](../../../../concepts/tokens/fungible-tokens/multi-purpose-tokens.md). It has several uses: diff --git a/docs/references/protocol/transactions/types/mptokenissuancecreate.md b/docs/references/protocol/transactions/types/mptokenissuancecreate.md index 47f88057198..f864fec0d23 100644 --- a/docs/references/protocol/transactions/types/mptokenissuancecreate.md +++ b/docs/references/protocol/transactions/types/mptokenissuancecreate.md @@ -5,7 +5,7 @@ labels: --- # MPTokenIssuanceCreate -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/MPTokenIssuanceCreate.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/MPTokenIssuanceCreate.cpp "Source") The `MPTokenIssuanceCreate` transaction creates an [MPTokenIssuance](../../ledger-data/ledger-entry-types/mptokenissuance.md) object and adds it to the relevant directory node of the creator account. This transaction is the only opportunity an issuer has to specify any token fields that are defined as immutable (for example, MPT Flags). diff --git a/docs/references/protocol/transactions/types/mptokenissuancedestroy.md b/docs/references/protocol/transactions/types/mptokenissuancedestroy.md index 2444c38958c..556372d243e 100644 --- a/docs/references/protocol/transactions/types/mptokenissuancedestroy.md +++ b/docs/references/protocol/transactions/types/mptokenissuancedestroy.md @@ -4,7 +4,7 @@ labels: - Multi-purpose Tokens, MPTs --- # MPTokenIssuanceDestroy -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/MPTokenIssuanceDestroy.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/MPTokenIssuanceDestroy.cpp "Source") The `MPTokenIssuanceDestroy` transaction is used to remove an `MPTokenIssuance` object from the directory node in which it is being held, effectively removing the token from the ledger ("destroying" it). diff --git a/docs/references/protocol/transactions/types/mptokenissuanceset.md b/docs/references/protocol/transactions/types/mptokenissuanceset.md index dda812c3251..64eb44a62e4 100644 --- a/docs/references/protocol/transactions/types/mptokenissuanceset.md +++ b/docs/references/protocol/transactions/types/mptokenissuanceset.md @@ -4,7 +4,7 @@ labels: - Multi-purpose Tokens, MPTs --- # MPTokenIssuanceSet -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/MPTokenIssuanceSet.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/MPTokenIssuanceSet.cpp "Source") Use this transaction to update a mutable property for a Multi-purpose Token. The transaction flags determine which change(s) to apply. diff --git a/docs/references/protocol/transactions/types/nftokenacceptoffer.md b/docs/references/protocol/transactions/types/nftokenacceptoffer.md index 69cf356b542..39355c4cac2 100644 --- a/docs/references/protocol/transactions/types/nftokenacceptoffer.md +++ b/docs/references/protocol/transactions/types/nftokenacceptoffer.md @@ -5,7 +5,7 @@ labels: - NFTs, Non-fungible Tokens --- # NFTokenAcceptOffer -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/NFTokenAcceptOffer.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/NFTokenAcceptOffer.cpp "Source") The `NFTokenAcceptOffer` transaction is used to accept offers to buy or sell an NFT. It has two possible modes: diff --git a/docs/references/protocol/transactions/types/nftokenburn.md b/docs/references/protocol/transactions/types/nftokenburn.md index 2113d0a0098..e98db14b25c 100644 --- a/docs/references/protocol/transactions/types/nftokenburn.md +++ b/docs/references/protocol/transactions/types/nftokenburn.md @@ -7,7 +7,7 @@ labels: - Non-fungible Tokens, NFTs --- # NFTokenBurn -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/NFTokenBurn.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/NFTokenBurn.cpp "Source") The `NFTokenBurn` transaction is used to remove a `NFToken` object from the `NFTokenPage` in which it is being held, effectively removing the token from the ledger (_burning_ it). diff --git a/docs/references/protocol/transactions/types/nftokencanceloffer.md b/docs/references/protocol/transactions/types/nftokencanceloffer.md index c68ce911cdf..6bae7bc3242 100644 --- a/docs/references/protocol/transactions/types/nftokencanceloffer.md +++ b/docs/references/protocol/transactions/types/nftokencanceloffer.md @@ -7,7 +7,7 @@ labels: - NFTs, Non-fungible Tokens --- # NFTokenCancelOffer -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/NFTokenCancelOffer.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/NFTokenCancelOffer.cpp "Source") The `NFTokenCancelOffer` transaction can be used to cancel existing token offers created using `NFTokenCreateOffer`. diff --git a/docs/references/protocol/transactions/types/nftokencreateoffer.md b/docs/references/protocol/transactions/types/nftokencreateoffer.md index 5bcfeed8e83..1ae55644ac0 100644 --- a/docs/references/protocol/transactions/types/nftokencreateoffer.md +++ b/docs/references/protocol/transactions/types/nftokencreateoffer.md @@ -7,7 +7,7 @@ labels: - Non-fungible Tokens, NFTs --- # NFTokenCreateOffer -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/NFTokenCreateOffer.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/NFTokenCreateOffer.cpp "Source") Creates either a new _Sell_ offer for an `NFToken` owned by the account executing the transaction, or a new _Buy_ offer for an `NFToken` owned by another account. diff --git a/docs/references/protocol/transactions/types/nftokenmint.md b/docs/references/protocol/transactions/types/nftokenmint.md index 72f75eae2b1..815bd5f3505 100644 --- a/docs/references/protocol/transactions/types/nftokenmint.md +++ b/docs/references/protocol/transactions/types/nftokenmint.md @@ -5,7 +5,7 @@ labels: - Non-fungible Tokens, NFTs --- # NFTokenMint -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/NFTokenMint.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/NFTokenMint.cpp "Source") The `NFTokenMint` transaction creates a non-fungible token and adds it to the relevant [NFTokenPage object][] of the `NFTokenMinter` as an [NFToken][] object. This transaction is the only opportunity the `NFTokenMinter` has to specify any token fields that are defined as immutable (for example, the `TokenFlags`). diff --git a/docs/references/protocol/transactions/types/nftokenmodify.md b/docs/references/protocol/transactions/types/nftokenmodify.md index e751ff2f975..3f5403c9f52 100644 --- a/docs/references/protocol/transactions/types/nftokenmodify.md +++ b/docs/references/protocol/transactions/types/nftokenmodify.md @@ -7,7 +7,7 @@ title: - NFTokenModify --- # NFTokenModify -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/NFTokenModify.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/NFTokenModify.cpp "Source") `NFTokenModify` is used to change the `URI` field of an NFT to point to a different URI in order to update the supporting data for the NFT. The NFT must have been minted with the `tfMutable` flag set. See [Dynamic Non-Fungible Tokens](../../../../concepts/tokens/nfts/dynamic-nfts.md). diff --git a/docs/references/protocol/transactions/types/offercancel.md b/docs/references/protocol/transactions/types/offercancel.md index 2843bfb72b0..da7cbd97d77 100644 --- a/docs/references/protocol/transactions/types/offercancel.md +++ b/docs/references/protocol/transactions/types/offercancel.md @@ -8,7 +8,7 @@ labels: --- # OfferCancel -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/CancelOffer.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/CancelOffer.cpp "Source") An OfferCancel transaction removes an Offer object from the XRP Ledger. diff --git a/docs/references/protocol/transactions/types/offercreate.md b/docs/references/protocol/transactions/types/offercreate.md index 59c6b893788..dce277fcd10 100644 --- a/docs/references/protocol/transactions/types/offercreate.md +++ b/docs/references/protocol/transactions/types/offercreate.md @@ -6,7 +6,7 @@ labels: --- # OfferCreate -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/CreateOffer.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/CreateOffer.cpp "Source") An OfferCreate transaction places an [Offer](../../../../concepts/tokens/decentralized-exchange/offers.md) in the [decentralized exchange](../../../../concepts/tokens/decentralized-exchange/index.md). diff --git a/docs/references/protocol/transactions/types/oracledelete.md b/docs/references/protocol/transactions/types/oracledelete.md index cb63191cf3b..8889a279a8f 100644 --- a/docs/references/protocol/transactions/types/oracledelete.md +++ b/docs/references/protocol/transactions/types/oracledelete.md @@ -8,7 +8,7 @@ labels: # OracleDelete _(Requires the [PriceOracle amendment][])_ -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/DeleteOracle.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/DeleteOracle.cpp "Source") Delete an `Oracle` ledger entry. diff --git a/docs/references/protocol/transactions/types/oracleset.md b/docs/references/protocol/transactions/types/oracleset.md index b01c099554a..a9350716e5d 100644 --- a/docs/references/protocol/transactions/types/oracleset.md +++ b/docs/references/protocol/transactions/types/oracleset.md @@ -6,7 +6,7 @@ labels: - Oracle --- # OracleSet -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/SetOracle.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/SetOracle.cpp "Source") Creates a new `Oracle` ledger entry or updates the fields of an existing one, using the Oracle Document ID. diff --git a/docs/references/protocol/transactions/types/payment.md b/docs/references/protocol/transactions/types/payment.md index 2c9703bd590..86ef58c0385 100644 --- a/docs/references/protocol/transactions/types/payment.md +++ b/docs/references/protocol/transactions/types/payment.md @@ -8,7 +8,7 @@ labels: - Tokens --- # Payment -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/Payment.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/Payment.cpp "Source") A Payment transaction represents a transfer of value from one account to another. (Depending on the path taken, this can involve additional exchanges of value, which occur atomically.) This transaction type can be used for several [types of payments](#types-of-payments). diff --git a/docs/references/protocol/transactions/types/paymentchannelclaim.md b/docs/references/protocol/transactions/types/paymentchannelclaim.md index 7967dd66260..349d3a84ff2 100644 --- a/docs/references/protocol/transactions/types/paymentchannelclaim.md +++ b/docs/references/protocol/transactions/types/paymentchannelclaim.md @@ -7,7 +7,7 @@ labels: - Payment Channels --- # PaymentChannelClaim -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/PayChan.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/PayChan.cpp "Source") Claim funds from a payment channel, adjust the payment channel's expiration, or both. This transaction can be used differently depending on the transaction sender's role in the specified channel: diff --git a/docs/references/protocol/transactions/types/paymentchannelcreate.md b/docs/references/protocol/transactions/types/paymentchannelcreate.md index 55acc9e3489..45bec8fcc90 100644 --- a/docs/references/protocol/transactions/types/paymentchannelcreate.md +++ b/docs/references/protocol/transactions/types/paymentchannelcreate.md @@ -5,7 +5,7 @@ labels: - Payment Channels --- # PaymentChannelCreate -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/PayChan.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/PayChan.cpp "Source") Create a [payment channel](../../../../concepts/payment-types/payment-channels.md) and fund it. The address sending this transaction becomes the "source address" of the payment channel. diff --git a/docs/references/protocol/transactions/types/paymentchannelfund.md b/docs/references/protocol/transactions/types/paymentchannelfund.md index e85f11e7b59..b355a0e1e7e 100644 --- a/docs/references/protocol/transactions/types/paymentchannelfund.md +++ b/docs/references/protocol/transactions/types/paymentchannelfund.md @@ -7,7 +7,7 @@ labels: - Payment Channels --- # PaymentChannelFund -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/PayChan.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/PayChan.cpp "Source") Add an additional amount to an open [payment channel](../../../../concepts/payment-types/payment-channels.md), and optionally update the expiration time of the channel. Only the source account of the channel can use this transaction. diff --git a/docs/references/protocol/transactions/types/permissioneddomaindelete.md b/docs/references/protocol/transactions/types/permissioneddomaindelete.md index 29b323e79f6..6ae7e03d87b 100644 --- a/docs/references/protocol/transactions/types/permissioneddomaindelete.md +++ b/docs/references/protocol/transactions/types/permissioneddomaindelete.md @@ -6,7 +6,7 @@ labels: - Permissioned Domains --- # PermissionedDomainDelete -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/PermissionedDomainDelete.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/PermissionedDomainDelete.cpp "Source") Delete a [permissioned domain][] that you own. diff --git a/docs/references/protocol/transactions/types/permissioneddomainset.md b/docs/references/protocol/transactions/types/permissioneddomainset.md index 4b0160b11ca..6997dffe47e 100644 --- a/docs/references/protocol/transactions/types/permissioneddomainset.md +++ b/docs/references/protocol/transactions/types/permissioneddomainset.md @@ -6,7 +6,7 @@ labels: - Permissioned Domains --- # PermissionedDomainSet -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/PermissionedDomainSet.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/PermissionedDomainSet.cpp "Source") Create a [permissioned domain][], or modify one that you own. diff --git a/docs/references/protocol/transactions/types/setregularkey.md b/docs/references/protocol/transactions/types/setregularkey.md index 16829f83467..5e4eab2b637 100644 --- a/docs/references/protocol/transactions/types/setregularkey.md +++ b/docs/references/protocol/transactions/types/setregularkey.md @@ -8,7 +8,7 @@ labels: --- # SetRegularKey -[[Source]](https://github.com/XRPLF/rippled/blob/4239880acb5e559446d2067f00dabb31cf102a23/src/ripple/app/transactors/SetRegularKey.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/SetRegularKey.cpp "Source") A `SetRegularKey` transaction assigns, changes, or removes the regular key pair associated with an account. diff --git a/docs/references/protocol/transactions/types/signerlistset.md b/docs/references/protocol/transactions/types/signerlistset.md index 121a9c6286a..5b8f3505e94 100644 --- a/docs/references/protocol/transactions/types/signerlistset.md +++ b/docs/references/protocol/transactions/types/signerlistset.md @@ -8,7 +8,7 @@ labels: --- # SignerListSet -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/SetSignerList.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/SetSignerList.cpp "Source") The SignerListSet transaction creates, replaces, or removes a list of signers that can be used to [multi-sign](../../../../concepts/accounts/multi-signing.md) a transaction. This transaction type was introduced by the [MultiSign amendment][]. diff --git a/docs/references/protocol/transactions/types/ticketcreate.md b/docs/references/protocol/transactions/types/ticketcreate.md index 42757d43eda..4a961ccb147 100644 --- a/docs/references/protocol/transactions/types/ticketcreate.md +++ b/docs/references/protocol/transactions/types/ticketcreate.md @@ -8,7 +8,7 @@ labels: --- # TicketCreate -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/CreateTicket.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/CreateTicket.cpp "Source") _(Added by the [TicketBatch amendment][].)_ diff --git a/docs/references/protocol/transactions/types/trustset.md b/docs/references/protocol/transactions/types/trustset.md index 90b7a2541cd..7741517df4a 100644 --- a/docs/references/protocol/transactions/types/trustset.md +++ b/docs/references/protocol/transactions/types/trustset.md @@ -8,7 +8,7 @@ labels: --- # TrustSet -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/SetTrust.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/SetTrust.cpp "Source") Create or modify a [trust line](../../../../concepts/tokens/fungible-tokens/index.md) linking two accounts. diff --git a/docs/references/protocol/transactions/types/xchainaccountcreatecommit.md b/docs/references/protocol/transactions/types/xchainaccountcreatecommit.md index 9186da7c37e..eefb1afeb0c 100644 --- a/docs/references/protocol/transactions/types/xchainaccountcreatecommit.md +++ b/docs/references/protocol/transactions/types/xchainaccountcreatecommit.md @@ -8,7 +8,7 @@ labels: status: not_enabled --- # XChainAccountCreateCommit -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/impl/TxFormats.cpp#L466-L474 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/XChainBridge.h#L254 "Source") _(Requires the [XChainBridge amendment][] {% not-enabled /%})_ diff --git a/docs/references/protocol/transactions/types/xchainaddaccountcreateattestation.md b/docs/references/protocol/transactions/types/xchainaddaccountcreateattestation.md index ddfab812f01..d1010b0b9f9 100644 --- a/docs/references/protocol/transactions/types/xchainaddaccountcreateattestation.md +++ b/docs/references/protocol/transactions/types/xchainaddaccountcreateattestation.md @@ -8,7 +8,7 @@ labels: status: not_enabled --- # XChainAddAccountCreateAttestation -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/impl/TxFormats.cpp#L447-L464 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/XChainBridge.h#L189-L208 "Source") _(Requires the [XChainBridge amendment][] {% not-enabled /%})_ diff --git a/docs/references/protocol/transactions/types/xchainaddclaimattestation.md b/docs/references/protocol/transactions/types/xchainaddclaimattestation.md index d17829567b2..886b82aee9f 100644 --- a/docs/references/protocol/transactions/types/xchainaddclaimattestation.md +++ b/docs/references/protocol/transactions/types/xchainaddclaimattestation.md @@ -8,7 +8,7 @@ labels: status: not_enabled --- # XChainAddClaimAttestation -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/impl/TxFormats.cpp#L429-L445 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/XChainBridge.h#L169-L187 "Source") _(Requires the [XChainBridge amendment][] {% not-enabled /%})_ diff --git a/docs/references/protocol/transactions/types/xchainclaim.md b/docs/references/protocol/transactions/types/xchainclaim.md index e6e529aa038..3deeba5c000 100644 --- a/docs/references/protocol/transactions/types/xchainclaim.md +++ b/docs/references/protocol/transactions/types/xchainclaim.md @@ -8,7 +8,7 @@ labels: status: not_enabled --- # XChainClaim -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/impl/TxFormats.cpp#L418-L427 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/XChainBridge.h#L84-L102 "Source") _(Requires the [XChainBridge amendment][] {% not-enabled /%})_ diff --git a/docs/references/protocol/transactions/types/xchaincommit.md b/docs/references/protocol/transactions/types/xchaincommit.md index 2cda7327515..61d7f63403f 100644 --- a/docs/references/protocol/transactions/types/xchaincommit.md +++ b/docs/references/protocol/transactions/types/xchaincommit.md @@ -8,7 +8,7 @@ labels: status: not_enabled --- # XChainCommit -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/impl/TxFormats.cpp#L408-L416 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/XChainBridge.h#L109-L129 "Source") _(Requires the [XChainBridge amendment][] {% not-enabled /%})_ diff --git a/docs/references/protocol/transactions/types/xchaincreatebridge.md b/docs/references/protocol/transactions/types/xchaincreatebridge.md index a3d70e71c01..a7d14379040 100644 --- a/docs/references/protocol/transactions/types/xchaincreatebridge.md +++ b/docs/references/protocol/transactions/types/xchaincreatebridge.md @@ -8,7 +8,7 @@ labels: status: not_enabled --- # XChainCreateBridge -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/impl/TxFormats.cpp#L381-L388 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/XChainBridge.h#L33-L50 "Source") _(Requires the [XChainBridge amendment][] {% not-enabled /%})_ diff --git a/docs/references/protocol/transactions/types/xchaincreateclaimid.md b/docs/references/protocol/transactions/types/xchaincreateclaimid.md index e6d12560947..dd8d7cf7991 100644 --- a/docs/references/protocol/transactions/types/xchaincreateclaimid.md +++ b/docs/references/protocol/transactions/types/xchaincreateclaimid.md @@ -8,7 +8,7 @@ labels: status: not_enabled --- # XChainCreateClaimID -[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/impl/TxFormats.cpp#L399-L406 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/XChainBridge.h#L141-L158 "Source") _(Requires the [XChainBridge amendment][] {% not-enabled /%})_ diff --git a/docs/references/protocol/transactions/types/xchainmodifybridge.md b/docs/references/protocol/transactions/types/xchainmodifybridge.md index 190b392a393..792976eaabf 100644 --- a/docs/references/protocol/transactions/types/xchainmodifybridge.md +++ b/docs/references/protocol/transactions/types/xchainmodifybridge.md @@ -8,7 +8,7 @@ labels: status: not_enabled --- # XChainModifyBridge -[[Source]](https://github.com/XRPLF/rippled/blob/develop/src/ripple/protocol/impl/TxFormats.cpp#L390-L397 "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/XChainBridge.h#L71 "Source") _(Requires the [XChainBridge amendment][] {% not-enabled /%})_ diff --git a/docs/tutorials/http-websocket-apis/build-apps/get-started.md b/docs/tutorials/http-websocket-apis/build-apps/get-started.md index 82edbc65ef3..a46fadde924 100644 --- a/docs/tutorials/http-websocket-apis/build-apps/get-started.md +++ b/docs/tutorials/http-websocket-apis/build-apps/get-started.md @@ -30,7 +30,7 @@ Both APIs can be served unencrypted (`http://` and `ws://`) or encrypted using T The API methods are divided into [Public Methods](../../../references/http-websocket-apis/public-api-methods/index.md) and [Admin Methods](../../../references/http-websocket-apis/admin-api-methods/index.md) so that organizations can offer public servers for the benefit of the community. To access admin methods, or admin functionality of public methods, you must connect to the API on a **port and IP address marked as admin** in the server's config file. -The [example config file](https://github.com/XRPLF/rippled/blob/f00f263852c472938bf8e993e26c7f96f435935c/cfg/rippled-example.cfg#L1154-L1179) listens for connections on the local loopback network (127.0.0.1), with JSON-RPC (HTTP) on port 5005 and WebSocket (WS) on port 6006, and treats all connected clients as admin. +The [example config file](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/cfg/rippled-example.cfg#L1414-L1448) listens for connections on the local loopback network (127.0.0.1), with JSON-RPC (HTTP) on port 5005 and WebSocket (WS) on port 6006, and treats all connected clients as admin. ## WebSocket API diff --git a/docs/tutorials/java/build-apps/get-started.md b/docs/tutorials/java/build-apps/get-started.md index 26237bbb2cb..75ae7b9b2ac 100644 --- a/docs/tutorials/java/build-apps/get-started.md +++ b/docs/tutorials/java/build-apps/get-started.md @@ -104,7 +104,7 @@ The sample code in the previous section shows you how to connect to the Testnet, XrplClient xrplClient = new XrplClient(rippledUrl); ``` - See the example [core server config file](https://github.com/XRPLF/rippled/blob/c0a0b79d2d483b318ce1d82e526bd53df83a4a2c/cfg/rippled-example.cfg#L1562) for more information about default values. + See the example [core server config file](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/cfg/rippled-example.cfg#L1423) for more information about default values. * By using one of the available [public servers][]: diff --git a/docs/tutorials/javascript/amm/trade-with-auction-slot.md b/docs/tutorials/javascript/amm/trade-with-auction-slot.md index 13a86f32e01..a03a690e686 100644 --- 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: +Use [AMM helper functions](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/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 tutorial uses three of the available [AMM helper functions](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/misc/detail/AMMHelpers.cpp). ### swapOut() diff --git a/docs/tutorials/javascript/build-apps/get-started.md b/docs/tutorials/javascript/build-apps/get-started.md index d82acff87ea..a1816499b6d 100644 --- a/docs/tutorials/javascript/build-apps/get-started.md +++ b/docs/tutorials/javascript/build-apps/get-started.md @@ -104,7 +104,7 @@ The sample code in the previous section shows you how to connect to the Testnet, await client.connect() ``` - See the example [core server config file](https://github.com/XRPLF/rippled/blob/c0a0b79d2d483b318ce1d82e526bd53df83a4a2c/cfg/rippled-example.cfg#L1562) for more information about default values. + See the example [core server config file](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/cfg/rippled-example.cfg#L1423) for more information about default values. * By using one of the available [public servers][]: diff --git a/docs/tutorials/php/build-apps/get-started.md b/docs/tutorials/php/build-apps/get-started.md index 1ac84f92810..f3db0e25288 100644 --- a/docs/tutorials/php/build-apps/get-started.md +++ b/docs/tutorials/php/build-apps/get-started.md @@ -86,7 +86,7 @@ The sample code in the previous section shows you how to connect to the Testnet, $client = new JsonRpcClient("LOCAL_JSON_RPC_URL"); ``` - See the example [core server config file](https://github.com/XRPLF/rippled/blob/c0a0b79d2d483b318ce1d82e526bd53df83a4a2c/cfg/rippled-example.cfg#L1562) for more information about default values. + See the example [core server config file](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/cfg/rippled-example.cfg#L1423) for more information about default values. * By using one of the available [public servers][]: diff --git a/docs/tutorials/python/build-apps/get-started.md b/docs/tutorials/python/build-apps/get-started.md index e6ad160dd15..2b27b173877 100644 --- a/docs/tutorials/python/build-apps/get-started.md +++ b/docs/tutorials/python/build-apps/get-started.md @@ -63,7 +63,7 @@ The sample code in the previous section shows you how to connect to the Testnet, client = JsonRpcClient(JSON_RPC_URL) ``` - See the example [core server config file](https://github.com/XRPLF/rippled/blob/c0a0b79d2d483b318ce1d82e526bd53df83a4a2c/cfg/rippled-example.cfg#L1562) for more information about default values. + See the example [core server config file](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/cfg/rippled-example.cfg#L1423) for more information about default values. * By using one of the available [public servers][]: diff --git a/docs/tutorials/python/send-payments/send-and-cash-checks.md b/docs/tutorials/python/send-payments/send-and-cash-checks.md index dde3a10a96e..6390f868f6e 100644 --- a/docs/tutorials/python/send-payments/send-and-cash-checks.md +++ b/docs/tutorials/python/send-payments/send-and-cash-checks.md @@ -33,7 +33,7 @@ If you haven't done so already, create a new folder on your local disk and insta pip3 install xrpl-py ``` -Clone or download the [Modular Tutorial Samples](https://github.com/XRPLF/xrpl-dev-portal/tree/master/content/_code-samples/quickstart/py/). +Clone or download the [Modular Tutorial Samples](https://github.com/XRPLF/xrpl-dev-portal/tree/master/_code-samples/quickstart/py/). {% admonition type="info" name="Note" %}Without the Quickstart Samples, you will not be able to try the examples that follow. {% /admonition %} @@ -120,7 +120,7 @@ To cancel a check you have previously sent to another account. # Code Walkthrough -You can download the [Quickstart Samples](https://github.com/XRPLF/xrpl-dev-portal/tree/master/content/_code-samples/quickstart/py/) in the source repository for this website. +You can download the [Quickstart Samples](https://github.com/XRPLF/xrpl-dev-portal/tree/master/_code-samples/quickstart/py/) in the source repository for this website. ## mod10.py diff --git a/resources/contribute-code/create-custom-transactors.md b/resources/contribute-code/create-custom-transactors.md index c0a80ff2154..b89a93e7cd1 100644 --- a/resources/contribute-code/create-custom-transactors.md +++ b/resources/contribute-code/create-custom-transactors.md @@ -21,8 +21,8 @@ Transactors follow a basic order of operations: This tutorial uses the existing `CreateCheck` transactor as an example. You can view the source files here: -- [Header File](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/CreateCheck.h) -- [CPP File](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/CreateCheck.cpp) +- [Header File](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/CreateCheck.h) +- [CPP File](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/CreateCheck.cpp) ## Header File @@ -78,8 +78,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) + - [`LedgerFormats.cpp`](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/libxrpl/protocol/LedgerFormats.cpp) + - [`TxFormats.cpp`](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/libxrpl/protocol/TxFormats.cpp) - `rippled` summarizes transaction results with result codes. See: [Transaction Results](../../docs/references/protocol/transactions/transaction-results/index.md) @@ -344,7 +344,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/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/applySteps.h#L54-L57) 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. diff --git a/resources/contribute-code/index.md b/resources/contribute-code/index.md index 01e8afa0110..b5781fee948 100644 --- a/resources/contribute-code/index.md +++ b/resources/contribute-code/index.md @@ -17,7 +17,7 @@ The software that powers the XRP Ledger is open-source, so anyone can download, | XRP Ledger Source Code | | |:-----------------------|:----------------------------------------------------| | Repository | | -| License | [Multiple; ISC (permissive)](https://github.com/XRPLF/rippled/blob/develop/LICENSE.md) | +| License | [Multiple; ISC (permissive)](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/LICENSE.md) | | Programming Language | C++ | If you're not sure where to start, Dev Null Productions provides a detailed and thorough [**Source Code Guide**](https://xrpintel.com/source) that describes the structure and functions of the core XRP Ledger server (`rippled`) implementation. diff --git a/resources/known-amendments.md b/resources/known-amendments.md index ce3ffa49ada..a67a5bb44fd 100644 --- a/resources/known-amendments.md +++ b/resources/known-amendments.md @@ -5,7 +5,7 @@ labels: - Blockchain --- # Known Amendments -[[Source]](https://github.com/xrplf/rippled/blob/master/src/ripple/protocol/impl/Feature.cpp "Source") +[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/libxrpl/protocol/Feature.cpp "Source") ## Known Amendments on Mainnet @@ -1679,7 +1679,7 @@ For more information, see the [Payment Channels Tutorial](../docs/tutorials/how- Allows accounts to delegate some permissions to other accounts. -Specification: [XLS-75](https://github.com/XRPLF/XRPL-Standards/tree/master/XLS-0075d-permission-delegation). +Specification: [XLS-75](https://github.com/XRPLF/XRPL-Standards/tree/master/XLS-0075-permission-delegation). ### PermissionedDEX @@ -1773,7 +1773,7 @@ When this amendment is activated, the XRP Ledger will undergo a brief scheduled Creates a structure for aggregating assets from multiple depositors. This is intended to be used with the proposed on-chain Lending Protocol. -Specification: [XLS-65](https://github.com/XRPLF/XRPL-Standards/tree/master/XLS-0065d-single-asset-vault). +Specification: [XLS-65](https://github.com/XRPLF/XRPL-Standards/tree/master/XLS-0065-single-asset-vault). ### SortedDirectories