mirror of
https://github.com/XRPLF/xrpl-dev-portal.git
synced 2026-06-07 10:46:45 +00:00
Compare commits
1 Commits
release-3.
...
fix_links_
| Author | SHA1 | Date | |
|---|---|---|---|
|
4dec5f720d |
@@ -1,6 +1,6 @@
|
||||
レジャーインデックスは、32ビットの符号なし整数であり、レジャーを識別するために使用します。レジャーインデックスは、レジャーの _シーケンス番号_ と呼ばれることもあります。（[アカウントシーケンス](../../references/protocol/data-types/basic-data-types.md#アカウントシーケンス)とは異なります。）一番最初のレジャーでは、レジャーインデックスは1でした。新しいレジャーのレジャーインデックスは、その直前のレジャーのレジャーインデックスに1を加算した値になります。
|
||||
レジャーインデックスは、32ビットの符号なし整数であり、レジャーを識別するために使用します。レジャーインデックスは、レジャーの _シーケンス番号_ と呼ばれることもあります。（[アカウントシーケンス](/docs/references/protocol/data-types/basic-data-types.md#アカウントシーケンス)とは異なります。）一番最初のレジャーでは、レジャーインデックスは1でした。新しいレジャーのレジャーインデックスは、その直前のレジャーのレジャーインデックスに1を加算した値になります。
|
||||
|
||||
レジャーインデックスがレジャーの順番を示すのに対し、[ハッシュ][]値はレジャーの正確なコンテンツを示します。2つのレジャーが同じハッシュ値を持つ場合、それらは必ず同じものです。検証済みレジャーでは、ハッシュ値とレジャーインデックスは等しく有効で、1:1の関係です。しかし、進行中のレジャーに対しては、以下の理由によりその限りでありません。
|
||||
レジャーインデックスがレジャーの順番を示すのに対し、[ハッシュ](/docs/references/protocol/data-types/basic-data-types.md#ハッシュ)値はレジャーの正確なコンテンツを示します。2つのレジャーが同じハッシュ値を持つ場合、それらは必ず同じものです。検証済みレジャーでは、ハッシュ値とレジャーインデックスは等しく有効で、1:1の関係です。しかし、進行中のレジャーに対しては、以下の理由によりその限りでありません。
|
||||
|
||||
* ネットワーク全体でのトランザクションの伝搬遅延が原因で、2つの異なる`rippled`サーバで、同じレジャーインデックスを持つ現行レジャーに対するコンテンツが異なる場合があります。
|
||||
* 決済済みレジャーバージョンが複数あり、コンセンサスによる検証が競合している場合があります。このようなレジャーバージョンでは、レジャーインデックスは同じですが、コンテンツは異なります（ハッシュも異なります）。これらの決済済みレジャーのうち、検証済みになるのは1つだけです。
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
A ledger index is a 32-bit unsigned integer used to identify a ledger. The ledger index is sometimes known as the ledger's _sequence number_. (This is different from an [account sequence](../../references/protocol/data-types/basic-data-types.md#account-sequence).) The very first ledger was ledger index 1, and each new ledger has a ledger index that is 1 higher than the ledger index of the ledger immediately before it.
|
||||
A ledger index is a 32-bit unsigned integer used to identify a ledger. The ledger index is sometimes known as the ledger's _sequence number_. (This is different from an [account sequence](/docs/references/protocol/data-types/basic-data-types.md#account-sequence).) The very first ledger was ledger index 1, and each new ledger has a ledger index that is 1 higher than the ledger index of the ledger immediately before it.
|
||||
|
||||
The ledger index indicates the order of the ledgers; the [Hash][] value identifies the exact contents of the ledger. Two ledgers with the same hash are always the same. For validated ledgers, hash values and ledger indexes are equally valid and correlate 1:1. However, this is not true for in-progress ledgers:
|
||||
The ledger index indicates the order of the ledgers; the [hash](/docs/references/protocol/data-types/basic-data-types.md#hashes) value identifies the exact contents of the ledger. Two ledgers with the same hash are always the same. For validated ledgers, hash values and ledger indexes are equally valid and correlate 1:1. However, this is not true for in-progress ledgers:
|
||||
|
||||
* Two different `rippled` servers may have different contents for a current ledger with the same ledger index, due to latency in propagating transactions throughout the network.
|
||||
* There may be multiple closed ledger versions competing to be validated by consensus. These ledger versions have the same ledger index but different contents (and different hashes). Only one of these closed ledgers can become validated.
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
| `Field` | Type | Description |
|
||||
|:--------------|:-------|:----------------------------------------------------|
|
||||
| `node` | String | The [node public key][] of the peer server this reservation is for, as [base58][]. |
|
||||
| `node` | String | The [node public key](/docs/concepts/networks-and-servers/peer-protocol.md#node-key-pair) of the peer server this reservation is for, as [base58](/docs/references/protocol/data-types/base58-encodings.md). |
|
||||
| `description` | String | _(May be omitted)_ The description provided with this peer reservation, if any. |
|
||||
|
||||
@@ -20,7 +20,7 @@ Having trouble getting your server started? See [rippled Server Won't Start](../
|
||||
|
||||
{% partial file="/docs/_snippets/conf-file-location.md" /%}
|
||||
|
||||
See [the `rippled` GitHub repository](https://github.com/XRPLF/rippled/blob/master/cfg/rippled-example.cfg) for a description of all configuration options.
|
||||
See [the `rippled` GitHub repository](https://github.com/XRPLF/rippled/blob/release-3.1/cfg/rippled-example.cfg) for a description of all configuration options.
|
||||
|
||||
You must restart `rippled` for any configuration changes to take effect.
|
||||
|
||||
|
||||
@@ -73,7 +73,7 @@ All of the configuration flags can be helpful for specific use cases. The follow
|
||||
|------|-------------|
|
||||
| `allowTrustLineClawback` | Allow account to claw back tokens it has issued. See [Clawing Back Tokens](../tokens/fungible-tokens/clawing-back-tokens.md). |
|
||||
| `disableMasterKey` | Disallow use of the master key pair. Can only be enabled if the account has configured another way to sign transactions, such as a regular key or a signer list. See [Master Key Pair](./cryptographic-keys.md#master-key-pair). |
|
||||
| `disallowIncomingTrustLine` | Block incoming trust lines. See [Trust Lines](../tokens/fungible-tokens/index.md#trust-lines). |
|
||||
| `disallowIncomingTrustLine` | Block incoming trust lines. See [Trust Line Tokens](../tokens/fungible-tokens/trust-line-tokens.md). |
|
||||
| `globalFreeze` | Freeze all tokens issued by this account. See [Global Freeze](../tokens/fungible-tokens/freezes.md#global-freeze).
|
||||
| `noFreeze` | Permanently remove the ability to freeze individual trust lines or end a global freeze. See [Freezing Tokens](../tokens/fungible-tokens/freezes.md). |
|
||||
| `requireAuthorization` | Requires authorized trust lines for other accounts to hold tokens issued by this account. See [Authorized Trust Lines](../tokens/fungible-tokens/authorized-trust-lines.md).
|
||||
|
||||
@@ -39,7 +39,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.) <!-- SPELLING_IGNORE: xrpuzzler -->
|
||||
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; he used the puzzle's solution as the passphrase to an account holding the prize XRP.) <!-- SPELLING_IGNORE: xrpuzzler -->
|
||||
|
||||
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.
|
||||
|
||||
|
||||
@@ -59,7 +59,7 @@ Applications can look up the current base and incremental reserve values using t
|
||||
|
||||
To determine the owner reserve of an account, multiply the incremental reserve by the number of objects the account owns. To look up the number of objects an account owns, call the [account_info method][] and take `account_data.OwnerCount`.
|
||||
|
||||
To calculate an address's total reserve requirement, multiply `OwnerCount` by `reserve_inc_xrp`, then add `reserve_base_xrp`. [Here is a demonstration](../../tutorials/sample-apps/build-a-desktop-wallet-in-python.md#codeblock-17) of this calculation in Python.
|
||||
To calculate an address's total reserve requirement, multiply `OwnerCount` by `reserve_inc_xrp`, then add `reserve_base_xrp`. See also: {% repo-link path="_code-samples/calculate-reserves/" %}Code Sample: Calculate Reserves{% /repo-link %}.
|
||||
|
||||
|
||||
## Going Below the Reserve Requirement
|
||||
|
||||
@@ -24,8 +24,8 @@ There are several interfaces you can use to connect to the XRP Ledger, depending
|
||||
|
||||
- [HTTP / WebSocket APIs](../../../../references/http-websocket-apis/index.md) can be used as a low-level interface to all core XRP Ledger functionality.
|
||||
- [Client Libraries](../../../../references/client-libraries.md) are available in several programming languages to provide convenient utilities for accessing the XRP Ledger.
|
||||
- Other tools such as [xApps](https://xumm.readme.io/docs/xapps) are also available.
|
||||
- Third party wallet applications might also be useful, especially for humans in charge of standby addresses.
|
||||
- Graphical wallet applications might also be useful, especially for humans in charge of standby addresses.
|
||||
- Some wallets provide extensible functionality like [xApps](https://docs.xaman.dev/environments/xapps-dapps).
|
||||
|
||||
However, take care to only use reputable tools from their official distribution channels. Malicious servers, libraries, or apps could be configured to leak secret keys to an attacker.
|
||||
|
||||
|
||||
@@ -21,7 +21,7 @@ See [NFT Reserve Requirements](reserve-requirements.md).
|
||||
|
||||
## Transfer Fees
|
||||
|
||||
As an issuer, you can mint your NFT with a transfer fee to be collected whenever your NFT is traded on the XRPL. If you specify a transfer fee, the NFT can only be traded for tokens for which you have a trust line. See [Trust Lines](../fungible-tokens/index.md#trust-lines).
|
||||
As an issuer, you can mint your NFT with a transfer fee to be collected whenever your NFT is traded on the XRPL. If you specify a transfer fee, the NFT can only be traded for tokens for which you have a trust line. See [Trust Line Tokens](../fungible-tokens/trust-line-tokens.md).
|
||||
|
||||
## Sell Offers
|
||||
|
||||
|
||||
@@ -207,7 +207,7 @@ If the transfer succeeds and the payee already holds vault shares, their balance
|
||||
|
||||
### Frozen Assets
|
||||
|
||||
The issuer of a vault asset can enact a [freeze](./fungible-tokens/freezes) for trust line tokens or [lock an MPT](./fungible-tokens/deep-freeze#how-does-mpt-freeze/lock-behavior-differ-from-iou). When a vault asset is frozen:
|
||||
The issuer of a vault asset can enact a [freeze](./fungible-tokens/freezes) for trust line tokens or [lock an MPT](./fungible-tokens/deep-freeze#how-does-mpt-freezelock-behavior-differ-from-iou). When a vault asset is frozen:
|
||||
|
||||
1. Withdrawals can only be made to the asset’s issuer.
|
||||
2. The asset cannot be deposited into the vault.
|
||||
|
||||
@@ -13,7 +13,7 @@ To use the XRP Ledger effectively, you need to be able to understand [transactio
|
||||
|
||||
The XRP Ledger is a shared system, with all data recorded publicly and carefully, securely updated with each new [ledger version](../../ledgers/index.md). Anyone can look up the exact outcome of any transaction and read the [transaction metadata](../../../references/protocol/transactions/metadata.md) to see what it did.
|
||||
|
||||
This document describes, at a low level, how to know why a transaction reached the outcome it did. For an end-user, it is easier to look at a processed view of a transaction. For example, you can [use XRP Charts to get an English-language description of any recorded transaction](https://xrpcharts.ripple.com/#/transactions/).
|
||||
This document describes, at a low level, how to know why a transaction reached the outcome it did. For an end-user, it is easier to look at a processed view of a transaction. For example, you can [use XRP Charts to get an English-language description of any recorded transaction](https://livenet.xrpl.org/transactions/transactions/).
|
||||
|
||||
## Prerequisites
|
||||
|
||||
@@ -241,7 +241,7 @@ The [`QualityIn` and `QualityOut` settings of trust lines](../../../references/p
|
||||
|
||||
If the amount to be sent or received is outside of the [token precision](../../../references/protocol/data-types/currency-formats.md#token-precision), it is possible that one side may be debited for an amount that is rounded to nothing on the other side of the transaction. As a result, when two parties transact while their balances are different by a factor of 10<sup>16</sup>, it is possible that rounding may effectively "create" or "destroy" small amounts of the token. (XRP is never rounded, so this is not possible with XRP.)
|
||||
|
||||
Depending on the length of the [paths](../../tokens/fungible-tokens/paths.md), the metadata for cross-currency payments can be _long_. For example, [transaction 8C55AFC2A2AA42B5CE624AEECDB3ACFDD1E5379D4E5BF74A8460C5E97EF8706B](https://xrpcharts.ripple.com/#/transactions/8C55AFC2A2AA42B5CE624AEECDB3ACFDD1E5379D4E5BF74A8460C5E97EF8706B) delivered 2.788 GCB issued by `rHaaans...`, spending XRP but passing through USD from 2 issuers, paying XRP to 2 accounts, removing an unfunded offer from `r9ZoLsJ...` to trade EUR for ETH, plus bookkeeping for a total of 17 different ledger objects modified. <!-- SPELLING_IGNORE: gcb -->
|
||||
Depending on the length of the [paths](../../tokens/fungible-tokens/paths.md), the metadata for cross-currency payments can be _long_. For example, [transaction 8C55AFC2A2AA42B5CE624AEECDB3ACFDD1E5379D4E5BF74A8460C5E97EF8706B](https://livenet.xrpl.org/transactions/transactions/8C55AFC2A2AA42B5CE624AEECDB3ACFDD1E5379D4E5BF74A8460C5E97EF8706B) delivered 2.788 GCB issued by `rHaaans...`, spending XRP but passing through USD from 2 issuers, paying XRP to 2 accounts, removing an unfunded offer from `r9ZoLsJ...` to trade EUR for ETH, plus bookkeeping for a total of 17 different ledger objects modified. <!-- SPELLING_IGNORE: gcb -->
|
||||
|
||||
#### Using AMM Liquidity
|
||||
|
||||
@@ -326,7 +326,7 @@ Of course, an EscrowFinish can only be successful if it meets the conditions of
|
||||
|
||||
Escrow transactions also do normal [bookkeeping](#general-purpose-bookkeeping) for adjusting the sender's owner reserve and the directories of the accounts involved.
|
||||
|
||||
In the following excerpt, we see that `r9UUEX...`'s balance increases by 1 billion XRP and its owner count decreases by 1 because an escrow from that account to itself finished successfully. The `Sequence` number does not change because [a third party completed the escrow](https://xrpcharts.ripple.com/#/transactions/C4FE7F5643E20E7C761D92A1B8C98320614DD8B8CD8A04CFD990EBC5A39DDEA2):
|
||||
In the following excerpt, we see that `r9UUEX...`'s balance increases by 1 billion XRP and its owner count decreases by 1 because an escrow from that account to itself finished successfully. The `Sequence` number does not change because [a third party completed the escrow](https://livenet.xrpl.org/transactions/transactions/C4FE7F5643E20E7C761D92A1B8C98320614DD8B8CD8A04CFD990EBC5A39DDEA2):
|
||||
|
||||
```json
|
||||
{
|
||||
|
||||
@@ -39,7 +39,7 @@ Strive to have your validator embody the following properties. Being a good vali
|
||||
|
||||
- **In agreement**
|
||||
|
||||
A good validator's votes match the outcome of the consensus process as often as possible. To do otherwise could indicate that your validator's software is outdated, buggy, or intentionally biased. Always run the [latest `rippled` release](https://github.com/XRPLF/rippled/tree/release) without modifications. [Watch `rippled` releases](https://github.com/XRPLF/rippled/releases) and subscribe to the [Google Group](https://groups.google.com/g/ripple-server) to be notified of new releases.
|
||||
A good validator's votes match the outcome of the consensus process as often as possible. To do otherwise could indicate that your validator's software is outdated, buggy, or intentionally biased. Always run the latest stable release without modifications. [Watch `rippled` releases](https://github.com/XRPLF/rippled/releases) and subscribe to the [Google Group](https://groups.google.com/g/ripple-server) to be notified of new releases.
|
||||
|
||||
- **Issuing prompt votes**
|
||||
|
||||
@@ -51,7 +51,7 @@ Strive to have your validator embody the following properties. Being a good vali
|
||||
|
||||
A good validator has a clearly identified owner. Providing [domain verification](#6-provide-domain-verification) is a good start. Ideally, XRP Ledger network UNLs include validators run by different owners in multiple legal jurisdictions and geographic areas. This reduces the chance that any localized events could interfere with the impartial operations of trusted validators. <!-- STYLE_OVERRIDE: clearly -->
|
||||
|
||||
It is strongly recommended that operators use the list providers that are present in this [example file](https://github.com/XRPLF/rippled/blob/develop/cfg/validators-example.txt).
|
||||
It is strongly recommended that operators use the list providers that are present in this [example file](https://github.com/XRPLF/rippled/blob/release-3.1/cfg/validators-example.txt).
|
||||
|
||||
|
||||
|
||||
@@ -163,7 +163,7 @@ For a comparison of these approaches, see [Pros and Cons of Peering Configuratio
|
||||
|
||||
This configuration connects your validator to the XRP Ledger network using [discovered peers](../../../concepts/networks-and-servers/peer-protocol.md#peer-discovery). This is the default behavior for `rippled` servers.
|
||||
|
||||
_**To connect your validator to the XRP Ledger network using discovered peers,**_ omit the `[peer_private]` stanza or set it to `0` in your validator's `rippled.cfg` file. The [example `rippled.cfg` file](https://github.com/XRPLF/rippled/blob/develop/cfg/rippled-example.cfg) is delivered with this configuration.
|
||||
_**To connect your validator to the XRP Ledger network using discovered peers,**_ omit the `[peer_private]` stanza or set it to `0` in your validator's `rippled.cfg` file. The [example `rippled.cfg` file](https://github.com/XRPLF/rippled/blob/release-3.1/cfg/rippled-example.cfg) is delivered with this configuration.
|
||||
|
||||
|
||||
### Connect using proxies
|
||||
@@ -218,7 +218,7 @@ _**To connect your validator to the network using public hubs:**_
|
||||
```
|
||||
|
||||
{% admonition type="info" name="Note" %}
|
||||
The above list may evolve over time. To ensure you're using the most current set of public hubs, refer to the official [`rippled-example.cfg`](https://github.com/XRPLF/rippled/blob/develop/cfg/rippled-example.cfg) maintained by XRPLF.
|
||||
The above list may evolve over time. To ensure you're using the most current set of public hubs, refer to the official [`rippled-example.cfg`](https://github.com/XRPLF/rippled/blob/release-3.1/cfg/rippled-example.cfg) maintained by XRPLF.
|
||||
{% /admonition %}
|
||||
|
||||
|
||||
@@ -285,7 +285,7 @@ To provide domain verification:
|
||||
|
||||
2. Serve an [`xrp-ledger.toml`](../../../references/xrp-ledger-toml.md) file at your domain, and complete the [domain verification](../../../references/xrp-ledger-toml.md#domain-verification) steps. Once you have completed these steps, your validator should be visible to the livenet [explorer](https://livenet.xrpl.org/network/validators) or any other site that monitors the validator network and supports decetralized domain verification.
|
||||
|
||||
3. Share your validator's public key with the public, especially other `rippled` operators. For example, you can share your validator's public key on your website, on social media, in the [XRPChat community forum](https://www.xrpchat.com/), or in a press release.
|
||||
3. Share your validator's public key with the public, especially other `rippled` operators. For example, you can share your validator's public key on your website, on social media, or in a press release.
|
||||
|
||||
|
||||
## Revoke validator keys
|
||||
|
||||
@@ -19,12 +19,12 @@ You should consider these factors to ensure that your server has the capacity to
|
||||
|
||||
The default configuration file contains settings for a broad range of common use cases. You can get better performance by customizing the settings for your specific hardware and intended usage pattern.
|
||||
|
||||
The settings in this section are parameters in the `rippled.cfg` file. You can access an example config file, `rippled-example.cfg`, in the [`cfg` directory](https://github.com/XRPLF/rippled/blob/develop/cfg/rippled-example.cfg) in the `rippled` GitHub repo. The settings in the example config file match the default config installed alongside the server.
|
||||
The settings in this section are parameters in the `rippled.cfg` file. You can access an example config file, `rippled-example.cfg`, in the [`cfg` directory](https://github.com/XRPLF/rippled/blob/release-3.1/cfg/rippled-example.cfg) in the `rippled` GitHub repo. The settings in the example config file match the default config installed alongside the server.
|
||||
|
||||
|
||||
### Node Size
|
||||
|
||||
The `[node_size]` parameter should match the overall hardware capacity of your server. You can omit this parameter to have the server automatically choose an appropriate setting based on the system's total RAM and number of CPU threads. You can set this value explicitly if the automatic setting is wrong for your system, for example if some of the system's RAM or threads need to be set aside for other software, or the amounts reported by the operating system are inaccurate. (This can occur in some containers.) {% badge href="https://github.com/XRPLF/rippled/releases/tag/1.8.1" %}Updated in: rippled 1.8.1{% /badge %}
|
||||
The `[node_size]` parameter should match the overall hardware capacity of your server. You can omit this parameter to have the server automatically choose an appropriate setting based on the system's total RAM and number of CPU threads. You can set this value explicitly if the automatic setting is wrong for your system, for example if some of the system's RAM or threads need to be set aside for other software, or the amounts reported by the operating system are inaccurate. (This can occur in some containers.)
|
||||
|
||||
As a general rule, you should always use the largest node size your available RAM can support. See the following table for recommended settings.
|
||||
|
||||
|
||||
@@ -102,7 +102,7 @@ Before you install Clio, you must meet the following requirements.
|
||||
If you want access to development or pre-release versions, use one of the following instead of `stable`:
|
||||
|
||||
- `unstable` - Pre-release builds such as betas or release candidates
|
||||
- `nightly` - Nightly development builds based on the [`develop` branch](https://github.com/XRPLF/Clio/tree/develop))
|
||||
- `nightly` - Nightly development builds
|
||||
|
||||
6. Fetch the Ripple repository.
|
||||
|
||||
|
||||
@@ -1,6 +1,4 @@
|
||||
---
|
||||
html: diagnosing-problems.html
|
||||
parent: troubleshoot-the-rippled-server.html
|
||||
seo:
|
||||
description: Collect information to identify the cause of problems.
|
||||
labels:
|
||||
@@ -127,47 +125,6 @@ It is normal for a `rippled` the server to print many warning-level (`WRN`) mess
|
||||
For a more thorough explanation of various types of log messages, see [Understanding Log Messages](understanding-log-messages.md).
|
||||
|
||||
|
||||
## Info Collection Script
|
||||
|
||||
If you have problems diagnosing the problem, or you are unable to resolve the problem with any of the common fixes, you may want to ask for help in a support forum or the [GitHub issues](https://github.com/XRPLF/rippled/issues). When asking for help, you can use an info collection script to gather information about your system to help others diagnose the issue.
|
||||
|
||||
The official package installation (for [Ubuntu/Debian](../installation/install-rippled-on-ubuntu.md) or [CentOS/RedHat](../installation/install-rippled-on-rhel.md)) installs such a script by default, to `/opt/ripple/bin/getRippledInfo`. If you compiled `rippled` yourself, you can find the same script [in the `rippled` source code repository](https://github.com/XRPLF/rippled/blob/develop/bin/getRippledInfo).
|
||||
|
||||
To use the script:
|
||||
|
||||
1. Run the script while `rippled` is running.
|
||||
|
||||
```
|
||||
$ /opt/ripple/bin/getRippledInfo
|
||||
|
||||
####################################################
|
||||
rippled info has been gathered. Please copy the
|
||||
contents of /tmp/ripple_info.Xo8Xr/rippled_info.md
|
||||
to a github gist at https://gist.github.com/
|
||||
|
||||
PLEASE REVIEW THIS FILE FOR ANY SENSITIVE DATA
|
||||
BEFORE POSTING! We have tried our best to omit
|
||||
any sensitive information from this file, but you
|
||||
should verify before posting.
|
||||
####################################################
|
||||
```
|
||||
|
||||
The script collects the output of many commands and writes them to a temporary file. The filename is randomized with a string of letters and numbers (case-sensitive), for example: `/tmp/ripple_info.Xo8Xr/rippled_info.md`
|
||||
|
||||
|
||||
2. Look over the output file for sensitive information.
|
||||
|
||||
The script attempts to scrub sensitive information from the output, such as validator keys or tokens. However, you should still check the output before posting publicly, as a precaution. For example, the script outputs detailed information about your server hardware, and you may want to remove some sections for privacy reasons. Use a text editor to read the output file and to remove anything you don't want to post.
|
||||
|
||||
```
|
||||
nano /tmp/ripple_info.Xo8Xr/rippled_info.md
|
||||
```
|
||||
|
||||
3. Upload the output file where others can see it.
|
||||
|
||||
You can upload the file directly to [GitHub Gist](https://gist.github.com/), [Pastebin](https://pastebin.com/), or a similar service. If you are running `rippled` on a remote server, you may find it easier to first transfer the file to a machine with a web browser, using `scp` or a similar tool. <!-- SPELLING_IGNORE: pastebin -->
|
||||
|
||||
|
||||
## See Also
|
||||
|
||||
- **Concepts:**
|
||||
|
||||
@@ -17,7 +17,9 @@ This document describes steps to detect and correct this problem if it occurs.
|
||||
|
||||
The capacity of the SQLite database is a result of the database's _page size_ parameter, which cannot be easily changed after the database is created. (For more information on SQLite's internals, see [the official SQLite documentation](https://www.sqlite.org/fileformat.html).) The database can reach its capacity even if there is still free space on the disk and filesystem where it is stored. As described in the [Fix](#fix) below, reconfiguring the page size to avoid this problem requires a somewhat time-consuming migration process. <!-- STYLE_OVERRIDE: easily -->
|
||||
|
||||
{% admonition type="success" name="Tip" %}Full history is not necessary for most use cases. Servers with full transaction history may be useful for long-term analysis and archive purposes or as a precaution against disasters.{% /admonition %}
|
||||
{% admonition type="success" name="Tip" %}
|
||||
Full history is not necessary for most use cases. Servers with full transaction history may be useful for long-term analysis and archive purposes or as a precaution against disasters.
|
||||
{% /admonition %}
|
||||
|
||||
|
||||
## Detection
|
||||
@@ -29,7 +31,9 @@ If your server is vulnerable to this problem, you can detect it two ways:
|
||||
|
||||
In both cases, detection of the problem requires access to `rippled`'s server logs.
|
||||
|
||||
{% admonition type="success" name="Tip" %}The location of the debug log depends on your `rippled` server's config file. The [default configuration](https://github.com/XRPLF/rippled/blob/master/cfg/rippled-example.cfg#L1139-L1142) writes the server's debug log to the file `/var/log/rippled/debug.log`.{% /admonition %}
|
||||
{% admonition type="success" name="Tip" %}
|
||||
The location of the debug log depends on your `rippled` server's config file. The [default configuration](https://github.com/XRPLF/rippled/blob/master/cfg/rippled-example.cfg#L1139-L1142) writes the server's debug log to the file `/var/log/rippled/debug.log`.
|
||||
{% /admonition %}
|
||||
|
||||
### Proactive Detection
|
||||
|
||||
|
||||
@@ -59,7 +59,7 @@ Since then, the company has regularly sold XRP, used it to strengthen XRP market
|
||||
|
||||
### Naming
|
||||
|
||||
Originally, the XRP Ledger was called "Ripple" for the way the technology allowed payments [to ripple through multiple hops and currencies](../concepts/tokens/fungible-tokens/rippling.md). For the native asset built into the ledger, the creators chose the ticker symbol "XRP" from the term "ripple credits" or "ripples" and the X prefix for non-national currencies in the [ISO 4217](https://www.iso.org/iso-4217-currency-codes.html) standard. The company registered itself as "Ripple Labs". The name "XRP" came to be used to refer to the asset in all contexts, to avoid confusion with the similar names for the technology and company, and eventually the company shortened its own name to "Ripple". In May 2018, [the community selected a new "X" symbol](https://twitter.com/xrpsymbol/status/1006925937571713025) to represent XRP to differentiate it from the triskelion logo that had previously been used for both the company and the digital asset.
|
||||
Originally, the XRP Ledger was called "Ripple" for the way the technology allowed payments [to ripple through multiple hops and currencies](../concepts/tokens/fungible-tokens/rippling.md). For the native asset built into the ledger, the creators chose the ticker symbol "XRP" from the term "ripple credits" or "ripples" and the X prefix for non-national currencies in the [ISO 4217](https://www.iso.org/iso-4217-currency-codes.html) standard. The company registered itself as "Ripple Labs". The name "XRP" came to be used to refer to the asset in all contexts, to avoid confusion with the similar names for the technology and company, and eventually the company shortened its own name to "Ripple". In May 2018, the community selected a new "X" symbol to represent XRP to differentiate it from the triskelion logo that had previously been used for both the company and the digital asset.
|
||||
|
||||
| XRP "X" Logo | Ripple triskelion |
|
||||
|:---------------------------------------|:------------------------------------|
|
||||
|
||||
@@ -11,14 +11,14 @@ These client libraries simplify some of the common work of accessing and process
|
||||
- To stay up-to-date on JavaScript/TypeScript and Python library updates, join the [xrpl-announce mailing list](https://groups.google.com/g/xrpl-announce).
|
||||
- For other programming languages, you can access the XRP Ledger through the [HTTP APIs](http-websocket-apis/index.md).
|
||||
|
||||
| Language | Library Name | Get Started | API Reference | Source Code |
|
||||
|---------------------------------|---------------------------|-------------|--------------|-------------|
|
||||
| **Python** | `xrpl-py` | [Get Started Using Python](../tutorials/get-started/get-started-python.md) | [API Reference](https://xrpl-py.readthedocs.io/) | [Repo](https://github.com/XRPLF/xrpl-py) |
|
||||
| **Go** | `xrpl-go` | [Get Started Using Go](../tutorials/get-started/get-started-go.md) | [API Reference](https://pkg.go.dev/github.com/Peersyst/xrpl-go) | [Repo](https://github.com/Peersyst/xrpl-go) |
|
||||
| **JavaScript** / **TypeScript** | `xrpl.js` | [Get Started](../tutorials/get-started/get-started-javascript.md) | [API Reference](https://js.xrpl.org/) | [Repo](https://github.com/XRPLF/xrpl.js) |
|
||||
| **JavaScript** / **TypeScript** | `xrpl-client` | [Get Started](https://jsfiddle.net/WietseWind/35az6p1b/) | [NPM Reference](https://www.npmjs.com/package/xrpl-client) | [Repo](https://github.com/XRPL-Labs/xrpl-client) |
|
||||
| **JavaScript** / **TypeScript** | `xrpl-accountlib` | [Get Started](https://jsfiddle.net/WietseWind/gkefpnu0/) | [NPM Reference](https://www.npmjs.com/package/xrpl-accountlib) | [Repo](https://github.com/WietseWind/xrpl-accountlib) |
|
||||
| **C++** | `rippled` Signing Library | [Get Started](https://github.com/XRPLF/rippled/tree/develop/Builds/linux#signing-library) | | (Part of [`rippled`](https://github.com/XRPLF/rippled/)) |
|
||||
| **Java** | `xrpl4j` | [Get Started Using Java](../tutorials/get-started/get-started-java.md) | [API Reference](https://javadoc.io/doc/org.xrpl/) | [Repo](https://github.com/XRPLF/xrpl4j) |
|
||||
| **PHP** | `XRPL_PHP` | [Get Started Using PHP](../tutorials/get-started/get-started-php.md) | [XRPL_PHP Docs](https://alexanderbuzz.github.io/xrpl-php-docs/) | [Repo](https://github.com/AlexanderBuzz/xrpl-php) |
|
||||
| **Ruby** | `XRPB` | | [XRPB Docs](https://www.rubydoc.info/gems/xrbp) | [Repo](https://github.com/DevNullProd/XRBP) |
|
||||
| Language | Library Name | Get Started | API Reference | Source Code |
|
||||
|---------------------------------|-------------------|-------------|--------------|-------------|
|
||||
| **Python** | `xrpl-py` | [Get Started Using Python](../tutorials/get-started/get-started-python.md) | [API Reference](https://xrpl-py.readthedocs.io/) | [Repo](https://github.com/XRPLF/xrpl-py) |
|
||||
| **Go** | `xrpl-go` | [Get Started Using Go](../tutorials/get-started/get-started-go.md) | [API Reference](https://pkg.go.dev/github.com/Peersyst/xrpl-go) | [Repo](https://github.com/Peersyst/xrpl-go) |
|
||||
| **JavaScript** / **TypeScript** | `xrpl.js` | [Get Started](../tutorials/get-started/get-started-javascript.md) | [API Reference](https://js.xrpl.org/) | [Repo](https://github.com/XRPLF/xrpl.js) |
|
||||
| **JavaScript** / **TypeScript** | `xrpl-client` | [Get Started](https://jsfiddle.net/WietseWind/35az6p1b/) | [NPM Reference](https://www.npmjs.com/package/xrpl-client) | [Repo](https://github.com/XRPL-Labs/xrpl-client) |
|
||||
| **JavaScript** / **TypeScript** | `xrpl-accountlib` | [Get Started](https://jsfiddle.net/WietseWind/gkefpnu0/) | [NPM Reference](https://www.npmjs.com/package/xrpl-accountlib) | [Repo](https://github.com/WietseWind/xrpl-accountlib) |
|
||||
| **C++** | `libxrpl` | [Get Started](https://github.com/XRPLF/rippled/blob/develop/BUILD.md) | | (Part of [`rippled`](https://github.com/XRPLF/rippled/)) |
|
||||
| **Java** | `xrpl4j` | [Get Started Using Java](../tutorials/get-started/get-started-java.md) | [API Reference](https://javadoc.io/doc/org.xrpl/) | [Repo](https://github.com/XRPLF/xrpl4j) |
|
||||
| **PHP** | `XRPL_PHP` | [Get Started Using PHP](../tutorials/get-started/get-started-php.md) | [XRPL_PHP Docs](https://alexanderbuzz.github.io/xrpl-php-docs/) | [Repo](https://github.com/AlexanderBuzz/xrpl-php) |
|
||||
| **Ruby** | `XRPB` | | [XRPB Docs](https://www.rubydoc.info/gems/xrbp) | [Repo](https://github.com/DevNullProd/XRBP) |
|
||||
|
||||
@@ -1,6 +1,4 @@
|
||||
---
|
||||
html: error-formatting.html
|
||||
parent: api-conventions.html
|
||||
seo:
|
||||
description: Error formats and common error codes for WebSocket, JSON-RPC, and Commandline interfaces.
|
||||
labels:
|
||||
@@ -111,7 +109,7 @@ All methods can potentially return any of the following values for the `error` c
|
||||
|
||||
- `amendmentBlocked` - The server is [amendment blocked](../../../concepts/networks-and-servers/amendments.md#amendment-blocked-servers) and needs to be updated to the latest version to stay synced with the XRP Ledger network.
|
||||
- `failedToForward` - (Clio servers only) The server tried to forward this request to a `rippled` server, but the connection failed.
|
||||
- `invalid_API_version` - The server does not support the [API version number](request-formatting.md#api-versioning) from the request.
|
||||
- `invalid_API_version` - The server does not support the [API version number](../index.md#api-versioning) from the request.
|
||||
- `jsonInvalid` - (WebSocket only) The request is not a proper JSON object.
|
||||
- JSON-RPC returns a 400 Bad Request HTTP error in this case instead.
|
||||
- `missingCommand` - (WebSocket only) The request did not specify a `command` field.
|
||||
|
||||
@@ -80,7 +80,7 @@ The object inside the `params` array can contain the following fields:
|
||||
|
||||
| Field | Type | Description |
|
||||
|:--------------------|:----------|:-------------------------------------------|
|
||||
| `api_version` | Number | _(Optional)_ The API version to use. For details, see [API Versioning](#api-versioning). |
|
||||
| `api_version` | Number | _(Optional)_ The API version to use. For details, see [API Versioning](../index.md#api-versioning). |
|
||||
| (Method Parameters) | (Various) | Provide any parameters to the method here. |
|
||||
|
||||
See [Response Formatting](response-formatting.md) for the response from the server.
|
||||
@@ -91,7 +91,7 @@ Put the API method name after any normal (dash-prefaced) commandline options, fo
|
||||
|
||||
The commandline calls JSON-RPC, so its responses always match the JSON-RPC [response format](response-formatting.md).
|
||||
|
||||
The commandline always uses the latest [API version](./index.md#api-versioning).
|
||||
The commandline always uses the latest [API version](../index.md#api-versioning).
|
||||
|
||||
{% admonition type="warning" name="Caution" %}The commandline interface is intended for administrative purposes only and is _not a supported API_. New versions of `rippled` may introduce breaking changes to the commandline API without warning!{% /admonition %}
|
||||
|
||||
|
||||
@@ -10,7 +10,7 @@ labels:
|
||||
|
||||
[[Source]](https://github.com/XRPLF/clio/blob/develop/src/rpc/handlers/NFTHistory.cpp "Source")
|
||||
|
||||
The `nft_history` command asks the Clio server for past transaction metadata for the [NFT](../../../../concepts/tokens/nfts/index.md) being queried. {% badge href="https://github.com/XRPLF/clio/releases/tag/1.1.0" %}New in: Clio v1.1.0{% /badge %}
|
||||
The `nft_history` command asks the Clio server for past transaction metadata for the [NFT](../../../../concepts/tokens/nfts/index.md) being queried. {% badge href="https://github.com/XRPLF/clio/releases/tag/2.0.0" %}New in: Clio v2.0.0{% /badge %}
|
||||
|
||||
{% admonition type="info" name="Note" %}`nft_history` returns only _successful_ transactions associated with the NFT.{% /admonition %}
|
||||
|
||||
|
||||
@@ -7,7 +7,7 @@ labels:
|
||||
# AMM
|
||||
[[Source]](https://github.com/XRPLF/rippled/blob/f64cf9187affd69650907d0d92e097eb29693945/include/xrpl/protocol/detail/ledger_entries.macro#L369-L380 "Source")
|
||||
|
||||
An `AMM` ledger entry describes a single [Automated Market Maker](../../../../concepts/tokens/decentralized-exchange/automated-market-makers.md) (AMM) instance. This is always paired with a [special AccountRoot entry](accountroot.md#special-amm-accountroot-entries). You can create an AMM by sending an [AMMCreate transaction][].
|
||||
An `AMM` ledger entry describes a single [Automated Market Maker](../../../../concepts/tokens/decentralized-exchange/automated-market-makers.md) (AMM) instance. This is always paired with a [special AccountRoot entry](accountroot.md#special-amm-accountroot-pseudo-account). You can create an AMM by sending an [AMMCreate transaction][].
|
||||
|
||||
{% amendment-disclaimer name="AMM" /%}
|
||||
|
||||
@@ -65,7 +65,7 @@ In addition to the [common fields](../common-fields.md), {% code-page-name /%} e
|
||||
|:-----------------|:--------------------|:------------------|:----------|--------------|
|
||||
| `Asset` | Object | Issue | Yes | The definition for one of the two assets this AMM holds. In JSON, this is an object with `currency` and `issuer` fields. |
|
||||
| `Asset2` | Object | Issue | Yes | The definition for the other asset this AMM holds. In JSON, this is an object with `currency` and `issuer` fields. |
|
||||
| `Account` | String - [Address][] | AccountID | Yes | The address of the [special account](accountroot.md#special-amm-accountroot-entries) that holds this AMM's assets. |
|
||||
| `Account` | String - [Address][] | AccountID | Yes | The address of the [special account](accountroot.md#special-amm-accountroot-pseudo-account) that holds this AMM's assets. |
|
||||
| `AuctionSlot` | Object | Object | No | Details of the current owner of the auction slot, as an [Auction Slot object](#auction-slot-object). |
|
||||
| `LPTokenBalance` | [Currency Amount][] | Amount | Yes | The total outstanding balance of liquidity provider tokens from this AMM instance. The holders of these tokens can vote on the AMM's trading fee in proportion to their holdings, or redeem the tokens for a share of the AMM's assets which grows with the trading fees collected. |
|
||||
| `PreviousTxnID` | String - [Hash][] | UInt256 | No | The identifying hash of the transaction that most recently modified this entry. {% amendment-disclaimer name="fixPreviousTxnID" /%} |
|
||||
|
||||
@@ -84,10 +84,10 @@ There are no flags defined for {% code-page-name /%} ledger entries.
|
||||
|
||||
## {% $frontmatter.seo.title %} ID Format
|
||||
|
||||
The ID of a `LoanBroker` entry is the [SHA512-Half][] of the following values, concatenated in order:
|
||||
The ID of a `LoanBroker` entry is the [SHA-512Half][] of the following values, concatenated in order:
|
||||
|
||||
- The `LoanBroker` space key `0x006C`.
|
||||
- The [AccountID][] of the account submitting the `LoanBrokerSet` transaction.
|
||||
- The transaction `Sequence` number. If the transaction used a [Ticket][], the `TicketSequence` value is used instead.
|
||||
- The transaction `Sequence` number. If the transaction used a [ticket](/docs/concepts/accounts/tickets.md), the `TicketSequence` value is used instead.
|
||||
|
||||
{% raw-partial file="/docs/_snippets/common-links.md" /%}
|
||||
|
||||
@@ -77,7 +77,7 @@ The ID of an `Oracle` object is the [SHA-512Half][] of the following values, con
|
||||
|
||||
## Currency Internal Format
|
||||
|
||||
The `Currency` field type contains 160 bits of arbitrary data representing a currency or asset code. If the data matches the XRPL's standard format for [currency codes][], the API displays it as a string such as `"USD"`; otherwise, it displays as 40 characters of hexadecimal. The following JSON example represents the `912810RR9/USD` trading pair. The `BaseAsset` is a CUSIP code `912810RR9` represented as a hexadecimal string, and the `QuoteAsset` is a standard `USD` currency code:
|
||||
The `Currency` field type contains 160 bits of arbitrary data representing a currency or asset code. If the data matches the XRPL's standard format for [currency codes][Currency Code], the API displays it as a string such as `"USD"`; otherwise, it displays as 40 characters of hexadecimal. The following JSON example represents the `912810RR9/USD` trading pair. The `BaseAsset` is a CUSIP code `912810RR9` represented as a hexadecimal string, and the `QuoteAsset` is a standard `USD` currency code:
|
||||
|
||||
```json
|
||||
{
|
||||
|
||||
@@ -12,7 +12,7 @@ txIcon: create
|
||||
|
||||
Create a new [Automated Market Maker](../../../../concepts/tokens/decentralized-exchange/automated-market-makers.md) (AMM) instance for trading a pair of assets ([fungible tokens](../../../../concepts/tokens/index.md) or [XRP](../../../../introduction/what-is-xrp.md)).
|
||||
|
||||
Creates both an [AMM entry][] and a [special AccountRoot entry](../../ledger-data/ledger-entry-types/accountroot.md#special-amm-accountroot-entries) to represent the AMM. Also transfers ownership of the starting balance of both assets from the sender to the created `AccountRoot` and issues an initial balance of liquidity provider tokens (LP Tokens) from the AMM account to the sender.
|
||||
Creates both an [AMM entry][] and a [special AccountRoot entry](../../ledger-data/ledger-entry-types/accountroot.md#special-amm-accountroot-pseudo-account) to represent the AMM. Also transfers ownership of the starting balance of both assets from the sender to the created `AccountRoot` and issues an initial balance of liquidity provider tokens (LP Tokens) from the AMM account to the sender.
|
||||
|
||||
{% admonition type="warning" name="Caution" %}When you create the AMM, you should fund it with (approximately) equal-value amounts of each asset. Otherwise, other users can profit at your expense by trading with this AMM ([performing arbitrage](https://www.machow.ski/posts/an_introduction_to_automated_market_makers/#price-arbitrage)). The currency risk that liquidity providers take on increases with the volatility (potential for imbalance) of the asset pair. The higher the trading fee, the more it offsets this risk, so it's best to set the trading fee based on the volatility of the asset pair.{% /admonition %}
|
||||
|
||||
|
||||
@@ -72,7 +72,7 @@ Besides errors that can occur for all transactions, {% $frontmatter.seo.title %}
|
||||
| `tecNO_PERMISSION` | At least one permission in the `Permissions` list is not delegatable. See [Permission Values](../../data-types/permission-values.md) for which permissions are not delegatable. |
|
||||
| `tecNO_TARGET` | The account specified in the `Authorize` field does not exist in the ledger. |
|
||||
| `temARRAY_TOO_LARGE` | The `Permissions` list is too large. It cannot contain more than 10 entries. |
|
||||
| `temDISABLED` | The [Permission Delegation amendment][] is not enabled. |
|
||||
| `temDISABLED` | The [PermissionDelegation amendment][] is not enabled. |
|
||||
| `temMALFORMED` | The transaction was invalid. For example, the `Authorize` account is the same as the sender of the transaction, the `Permissions` list contains duplicate entries, or one of the permissions in the list is not a valid permission. |
|
||||
|
||||
## See Also
|
||||
|
||||
@@ -42,7 +42,7 @@ Create a [permissioned domain][], or modify one that you own.
|
||||
| Field | JSON Type | [Internal Type][] | Required? | Description |
|
||||
|:----------------------|:------------------|:------------------|:----------|:------------|
|
||||
| `DomainID` | String - [Hash][] | UInt256 | No | The ledger entry ID of an existing permissioned domain to modify. If omitted, creates a new permissioned domain. |
|
||||
| `AcceptedCredentials` | Array | Array | Yes | A list of 1 to 10 [**Accepted Credentials objects**](#accepted-credentials-objects) that grant access to this domain. The list does not need to be sorted, but it cannot contain duplicates. When modifying an existing domain, this list replaces the existing list. |
|
||||
| `AcceptedCredentials` | Array | Array | Yes | A list of 1 to 10 [**Accepted Credentials objects**](#acceptedcredentials-objects) that grant access to this domain. The list does not need to be sorted, but it cannot contain duplicates. When modifying an existing domain, this list replaces the existing list. |
|
||||
|
||||
### AcceptedCredentials Objects
|
||||
|
||||
|
||||
@@ -45,9 +45,9 @@ When you're working with the XRP Ledger, there are a few things you'll need to m
|
||||
|
||||
Here are the basic steps you'll need to cover for almost any XRP Ledger project:
|
||||
|
||||
1. [Connect to the XRP Ledger.](#1.-connect-to-the-xrp-ledger)
|
||||
2. [Get an account.](#2.-get-account)
|
||||
3. [Query the XRP Ledger.](#3.-query-the-xrp-ledger)
|
||||
1. [Connect to the XRP Ledger.](#1-connect-to-the-xrp-ledger)
|
||||
2. [Get an account.](#2-get-account)
|
||||
3. [Query the XRP Ledger.](#3-query-the-xrp-ledger)
|
||||
|
||||
### 1. Connect to the XRP Ledger
|
||||
|
||||
|
||||
@@ -105,7 +105,7 @@ With {% amendment-disclaimer name="TokenEscrow" compact=true /%}, escrows can se
|
||||
|
||||
### 6. Display information about the escrows
|
||||
|
||||
Each entry in the list you built earlier should be an [Escrow ledger entry][] sent either to or from the account whose address you specified when looking them up. Use the fields of those objects to display more information about the escrows.
|
||||
Each entry in the list you built earlier should be an [Escrow entry][] sent either to or from the account whose address you specified when looking them up. Use the fields of those objects to display more information about the escrows.
|
||||
|
||||
For the `FinishAfter` (maturity time) and `CancelAfter` (expiration time) fields, compare them to the official close time of the most recently validated ledger to see if the escrow has matured or expired, respectively. These fields are formatted natively as [seconds since the Ripple Epoch][], so be sure to convert them to a more human-readable format for display.
|
||||
|
||||
|
||||
@@ -892,7 +892,7 @@ After finishing this step the application should look like this:
|
||||
|
||||
1. In the project root, create a new folder `bootstrap` and add the following files into that directory:
|
||||
{% repo-link path="_code-samples/build-a-desktop-wallet/js/bootstrap/bootstrap.bundle.min.js" %}`bootstrap.bundle.min.js`{% /repo-link %},
|
||||
{% repo-link path="_code-samples/build-a-desktop-wallet/js/bootstrap/bootstrap.bundle.min.css" %}`bootstrap.min.css`{% /repo-link %},
|
||||
{% repo-link path="_code-samples/build-a-desktop-wallet/js/bootstrap/bootstrap.min.css" %}`bootstrap.min.css`{% /repo-link %},
|
||||
{% repo-link path="_code-samples/build-a-desktop-wallet/js/bootstrap/custom.css" %}`custom.css`{% /repo-link %},
|
||||
{% repo-link path="_code-samples/build-a-desktop-wallet/js/bootstrap/XRPLedger_DevPortal-white.svg" %}`XRPLedger_DevPortal-white.svg`{% /repo-link %}
|
||||
|
||||
|
||||
@@ -43,7 +43,7 @@ To mint a non-fungible token object:
|
||||
1. Click the Account 1 or Account 2 radio button. The account information populates the uneditable fields of the form.
|
||||
2. Set the **Flags** field. For testing purposes, we recommend setting the value to _8_. This sets the _tsTransferable_ flag, meaning that the NFT object can be transferred to another account. Otherwise, the NFT object can only be transferred back to the issuing account.
|
||||
2. Enter the **NFT URL**. This is a URI that points to the data or metadata associated with the NFT object. You can use the sample URI provided if you do not have one of your own.
|
||||
3. Enter the **Transfer Fee**, a percentage of the proceeds from future sales of the NFT that will be returned to the original creator. This is a value of 0-50000 inclusive, allowing transfer rates between 0.000% and 50.000% in increments of 0.001%. If you do not set the **Flags** field to allow the NFT to be transferrable, set this field to 0. If you impose a transfer fee, your NFT can only be traded for tokens for which your account has a trust line. See [Trust Lines](../../../concepts/tokens/fungible-tokens/index.md#trust-lines).
|
||||
3. Enter the **Transfer Fee**, a percentage of the proceeds from future sales of the NFT that will be returned to the original creator. This is a value of 0-50000 inclusive, allowing transfer rates between 0.000% and 50.000% in increments of 0.001%. If you do not set the **Flags** field to allow the NFT to be transferrable, set this field to 0. If you impose a transfer fee, your NFT can only be traded for tokens for which your account has a trust line. See [Trust Line Tokens](../../../concepts/tokens/fungible-tokens/trust-line-tokens.md).
|
||||
4. Enter an **NFT Taxon**. This is a required value, but if you are not using the field to create an integer-based taxon entry, you can set the value to 0.
|
||||
5. (Optional) You can set an expected price for the NFT. To set a price in XRP, enter the amount in drops in the **Amount** field. To use an issued currency, enter the **Currency**, **Issuer**, and **Amount**.
|
||||
6. Optionally, you can enter a **Destination** address that will be the only account authorized to purchase the NFT.
|
||||
|
||||
@@ -52,7 +52,7 @@ Running a permissioned DEX involves several steps:
|
||||
|
||||
1. **[Select a credential issuer.](#select-a-credential-issuer)**
|
||||
2. **[Create a permissioned domain.](#create-a-permissioned-domain)**
|
||||
3. **[Use the domain ID in payments & offers.](#use-the-domain-id-in-payments-and-offers)**
|
||||
3. **[Use the domain ID in payments & offers.](#use-the-permissioned-dex-to-facilitate-payments-and-offers)**
|
||||
|
||||
### Select a credential issuer
|
||||
|
||||
|
||||
@@ -195,10 +195,6 @@ const PaymentsPage: React.FC = () => {
|
||||
{
|
||||
text: "Join the Developer Discord",
|
||||
url: "https://discord.gg/sfX3ERAMjH"
|
||||
},
|
||||
{
|
||||
text: "Sign up for the Newsletter",
|
||||
url: "https://xrplresources.org/subscribe"
|
||||
}
|
||||
],
|
||||
backgroundClass: "learn-stay-updated"
|
||||
|
||||
@@ -466,10 +466,6 @@ export default function RwaTokenization() {
|
||||
text: "Join the Developer Discord",
|
||||
url: "https://discord.gg/sfX3ERAMjH",
|
||||
},
|
||||
{
|
||||
text: "Sign up for the Newsletter",
|
||||
url: "https://xrplresources.org/subscribe",
|
||||
},
|
||||
],
|
||||
backgroundClass: "learn-stay-updated",
|
||||
},
|
||||
|
||||
@@ -128,7 +128,7 @@ Each "trust line" is a bidirectional relationship consisting of:
|
||||
|
||||
Each trust line is specific to a given currency code. Two accounts can have any number of trust lines between them for different currency codes, but only one shared trust line for any particular currency code.
|
||||
|
||||
See [Trust Lines](../../concepts/tokens/fungible-tokens/index.md#trust-lines).
|
||||
See [Trust Line Tokens](../../concepts/tokens/fungible-tokens/trust-line-tokens.md).
|
||||
|
||||
### Authorized Trust Lines
|
||||
|
||||
|
||||
Reference in New Issue
Block a user