Tokens renaming: more fixes

This commit is contained in:
mDuo13
2022-02-16 19:18:53 -08:00
parent ca80f66efe
commit a01585becd
15 changed files with 31 additions and 26 deletions

View File

@@ -53,7 +53,7 @@
<w>410</w>
<h>30</h>
</coordinates>
<panel_attributes>mantissa (54 bits)</panel_attributes>
<panel_attributes>significant digits (54 bits)</panel_attributes>
<additional_attributes/>
</element>
<element>
@@ -157,7 +157,7 @@ style=wordwrap</panel_attributes>
<w>650</w>
<h>70</h>
</coordinates>
<panel_attributes>Issued Currency Number Format</panel_attributes>
<panel_attributes>Token Number Format</panel_attributes>
<additional_attributes/>
</element>
<element>

View File

@@ -42,7 +42,7 @@
<w>190</w>
<h>30</h>
</coordinates>
<panel_attributes>mantissa (54 bits)</panel_attributes>
<panel_attributes>significant digits (54 bits)</panel_attributes>
<additional_attributes/>
</element>
<element>
@@ -335,7 +335,7 @@ style=wordwrap</panel_attributes>
<w>240</w>
<h>30</h>
</coordinates>
<panel_attributes>Issued Currency Amount Format</panel_attributes>
<panel_attributes>Token Amount Format</panel_attributes>
<additional_attributes/>
</element>
<element>
@@ -357,7 +357,7 @@ style=wordwrap</panel_attributes>
<w>240</w>
<h>30</h>
</coordinates>
<panel_attributes>Issued Currency Code Format</panel_attributes>
<panel_attributes>Standard Currency Code Format</panel_attributes>
<additional_attributes/>
</element>
<element>

View File

@@ -183,6 +183,7 @@
<!--{# Amendment links #}-->
{% set amendment_names = [
"Checks",
"CheckCashMakesTrustLine",
"CryptoConditions",
"CryptoConditionsSuite",
"DeletableAccounts",

View File

@@ -36,7 +36,7 @@ For more information, see [Auto-Bridging](autobridging.html).
- [Payment transaction type][Payment transaction]
- [path_find method][]
- [ripple_path_find method][]
- [Interpreting Metadata of Issued Currency Payments](look-up-transaction-results.html#issued-currency-payments)
- [Interpreting Metadata of Cross-Currency Payments](look-up-transaction-results.html#token-payments)
<!--{# common link defs #}-->
{% include '_snippets/rippled-api-links.md' %}

View File

@@ -41,7 +41,7 @@ To convert between display amounts and ledger amounts, you can use the following
2. Apply it to the amount to convert:
- To convert ledger values to display values, multiply by the demurrage coefficient.
- To convert display values to ledger values, divide by the demurrage coefficient.
3. If necessary, adjust the resulting value so that it can be represented to the desired accuracy. Ledger values are limited to 15 decimal digits of precision, according to the XRP Ledger's [token format](currency-formats.html#issued-currency-precision).
3. If necessary, adjust the resulting value so that it can be represented to the desired accuracy. Ledger values are limited to 15 decimal digits of precision, according to the XRP Ledger's [token format](currency-formats.html#token-precision).
## Interest-Bearing Currency Code Format

View File

@@ -8,7 +8,7 @@ labels:
---
# パス
XRP Ledgerでは、[発行済み通貨](issued-currencies-overview.html)の支払いが送金元から受取人に届くまでにたどる中間ステップの道筋をパスによって定義します。パスは、XRP Ledgerの[分散型取引所](decentralized-exchange.html)のオーダーを介して送金元と受取人を結び付けることで、[複数通貨間の支払い](cross-currency-payments.html)を可能にします。また、負債を相殺するような複雑な決済もパスにより可能になります。
XRP Ledgerでは、[発行済み通貨](tokens.html)の支払いが送金元から受取人に届くまでにたどる中間ステップの道筋をパスによって定義します。パスは、XRP Ledgerの[分散型取引所](decentralized-exchange.html)のオーダーを介して送金元と受取人を結び付けることで、[複数通貨間の支払い](cross-currency-payments.html)を可能にします。また、負債を相殺するような複雑な決済もパスにより可能になります。
XRP Ledgerでは1つのPaymentトランザクションは複数のパスを使用でき、複数のソースの流動性を組み合わせて必要な額を送金することができます。そのため、トランザクションには使用可能なパスをまとめた _パスセット_ が含まれます。パスセットの中のパスでは開始時と終了時には同一通貨が使用される必要があります。

View File

@@ -1,5 +1,6 @@
---
parent: concepts.html
html: tokens.html
blurb: 発行済み通貨の概要と、XRP Ledgerにおけるその特性について説明します。
labels:
- トークン

View File

@@ -6,7 +6,7 @@ labels:
---
# Tokens
All assets other than XRP can be represented in the XRP Ledger as **tokens**. Standard tokens are tracked in relationships called [trust lines](trust-lines-and-issuing) between accounts. Any account can issue tokens to other recipients who are willing to hold them, but you cannot unilaterally give tokens away to users who don't want them. Tokens can represent any type of value, including "stablecoins" backed by assets that exist outside of the ledger, purely digital tokens created specifically on the XRP Ledger, community credit, and more.
All assets other than XRP can be represented in the XRP Ledger as **tokens**. Standard tokens are tracked in relationships called [trust lines](trust-lines-and-issuing.html) between accounts. Any account can issue tokens to other recipients who are willing to hold them, but you cannot unilaterally give tokens away to users who don't want them. Tokens can represent any type of value, including "stablecoins" backed by assets that exist outside of the ledger, purely digital tokens created specifically on the XRP Ledger, community credit, and more.
Standard tokens are fungible: meaning, all units of that token are interchangeable and indistinguishable. Non-fungible tokens are also possible: see [Non-Fungible Tokens](non-fungible-tokens.html) :not_enabled: for details of the XRP Ledger's native support.

View File

@@ -13,7 +13,7 @@ Each "trust line" is a _bidirectional_ relationship consisting of:
- The identifiers for the **two [accounts](accounts.html)** that the trust line connects.
- A single, shared **balance**, which is positive from the perspective of one account and negative from the other perspective.
- The account with a negative balance is generally considered the "issuer" of the tokens. However, in the [APIs](rippled-apis.html), the name `issuer` can refer to either side.
- The account with a negative balance is generally considered the "issuer" of the tokens. However, in the [APIs](rippled-api.html), the name `issuer` can refer to either side.
- Various **settings** and metadata. _Each_ of the two accounts can control its own settings on the trust line.
- Most importantly, each side sets a **limit** on the trust line, which is 0 by default. Each account's balance (from its perspective on the trust line) can't go above that account's limit, except [through that account's own actions](#going-below-the-limit).
@@ -43,7 +43,7 @@ In addition to the shared balance, each account has its own settings on the trus
- The **Limit**, a number from 0 to the [maximum token amount](currency-formats.html). Payments and other accounts' actions cannot cause the trust line's balance (from this account's perspective) to go over the limit. The default is `0`.
- **Authorized**: A true/false value used with [Authorized Trust Lines](authorized-trust-lines.html) to allow the other side to hold tokens this account issues. The default is `false`. Once set to `true`, this cannot be changed back.
- **No Ripple**: A true/false value to control whether tokens can [ripple](rippling.html) through this trust line. The default depends on the account's "Default Ripple" setting; for new accounts, "Default Ripple" is off which means that `true` is the default for No Ripple. Usually, issuers should allow rippling and non-issuers should disable rippling unless they are using trust lines for community credit.
- **Freeze**: A true/false value indicating whether an [individual freeze](freezes.html#individual freeze) is in effect on this trust line. The default is `false`.
- **Freeze**: A true/false value indicating whether an [individual freeze](freezes.html#individual-freeze) is in effect on this trust line. The default is `false`.
- **Quality In** and **Quality Out** settings, which allow the account to value tokens issued by the other account on this trust line at less (or more) than face value. For example, if a stablecoin issuer charges a 3% fee for withdrawing tokens for the equivalent off-ledger assets, you could use these settings to value those tokens at 97% of face value. The default, `0`, represents face value.

View File

@@ -224,7 +224,7 @@ The "Amount" type is a special field type that represents an amount of currency,
Tokens consist of three segments in order:
1. 64 bits indicating the amount in the [internal currency amount format](#issued-currency-amount-format). The first bit is `1` to indicate that this is not XRP.
1. 64 bits indicating the amount in the [token amount format](#token-amount-format). The first bit is `1` to indicate that this is not XRP.
2. 160 bits indicating the [currency code](currency-formats.html#currency-codes). The standard API converts 3-character codes such as "USD" into 160-bit codes using the [standard currency code format](currency-formats.html#standard-currency-codes), but custom 160-bit codes are also possible.
3. 160 bits indicating the issuer's Account ID. (See also: [Account Address Encoding](accounts.html#address-encoding))
@@ -232,7 +232,7 @@ You can tell which of the two sub-types it is based on the first bit: `0` for XR
The following diagram shows the serialization formats for both XRP amounts and token amounts:
{{ include_svg("img/serialization-amount.svg", 'XRP amounts have a "not XRP" bit, a sign bit, and 62 bits of precision. Token amounts consist of a "not XRP" bit, a sign bit, an exponent (8 bits), mantissa (54 bits), currency code (160 bits), and issuer (160 bits).') }}
{{ include_svg("img/serialization-amount.svg", 'XRP amounts have a "not XRP" bit, a sign bit, and 62 bits of precision. Token amounts consist of a "not XRP" bit, a sign bit, an exponent (8 bits), significant digits (54 bits), currency code (160 bits), and issuer (160 bits).') }}
#### Token Amount Format
[[Source]](https://github.com/ripple/rippled/blob/35fa20a110e3d43ffc1e9e664fc9017b6f2747ae/src/ripple/protocol/impl/STAmount.cpp "Source")
@@ -244,7 +244,7 @@ The XRP Ledger uses 64 bits to serialize the numeric amount of a (fungible) toke
1. The first (most significant) bit for an token amount is `1` to indicate that it is not an XRP amount. (XRP amounts always have the most significant bit set to `0` to distinguish them from this format.)
2. The sign bit indicates whether the amount is positive or negative. Unlike standard [two's complement](https://en.wikipedia.org/wiki/Two%27s_complement) integers, `1` indicates **positive** in the XRP Ledger format, and `0` indicates negative.
3. The next 8 bits represent the exponent as an unsigned integer. The exponent indicates the scale (what power of 10 the significant digits should be multiplied by) in the range -96 to +80 (inclusive). However, when serializing, we add 97 to the exponent to make it possible to serialize as an unsigned integer. Thus, a serialized value of `1` indicates an exponent of `-96`, a serialized value of `177` indicates an exponent of 80, and so on.
4. The remaining 54 bits represent the significant digits as an unsigned integer. When serializing, this value is normalized to the range 10<sup>15</sup> (`1000000000000000`) to 10<sup>16</sup>-1 (`9999999999999999`) inclusive, except for the special case of the value 0. In the special case for 0, the sign bit, exponent, and mantissa are all zeroes, so the 64-bit value is serialized as `0x8000000000000000000000000000000000000000`.
4. The remaining 54 bits represent the significant digits (sometimes called a _mantissa_) as an unsigned integer. When serializing, this value is normalized to the range 10<sup>15</sup> (`1000000000000000`) to 10<sup>16</sup>-1 (`9999999999999999`) inclusive, except for the special case of the value 0. In the special case for 0, the sign bit, exponent, and significant digits are all zeroes, so the 64-bit value is serialized as `0x8000000000000000000000000000000000000000`.
The numeric amount is serialized alongside the [currency code][] and issuer to form a full [token amount](#amount-fields).

View File

@@ -95,8 +95,8 @@ Each member of the `books` array, if provided, is an object with the following f
| `Field` | Type | Description |
|:-------------|:--------|:----------------------------------------------------|
| `taker_gets` | Object | Specification of which currency the account taking the Offer would receive, as a [currency object with no amount](currency-formats.html#specifying-currencies-without-amounts). |
| `taker_pays` | Object | Specification of which currency the account taking the Offer would pay, as a [currency object with no amount](currency-formats.html#specifying-currencies-without-amounts). |
| `taker_gets` | Object | Specification of which currency the account taking the Offer would receive, as a [currency object with no amount](currency-formats.html#specifying-without-amounts). |
| `taker_pays` | Object | Specification of which currency the account taking the Offer would pay, as a [currency object with no amount](currency-formats.html#specifying-without-amounts). |
| `taker` | String | Unique [account address](accounts.html) to use as a perspective for viewing offers, in the XRP Ledger's [base58][] format. (This affects the funding status and fees of [Offers](offers.html).) |
| `snapshot` | Boolean | _(Optional)_ If `true`, return the current state of the order book once when you subscribe before sending updates. The default is `false`. |
| `both` | Boolean | _(Optional)_ If `true`, return both sides of the order book. The default is `false`. |

View File

@@ -180,6 +180,9 @@ targets:
# next-nearest equivalent of the #seed anchor:
"cryptographic-keys.html#seed": "cryptographic-keys.html#キーの生成"
"cryptographic-keys.html#regular-key-pair": "cryptographic-keys.html#レギュラーキーペア"
# Fix links from untranslated common-misconceptions-about-freezes.html
# Not updated to have the table. The top-level of the page is pretty close.
"currency-formats.html#comparison": "currency-formats.html"
pages:

View File

@@ -67,7 +67,7 @@
><path fill="none" d="M0.5 0.5 L260.5 0.5 L260.5 21.6094 L649 21.6094 L649 69 L0.5 69 Z" clip-path="url(#clipPath4)"
/><path fill="none" d="M0.5 21.6094 L260.5 21.6094" clip-path="url(#clipPath4)"
/><text x="5" font-size="14px" y="16.1094" clip-path="url(#clipPath4)" font-family="sans-serif" stroke="none" xml:space="preserve"
>Issued Currency Number Format</text
>Token Number Format</text
></g
><g font-family="sans-serif" font-size="14px" transform="translate(530,110)"
><text x="5" xml:space="preserve" y="18.1094" clip-path="url(#clipPath5)" stroke="none"
@@ -96,8 +96,8 @@
/></g
><g transform="translate(250,50)"
><rect fill="none" x="0.5" width="408.5" height="28.5" y="0.5" clip-path="url(#clipPath8)"
/><text x="141" font-size="14px" y="18.1094" clip-path="url(#clipPath8)" font-family="sans-serif" stroke="none" xml:space="preserve"
>mantissa (54 bits)</text
/><text x="115" font-size="14px" y="18.1094" clip-path="url(#clipPath8)" font-family="sans-serif" stroke="none" xml:space="preserve"
>significant digits (54 bits)</text
></g
><g fill="rgb(255,255,255)" fill-opacity="0" transform="translate(90,50)" stroke-opacity="0" stroke="rgb(255,255,255)"
><rect x="0.5" width="148.5" height="28.5" y="0.5" clip-path="url(#clipPath9)" stroke="none"

Before

Width:  |  Height:  |  Size: 9.7 KiB

After

Width:  |  Height:  |  Size: 9.7 KiB

View File

@@ -80,7 +80,7 @@
/></g
><g font-family="sans-serif" font-size="14px" transform="translate(90,470)"
><text x="5" xml:space="preserve" y="18.1094" clip-path="url(#clipPath3)" stroke="none"
>Issued Currency Code Format</text
>Standard Currency Code Format</text
></g
><g fill="rgb(255,255,255)" fill-opacity="0" transform="translate(30,260)" stroke-opacity="0" stroke="rgb(255,255,255)"
><rect x="0.5" width="848.5" height="48.5" y="0.5" clip-path="url(#clipPath4)" stroke="none"
@@ -90,7 +90,7 @@
/></g
><g font-family="sans-serif" font-size="14px" transform="translate(30,230)"
><text x="5" xml:space="preserve" y="18.1094" clip-path="url(#clipPath3)" stroke="none"
>Issued Currency Amount Format</text
>Token Amount Format</text
></g
><g font-family="sans-serif" font-size="14px" transform="translate(30,20)"
><text x="5" xml:space="preserve" y="18.1094" clip-path="url(#clipPath5)" stroke="none"
@@ -209,8 +209,8 @@
/></g
><g transform="translate(260,270)"
><rect fill="none" x="0.5" width="188.5" height="28.5" y="0.5" clip-path="url(#clipPath16)"
/><text x="31" font-size="14px" y="18.1094" clip-path="url(#clipPath16)" font-family="sans-serif" stroke="none" xml:space="preserve"
>mantissa (54 bits)</text
/><text x="5" font-size="14px" y="18.1094" clip-path="url(#clipPath16)" font-family="sans-serif" stroke="none" xml:space="preserve"
>significant digits (54 bits)</text
></g
><g fill="rgb(255,255,255)" fill-opacity="0" transform="translate(100,270)" stroke-opacity="0" stroke="rgb(255,255,255)"
><rect x="0.5" width="148.5" height="28.5" y="0.5" clip-path="url(#clipPath11)" stroke="none"

Before

Width:  |  Height:  |  Size: 16 KiB

After

Width:  |  Height:  |  Size: 16 KiB

View File

@@ -99,9 +99,9 @@
{ "href": "multi-signing.html",
"title": _("Multi-Signing"),
"description": _("Flexible options for custody and security of on-ledger accounts")},
{ "href": "issued-currencies-overview.html",
"title": _("Issued Currencies"),
"description": _("All currencies other than XRP can be represented in the XRP Ledger as issued currencies, sometimes called “IOUs”")},
{ "href": "tokens.html",
"title": _("Tokens"),
"description": _("All currencies other than XRP can be represented in the XRP Ledger as tokens, sometimes called “IOUs”")},
] %}
{% for card in cards2 %}