mirror of
https://github.com/XRPLF/xrpl-dev-portal.git
synced 2025-11-29 08:05:49 +00:00
Fix some links in complex-pay-types tuts
This commit is contained in:
@@ -1,9 +1,13 @@
|
|||||||
# Install rippled
|
# Install rippled
|
||||||
|
|
||||||
For development, you can [compile `rippled` from source](https://wiki.ripple.com/Rippled_build_instructions).
|
|
||||||
|
|
||||||
Production `rippled` instances can [use Ripple's binary executable](#installation-on-centosred-hat-with-yum), available from the Ripple [yum](https://en.wikipedia.org/wiki/Yellowdog_Updater,_Modified) repository.
|
Production `rippled` instances can [use Ripple's binary executable](#installation-on-centosred-hat-with-yum), available from the Ripple [yum](https://en.wikipedia.org/wiki/Yellowdog_Updater,_Modified) repository.
|
||||||
|
|
||||||
|
For development, you can compile `rippled` from source:
|
||||||
|
|
||||||
|
- See [Build and Run `rippled` on Ubuntu](build-run-rippled-ubuntu.html) for Ubuntu Linux 16.04 and higher.
|
||||||
|
- For other platforms, see the [rippled repository](https://github.com/ripple/rippled/tree/develop/Builds) for instructions.
|
||||||
|
|
||||||
|
|
||||||
## Minimum System Requirements
|
## Minimum System Requirements
|
||||||
|
|
||||||
A `rippled` server should run comfortably on commodity hardware, to make it inexpensive to participate in the network. At present, we recommend the following mimimum requirements:
|
A `rippled` server should run comfortably on commodity hardware, to make it inexpensive to participate in the network. At present, we recommend the following mimimum requirements:
|
||||||
@@ -19,7 +23,8 @@ A `rippled` server should run comfortably on commodity hardware, to make it inex
|
|||||||
|
|
||||||
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.
|
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.
|
||||||
|
|
||||||
**Tip:** For recommendations beyond the minimum requirements, see [Capacity Planning](#capacity-planning).
|
**Tip:** For recommendations beyond the minimum requirements, see [Capacity Planning](capacity-planning.html).
|
||||||
|
|
||||||
|
|
||||||
## Installation on CentOS/Red Hat with yum
|
## Installation on CentOS/Red Hat with yum
|
||||||
|
|
||||||
@@ -78,6 +83,8 @@ This section assumes that you are using Ubuntu 15.04 or later.
|
|||||||
|
|
||||||
It can take several minutes for `rippled` to sync with the rest of the network, during which time it outputs warnings about missing ledgers. After that, you have a fully functional stock `rippled` server that you can use for local signing and API access to the XRP Ledger.
|
It can take several minutes for `rippled` to sync with the rest of the network, during which time it outputs warnings about missing ledgers. After that, you have a fully functional stock `rippled` server that you can use for local signing and API access to the XRP Ledger.
|
||||||
|
|
||||||
[rippled commands](reference-rippled.html#list-of-public-commands) can be run with:
|
You can use the [rippled commandline interface](get-started-with-the-rippled-api.html#commandline) as follows:
|
||||||
|
|
||||||
$ /opt/ripple/bin/rippled <command>
|
$ /opt/ripple/bin/rippled <METHOD>
|
||||||
|
|
||||||
|
For a full list of available methods, see the [rippled API reference](rippled-api.html).
|
||||||
|
|||||||
@@ -1,6 +1,6 @@
|
|||||||
# Cash a Check for a Flexible Amount
|
# Cash a Check for a Flexible Amount
|
||||||
|
|
||||||
_Requires the [Checks Amendment](reference-amendments.html#checks)._
|
_Requires the [Checks Amendment](known-amendments.html#checks)._
|
||||||
|
|
||||||
As long as the Check is in the ledger and not expired, the specified recipient can cash it to receive a flexible amount by sending a [CheckCash transaction][] with a `DeliverMin` field. When cashing a Check in this way, the receiver gets as much as is possible to deliver, debiting the Check's sender for the Check's full `SendMax` amount or as much as is available. Cashing fails if it doesn't deliver at least the `DeliverMin` amount to the Check's recipient.
|
As long as the Check is in the ledger and not expired, the specified recipient can cash it to receive a flexible amount by sending a [CheckCash transaction][] with a `DeliverMin` field. When cashing a Check in this way, the receiver gets as much as is possible to deliver, debiting the Check's sender for the Check's full `SendMax` amount or as much as is available. Cashing fails if it doesn't deliver at least the `DeliverMin` amount to the Check's recipient.
|
||||||
|
|
||||||
|
|||||||
@@ -1,6 +1,6 @@
|
|||||||
# Cash a Check for an Exact Amount
|
# Cash a Check for an Exact Amount
|
||||||
|
|
||||||
_Requires the [Checks Amendment](reference-amendments.html#checks)._
|
_Requires the [Checks Amendment](known-amendments.html#checks)._
|
||||||
|
|
||||||
As long as the Check is in the ledger and not expired, the specified recipient can cash it to receive any exact amount up to the amount specified in the Check by sending a [CheckCash transaction][] with an `Amount` field. You would cash a Check this way if you want to receive a specific amount, for example to pay off an invoice or bill exactly.
|
As long as the Check is in the ledger and not expired, the specified recipient can cash it to receive any exact amount up to the amount specified in the Check by sending a [CheckCash transaction][] with an `Amount` field. You would cash a Check this way if you want to receive a specific amount, for example to pay off an invoice or bill exactly.
|
||||||
|
|
||||||
|
|||||||
@@ -1,6 +1,6 @@
|
|||||||
# Look Up Checks by Recipient
|
# Look Up Checks by Recipient
|
||||||
|
|
||||||
_Requires the [Checks Amendment](reference-amendments.html#checks)._
|
_Requires the [Checks Amendment](known-amendments.html#checks)._
|
||||||
|
|
||||||
This tutorial shows how to look up [Checks](checks.html) by their recipient. You may also want to [look up Checks by sender](tutorial-checks-lookup-by-sender.html).
|
This tutorial shows how to look up [Checks](checks.html) by their recipient. You may also want to [look up Checks by sender](tutorial-checks-lookup-by-sender.html).
|
||||||
|
|
||||||
|
|||||||
@@ -1,6 +1,6 @@
|
|||||||
# Look Up Checks by Sender
|
# Look Up Checks by Sender
|
||||||
|
|
||||||
_Requires the [Checks Amendment](reference-amendments.html#checks)._
|
_Requires the [Checks Amendment](known-amendments.html#checks)._
|
||||||
|
|
||||||
This tutorial shows how to look up [Checks](checks.html) by their sender. You may also want to [look up Checks by recipient](tutorial-checks-lookup-by-recipient.html).
|
This tutorial shows how to look up [Checks](checks.html) by their sender. You may also want to [look up Checks by recipient](tutorial-checks-lookup-by-recipient.html).
|
||||||
|
|
||||||
|
|||||||
@@ -1,6 +1,6 @@
|
|||||||
# Send a Check
|
# Send a Check
|
||||||
|
|
||||||
_Requires the [Checks Amendment](reference-amendments.html#checks)._
|
_Requires the [Checks Amendment](known-amendments.html#checks)._
|
||||||
|
|
||||||
Sending a Check is like writing permission for an intended recipient to pull a payment from you. The outcome of this process is a [Check object in the ledger](reference-ledger-format.html#check) which the recipient can cash later.
|
Sending a Check is like writing permission for an intended recipient to pull a payment from you. The outcome of this process is a [Check object in the ledger](reference-ledger-format.html#check) which the recipient can cash later.
|
||||||
|
|
||||||
|
|||||||
@@ -2,4 +2,4 @@
|
|||||||
|
|
||||||
Checks in the XRP Ledger authorize another account to claim funds later, similar to how personal paper checks work.
|
Checks in the XRP Ledger authorize another account to claim funds later, similar to how personal paper checks work.
|
||||||
|
|
||||||
**Caution:** As of 2018-05-03, the [Checks amendment](reference-amendments.html#checks) is not enabled on the XRP Ledger. You can use Checks on the [XRP Test Net](TODO:link) only.
|
**Caution:** As of 2018-05-03, the [Checks amendment](known-amendments.html#checks) is not enabled on the XRP Ledger. You can use Checks on the [XRP Test Net](TODO:link) only.
|
||||||
|
|||||||
@@ -1,3 +1,3 @@
|
|||||||
# Use Complex Payment Types
|
# Use Complex Payment Types
|
||||||
|
|
||||||
In addition to [simple, direct XRP Payments](TODO:link), the XRP Ledger supports a variety of more complex payments for building smart apps on the decentralized ledger.
|
In addition to simple, direct XRP Payments, <!--{# TODO:link tutorial or concept (DOC-1560) for simple XRP payments #}--> the XRP Ledger supports a variety of more complex payments for building smart apps on the decentralized ledger.
|
||||||
|
|||||||
@@ -43,7 +43,7 @@ _Websocket_
|
|||||||
|
|
||||||
You can use the [`account_objects`](reference-rippled.html#account-objects) method to look up escrow objects by destination address.
|
You can use the [`account_objects`](reference-rippled.html#account-objects) method to look up escrow objects by destination address.
|
||||||
|
|
||||||
**Note:** You can only look up pending escrow objects by destination address if those escrows were created after the [fix1523 amendment](reference-amendments.html#fix1523) was enabled on 2017-11-14.
|
**Note:** You can only look up pending escrow objects by destination address if those escrows were created after the [fix1523 amendment](known-amendments.html#fix1523) was enabled on 2017-11-14.
|
||||||
|
|
||||||
Let's say that you want to look up all pending escrow objects with a destination address of `rfztBskAVszuS3s5Kq7zDS74QtHrw893fm`. You can do this using the following example request, where the destination address is the `account` value.
|
Let's say that you want to look up all pending escrow objects with a destination address of `rfztBskAVszuS3s5Kq7zDS74QtHrw893fm`. You can do this using the following example request, where the destination address is the `account` value.
|
||||||
|
|
||||||
|
|||||||
@@ -615,13 +615,13 @@ pages:
|
|||||||
|
|
||||||
# TODO: "Use Deposit Authorization to Block Unwanted Payments" (DOC-1555)
|
# TODO: "Use Deposit Authorization to Block Unwanted Payments" (DOC-1555)
|
||||||
|
|
||||||
- md: tutorials/use-complex-payment-types/use-complex-payment-types.md
|
- name: Use Complex Payment Types
|
||||||
html: use-complex-payment-types.html
|
html: use-complex-payment-types.html
|
||||||
funnel: Docs
|
funnel: Docs
|
||||||
doc_type: Tutorials
|
doc_type: Tutorials
|
||||||
category: Use Complex Payment Types
|
category: Use Complex Payment Types
|
||||||
template: template-landing-children.html
|
template: template-landing-children.html
|
||||||
blurb: Use advanced features like Escrow and Payment Channels to build applications on top of XRP.
|
blurb: Use advanced features like Escrow and Payment Channels to build smart applications on the XRP Ledger.
|
||||||
targets:
|
targets:
|
||||||
- local
|
- local
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user