Remove badges > ~2yrs old

Version 1.8.0 of rippled was released in late 2021, so any changes prior
to that are historical and no longer need badges.

Fixes #1978
This commit is contained in:
mDuo13
2024-01-23 13:12:55 -08:00
parent 20c7f5d0b1
commit 33cd1f54a5
41 changed files with 84 additions and 436 deletions

View File

@@ -11,7 +11,7 @@ labels:
_([TicketBatch amendment][]が必要です)_
`Ticket`オブジェクトタイプは、将来の使用のために確保されたアカウント[シーケンス番号](../../data-types/basic-data-types.md#アカウントシーケンス)を追跡する[Ticket](../../../../concepts/accounts/tickets.md)を表します。[TicketCreate トランザクション][]で新しいチケットを作成することができます。{% badge href="https://github.com/XRPLF/rippled/releases/tag/1.7.0" %}New in: rippled 1.7.0{% /badge %}.
`Ticket`オブジェクトタイプは、将来の使用のために確保されたアカウント[シーケンス番号](../../data-types/basic-data-types.md#アカウントシーケンス)を追跡する[Ticket](../../../../concepts/accounts/tickets.md)を表します。[TicketCreate トランザクション][]で新しいチケットを作成することができます。
## {% $frontmatter.seo.title %} JSONの例

View File

@@ -172,50 +172,6 @@
[ImmediateOfferKilledの修正]: /resources/known-amendments.md#immediateofferkilled
[Interledger Protocol]: https://interledger.org/
[Internal Type]: /references/protocol/binary-format.md
[Introduced in: rippled 0.26.0]: https://github.com/XRPLF/rippled/releases/tag/0.26.0 "BADGE_BLUE"
[Introduced in: rippled 0.26.1]: https://github.com/XRPLF/rippled/releases/tag/0.26.1 "BADGE_BLUE"
[Introduced in: rippled 0.26.2]: https://github.com/XRPLF/rippled/releases/tag/0.26.2 "BADGE_BLUE"
[Introduced in: rippled 0.26.3-sp1]: https://github.com/XRPLF/rippled/releases/tag/0.26.3-sp1 "BADGE_BLUE"
[Introduced in: rippled 0.26.4-sp1]: https://github.com/XRPLF/rippled/releases/tag/0.26.4-sp1 "BADGE_BLUE"
[Introduced in: rippled 0.26.4]: https://github.com/XRPLF/rippled/releases/tag/0.26.4 "BADGE_BLUE"
[Introduced in: rippled 0.27.0]: https://github.com/XRPLF/rippled/releases/tag/0.27.0 "BADGE_BLUE"
[Introduced in: rippled 0.27.1]: https://github.com/XRPLF/rippled/releases/tag/0.27.1 "BADGE_BLUE"
[Introduced in: rippled 0.27.2]: https://github.com/XRPLF/rippled/releases/tag/0.27.2 "BADGE_BLUE"
[Introduced in: rippled 0.27.3-sp1]: https://github.com/XRPLF/rippled/releases/tag/0.27.3-sp1 "BADGE_BLUE"
[Introduced in: rippled 0.27.3-sp2]: https://github.com/XRPLF/rippled/releases/tag/0.27.3-sp2 "BADGE_BLUE"
[Introduced in: rippled 0.27.3]: https://github.com/XRPLF/rippled/releases/tag/0.27.3 "BADGE_BLUE"
[Introduced in: rippled 0.27.4]: https://github.com/XRPLF/rippled/releases/tag/0.27.4 "BADGE_BLUE"
[Introduced in: rippled 0.28.0]: https://github.com/XRPLF/rippled/releases/tag/0.28.0 "BADGE_BLUE"
[Introduced in: rippled 0.28.2]: https://github.com/XRPLF/rippled/releases/tag/0.28.2 "BADGE_BLUE"
[Introduced in: rippled 0.29.0-hf1]: https://github.com/XRPLF/rippled/releases/tag/0.29.0-hf1 "BADGE_BLUE"
[Introduced in: rippled 0.29.0]: https://github.com/XRPLF/rippled/releases/tag/0.29.0 "BADGE_BLUE"
[Introduced in: rippled 0.30.0]: https://github.com/XRPLF/rippled/releases/tag/0.30.0 "BADGE_BLUE"
[Introduced in: rippled 0.30.1]: https://github.com/XRPLF/rippled/releases/tag/0.30.1 "BADGE_BLUE"
[Introduced in: rippled 0.31.0]: https://github.com/XRPLF/rippled/releases/tag/0.31.0 "BADGE_BLUE"
[Introduced in: rippled 0.32.0]: https://github.com/XRPLF/rippled/releases/tag/0.32.0 "BADGE_BLUE"
[Introduced in: rippled 0.32.1]: https://github.com/XRPLF/rippled/releases/tag/0.32.1 "BADGE_BLUE"
[Introduced in: rippled 0.33.0]: https://github.com/XRPLF/rippled/releases/tag/0.33.0 "BADGE_BLUE"
[Introduced in: rippled 0.50.0]: https://github.com/XRPLF/rippled/releases/tag/0.50.0 "BADGE_BLUE"
[Introduced in: rippled 0.70.0]: https://github.com/XRPLF/rippled/releases/tag/0.70.0 "BADGE_BLUE"
[Introduced in: rippled 0.70.2]: https://github.com/XRPLF/rippled/releases/tag/0.70.2 "BADGE_BLUE"
[Introduced in: rippled 0.80.0]: https://github.com/XRPLF/rippled/releases/tag/0.80.0 "BADGE_BLUE"
[Introduced in: rippled 0.80.1]: https://github.com/XRPLF/rippled/releases/tag/0.80.1 "BADGE_BLUE"
[Introduced in: rippled 0.90.0]: https://github.com/XRPLF/rippled/releases/tag/0.90.0 "BADGE_BLUE"
[Introduced in: rippled 1.0.0]: https://github.com/XRPLF/rippled/releases/tag/1.0.0 "BADGE_BLUE"
[Introduced in: rippled 1.1.0]: https://github.com/XRPLF/rippled/releases/tag/1.1.0 "BADGE_BLUE"
[Introduced in: rippled 1.10.0]: https://github.com/XRPLF/rippled/releases/tag/1.10.0 "BADGE_BLUE"
[Introduced in: rippled 1.11.0]: https://github.com/XRPLF/rippled/releases/tag/1.11.0 "BADGE_BLUE"
[Introduced in: rippled 1.12.0]: https://github.com/XRPLF/rippled/releases/tag/1.12.0 "BADGE_BLUE"
[Introduced in: rippled 1.2.0]: https://github.com/XRPLF/rippled/releases/tag/1.2.0 "BADGE_BLUE"
[Introduced in: rippled 1.2.1]: https://github.com/XRPLF/rippled/releases/tag/1.2.1 "BADGE_BLUE"
[Introduced in: rippled 1.3.1]: https://github.com/XRPLF/rippled/releases/tag/1.3.1 "BADGE_BLUE"
[Introduced in: rippled 1.4.0]: https://github.com/XRPLF/rippled/releases/tag/1.4.0 "BADGE_BLUE"
[Introduced in: rippled 1.5.0]: https://github.com/XRPLF/rippled/releases/tag/1.5.0 "BADGE_BLUE"
[Introduced in: rippled 1.6.0]: https://github.com/XRPLF/rippled/releases/tag/1.6.0 "BADGE_BLUE"
[Introduced in: rippled 1.7.0]: https://github.com/XRPLF/rippled/releases/tag/1.7.0 "BADGE_BLUE"
[Introduced in: rippled 1.7.2]: https://github.com/XRPLF/rippled/releases/tag/1.7.2 "BADGE_BLUE"
[Introduced in: rippled 1.8.1]: https://github.com/XRPLF/rippled/releases/tag/1.8.1 "BADGE_BLUE"
[Introduced in: rippled 2.0.0]: https://github.com/XRPLF/rippled/releases/tag/2.0.0 "BADGE_BLUE"
[Ledger Index]: /references/protocol/data-types/basic-data-types.md#ledger-index
[LedgerHashes entry]: /references/protocol/ledger-data/ledger-entry-types/ledgerhashes.md
[LedgerHashes object]: /references/protocol/ledger-data/ledger-entry-types/ledgerhashes.md
@@ -274,50 +230,6 @@
[NegativeUNLの修正]: /resources/known-amendments.md#negativeunl
[NegativeUNLエントリ]: /references/protocol/ledger-data/ledger-entry-types/negativeunl.md
[NegativeUNLオブジェクト]: /references/protocol/ledger-data/ledger-entry-types/negativeunl.md
[New in: rippled 0.26.0]: https://github.com/XRPLF/rippled/releases/tag/0.26.0 "BADGE_BLUE"
[New in: rippled 0.26.1]: https://github.com/XRPLF/rippled/releases/tag/0.26.1 "BADGE_BLUE"
[New in: rippled 0.26.2]: https://github.com/XRPLF/rippled/releases/tag/0.26.2 "BADGE_BLUE"
[New in: rippled 0.26.3-sp1]: https://github.com/XRPLF/rippled/releases/tag/0.26.3-sp1 "BADGE_BLUE"
[New in: rippled 0.26.4-sp1]: https://github.com/XRPLF/rippled/releases/tag/0.26.4-sp1 "BADGE_BLUE"
[New in: rippled 0.26.4]: https://github.com/XRPLF/rippled/releases/tag/0.26.4 "BADGE_BLUE"
[New in: rippled 0.27.0]: https://github.com/XRPLF/rippled/releases/tag/0.27.0 "BADGE_BLUE"
[New in: rippled 0.27.1]: https://github.com/XRPLF/rippled/releases/tag/0.27.1 "BADGE_BLUE"
[New in: rippled 0.27.2]: https://github.com/XRPLF/rippled/releases/tag/0.27.2 "BADGE_BLUE"
[New in: rippled 0.27.3-sp1]: https://github.com/XRPLF/rippled/releases/tag/0.27.3-sp1 "BADGE_BLUE"
[New in: rippled 0.27.3-sp2]: https://github.com/XRPLF/rippled/releases/tag/0.27.3-sp2 "BADGE_BLUE"
[New in: rippled 0.27.3]: https://github.com/XRPLF/rippled/releases/tag/0.27.3 "BADGE_BLUE"
[New in: rippled 0.27.4]: https://github.com/XRPLF/rippled/releases/tag/0.27.4 "BADGE_BLUE"
[New in: rippled 0.28.0]: https://github.com/XRPLF/rippled/releases/tag/0.28.0 "BADGE_BLUE"
[New in: rippled 0.28.2]: https://github.com/XRPLF/rippled/releases/tag/0.28.2 "BADGE_BLUE"
[New in: rippled 0.29.0-hf1]: https://github.com/XRPLF/rippled/releases/tag/0.29.0-hf1 "BADGE_BLUE"
[New in: rippled 0.29.0]: https://github.com/XRPLF/rippled/releases/tag/0.29.0 "BADGE_BLUE"
[New in: rippled 0.30.0]: https://github.com/XRPLF/rippled/releases/tag/0.30.0 "BADGE_BLUE"
[New in: rippled 0.30.1]: https://github.com/XRPLF/rippled/releases/tag/0.30.1 "BADGE_BLUE"
[New in: rippled 0.31.0]: https://github.com/XRPLF/rippled/releases/tag/0.31.0 "BADGE_BLUE"
[New in: rippled 0.32.0]: https://github.com/XRPLF/rippled/releases/tag/0.32.0 "BADGE_BLUE"
[New in: rippled 0.32.1]: https://github.com/XRPLF/rippled/releases/tag/0.32.1 "BADGE_BLUE"
[New in: rippled 0.33.0]: https://github.com/XRPLF/rippled/releases/tag/0.33.0 "BADGE_BLUE"
[New in: rippled 0.50.0]: https://github.com/XRPLF/rippled/releases/tag/0.50.0 "BADGE_BLUE"
[New in: rippled 0.70.0]: https://github.com/XRPLF/rippled/releases/tag/0.70.0 "BADGE_BLUE"
[New in: rippled 0.70.2]: https://github.com/XRPLF/rippled/releases/tag/0.70.2 "BADGE_BLUE"
[New in: rippled 0.80.0]: https://github.com/XRPLF/rippled/releases/tag/0.80.0 "BADGE_BLUE"
[New in: rippled 0.80.1]: https://github.com/XRPLF/rippled/releases/tag/0.80.1 "BADGE_BLUE"
[New in: rippled 0.90.0]: https://github.com/XRPLF/rippled/releases/tag/0.90.0 "BADGE_BLUE"
[New in: rippled 1.0.0]: https://github.com/XRPLF/rippled/releases/tag/1.0.0 "BADGE_BLUE"
[New in: rippled 1.1.0]: https://github.com/XRPLF/rippled/releases/tag/1.1.0 "BADGE_BLUE"
[New in: rippled 1.10.0]: https://github.com/XRPLF/rippled/releases/tag/1.10.0 "BADGE_BLUE"
[New in: rippled 1.11.0]: https://github.com/XRPLF/rippled/releases/tag/1.11.0 "BADGE_BLUE"
[New in: rippled 1.12.0]: https://github.com/XRPLF/rippled/releases/tag/1.12.0 "BADGE_BLUE"
[New in: rippled 1.2.0]: https://github.com/XRPLF/rippled/releases/tag/1.2.0 "BADGE_BLUE"
[New in: rippled 1.2.1]: https://github.com/XRPLF/rippled/releases/tag/1.2.1 "BADGE_BLUE"
[New in: rippled 1.3.1]: https://github.com/XRPLF/rippled/releases/tag/1.3.1 "BADGE_BLUE"
[New in: rippled 1.4.0]: https://github.com/XRPLF/rippled/releases/tag/1.4.0 "BADGE_BLUE"
[New in: rippled 1.5.0]: https://github.com/XRPLF/rippled/releases/tag/1.5.0 "BADGE_BLUE"
[New in: rippled 1.6.0]: https://github.com/XRPLF/rippled/releases/tag/1.6.0 "BADGE_BLUE"
[New in: rippled 1.7.0]: https://github.com/XRPLF/rippled/releases/tag/1.7.0 "BADGE_BLUE"
[New in: rippled 1.7.2]: https://github.com/XRPLF/rippled/releases/tag/1.7.2 "BADGE_BLUE"
[New in: rippled 1.8.1]: https://github.com/XRPLF/rippled/releases/tag/1.8.1 "BADGE_BLUE"
[New in: rippled 2.0.0]: https://github.com/XRPLF/rippled/releases/tag/2.0.0 "BADGE_BLUE"
[NonFungibleTokensV1 amendment]: /resources/known-amendments.md#nonfungibletokensv1
[NonFungibleTokensV1_1 amendment]: /resources/known-amendments.md#nonfungibletokensv1_1
[NonFungibleTokensV1_1の修正]: /resources/known-amendments.md#nonfungibletokensv1_1
@@ -369,50 +281,6 @@
[Payment]: /references/protocol/transactions/types/payment.md
[Paymentトランザクション]: /references/protocol/transactions/types/payment.md
[RFC-1751]: https://tools.ietf.org/html/rfc1751
[Removed in: rippled 0.26.0]: https://github.com/XRPLF/rippled/releases/tag/0.26.0 "BADGE_RED"
[Removed in: rippled 0.26.1]: https://github.com/XRPLF/rippled/releases/tag/0.26.1 "BADGE_RED"
[Removed in: rippled 0.26.2]: https://github.com/XRPLF/rippled/releases/tag/0.26.2 "BADGE_RED"
[Removed in: rippled 0.26.3-sp1]: https://github.com/XRPLF/rippled/releases/tag/0.26.3-sp1 "BADGE_RED"
[Removed in: rippled 0.26.4-sp1]: https://github.com/XRPLF/rippled/releases/tag/0.26.4-sp1 "BADGE_RED"
[Removed in: rippled 0.26.4]: https://github.com/XRPLF/rippled/releases/tag/0.26.4 "BADGE_RED"
[Removed in: rippled 0.27.0]: https://github.com/XRPLF/rippled/releases/tag/0.27.0 "BADGE_RED"
[Removed in: rippled 0.27.1]: https://github.com/XRPLF/rippled/releases/tag/0.27.1 "BADGE_RED"
[Removed in: rippled 0.27.2]: https://github.com/XRPLF/rippled/releases/tag/0.27.2 "BADGE_RED"
[Removed in: rippled 0.27.3-sp1]: https://github.com/XRPLF/rippled/releases/tag/0.27.3-sp1 "BADGE_RED"
[Removed in: rippled 0.27.3-sp2]: https://github.com/XRPLF/rippled/releases/tag/0.27.3-sp2 "BADGE_RED"
[Removed in: rippled 0.27.3]: https://github.com/XRPLF/rippled/releases/tag/0.27.3 "BADGE_RED"
[Removed in: rippled 0.27.4]: https://github.com/XRPLF/rippled/releases/tag/0.27.4 "BADGE_RED"
[Removed in: rippled 0.28.0]: https://github.com/XRPLF/rippled/releases/tag/0.28.0 "BADGE_RED"
[Removed in: rippled 0.28.2]: https://github.com/XRPLF/rippled/releases/tag/0.28.2 "BADGE_RED"
[Removed in: rippled 0.29.0-hf1]: https://github.com/XRPLF/rippled/releases/tag/0.29.0-hf1 "BADGE_RED"
[Removed in: rippled 0.29.0]: https://github.com/XRPLF/rippled/releases/tag/0.29.0 "BADGE_RED"
[Removed in: rippled 0.30.0]: https://github.com/XRPLF/rippled/releases/tag/0.30.0 "BADGE_RED"
[Removed in: rippled 0.30.1]: https://github.com/XRPLF/rippled/releases/tag/0.30.1 "BADGE_RED"
[Removed in: rippled 0.31.0]: https://github.com/XRPLF/rippled/releases/tag/0.31.0 "BADGE_RED"
[Removed in: rippled 0.32.0]: https://github.com/XRPLF/rippled/releases/tag/0.32.0 "BADGE_RED"
[Removed in: rippled 0.32.1]: https://github.com/XRPLF/rippled/releases/tag/0.32.1 "BADGE_RED"
[Removed in: rippled 0.33.0]: https://github.com/XRPLF/rippled/releases/tag/0.33.0 "BADGE_RED"
[Removed in: rippled 0.50.0]: https://github.com/XRPLF/rippled/releases/tag/0.50.0 "BADGE_RED"
[Removed in: rippled 0.70.0]: https://github.com/XRPLF/rippled/releases/tag/0.70.0 "BADGE_RED"
[Removed in: rippled 0.70.2]: https://github.com/XRPLF/rippled/releases/tag/0.70.2 "BADGE_RED"
[Removed in: rippled 0.80.0]: https://github.com/XRPLF/rippled/releases/tag/0.80.0 "BADGE_RED"
[Removed in: rippled 0.80.1]: https://github.com/XRPLF/rippled/releases/tag/0.80.1 "BADGE_RED"
[Removed in: rippled 0.90.0]: https://github.com/XRPLF/rippled/releases/tag/0.90.0 "BADGE_RED"
[Removed in: rippled 1.0.0]: https://github.com/XRPLF/rippled/releases/tag/1.0.0 "BADGE_RED"
[Removed in: rippled 1.1.0]: https://github.com/XRPLF/rippled/releases/tag/1.1.0 "BADGE_RED"
[Removed in: rippled 1.10.0]: https://github.com/XRPLF/rippled/releases/tag/1.10.0 "BADGE_RED"
[Removed in: rippled 1.11.0]: https://github.com/XRPLF/rippled/releases/tag/1.11.0 "BADGE_RED"
[Removed in: rippled 1.12.0]: https://github.com/XRPLF/rippled/releases/tag/1.12.0 "BADGE_RED"
[Removed in: rippled 1.2.0]: https://github.com/XRPLF/rippled/releases/tag/1.2.0 "BADGE_RED"
[Removed in: rippled 1.2.1]: https://github.com/XRPLF/rippled/releases/tag/1.2.1 "BADGE_RED"
[Removed in: rippled 1.3.1]: https://github.com/XRPLF/rippled/releases/tag/1.3.1 "BADGE_RED"
[Removed in: rippled 1.4.0]: https://github.com/XRPLF/rippled/releases/tag/1.4.0 "BADGE_RED"
[Removed in: rippled 1.5.0]: https://github.com/XRPLF/rippled/releases/tag/1.5.0 "BADGE_RED"
[Removed in: rippled 1.6.0]: https://github.com/XRPLF/rippled/releases/tag/1.6.0 "BADGE_RED"
[Removed in: rippled 1.7.0]: https://github.com/XRPLF/rippled/releases/tag/1.7.0 "BADGE_RED"
[Removed in: rippled 1.7.2]: https://github.com/XRPLF/rippled/releases/tag/1.7.2 "BADGE_RED"
[Removed in: rippled 1.8.1]: https://github.com/XRPLF/rippled/releases/tag/1.8.1 "BADGE_RED"
[Removed in: rippled 2.0.0]: https://github.com/XRPLF/rippled/releases/tag/2.0.0 "BADGE_RED"
[Reporting Mode]: /concepts/networks-and-servers/rippled-server-modes.md#reporting-mode
[RequireFullyCanonicalSig amendment]: /resources/known-amendments.md#requirefullycanonicalsig
[RequireFullyCanonicalSigの修正]: /resources/known-amendments.md#requirefullycanonicalsig
@@ -484,50 +352,6 @@
[UNLModify pseudo-transactions]: /references/protocol/transactions/pseudo-transaction-types/unlmodify.md
[UNLModify]: /references/protocol/transactions/pseudo-transaction-types/unlmodify.md
[UNLModify疑似トランザクション]: /references/protocol/transactions/pseudo-transaction-types/unlmodify.md
[Updated in: rippled 0.26.0]: https://github.com/XRPLF/rippled/releases/tag/0.26.0 "BADGE_BLUE"
[Updated in: rippled 0.26.1]: https://github.com/XRPLF/rippled/releases/tag/0.26.1 "BADGE_BLUE"
[Updated in: rippled 0.26.2]: https://github.com/XRPLF/rippled/releases/tag/0.26.2 "BADGE_BLUE"
[Updated in: rippled 0.26.3-sp1]: https://github.com/XRPLF/rippled/releases/tag/0.26.3-sp1 "BADGE_BLUE"
[Updated in: rippled 0.26.4-sp1]: https://github.com/XRPLF/rippled/releases/tag/0.26.4-sp1 "BADGE_BLUE"
[Updated in: rippled 0.26.4]: https://github.com/XRPLF/rippled/releases/tag/0.26.4 "BADGE_BLUE"
[Updated in: rippled 0.27.0]: https://github.com/XRPLF/rippled/releases/tag/0.27.0 "BADGE_BLUE"
[Updated in: rippled 0.27.1]: https://github.com/XRPLF/rippled/releases/tag/0.27.1 "BADGE_BLUE"
[Updated in: rippled 0.27.2]: https://github.com/XRPLF/rippled/releases/tag/0.27.2 "BADGE_BLUE"
[Updated in: rippled 0.27.3-sp1]: https://github.com/XRPLF/rippled/releases/tag/0.27.3-sp1 "BADGE_BLUE"
[Updated in: rippled 0.27.3-sp2]: https://github.com/XRPLF/rippled/releases/tag/0.27.3-sp2 "BADGE_BLUE"
[Updated in: rippled 0.27.3]: https://github.com/XRPLF/rippled/releases/tag/0.27.3 "BADGE_BLUE"
[Updated in: rippled 0.27.4]: https://github.com/XRPLF/rippled/releases/tag/0.27.4 "BADGE_BLUE"
[Updated in: rippled 0.28.0]: https://github.com/XRPLF/rippled/releases/tag/0.28.0 "BADGE_BLUE"
[Updated in: rippled 0.28.2]: https://github.com/XRPLF/rippled/releases/tag/0.28.2 "BADGE_BLUE"
[Updated in: rippled 0.29.0-hf1]: https://github.com/XRPLF/rippled/releases/tag/0.29.0-hf1 "BADGE_BLUE"
[Updated in: rippled 0.29.0]: https://github.com/XRPLF/rippled/releases/tag/0.29.0 "BADGE_BLUE"
[Updated in: rippled 0.30.0]: https://github.com/XRPLF/rippled/releases/tag/0.30.0 "BADGE_BLUE"
[Updated in: rippled 0.30.1]: https://github.com/XRPLF/rippled/releases/tag/0.30.1 "BADGE_BLUE"
[Updated in: rippled 0.31.0]: https://github.com/XRPLF/rippled/releases/tag/0.31.0 "BADGE_BLUE"
[Updated in: rippled 0.32.0]: https://github.com/XRPLF/rippled/releases/tag/0.32.0 "BADGE_BLUE"
[Updated in: rippled 0.32.1]: https://github.com/XRPLF/rippled/releases/tag/0.32.1 "BADGE_BLUE"
[Updated in: rippled 0.33.0]: https://github.com/XRPLF/rippled/releases/tag/0.33.0 "BADGE_BLUE"
[Updated in: rippled 0.50.0]: https://github.com/XRPLF/rippled/releases/tag/0.50.0 "BADGE_BLUE"
[Updated in: rippled 0.70.0]: https://github.com/XRPLF/rippled/releases/tag/0.70.0 "BADGE_BLUE"
[Updated in: rippled 0.70.2]: https://github.com/XRPLF/rippled/releases/tag/0.70.2 "BADGE_BLUE"
[Updated in: rippled 0.80.0]: https://github.com/XRPLF/rippled/releases/tag/0.80.0 "BADGE_BLUE"
[Updated in: rippled 0.80.1]: https://github.com/XRPLF/rippled/releases/tag/0.80.1 "BADGE_BLUE"
[Updated in: rippled 0.90.0]: https://github.com/XRPLF/rippled/releases/tag/0.90.0 "BADGE_BLUE"
[Updated in: rippled 1.0.0]: https://github.com/XRPLF/rippled/releases/tag/1.0.0 "BADGE_BLUE"
[Updated in: rippled 1.1.0]: https://github.com/XRPLF/rippled/releases/tag/1.1.0 "BADGE_BLUE"
[Updated in: rippled 1.10.0]: https://github.com/XRPLF/rippled/releases/tag/1.10.0 "BADGE_BLUE"
[Updated in: rippled 1.11.0]: https://github.com/XRPLF/rippled/releases/tag/1.11.0 "BADGE_BLUE"
[Updated in: rippled 1.12.0]: https://github.com/XRPLF/rippled/releases/tag/1.12.0 "BADGE_BLUE"
[Updated in: rippled 1.2.0]: https://github.com/XRPLF/rippled/releases/tag/1.2.0 "BADGE_BLUE"
[Updated in: rippled 1.2.1]: https://github.com/XRPLF/rippled/releases/tag/1.2.1 "BADGE_BLUE"
[Updated in: rippled 1.3.1]: https://github.com/XRPLF/rippled/releases/tag/1.3.1 "BADGE_BLUE"
[Updated in: rippled 1.4.0]: https://github.com/XRPLF/rippled/releases/tag/1.4.0 "BADGE_BLUE"
[Updated in: rippled 1.5.0]: https://github.com/XRPLF/rippled/releases/tag/1.5.0 "BADGE_BLUE"
[Updated in: rippled 1.6.0]: https://github.com/XRPLF/rippled/releases/tag/1.6.0 "BADGE_BLUE"
[Updated in: rippled 1.7.0]: https://github.com/XRPLF/rippled/releases/tag/1.7.0 "BADGE_BLUE"
[Updated in: rippled 1.7.2]: https://github.com/XRPLF/rippled/releases/tag/1.7.2 "BADGE_BLUE"
[Updated in: rippled 1.8.1]: https://github.com/XRPLF/rippled/releases/tag/1.8.1 "BADGE_BLUE"
[Updated in: rippled 2.0.0]: https://github.com/XRPLF/rippled/releases/tag/2.0.0 "BADGE_BLUE"
[XChainBridge amendment]: /resources/known-amendments.md#xchainbridge
[XChainBridgeの修正]: /resources/known-amendments.md#xchainbridge
[XRP, in drops]: /references/protocol/data-types/basic-data-types.md#specifying-currency-amounts
@@ -880,184 +704,8 @@
[公開サーバー]: /tutorials/get-started/public-servers.md
[共通フィールド]: /references/protocol/transactions/common-fields.md
[内部の型]: /references/protocol/binary-format.md
[削除: rippled 0.26.0]: https://github.com/XRPLF/rippled/releases/tag/0.26.0 "BADGE_RED"
[削除: rippled 0.26.1]: https://github.com/XRPLF/rippled/releases/tag/0.26.1 "BADGE_RED"
[削除: rippled 0.26.2]: https://github.com/XRPLF/rippled/releases/tag/0.26.2 "BADGE_RED"
[削除: rippled 0.26.3-sp1]: https://github.com/XRPLF/rippled/releases/tag/0.26.3-sp1 "BADGE_RED"
[削除: rippled 0.26.4-sp1]: https://github.com/XRPLF/rippled/releases/tag/0.26.4-sp1 "BADGE_RED"
[削除: rippled 0.26.4]: https://github.com/XRPLF/rippled/releases/tag/0.26.4 "BADGE_RED"
[削除: rippled 0.27.0]: https://github.com/XRPLF/rippled/releases/tag/0.27.0 "BADGE_RED"
[削除: rippled 0.27.1]: https://github.com/XRPLF/rippled/releases/tag/0.27.1 "BADGE_RED"
[削除: rippled 0.27.2]: https://github.com/XRPLF/rippled/releases/tag/0.27.2 "BADGE_RED"
[削除: rippled 0.27.3-sp1]: https://github.com/XRPLF/rippled/releases/tag/0.27.3-sp1 "BADGE_RED"
[削除: rippled 0.27.3-sp2]: https://github.com/XRPLF/rippled/releases/tag/0.27.3-sp2 "BADGE_RED"
[削除: rippled 0.27.3]: https://github.com/XRPLF/rippled/releases/tag/0.27.3 "BADGE_RED"
[削除: rippled 0.27.4]: https://github.com/XRPLF/rippled/releases/tag/0.27.4 "BADGE_RED"
[削除: rippled 0.28.0]: https://github.com/XRPLF/rippled/releases/tag/0.28.0 "BADGE_RED"
[削除: rippled 0.28.2]: https://github.com/XRPLF/rippled/releases/tag/0.28.2 "BADGE_RED"
[削除: rippled 0.29.0-hf1]: https://github.com/XRPLF/rippled/releases/tag/0.29.0-hf1 "BADGE_RED"
[削除: rippled 0.29.0]: https://github.com/XRPLF/rippled/releases/tag/0.29.0 "BADGE_RED"
[削除: rippled 0.30.0]: https://github.com/XRPLF/rippled/releases/tag/0.30.0 "BADGE_RED"
[削除: rippled 0.30.1]: https://github.com/XRPLF/rippled/releases/tag/0.30.1 "BADGE_RED"
[削除: rippled 0.31.0]: https://github.com/XRPLF/rippled/releases/tag/0.31.0 "BADGE_RED"
[削除: rippled 0.32.0]: https://github.com/XRPLF/rippled/releases/tag/0.32.0 "BADGE_RED"
[削除: rippled 0.32.1]: https://github.com/XRPLF/rippled/releases/tag/0.32.1 "BADGE_RED"
[削除: rippled 0.33.0]: https://github.com/XRPLF/rippled/releases/tag/0.33.0 "BADGE_RED"
[削除: rippled 0.50.0]: https://github.com/XRPLF/rippled/releases/tag/0.50.0 "BADGE_RED"
[削除: rippled 0.70.0]: https://github.com/XRPLF/rippled/releases/tag/0.70.0 "BADGE_RED"
[削除: rippled 0.70.2]: https://github.com/XRPLF/rippled/releases/tag/0.70.2 "BADGE_RED"
[削除: rippled 0.80.0]: https://github.com/XRPLF/rippled/releases/tag/0.80.0 "BADGE_RED"
[削除: rippled 0.80.1]: https://github.com/XRPLF/rippled/releases/tag/0.80.1 "BADGE_RED"
[削除: rippled 0.90.0]: https://github.com/XRPLF/rippled/releases/tag/0.90.0 "BADGE_RED"
[削除: rippled 1.0.0]: https://github.com/XRPLF/rippled/releases/tag/1.0.0 "BADGE_RED"
[削除: rippled 1.1.0]: https://github.com/XRPLF/rippled/releases/tag/1.1.0 "BADGE_RED"
[削除: rippled 1.10.0]: https://github.com/XRPLF/rippled/releases/tag/1.10.0 "BADGE_RED"
[削除: rippled 1.11.0]: https://github.com/XRPLF/rippled/releases/tag/1.11.0 "BADGE_RED"
[削除: rippled 1.12.0]: https://github.com/XRPLF/rippled/releases/tag/1.12.0 "BADGE_RED"
[削除: rippled 1.2.0]: https://github.com/XRPLF/rippled/releases/tag/1.2.0 "BADGE_RED"
[削除: rippled 1.2.1]: https://github.com/XRPLF/rippled/releases/tag/1.2.1 "BADGE_RED"
[削除: rippled 1.3.1]: https://github.com/XRPLF/rippled/releases/tag/1.3.1 "BADGE_RED"
[削除: rippled 1.4.0]: https://github.com/XRPLF/rippled/releases/tag/1.4.0 "BADGE_RED"
[削除: rippled 1.5.0]: https://github.com/XRPLF/rippled/releases/tag/1.5.0 "BADGE_RED"
[削除: rippled 1.6.0]: https://github.com/XRPLF/rippled/releases/tag/1.6.0 "BADGE_RED"
[削除: rippled 1.7.0]: https://github.com/XRPLF/rippled/releases/tag/1.7.0 "BADGE_RED"
[削除: rippled 1.7.2]: https://github.com/XRPLF/rippled/releases/tag/1.7.2 "BADGE_RED"
[削除: rippled 1.8.1]: https://github.com/XRPLF/rippled/releases/tag/1.8.1 "BADGE_RED"
[削除: rippled 2.0.0]: https://github.com/XRPLF/rippled/releases/tag/2.0.0 "BADGE_RED"
[導入: rippled 0.26.0]: https://github.com/XRPLF/rippled/releases/tag/0.26.0 "BADGE_BLUE"
[導入: rippled 0.26.1]: https://github.com/XRPLF/rippled/releases/tag/0.26.1 "BADGE_BLUE"
[導入: rippled 0.26.2]: https://github.com/XRPLF/rippled/releases/tag/0.26.2 "BADGE_BLUE"
[導入: rippled 0.26.3-sp1]: https://github.com/XRPLF/rippled/releases/tag/0.26.3-sp1 "BADGE_BLUE"
[導入: rippled 0.26.4-sp1]: https://github.com/XRPLF/rippled/releases/tag/0.26.4-sp1 "BADGE_BLUE"
[導入: rippled 0.26.4]: https://github.com/XRPLF/rippled/releases/tag/0.26.4 "BADGE_BLUE"
[導入: rippled 0.27.0]: https://github.com/XRPLF/rippled/releases/tag/0.27.0 "BADGE_BLUE"
[導入: rippled 0.27.1]: https://github.com/XRPLF/rippled/releases/tag/0.27.1 "BADGE_BLUE"
[導入: rippled 0.27.2]: https://github.com/XRPLF/rippled/releases/tag/0.27.2 "BADGE_BLUE"
[導入: rippled 0.27.3-sp1]: https://github.com/XRPLF/rippled/releases/tag/0.27.3-sp1 "BADGE_BLUE"
[導入: rippled 0.27.3-sp2]: https://github.com/XRPLF/rippled/releases/tag/0.27.3-sp2 "BADGE_BLUE"
[導入: rippled 0.27.3]: https://github.com/XRPLF/rippled/releases/tag/0.27.3 "BADGE_BLUE"
[導入: rippled 0.27.4]: https://github.com/XRPLF/rippled/releases/tag/0.27.4 "BADGE_BLUE"
[導入: rippled 0.28.0]: https://github.com/XRPLF/rippled/releases/tag/0.28.0 "BADGE_BLUE"
[導入: rippled 0.28.2]: https://github.com/XRPLF/rippled/releases/tag/0.28.2 "BADGE_BLUE"
[導入: rippled 0.29.0-hf1]: https://github.com/XRPLF/rippled/releases/tag/0.29.0-hf1 "BADGE_BLUE"
[導入: rippled 0.29.0]: https://github.com/XRPLF/rippled/releases/tag/0.29.0 "BADGE_BLUE"
[導入: rippled 0.30.0]: https://github.com/XRPLF/rippled/releases/tag/0.30.0 "BADGE_BLUE"
[導入: rippled 0.30.1]: https://github.com/XRPLF/rippled/releases/tag/0.30.1 "BADGE_BLUE"
[導入: rippled 0.31.0]: https://github.com/XRPLF/rippled/releases/tag/0.31.0 "BADGE_BLUE"
[導入: rippled 0.32.0]: https://github.com/XRPLF/rippled/releases/tag/0.32.0 "BADGE_BLUE"
[導入: rippled 0.32.1]: https://github.com/XRPLF/rippled/releases/tag/0.32.1 "BADGE_BLUE"
[導入: rippled 0.33.0]: https://github.com/XRPLF/rippled/releases/tag/0.33.0 "BADGE_BLUE"
[導入: rippled 0.50.0]: https://github.com/XRPLF/rippled/releases/tag/0.50.0 "BADGE_BLUE"
[導入: rippled 0.70.0]: https://github.com/XRPLF/rippled/releases/tag/0.70.0 "BADGE_BLUE"
[導入: rippled 0.70.2]: https://github.com/XRPLF/rippled/releases/tag/0.70.2 "BADGE_BLUE"
[導入: rippled 0.80.0]: https://github.com/XRPLF/rippled/releases/tag/0.80.0 "BADGE_BLUE"
[導入: rippled 0.80.1]: https://github.com/XRPLF/rippled/releases/tag/0.80.1 "BADGE_BLUE"
[導入: rippled 0.90.0]: https://github.com/XRPLF/rippled/releases/tag/0.90.0 "BADGE_BLUE"
[導入: rippled 1.0.0]: https://github.com/XRPLF/rippled/releases/tag/1.0.0 "BADGE_BLUE"
[導入: rippled 1.1.0]: https://github.com/XRPLF/rippled/releases/tag/1.1.0 "BADGE_BLUE"
[導入: rippled 1.10.0]: https://github.com/XRPLF/rippled/releases/tag/1.10.0 "BADGE_BLUE"
[導入: rippled 1.11.0]: https://github.com/XRPLF/rippled/releases/tag/1.11.0 "BADGE_BLUE"
[導入: rippled 1.12.0]: https://github.com/XRPLF/rippled/releases/tag/1.12.0 "BADGE_BLUE"
[導入: rippled 1.2.0]: https://github.com/XRPLF/rippled/releases/tag/1.2.0 "BADGE_BLUE"
[導入: rippled 1.2.1]: https://github.com/XRPLF/rippled/releases/tag/1.2.1 "BADGE_BLUE"
[導入: rippled 1.3.1]: https://github.com/XRPLF/rippled/releases/tag/1.3.1 "BADGE_BLUE"
[導入: rippled 1.4.0]: https://github.com/XRPLF/rippled/releases/tag/1.4.0 "BADGE_BLUE"
[導入: rippled 1.5.0]: https://github.com/XRPLF/rippled/releases/tag/1.5.0 "BADGE_BLUE"
[導入: rippled 1.6.0]: https://github.com/XRPLF/rippled/releases/tag/1.6.0 "BADGE_BLUE"
[導入: rippled 1.7.0]: https://github.com/XRPLF/rippled/releases/tag/1.7.0 "BADGE_BLUE"
[導入: rippled 1.7.2]: https://github.com/XRPLF/rippled/releases/tag/1.7.2 "BADGE_BLUE"
[導入: rippled 1.8.1]: https://github.com/XRPLF/rippled/releases/tag/1.8.1 "BADGE_BLUE"
[導入: rippled 2.0.0]: https://github.com/XRPLF/rippled/releases/tag/2.0.0 "BADGE_BLUE"
[手数料レベル]: /concepts/transactions/transaction-cost.md#手数料レベル
[新規: rippled 0.26.0]: https://github.com/XRPLF/rippled/releases/tag/0.26.0 "BADGE_BLUE"
[新規: rippled 0.26.1]: https://github.com/XRPLF/rippled/releases/tag/0.26.1 "BADGE_BLUE"
[新規: rippled 0.26.2]: https://github.com/XRPLF/rippled/releases/tag/0.26.2 "BADGE_BLUE"
[新規: rippled 0.26.3-sp1]: https://github.com/XRPLF/rippled/releases/tag/0.26.3-sp1 "BADGE_BLUE"
[新規: rippled 0.26.4-sp1]: https://github.com/XRPLF/rippled/releases/tag/0.26.4-sp1 "BADGE_BLUE"
[新規: rippled 0.26.4]: https://github.com/XRPLF/rippled/releases/tag/0.26.4 "BADGE_BLUE"
[新規: rippled 0.27.0]: https://github.com/XRPLF/rippled/releases/tag/0.27.0 "BADGE_BLUE"
[新規: rippled 0.27.1]: https://github.com/XRPLF/rippled/releases/tag/0.27.1 "BADGE_BLUE"
[新規: rippled 0.27.2]: https://github.com/XRPLF/rippled/releases/tag/0.27.2 "BADGE_BLUE"
[新規: rippled 0.27.3-sp1]: https://github.com/XRPLF/rippled/releases/tag/0.27.3-sp1 "BADGE_BLUE"
[新規: rippled 0.27.3-sp2]: https://github.com/XRPLF/rippled/releases/tag/0.27.3-sp2 "BADGE_BLUE"
[新規: rippled 0.27.3]: https://github.com/XRPLF/rippled/releases/tag/0.27.3 "BADGE_BLUE"
[新規: rippled 0.27.4]: https://github.com/XRPLF/rippled/releases/tag/0.27.4 "BADGE_BLUE"
[新規: rippled 0.28.0]: https://github.com/XRPLF/rippled/releases/tag/0.28.0 "BADGE_BLUE"
[新規: rippled 0.28.2]: https://github.com/XRPLF/rippled/releases/tag/0.28.2 "BADGE_BLUE"
[新規: rippled 0.29.0-hf1]: https://github.com/XRPLF/rippled/releases/tag/0.29.0-hf1 "BADGE_BLUE"
[新規: rippled 0.29.0]: https://github.com/XRPLF/rippled/releases/tag/0.29.0 "BADGE_BLUE"
[新規: rippled 0.30.0]: https://github.com/XRPLF/rippled/releases/tag/0.30.0 "BADGE_BLUE"
[新規: rippled 0.30.1]: https://github.com/XRPLF/rippled/releases/tag/0.30.1 "BADGE_BLUE"
[新規: rippled 0.31.0]: https://github.com/XRPLF/rippled/releases/tag/0.31.0 "BADGE_BLUE"
[新規: rippled 0.32.0]: https://github.com/XRPLF/rippled/releases/tag/0.32.0 "BADGE_BLUE"
[新規: rippled 0.32.1]: https://github.com/XRPLF/rippled/releases/tag/0.32.1 "BADGE_BLUE"
[新規: rippled 0.33.0]: https://github.com/XRPLF/rippled/releases/tag/0.33.0 "BADGE_BLUE"
[新規: rippled 0.50.0]: https://github.com/XRPLF/rippled/releases/tag/0.50.0 "BADGE_BLUE"
[新規: rippled 0.70.0]: https://github.com/XRPLF/rippled/releases/tag/0.70.0 "BADGE_BLUE"
[新規: rippled 0.70.2]: https://github.com/XRPLF/rippled/releases/tag/0.70.2 "BADGE_BLUE"
[新規: rippled 0.80.0]: https://github.com/XRPLF/rippled/releases/tag/0.80.0 "BADGE_BLUE"
[新規: rippled 0.80.1]: https://github.com/XRPLF/rippled/releases/tag/0.80.1 "BADGE_BLUE"
[新規: rippled 0.90.0]: https://github.com/XRPLF/rippled/releases/tag/0.90.0 "BADGE_BLUE"
[新規: rippled 1.0.0]: https://github.com/XRPLF/rippled/releases/tag/1.0.0 "BADGE_BLUE"
[新規: rippled 1.1.0]: https://github.com/XRPLF/rippled/releases/tag/1.1.0 "BADGE_BLUE"
[新規: rippled 1.10.0]: https://github.com/XRPLF/rippled/releases/tag/1.10.0 "BADGE_BLUE"
[新規: rippled 1.11.0]: https://github.com/XRPLF/rippled/releases/tag/1.11.0 "BADGE_BLUE"
[新規: rippled 1.12.0]: https://github.com/XRPLF/rippled/releases/tag/1.12.0 "BADGE_BLUE"
[新規: rippled 1.2.0]: https://github.com/XRPLF/rippled/releases/tag/1.2.0 "BADGE_BLUE"
[新規: rippled 1.2.1]: https://github.com/XRPLF/rippled/releases/tag/1.2.1 "BADGE_BLUE"
[新規: rippled 1.3.1]: https://github.com/XRPLF/rippled/releases/tag/1.3.1 "BADGE_BLUE"
[新規: rippled 1.4.0]: https://github.com/XRPLF/rippled/releases/tag/1.4.0 "BADGE_BLUE"
[新規: rippled 1.5.0]: https://github.com/XRPLF/rippled/releases/tag/1.5.0 "BADGE_BLUE"
[新規: rippled 1.6.0]: https://github.com/XRPLF/rippled/releases/tag/1.6.0 "BADGE_BLUE"
[新規: rippled 1.7.0]: https://github.com/XRPLF/rippled/releases/tag/1.7.0 "BADGE_BLUE"
[新規: rippled 1.7.2]: https://github.com/XRPLF/rippled/releases/tag/1.7.2 "BADGE_BLUE"
[新規: rippled 1.8.1]: https://github.com/XRPLF/rippled/releases/tag/1.8.1 "BADGE_BLUE"
[新規: rippled 2.0.0]: https://github.com/XRPLF/rippled/releases/tag/2.0.0 "BADGE_BLUE"
[時間の指定]: /references/protocol/data-types/basic-data-types.md#時間の指定
[更新: rippled 0.26.0]: https://github.com/XRPLF/rippled/releases/tag/0.26.0 "BADGE_BLUE"
[更新: rippled 0.26.1]: https://github.com/XRPLF/rippled/releases/tag/0.26.1 "BADGE_BLUE"
[更新: rippled 0.26.2]: https://github.com/XRPLF/rippled/releases/tag/0.26.2 "BADGE_BLUE"
[更新: rippled 0.26.3-sp1]: https://github.com/XRPLF/rippled/releases/tag/0.26.3-sp1 "BADGE_BLUE"
[更新: rippled 0.26.4-sp1]: https://github.com/XRPLF/rippled/releases/tag/0.26.4-sp1 "BADGE_BLUE"
[更新: rippled 0.26.4]: https://github.com/XRPLF/rippled/releases/tag/0.26.4 "BADGE_BLUE"
[更新: rippled 0.27.0]: https://github.com/XRPLF/rippled/releases/tag/0.27.0 "BADGE_BLUE"
[更新: rippled 0.27.1]: https://github.com/XRPLF/rippled/releases/tag/0.27.1 "BADGE_BLUE"
[更新: rippled 0.27.2]: https://github.com/XRPLF/rippled/releases/tag/0.27.2 "BADGE_BLUE"
[更新: rippled 0.27.3-sp1]: https://github.com/XRPLF/rippled/releases/tag/0.27.3-sp1 "BADGE_BLUE"
[更新: rippled 0.27.3-sp2]: https://github.com/XRPLF/rippled/releases/tag/0.27.3-sp2 "BADGE_BLUE"
[更新: rippled 0.27.3]: https://github.com/XRPLF/rippled/releases/tag/0.27.3 "BADGE_BLUE"
[更新: rippled 0.27.4]: https://github.com/XRPLF/rippled/releases/tag/0.27.4 "BADGE_BLUE"
[更新: rippled 0.28.0]: https://github.com/XRPLF/rippled/releases/tag/0.28.0 "BADGE_BLUE"
[更新: rippled 0.28.2]: https://github.com/XRPLF/rippled/releases/tag/0.28.2 "BADGE_BLUE"
[更新: rippled 0.29.0-hf1]: https://github.com/XRPLF/rippled/releases/tag/0.29.0-hf1 "BADGE_BLUE"
[更新: rippled 0.29.0]: https://github.com/XRPLF/rippled/releases/tag/0.29.0 "BADGE_BLUE"
[更新: rippled 0.30.0]: https://github.com/XRPLF/rippled/releases/tag/0.30.0 "BADGE_BLUE"
[更新: rippled 0.30.1]: https://github.com/XRPLF/rippled/releases/tag/0.30.1 "BADGE_BLUE"
[更新: rippled 0.31.0]: https://github.com/XRPLF/rippled/releases/tag/0.31.0 "BADGE_BLUE"
[更新: rippled 0.32.0]: https://github.com/XRPLF/rippled/releases/tag/0.32.0 "BADGE_BLUE"
[更新: rippled 0.32.1]: https://github.com/XRPLF/rippled/releases/tag/0.32.1 "BADGE_BLUE"
[更新: rippled 0.33.0]: https://github.com/XRPLF/rippled/releases/tag/0.33.0 "BADGE_BLUE"
[更新: rippled 0.50.0]: https://github.com/XRPLF/rippled/releases/tag/0.50.0 "BADGE_BLUE"
[更新: rippled 0.70.0]: https://github.com/XRPLF/rippled/releases/tag/0.70.0 "BADGE_BLUE"
[更新: rippled 0.70.2]: https://github.com/XRPLF/rippled/releases/tag/0.70.2 "BADGE_BLUE"
[更新: rippled 0.80.0]: https://github.com/XRPLF/rippled/releases/tag/0.80.0 "BADGE_BLUE"
[更新: rippled 0.80.1]: https://github.com/XRPLF/rippled/releases/tag/0.80.1 "BADGE_BLUE"
[更新: rippled 0.90.0]: https://github.com/XRPLF/rippled/releases/tag/0.90.0 "BADGE_BLUE"
[更新: rippled 1.0.0]: https://github.com/XRPLF/rippled/releases/tag/1.0.0 "BADGE_BLUE"
[更新: rippled 1.1.0]: https://github.com/XRPLF/rippled/releases/tag/1.1.0 "BADGE_BLUE"
[更新: rippled 1.10.0]: https://github.com/XRPLF/rippled/releases/tag/1.10.0 "BADGE_BLUE"
[更新: rippled 1.11.0]: https://github.com/XRPLF/rippled/releases/tag/1.11.0 "BADGE_BLUE"
[更新: rippled 1.12.0]: https://github.com/XRPLF/rippled/releases/tag/1.12.0 "BADGE_BLUE"
[更新: rippled 1.2.0]: https://github.com/XRPLF/rippled/releases/tag/1.2.0 "BADGE_BLUE"
[更新: rippled 1.2.1]: https://github.com/XRPLF/rippled/releases/tag/1.2.1 "BADGE_BLUE"
[更新: rippled 1.3.1]: https://github.com/XRPLF/rippled/releases/tag/1.3.1 "BADGE_BLUE"
[更新: rippled 1.4.0]: https://github.com/XRPLF/rippled/releases/tag/1.4.0 "BADGE_BLUE"
[更新: rippled 1.5.0]: https://github.com/XRPLF/rippled/releases/tag/1.5.0 "BADGE_BLUE"
[更新: rippled 1.6.0]: https://github.com/XRPLF/rippled/releases/tag/1.6.0 "BADGE_BLUE"
[更新: rippled 1.7.0]: https://github.com/XRPLF/rippled/releases/tag/1.7.0 "BADGE_BLUE"
[更新: rippled 1.7.2]: https://github.com/XRPLF/rippled/releases/tag/1.7.2 "BADGE_BLUE"
[更新: rippled 1.8.1]: https://github.com/XRPLF/rippled/releases/tag/1.8.1 "BADGE_BLUE"
[更新: rippled 2.0.0]: https://github.com/XRPLF/rippled/releases/tag/2.0.0 "BADGE_BLUE"
[標準フォーマット]: /references/http-websocket-apis/api-conventions/response-formatting.md
[汎用エラータイプ]: /references/http-websocket-apis/api-conventions/error-formatting.md#汎用エラー
[識別用ハッシュ]: /concepts/transactions/index.md#トランザクションの識別

View File

@@ -63,7 +63,7 @@ The node key pair also identifies other servers for purposes of [clustering](clu
Normally, a `rippled` server attempts to maintain a healthy number of peers, and automatically connects to untrusted peers up to a maximum number. You can configure a `rippled` server to remain connected to specific peer servers in several ways:
- Use **Fixed Peers** to remain always connected to specific other peers based on their IP addresses. This only works if the peers have fixed IP addresses. Use the `[ips_fixed]` config stanza to configure fixed peers. This is a necessary part of [clustering](clustering.md) or [private peers](#private-peers). Fixed peers are defined in the config file, so changes only apply after restarting the server. Fixed peers are most useful for keeping servers connected if those servers are run by the same person or organization.
- Use **Peer Reservations** to prioritize specific peers. If your server has a peer reservation for a specific peer, then your server always accepts connection requests from that peer even if your server is already at its maximum number of connected peers. (This can cause your server to go _over_ the maximum number of peers.) You identify a reserved peer by its [node key pair](#node-key-pair), so you can do this even for peers with variable IP addresses. Peer reservations are configured through admin commands and saved in the server databases, so they can be adjusted while the server is online and are saved across restarts. Peer reservations are most useful for connecting servers run by different people or organizations. {% badge href="https://github.com/XRPLF/rippled/releases/tag/1.4.0" %}New in: rippled 1.4.0{% /badge %} <!-- STYLE_OVERRIDE: prioritize -->
- Use **Peer Reservations** to prioritize specific peers. If your server has a peer reservation for a specific peer, then your server always accepts connection requests from that peer even if your server is already at its maximum number of connected peers. (This can cause your server to go _over_ the maximum number of peers.) You identify a reserved peer by its [node key pair](#node-key-pair), so you can do this even for peers with variable IP addresses. Peer reservations are configured through admin commands and saved in the server databases, so they can be adjusted while the server is online and are saved across restarts. Peer reservations are most useful for connecting servers run by different people or organizations. <!-- STYLE_OVERRIDE: prioritize -->
In the following cases, a `rippled` server does not connect to untrusted peers:
@@ -83,7 +83,7 @@ Configuring a server as a private server has several effects:
- The server does not accept incoming connections from other servers unless it has been explicitly configured to accept connections from those servers.
- The server asks its direct peers not to reveal its IP address in untrusted communications, including the [peer crawler API response](../../references/http-websocket-apis/peer-port-methods/peer-crawler.md). This does not affect trusted communications such as the [peers admin method][peers method].
Validators always ask their peers to hide the validators' IP addresses, regardless of the private server settings. This helps protect validators from being overloaded by denial of service attacks. {% badge href="https://github.com/XRPLF/rippled/releases/tag/1.2.1" %}New in: rippled 1.2.1{% /badge %}
Validators always ask their peers to hide the validators' IP addresses, regardless of the private server settings. This helps protect validators from being overloaded by denial of service attacks.
**Caution:** It is possible to modify a server's source code so that it ignores this request and shares its immediate peers' IP addresses anyway. You should configure your private server to connect only to servers that you know are not modified in this way.

View File

@@ -13,7 +13,7 @@ The `rippled` server software can run in several modes depending on its configur
- [**Validator**](#validators) - Helps secure the network by participating in consensus.
- [**API Server**](#api-servers) - Provides [API access](../../tutorials/get-started/get-started-using-http-websocket-apis.md) to read data from the shared ledger, submit transactions, and watch activity in the ledger. Optionally, this can be a [**Full History Server**](#full-history-servers), which keeps a complete record of transaction and ledger history.
- [**Hub Server**](#public-hubs) - Relays messages between many other members of the peer-to-peer network.
- [**Reporting mode**](#reporting-mode) - A specialized mode for serving API requests from a relational database. It does not participate in the peer-to-peer network, so you need to run a P2P Mode server and connect the reporting mode server using a trusted gRPC connection. {% badge href="https://github.com/XRPLF/rippled/releases/tag/1.7.0" %}New in: rippled 1.7.0{% /badge %}
- [**Reporting mode**](#reporting-mode) - A specialized mode for serving API requests from a relational database. It does not participate in the peer-to-peer network, so you need to run a P2P Mode server and connect the reporting mode server using a trusted gRPC connection.
- [**Stand-alone mode**](#stand-alone-mode) - An offline mode for testing. Does not connect to the peer-to-peer network or use consensus.
You can also run the `rippled` executable as a client application for accessing [`rippled` APIs](../../references/http-websocket-apis/index.md) locally. (Two instances of the same binary can run side-by-side in this case; one as a server, and the other running briefly as a client and then terminating.)
@@ -68,7 +68,7 @@ For more information about running a validator, see [Run `rippled` as a Validato
## Reporting Mode
{% badge href="https://github.com/XRPLF/rippled/releases/tag/1.7.0" %}New in: rippled 1.7.0{% /badge %}
Reporting mode is specialized mode for serving API requests more efficiently. In this mode, the server gets the latest validated ledger data over [gRPC](../../infrastructure/configuration/configure-grpc.md) from a separate `rippled` server running in P2P Mode, then loads that data into a relational database ([PostgreSQL](https://www.postgresql.org/)). The reporting mode server does not directly participate in the peer-to-peer network, though it can forward requests such as transaction submission to the P2P Mode server it uses.

View File

@@ -74,8 +74,8 @@ You can find the `delivered_amount` field in the following places:
| [JSON-RPC / WebSocket][] | [account_tx method][] | `result.transactions` array members' `meta.delivered_amount` |
| [JSON-RPC / WebSocket][] | [tx method][] | `result.meta.delivered_amount` |
| [JSON-RPC / WebSocket][] | [transaction_entry method][] | `result.metadata.delivered_amount` |
| [JSON-RPC / WebSocket][] | [ledger method][] (with transactions expanded) | `result.ledger.transactions` array members' `metaData.delivered_amount` {% badge href="https://github.com/XRPLF/rippled/releases/tag/1.2.1" %}New in: rippled 1.2.1{% /badge %} |
| [WebSocket][] | [Transaction subscriptions](../../references/http-websocket-apis/public-api-methods/subscription-methods/subscribe.md#transaction-streams) | Subscription messages' `meta.delivered_amount` {% badge href="https://github.com/XRPLF/rippled/releases/tag/1.2.1" %}New in: rippled 1.2.1{% /badge %} |
| [JSON-RPC / WebSocket][] | [ledger method][] (with transactions expanded) | `result.ledger.transactions` array members' `metaData.delivered_amount` |
| [WebSocket][] | [Transaction subscriptions](../../references/http-websocket-apis/public-api-methods/subscription-methods/subscribe.md#transaction-streams) | Subscription messages' `meta.delivered_amount` |
| ripple-lib v1.x | `getTransaction` method | `outcome.deliveredAmount` |
| ripple-lib v1.x | `getTransactions` method | array members' `outcome.deliveredAmount` |

View File

@@ -138,7 +138,7 @@ While running unit tests, you can specify the [Generic Options](#generic-options
| Option | Short Version | Description |
|:-----------------------------------|:--------------|:------------------------|
| `--unittest-ipv6` | | Use [IPv6](https://en.wikipedia.org/wiki/IPv6) to connect to the local server when running unit tests. If not provided, unit tests use IPv4 instead. {% badge href="https://github.com/XRPLF/rippled/releases/tag/1.1.0" %}New in: rippled 1.1.0{% /badge %} |
| `--unittest-ipv6` | | Use [IPv6](https://en.wikipedia.org/wiki/IPv6) to connect to the local server when running unit tests. If not provided, unit tests use IPv4 instead. |
| `--unittest-jobs {NUMBER_OF_JOBS}` | | Use the specified number of processes to run unit tests. This can finish running tests faster on multi-core systems. The `{NUMBER_OF_JOBS}` should be a positive integer indicating the number of processes to use. |
| `--unittest-log` | | Allow unit tests to write to logs even if `--quiet` is specified. (No effect otherwise.) |
| `--quiet` | `-q` | Print fewer diagnostic messages when running unit tests. |

View File

@@ -25,7 +25,7 @@ Before you configure your `rippled` server to store history shards, you must dec
- The history shard store and the ledger store _MUST_ be stored at different file paths. You can configure the ledger store and history store to be on different disks or partitions if desired.
- It is possible but redundant to hold full ledger history in both the ledger store and the history shard store.
- The time to acquire a shard, number of file handles needed by the `rippled` server, and memory cache usage is directly affected by the size of the shard.
- You can specify additional paths to store older history shards by providing a `[historical_shard_paths]` stanza. These paths may be on different, slower disks because they hold data that is used less often. The most recent two shards (the ones with the largest ledger indexes) are always stored in the path specified in the `[shard_db]` stanza. {% badge href="https://github.com/XRPLF/rippled/releases/tag/1.7.0" %}New in: rippled 1.7.0{% /badge %}
- You can specify additional paths to store older history shards by providing a `[historical_shard_paths]` stanza. These paths may be on different, slower disks because they hold data that is used less often. The most recent two shards (the ones with the largest ledger indexes) are always stored in the path specified in the `[shard_db]` stanza.
## 2. Edit rippled.cfg
@@ -48,7 +48,7 @@ max_historical_shards=12
/mnt/disk2
```
The `type` field of `[shard_db]` can be omitted. If present, it _MUST_ be `NuDB`. {% badge href="https://github.com/XRPLF/rippled/releases/tag/1.3.1" %}New in: rippled 1.3.1{% /badge %}
The `type` field of `[shard_db]` can be omitted. If present, it _MUST_ be `NuDB`.
**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.

View File

@@ -9,7 +9,7 @@ labels:
# Online Deletion
[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/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. {% badge href="https://github.com/XRPLF/rippled/releases/tag/0.27.0" %}New in: rippled 0.27.0{% /badge %}
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.
The server always keeps the complete _current_ state of the ledger, with all the balances and settings it contains. The deleted data includes older transactions and versions of the ledger state that are older than the stored history.

View File

@@ -8,7 +8,7 @@ labels:
---
# Enable Public Signing
By default, the signing methods for [`rippled`](../../concepts/networks-and-servers/index.md) are limited to [administrative connections](../../references/http-websocket-apis/admin-api-methods/index.md). If you want to allow signing methods to be used as public API methods (like with versions of `rippled` before v1.1.0), you can enable it with a configuration change. {% badge href="https://github.com/XRPLF/rippled/releases/tag/1.1.0" %}New in: rippled 1.1.0{% /badge %}
By default, the signing methods for [`rippled`](../../concepts/networks-and-servers/index.md) are limited to [administrative connections](../../references/http-websocket-apis/admin-api-methods/index.md). If you want to allow signing methods to be used as public API methods (like with versions of `rippled` before v1.1.0), you can enable it with a configuration change.
This enables the following methods to be used on "public" [JSON-RPC and WebSocket connections](../../tutorials/get-started/get-started-using-http-websocket-apis.md), if your server accepts them:

View File

@@ -27,7 +27,7 @@ In a genesis ledger, the [genesis address](../../concepts/accounts/addresses.md#
In a new genesis ledger, the hard-coded default [Reserve](../../concepts/accounts/reserves.md) is **200 XRP** minimum for funding a new address, with an increment of **50 XRP** per object in the ledger. These values are higher than the current reserve requirements of the production network. (See also: [Fee Voting](../../concepts/consensus-protocol/fee-voting.md))
By default, a new genesis ledger has no [amendments](../../concepts/networks-and-servers/amendments.md) enabled. If you start a new genesis ledger with `--start`, the genesis ledger contains an [EnableAmendment pseudo-transaction](../../references/protocol/transactions/pseudo-transaction-types/enableamendment.md) to turn on all amendments natively supported by the `rippled` server, except for amendments that you explicitly disable in the config file. The effects of those amendments are available starting from the very next ledger version. (Reminder: in stand-alone mode, you must [advance the ledger manually](advance-the-ledger-in-stand-alone-mode.md).) {% badge href="https://github.com/XRPLF/rippled/releases/tag/0.50.0" %}New in: rippled 0.50.0{% /badge %}
By default, a new genesis ledger has no [amendments](../../concepts/networks-and-servers/amendments.md) enabled. If you start a new genesis ledger with `--start`, the genesis ledger contains an [EnableAmendment pseudo-transaction](../../references/protocol/transactions/pseudo-transaction-types/enableamendment.md) to turn on all amendments natively supported by the `rippled` server, except for amendments that you explicitly disable in the config file. The effects of those amendments are available starting from the very next ledger version. (Reminder: in stand-alone mode, you must [advance the ledger manually](advance-the-ledger-in-stand-alone-mode.md).)
## See Also

View File

@@ -130,7 +130,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`. {% badge href="https://github.com/XRPLF/rippled/releases/tag/1.5.0" %}New in: rippled 1.5.0{% /badge %} 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/develop/bin/getRippledInfo).
To use the script:

View File

@@ -23,7 +23,7 @@ The capacity of the SQLite database is a result of the database's _page size_ pa
If your server is vulnerable to this problem, you can detect it two ways:
- You can detect the problem [proactively](#proactive-detection) (before it causes problems) if your `rippled` server is [version 1.1.0][New in: rippled 1.1.0] or later.
- You can detect the problem [proactively](#proactive-detection) (before it causes problems) if your `rippled` server is version 1.1.0 or later.
- You can identify the problem [reactively](#reactive-detection) (when your server is crashing) on any `rippled` version.
In both cases, detection of the problem requires access to `rippled`'s server logs.
@@ -32,7 +32,7 @@ In both cases, detection of the problem requires access to `rippled`'s server lo
### Proactive Detection
To detect the SQLite page size problem proactively, you must be running **[rippled 1.1.0][New in: rippled 1.1.0] or later**. The `rippled` server writes a message such as the following in its debug log periodically, at least once every 2 minutes. (The exact numeric values from the log entry and the path to your transaction database depend on your environment.)
To detect the SQLite page size problem proactively, you must be running **`rippled` 1.1.0 or later**. The `rippled` server writes a message such as the following in its debug log periodically, at least once every 2 minutes. (The exact numeric values from the log entry and the path to your transaction database depend on your environment.)
```text
Transaction DB pathname: /opt/rippled/transaction.db; SQLite page size: 1024
@@ -75,7 +75,7 @@ You can fix this issue using `rippled` on supported Linux systems according to t
### Prerequisites
- You must be running **[rippled version 1.1.0][New in: rippled 1.1.0] or later**.
- You must be running **`rippled` version 1.1.0 or later**.
- [Upgrade rippled](../installation/index.md) to the latest stable version before starting this process.

View File

@@ -198,7 +198,7 @@ If your config includes a `[shard_db]` stanza, it must contain a `path` field, w
## Unsupported shard store type: RocksDB
RocksDB is no longer supported as a backend for [history sharding](../configuration/data-retention/history-sharding.md). If you have an existing configuration that defines a RocksDB shard store, the server fails to start. {% badge href="https://github.com/XRPLF/rippled/releases/tag/1.3.1" %}New in: rippled 1.3.1{% /badge %}
RocksDB is no longer supported as a backend for [history sharding](../configuration/data-retention/history-sharding.md). If you have an existing configuration that defines a RocksDB shard store, the server fails to start.
In this case, the process dies shortly after the log startup command, with a message such as the following appearing earlier in the output log:

View File

@@ -26,7 +26,7 @@ Each line represents one log entry, with the following parts in order, separated
1. The date the log entry was written, such as `2020-Jul-08`.
2. The time the log entry was written, such as `20:12:12.075081020`.
3. The time zone indicator `UTC`. (Log dates are always in UTC.) {% badge href="https://github.com/XRPLF/rippled/releases/tag/1.5.0" %}New in: rippled 1.5.0{% /badge %}
3. The time zone indicator `UTC`. (Log dates are always in UTC.)
4. The log partition and severity, such as `LoadMonitor:WRN`.
5. The log message, such as `Job: sweep run: 1172ms wait: 0ms`.

View File

@@ -183,7 +183,7 @@ The response follows the [standard format][], with a successful result containin
| `account_id` | String | The [Address][] of the account in the XRP Ledger's [base58][] format. This is not the public key, but a hash-of-a-hash of it. It also has a checksum so a typo almost certainly results in an invalid address rather than a valid, but different address. This is the primary identifier of an account in the XRP Ledger. You tell people this to get paid, and use it in transactions to indicate who you are and who you're paying, trusting, and so forth. [Multi-signing lists](../../../../concepts/accounts/multi-signing.md) also use these to identify other signers. |
| `public_key` | String | The public key of the key pair, in the XRP Ledger's [base58][] encoded string format. Derived from the `master_seed`. |
| `public_key_hex` | String | This is the public key of the key pair, in hexadecimal. Derived from the `master_seed`. To validate the signature on a transaction, `rippled` needs this public key. That's why the format for a signed transaction includes the public key in the `SigningPubKey` field. |
| `warning` | String | (May be omitted) If the request specified a seed value, this field provides a warning that it may be insecure. {% badge href="https://github.com/XRPLF/rippled/releases/tag/0.32.0" %}New in: rippled 0.32.0{% /badge %} |
| `warning` | String | (May be omitted) If the request specified a seed value, this field provides a warning that it may be insecure. |
You can also use this method to generate a key pair to use as a regular key pair for an account. You assign a regular key pair to an account to be able to sign most transactions with it, while keeping your master key pair offline whenever possible.

View File

@@ -8,7 +8,7 @@ labels:
# 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. {% badge href="https://github.com/XRPLF/rippled/releases/tag/1.2.0" %}New in: rippled 1.2.0{% /badge %}
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._

View File

@@ -8,7 +8,7 @@ labels:
# peer_reservations_add
[[Source]](https://github.com/XRPLF/rippled/blob/4a1148eb2849513dd1e7ae080288fd47ab57a376/src/ripple/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). {% badge href="https://github.com/XRPLF/rippled/releases/tag/1.4.0" %}New in: rippled 1.4.0{% /badge %}
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).
_The {% code-page-name /%} method is an [admin method](../index.md) that cannot be run by unprivileged users._

View File

@@ -8,7 +8,7 @@ labels:
# peer_reservations_del
[[Source]](https://github.com/XRPLF/rippled/blob/4a1148eb2849513dd1e7ae080288fd47ab57a376/src/ripple/rpc/handlers/Reservations.cpp#L89 "Source")
The {% code-page-name /%} method removes a specific [peer reservation][], if one exists. {% badge href="https://github.com/XRPLF/rippled/releases/tag/1.4.0" %}New in: rippled 1.4.0{% /badge %}
The {% code-page-name /%} method removes a specific [peer reservation][], if one exists.
_The {% code-page-name /%} method is an [admin method](../index.md) that cannot be run by unprivileged users._

View File

@@ -8,7 +8,7 @@ labels:
# peer_reservations_list
[[Source]](https://github.com/XRPLF/rippled/blob/4a1148eb2849513dd1e7ae080288fd47ab57a376/src/ripple/rpc/handlers/Reservations.cpp#L116 "Source")
The {% code-page-name /%} method lists [peer reservations][]. {% badge href="https://github.com/XRPLF/rippled/releases/tag/1.4.0" %}New in: rippled 1.4.0{% /badge %}
The {% code-page-name /%} method lists [peer reservations][].
_The {% code-page-name /%} method is an [admin method](../index.md) that cannot be run by unprivileged users._

View File

@@ -371,7 +371,7 @@ The response follows the [standard format][], with a successful result containin
| `Field` | Type | Description |
|:----------|:-------|:--------------------------------------------------------|
| `cluster` | Object | Summary of other `rippled` servers in the same cluster, if [configured as a cluster](../../../../concepts/networks-and-servers/clustering.md). {% badge href="https://github.com/XRPLF/rippled/releases/tag/0.30.1" %}New in: rippled 0.30.1{% /badge %} |
| `cluster` | Object | Summary of other `rippled` servers in the same cluster, if [configured as a cluster](../../../../concepts/networks-and-servers/clustering.md). |
| `peers` | Array | Array of peer objects. |
Each field of the `cluster` object is the public key of that `rippled` server's identifying key pair. (This is the same value that that server returns as `pubkey_node` in the [server_info method][].) The contents of that field are an object with the following fields:
@@ -395,11 +395,11 @@ Each member of the `peers` array is a peer object with the following fields:
| `ledger` | String | The identifying [hash][Hash] of the peer's most recently closed ledger |
| `load` | Number | A measure of the amount of load the peer server is putting on the local server. Larger numbers indicate more load. (The units by which load is measured are not formally defined.) |
| `protocol` | String | _(May be omitted)_ The protocol version that the peer is using, if not the same as the local server. |
| `metrics` | Object | Details on the amount of data sent to and received from this peer. See the description of the `metrics` object below for details. {% badge href="https://github.com/XRPLF/rippled/releases/tag/1.4.0" %}New in: rippled 1.4.0{% /badge %} |
| `metrics` | Object | Details on the amount of data sent to and received from this peer. See the description of the `metrics` object below for details. |
| `public_key` | String | _(May be omitted)_ A public key that can be used to verify the integrity of the peer's messages. This is not the same key that is used for validations, but it follows the same format. |
| `sanity` | String | _(May be omitted)_ Whether this peer is following the same rules and ledger history as the current server. A value of `insane` probably indicates that the peer is part of a [parallel network](../../../../concepts/networks-and-servers/parallel-networks.md). The value `unknown` indicates that the current server is unsure whether the peer is compatible. <!-- STYLE_OVERRIDE: insane --> |
| `status` | String | _(May be omitted)_ The most recent status message from the peer. Could be `connecting`, `connected`, `monitoring`, `validating`, or `shutting`. |
| `uptime` | Number | The number of seconds that your `rippled` server has been continuously connected to this peer. {% badge href="https://github.com/XRPLF/rippled/releases/tag/0.30.1" %}New in: rippled 0.30.1{% /badge %} |
| `uptime` | Number | The number of seconds that your `rippled` server has been continuously connected to this peer. |
| `version` | string | _(May be omitted)_ The `rippled` version number of the peer server |
The `metrics` object contains the following fields:

View File

@@ -94,7 +94,7 @@ The request includes the following parameters:
| `offline` | Boolean | _(Optional)_ If `true`, when constructing the transaction, do not try to [automatically fill](#auto-fillable-fields) any transaction details. The default is `false`. |
| `build_path` | Boolean | _(Optional)_ If this field is provided, the server [auto-fills](../../../protocol/transactions/common-fields.md#auto-fillable-fields) the `Paths` field of a [Payment transaction][] before signing. You must omit this field if the transaction is a [direct XRP payment](../../../../concepts/payment-types/direct-xrp-payments.md) or if it is not a Payment-type transaction. **Caution:** The server looks for the presence or absence of this field, not its value. This behavior may change. ([Issue #3272](https://github.com/XRPLF/rippled/issues/3272)) |
| `fee_mult_max` | Integer | _(Optional)_ Signing fails with the error `rpcHIGH_FEE` if the [auto-filled `Fee` value](../../../protocol/transactions/common-fields.md#auto-fillable-fields) would be greater than the [reference transaction cost](../../../../concepts/transactions/transaction-cost.md#special-transaction-costs) × `fee_mult_max` ÷ `fee_div_max`. This field has no effect if you explicitly specify the `Fee` field of the transaction. The default is `10`. |
| `fee_div_max` | Integer | _(Optional)_ Signing fails with the error `rpcHIGH_FEE` if the [auto-filled `Fee` value](../../../protocol/transactions/common-fields.md#auto-fillable-fields) would be greater than the [reference transaction cost](../../../../concepts/transactions/transaction-cost.md#special-transaction-costs) × `fee_mult_max` ÷ `fee_div_max`. This field has no effect if you explicitly specify the `Fee` field of the transaction. The default is `1`. {% badge href="https://github.com/XRPLF/rippled/releases/tag/0.30.1" %}New in: rippled 0.30.1{% /badge %} |
| `fee_div_max` | Integer | _(Optional)_ Signing fails with the error `rpcHIGH_FEE` if the [auto-filled `Fee` value](../../../protocol/transactions/common-fields.md#auto-fillable-fields) would be greater than the [reference transaction cost](../../../../concepts/transactions/transaction-cost.md#special-transaction-costs) × `fee_mult_max` ÷ `fee_div_max`. This field has no effect if you explicitly specify the `Fee` field of the transaction. The default is `1`. |
### Auto-Fillable Fields

View File

@@ -13,7 +13,7 @@ The `sign_for` command provides one signature for a [multi-signed transaction](.
{% partial file="/_snippets/public-signing-note.md" /%}
This command requires the [MultiSign amendment][] to be enabled. {% badge href="https://github.com/XRPLF/rippled/releases/tag/0.31.0" %}New in: rippled 0.31.0{% /badge %}
This command requires the [MultiSign amendment][] to be enabled.
## Request Format
An example of the request format:

View File

@@ -9,7 +9,7 @@ labels:
# feature
[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/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). {% badge href="https://github.com/XRPLF/rippled/releases/tag/0.31.0" %}New in: rippled 0.31.0{% /badge %}
The `feature` command returns information about [amendments](../../../../concepts/networks-and-servers/amendments.md) this server knows about, including whether they are enabled and whether the server is voting in favor of those amendments in the [amendment process](../../../../concepts/networks-and-servers/amendments.md#amendment-process).
You can use the `feature` command to configure the server to vote against or in favor of an amendment. This change persists even if you restart the server. {% badge href="https://github.com/XRPLF/rippled/releases/tag/1.7.0" %}Updated in: rippled 1.7.0{% /badge %}

View File

@@ -9,7 +9,7 @@ labels:
# validator_list_sites
[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/ValidatorListSites.cpp "Source")
The `validator_list_sites` command returns status information of sites serving validator lists. {% badge href="https://github.com/XRPLF/rippled/releases/tag/0.80.1" %}New in: rippled 0.80.1{% /badge %}
The `validator_list_sites` command returns status information of sites serving validator lists.
*The `validator_list_sites` method is an [admin method](../index.md) that cannot be run by unprivileged users!*

View File

@@ -58,7 +58,7 @@ After you open a WebSocket to the `rippled` server, you can send commands as a [
|:--------------------|:----------|:-------------------------------------------|
| `command` | String | The name of the [API method](../public-api-methods/index.md). |
| `id` | (Various) | _(Optional)_ A unique value to identify this request. The response to this request uses the same `id` field. This way, even if responses arrive out of order, you know which request prompted which response. |
| `api_version` | Number | _(Optional)_ The API version to use. If omitted, use version 1. For details, see [API Versioning](#api-versioning). {% badge href="https://github.com/XRPLF/rippled/releases/tag/1.5.0" %}New in: rippled 1.5.0{% /badge %} |
| `api_version` | Number | _(Optional)_ The API version to use. If omitted, use version 1. For details, see [API Versioning](#api-versioning). |
| (Method Parameters) | (Various) | Provide any parameters to the method at the top level. |
See [Response Formatting](response-formatting.md) for the response from the server.

View File

@@ -17,7 +17,7 @@ The fields of a successful response include:
| `type` | String | (WebSocket only) The value `response` indicates a direct response to an API request. [Asynchronous notifications](../public-api-methods/subscription-methods/subscribe.md) use a different value such as `ledgerClosed` or `transaction`. |
| `result` | Object | The result of the query; contents vary depending on the command. |
| `warning` | String | _(May be omitted)_ If this field is provided, the value is the string `load`. This means the client is approaching the [rate limiting](rate-limiting.md) threshold where the server will disconnect this client. <!-- STYLE_OVERRIDE: will --> |
| `warnings` | Array | _(May be omitted)_ If this field is provided, it contains one or more **Warnings Objects** with important warnings. For details, see [API Warnings](#api-warnings). {% badge href="https://github.com/XRPLF/rippled/releases/tag/1.5.0" %}New in: rippled 1.5.0{% /badge %} |
| `warnings` | Array | _(May be omitted)_ If this field is provided, it contains one or more **Warnings Objects** with important warnings. For details, see [API Warnings](#api-warnings). |
| `forwarded` | Boolean | _(May be omitted)_ If `true`, this request and response have been forwarded from a [Reporting Mode][] server to a P2P Mode server (and back) because the request requires data that is not available in Reporting Mode. The default is `false`. |
@@ -159,7 +159,7 @@ This warning indicates that the server is [amendment blocked](../../../concepts/
The server administrator must [upgrade `rippled`](../../../infrastructure/installation/index.md) to a version that supports the activated amendments.
### 1003. This is a reporting server
{% badge href="https://github.com/XRPLF/rippled/releases/tag/1.7.0" %}New in: rippled 1.7.0{% /badge %}
Example warning:

View File

@@ -8,7 +8,7 @@ labels:
---
# Validator List Method
The validator list method is a special API endpoint that fetches a current, trusted validator list a `rippled` server is using. This often represents the exact list of validators a server trusts. {% badge href="https://github.com/XRPLF/rippled/releases/tag/1.5.0" %}New in: rippled 1.5.0{% /badge %}
The validator list method is a special API endpoint that fetches a current, trusted validator list a `rippled` server is using. This often represents the exact list of validators a server trusts.
Like the [Peer Crawler](peer-crawler.md), the validator list method is available by default on a non-privileged basis through the [Peer Protocol](../../../concepts/networks-and-servers/peer-protocol.md) port, which is also used for `rippled` servers' peer-to-peer communications.
@@ -41,7 +41,7 @@ The JSON object has the following fields:
| `blob` | String | Base64-encoded JSON data representing the validator list. |
| `signature` | String | The signature of the `blob` data, in hexadecimal. |
| `version` | Number | The version of the validator list protocol this object uses. The current version is **1**. A higher version number indicates backwards-incompatible changes with a previous version of the validator list protocol. |
| `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`. {% badge href="https://github.com/XRPLF/rippled/releases/tag/1.7.0" %}New in: rippled 1.7.0{% /badge %} |
| `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")

View File

@@ -8,7 +8,7 @@ labels:
# account_channels
[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/rpc/handlers/AccountChannels.cpp "Source")
_(Added by the [PayChan amendment][]. {% badge href="https://github.com/XRPLF/rippled/releases/tag/0.33.0" %}New in: rippled 0.33.0{% /badge %})_
_(Added by the [PayChan amendment][].)_
The `account_channels` method returns information about an account's Payment Channels. This includes only channels where the specified account is the channel's source, not the destination. (A channel's "source" and "owner" are the same.) All information retrieved is relative to a particular version of the ledger.
@@ -160,9 +160,9 @@ The response follows the [standard format][], with a successful result containin
|:---------------|:-------------------------|:---------------------------------|
| `account` | String | The address of the source/owner of the payment channels. This corresponds to the `account` field of the request. |
| `channels` | Array of Channel Objects | Payment channels owned by this `account`. {% badge href="https://github.com/XRPLF/rippled/releases/tag/1.5.0" %}Updated in: rippled 1.5.0{% /badge %} |
| `ledger_hash` | String | _(May be omitted)_ The identifying [Hash][] of the ledger version used to generate this response. {% badge href="https://github.com/XRPLF/rippled/releases/tag/0.90.0" %}New in: rippled 0.90.0{% /badge %} |
| `ledger_index` | Number | The [Ledger Index][] of the ledger version used to generate this response. {% badge href="https://github.com/XRPLF/rippled/releases/tag/0.90.0" %}New in: rippled 0.90.0{% /badge %} |
| `validated` | Boolean | _(May be omitted)_ If `true`, the information in this response comes from a validated ledger version. Otherwise, the information is subject to change. {% badge href="https://github.com/XRPLF/rippled/releases/tag/0.90.0" %}New in: rippled 0.90.0{% /badge %} |
| `ledger_hash` | String | _(May be omitted)_ The identifying [Hash][] of the ledger version used to generate this response. |
| `ledger_index` | Number | The [Ledger Index][] of the ledger version used to generate this response. |
| `validated` | Boolean | _(May be omitted)_ If `true`, the information in this response comes from a validated ledger version. Otherwise, the information is subject to change. |
| `limit` | Number | _(May be omitted)_ The limit to how many channel objects were actually returned by this request. |
| `marker` | [Marker][] | _(May be omitted)_ Server-defined value for pagination. Pass this to the next call to resume getting results where this call left off. Omitted when there are no additional pages after this one. |

View File

@@ -208,7 +208,7 @@ The response follows the [standard format][], with the result containing the req
| `ledger_current_index` | Integer | _(Omitted if `ledger_index` is provided instead)_ The [ledger index][] of the current in-progress ledger, which was used when retrieving this information. |
| `ledger_index` | Integer | _(Omitted if `ledger_current_index` is provided instead)_ The [ledger index][] of the ledger version used when retrieving this information. The information does not contain any changes from ledger versions newer than this one. |
| `queue_data` | Object | _(Omitted unless `queue` specified as `true` and querying the current open ledger.)_ Information about [queued transactions](../../../../concepts/transactions/transaction-cost.md#queued-transactions) sent by this account. This information describes the state of the local `rippled` server, which may be different from other servers in the [peer-to-peer XRP Ledger network](../../../../concepts/networks-and-servers/peer-protocol.md). Some fields may be omitted because the values are calculated "lazily" by the queuing mechanism. |
| `validated` | Boolean | True if this data is from a validated ledger version; if omitted or set to false, this data is not final. {% badge href="https://github.com/XRPLF/rippled/releases/tag/0.26.0" %}New in: rippled 0.26.0{% /badge %} |
| `validated` | Boolean | True if this data is from a validated ledger version; if omitted or set to false, this data is not final. |
The `account_flags` field contains the following nested fields:

View File

@@ -75,7 +75,7 @@ The request includes the following parameters:
| `Field` | Type | Required? | Description |
|:-------------------------|:-----------------|:----------|-------------|
| `account` | String | Yes | A unique identifier for the account, most commonly the account's [Address][]. |
| `deletion_blockers_only` | Boolean | No | If `true`, the response only includes objects that would block this account from [being deleted](../../../../concepts/accounts/deleting-accounts.md). The default is `false`. {% badge href="https://github.com/XRPLF/rippled/releases/tag/1.4.0" %}New in: rippled 1.4.0{% /badge %} |
| `deletion_blockers_only` | Boolean | No | If `true`, the response only includes objects that would block this account from [being deleted](../../../../concepts/accounts/deleting-accounts.md). The default is `false`. |
| `ledger_hash` | [Hash][] | No | A 20-byte hex string for the ledger version to use. (See [Specifying Ledgers][]) |
| `ledger_index` | [Ledger Index][] | No | The [ledger index][] of the ledger to use, or a shortcut string to choose a ledger automatically. (See [Specifying Ledgers][]) |
| `limit` | Number | No | The maximum number of objects to include in the results. Must be within the inclusive range `10` to `400` on non-admin connections. The default is `200`. |

View File

@@ -206,8 +206,8 @@ Each offer object contains the following fields:
| `seq` | Unsigned integer | Sequence number of the transaction that created this entry. (Transaction [sequence numbers](../../../protocol/data-types/basic-data-types.md#account-sequence) are relative to accounts.) |
| `taker_gets` | String or Object | The amount the account accepting the offer receives, as a String representing an amount in XRP, or a currency specification object. (See [Specifying Currency Amounts][Currency Amount]) |
| `taker_pays` | String or Object | The amount the account accepting the offer provides, as a String representing an amount in XRP, or a currency specification object. (See [Specifying Currency Amounts][Currency Amount]) |
| `quality` | String | The exchange rate of the offer, as the ratio of the original `taker_pays` divided by the original `taker_gets`. When executing offers, the offer with the most favorable (lowest) quality is consumed first; offers with the same quality are executed from oldest to newest. {% badge href="https://github.com/XRPLF/rippled/releases/tag/0.29.0" %}New in: rippled 0.29.0{% /badge %} |
| `expiration` | Unsigned integer | (May be omitted) A time after which this offer is considered unfunded, as the number of [seconds since the Ripple Epoch][]. See also: [Offer Expiration](../../../../concepts/tokens/decentralized-exchange/offers.md#offer-expiration). {% badge href="https://github.com/XRPLF/rippled/releases/tag/0.30.1" %}New in: rippled 0.30.1{% /badge %} |
| `quality` | String | The exchange rate of the offer, as the ratio of the original `taker_pays` divided by the original `taker_gets`. When executing offers, the offer with the most favorable (lowest) quality is consumed first; offers with the same quality are executed from oldest to newest. |
| `expiration` | Unsigned integer | (May be omitted) A time after which this offer is considered unfunded, as the number of [seconds since the Ripple Epoch][]. See also: [Offer Expiration](../../../../concepts/tokens/decentralized-exchange/offers.md#offer-expiration). |
## Possible Errors

View File

@@ -9,7 +9,7 @@ labels:
# gateway_balances
[[Source]](https://github.com/XRPLF/rippled/blob/9111ad1a9dc37d49d085aa317712625e635197c0/src/ripple/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). {% badge href="https://github.com/XRPLF/rippled/releases/tag/0.28.2" %}New in: rippled 0.28.2{% /badge %}
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).
**Caution:** Some public servers disable this API method because it can require a large amount of processing.

View File

@@ -386,7 +386,7 @@ rippled json ledger_entry '{ "ripple_state": { "accounts": ["rf1BiGeXwwQoi8Z2ueF
### Get Check Object
Retrieve a [Check entry](../../../protocol/ledger-data/ledger-entry-types/check.md), which is a potential payment that can be cashed by its recipient. {% badge href="https://github.com/XRPLF/rippled/releases/tag/1.0.0" %}New in: rippled 1.0.0{% /badge %}
Retrieve a [Check entry](../../../protocol/ledger-data/ledger-entry-types/check.md), which is a potential payment that can be cashed by its recipient.
| Field | Type | Description |
|:--------|:-------|:----------------------------------------------------------|
@@ -431,7 +431,7 @@ rippled json ledger_entry '{ "check": "C4A46CCD8F096E994C4B0DEAB6CE98E722FC17D79
### Get Escrow Object
Retrieve an [Escrow entry](../../../protocol/ledger-data/ledger-entry-types/escrow.md), which holds XRP until a specific time or condition is met. Can be provided as string (object ID of the Escrow) or as an object. {% badge href="https://github.com/XRPLF/rippled/releases/tag/1.0.0" %}New in: rippled 1.0.0{% /badge %}
Retrieve an [Escrow entry](../../../protocol/ledger-data/ledger-entry-types/escrow.md), which holds XRP until a specific time or condition is met. Can be provided as string (object ID of the Escrow) or as an object.
| Field | Type | Description |
|:------------------------|:---------------------------|:----------------------|
@@ -484,7 +484,7 @@ rippled json ledger_entry '{ "escrow": { "owner": "rL4fPHi2FWGwRGRQSH7gBcxkuo2b9
### Get PayChannel Object
Retrieve a [PayChannel entry](../../../protocol/ledger-data/ledger-entry-types/paychannel.md), which holds XRP for asynchronous payments. {% badge href="https://github.com/XRPLF/rippled/releases/tag/1.0.0" %}New in: rippled 1.0.0{% /badge %}
Retrieve a [PayChannel entry](../../../protocol/ledger-data/ledger-entry-types/paychannel.md), which holds XRP for asynchronous payments.
| Field | Type | Description |
|:------------------|:-------|:------------------------------------------------|
@@ -528,7 +528,7 @@ rippled json ledger_entry '{ "payment_channel": "C7F634794B79DB40E87179A9D1BF05D
### Get DepositPreauth Object
Retrieve a [DepositPreauth entry](../../../protocol/ledger-data/ledger-entry-types/depositpreauth.md), which tracks preauthorization for payments to accounts requiring [Deposit Authorization](../../../../concepts/accounts/depositauth.md). {% badge href="https://github.com/XRPLF/rippled/releases/tag/1.1.0" %}New in: rippled 1.1.0{% /badge %}
Retrieve a [DepositPreauth entry](../../../protocol/ledger-data/ledger-entry-types/depositpreauth.md), which tracks preauthorization for payments to accounts requiring [Deposit Authorization](../../../../concepts/accounts/depositauth.md).
| Field | Type | Description |
|:-----------------------------|:---------------------|:-----------------------|

View File

@@ -59,8 +59,8 @@ The request includes the following parameters:
| `subcommand` | String | Use `"create"` to send the create sub-command |
| `source_account` | String | Unique address of the account to find a path from. (In other words, the account that would be sending a payment.) |
| `destination_account` | String | Unique address of the account to find a path to. (In other words, the account that would receive a payment.) |
| `destination_amount` | String or Object | [Currency Amount][] that the destination account would receive in a transaction. **Special case:** {% badge href="https://github.com/XRPLF/rippled/releases/tag/0.30.0" %}New in: rippled 0.30.0{% /badge %} You can specify `"-1"` (for XRP) or provide -1 as the contents of the `value` field (for non-XRP currencies). This requests a path to deliver as much as possible, while spending no more than the amount specified in `send_max` (if provided). |
| `send_max` | String or Object | _(Optional)_ [Currency Amount][] that would be spent in the transaction. Not compatible with `source_currencies`. {% badge href="https://github.com/XRPLF/rippled/releases/tag/0.30.0" %}New in: rippled 0.30.0{% /badge %} |
| `destination_amount` | String or Object | [Currency Amount][] that the destination account would receive in a transaction. **Special case:** You can specify `"-1"` (for XRP) or provide -1 as the contents of the `value` field (for non-XRP currencies). This requests a path to deliver as much as possible, while spending no more than the amount specified in `send_max` (if provided). |
| `send_max` | String or Object | _(Optional)_ [Currency Amount][] that would be spent in the transaction. Not compatible with `source_currencies`. |
| `paths` | Array | _(Optional)_ Array of arrays of objects, representing [payment paths](../../../../concepts/tokens/fungible-tokens/paths.md) to check. You can use this to keep updated on changes to particular paths you already know about, or to check the overall cost to make a payment along a certain path. |
The server also recognizes the following fields, but the results of using them are not guaranteed: `source_currencies`, `bridges`. These fields should be considered reserved for future use.
@@ -449,7 +449,7 @@ The initial response follows the [standard format](../../api-conventions/respons
| `destination_account` | String | Unique address of the account that would receive a transaction. |
| `destination_amount` | String or Object | [Currency Amount][] that the destination would receive in a transaction. |
| `source_account` | String | Unique address that would send a transaction. |
| `full_reply` | Boolean | If `false`, this is the result of an incomplete search. A later reply may have a better path. If `true`, then this is the best path found. (It is still theoretically possible that a better path could exist, but `rippled` won't find it.) Until you close the pathfinding request, `rippled` continues to send updates each time a new ledger closes. {% badge href="https://github.com/XRPLF/rippled/releases/tag/0.29.0" %}New in: rippled 0.29.0{% /badge %} |
| `full_reply` | Boolean | If `false`, this is the result of an incomplete search. A later reply may have a better path. If `true`, then this is the best path found. (It is still theoretically possible that a better path could exist, but `rippled` won't find it.) Until you close the pathfinding request, `rippled` continues to send updates each time a new ledger closes. |
Each element in the `alternatives` array is an object that represents a path from one possible source currency (held by the initiating account) to the destination account and currency. This object has the following fields:

View File

@@ -88,8 +88,8 @@ The request includes the following parameters:
|:----------------------|:---------------------------|:------------------------|
| `source_account` | String | Unique address of the account that would send funds in a transaction |
| `destination_account` | String | Unique address of the account that would receive funds in a transaction |
| `destination_amount` | String or Object | [Currency Amount][] that the destination account would receive in a transaction. **Special case:** {% badge href="https://github.com/XRPLF/rippled/releases/tag/0.30.0" %}New in: rippled 0.30.0{% /badge %} You can specify `"-1"` (for XRP) or provide -1 as the contents of the `value` field (for non-XRP currencies). This requests a path to deliver as much as possible, while spending no more than the amount specified in `send_max` (if provided). |
| `send_max` | String or Object | _(Optional)_ [Currency Amount][] that would be spent in the transaction. Cannot be used with `source_currencies`. {% badge href="https://github.com/XRPLF/rippled/releases/tag/0.30.0" %}New in: rippled 0.30.0{% /badge %} |
| `destination_amount` | String or Object | [Currency Amount][] that the destination account would receive in a transaction. **Special case:** You can specify `"-1"` (for XRP) or provide -1 as the contents of the `value` field (for non-XRP currencies). This requests a path to deliver as much as possible, while spending no more than the amount specified in `send_max` (if provided). |
| `send_max` | String or Object | _(Optional)_ [Currency Amount][] that would be spent in the transaction. Cannot be used with `source_currencies`. |
| `source_currencies` | Array | _(Optional)_ Array of currencies that the source account might want to spend. Each entry in the array should be a JSON object with a mandatory `currency` field and optional `issuer` field, like how [currency amounts][Currency Amount] are specified. Cannot contain more than **18** source currencies. By default, uses all source currencies available up to a maximum of **88** different currency/issuer pairs. |
| `ledger_hash` | String | _(Optional)_ A 20-byte hex string for the ledger version to use. (See [Specifying Ledgers][]) |
| `ledger_index` | String or Unsigned Integer | _(Optional)_ The [ledger index][] of the ledger to use, or a shortcut string to choose a ledger automatically. (See [Specifying Ledgers][]) |

View File

@@ -8,7 +8,7 @@ labels:
# channel_authorize
[[Source]](https://github.com/XRPLF/rippled/blob/d4a56f223a3b80f64ff70b4e90ab6792806929ca/src/ripple/rpc/handlers/PayChanClaim.cpp#L41 "Source")
_(Added by the [PayChan amendment][] to be enabled. {% badge href="https://github.com/XRPLF/rippled/releases/tag/0.33.0" %}New in: rippled 0.33.0{% /badge %})_
_(Added by the [PayChan amendment][] to be enabled.)_
The `channel_authorize` method creates a signature that can be used to redeem a specific amount of XRP from a payment channel.
@@ -62,10 +62,10 @@ The request includes the following parameters:
|-------|------|-------------|
| `channel_id` | String | The unique ID of the payment channel to use.
| `secret` | String | _(Optional)_ The secret key to use to sign the claim. This must be the same key pair as the public key specified in the channel. Cannot be used with `seed`, `seed_hex`, or `passphrase`. {% badge href="https://github.com/XRPLF/rippled/releases/tag/1.4.0" %}Updated in: rippled 1.4.0{% /badge %} |
| `seed` | String | _(Optional)_ The secret seed to use to sign the claim. This must be the same key pair as the public key specified in the channel. Must be in the XRP Ledger's [base58][] format. If provided, you must also specify the `key_type`. Cannot be used with `secret`, `seed_hex`, or `passphrase`. {% badge href="https://github.com/XRPLF/rippled/releases/tag/1.4.0" %}New in: rippled 1.4.0{% /badge %} |
| `seed_hex` | String | _(Optional)_ The secret seed to use to sign the claim. This must be the same key pair as the public key specified in the channel. Must be in hexadecimal format. If provided, you must also specify the `key_type`. Cannot be used with `secret`, `seed`, or `passphrase`. {% badge href="https://github.com/XRPLF/rippled/releases/tag/1.4.0" %}New in: rippled 1.4.0{% /badge %} |
| `passphrase` | String | _(Optional)_ A string passphrase to use to sign the claim. This must be the same key pair as the public key specified in the channel. The [key derived from this passphrase](../../../../concepts/accounts/cryptographic-keys.md#key-derivation) must match the public key specified in the channel. If provided, you must also specify the `key_type`. Cannot be used with `secret`, `seed`, or `seed_hex`. {% badge href="https://github.com/XRPLF/rippled/releases/tag/1.4.0" %}New in: rippled 1.4.0{% /badge %} |
| `key_type` | String | _(Optional)_ The [signing algorithm](../../../../concepts/accounts/cryptographic-keys.md#signing-algorithms) of the cryptographic key pair provided. Valid types are `secp256k1` or `ed25519`. The default is `secp256k1`. {% badge href="https://github.com/XRPLF/rippled/releases/tag/1.4.0" %}New in: rippled 1.4.0{% /badge %} |
| `seed` | String | _(Optional)_ The secret seed to use to sign the claim. This must be the same key pair as the public key specified in the channel. Must be in the XRP Ledger's [base58][] format. If provided, you must also specify the `key_type`. Cannot be used with `secret`, `seed_hex`, or `passphrase`. |
| `seed_hex` | String | _(Optional)_ The secret seed to use to sign the claim. This must be the same key pair as the public key specified in the channel. Must be in hexadecimal format. If provided, you must also specify the `key_type`. Cannot be used with `secret`, `seed`, or `passphrase`. |
| `passphrase` | String | _(Optional)_ A string passphrase to use to sign the claim. This must be the same key pair as the public key specified in the channel. The [key derived from this passphrase](../../../../concepts/accounts/cryptographic-keys.md#key-derivation) must match the public key specified in the channel. If provided, you must also specify the `key_type`. Cannot be used with `secret`, `seed`, or `seed_hex`. |
| `key_type` | String | _(Optional)_ The [signing algorithm](../../../../concepts/accounts/cryptographic-keys.md#signing-algorithms) of the cryptographic key pair provided. Valid types are `secp256k1` or `ed25519`. The default is `secp256k1`. |
| `amount` | String | Cumulative amount of XRP, in drops, to authorize. If the destination has already received a lesser amount of XRP from this channel, the signature created by this method can be redeemed for the difference. |
The request **must** specify exactly one of `secret`, `seed`, `seed_hex`, or `passphrase`.
@@ -125,7 +125,7 @@ The response follows the [standard format][], with a successful result containin
## Possible Errors
* Any of the [universal error types][].
* `badKeyType` - The `key_type` parameter in the request is not a valid key type. (Valid types are `secp256k1` or `ed25519`.) {% badge href="https://github.com/XRPLF/rippled/releases/tag/1.4.0" %}New in: rippled 1.4.0{% /badge %}
* `badKeyType` - The `key_type` parameter in the request is not a valid key type. (Valid types are `secp256k1` or `ed25519`.)
* `badSeed` - The `secret` in the request is not a valid secret key.
* `channelAmtMalformed` - The `amount` in the request is not a valid [XRP amount][XRP, in drops].
* `channelMalformed` - The `channel_id` in the request is not a valid Channel ID. The Channel ID should be a 256-bit (64-character) hexadecimal string.

View File

@@ -8,7 +8,7 @@ labels:
# channel_verify
[[Source]](https://github.com/XRPLF/rippled/blob/d4a56f223a3b80f64ff70b4e90ab6792806929ca/src/ripple/rpc/handlers/PayChanClaim.cpp#L89 "Source")
_(Added by the [PayChan amendment][] to be enabled. {% badge href="https://github.com/XRPLF/rippled/releases/tag/0.33.0" %}New in: rippled 0.33.0{% /badge %})_
_(Added by the [PayChan amendment][] to be enabled.)_
The `channel_verify` method checks the validity of a signature that can be used to redeem a specific amount of XRP from a payment channel.

View File

@@ -8,7 +8,7 @@ labels:
# fee
[[Source]](https://github.com/XRPLF/rippled/blob/release/src/ripple/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. {% badge href="https://github.com/XRPLF/rippled/releases/tag/0.31.0" %}New in: rippled 0.31.0{% /badge %}
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.
This is a public command available to unprivileged users. {% badge href="https://github.com/XRPLF/rippled/releases/tag/0.32.0" %}Updated in: rippled 0.32.0{% /badge %}
@@ -154,7 +154,7 @@ The response follows the [standard format][], with a successful result containin
| `drops.minimum_fee` | String (Integer) | The minimum transaction cost for a [reference transaction](../../../../concepts/transactions/transaction-cost.md#reference-transaction-cost) to be queued for a later ledger, represented in drops of XRP. If greater than `base_fee`, the transaction queue is full. |
| `drops.open_ledger_fee` | String (Integer) | The minimum transaction cost that a [reference transaction](../../../../concepts/transactions/transaction-cost.md#reference-transaction-cost) must pay to be included in the current open ledger, represented in drops of XRP. |
| `expected_ledger_size` | String (Integer) | The approximate number of transactions expected to be included in the current ledger. This is based on the number of transactions in the previous ledger. |
| `ledger_current_index` | Number | The [Ledger Index][] of the current open ledger these stats describe. {% badge href="https://github.com/XRPLF/rippled/releases/tag/0.50.0" %}New in: rippled 0.50.0{% /badge %} |
| `ledger_current_index` | Number | The [Ledger Index][] of the current open ledger these stats describe. |
| `levels` | Object | Various information about the transaction cost, in [fee levels][]. The ratio in fee levels applies to any transaction relative to the minimum cost of that particular transaction. |
| `levels.median_level` | String (Integer) | The median transaction cost among transactions in the previous validated ledger, represented in [fee levels][]. |
| `levels.minimum_level` | String (Integer) | The minimum transaction cost required to be queued for a future ledger, represented in [fee levels][]. |

View File

@@ -215,20 +215,20 @@ The fields from a validations stream message are as follows:
| `Field` | Type | Description |
|:------------------------|:-----------------|:--------------------------------|
| `type` | String | The value `validationReceived` indicates this is from the validations stream. |
| `amendments` | Array of Strings | _(May be omitted)_ The [amendments](../../../../concepts/networks-and-servers/amendments.md) this server wants to be added to the protocol. {% badge href="https://github.com/XRPLF/rippled/releases/tag/0.32.0" %}New in: rippled 0.32.0{% /badge %} |
| `base_fee` | Integer | _(May be omitted)_ The unscaled transaction cost (`reference_fee` value) this server wants to set by [Fee Voting](../../../../concepts/consensus-protocol/fee-voting.md). {% badge href="https://github.com/XRPLF/rippled/releases/tag/0.32.0" %}New in: rippled 0.32.0{% /badge %} |
| `amendments` | Array of Strings | _(May be omitted)_ The [amendments](../../../../concepts/networks-and-servers/amendments.md) this server wants to be added to the protocol. |
| `base_fee` | Integer | _(May be omitted)_ The unscaled transaction cost (`reference_fee` value) this server wants to set by [Fee Voting](../../../../concepts/consensus-protocol/fee-voting.md). |
| `cookie` | String - Number | _(May be omitted)_ An arbitrary value chosen by the server at startup. If the same validation key pair signs validations with different cookies concurrently, that usually indicates that multiple servers are incorrectly configured to use the same validation key pair. {% badge href="https://github.com/XRPLF/rippled/releases/tag/1.8.1" %}New in: rippled 1.8.1{% /badge %} |
| `flags` | Number | Bit-mask of flags added to this validation message. The flag `0x80000000` indicates that the validation signature is fully-canonical. The flag `0x00000001` indicates that this is a full validation; otherwise it's a partial validation. Partial validations are not meant to vote for any particular ledger. A partial validation indicates that the validator is still online but not keeping up with consensus. {% badge href="https://github.com/XRPLF/rippled/releases/tag/0.32.0" %}New in: rippled 0.32.0{% /badge %} |
| `full` | Boolean | If `true`, this is a full validation. Otherwise, this is a partial validation. Partial validations are not meant to vote for any particular ledger. A partial validation indicates that the validator is still online but not keeping up with consensus. {% badge href="https://github.com/XRPLF/rippled/releases/tag/0.32.0" %}New in: rippled 0.32.0{% /badge %} |
| `flags` | Number | Bit-mask of flags added to this validation message. The flag `0x80000000` indicates that the validation signature is fully-canonical. The flag `0x00000001` indicates that this is a full validation; otherwise it's a partial validation. Partial validations are not meant to vote for any particular ledger. A partial validation indicates that the validator is still online but not keeping up with consensus. |
| `full` | Boolean | If `true`, this is a full validation. Otherwise, this is a partial validation. Partial validations are not meant to vote for any particular ledger. A partial validation indicates that the validator is still online but not keeping up with consensus. |
| `ledger_hash` | String | The identifying hash of the proposed ledger is being validated. |
| `ledger_index` | String - Number | The [Ledger Index][] of the proposed ledger. {% badge href="https://github.com/XRPLF/rippled/releases/tag/0.31.0" %}New in: rippled 0.31.0{% /badge %} |
| `load_fee` | Integer | _(May be omitted)_ The local load-scaled transaction cost this validator is currently enforcing, in fee units. {% badge href="https://github.com/XRPLF/rippled/releases/tag/0.32.0" %}New in: rippled 0.32.0{% /badge %} |
| `master_key` | String | _(May be omitted)_ The validator's master public key, if the validator is using a validator token, in the XRP Ledger's [base58][] format. (See also: [Enable Validation on your `rippled` Server](../../../../infrastructure/configuration/server-modes/run-rippled-as-a-validator.md#3-enable-validation-on-your-rippled-server).) {% badge href="https://github.com/XRPLF/rippled/releases/tag/1.4.0" %}New in: rippled 1.4.0{% /badge %} |
| `reserve_base` | Integer | _(May be omitted)_ The minimum reserve requirement (`account_reserve` value) this validator wants to set by [Fee Voting](../../../../concepts/consensus-protocol/fee-voting.md). {% badge href="https://github.com/XRPLF/rippled/releases/tag/0.32.0" %}New in: rippled 0.32.0{% /badge %} |
| `reserve_inc` | Integer | _(May be omitted)_ The increment in the reserve requirement (`owner_reserve` value) this validator wants to set by [Fee Voting](../../../../concepts/consensus-protocol/fee-voting.md). {% badge href="https://github.com/XRPLF/rippled/releases/tag/0.32.0" %}New in: rippled 0.32.0{% /badge %} |
| `ledger_index` | String - Number | The [Ledger Index][] of the proposed ledger. |
| `load_fee` | Integer | _(May be omitted)_ The local load-scaled transaction cost this validator is currently enforcing, in fee units. |
| `master_key` | String | _(May be omitted)_ The validator's master public key, if the validator is using a validator token, in the XRP Ledger's [base58][] format. (See also: [Enable Validation on your `rippled` Server](../../../../infrastructure/configuration/server-modes/run-rippled-as-a-validator.md#3-enable-validation-on-your-rippled-server).) |
| `reserve_base` | Integer | _(May be omitted)_ The minimum reserve requirement (`account_reserve` value) this validator wants to set by [Fee Voting](../../../../concepts/consensus-protocol/fee-voting.md). |
| `reserve_inc` | Integer | _(May be omitted)_ The increment in the reserve requirement (`owner_reserve` value) this validator wants to set by [Fee Voting](../../../../concepts/consensus-protocol/fee-voting.md). |
| `server_version` | String - Number | _(May be omitted)_ An 64-bit integer that encodes the version number of the validating server. For example, `"1745990410175512576"`. Only provided once every 256 ledgers. {% badge href="https://github.com/XRPLF/rippled/releases/tag/1.8.1" %}New in: rippled 1.8.1{% /badge %} |
| `signature` | String | The signature that the validator used to sign its vote for this ledger. |
| `signing_time` | Number | When this validation vote was signed, in [seconds since the Ripple Epoch][]. {% badge href="https://github.com/XRPLF/rippled/releases/tag/0.32.0" %}New in: rippled 0.32.0{% /badge %} |
| `signing_time` | Number | When this validation vote was signed, in [seconds since the Ripple Epoch][]. |
| `validated_hash` | String | The unique hash of the proposed ledger this validation applies to. {% badge href="https://github.com/XRPLF/rippled/releases/tag/1.8.1" %}New in: rippled 1.8.1{% /badge %} |
| `validation_public_key` | String | The public key from the key-pair that the validator used to sign the message, in the XRP Ledger's [base58][] format. This identifies the validator sending the message and can also be used to verify the `signature`. If the validator is using a token, this is an ephemeral public key. |

View File

@@ -91,7 +91,7 @@ The request includes the following parameters:
| `offline` | Boolean | _(Optional)_ If `true`, when constructing the transaction, do not try to automatically fill in or validate values. The default is `false`. |
| `build_path` | Boolean | _(Optional)_ If this field is provided, the server [auto-fills](../../../protocol/transactions/common-fields.md#auto-fillable-fields) the `Paths` field of a [Payment transaction][] before signing. You must omit this field if the transaction is a [direct XRP payment](../../../../concepts/payment-types/direct-xrp-payments.md) or if it is not a Payment-type transaction. **Caution:** The server looks for the presence or absence of this field, not its value. This behavior may change. ([Issue #3272](https://github.com/XRPLF/rippled/issues/3272)) |
| `fee_mult_max` | Integer | _(Optional)_ Sign-and-submit fails with the error `rpcHIGH_FEE` if the [auto-filled `Fee` value](../../../protocol/transactions/common-fields.md#auto-fillable-fields) would be greater than the [reference transaction cost](../../../../concepts/transactions/transaction-cost.md#special-transaction-costs) × `fee_mult_max` ÷ `fee_div_max`. This field has no effect if you explicitly specify the `Fee` field of the transaction. The default is `10`. |
| `fee_div_max` | Integer | _(Optional)_ Sign-and-submit fails with the error `rpcHIGH_FEE` if the [auto-filled `Fee` value](../../../protocol/transactions/common-fields.md#auto-fillable-fields) would be greater than the [reference transaction cost](../../../../concepts/transactions/transaction-cost.md#special-transaction-costs) × `fee_mult_max` ÷ `fee_div_max`. This field has no effect if you explicitly specify the `Fee` field of the transaction. The default is `1`. {% badge href="https://github.com/XRPLF/rippled/releases/tag/0.30.1" %}New in: rippled 0.30.1{% /badge %} |
| `fee_div_max` | Integer | _(Optional)_ Sign-and-submit fails with the error `rpcHIGH_FEE` if the [auto-filled `Fee` value](../../../protocol/transactions/common-fields.md#auto-fillable-fields) would be greater than the [reference transaction cost](../../../../concepts/transactions/transaction-cost.md#special-transaction-costs) × `fee_mult_max` ÷ `fee_div_max`. This field has no effect if you explicitly specify the `Fee` field of the transaction. The default is `1`. |
See the [sign method][] for detailed information on how the server automatically fills in certain fields.
@@ -297,14 +297,14 @@ The response follows the [standard format][], with a successful result containin
| `engine_result_message` | String | Human-readable explanation of the transaction's preliminary result |
| `tx_blob` | String | The complete transaction in hex string format |
| `tx_json` | Object | The complete transaction in JSON format |
| `accepted` | Boolean | _(Omitted in sign-and-submit mode)_ The value `true` indicates that the transaction was applied, queued, broadcast, or kept for later. The value `false` indicates that none of those happened, so the transaction cannot possibly succeed as long as you do not submit it again and have not already submitted it another time. {% badge href="https://github.com/XRPLF/rippled/releases/tag/1.5.0" %}New in: rippled 1.5.0{% /badge %} |
| `account_sequence_available` | Number | _(Omitted in sign-and-submit mode)_ The next [Sequence Number][] available for the sending account after all pending and [queued](../../../../concepts/transactions/transaction-queue.md) transactions. {% badge href="https://github.com/XRPLF/rippled/releases/tag/1.5.0" %}New in: rippled 1.5.0{% /badge %} |
| `account_sequence_next` | number | _(Omitted in sign-and-submit mode)_ The next [Sequence Number][] for the sending account after all transactions that have been provisionally applied, but not transactions in the [queue](../../../../concepts/transactions/transaction-queue.md). {% badge href="https://github.com/XRPLF/rippled/releases/tag/1.5.0" %}New in: rippled 1.5.0{% /badge %} |
| `applied` | Boolean | _(Omitted in sign-and-submit mode)_ The value `true` indicates that this transaction was applied to the open ledger. In this case, the transaction is likely, but not guaranteed, to be validated in the next ledger version. {% badge href="https://github.com/XRPLF/rippled/releases/tag/1.5.0" %}New in: rippled 1.5.0{% /badge %} |
| `broadcast` | Boolean | _(Omitted in sign-and-submit mode)_ The value `true` indicates this transaction was broadcast to peer servers in the peer-to-peer XRP Ledger network. (Note: if the server has no peers, such as in [stand-alone mode][], the server uses the value `true` for cases where it _would_ have broadcast the transaction.) The value `false` indicates the transaction was not broadcast to any other servers. {% badge href="https://github.com/XRPLF/rippled/releases/tag/1.5.0" %}New in: rippled 1.5.0{% /badge %} |
| `kept` | Boolean | _(Omitted in sign-and-submit mode)_ The value `true` indicates that the transaction was kept to be retried later. {% badge href="https://github.com/XRPLF/rippled/releases/tag/1.5.0" %}New in: rippled 1.5.0{% /badge %} |
| `queued` | Boolean | _(Omitted in sign-and-submit mode)_ The value `true` indicates the transaction was put in the [Transaction Queue](../../../../concepts/transactions/transaction-queue.md), which means it is likely to be included in a future ledger version. {% badge href="https://github.com/XRPLF/rippled/releases/tag/1.5.0" %}New in: rippled 1.5.0{% /badge %} |
| `open_ledger_cost` | String | _(Omitted in sign-and-submit mode)_ The current [open ledger cost](../../../../concepts/transactions/transaction-cost.md#open-ledger-cost) before processing this transaction. Transactions with a lower cost are likely to be [queued](../../../../concepts/transactions/transaction-queue.md). {% badge href="https://github.com/XRPLF/rippled/releases/tag/1.5.0" %}New in: rippled 1.5.0{% /badge %} |
| `accepted` | Boolean | _(Omitted in sign-and-submit mode)_ The value `true` indicates that the transaction was applied, queued, broadcast, or kept for later. The value `false` indicates that none of those happened, so the transaction cannot possibly succeed as long as you do not submit it again and have not already submitted it another time. |
| `account_sequence_available` | Number | _(Omitted in sign-and-submit mode)_ The next [Sequence Number][] available for the sending account after all pending and [queued](../../../../concepts/transactions/transaction-queue.md) transactions. |
| `account_sequence_next` | number | _(Omitted in sign-and-submit mode)_ The next [Sequence Number][] for the sending account after all transactions that have been provisionally applied, but not transactions in the [queue](../../../../concepts/transactions/transaction-queue.md). |
| `applied` | Boolean | _(Omitted in sign-and-submit mode)_ The value `true` indicates that this transaction was applied to the open ledger. In this case, the transaction is likely, but not guaranteed, to be validated in the next ledger version. |
| `broadcast` | Boolean | _(Omitted in sign-and-submit mode)_ The value `true` indicates this transaction was broadcast to peer servers in the peer-to-peer XRP Ledger network. (Note: if the server has no peers, such as in [stand-alone mode][], the server uses the value `true` for cases where it _would_ have broadcast the transaction.) The value `false` indicates the transaction was not broadcast to any other servers. |
| `kept` | Boolean | _(Omitted in sign-and-submit mode)_ The value `true` indicates that the transaction was kept to be retried later. |
| `queued` | Boolean | _(Omitted in sign-and-submit mode)_ The value `true` indicates the transaction was put in the [Transaction Queue](../../../../concepts/transactions/transaction-queue.md), which means it is likely to be included in a future ledger version. |
| `open_ledger_cost` | String | _(Omitted in sign-and-submit mode)_ The current [open ledger cost](../../../../concepts/transactions/transaction-cost.md#open-ledger-cost) before processing this transaction. Transactions with a lower cost are likely to be [queued](../../../../concepts/transactions/transaction-queue.md). |
| `validated_ledger_index` | Integer | _(Omitted in sign-and-submit mode)_ The [ledger index][] of the newest validated ledger at the time of submission. This provides a lower bound on the ledger versions that the transaction can appear in as a result of this request. (The transaction could only have been validated in this ledger version or earlier if it had already been submitted before.) |
**Warning:** Even if the WebSocket response has `"status":"success"`, indicating that the command was successfully received, that does _not_ indicate that the transaction executed successfully. Many situations can prevent a transaction from processing successfully, such as a lack of trust lines connecting the two accounts in a payment, or changes in the state of the ledger since the time the transaction was constructed. Even if nothing is wrong, it may take several seconds to close and validate the ledger version that includes the transaction. See the [full list of transaction responses](../../../protocol/transactions/transaction-results/transaction-results.md) for details, and do not consider the transaction's results final until they appear in a validated ledger version.
@@ -328,6 +328,6 @@ The response follows the [standard format][], with a successful result containin
* `invalidTransaction` - The transaction is malformed or otherwise invalid.
* `noPath` - The transaction did not include paths, and the server was unable to find a path by which this payment can occur. (Sign-and-Submit mode only)
* `tooBusy` - The transaction did not include paths, but the server is too busy to do pathfinding right now. Does not occur if you are connected as an admin. (Sign-and-Submit mode only)
* `notSupported` - Signing is not supported by this server (Sign-and-Submit mode only.) If you are the server admin, you can still access signing when connected [as an admin](../../admin-api-methods/index.md), or you could [enable public signing](../../../../infrastructure/configuration/enable-public-signing.md). {% badge href="https://github.com/XRPLF/rippled/releases/tag/1.1.0" %}New in: rippled 1.1.0{% /badge %}
* `notSupported` - Signing is not supported by this server (Sign-and-Submit mode only.) If you are the server admin, you can still access signing when connected [as an admin](../../admin-api-methods/index.md), or you could [enable public signing](../../../../infrastructure/configuration/enable-public-signing.md).
{% raw-partial file="/_snippets/common-links.md" /%}

View File

@@ -10,7 +10,7 @@ labels:
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).)
This command requires the [MultiSign amendment][] to be enabled. {% badge href="https://github.com/XRPLF/rippled/releases/tag/0.31.0" %}New in: rippled 0.31.0{% /badge %}
This command requires the [MultiSign amendment][] to be enabled.
## Request Format
An example of the request format: