mirror of
https://github.com/XRPLF/xrpl-dev-portal.git
synced 2025-11-04 11:55:50 +00:00
More interlinking from concept articles
Information architecture improvements, mostly 'See Also' headers within a bunch of concept articles
This commit is contained in:
mDuo13
@@ -32,7 +32,9 @@ No. The XRP Ledger network is opt-in. Each participant directly or indirectly ch
|
||||
|
||||
#### What is the validator incentive structure for validators not run by Ripple?
|
||||
|
||||
If the XRP Ledger becomes successful and is widely used for interbank settlement, there will be an incentive for participants to ensure the reliability and stability of the network. If this happens, institutions will run `rippled` servers to participate in the network. Once you are running a server, the additional cost and effort to operate a validator is essentially zero—it would simply involve flipping a software switch from off to on. It is the validators who decide the evolution of the XRP Ledger, so the primary incentive to run a validator is to preserve and protect the stable operation and sensible evolution of the network.
|
||||
The primary incentive to run a validator is to preserve and protect the stable operation and sensible evolution of the network. It is the validators who decide the evolution of the XRP Ledger, so any business that uses or depends on the XRP Ledger has an inherent incentive to ensure the reliability and stability of the network.
|
||||
|
||||
If you run an XRP Ledger server to participate in the network, the additional cost and effort to operate a validator is minimal. This means that additional incentives, such as the mining rewards in Bitcoin, are not necessary. Ripple avoids paying XRP as a reward for operating a validator so that such incentives do not warp the behavior of validators.
|
||||
|
||||
|
||||
#### Can financial institutions set up transaction validators that will help them meet specific institutional standards and requirements?
|
||||
@@ -51,7 +53,9 @@ However, there will only be one authoritative ledger version at any given time;
|
||||
|
||||
#### Does the XRP Ledger utilize a formal validator onboarding process?
|
||||
|
||||
No, a formal validator onboarding process is not compatible with the XRP Ledger, as it is a system with no central authority. Rather, Ripple provides recommendations and best practices.
|
||||
No, a formal validator onboarding process is not compatible with the XRP Ledger, as it is a system with no central authority.
|
||||
|
||||
For recommendations and best practices, see [Run `rippled` as a Validator](run-rippled-as-a-validator.html).
|
||||
|
||||
|
||||
## Role of XRP
|
||||
@@ -91,7 +95,7 @@ You don't need to use Ripple’s version of the XRP Ledger software to interact
|
||||
|
||||
#### Does Ripple offer a secure method to download their software?
|
||||
|
||||
`rippled` source code is available at <https://github.com/ripple/rippled>, where the tip of the `master`, `release` and `develop` branches always contains a version-setting commit signed by a `rippled` developer. The XRP Ledger also offers prebuilt RPM packages for CentOS, RedHat Enterprise Linux, Fedora and Ubuntu. Those packages are digitally signed by Ripple so that they are tamper-evident and their authenticity can be verified. Lastly, release bulletins are made available over a secure website, and include the commit ID of the repository, as well as the md5sum of the RPM packages that are published.
|
||||
`rippled` source code is available at <https://github.com/ripple/rippled>, where the tip of the `master`, `release` and `develop` branches always contains a version-setting commit signed by a `rippled` developer. The XRP Ledger also offers prebuilt binary packages for CentOS, RedHat Enterprise Linux, Fedora, Ubuntu, and Debian Linux. Those packages are digitally signed by Ripple so that they are tamper-evident and their authenticity can be verified. Lastly, release bulletins are made available over a secure website, and include the commit ID of the repository, as well as the cryptographic hash values of the packages that are published.
|
||||
|
||||
|
||||
#### Does Ripple distinguish between the codebase for validation and the one for user software?
|
||||
|
||||
@@ -79,7 +79,7 @@ For more information, see [Cryptographic Keys](cryptographic-keys.html) and [Mul
|
||||
## Modern Features for Smart Contracts
|
||||
[Modern Features for Smart Contracts]: #modern-features-for-smart-contracts
|
||||
|
||||
Besides simple value transfer with XRP payments, the XRP Ledger has several advanced features that provide useful functions for building applications that use the Internet of Value to serve previously unknown or impractical needs. Rather than running applications as "smart contracts" in the network itself, the XRP Ledger provides tools for settling contracts, while letting the applications themselves run anywhere, in whatever environment or container is appropriate. This "keep it simple" approach is flexible, scalable, and powerful.
|
||||
Besides simple value transfer with [XRP payments](direct-xrp-payments.html), the XRP Ledger has advanced features specialized for the Internet of Value. This allows applications built on XRP to provide services and functionality that would have been impractical or impossible in the past. Rather than running applications as "smart contracts" in the network itself, the XRP Ledger provides tools for settling contracts, while letting the applications themselves run anywhere, in whatever environment or container is appropriate. This "keep it simple" approach is flexible, scalable, and powerful.
|
||||
|
||||
A sample of advanced features in the XRP Ledger:
|
||||
|
||||
|
||||
@@ -31,3 +31,9 @@ Originally, the XRP Ledger was called "Ripple" for the way the technology allowe
|
||||
|
||||
|
||||
The smallest, indivisible unit of XRP was named a "drop" [at the suggestion of Ripple forum member ThePiachu](https://forum.ripple.com/viewtopic.php?f=1&t=40&p=228). An early alternative term was a "jed", after Jed McCaleb.
|
||||
|
||||
## See Also
|
||||
|
||||
- [Send XRP (Interactive Tutorial)](send-xrp.html)
|
||||
- [List XRP In Your Exchange](list-xrp-in-your-exchange.html)
|
||||
- [Currency Formatting in rippled APIs](currency-formats.html#)
|
||||
|
||||
@@ -137,6 +137,23 @@ The formula for calculating an XRP Ledger address is as follows. For the complet
|
||||
console.log(address);
|
||||
// rDTXLQ7ZKZVKz33zJbHjgVShjsBnqMBhmN
|
||||
|
||||
|
||||
## See Also
|
||||
|
||||
- **Concepts:**
|
||||
- [Reserves](reserves.html)
|
||||
- [Cryptographic Keys](cryptographic-keys.html)
|
||||
- [Issuing and Operational Addresses](issuing-and-operational-addresses.html)
|
||||
- **References:**
|
||||
- [account_info method][]
|
||||
- [wallet_propose method][]
|
||||
- [AccountSet transaction][]
|
||||
- [Payment transaction][]
|
||||
- [AccountRoot object](accountroot.html)
|
||||
- **Tutorials:**
|
||||
- [Manage Account Settings (Category)](manage-account-settings.html)
|
||||
- [Monitor Incoming Payments with WebSocket](monitor-incoming-payments-with-websocket.html)
|
||||
|
||||
<!--{# common link defs #}-->
|
||||
{% include '_snippets/rippled-api-links.md' %}
|
||||
{% include '_snippets/tx-type-links.md' %}
|
||||
|
||||
@@ -28,8 +28,19 @@ To successfully submit a multi-signed transaction, you must do all of the follow
|
||||
* All fields of the transaction must be defined before collecting signatures. You cannot [auto-fill](transaction-common-fields.html#auto-fillable-fields) any fields.
|
||||
* If presented in binary form, the `Signers` array must be sorted based on the numeric value of the signer addresses, with the lowest value first. (If submitted as JSON, the [submit_multisigned method][] handles this automatically.)
|
||||
|
||||
For more information, see [Set Up Multi-Signing](set-up-multi-signing.html).
|
||||
## See Also
|
||||
|
||||
- **Tutorials:**
|
||||
- [Set Up Multi-Signing](set-up-multi-signing.html)
|
||||
- [Send a Multi-Signed Transaction](send-a-multi-signed-transaction.html)
|
||||
- **Concepts:**
|
||||
- [Cryptographic Keys](cryptographic-keys.html)
|
||||
- [Special Transaction Cost for Multi-signed transactions](transaction-cost.html#special-transaction-costs)
|
||||
- **References:**
|
||||
- [SignerListSet transaction][]
|
||||
- [SignerList object](signerlist.html)
|
||||
- [sign_for method][]
|
||||
- [submit_multisigned method][]
|
||||
|
||||
{% include '_snippets/rippled-api-links.md' %}
|
||||
{% include '_snippets/tx-type-links.md' %}
|
||||
|
||||
@@ -46,6 +46,13 @@ When an address holds less XRP than its current reserve requirement, it cannot s
|
||||
|
||||
The XRP Ledger has a mechanism to adjust the reserve requirements for long-term changes in the value of XRP. Any changes have to be approved by the consensus process. See [Fee Voting](fee-voting.html) for more information.
|
||||
|
||||
## See Also
|
||||
|
||||
- [account_objects method][]
|
||||
- [AccountRoot Object][]
|
||||
- [Fee Voting](fee-voting.html)
|
||||
- [SetFee pseudo-transaction][]
|
||||
|
||||
<!--{# common link defs #}-->
|
||||
{% include '_snippets/rippled-api-links.md' %}
|
||||
{% include '_snippets/tx-type-links.md' %}
|
||||
|
||||
@@ -19,6 +19,13 @@ Cross-currency payments that exchange two issued currencies automatically use XR
|
||||
|
||||
For more information, see [Autobridging](autobridging.html).
|
||||
|
||||
## See Also
|
||||
|
||||
- [Issued Currencies](issued-currencies.html)
|
||||
- [Decentralized Exchange](decentralized-exchange.html)
|
||||
- [Payment transaction type][Payment transaction]
|
||||
- [Paths](paths.html)
|
||||
|
||||
<!--{# common link defs #}-->
|
||||
{% include '_snippets/rippled-api-links.md' %}
|
||||
{% include '_snippets/tx-type-links.md' %}
|
||||
|
||||
Reference in New Issue
Block a user