From 11d73c4a72a9b08d70a1529e95de75b48620f46b Mon Sep 17 00:00:00 2001 From: JST5000 Date: Tue, 21 Nov 2023 15:38:58 +0000 Subject: [PATCH] deploy: b547db768d34d93d5a217633fd4a7f3177b37b26 --- .../build-a-desktop-wallet-in-javascript.html | 4 +- .../build-a-desktop-wallet-in-python.html | 6 +- pr-preview/jm-faucets/code-samples.html | 12 +- ...nect-your-rippled-to-the-xrp-test-net.html | 2 +- .../create-an-automated-market-maker.html | 2 +- pr-preview/jm-faucets/dev-tools.html | 2 +- pr-preview/jm-faucets/docs.html | 6 +- .../jm-faucets/get-started-using-java.html | 2 +- .../get-started-using-javascript.html | 2 +- .../jm-faucets/get-started-using-python.html | 8 +- .../build-a-desktop-wallet-in-javascript.html | 4 +- .../ja/build-a-desktop-wallet-in-python.html | 6 +- pr-preview/jm-faucets/ja/code-samples.html | 12 +- ...nect-your-rippled-to-the-xrp-test-net.html | 6 +- .../ja/create-an-automated-market-maker.html | 2 +- pr-preview/jm-faucets/ja/dev-tools.html | 2 +- pr-preview/jm-faucets/ja/docs.html | 6 +- pr-preview/jm-faucets/ja/escrow.html | 2 +- .../jm-faucets/ja/get-started-using-java.html | 2 +- .../ja/get-started-using-javascript.html | 2 +- .../ja/get-started-using-python.html | 8 +- ...itor-incoming-payments-with-websocket.html | 2 +- .../jm-faucets/ja/offline-account-setup.html | 2 +- .../jm-faucets/ja/parallel-networks.html | 4 +- .../jm-faucets/ja/use-payment-channels.html | 2 +- .../jm-faucets/offline-account-setup.html | 2 +- pr-preview/jm-faucets/parallel-networks.html | 2 +- pr-preview/jm-faucets/style_report.txt | 328 +++++++++--------- .../jm-faucets/use-payment-channels.html | 2 +- 29 files changed, 221 insertions(+), 221 deletions(-) diff --git a/pr-preview/jm-faucets/build-a-desktop-wallet-in-javascript.html b/pr-preview/jm-faucets/build-a-desktop-wallet-in-javascript.html index ccb5b2fc1be..42fb87f83ee 100644 --- a/pr-preview/jm-faucets/build-a-desktop-wallet-in-javascript.html +++ b/pr-preview/jm-faucets/build-a-desktop-wallet-in-javascript.html @@ -915,7 +915,7 @@

3. Display an Account

you can get one from the faucet. Then you can paste that address into the Transaction Sender to send XRP transactions that your app can see.

+

If you need a Testnet address, you can get one from the faucet. Then you can paste that address into the Transaction Sender to send XRP transactions that your app can see.

On, startup, the application should display a simple dialog prompting the user for an XRPL account address. After entering the address the application should display some basic information about that account and about the ledger.

To run the reference application found in content/_code-samples/build-a-desktop-wallet/desktop-js for this step, run:

npm run account
@@ -1456,7 +1456,7 @@ 
5. Saving the Private Keys wi
 
npm run start
 

 
On first run, It should first prompt you for an account seed and then for a password.

-
You can generate a test account's seed via the testnet faucet here .

+
You can generate a test account's seed via the testnet faucet here .

 
After you have created a wallet this way, you should close the application and start it up a second time: On second run it should prompt you for the password, and you should see the same result as in the last step.

 
To run the reference application found in content/_code-samples/build-a-desktop-wallet/desktop-js for this step, run:

 
npm run password
diff --git a/pr-preview/jm-faucets/build-a-desktop-wallet-in-python.html b/pr-preview/jm-faucets/build-a-desktop-wallet-in-python.html
index 1c919a8889b..a86dfa5caf6 100644
--- a/pr-preview/jm-faucets/build-a-desktop-wallet-in-python.html
+++ b/pr-preview/jm-faucets/build-a-desktop-wallet-in-python.html
@@ -801,7 +801,7 @@ 
3. Display an Account
Testnet Faucet and Get Testnet credentials. Save the address and secret key somewhere, and try your wallet app with either one. Then, to see balance changes, go to the Transaction Sender and paste your address into the Destination Address field. Click Initialize and try out some of the transaction types there, and see if the balance displayed by your wallet app updates as you expect.

+
To test your wallet app with your own test account, first go to the Testnet Faucet and Get Testnet credentials. Save the address and secret key somewhere, and try your wallet app with either one. Then, to see balance changes, go to the Transaction Sender and paste your address into the Destination Address field. Click Initialize and try out some of the transaction types there, and see if the balance displayed by your wallet app updates as you expect.

 
4. Show Account's Transactions

 
Full code for this step: 4_tx_history.py 

 
At this point, your wallet shows the account's balance getting updated, but doesn't show you anything about the actual transactions that caused the updates. So, the next step is to display the account's transaction history (and keep it updated).

@@ -974,7 +974,7 @@ 
4. Show Account's Transactionsnotif.SetFlags(wx.ICON_INFORMATION)
         notif.Show()
-

As before, you can test your wallet app with your own test account if you use the Testnet Faucet and the Transaction Sender. On the Faucet page, select Get Testnet credentials (or use the same credentials from before). Input either the address or secret when you open your wallet app. On the Transaction Sender page, paste your address into the Destination Address field, click Initialize, then click various transaction buttons to see how your wallet displays the results.

+

As before, you can test your wallet app with your own test account if you use the Testnet Faucet and the Transaction Sender. On the Faucet page, select Get Testnet credentials (or use the same credentials from before). Input either the address or secret when you open your wallet app. On the Transaction Sender page, paste your address into the Destination Address field, click Initialize, then click various transaction buttons to see how your wallet displays the results.

5. Send XRP

Full code for this step: 5_send_xrp.py

Until now, you've made the app able to view data from the ledger, and it's capable of showing the transactions an account has received. Now it's finally time to make the app capable of sending transactions. For now, you can stick to sending direct XRP payments because there are more complexities involved in sending issued tokens.

@@ -1205,7 +1205,7 @@

5. Send XRP.

+

Open your wallet app and provide a Secret (seed) value from an already-funded address, such as one you got from the Testnet Faucet.

  • Send at least the base reserve (currently 10 XRP) to the brand-new classic address you generated in the Python interpreter.

    diff --git a/pr-preview/jm-faucets/code-samples.html b/pr-preview/jm-faucets/code-samples.html index f6cd7052a1a..20e4246c6e9 100644 --- a/pr-preview/jm-faucets/code-samples.html +++ b/pr-preview/jm-faucets/code-samples.html @@ -3439,21 +3439,21 @@
    Help the XRPL community by submitting your
    own cod -
    - - -
    +
    + + +
    - - + +
    diff --git a/pr-preview/jm-faucets/connect-your-rippled-to-the-xrp-test-net.html b/pr-preview/jm-faucets/connect-your-rippled-to-the-xrp-test-net.html index 6a1364cd0be..c88c007795c 100644 --- a/pr-preview/jm-faucets/connect-your-rippled-to-the-xrp-test-net.html +++ b/pr-preview/jm-faucets/connect-your-rippled-to-the-xrp-test-net.html @@ -461,7 +461,7 @@

    5. Verify that your server syncs.See Also

    @@ -355,10 +355,10 @@

    Connect to the production XRP Ledg

    2. Get account

    To store value and execute transactions on the XRP Ledger, you need an account: a set of keys and an address that's been funded with enough XRP to meet the account reserve. The address is the identifier of your account and you use the private key to sign transactions that you submit to the XRP Ledger.

    -

    For testing and development purposes, you can use the XRP Faucets to generate keys and fund the account on the Testnet or Devnet. For production purposes, you should take care to store your keys and set up a secure signing method. Another difference in production is that XRP has real worth, so you can't get it for free from a faucet.

    +

    For testing and development purposes, you can use the XRP Faucets to generate keys and fund the account on the Testnet or Devnet. For production purposes, you should take care to store your keys and set up a secure signing method. Another difference in production is that XRP has real worth, so you can't get it for free from a faucet.

    To create and fund an account on the Testnet, xrpl-py provides the generate_faucet_wallet method:

    # Create a wallet using the testnet faucet:
-# https://xrpl.org/xrp-testnet-faucet.html
+# https://xrpl.org//dev-tools/xrp-faucets
 from xrpl.wallet import generate_faucet_wallet
 test_wallet = generate_faucet_wallet(client, debug=True)
    @@ -431,7 +431,7 @@

    4. Putting it all together# Create a wallet using the testnet faucet: -# https://xrpl.org/xrp-testnet-faucet.html +# https://xrpl.org//dev-tools/xrp-faucets from xrpl.wallet import generate_faucet_wallet test_wallet = generate_faucet_wallet(client, debug=True) diff --git a/pr-preview/jm-faucets/ja/build-a-desktop-wallet-in-javascript.html b/pr-preview/jm-faucets/ja/build-a-desktop-wallet-in-javascript.html index 4893e69e8ae..216089ca7a4 100644 --- a/pr-preview/jm-faucets/ja/build-a-desktop-wallet-in-javascript.html +++ b/pr-preview/jm-faucets/ja/build-a-desktop-wallet-in-javascript.html @@ -919,7 +919,7 @@

    3. Display an Account

    you can get one from the faucet. Then you can paste that address into the Transaction Sender to send XRP transactions that your app can see.

    +

    If you need a Testnet address, you can get one from the faucet. Then you can paste that address into the Transaction Sender to send XRP transactions that your app can see.

    On, startup, the application should display a simple dialog prompting the user for an XRPL account address. After entering the address the application should display some basic information about that account and about the ledger.

    To run the reference application found in content/_code-samples/build-a-desktop-wallet/desktop-js for this step, run:

    npm run account
@@ -1460,7 +1460,7 @@ 
    5. Saving the Private Keys wi
 
    npm run start
 
    
 
    On first run, It should first prompt you for an account seed and then for a password.
    
-
    You can generate a test account's seed via the testnet faucet here .
    
+
    You can generate a test account's seed via the testnet faucet here .
    
 
    After you have created a wallet this way, you should close the application and start it up a second time: On second run it should prompt you for the password, and you should see the same result as in the last step.
    
 
    To run the reference application found in content/_code-samples/build-a-desktop-wallet/desktop-js for this step, run:
    
 
    npm run password
diff --git a/pr-preview/jm-faucets/ja/build-a-desktop-wallet-in-python.html b/pr-preview/jm-faucets/ja/build-a-desktop-wallet-in-python.html
index f684552f367..ee147f5488d 100644
--- a/pr-preview/jm-faucets/ja/build-a-desktop-wallet-in-python.html
+++ b/pr-preview/jm-faucets/ja/build-a-desktop-wallet-in-python.html
@@ -805,7 +805,7 @@ 
    3. Display an Account
    Testnet Faucet and Get Testnet credentials. Save the address and secret key somewhere, and try your wallet app with either one. Then, to see balance changes, go to the Transaction Sender and paste your address into the Destination Address field. Click Initialize and try out some of the transaction types there, and see if the balance displayed by your wallet app updates as you expect.
    
+
    To test your wallet app with your own test account, first go to the Testnet Faucet and Get Testnet credentials. Save the address and secret key somewhere, and try your wallet app with either one. Then, to see balance changes, go to the Transaction Sender and paste your address into the Destination Address field. Click Initialize and try out some of the transaction types there, and see if the balance displayed by your wallet app updates as you expect.
    
 
    4. Show Account's Transactions
    
 
    Full code for this step: 4_tx_history.py 
    
 
    At this point, your wallet shows the account's balance getting updated, but doesn't show you anything about the actual transactions that caused the updates. So, the next step is to display the account's transaction history (and keep it updated).
    
@@ -978,7 +978,7 @@ 
    4. Show Account's Transactionsnotif.SetFlags(wx.ICON_INFORMATION)
         notif.Show()
    -

    As before, you can test your wallet app with your own test account if you use the Testnet Faucet and the Transaction Sender. On the Faucet page, select Get Testnet credentials (or use the same credentials from before). Input either the address or secret when you open your wallet app. On the Transaction Sender page, paste your address into the Destination Address field, click Initialize, then click various transaction buttons to see how your wallet displays the results.

    +

    As before, you can test your wallet app with your own test account if you use the Testnet Faucet and the Transaction Sender. On the Faucet page, select Get Testnet credentials (or use the same credentials from before). Input either the address or secret when you open your wallet app. On the Transaction Sender page, paste your address into the Destination Address field, click Initialize, then click various transaction buttons to see how your wallet displays the results.

    5. Send XRP

    Full code for this step: 5_send_xrp.py

    Until now, you've made the app able to view data from the ledger, and it's capable of showing the transactions an account has received. Now it's finally time to make the app capable of sending transactions. For now, you can stick to sending direct XRP payments because there are more complexities involved in sending issued tokens.

    @@ -1209,7 +1209,7 @@

    5. Send XRP.

    +

    Open your wallet app and provide a Secret (seed) value from an already-funded address, such as one you got from the Testnet Faucet.

  • Send at least the base reserve (currently 10 XRP) to the brand-new classic address you generated in the Python interpreter.

    diff --git a/pr-preview/jm-faucets/ja/code-samples.html b/pr-preview/jm-faucets/ja/code-samples.html index 8d9d4315de4..86a50164276 100644 --- a/pr-preview/jm-faucets/ja/code-samples.html +++ b/pr-preview/jm-faucets/ja/code-samples.html @@ -3435,21 +3435,21 @@
    コードサンプルを投稿して、XRPLコミュ -
    - - -
    +
    + + +
    - - + +
    diff --git a/pr-preview/jm-faucets/ja/connect-your-rippled-to-the-xrp-test-net.html b/pr-preview/jm-faucets/ja/connect-your-rippled-to-the-xrp-test-net.html index ce1cf715d1f..7f6c234b326 100644 --- a/pr-preview/jm-faucets/ja/connect-your-rippled-to-the-xrp-test-net.html +++ b/pr-preview/jm-faucets/ja/connect-your-rippled-to-the-xrp-test-net.html @@ -312,11 +312,11 @@

    XRPL Altnetへのrippledの接続
  • rippled.cfgファイルで以下の手順に従います。
    • -

    a. Testnetに接続するには、以下のセクションのコメントを解除し、次のように追加します。

    +

    a. Testnetに接続するには、以下のセクションのコメントを解除し、次のように追加します。

        [ips]
     s.altnet.rippletest.net 51235
    -

    b. Devnetに接続するには、以下のセクションのコメントを解除し、次のように追加します。

    +

    b. Devnetに接続するには、以下のセクションのコメントを解除し、次のように追加します。

        [ips]
     s.devnet.rippletest.net 51235
    @@ -382,7 +382,7 @@

    XRPL Altnetへのrippledの接続関連項目

    @@ -356,10 +356,10 @@

    Connect to the production XRP Ledg

    2. Get account

    To store value and execute transactions on the XRP Ledger, you need an account: a set of keys and an address that's been funded with enough XRP to meet the account reserve. The address is the identifier of your account and you use the private key to sign transactions that you submit to the XRP Ledger.

    -

    For testing and development purposes, you can use the XRP Faucets to generate keys and fund the account on the Testnet or Devnet. For production purposes, you should take care to store your keys and set up a secure signing method. Another difference in production is that XRP has real worth, so you can't get it for free from a faucet.

    +

    For testing and development purposes, you can use the XRP Faucets to generate keys and fund the account on the Testnet or Devnet. For production purposes, you should take care to store your keys and set up a secure signing method. Another difference in production is that XRP has real worth, so you can't get it for free from a faucet.

    To create and fund an account on the Testnet, xrpl-py provides the generate_faucet_wallet method:

    # Create a wallet using the testnet faucet:
-# https://xrpl.org/xrp-testnet-faucet.html
+# https://xrpl.org//dev-tools/xrp-faucets
 from xrpl.wallet import generate_faucet_wallet
 test_wallet = generate_faucet_wallet(client, debug=True)
    @@ -432,7 +432,7 @@

    4. Putting it all together# Create a wallet using the testnet faucet: -# https://xrpl.org/xrp-testnet-faucet.html +# https://xrpl.org//dev-tools/xrp-faucets from xrpl.wallet import generate_faucet_wallet test_wallet = generate_faucet_wallet(client, debug=True) diff --git a/pr-preview/jm-faucets/ja/monitor-incoming-payments-with-websocket.html b/pr-preview/jm-faucets/ja/monitor-incoming-payments-with-websocket.html index 660a8b54e11..f8550a02d1c 100644 --- a/pr-preview/jm-faucets/ja/monitor-incoming-payments-with-websocket.html +++ b/pr-preview/jm-faucets/ja/monitor-incoming-payments-with-websocket.html @@ -348,7 +348,7 @@

    1. XRP Ledgerへの接続

    Test Net上にあるRippleの公開APIサーバーの1つに対して、安全な接続（wss://）を開きます。代わりにデフォルトの構成を使用してローカルで運用しているrippledサーバーに接続するには、最初の行に以下を使用して、ローカルのポート6006で 安全ではない 接続（ws://）を開きます。

    +

    上記の例では、Test Net上にあるRippleの公開APIサーバーの1つに対して、安全な接続（wss://）を開きます。代わりにデフォルトの構成を使用してローカルで運用しているrippledサーバーに接続するには、最初の行に以下を使用して、ローカルのポート6006で 安全ではない 接続（ws://）を開きます。

    const socket = new WebSocket('ws://localhost:6006')

    ヒント: デフォルトでは、ローカルrippledサーバーに接続することで、インターネット上の公開サーバーに接続する際に使用できるパブリックメソッド以外に、すべての管理メソッドと、server_infoなどの一部の応答に含まれる管理者専用データを利用できます。

    diff --git a/pr-preview/jm-faucets/ja/offline-account-setup.html b/pr-preview/jm-faucets/ja/offline-account-setup.html index 44cf9be9f80..a6ed9e58702 100644 --- a/pr-preview/jm-faucets/ja/offline-account-setup.html +++ b/pr-preview/jm-faucets/ja/offline-account-setup.html @@ -366,7 +366,7 @@

    2.暗号鍵の生成

    オンラインマシンから、ステップ1でメモしたアカウントアドレス に十分なXRPを送金します。詳細は、アカウントの作成を参照してください。

    -

    ヒント: テストの目的で、Testnet Faucetを使用して、テスト用のXRPが入った新しいアカウントを取得できます。そのアカウントを使用して、オフラインで生成されたアドレスに資金を供給します。

    +

    ヒント: テストの目的で、Testnet Faucetを使用して、テスト用のXRPが入った新しいアカウントを取得できます。そのアカウントを使用して、オフラインで生成されたアドレスに資金を供給します。

    4.アカウントの詳細の確認

    前のステップからのトランザクションがコンセンサスにより検証されたら、アカウントが作成されたことになります。オンラインマシンから、account_infoメソッドを使用して、アカウントのステータスを確認します。応答に"validated": trueが含まれていることを確認し、この結果が最終的なものであることを確認します。

    結果のaccount_dataのSequenceフィールドにある、アカウントのシーケンス番号をメモします。この後のステップでアカウントのトランザクションに署名するために、このシーケンス番号を把握しておく必要があります。

    diff --git a/pr-preview/jm-faucets/ja/parallel-networks.html b/pr-preview/jm-faucets/ja/parallel-networks.html index d47a9f69efc..17a1220d142 100644 --- a/pr-preview/jm-faucets/ja/parallel-networks.html +++ b/pr-preview/jm-faucets/ja/parallel-networks.html @@ -329,7 +329,7 @@

    並列ネットワーク

    無償で提供されています。テスト用のXRPは実際には価値を持たず、ネットワークがリセットされると失われます。

    +

    テスト用XRPは、XRP Ledgerの実験やアプリケーションの開発、統合に興味のある人々に無償で提供されています。テスト用のXRPは実際には価値を持たず、ネットワークがリセットされると失われます。

    注意: XRP Ledgerメインネットとは異なり、テストネットワークは通常「中央集権型」であり、これらのネットワークの安定性や可用性については保証されていません。これらのネットワークは、サーバ構成、ネットワークトポロジー、ネットワークパフォーマンスのさまざまな特性をテストする目的でこれまで使用され、またこれからも同様に使用されます。

    並列ネットワークとコンセンサス

    使用するネットワークを定義するrippledの設定はありません。その代わり、信頼するバリデータのコンセンサスに基づいてどのレジャーを正しいレジャーとして受け入れるかを把握します。rippledインスタンスからなる異なるコンセンサスグループが、同じグループの他のメンバーだけを信頼する場合、各グループは引き続き並列ネットワークとして機能します。悪意のあるコンピューターや不適切に動作するコンピューターが両方のネットワークに接続している場合でも、各ネットワークのメンバーが、定数設定を超えて別のネットワークのメンバーを信頼するように設定されていない限り、コンセンサスプロセスに混乱は生じません。

    @@ -337,7 +337,7 @@

    並列ネットワーク

    関連項目

    • ツール:
      • -
    • XRP Testnet Faucet
      • +
    • XRP Testnet Faucet
    • コンセプト:
    • コンセンサスについて
    • Amendment
      • diff --git a/pr-preview/jm-faucets/ja/use-payment-channels.html b/pr-preview/jm-faucets/ja/use-payment-channels.html index b94e1905dd8..f0d95f1963c 100644 --- a/pr-preview/jm-faucets/ja/use-payment-channels.html +++ b/pr-preview/jm-faucets/ja/use-payment-channels.html @@ -345,7 +345,7 @@

      サンプルの値

      XRP Ledger Testnetのアドレスを使用できます。XRP Ledger Test Netを使用する場合、http://localhost:5005/ではなくhttps://api.altnet.rippletest.net:51234に接続することで、Test NetサーバーのJSON-RPC APIを使用できます。

      +

      実際のXRPを送金せずにテストを実施するには、Test Net XRPを保有するXRP Ledger Testnetのアドレスを使用できます。XRP Ledger Test Netを使用する場合、http://localhost:5005/ではなくhttps://api.altnet.rippletest.net:51234に接続することで、Test NetサーバーのJSON-RPC APIを使用できます。

      Payment Channelに使用できるXRPの額に制限はありません。このチュートリアルで使用されているサンプルの値では、Payment Channelで100 XRP（100000000 drop）が少なくとも1日間は確保されます。

      フローチャート

      次の図は、Payment Channelのライフサイクルの概要を示します。

      diff --git a/pr-preview/jm-faucets/offline-account-setup.html b/pr-preview/jm-faucets/offline-account-setup.html index d3f9898518c..7d2b8c07512 100644 --- a/pr-preview/jm-faucets/offline-account-setup.html +++ b/pr-preview/jm-faucets/offline-account-setup.html @@ -368,7 +368,7 @@

      2. Generate cryptographic keys

      3. Fund the new address

      From an online machine, send enough XRP to the account address you noted in step 1. For more information, see Creating Accounts.

      -

      Tip: For testing purposes, you can use the Testnet Faucet to get a new account with Test XRP, then use that account to fund the address you generated offline.

      +

      Tip: For testing purposes, you can use the Testnet Faucet to get a new account with Test XRP, then use that account to fund the address you generated offline.

      4. Confirm account details

      When the transaction from the previous step is validated by consensus, your account has been created. From the online machine, you can confirm the status of the account with the account_info method. Make sure the response contains "validated": true to confirm that this result is final.

      Take note of the sequence number of the account, in the Sequence field of the result's account_data. You need to know the sequence number to sign transactions from the account in future steps.

      diff --git a/pr-preview/jm-faucets/parallel-networks.html b/pr-preview/jm-faucets/parallel-networks.html index 05799647f2a..dcda4be753e 100644 --- a/pr-preview/jm-faucets/parallel-networks.html +++ b/pr-preview/jm-faucets/parallel-networks.html @@ -333,7 +333,7 @@

      Parallel Networks to parties interested in experimenting with the XRP Ledger and developing applications and integrations. Test XRP does not have real-world value and is lost when the network is reset.

      +

      Each altnet has its own separate supply of test XRP, which is given away for free to parties interested in experimenting with the XRP Ledger and developing applications and integrations. Test XRP does not have real-world value and is lost when the network is reset.

      Caution: Unlike the XRP Ledger Mainnet, test networks are usually centralized and there are no guarantees about the stability and availability of these networks. They have been and continue to be used to test various properties of server configuration, network topology, and network performance.

      Parallel Networks and Consensus

      The main factor in determining which network a server follows is its configured UNL—the list of validators it trusts not to collude. Each server uses its configured UNL to know which ledger to accept as the truth. When different consensus groups of rippled instances only trust other members of the same group, each group continues as a parallel network. Even if malicious or misbehaving computers connect to both networks, the consensus process avoids confusion as long as the members of each network are not configured to trust members of another network in excess of their quorum settings.

      diff --git a/pr-preview/jm-faucets/style_report.txt b/pr-preview/jm-faucets/style_report.txt index 8fb26fca827..63f25fe4ba6 100644 --- a/pr-preview/jm-faucets/style_report.txt +++ b/pr-preview/jm-faucets/style_report.txt @@ -3,9 +3,9 @@ Spell Checker ------------- Found 326 possible spelling errors: Unknown Words: - gifs: gies, gifts, gins - kuressaare: + gifs: gies, gif, kifs ringtee: + kuressaare: lõõtsa: Unknown Words: @@ -40,16 +40,16 @@ Found 326 possible spelling errors: tokentaxon: Unknown Words: - investopedia: arbitraging: arbitrating + investopedia: unprecented: unprevented, unpresented - clob: blob, cloe, cloy + clob: clof, clog, clou 30d: 3rd, 3d, 3-d frontrunning: Unknown Words: 0b0: - v3: vd, t3, vv + v3: vt, v, c3 Unknown Words: 11d: @@ -59,7 +59,7 @@ Found 326 possible spelling errors: nftokencounttracking: Unknown Words: - ooffers: coffers, doffers, goffers + ooffers: offers, doffers, coffers Unknown Words: arweave: @@ -80,47 +80,47 @@ Found 326 possible spelling errors: nftokentaxon: Unknown Words: - blackhole: blockhole, black-hole + blackhole: black-hole, blockhole Unknown Words: nft_history: - slas: silas, ssas, slam + slas: sas, slap, slar Unknown Words: - rsa2lpzuawewsbqxkiju3yqtmzw13paadw: rp6abvbtbjoce8zdjkt6snvxtzsymbcc9s: + rsa2lpzuawewsbqxkiju3yqtmzw13paadw: Unknown Words: stablefoo: - unbalances: unbalance, unbalanced + unbalances: unbalanced, unbalance machowski: ammdelete: Unknown Words: + v3: vt, v, c3 30d: 3rd, 3d, 3-d - v3: vd, t3, vv Unknown Words: - mod1: mody, mod, mods + mod1: mody, mod., mods testnet_url: rippletest: get_account_info: send_xrp: - lesson1: lesson, lessons - tkinter: twinter, tinter + lesson1: lessons, lesson + tkinter: tinter, twinter getstandbyaccount: get_standby_account_info: standby_send_xrp: Unknown Words: - mod2: mody, mod, mods + mod2: mody, mod., mods send_currency: get_balance: configure_account: - lesson2: lesson, lessons + lesson2: lessons, lesson Unknown Words: - mod8: mody, mod, mods + mod8: mody, mod., mods add_seconds: numofseconds: create_time_escrow: @@ -130,182 +130,182 @@ Found 326 possible spelling errors: cancel_time_escrows: get_transaction: accounttx: account_tx - lesson8: lesson, lessons + lesson8: lessons, lesson Unknown Words: - mod3: mody, mod, mods + mod3: mody, mod., mods minttoken: gettokens: burn_token: Unknown Words: - mod4: mody, mod, mods + mod4: mody, mod., mods offer___index: alloffers: - lesson4: lesson, lessons + lesson4: lessons, lesson Unknown Words: - sell___offer___index: - buy___offer___index: broker___fee: - lesson5: lesson, lessons - get_broker_account_info: - nsew: nsw, nse, nsem - btn_broker_sale: - btn_broker_get_account: + buy___offer___index: + sell___offer___index: + lesson5: lessons, lesson btn_broker_get_offers: - broker_cancel_offer: - frm_broker: - btn_broker_cancel_offer: btn_broker_get_account_info: - get_broker_account: broker_broker_sale: + broker_cancel_offer: + btn_broker_get_account: + btn_broker_sale: + nsew: nsem, unsew, nsel + get_broker_account_info: broker_get_offers: - frm_form: + get_broker_account: + btn_broker_cancel_offer: + frm_broker: borderwidth: - ent_standby_account: - ent_standby_uri: - checkbutton: + frm_form: + ent_standby_destination: ent_standby_balance: - lbl_standby_taxon: - ent_standby_expiration: - onvalue: nonvalue, unvalue - lbl_standby_destination: - cb_standby_allow_rippling: - lbl_standy_seed: - lbl_standby_account: + ent_standby_uri: + ent_standby_owner: + lbl_standby_results: + lbl_standby_transfer_fee: + ent_standby_currency: text_standby_results: - lbl_standy_amount: - ent_standby_nft_offer_index: - ent_standby_taxon: - lbl_standby_balance: - ent_standby_flags: lbl_standby_owner: - lbl_standby_nft_offer_index: - offvalue: + checkbutton: + ent_standby_account: lbl_standby_nft_id: - lbl_standby_currency: - lbl_standby_transfer_fee: - ent_standby_amount: - ent_standby_transfer_fee: - ent_standby_destination: - ent_standby_seed: - ent_standby_currency: + ent_standby_expiration: lbl_standby_flags: - ent_standby_owner: + ent_standby_taxon: lbl_standby_expiration: - standbyrippling: + onvalue: nonvalue, unvalue ent_standby_nft_id: - lbl_standby_results: + ent_standby_seed: + ent_standby_flags: lbl_standby_uri: - ent_operational_currency: - lbl_operational_uri: - lbl_operational_amount: - lbl_operational_transfer_fee: - ent_operational_balance: - lbl_operational_seed: - lbl_operational_owner: - ent_operational_nft_id: - ent_operational_uri: - ent_operational_account: - cb_operational_allow_rippling: - lbl_operational_destination: + ent_standby_amount: + lbl_standby_taxon: + ent_standby_transfer_fee: + lbl_standy_amount: + lbl_standby_nft_offer_index: + standbyrippling: + lbl_standby_balance: + ent_standby_nft_offer_index: + lbl_standy_seed: + offvalue: + lbl_standby_account: + cb_standby_allow_rippling: + lbl_standby_currency: + lbl_standby_destination: ent_operational_seed: - ent_operational_destination: - operationalrippling: - ent_operational_taxon: - lbl_operational_nft_offer_index: + ent_operational_flags: + lbl_operational_transfer_fee: lbl_operational_nft_id: - lbl_operational_flags: - ent_operational_owner: + lbl_operational_expiration: + lbl_operational_amount: + lbl_operational_uri: ent_operational_expiration: - text_operational_results: + ent_operational_taxon: + lbl_operational_account: lbl_operational_results: - lbl_operational_currency: - ent_operational_flags: + ent_operational_balance: + ent_operational_nft_id: + ent_operational_currency: + lbl_operational_nft_offer_index: ent_operational_transfer_fee: + text_operational_results: + ent_operational_owner: ent_operational_nft_offer_index: - lbl_operational_balance: - lbl_operational_account: + lbl_operational_flags: lbl_operational_taxon: - lbl_operational_expiration: ent_operational_amount: - btn_get_standby_account_info: - standby_create_sell_offer: - standby_get_offers: + lbl_operational_destination: + ent_operational_destination: + lbl_operational_currency: + lbl_operational_seed: + ent_operational_account: + ent_operational_uri: + lbl_operational_balance: + cb_operational_allow_rippling: + lbl_operational_owner: + operationalrippling: + btn_standby_create_buy_offer: + standby_send_currency: btn_standby_burn_token: + btn_get_standby_account: + get_balances: get_standby_account_info: - standby_get_tokens: + btn_standby_cancel_offer: standby_send_xrp: - standby_cancel_offer: + standby_configure_account: + btn_standby_mint_token: get_standby_account: + standby_accept_buy_offer: + btn_standby_configure_account: + btn_standby_get_offers: + btn_standby_get_tokens: + btn_standby_accept_buy_offer: + standby_accept_sell_offer: + standby_create_trust_line: + standby_create_sell_offer: btn_standby_accept_sell_offer: - standby_burn_token: - get_balances: - standby_send_currency: - btn_standby_cancel_offer: - btn_standby_send_xrp: + standby_create_buy_offer: btn_standby_send_currency: - standby_create_trust_line: - btn_standby_create_trust_line: - btn_standby_get_tokens: + btn_get_standby_account_info: + standby_cancel_offer: standby_mint_token: + btn_standby_send_xrp: btn_standby_create_sell_offer: - btn_standby_mint_token: - standby_accept_buy_offer: - standby_create_buy_offer: - btn_standby_configure_account: - standby_configure_account: - standby_accept_sell_offer: - btn_standby_accept_buy_offer: - btn_get_standby_account: - btn_standby_create_buy_offer: - btn_standby_get_offers: - btn_op_cancel_offer: - operational_burn_token: - btn_op_configure_account: + btn_standby_create_trust_line: + standby_burn_token: + standby_get_tokens: + standby_get_offers: btn_op_get_offers: - btn_op_send_currency: - btn_get_op_account_info: - btn_op_get_balances: + get_operational_account_info: + operational_create_trust_line: + op_create_buy_offer: + operational_get_tokens: + btn_op_configure_account: + btn_get_operational_account: + btn_op_create_buy_offer: op_get_offers: + operational_configure_account: + btn_op_cancel_offer: + btn_op_get_balances: + btn_op_accept_sell_offer: + btn_op_burn_token: + op_cancel_offer: + btn_get_op_account_info: + op_accept_buy_offer: + get_operational_account: operational_send_xrp: btn_op_get_tokens: btn_op_create_sell_offer: + btn_op_send_currency: op_accept_sell_offer: - op_accept_buy_offer: - operational_create_trust_line: - btn_op_accept_buy_offer: - op_create_buy_offer: - operational_mint_token: - btn_get_operational_account: btn_op_mint_token: - op_cancel_offer: - operational_configure_account: + btn_op_send_xrp: op_create_sell_offer: - btn_op_accept_sell_offer: - btn_op_create_buy_offer: btn_op_create_trust_line: - get_operational_account_info: - operational_get_tokens: - get_operational_account: - btn_op_send_xrp: - btn_op_burn_token: + operational_mint_token: + operational_burn_token: + btn_op_accept_buy_offer: operational_send_currency: mainloop: Unknown Words: - mod6: mody, mod, mods + mod6: mody, mod., mods mint_other: - lesson6: lesson, lessons - lesson4: lesson, lessons + lesson6: lessons, lesson + lesson4: lessons, lesson Unknown Words: testnet_url: - lesson7: lesson, lessons + lesson7: lessons, lesson Unknown Words: - ripple8: ripplet, ripple, ripplex + ripple8: ripplet, rippled, ripplex numofseconds: offersequence: @@ -314,15 +314,15 @@ Found 326 possible spelling errors: ripplex9: ripplex Unknown Words: - preloader: reloader, preloaded + preloader: preloaded, reloader frontend: fronted websockets: websocket boostrap: bootstrap Unknown Words: fixnftokenremint: - nftokenoffers: nftokenoffer disallowincoming: + nftokenoffers: nftokenoffer Unknown Words: voteentry: @@ -335,11 +335,11 @@ Found 326 possible spelling errors: Unknown Words: networkid: networked - v3: vd, t3, vv + v3: vt, v, c3 Unknown Words: - nftokenoffers: nftokenoffer disallowincoming: + nftokenoffers: nftokenoffer nftokenminter: Unknown Words: @@ -352,8 +352,8 @@ Found 326 possible spelling errors: disallowincoming: Unknown Words: - nftokenoffers: nftokenoffer disallowincoming: + nftokenoffers: nftokenoffer Unknown Words: immediateofferkilled: @@ -371,7 +371,7 @@ Found 326 possible spelling errors: nftokenid: Unknown Words: - ctid: ccid, cid, ctd + ctid: cid, clid, cetid 37d: 3rd, 3d, 3-d Unknown Words: @@ -384,7 +384,7 @@ Found 326 possible spelling errors: trustlines: Unknown Words: - ctid: ccid, cid, ctd + ctid: cid, clid, cetid Unknown Words: xrpfees: @@ -396,66 +396,66 @@ Found 326 possible spelling errors: scalability: salability Unknown Words: - ext4: exta, ext., extg - zfs: afs, fs, vfs - xfs: afs, fs, vfs + ext4: extg, ext., ext filesystems: filesystem + xfs: x's, efs, bfs + zfs: efs, bfs, jfs Unknown Words: - depositpreauthamendment: - immediateofferkilled: - fixuniversalnumber: - disallowincoming: fixnonfungibletokensv1_2: + fixuniversalnumber: xrpfees: - fixreducedoffersv1: fixnftokenremint: - 38d: 3rd, 3d, 3-d + disallowincoming: + fixreducedoffersv1: + depositpreauthamendment: + immediateofferkilled: xchainbridge: + 38d: 3rd, 3d, 3-d ammdelete: nftokenoffers: nftokenoffer - asfdisallowincomingnftoffer: - asfdisallowincomingpaychan: asfdisallowincomingcheck: + asfdisallowincomingpaychan: asfdisallowincomingtrustline: - 1e: be, ke, ie + asfdisallowincomingnftoffer: + 1e: ue, te, we 30d: 3rd, 3d, 3-d Unknown Words: transactors: transactor Unknown Words: + umlet: amlet, unlet, umset + img: pmg, cmg, imt _img: - img: mig, ims, irg - _snippets: snippets _code: code - scss: scsa, sass, suss - umlet: amlet, umset, mulet + scss: suss, scts, sess + _snippets: snippets frontmatter: + h1: hz, ho, hm santilli: - h1: hr, ht, hz - websockets: websocket + trustline: + postgres: postures xrps: xrpl, xrp, rps camelcase: - trustline: + websockets: websocket orderbook: order-book - postgres: postures fronmatter: dropdowns: dropdown: Unknown Words: bcp47: - zh: ch, eh, ze + zh: nh, dh, ph hyperlinks: frontmatter: - utf: ltf, etf, uts + utf: utu, uts, wtf Unknown Words: subfolder: subfolders inlined: inline, inclined, unlined - umlet: amlet, umset, mulet - scss: scsa, sass, suss + umlet: amlet, unlet, umset + scss: suss, scts, sess Unknown Words: screenshots: screenshot diff --git a/pr-preview/jm-faucets/use-payment-channels.html b/pr-preview/jm-faucets/use-payment-channels.html index c2c7568149f..11460a88355 100644 --- a/pr-preview/jm-faucets/use-payment-channels.html +++ b/pr-preview/jm-faucets/use-payment-channels.html @@ -345,7 +345,7 @@

      Example Values

      XRP Ledger Testnet addresses with Testnet XRP. If you do use the Testnet, you can use the Testnet servers' JSON-RPC API by connecting to https://api.altnet.rippletest.net:51234 instead of http://localhost:5005/.

      +

      To test without transferring real XRP, you can use XRP Ledger Testnet addresses with Testnet XRP. If you do use the Testnet, you can use the Testnet servers' JSON-RPC API by connecting to https://api.altnet.rippletest.net:51234 instead of http://localhost:5005/.

      You can use any amount of XRP for the payment channels. The example values in this tutorial set aside 100 XRP (100000000 drops) in a payment channel for at least 1 day.

      Flow Diagram

      The following diagram summarizes the lifecycle of a payment channel: