From 032eee07fba1cb65cca600ab4e9bf9a0bff2b03f Mon Sep 17 00:00:00 2001 From: mDuo13 Date: Thu, 27 May 2021 16:26:21 -0700 Subject: [PATCH] Spell checker pass --- content/_snippets/data_types/address.ja.md | 6 +- content/_snippets/data_types/address.md | 2 +- .../interactive-tutorials/generate-step.md | 2 +- content/_snippets/wait-for-validation.ja.md | 2 +- content/_snippets/wait-for-validation.md | 2 +- .../amendments/amendments.md | 4 +- .../amendments/known-amendments.md | 12 +- .../consensus-protections.md | 2 +- .../decentralized-exchange/autobridging.md | 2 +- .../issued-currencies-overview.md | 4 +- .../accounts/cryptographic-keys.md | 2 +- content/contributing/contribute-code.md | 2 +- .../protocol-reference/currency-formats.md | 2 +- .../ledger-object-types/negativeunl.md | 1 + .../peer-port-methods/peer-crawler.md | 2 +- .../get-started/get-started-using-java.md | 11 +- .../get-started/get-started-using-node-js.md | 2 +- .../get-started/get-started-using-python.md | 4 +- content/tutorials/get-started/get-started.md | 2 +- content/tutorials/get-started/send-xrp.md | 36 +-- .../installation/capacity-planning.md | 2 +- .../installation/system-requirements.md | 2 +- .../update-rippled-manually-on-centos-rhel.md | 2 +- .../understanding-log-messages.md | 1 + .../set-up-secure-signing.md | 2 +- tool/spelling.txt | 249 ++++++++++-------- 26 files changed, 197 insertions(+), 163 deletions(-) diff --git a/content/_snippets/data_types/address.ja.md b/content/_snippets/data_types/address.ja.md index 80e3b7068c..48a71c5a6f 100644 --- a/content/_snippets/data_types/address.ja.md +++ b/content/_snippets/data_types/address.ja.md @@ -2,12 +2,12 @@ XRP Ledgerのアカウントは、XRP Ledgerの[base58][]フォーマットの * 長さは25から35文字です * 文字`r`で始まります - - **注記:** XRPコミュニティは、取引所およびウォレットで[宛先タグ](https://xrpl.org/source-and-destination-tags.html)の代わりに使用できる新しいフォーマット、**X**アドレスを[提案](https://github.com/xrp-community/standards-drafts/issues/6)（これをサポートする[コーデック](https://github.com/xrp-community/xrpl-tagged-address-codec)も開発）しました。これらの「パック化」したアドレスは、`r`ではなく`X`で開始します。詳細は、[XRPL 𝗫-address format](https://xrpaddress.info/)のサイトを参照してください。 + + **注記:** XRPコミュニティは、取引所およびウォレットで[宛先タグ](https://xrpl.org/source-and-destination-tags.html)の代わりに使用できる新しいフォーマット、**X**アドレスを[提案](https://github.com/xrp-community/standards-drafts/issues/6)（これをサポートする[コーデック](https://github.com/xrp-community/xrpl-tagged-address-codec)も開発）しました。これらの「パック化」したアドレスは、`r`ではなく`X`で開始します。詳細は、[𝗫-address format](https://xrpaddress.info/)のサイトを参照してください。 * 英数字を使用します（数字「`0`」、大文字「`O`」、大文字「`I`」、小文字「`l`」を除く） * 大/小文字を区別します * 4バイトのチェックサムを含むため、ランダムな文字から有効なアドレスが生成される確率はおよそ2^32分の1となります -{% if currentpage.md != "concept-accounts.md" %} +{% if currentpage.md != "concept-accounts.md" %} 詳しくは、[アカウント](accounts.html)と[base58エンコード](base58-encodings.html)を参照してください。{% endif %} diff --git a/content/_snippets/data_types/address.md b/content/_snippets/data_types/address.md index 327b2e4fea..8ba7d9353a 100644 --- a/content/_snippets/data_types/address.md +++ b/content/_snippets/data_types/address.md @@ -8,7 +8,7 @@ Accounts in the XRP Ledger are identified by an address in the XRP Ledger's [bas > **Note:** The XRP community has [proposed](https://github.com/xrp-community/standards-drafts/issues/6) an **X**-address format that "packs" a [destination tag](source-and-destination-tags.html) into the address. These addresses start with an `X` (for the mainnet) or a `T` (for the [testnet](parallel-networks.html)). Exchanges and wallets can use X-addresses to represent all the data a customer needs to know in one value. For more information, see the [X-address format site](https://xrpaddress.info/) and [codec](https://github.com/xrp-community/xrpl-tagged-address-codec). > -> The XRP Ledger protocol only supports "classic" addresses natively, but [ripple-lib](rippleapi-reference.html), [xrpl-py](https://github.com/XRPLF/xrpl-py), and many other tools support X-addresses too. +> The XRP Ledger protocol only supports "classic" addresses natively, but [ripple-lib](rippleapi-reference.html), [`xrpl-py`](https://github.com/XRPLF/xrpl-py), and many other tools support X-addresses too. {% if currentpage.md != "concept-accounts.md" %} For more information, see [Accounts](accounts.html) and [base58 Encodings](base58-encodings.html). diff --git a/content/_snippets/interactive-tutorials/generate-step.md b/content/_snippets/interactive-tutorials/generate-step.md index 19d218d1c3..68bad689c9 100644 --- a/content/_snippets/interactive-tutorials/generate-step.md +++ b/content/_snippets/interactive-tutorials/generate-step.md @@ -12,4 +12,4 @@
{{ end_step() }} -**Caution:** Ripple provides the [Testnet and Devnet](parallel-networks.html) for testing purposes only, and sometimes resets the state of these test networks along with all balances. As a precaution, Ripple recommends **not** using the same addresses on Testnet/Devnet and Mainnet. +**Caution:** Ripple provides the [Testnet and Devnet](parallel-networks.html) for testing purposes only, and sometimes resets the state of these test networks along with all balances. As a precaution, **do not** use the same addresses on Testnet/Devnet and Mainnet. diff --git a/content/_snippets/wait-for-validation.ja.md b/content/_snippets/wait-for-validation.ja.md index ff6cde9761..ba0ca7019d 100644 --- a/content/_snippets/wait-for-validation.ja.md +++ b/content/_snippets/wait-for-validation.ja.md @@ -1,3 +1,3 @@ -本番環境のネットワークやRipple Test Netでは、レジャーが自動的に閉鎖するまでに4～7秒かかる場合があります。 +本番環境のネットワークやTestnetでは、レジャーが自動的に閉鎖するまでに4～7秒かかる場合があります。 スタンドアロンモードで`rippled`を実行している場合は、[ledger_acceptメソッド][]を使用してレジャーを手動で閉鎖します。 diff --git a/content/_snippets/wait-for-validation.md b/content/_snippets/wait-for-validation.md index b88f2f7911..d020db203d 100644 --- a/content/_snippets/wait-for-validation.md +++ b/content/_snippets/wait-for-validation.md @@ -1,3 +1,3 @@ -On the live network or the Ripple Test Net, you can wait 4-7 seconds for the ledger to close automatically. +On a live network (including Mainnet, Testnet, or Devnet), you can wait 4-7 seconds for the ledger to close automatically. If you're running `rippled` in stand-alone mode, use the [ledger_accept method][] to manually close the ledger. diff --git a/content/concepts/consensus-network/amendments/amendments.md b/content/concepts/consensus-network/amendments/amendments.md index 636d3e4c3a..f730c7bf56 100644 --- a/content/concepts/consensus-network/amendments/amendments.md +++ b/content/concepts/consensus-network/amendments/amendments.md @@ -30,7 +30,7 @@ An amendment is a fully-functional feature or change, waiting to be enabled by t Every amendment has a unique identifying hex value and a short name. The short name is for human use, and is not used in the amendment process. Two servers can support the same amendment ID while using different names to describe it. An amendment's name is not guaranteed to be unique. -By convention, Ripple's developers use the SHA-512Half hash of the amendment name as the amendment ID. +By convention, an amendment's ID should be the SHA-512Half hash of the amendment's short name. ## Amendment Process @@ -59,7 +59,7 @@ Each version of `rippled` is compiled with a list of known amendments and the co To become enabled, an amendment must be supported by at least 80% of trusted validators continuously for two weeks. If support for an amendment goes below 80% of trusted validators, the amendment is temporarily rejected. The two week period starts over if the amendment regains support of at least 80% of trusted validators. (This can occur if validators vote differently, or if there is a change in which validators are trusted.) An amendment can gain and lose a majority any number of times before it becomes permanently enabled. An amendment cannot be permanently rejected, but it becomes very unlikely for an amendment to become enabled if new versions of `rippled` do not have the amendment in their known amendments list. -As with all aspects of the consensus process, amendment votes are only taken into account by servers that trust the validators sending those votes. At this time, Ripple (the company) recommends only trusting the validators on the validator list that Ripple publishes at . For now, trusting only those validators is enough to coordinate with Ripple on releasing new features. +As with all aspects of the consensus process, amendment votes are only taken into account by servers that trust the validators sending those votes. For information on how to configure your server's amendment votes, see [Configure Amendment Voting](configure-amendment-voting.html). [Updated in: rippled 1.7.0][] diff --git a/content/concepts/consensus-network/amendments/known-amendments.md b/content/concepts/consensus-network/amendments/known-amendments.md index d4d2ca6e83..260eacdccc 100644 --- a/content/concepts/consensus-network/amendments/known-amendments.md +++ b/content/concepts/consensus-network/amendments/known-amendments.md @@ -86,7 +86,7 @@ This amendment also changes the OfferCreate transaction to return `tecEXPIRED` w |:-----------------------------------------------------------------|:----------| | 1562511F573A19AE9BD103B5D6B9E01B3B46805AEC5D3C4805C902B514399146 | Enabled | -Although this amendment is enabled, it has no effect unless the [SusPay](#suspay) amendment is also enabled. Ripple does not expect SusPay to become enabled. Instead, Ripple plans to incorporate crypto-conditions in the [Escrow](#escrow) amendment. +Although this amendment is enabled, it has no effect unless the [SusPay](#suspay) amendment is also enabled. The SusPay amendment was replaced by the [Escrow](#escrow) amendment, so the CryptoConditions amendment has no effect. ## CryptoConditionsSuite @@ -152,7 +152,7 @@ Also changes the behavior of cross-currency Payments from an account to itself w |:-----------------------------------------------------------------|:----------| | DC9CA96AEA1DCF83E527D1AFC916EFAF5D27388ECA4060A88817C1238CAEE0BF | Enabled | -Adds sanity checks to transaction processing to ensure that certain conditions are always met. This provides an extra, independent layer of protection against bugs in transaction processing that could otherwise cause exploits and vulnerabilities in the XRP Ledger. Ripple expects to add more invariant checks in future versions of `rippled` without additional amendments. +Adds sanity checks to transaction processing to ensure that certain conditions are always met. This provides an extra, independent layer of protection against bugs in transaction processing that could otherwise cause exploits and vulnerabilities in the XRP Ledger. Future versions of `rippled` may add more invariants without additional amendments. Introduces two new transaction error codes, `tecINVARIANT_FAILED` and `tefINVARIANT_FAILED`. Changes transaction processing to add the new checks. @@ -351,8 +351,6 @@ With this amendment enabled, transaction processing adds a `DeliveredAmount` fie The fix1623 amendment has no effect on [CheckCash transactions][] for a fixed amount (using the `Amount` field) or any other transaction types. -**Caution:** In `rippled` 1.0.0, if the Checks amendment is enabled before the fix1623 amendment, the `delivered_amount` may display as "0" for variable-amount CheckCash transactions from before this amendment was enabled, even if the transaction delivered a nonzero amount. Ripple plans to enable fix1623 at the same time as the [Checks][] amendment on the production network, but this situation may be possible on [parallel networks](parallel-networks.html). - ## fix1781 [fix1781]: #fix1781 @@ -586,7 +584,7 @@ Fixes an inconsistency in the way [transfer fees](transfer-fees.html) are calcul This Amendment requires the [Flow Amendment](#flow) to be enabled. -**Note:** An incomplete version of this amendment was introduced in v0.33.0 and removed in v0.80.0. (It was never enabled.) Ripple plans to re-add the amendment when the code is stable enough. +**Note:** An incomplete version of this amendment was introduced in v0.33.0 and removed in v0.80.0. (It was never enabled.) ## PayChan @@ -596,7 +594,7 @@ This Amendment requires the [Flow Amendment](#flow) to be enabled. |:-----------------------------------------------------------------|:----------| | 08DE7D96082187F6E6578530258C77FAABABE4C20474BDB82F04B021F1A68647 | Enabled | -Creates "Payment Channels" for XRP. Payment channels are a tool for facilitating repeated, unidirectional payments or temporary credit between two parties. Ripple expects this feature to be useful for the [Interledger Protocol](https://interledger.org/). One party creates a Payment Channel and sets aside some XRP in that channel for a predetermined expiration. Then, through off-ledger secure communications, the sender can send "Claim" messages to the receiver. The receiver can redeem the Claim messages before the expiration, or choose not to in case the payment is not needed. The receiver can verify Claims individually without actually distributing them to the network and waiting for the consensus process to redeem them, then redeem the combined content of many small Claims later, as long as it is within the expiration. +Creates "Payment Channels" for XRP. Payment channels are a tool for facilitating repeated, unidirectional payments or temporary credit between two parties. This feature is expected to be useful for the [Interledger Protocol](https://interledger.org/). One party creates a Payment Channel and sets aside some XRP in that channel for a predetermined expiration. Then, through off-ledger secure communications, the sender can send "Claim" messages to the receiver. The receiver can redeem the Claim messages before the expiration, or choose not to in case the payment is not needed. The receiver can verify Claims individually without actually distributing them to the network and waiting for the consensus process to redeem them, then redeem the combined content of many small Claims later, as long as it is within the expiration. Creates three new transaction types: [PaymentChannelCreate][], [PaymentChannelClaim][], and [PaymentChannelFund][]. Creates a new ledger object type, [PayChannel](paychannel.html). Defines an off-ledger data structure called a `Claim`; the PaymentChannelClaim uses a signature for this data structure. Creates new `rippled` API methods: [`channel_authorize`](channel_authorize.html) (creates a signed Claim), [`channel_verify`](channel_verify.html) (verifies a signed Claim), and [`account_channels`](account_channels.html) (lists Channels associated with an account). @@ -662,7 +660,7 @@ This amendment was replaced by the [Escrow](escrow-object.html) amendment. This amendment adds [Tickets](tickets.html) as a way of sending transactions out of the typical sequence number order. -Standards Draft: [XLS-13d](https://github.com/xrp-community/standards-drafts/issues/16). +Standards Draft: [XLS-13d](https://github.com/xrp-community/standards-drafts/issues/16). ## Tickets diff --git a/content/concepts/consensus-network/consensus-protections.md b/content/concepts/consensus-network/consensus-protections.md index b28376ef03..bfc2c94c5b 100644 --- a/content/concepts/consensus-network/consensus-protections.md +++ b/content/concepts/consensus-network/consensus-protections.md @@ -30,7 +30,7 @@ The only way to confirm an invalid transaction would be to get at least 80% of t ## Software Vulnerabilities -As with any software system, bugs (or intentionally malicious code) in the implementation of the XRP Ledger Consensus Protocol, commonly deployed software packages, or their dependencies, are a problem to be taken seriously. Even bugs that cause a server to crash when it sees carefully crafted inputs can be abused to disrupt the progress of the network. Ripple has a number of precautions in place to address this threat, including: +As with any software system, bugs (or intentionally malicious code) in the implementation of the XRP Ledger Consensus Protocol, commonly deployed software packages, or their dependencies, are a problem to be taken seriously. Even bugs that cause a server to crash when it sees carefully crafted inputs can be abused to disrupt the progress of the network. Ripple takes precautions to address this threat in its reference implementations of XRP Ledger software, including: - An [open-source code base](https://github.com/ripple/rippled/), so any member of the public can review, compile, and independently test the relevant software. - A thorough and robust code review process for all changes to the official XRP Ledger repositories. diff --git a/content/concepts/decentralized-exchange/autobridging.md b/content/concepts/decentralized-exchange/autobridging.md index d214f56e44..51a4e1f661 100644 --- a/content/concepts/decentralized-exchange/autobridging.md +++ b/content/concepts/decentralized-exchange/autobridging.md @@ -7,7 +7,7 @@ blurb: Autobriding automatically connects order books using XRP as an intermedia Any [Offer](offers.html) in the XRP Ledger's [decentralized exchange](decentralized-exchange.html) that would exchange two non-XRP currencies could potentially use [XRP](xrp.html) as an intermediary currency in a synthetic order book. This is because of _auto-bridging_, which serves to improve liquidity across all currency pairs by using XRP when doing so is cheaper than trading those currencies directly. This works because of XRP's nature as a native cryptocurrency to the XRP Ledger. Offer execution can use a combination of direct and auto-bridged offers to achieve the best total exchange rate. -Example: _Anita places an offer to sell GBP and buy BRL. She might find that this uncommon currency market has few offers. There is one offer with a good rate, but it has insufficient quantity to satisfy Anita's trade. However, both GBP and BRL have active, competitive markets to XRP. The XRP Ledger's auto-bridging system finds a way to complete Anita's offer by purchasing XRP with GBP from one trader, then selling the XRP to another trader to buy BRL. Anita automatically gets the best rate possible by combining the small offer in the direct GBP:BRL market with the better composite rates created by pairing GBP:XRP and XRP:BRL offers._ +Example: _Anita places an offer to sell GBP and buy BRL. She might find that this uncommon currency market has few offers. There is one offer with a good rate, but it has insufficient quantity to satisfy Anita's trade. However, both GBP and BRL have active, competitive markets to XRP. The XRP Ledger's auto-bridging system finds a way to complete Anita's offer by purchasing XRP with GBP from one trader, then selling the XRP to another trader to buy BRL. Anita automatically gets the best rate possible by combining the small offer in the direct GBP:BRL market with the better composite rates created by pairing GBP:XRP and XRP:BRL offers._ Auto-bridging happens automatically on any [OfferCreate transaction][]. [Payment transactions](payment.html) _do not_ use auto-bridging by default, but path-finding can find [paths](paths.html) that have the same effect. diff --git a/content/concepts/issued-currencies/issued-currencies-overview.md b/content/concepts/issued-currencies/issued-currencies-overview.md index e93cd4c3d1..44bc92bc69 100644 --- a/content/concepts/issued-currencies/issued-currencies-overview.md +++ b/content/concepts/issued-currencies/issued-currencies-overview.md @@ -15,9 +15,9 @@ In the typical model, an issued currency is tied to holdings of currency or othe There are other use cases for issued currencies in the XRP Ledger. For example, you can create an "Initial Coin Offering" (ICO) by issuing a fixed amount of currency to a secondary address, then "throwing away the key" to the issuer. -**Warning:** ICOs may be [regulated as securities](https://www.sec.gov/oiea/investor-alerts-and-bulletins/ib_coinofferings) in the USA. +**Warning:** ICOs may be [regulated as securities](https://www.sec.gov/oiea/investor-alerts-and-bulletins/ib_coinofferings) in the USA. -Ripple strongly recommends researching the relevant regulations before engaging in any financial service business. +Be sure to research the relevant regulations before engaging in any financial service business. ## Issued Currency Usage diff --git a/content/concepts/payment-system-basics/accounts/cryptographic-keys.md b/content/concepts/payment-system-basics/accounts/cryptographic-keys.md index 2c3d771650..da021f3de3 100644 --- a/content/concepts/payment-system-basics/accounts/cryptographic-keys.md +++ b/content/concepts/payment-system-basics/accounts/cryptographic-keys.md @@ -37,7 +37,7 @@ For more technical details of how key derivation works, see [Key Derivation](#ke ### Passphrase -You can, optionally, use a passphrase or some other input as a way of choosing a seed or private key. This is less secure than choosing the seed or private key completely at random, but there are some rare cases where you want to do this. (For example, in 2018 "XRPuzzler" gave away XRP to the first person [to solve a puzzle](https://bitcoinexchangeguide.com/cryptographic-puzzle-creator-xrpuzzler-offers-137-xrp-reward-to-anyone-who-can-solve-it/); he used the puzzle's solution as the passphrase to an account holding the prize XRP.) +You can, optionally, use a passphrase or some other input as a way of choosing a seed or private key. This is less secure than choosing the seed or private key completely at random, but there are some rare cases where you want to do this. (For example, in 2018 "XRPuzzler" gave away XRP to the first person [to solve a puzzle](https://bitcoinexchangeguide.com/cryptographic-puzzle-creator-xrpuzzler-offers-137-xrp-reward-to-anyone-who-can-solve-it/); he used the puzzle's solution as the passphrase to an account holding the prize XRP.) The passphrase is secret information, so you must protect it very carefully. Anyone who knows an address's passphrase has effectively full control over the address. diff --git a/content/contributing/contribute-code.md b/content/contributing/contribute-code.md index 85b54dc954..002ffeb728 100644 --- a/content/contributing/contribute-code.md +++ b/content/contributing/contribute-code.md @@ -24,6 +24,6 @@ You can find various XRP Ledger-related projects under these and other GitHub or - [Ripple](https://github.com/ripple/) - [RippleX (formerly Xpring)](https://github.com/xpring-eng/) - [XRP Community](https://github.com/xrp-community/) -- [XRPL Labs](https://github.com/XRPL-Labs/) +- [XRPL Labs](https://github.com/XRPL-Labs/) Be sure to look at each repository's license and contributing guidelines before contributing to that repository. diff --git a/content/references/protocol-reference/currency-formats.md b/content/references/protocol-reference/currency-formats.md index 6e4c8fa960..5a9a6ad3b4 100644 --- a/content/references/protocol-reference/currency-formats.md +++ b/content/references/protocol-reference/currency-formats.md @@ -93,7 +93,7 @@ The issued currency format can store a wide variety of assets, including those t When sending issued currency amounts in the XRP Ledger's peer-to-peer network, servers [serialize](serialization.html) the amount to a 64-bit binary value. -**Note:** The XRP Ledger does not **natively** support issued currencies that are not [fungible](https://en.wikipedia.org/wiki/Fungibility), while non-fungible issued currencies can be implemented by clients implementing a proposed standard like [XLS-14d](https://github.com/XRPLF/XRPL-Standards/discussions/30). It also does not support limiting an issued currency to whole number amounts only. All issued currencies in the XRP Ledger are always divisible down to the minimum amount. +**Note:** The XRP Ledger does not **natively** support issued currencies that are not [fungible](https://en.wikipedia.org/wiki/Fungibility). It also does not support limiting an issued currency to whole number amounts only. All issued currencies in the XRP Ledger are always divisible down to the minimum amount. However non-fungible issued currencies can be implemented in clients following a proposed standard like [XLS-14d](https://github.com/XRPLF/XRPL-Standards/discussions/30). ## Currency Codes [Currency Code]: #currency-codes diff --git a/content/references/protocol-reference/ledger-data/ledger-object-types/negativeunl.md b/content/references/protocol-reference/ledger-data/ledger-object-types/negativeunl.md index 16a6b77b62..6fe654d562 100644 --- a/content/references/protocol-reference/ledger-data/ledger-object-types/negativeunl.md +++ b/content/references/protocol-reference/ledger-data/ledger-object-types/negativeunl.md @@ -41,6 +41,7 @@ A `NegativeUNL` object has the following fields: | `ValidatorToReEnable` | String | Blob | _(May be omitted)_ The public key of a trusted validator in the Negative UNL that is scheduled to be re-enabled in the next flag ledger. | ## DisabledValidator Objects + Each `DisabledValidator` object represents one disabled validator. In JSON, a `DisabledValidator` object has one field, `DisabledValidator`, which in turn contains another object with the following fields: diff --git a/content/references/rippled-api/peer-port-methods/peer-crawler.md b/content/references/rippled-api/peer-port-methods/peer-crawler.md index 89ca8dd42e..20fa6d7c13 100644 --- a/content/references/rippled-api/peer-port-methods/peer-crawler.md +++ b/content/references/rippled-api/peer-port-methods/peer-crawler.md @@ -20,7 +20,7 @@ To request the Peer Crawler information, make the following HTTP request: - **Path:** `/crawl` - **Security:** Most `rippled` servers use a self-signed certificate to respond to the request. By default, most tools (including web browsers) flag or block such responses for being untrusted. You must ignore the certificate checking (for example, if using cURL, add the `--insecure` flag) to display a response from those servers. -**Tip:** Since this request uses the GET method, you can test this request using the URL bar of your web browser. For example, requests peer crawler information from one of Ripple's public servers. +**Tip:** Since this request uses the GET method, you can test this request using the URL bar of your web browser. For example, requests peer crawler information from one of Ripple's public servers. ## Response Format diff --git a/content/tutorials/get-started/get-started-using-java.md b/content/tutorials/get-started/get-started-using-java.md index 8ad10d3d2a..3fcf065e80 100644 --- a/content/tutorials/get-started/get-started-using-java.md +++ b/content/tutorials/get-started/get-started-using-java.md @@ -29,7 +29,7 @@ In this tutorial, you'll learn: ## Requirements * The `xrpl4j` library supports Java 1.8 and later. -* A project management tool such as [Maven](https://maven.apache.org/) or [Gradle](https://gradle.org/). +* A project management tool such as [Maven](https://maven.apache.org/) or [Gradle](https://gradle.org/). ## Installation @@ -37,10 +37,7 @@ In this tutorial, you'll learn: The [`xrpl4j` library](https://github.com/XRPLF/xrpl4j) is available on [Maven Central](https://search.maven.org/artifact/org.xrpl/xrpl4j-parent). `xrpl4j` is split into multiple artifacts, which can be imported as needed. -In this tutorial, you will need the [xrpl4j-client](https://javadoc.io/doc/org.xrpl/xrpl4j-client/latest/index.html), -[xrpl4j-address-codec](https://javadoc.io/doc/org.xrpl/xrpl4j-address-codec/latest/index.html), -[xrpl4j-keypairs](https://javadoc.io/doc/org.xrpl/xrpl4j-keypairs/latest/index.html), and -[xrpl4j-model](https://javadoc.io/doc/org.xrpl/xrpl4j-model/latest/index.html) modules. +In this tutorial, you will need the [xrpl4j-client](https://javadoc.io/doc/org.xrpl/xrpl4j-client/latest/index.html), [xrpl4j-address-codec](https://javadoc.io/doc/org.xrpl/xrpl4j-address-codec/latest/index.html), [xrpl4j-keypairs](https://javadoc.io/doc/org.xrpl/xrpl4j-keypairs/latest/index.html), and [xrpl4j-model](https://javadoc.io/doc/org.xrpl/xrpl4j-model/latest/index.html) modules. To install with Maven, add the following to your project's `pom.xml` file and then run `mvn install`: @@ -138,13 +135,13 @@ Wallet { } ``` -In order to fund the account on the XRP Ledger, you can use a `FaucetClient` connected to the XRPL Testnet: +In order to fund the account on the XRP Ledger, you can use a `FaucetClient` connected to the XRP Ledger Testnet: {{ include_code("_code-samples/xrpl4j/GetAccountInfo.java", start_with="// Fund the account using the testnet Faucet", end_before="// Look up your Account Info", language="java") }} ### {{n.next()}}. Query the XRP Ledger -You can query the XRP Ledger to get information about [a specific account](account-methods.html), [a specific transaction](tx.html), the state of a [current or a historical ledger](ledger-methods.html), and [the XRP Ledger's decentralized exhange](path-and-order-book-methods.html). You need to make these queries, among other reasons, to look up account info to follow best practices for [reliable transaction submission](reliable-transaction-submission.html). +You can query the XRP Ledger to get information about [a specific account](account-methods.html), [a specific transaction](tx.html), the state of a [current or a historical ledger](ledger-methods.html), and [the XRP Ledger's decentralized exchange](path-and-order-book-methods.html). You need to make these queries, among other reasons, to look up account info to follow best practices for [reliable transaction submission](reliable-transaction-submission.html). Here, we'll use the [`XrplClient` we constructed](#1-connect-to-the-xrp-ledger) to look up information about the [wallet we generated](#2-generate-wallet) in the previous step. diff --git a/content/tutorials/get-started/get-started-using-node-js.md b/content/tutorials/get-started/get-started-using-node-js.md index 9ef86a2b93..89a4fa7fc2 100644 --- a/content/tutorials/get-started/get-started-using-node-js.md +++ b/content/tutorials/get-started/get-started-using-node-js.md @@ -277,7 +277,7 @@ _jsDelivr_ Instead of using Node.js's "require" syntax, the browser version creates a global variable named `ripple`, which contains the `RippleAPI` class. - + ## Build a Browser-Compatible Version of RippleAPI diff --git a/content/tutorials/get-started/get-started-using-python.md b/content/tutorials/get-started/get-started-using-python.md index 12f85e436d..04fadaf4d0 100644 --- a/content/tutorials/get-started/get-started-using-python.md +++ b/content/tutorials/get-started/get-started-using-python.md @@ -30,7 +30,7 @@ The `xrpl-py` library supports [Python 3.7](https://www.python.org/downloads/) a ## Installation -The [`xrpl-py` library](https://github.com/XRPLF/xrpl-py) is available on [PyPI](https://pypi.org/project/xrpl-py/). Install with `pip`: +The [`xrpl-py` library](https://github.com/XRPLF/xrpl-py) is available on [PyPI](https://pypi.org/project/xrpl-py/). Install with `pip`: ```py @@ -140,7 +140,7 @@ The X-address format [packs the address and destination tag](https://github.com/ ### {{n.next()}}. Query the XRP Ledger -You can query the XRP Ledger to get information about [a specific account](account-methods.html), [a specific transaction](tx.html), the state of a [current or a historical ledger](ledger-methods.html), and [the XRP Ledger's decentralized exhange](path-and-order-book-methods.html). You need to make these queries, among other reasons, to look up account info to follow best practices for [reliable transaction submission](reliable-transaction-submission.html). +You can query the XRP Ledger to get information about [a specific account](account-methods.html), [a specific transaction](tx.html), the state of a [current or a historical ledger](ledger-methods.html), and [the XRP Ledger's decentralized exchange](path-and-order-book-methods.html). You need to make these queries, among other reasons, to look up account info to follow best practices for [reliable transaction submission](reliable-transaction-submission.html). Here, we'll use `xrpl-py`'s [`xrpl.account`](https://xrpl-py.readthedocs.io/en/latest/source/xrpl.account.html) module to look up information about the [wallet we generated](#2-generate-wallet) in the previous step. diff --git a/content/tutorials/get-started/get-started.md b/content/tutorials/get-started/get-started.md index 99eaf1fd82..f30f5ed131 100644 --- a/content/tutorials/get-started/get-started.md +++ b/content/tutorials/get-started/get-started.md @@ -12,7 +12,7 @@ The XRP Ledger is always online and entirely public. Anyone can access it **dire The following example gets the latest [ledger version](ledgers.html) and a list of transactions that were newly-validated in that ledger version, using the [`getLedger()` method](rippleapi-reference.html#getledger). Try running it as-is, or change the code and see what happens. -**Tip:** If you can, open your browser's Developer Tools by pressing **F12**. The "Console" tab provides a native JavaScript console and can give insight into what code is running on any webpage. +**Tip:** If you can, open your browser's Developer Tools by pressing **F12**. The "Console" tab provides a native JavaScript console and can give insight into what code is running on any webpage. {{currentpage.lodash_tag}} diff --git a/content/tutorials/get-started/send-xrp.md b/content/tutorials/get-started/send-xrp.md index 34ae1ab206..b13477826d 100644 --- a/content/tutorials/get-started/send-xrp.md +++ b/content/tutorials/get-started/send-xrp.md @@ -10,7 +10,7 @@ filters: --- # Send XRP -This tutorial explains how to send a simple XRP Payment using ripple-lib for JavaScript, xrpl-py for Python, or xrpl4j for Java. First, we step through the process with the [XRP Ledger Testnet](parallel-networks.html). Then, we compare that to the additional requirements for doing the equivalent in production. +This tutorial explains how to send a simple XRP Payment using ripple-lib for JavaScript, `xrpl-py` for Python, or xrpl4j for Java. First, we step through the process with the [XRP Ledger Testnet](parallel-networks.html). Then, we compare that to the additional requirements for doing the equivalent in production. **Tip:** Check out the [Code Samples](https://github.com/ripple/xrpl-dev-portal/tree/master/content/_code-samples) for a complete version of the code used in this tutorial. @@ -23,7 +23,7 @@ This tutorial explains how to send a simple XRP Payment using ripple-lib for Jav To interact with the XRP Ledger, you need to set up a dev environment with the necessary tools. This tutorial provides examples using the following options: - **JavaScript** with the [ripple-lib (RippleAPI) library](https://github.com/ripple/ripple-lib/). See the [RippleAPI Beginners Guide](get-started-with-rippleapi-for-javascript.html) for detailed instructions on getting started. -- **Python** with the [xrpl-py library](https://xrpl-py.readthedocs.io/). See [Get Started using Python](get-started-using-python.html) for setup steps. +- **Python** with the [`xrpl-py` library](https://xrpl-py.readthedocs.io/). See [Get Started using Python](get-started-using-python.html) for setup steps. - **Java** with the [xrpl4j library](https://github.com/XRPLF/xrpl4j). See [Get Started Using Java](get-started-using-java.html) for setup steps. @@ -73,7 +73,7 @@ _Python_ {{ include_code("_code-samples/send-xrp/send-xrp.py", start_with="# Connect", end_before="# Get credentials", language="py") }} -_Java_ +_Java_ {{ include_code("_code-samples/send-xrp/SendXrp.java", start_with="// Connect", end_before="// Prepare transaction", language="java") }} @@ -107,10 +107,10 @@ The bare minimum set of instructions you must provide for an XRP Payment is: Technically, a viable transaction must contain some additional fields, and certain optional fields such as `LastLedgerSequence` are strongly recommended. Some other language-specific notes: - If you're using ripple-lib for JavaScript, you can use the [`prepareTransaction()` method](rippleapi-reference.html#preparetransaction) to automatically fill in good defaults for the remaining fields of a transaction. -- With xrpl-py for Python, you can use the models in `xrpl.models.transactions` to construct transactions as native Python objects. +- With `xrpl-py` for Python, you can use the models in `xrpl.models.transactions` to construct transactions as native Python objects. - With xrpl4j for Java, you can use the model objects in the `xrpl4j-model` module to construct transactions as Java objects. - - Unlike the other SDKs, you must provide the account `sequence` and the `signingPublicKey` of the source - account of a `Transaction` at the time of construction, as well as a `fee`. + - Unlike the other libraries, you must provide the account `sequence` and the `signingPublicKey` of the source + account of a `Transaction` at the time of construction, as well as a `fee`. Here's an example of preparing the above payment: @@ -153,7 +153,7 @@ _Java_ Signing a transaction uses your credentials to authorize the transaction on your behalf. The input to this step is a completed set of transaction instructions (usually JSON), and the output is a binary blob containing the instructions and a signature from the sender. - **JavaScript:** Use the [sign() method](rippleapi-reference.html#sign) to sign the transaction with ripple-lib. The first argument is a string version of the JSON transaction to sign. -- **Python:** Use the [xrpl.transaction.safe_sign_transaction() method](https://xrpl-py.readthedocs.io/en/latest/source/xrpl.transaction.html#xrpl.transaction.safe_sign_transaction) with a model and wallet object. +- **Python:** Use the [`xrpl.transaction.safe_sign_transaction()` method](https://xrpl-py.readthedocs.io/en/latest/source/xrpl.transaction.html#xrpl.transaction.safe_sign_transaction) with a model and wallet object. - **Java:** Use a [`SignatureService`](https://javadoc.io/doc/org.xrpl/xrpl4j-crypto-core/latest/org/xrpl/xrpl4j/crypto/signing/SignatureService.html) instance to sign the transaction. For this tutorial, use the [`SingleKeySignatureService`](https://javadoc.io/doc/org.xrpl/xrpl4j-crypto-bouncycastle/latest/org/xrpl/xrpl4j/crypto/signing/SingleKeySignatureService.html). @@ -172,13 +172,13 @@ _Java_ {{ include_code("_code-samples/send-xrp/SendXrp.java", start_with="// Sign", end_before="// Submit", language="java" ) }} - + The result of the signing operation is a transaction object containing a signature. Typically, XRP Ledger APIs expect a signed transaction to be the hexadecimal representation of the transaction's canonical [binary format](serialization.html), called a "blob". - In ripple-lib, the signing API also returns the transaction's ID, or identifying hash, which you can use to look up the transaction later. This is a 64-character hexadecimal string that is unique to this transaction. -- In xrpl-py, you can get the transaction's hash in the response to submitting it in the next step. +- In `xrpl-py`, you can get the transaction's hash in the response to submitting it in the next step. - In xrpl4j, `SignatureService.sign` returns a `SignedTransaction`, which contains the transaction's hash, which you can use to look up the transaction later. {{ start_step("Sign") }} @@ -192,9 +192,9 @@ The result of the signing operation is a transaction object containing a signatu Now that you have a signed transaction, you can submit it to an XRP Ledger server, and that server will relay it through the network. It's also a good idea to take note of the latest validated ledger index before you submit. The earliest ledger version that your transaction could get into as a result of this submission is one higher than the latest validated ledger when you submit it. Of course, if the same transaction was previously submitted, it could already be in a previous ledger. (It can't succeed a second time, but you may not realize it succeeded if you aren't looking in the right ledger versions.) -- **JavaScript:** Use the [submit() method](rippleapi-reference.html#submit) to submit a transaction to the network. Use the [`getLedgerVersion()` method](rippleapi-reference.html#getledgerversion) to get the latest validated ledger index. -- **Python:** Use the [xrpl.transaction.submit_transaction() method](https://xrpl-py.readthedocs.io/en/latest/source/xrpl.transaction.html#xrpl.transaction.submit_transaction) to submit a transaction to the network. Use the [xrpl.ledger.get_latest_validated_ledger_sequence() method](https://xrpl-py.readthedocs.io/en/latest/source/xrpl.ledger.html#xrpl.ledger.get_latest_validated_ledger_sequence) to get the latest validated ledger index. -- **Java:** Use the [XrplClient.submit(SignedTransaction) method](https://javadoc.io/doc/org.xrpl/xrpl4j-client/latest/org/xrpl/xrpl4j/client/XrplClient.html#submit(org.xrpl.xrpl4j.crypto.signing.SignedTransaction)) to submit a transaction to the network. Use the [`XrplClient.ledger()`](https://javadoc.io/doc/org.xrpl/xrpl4j-client/latest/org/xrpl/xrpl4j/client/XrplClient.html#ledger(org.xrpl.xrpl4j.model.client.ledger.LedgerRequestParams)) method to get the latest validated ledger index. +- **JavaScript:** Use the [`submit()` method](rippleapi-reference.html#submit) to submit a transaction to the network. Use the [`getLedgerVersion()` method](rippleapi-reference.html#getledgerversion) to get the latest validated ledger index. +- **Python:** Use the [`xrpl.transaction.submit_transaction()` method](https://xrpl-py.readthedocs.io/en/latest/source/xrpl.transaction.html#xrpl.transaction.submit_transaction) to submit a transaction to the network. Use the [`xrpl.ledger.get_latest_validated_ledger_sequence()` method](https://xrpl-py.readthedocs.io/en/latest/source/xrpl.ledger.html#xrpl.ledger.get_latest_validated_ledger_sequence) to get the latest validated ledger index. +- **Java:** Use the [`XrplClient.submit(SignedTransaction)` method](https://javadoc.io/doc/org.xrpl/xrpl4j-client/latest/org/xrpl/xrpl4j/client/XrplClient.html#submit(org.xrpl.xrpl4j.crypto.signing.SignedTransaction)) to submit a transaction to the network. Use the [`XrplClient.ledger()`](https://javadoc.io/doc/org.xrpl/xrpl4j-client/latest/org/xrpl/xrpl4j/client/XrplClient.html#ledger(org.xrpl.xrpl4j.model.client.ledger.LedgerRequestParams)) method to get the latest validated ledger index. @@ -235,11 +235,11 @@ example transaction Most transactions are accepted into the next ledger version after they're submitted, which means it may take 4-7 seconds for a transaction's outcome to be final. If the XRP Ledger is busy or poor network connectivity delays a transaction from being relayed throughout the network, a transaction may take longer to be confirmed. (For more information on expiration of unconfirmed transactions, see [Reliable Transaction Submission](reliable-transaction-submission.html).) - **JavaScript:** Use an account [subscription](rippleapi-reference.html#listening-to-streams) to listen for an event when the transaction is confirmed. Use the `ledger` event type to trigger your code to run whenever there is a new validated ledger version so that you can know if the transaction can no longer be confirmed. -- **Python:** Poll the [xrpl.transaction.get_transaction_from_hash() method](https://xrpl-py.readthedocs.io/en/latest/source/xrpl.transaction.html#xrpl.transaction.get_transaction_from_hash) to see if your transaction has a final result. Periodically use the [xrpl.ledger.get_latest_validated_ledger_sequence() method](https://xrpl-py.readthedocs.io/en/latest/source/xrpl.ledger.html#xrpl.ledger.get_latest_validated_ledger_sequence) so you can know if the transaction can no longer be confirmed. +- **Python:** Poll the [`xrpl.transaction.get_transaction_from_hash()` method](https://xrpl-py.readthedocs.io/en/latest/source/xrpl.transaction.html#xrpl.transaction.get_transaction_from_hash) to see if your transaction has a final result. Periodically use the [`xrpl.ledger.get_latest_validated_ledger_sequence()` method](https://xrpl-py.readthedocs.io/en/latest/source/xrpl.ledger.html#xrpl.ledger.get_latest_validated_ledger_sequence) so you can know if the transaction can no longer be confirmed. - **Tip:** The [xrpl.transaction.send_reliable_submission() method](https://xrpl-py.readthedocs.io/en/latest/source/xrpl.transaction.html#xrpl.transaction.send_reliable_submission) handles this process all in one call. You can use this instead of `submit_transaction()` wherever it's appropriate for your code to stop and wait for a transaction's [final result](finality-of-results.html) to be confirmed. - -- **Java** Poll the [XrplClient.transaction() method](https://javadoc.io/doc/org.xrpl/xrpl4j-client/latest/org/xrpl/xrpl4j/client/XrplClient.html#transaction(org.xrpl.xrpl4j.model.client.transactions.TransactionRequestParams,java.lang.Class)) to see if your transaction has a final result. Periodically check that the latest validated ledger index has not passed the `LastLedgerIndex` of the transaction using the [`XrplClient.ledger()`](https://javadoc.io/doc/org.xrpl/xrpl4j-client/latest/org/xrpl/xrpl4j/client/XrplClient.html#ledger(org.xrpl.xrpl4j.model.client.ledger.LedgerRequestParams)) method. + **Tip:** The [`xrpl.transaction.send_reliable_submission()` method](https://xrpl-py.readthedocs.io/en/latest/source/xrpl.transaction.html#xrpl.transaction.send_reliable_submission) handles this process all in one call. You can use this instead of `submit_transaction()` wherever it's appropriate for your code to stop and wait for a transaction's [final result](finality-of-results.html) to be confirmed. + +- **Java** Poll the [`XrplClient.transaction()` method](https://javadoc.io/doc/org.xrpl/xrpl4j-client/latest/org/xrpl/xrpl4j/client/XrplClient.html#transaction(org.xrpl.xrpl4j.model.client.transactions.TransactionRequestParams,java.lang.Class)) to see if your transaction has a final result. Periodically check that the latest validated ledger index has not passed the `LastLedgerIndex` of the transaction using the [`XrplClient.ledger()`](https://javadoc.io/doc/org.xrpl/xrpl4j-client/latest/org/xrpl/xrpl4j/client/XrplClient.html#ledger(org.xrpl.xrpl4j.model.client.ledger.LedgerRequestParams)) method. @@ -267,7 +267,7 @@ _Java_ To know for sure what a transaction did, you must look up the outcome of the transaction when it appears in a validated ledger version. - **JavaScript:** Use the [`getTransaction()` method](rippleapi-reference.html#gettransaction) to check the status of a transaction. -- **Python:** The response of [xrpl.transaction.get_transaction_from_hash() method](https://xrpl-py.readthedocs.io/en/latest/source/xrpl.transaction.html#xrpl.transaction.get_transaction_from_hash) contains the results if the transaction has been validated by consensus. (See [tx result](https://xrpl.org/tx.html#response-format) for a detailed reference of the fields this can contain.) +- **Python:** The response of [`xrpl.transaction.get_transaction_from_hash()` method](https://xrpl-py.readthedocs.io/en/latest/source/xrpl.transaction.html#xrpl.transaction.get_transaction_from_hash) contains the results if the transaction has been validated by consensus. (See the [tx method response format](tx.html#response-format) for a detailed reference of the fields this can contain.) - **Java:** Use the [`XrplClient.transaction()`](https://javadoc.io/doc/org.xrpl/xrpl4j-client/latest/org/xrpl/xrpl4j/client/XrplClient.html#transaction(org.xrpl.xrpl4j.model.client.transactions.TransactionRequestParams,java.lang.Class)) method to check the status of a transaction. @@ -409,7 +409,7 @@ XrplClient xrplClient = new XrplClient(rippledUrl); After completing this tutorial, you may want to try the following: - Build [Reliable transaction submission](reliable-transaction-submission.html) for production systems. -- Consult [RippleAPI JavaScript Reference](rippleapi-reference.html), [xrpl-py Python Reference](https://xrpl-py.readthedocs.io/), or [xrpl4j Javadocs](https://javadoc.io/doc/org.xrpl/) for the full range of XRP Ledger functionality. +- Consult [RippleAPI JavaScript Reference](rippleapi-reference.html), [`xrpl-py` Python Reference](https://xrpl-py.readthedocs.io/), or [xrpl4j Javadocs](https://javadoc.io/doc/org.xrpl/) for the full range of XRP Ledger functionality. - Customize your [Account Settings](manage-account-settings.html). - Learn how [Transaction Metadata](transaction-metadata.html) describes the outcome of a transaction in detail. - Explore more [Payment Types](payment-types.html) such as Escrows and Payment Channels. diff --git a/content/tutorials/manage-the-rippled-server/installation/capacity-planning.md b/content/tutorials/manage-the-rippled-server/installation/capacity-planning.md index 454340f0ed..d424f33f79 100644 --- a/content/tutorials/manage-the-rippled-server/installation/capacity-planning.md +++ b/content/tutorials/manage-the-rippled-server/installation/capacity-planning.md @@ -184,7 +184,7 @@ Memory requirements are mainly a function of the `node_size` configuration setti Any enterprise or carrier-class data center should have substantial network bandwidth to support running `rippled` servers. The actual bandwidth necessary varies significantly based on the current transaction volume in the network. Server behavior (such as backfilling [ledger history](ledger-history.html)) also affects network use. -During exceptionally high periods of transaction volume, some operators have reported that their `rippled` servers have completely saturated a 100 MBit/s network link. Therefore, a gigabit network interface is required for reliable performance. +During exceptionally high periods of transaction volume, some operators have reported that their `rippled` servers have completely saturated a 100 megabit/s network link. Therefore, a gigabit network interface is required for reliable performance. Here are examples of observed uncompressed network bandwidth use for common `rippled` tasks: diff --git a/content/tutorials/manage-the-rippled-server/installation/system-requirements.md b/content/tutorials/manage-the-rippled-server/installation/system-requirements.md index 62480486d5..c66aad744f 100644 --- a/content/tutorials/manage-the-rippled-server/installation/system-requirements.md +++ b/content/tutorials/manage-the-rippled-server/installation/system-requirements.md @@ -16,7 +16,7 @@ A `rippled` server should run comfortably on commodity hardware, to make it inex - Disk: Minimum 50 GB for the database partition. SSD strongly recommended (minimum 1000 IOPS, more is better) - RAM: 8 GB+ - + Amazon EC2's `m3.large` VM size may be appropriate depending on your workload. A fast network connection is preferable. Any increase in a server's client-handling load increases resources needs. diff --git a/content/tutorials/manage-the-rippled-server/installation/update-rippled-manually-on-centos-rhel.md b/content/tutorials/manage-the-rippled-server/installation/update-rippled-manually-on-centos-rhel.md index 1a27e82643..615223f018 100644 --- a/content/tutorials/manage-the-rippled-server/installation/update-rippled-manually-on-centos-rhel.md +++ b/content/tutorials/manage-the-rippled-server/installation/update-rippled-manually-on-centos-rhel.md @@ -13,7 +13,7 @@ These instructions assume you have already [installed `rippled` from the `yum` r To update manually, complete the following steps: -1. If you are upgrading to `rippled` 1.7.0 from an earlier version, re-add the repository to get Ripple's updated GPG key. Otherwise, skip this step: +1. If you are upgrading to `rippled` 1.7.0 from an earlier version, re-add the repository to get Ripple's updated GPG key. Otherwise, skip this step: $ cat << REPOFILE | sudo tee /etc/yum.repos.d/ripple.repo [ripple-stable] diff --git a/content/tutorials/manage-the-rippled-server/troubleshooting/understanding-log-messages.md b/content/tutorials/manage-the-rippled-server/troubleshooting/understanding-log-messages.md index 61aa5b9e1f..f295ddbb06 100644 --- a/content/tutorials/manage-the-rippled-server/troubleshooting/understanding-log-messages.md +++ b/content/tutorials/manage-the-rippled-server/troubleshooting/understanding-log-messages.md @@ -298,6 +298,7 @@ Validations:WRN Unable to determine hash of ancestor seq=3 from ledger hash=00B1 ## [veto_amendments] section in config file ignored + Log messages such as the following occur when your `rippled.cfg` file contains a legacy `[veto_amendments]` stanza. The first time the server starts on version 1.7.0 or higher, it reads the stanza to set amendment votes; on later restarts, it ignores the `[amendments]` and `[veto_amendments]` stanzas and prints this message instead. diff --git a/content/tutorials/production-readiness/set-up-secure-signing.md b/content/tutorials/production-readiness/set-up-secure-signing.md index af1d994513..78443e9e08 100644 --- a/content/tutorials/production-readiness/set-up-secure-signing.md +++ b/content/tutorials/production-readiness/set-up-secure-signing.md @@ -148,7 +148,7 @@ To use this configuration, follow the steps for [running `rippled` on a private - [sign method][] - [submit method][] - [RippleAPI Reference](rippleapi-reference.html) - - [xrpl-py Reference](https://xrpl-py.readthedocs.io/en/latest/index.html) + - [`xrpl-py` Reference](https://xrpl-py.readthedocs.io/en/latest/index.html) diff --git a/tool/spelling.txt b/tool/spelling.txt index 5a9c4483e6..fde31322cf 100644 --- a/tool/spelling.txt +++ b/tool/spelling.txt @@ -1,3 +1,4 @@ +# Data Types hash128 hash160 hash256 @@ -8,64 +9,157 @@ uint32 uint64 uint8 vector256 - -512half -account_channels -account_currencies -account_info -account_lines -account_objects -account_offers -account_one -account_tx -account_zero -accountdelete accountid -accountroot -accountset + +# General purpose words +512half +account_one +account_zero altnet altnets autobridging base58 base58check base64 -book_offers -can_delete -channel_authorize -channel_verify -checkcancel -checkcash -checkcreate +blockchains cmake -consensus_info cors -crawl_shards +counterparty +counterparties crypto -cryptoconditions -cryptoconditionssuite -deletableaccounts -deposit_authorized -depositauth -depositpreauth demurrage demurraging +deserialization devnet -directorynode -download_shard ecdsa ecmascript ed25519 eddsa +etl +fincen +gravatar +grpc +hmac +interledger +interoperability +kyc +lz4 +mainnet +micropayments +middleware +multisigning +noripple +nudb +p2p +pathfinding +pathset +postgresql +preauthorizations +readme +ripemd160 +rippleapi +rocksdb +rtxp +secp256k1 +semver +shor +SSDs +SSL +statsd +testnet +TLS +unl +unls +v0 +v1 +v2 +v10 +validators + +# rippled API methods +account_channels +account_currencies +account_info +account_lines +account_objects +account_offers +account_tx +book_offers +can_delete +channel_authorize +channel_verify +consensus_info +crawl_shards +deposit_authorized +download_shard +fetch_info +gateway_balances +get_counts +ledger_accept +ledger_cleaner +ledger_closed +ledger_current +ledger_data +ledger_entry +ledger_request +log_level +logrotate +noripple_check +path_find +peer_reservations_add +peer_reservations_del +peer_reservations_list +ripple_path_find +server_info +server_state +sign_for +submit_multisigned +transaction_entry +tx_history +validation_create +validation_seed +validator_info +validator_list_sites +wallet_propose + +# XRP Ledger transaction types +accountdelete +accountset +checkcancel +checkcash +checkcreate enableamendment -enforceinvariants escrowcancel escrowcreate escrowfinish -etl -feeescalation +offercancel +offercreate +paymentchannelclaim +paymentchannelcreate +paymentchannelfund +setfee +setregularkey +signerlistset +TicketCreate +trustset +UNLModify + +# XRP Ledger data objects +accountroot +directorynode feesettings -fetch_info -fincen +ledgerhashes +paychannel +ripplestate +signerlist + +# XRP Ledger amendment names +cryptoconditions +cryptoconditionssuite +deletableaccounts +depositauth +depositpreauth +enforceinvariants fix1201 fix1368 fix1373 @@ -84,92 +178,35 @@ fixcheckthreading fixmasterkeyasregularkey fixpaychanrecipientownerdir fixqualityupperbound +fixrmsmallincreasedqoffers +fixstamountcanonicalize fixtakerdryofferremoval flowcross +flowsortstrands flowv2 -gateway_balances -get_counts -gravatar -grpc +feeescalation hardenedvalidations -hmac -interledger -kyc -ledger_accept -ledger_cleaner -ledger_closed -ledger_current -ledger_data -ledger_entry -ledger_request -ledgerhashes -log_level -logrotate -lz4 -mainnet -micropayments multisign -multisigning multisignreserve negativeunl -noripple -noripple_check -nudb ownerpaysfee -path_find -pathfinding -pathset paychan -paychannel -paymentchannelclaim -paymentchannelcreate -paymentchannelfund -peer_reservations_add -peer_reservations_del -peer_reservations_list -preauthorizations -offercancel -offercreate requirefullycanonicalsig -ripemd160 -ripple_path_find -rippleapi -ripplestate -rocksdb -rtxp -secp256k1 -semver -server_info -server_state -setfee -setregularkey shamapv2 -shor sorteddirectories -sign_for -signerlist -signerlistset -statsd -submit_multisigned suspay -testnet +ticketbatch ticksize -transaction_entry -trustset trustsetauth -tx_history -unl -UNLModify -unls -wallet_propose -v0 -validation_create -validation_seed -validator_info -validator_list_sites -xpring -xrpchat +# Names of people, orgs, etc. +bithomp britto macbrough +RippleX +xpring +xrpcharts +xrpchat xrpscan +xrpl4j +XRPLF