mirror of
https://github.com/XRPLF/xrpl-dev-portal.git
synced 2025-11-22 12:45:50 +00:00
Merge pull request #1314 from XRPLF/fix_links_20220207
Fix links (2022-02-09)
This commit is contained in:
Rome Reginelli
@@ -1,18 +1,20 @@
|
||||
|
||||
$(document).ready(()=> {
|
||||
|
||||
|
||||
//top video. Show inline replacing image
|
||||
$("#playvideo").click(function(){
|
||||
$("#playvideo").click(function(event){
|
||||
$("#playvideo").hide();
|
||||
$("#video1").show();
|
||||
$("#video1")[0].src += "?autoplay=1";
|
||||
event.preventDefault()
|
||||
});
|
||||
|
||||
//bottom 3. Show in overlay
|
||||
$('.btn1').click(function() {
|
||||
$('.btn1').click(function(event) {
|
||||
var src = $(this).attr("data-url");
|
||||
$("#player").attr("src", src);
|
||||
$('#video, #video-overlay').fadeIn('slow');
|
||||
event.preventDefault()
|
||||
});
|
||||
|
||||
});
|
||||
|
||||
@@ -85,11 +85,13 @@
|
||||
[{{ledger_entry}} object]: {{ledger_entry|lower}}-object.html
|
||||
{% if target.lang == "ja" %}
|
||||
[{{ledger_entry}}オブジェクト]: {{ledger_entry|lower}}-object.html
|
||||
[{{ledger_entry}} オブジェクト]: {{ledger_entry|lower}}-object.html
|
||||
{% endif %}
|
||||
{% else %}
|
||||
[{{ledger_entry}} object]: {{ledger_entry|lower}}.html
|
||||
{% if target.lang == "ja" %}
|
||||
[{{ledger_entry}}オブジェクト]: {{ledger_entry|lower}}.html
|
||||
[{{ledger_entry}} オブジェクト]: {{ledger_entry|lower}}.html
|
||||
{% endif %}
|
||||
{% endif %}
|
||||
{% endfor %}
|
||||
|
||||
@@ -37,6 +37,7 @@
|
||||
[{{tx}} transactions]: {{tx|lower}}.html
|
||||
{% if target.lang == "ja" %}
|
||||
[{{tx}}トランザクション]: {{tx|lower}}.html
|
||||
[{{tx}} トランザクション]: {{tx|lower}}.html
|
||||
{% endif %}
|
||||
{% endfor %}
|
||||
|
||||
|
||||
@@ -43,7 +43,7 @@ XRP Ledgerは、各トランザクションについて、以下のすべての
|
||||
|
||||
[[ソース]](https://github.com/ripple/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h#L118 "ソース")
|
||||
|
||||
- [XRPは作成されません](#XRPは作成されません)
|
||||
- [XRPは作成されません](#xrpは作成されません)
|
||||
|
||||
[[ソース]](https://github.com/ripple/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h#L146 "ソース")
|
||||
|
||||
@@ -51,7 +51,7 @@ XRP Ledgerは、各トランザクションについて、以下のすべての
|
||||
|
||||
[[ソース]](https://github.com/ripple/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h#L173 "ソース")
|
||||
|
||||
- [XRPの残高確認](#XRPの残高確認)
|
||||
- [XRPの残高確認](#xrpの残高確認)
|
||||
|
||||
[[ソース]](https://github.com/ripple/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h#L197 "ソース")
|
||||
|
||||
@@ -59,7 +59,7 @@ XRP Ledgerは、各トランザクションについて、以下のすべての
|
||||
|
||||
[[ソース]](https://github.com/ripple/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h#L224 "ソース")
|
||||
|
||||
- [XRPのトラストラインはありません](#XRPのトラストラインはありません)
|
||||
- [XRPのトラストラインはありません](#xrpのトラストラインはありません)
|
||||
|
||||
[[ソース]](https://github.com/ripple/rippled/blob/023f5704d07d09e70091f38a0d4e5df213a3144b/src/ripple/app/tx/impl/InvariantCheck.h#L251 "ソース")
|
||||
|
||||
@@ -114,7 +114,7 @@ XRP Ledgerは、各トランザクションについて、以下のすべての
|
||||
### 不正なオファーでない
|
||||
|
||||
- **不変条件:**
|
||||
- [オファー](offer.html#オファー)は負でない金額でなければならず、XRP同士であってはいけません。
|
||||
- [オファー](offer.html)は負でない金額でなければならず、XRP同士であってはいけません。
|
||||
|
||||
|
||||
### 0のエスクローでない
|
||||
@@ -146,7 +146,7 @@ XRP Ledgerは、各トランザクションについて、以下のすべての
|
||||
|
||||
- **その他:**
|
||||
- [Authorized Trust Lines](authorized-trust-lines.html)
|
||||
- [XRPの特性](xrp.html#XRPの特性)
|
||||
- [XRPの特性](xrp.html#xrpの特性)
|
||||
- [トランザクションの残高変化の計算](https://xrpl.org/blog/2015/calculating-balance-changes-for-a-transaction.html#calculating-balance-changes-for-a-transaction)
|
||||
|
||||
|
||||
|
||||
@@ -114,7 +114,7 @@ The XRP Ledger checks all the following invariants on each transaction:
|
||||
### No Bad Offers
|
||||
|
||||
- **Invariant Condition(s):**
|
||||
- [Offers](offer.html#offer) should be for non-negative amounts and must not be XRP to XRP.
|
||||
- [Offers](offer.html) should be for non-negative amounts and must not be XRP to XRP.
|
||||
|
||||
|
||||
### No Zero Escrow
|
||||
|
||||
@@ -9,7 +9,7 @@ labels:
|
||||
|
||||
**XRP**は、XRP Ledgerのネイティブ暗号資産です。XRP Ledgerのすべての[アカウント](accounts.html)間で相互にXRPを送金できます。アカウントは、最小限度額のXRPを[準備金](reserves.html)として保有する必要があります。XRP Ledgerアドレス間にてXRPの直接送金が可能で、ゲートウェイや流動性プロバイダーを必要としません。このため、XRPは便利なブリッジ通貨となりました。
|
||||
|
||||
XRP Ledgerの高度機能の一部（[Escrow](escrow.html)や[Payment Channel](use-payment-channels.html)など）は、XRPでのみ使えます。オーダーブックの[オートブリッジング](https://ripple.com/dev-blog/introducing-offer-autobridging/)は、XRPを使用して、2つの発行済み通貨のオーダーブックをXRPオーダーブックにマージして、合成された一つのオーダーブックを作成することで、分散型取引所の流動性を高めます。（たとえば、オートブリッジングによりUSD:XRPオーダーとXRP:EURオーダーがマッチングされ、USD:EURオーダーブックとなります。）
|
||||
XRP Ledgerの高度機能の一部（[Escrow](escrow.html)や[Payment Channel](use-payment-channels.html)など）は、XRPでのみ使えます。オーダーブックの[オートブリッジング](autobridging.html)は、XRPを使用して、2つの発行済み通貨のオーダーブックをXRPオーダーブックにマージして、合成された一つのオーダーブックを作成することで、分散型取引所の流動性を高めます。（たとえば、オートブリッジングによりUSD:XRPオーダーとXRP:EURオーダーがマッチングされ、USD:EURオーダーブックとなります。）
|
||||
|
||||
XRPはまた、ネットワークのスパムの防御対策としても機能します。すべてのXRP Ledgerアドレスには、XRP Ledger維持管理コストを支払うために少額のXRPが必要です。[トランザクションコスト](transaction-cost.html)と[準備金](reserves.html)は、XRP建ての中立的な手数料であり、どの当事者にも支払われません。レジャーのデータフォーマットで、XRPは[AccountRootオブジェクト](accountroot.html)に保管されます。
|
||||
|
||||
|
||||
@@ -9,7 +9,7 @@ labels:
|
||||
|
||||
**XRP** is the native cryptocurrency of the XRP Ledger. All [accounts](accounts.html) in the XRP Ledger can send XRP among one another and must hold a minimum amount of XRP as a [reserve](reserves.html). XRP can be sent directly from any XRP Ledger address to any other, without needing a gateway or liquidity provider. This helps make XRP a convenient bridge currency.
|
||||
|
||||
Some advanced features of the XRP Ledger, such as [Escrow](escrow.html) and [Payment Channels](use-payment-channels.html), only work with XRP. Order book [auto-bridging](https://xrpl.org/blog/2014/introducing-offer-autobridging.html) uses XRP to deepen liquidity in the decentralized exchange by merging order books of two issued currencies with XRP order books to create synthetic combined order books. (For example, auto-bridging matches USD:XRP and XRP:EUR orders to augment USD:EUR order books.)
|
||||
Some advanced features of the XRP Ledger, such as [Escrow](escrow.html) and [Payment Channels](use-payment-channels.html), only work with XRP. Order book [auto-bridging](autobridging.html) uses XRP to deepen liquidity in the decentralized exchange by merging order books of two issued currencies with XRP order books to create synthetic combined order books. (For example, auto-bridging matches USD:XRP and XRP:EUR orders to augment USD:EUR order books.)
|
||||
|
||||
XRP also serves as a protective measure against spamming the network. All XRP Ledger addresses need a small amount of XRP to offset the costs of maintaining the XRP Ledger. The [transaction cost](transaction-cost.html) and [reserve](reserves.html) are neutral fees denominated in XRP and not paid to any party. In the ledger's data format, XRP is stored in [AccountRoot objects](accountroot.html).
|
||||
|
||||
|
||||
@@ -52,7 +52,7 @@ XRP Ledgerのチケットは、取引をすぐに送信せずに、その取引
|
||||
- 各チケットは一度しか使用できません。同じチケットシーケンスを使用する複数の異なるトランザクション候補があることは可能ですが、コンセンサスで検証できるのはそのうちの1つだけです。
|
||||
- 各アカウントでは、一度に250枚以上のチケットをレジャーに登録することはできません。また、一度に250枚以上のチケットを作成することもできません。
|
||||
- チケットを使って別のチケットを作ることは_できます_。その場合、使用したチケットは、一度に所持できるチケットの合計数にはカウントされません。
|
||||
- 各チケットは[所有者準備金](eserves.html#所有者準備金)にカウントされるため、まだ使用していないチケット1枚につき2XRPを確保する必要があります。このXRPは、チケットを使用した後、再び使用することができます。
|
||||
- 各チケットは[所有者準備金](reserves.html#所有者準備金)にカウントされるため、まだ使用していないチケット1枚につき2XRPを確保する必要があります。このXRPは、チケットを使用した後、再び使用することができます。
|
||||
- 個々の元帳の中では、チケットを使用した取引は、同じ送信者からの他の取引の後に実行されます。1つのアカウントが同じ元帳のバージョンでTicketを使用する複数のトランザクションを持つ場合、それらのTicketは最も低いTicket Sequenceから最も高いTicket Sequenceの順に実行されます。 (詳細については、コンセンサスの[正規順序](consensus.html#xrp-ledgerプロトコル-コンセンサスと検証)に関するドキュメントを参照してください)。
|
||||
- 個々の元帳の中では、チケットを使用した取引は、同じ送信者からの他の取引の後に実行されます。1つのアカウントが同じ元帳のバージョンでチケットを使用する複数のトランザクションを持つ場合、それらのチケットは最も低いチケット シーケンス番号から最も高いチケット シーケンス番号の順に実行されます。 (詳細については、コンセンサスの[正規順序](consensus.html#xrp-ledgerプロトコル-コンセンサスと検証)に関するドキュメントを参照してください)。
|
||||
|
||||
|
||||
@@ -143,6 +143,9 @@ An issuer might issue several NFTs with the same taxon; to ensure that NFTs are
|
||||
|
||||
Notice that the scrambled version of the taxon is `0xBC8B858E`: the scrambled version of the taxon specified by the issuer. But the _actual_ value of the taxon is the unscrambled value.
|
||||
|
||||
### Token Sequence
|
||||
|
||||
The fifth section is a sequence number that increases with each `NFToken` the issuer creates. The [NFTokenMint transaction][] sets this part of the `TokenID` automatically based on the `MintedTokens` field of the `Issuer` account. If the issuer's [AccountRoot object][] does not have a `MintedTokens` field, the field is assumed to have the value 0; the value of the field is then incremented by exactly 1.
|
||||
|
||||
|
||||
## URI
|
||||
|
||||
@@ -9,9 +9,9 @@ status: not_enabled
|
||||
# NFTokenCreateOffer
|
||||
{% include '_snippets/nfts-disclaimer.md' %}
|
||||
|
||||
The `NFTokenCreateOffer` transaction creates either a new _Sell_ offer for an `NFToken` owned by the account executing the transaction, or a new _Buy_ offer for an `NFToken` owned by another account.
|
||||
Creates either a new _Sell_ offer for an `NFToken` owned by the account executing the transaction, or a new _Buy_ offer for an `NFToken` owned by another account.
|
||||
|
||||
Each offer costs one incremental reserve.
|
||||
If successful, the transaction creates a [NFTokenOffer object][]. Each offer counts as one object towards the [owner reserve](reserves.html) of the account that placed the offer.
|
||||
|
||||
## Example {{currentpage.name}} JSON
|
||||
|
||||
@@ -25,161 +25,25 @@ Each offer costs one incremental reserve.
|
||||
}
|
||||
```
|
||||
|
||||
## `NFTokenCreateOffer` Fields
|
||||
|
||||
<table>
|
||||
<tr>
|
||||
<td><strong>Field Name</strong>
|
||||
</td>
|
||||
<td><strong>Required?</strong>
|
||||
</td>
|
||||
<td><strong>JSON Type</strong>
|
||||
</td>
|
||||
<td><strong>Internal Type</strong>
|
||||
</td>
|
||||
<td><strong>Description</strong>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>TransactionType</code>
|
||||
</td>
|
||||
<td>Yes
|
||||
</td>
|
||||
<td>string
|
||||
</td>
|
||||
<td>UInt16
|
||||
</td>
|
||||
<td>Indicates the new transaction type <code>NFTokenCreateOffer</code>. The integer identifier is <code>27</code>.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>Account</code>
|
||||
</td>
|
||||
<td>Yes
|
||||
</td>
|
||||
<td>string
|
||||
</td>
|
||||
<td>AccountID
|
||||
</td>
|
||||
<td>Indicates the <code>AccountID</code> of the account that initiated the transaction.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>Owner</code>
|
||||
</td>
|
||||
<td>No
|
||||
</td>
|
||||
<td>string
|
||||
</td>
|
||||
<td>AccountID
|
||||
</td>
|
||||
<td>Who owns the corresponding <code>NFToken</code>.
|
||||
<ul>
|
||||
{% include '_snippets/tx-fields-intro.md' %}
|
||||
|
||||
<li>
|
||||
If the offer is to buy a token, this field must be present and it must be different than <code>Account</code> (since an offer to buy a token one already holds is meaningless).
|
||||
|
||||
<li>If the offer is to sell a token, this field must not be present, as the owner is, implicitly, the same as <code>Account</code> (since an offer to sell a token one doesn't already hold is meaningless).
|
||||
</li>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>TokenID</code>
|
||||
</td>
|
||||
<td>Yes
|
||||
</td>
|
||||
<td>string
|
||||
</td>
|
||||
<td>Hash256
|
||||
</td>
|
||||
<td>Identifies the <code>TokenID</code> of the <code>NFToken</code> object that the offer references.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>Amount</code>
|
||||
</td>
|
||||
<td>Yes
|
||||
</td>
|
||||
<td>Currency Amount
|
||||
</td>
|
||||
<td>AMOUNT
|
||||
</td>
|
||||
<td>Indicates the amount expected or offered for the <code>Token</code>.
|
||||
<p>
|
||||
The amount must be non-zero, except where this is an offer to sell and the asset is XRP; then, it is legal to specify an amount of zero, which means that the current owner of the token is giving it away, gratis, either to anyone at all, or to the account identified by the <code>Destination</code> field.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>Expiration</code>
|
||||
</td>
|
||||
<td>No
|
||||
</td>
|
||||
<td>number
|
||||
</td>
|
||||
<td>UInt32
|
||||
</td>
|
||||
<td>Indicates the time after which the offer will no longer be valid. The value is the number of seconds since the <a href="https://xrpl.org/basic-data-types.html#specifying-time">Ripple Epoch</a>.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>Destination</code>
|
||||
</td>
|
||||
<td>No
|
||||
</td>
|
||||
<td>string
|
||||
</td>
|
||||
<td>AccountID
|
||||
</td>
|
||||
<td>If present, indicates that this offer may only be accepted by the specified account. Attempts by other accounts to accept this offer MUST fail.
|
||||
<p>
|
||||
If successful, the transaction creates a [NFTokenOffer object][].
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>Flags</code>
|
||||
</td>
|
||||
<td>Yes
|
||||
</td>
|
||||
<td>number
|
||||
</td>
|
||||
<td>UInt32
|
||||
</td>
|
||||
<td>A set of flags that specifies options or controls the behavior of the transaction. The flag is defined in the table below.
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
| Field | JSON Type | [Internal Type][] | Description |
|
||||
|:--------------|:--------------------|:------------------|:-------------------|
|
||||
| `Owner` | String | AccountID | _(Optional)_ Who owns the corresponding `NFToken`. If the offer is to buy a token, this field must be present and it must be different than the `Account` field (since an offer to buy a token one already holds is meaningless). If the offer is to sell a token, this field must not be present, as the owner is, implicitly, the same as the `Account` (since an offer to sell a token one doesn't already hold is meaningless). |
|
||||
| `TokenID` | String | Hash256 | Identifies the `NFToken` object that the offer references. |
|
||||
| `Amount` | [Currency Amount][] | Amount | Indicates the amount expected or offered for the corresponding `NFToken`. The amount must be non-zero, except where this is an offer to sell and the asset is XRP; then, it is legal to specify an amount of zero, which means that the current owner of the token is giving it away, gratis, either to anyone at all, or to the account identified by the `Destination` field. |
|
||||
| `Expiration` | Number | UInt32 | _(Optional)_ Indicates the time after which the offer will no longer be valid. The value is the number of [seconds since the Ripple Epoch][]. |
|
||||
| `Destination` | String | AccountID | _(Optional)_ If present, indicates that this offer may only be accepted by the specified account. Attempts by other accounts to accept this offer MUST fail. |
|
||||
|
||||
|
||||
## NFTokenCreateOffer Flags
|
||||
|
||||
## `NFTokenCreateOffer` Flags
|
||||
|
||||
|
||||
<table>
|
||||
<tr>
|
||||
<td><strong>Flag Name</strong>
|
||||
</td>
|
||||
<td><strong>Flag Value</strong>
|
||||
</td>
|
||||
<td><strong>Description</strong>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>tfSellToken</code>
|
||||
</td>
|
||||
<td><code>0x00000001</code>
|
||||
</td>
|
||||
<td>If set, indicates that the offer is a sell offer. Otherwise, it is a buy offer.
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
|
||||
Note that the `Flags` field includes both transaction-specific and generic flags; all currently valid generics flags (for example, `tfFullyCanonicalSig`) are applicable, but not listed here.
|
||||
|
||||
The transactor does not allow unknown flags to be set.
|
||||
|
||||
Transactions of the NFTokenCreateOffer type support additional values in the [`Flags` field](transaction-common-fields.html#flags-field), as follows:
|
||||
|
||||
| Flag Name | Hex Value | Decimal Value | Description |
|
||||
|:--------------|:-------------|:--------------|:------------------------------|
|
||||
| `tfSellToken` | `0x00000001` | `1` | If enabled, indicates that the offer is a sell offer. Otherwise, it is a buy offer. |
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -7,6 +7,7 @@ labels:
|
||||
status: not_enabled
|
||||
---
|
||||
# NFTokenMint
|
||||
[[Source]](https://github.com/ripple/rippled/blob/xls20/src/ripple/app/tx/impl/NFTokenMint.cpp)
|
||||
{% include '_snippets/nfts-disclaimer.md' %}
|
||||
|
||||
The `NFTokenMint` transaction creates an non-fungible token and adds it to the relevant [NFTokenPage object][] of the `minter` as an [NFToken][] object. A required parameter to this transaction is the `Token` field specifying the actual token. This transaction is the only opportunity the `minter` has to specify any token fields that are defined as immutable (for example, the `TokenFlags`).
|
||||
@@ -43,175 +44,41 @@ If the transaction is successful, the newly minted token is owned by the account
|
||||
This transaction assumes that the issuer, `rNCFjv8Ek5oDrNiMJ3pw6eLLFtMjZLJnf2`, has set the `MintAccount` field in its `AccountRoot` to `rvYAfWj5gh67oV6fW32ZzP3Aw4Eubs59B`, thereby authorizing that account to mint tokens on its behalf.
|
||||
|
||||
|
||||
## **Execution**
|
||||
|
||||
|
||||
In executing, this transaction examines the `MintedTokens` field in the account root of the `Issuer` and uses it to construct the `TokenID` for the token being minted. If the field does not exist, the field is assumed to have the value 0; the value of the field is then incremented by exactly 1.
|
||||
|
||||
{% include '_snippets/tx-fields-intro.md' %}
|
||||
|
||||
<table>
|
||||
<tr>
|
||||
<td>Field Name
|
||||
</td>
|
||||
<td>Required?
|
||||
</td>
|
||||
<td>JSON Type
|
||||
</td>
|
||||
<td>Internal Type
|
||||
</td>
|
||||
<td>Description
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>TransactionType</code>
|
||||
</td>
|
||||
<td>Yes
|
||||
</td>
|
||||
<td><code>string</code>
|
||||
</td>
|
||||
<td><code>UInt16</code>
|
||||
</td>
|
||||
<td>Indicates the new transaction type <code>NFTokenMint</code>. The integer value is <code>25</code>.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>Account</code>
|
||||
</td>
|
||||
<td>Yes
|
||||
</td>
|
||||
<td><code>string</code>
|
||||
</td>
|
||||
<td><code>AccountID</code>
|
||||
</td>
|
||||
<td>Indicates the account that is minting the token. The account MUST <em>either</em>:
|
||||
<ul>
|
||||
|
||||
<li>match the <code>Issuer</code> field in the <code>NFToken</code> object; or
|
||||
|
||||
<li>match the <code>MintAccount</code> field in the <code>AccountRoot</code> of the <code>Issuer</code> field in the <code>NFToken</code> object.
|
||||
</li>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>Issuer</code>
|
||||
</td>
|
||||
<td>No
|
||||
</td>
|
||||
<td><code>string</code>
|
||||
</td>
|
||||
<td><code>AccountID</code>
|
||||
</td>
|
||||
<td>Indicates the account that issues the token. This value is <em>optional</em> and should only be specified if the account executing the transaction is not the <code>Issuer</code> of the <code>NFToken</code> object. If it is present, the <code>MintAccount</code> field in the <code>AccountRoot</code> of the <code>Issuer</code> field must match the <code>Account</code>. Otherwise, the transaction fails.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>TokenTaxon</code>
|
||||
</td>
|
||||
<td>Yes
|
||||
</td>
|
||||
<td><code>number</code>
|
||||
</td>
|
||||
<td><code>UInt32</code>
|
||||
</td>
|
||||
<td>The taxon associated with the token. The taxon is generally a value chosen by the <code>minter</code> of the token. A given taxon can be used for multiple tokens. This implementation reserves all taxon identifiers greater than or equal to <code>0x80000000</code>; attempts to use mint tokens with such taxons should fail and a fee should be claimed.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>TransferFee</code>
|
||||
</td>
|
||||
<td>No
|
||||
</td>
|
||||
<td><code>number</code>
|
||||
</td>
|
||||
<td><code>UInt16</code>
|
||||
</td>
|
||||
<td>The value specifies the fee charged by the issuer for secondary sales of the Token, if such sales are allowed. Valid values for this field are between 0 and 9999 inclusive, allowing transfer rates of between 0.00% and 99.99% in increments of 0.01.
|
||||
<p>
|
||||
The field MUST NOT be present if <code>tfTransferable</code> is not set. If it is, the transaction should fail and the server should claim a fee.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>URI</code>
|
||||
</td>
|
||||
<td>No
|
||||
</td>
|
||||
<td><code>string</code>
|
||||
</td>
|
||||
<td><code>BLOB</code>
|
||||
</td>
|
||||
<td>A URI that points to the data or metadata associated with the NFT. This field need not be an HTTP or HTTPS URL; it could be an IPFS URI, a magnet link, immediate data encoded as an RFC2379 <a href="https://datatracker.ietf.org/doc/html/rfc2397">"data" URL</a>, or even an opaque issuer-specific encoding. The URI is NOT checked for validity, but the field is limited to a maximum length of 256 bytes.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>Flags</code>
|
||||
</td>
|
||||
<td>No
|
||||
</td>
|
||||
<td><code>number</code>
|
||||
</td>
|
||||
<td><code>UInt32</code>
|
||||
</td>
|
||||
<td>Specifies the flags used for the minting transaction. See the mint transaction flags in the following table.
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
| Field | JSON Type | [Internal Type][] | Description |
|
||||
|:--------------|:--------------------|:------------------|:-------------------|
|
||||
| `TokenTaxon` | Number | UInt32 | The taxon associated with the token. The taxon is generally a value chosen by the minter of the token. A given taxon can be used for multiple tokens. Taxon identifiers greater than or equal to `0x80000000` are disallowed. |
|
||||
| `Issuer` | String | AccountID | _(Optional)_ The issuer of the token, if the sender of the account is issuing it on behalf of another account. This field must be omitted if the account sending the transaction is the issuer of the `NFToken`. If provided, the issuer's [AccountRoot object][] must have the `MintAccount` field set to sender of this transaction (this transaction's `Account` field). |
|
||||
| `TransferFee` | Number | UInt16 | _(Optional)_ The value specifies the fee charged by the issuer for secondary sales of the Token, if such sales are allowed. Valid values for this field are between 0 and 9999 inclusive, allowing transfer rates of between 0.00% and 99.99% in increments of 0.01. If this field is provided, the transaction MUST have the [`tfTransferable` flag](#nftokenmint-flags) enabled. |
|
||||
| `URI` | String | Blob | _(Optional)_ A URI that points to the data or metadata associated with the NFT. This field need not be an HTTP or HTTPS URL; it could be an IPFS URI, a magnet link, immediate data encoded as an [RFC2379 "data" URL](https://datatracker.ietf.org/doc/html/rfc2397), or even an issuer-specific encoding. The URI is NOT checked for validity, but the field is limited to a maximum length of 256 bytes.
|
||||
|
||||
|
||||
## NFTokenMint Flags
|
||||
|
||||
Transactions of the NFTokenMint type support additional values in the [`Flags` field](transaction-common-fields.html#flags-field), as follows:
|
||||
|
||||
<table>
|
||||
<tr>
|
||||
<td><strong>Flag Name</strong>
|
||||
</td>
|
||||
<td><strong>Flag Value</strong>
|
||||
</td>
|
||||
<td><strong>Description</strong>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>tfBurnable</code>
|
||||
</td>
|
||||
<td><code>0x00000001</code>
|
||||
</td>
|
||||
<td>If set, indicates that the <code>lsfBurnable</code> flag should be set.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>tfOnlyXRP</code>
|
||||
</td>
|
||||
<td><code>0x00000002</code>
|
||||
</td>
|
||||
<td>If set, indicates that the <code>lsfOnlyXRP</code> flag should be set.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>tfTrustLine</code>
|
||||
</td>
|
||||
<td><code>0x00000004</code>
|
||||
</td>
|
||||
<td>If set, indicates that the <code>lsfTrustLine</code> flag should be set.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>tfTransferable</code>
|
||||
</td>
|
||||
<td><code>0x00000008</code>
|
||||
</td>
|
||||
<td>If set, indicates that the <code>lsfTransferable</code> flag should be set.
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
| Flag Name | Hex Value | Decimal Value | Description |
|
||||
|:--------------|:-------------|:--------------|:------------------------------|
|
||||
| `tfBurnable` | `0x00000001` | 1 | Allow the issuer (or an entity authorized by the issuer) to destroy the minted `NFToken`. (The `NFToken`'s owner can _always_ do so.) |
|
||||
| `tfOnlyXRP` | `0x00000002` | 2 | The minted `NFToken` can only be bought or sold for XRP. This may be desirable if the token has a transfer fee and the issuer does not want to receive fees in non-XRP currencies. |
|
||||
| `tfTrustLine` | `0x00000004` | 4 | Automatically create [trust lines](trust-lines-and-issuing.html) from the issuer to hold transfer fees received from transferring the minted `NFToken`. |
|
||||
| `tfTransferable` | `0x00000008` | 8 | The minted `NFToken` can be transferred to others. If this flag is _not_ enabled, the token can still be transferred _from_ or _to_ the issuer. |
|
||||
|
||||
|
||||
## Embedding additional information
|
||||
|
||||
If you need to specify additional information during minting (for example, details identifying a property by referencing a particular [plat](https://en.wikipedia.org/wiki/Plat), a vehicle by specifying a [VIN](https://en.wikipedia.org/wiki/Vehicle_identification_number), or other object-specific descriptions) you can use the <code>[memo](https://xrpl.org/transaction-common-fields.html#memos-field)</code> functionality already available on the XRP Ledger as a common field. Memos are a part of the signed transaction and are available from historical archives, but are not stored in the ledger.
|
||||
If you need to specify additional information during minting (for example, details identifying a property by referencing a particular [plat](https://en.wikipedia.org/wiki/Plat), a vehicle by specifying a [VIN](https://en.wikipedia.org/wiki/Vehicle_identification_number), or other object-specific descriptions) you can use a [transaction memo](transaction-common-fields.html#memos-field). Memos are a part of the signed transaction and are available from historical archives, but are not stored in the ledger's state data.
|
||||
|
||||
## Error Cases
|
||||
|
||||
- If the `TransferFee` field is not within the acceptable range (0 to 9999 inclusive) the transaction fails with `temBAD_TRANSFER_RATE`.
|
||||
- If the `URI` field is longer than 256 bytes, the transaction fails with `temMALFORMED`.
|
||||
- If the `Issuer` field refers to an account that does not exist, the transaction fails with `tecNO_ISSUER`.
|
||||
- If account referenced by the `Issuer` field has not authorized this transaction's sender (using the `MintAccount` setting) to mint `NFToken`s on their behalf, the transaction fails with `tecNO_PERMISSION`.
|
||||
- If the owner would not meet the updated [reserve requirement](reserves.html) after minting the token, the transaction fails with `tecINSUFFICIENT_RESERVE`. Note that new `NFToken`s only increase the owner's reserve if it requires a new [NFTokenPage object][], which can each hold up to 32 NFTs.
|
||||
- If the `Issuer`'s `MintedTokens` field maxes out, the transaction fails with `tecMAX_SEQUENCE_REACHED`. This is only possible if 2<sup>32</sup>-1 `NFToken`s have been minted in total by the issuer or on their behalf.
|
||||
|
||||
<!--{# common link defs #}-->
|
||||
{% include '_snippets/rippled-api-links.md' %}
|
||||
|
||||
@@ -26,8 +26,6 @@ An OfferCancel transaction removes an Offer object from the XRP Ledger.
|
||||
```
|
||||
|
||||
{% include '_snippets/tx-fields-intro.md' %}
|
||||
<!--{# fix md highlighting_ #}-->
|
||||
|
||||
|
||||
| Field | JSON Type | [Internal Type][] | Description |
|
||||
|:----------------|:----------|:------------------|:-----------------------------|
|
||||
|
||||
@@ -32,7 +32,7 @@ TicketCreateトランザクションは、1つまたは複数の[シーケンス
|
||||
|:-----------------|:-----------------|:------------------|:-------------------|
|
||||
| `TicketCount` | 数値 | UInt32 | 作成するチケットの枚数。これは正の数でなければならず、このトランザクションの実行の結果、アカウントが250枚以上のチケットを所有することはできません。 |
|
||||
|
||||
トランザクションが要求されたチケット_全て_を作成できない場合(250チケットの制限または[所有者準備金](reservices.html)のいずれかが原因)、失敗してチケットは作成されません。アカウントが現在所有しているチケットの数を調べるには、[account_info メソッド][]を使用して、`account_data.TicketCount`フィールドを確認してください。
|
||||
トランザクションが要求されたチケット_全て_を作成できない場合(250チケットの制限または[所有者準備金](reserves.html)のいずれかが原因)、失敗してチケットは作成されません。アカウントが現在所有しているチケットの数を調べるには、[account_info メソッド][]を使用して、`account_data.TicketCount`フィールドを確認してください。
|
||||
|
||||
**ヒント:** このトランザクションは、送信アカウントの[シーケンス番号][Sequence Number]を1 _+_ 作成するチケットの数(`TicketCount`)だけ増加させます。この取引は、アカウントのシーケンス番号を1より多く増加させる唯一の取引です。
|
||||
|
||||
|
||||
@@ -23,7 +23,6 @@ To request the Peer Crawler information, make the following HTTP request:
|
||||
- **Path:** `/crawl`
|
||||
- **Security:** Most `rippled` servers use a self-signed certificate to respond to the request. By default, most tools (including web browsers) flag or block such responses for being untrusted. You must ignore the certificate checking (for example, if using cURL, add the `--insecure` flag) to display a response from those servers.
|
||||
|
||||
**Tip:** Since this request uses the GET method, you can test this request using the URL bar of your web browser. For example, <https://s1.ripple.com:51235/crawl> requests peer crawler information from one of Ripple's public servers. <!-- SPELLING_IGNORE: s1 -->
|
||||
|
||||
## Response Format
|
||||
|
||||
|
||||
@@ -29,7 +29,6 @@ request:
|
||||
|
||||
The validator list contents are signed with a separate cryptographic key, so you can verify their integrity regardless of the TLS certificate used.
|
||||
|
||||
**Tip:** Since this request uses the GET method, you can test this request using the URL bar of your web browser. For example, <https://s1.ripple.com:51235/vl/ED2677ABFFD1B33AC6FBC3062B71F1E8397C1505E1C42C64D11AD1B28FF73F4734> requests Ripple's recommended list from one of Ripple's public servers. <!-- SPELLING_IGNORE: s1 -->
|
||||
|
||||
## Response Format
|
||||
|
||||
|
||||
@@ -49,7 +49,7 @@ XRP Ledgerを使用する際には、XRPを[ウォレット](wallets.html)に追
|
||||
多くのXRP Ledgerプロジェクトで使用している手順をご紹介します。
|
||||
|
||||
1. [ライブラリのインポート](#1-ライブラリのインポート)
|
||||
1. [XRP Ledgerへの接続](#2-xrp-leddgerへの接続)
|
||||
1. [XRP Ledgerへの接続](#2-xrp-ledgerへの接続)
|
||||
1. [ウォレットの作成](#3-ウォレットの作成)
|
||||
1. [XRP Ledgerの参照](#4-xrp-ledgerの参照)
|
||||
1. [イベントのListen](#5-イベントのlisten)
|
||||
|
||||
@@ -167,7 +167,7 @@ Using these building blocks, we can create a simple Python app that:
|
||||
{% include '_code-samples/get-started/py/get-acct-info.py' %}
|
||||
```
|
||||
|
||||
To run the app, you can copy and paste the code into an editor or IDE and run it from there. Or you could download the file from the [XRP Ledger Dev Portal repo](https://github.com/XRPLF/xrpl-dev-portal/tree/master/content/_code-samples/xrpl-py) and run it locally:
|
||||
To run the app, you can copy and paste the code into an editor or IDE and run it from there. Or you could download the file from the [XRP Ledger Dev Portal repo](https://github.com/XRPLF/xrpl-dev-portal/tree/master/content/_code-samples/get-started/py) and run it locally:
|
||||
|
||||
|
||||
```sh
|
||||
|
||||
@@ -11,7 +11,7 @@ labels:
|
||||
|
||||
XRP Ledgerは常にオンラインで、完全に公開されています。このページにあるようなソースコードがあれば、誰でも**ブラウザから直接**アクセスすることができます。
|
||||
|
||||
次の例では、最新の[レジャーバージョン](ledgers.html)と、そのレジャーバージョンで新たに検証されたトランザクションのリストを、[レジャー method][]を使って取得しています。このまま実行してみたり、コードを変更して何が起こるか見てみましょう。
|
||||
次の例では、最新の[レジャーバージョン](ledgers.html)と、そのレジャーバージョンで新たに検証されたトランザクションのリストを、[ledger メソッド][]を使って取得しています。このまま実行してみたり、コードを変更して何が起こるか見てみましょう。
|
||||
|
||||
**ヒント：**可能であれば、**F12**を押して、ブラウザの開発者ツールを開いてください。コンソールタブには、JavaScriptのネイティブコンソールが用意されており、どのウェブページでどのようなコードが実行されているかを知ることができます。 <!-- SPELLING_IGNORE: f12 -->
|
||||
|
||||
|
||||
@@ -235,7 +235,7 @@ _JavaScript_
|
||||
|
||||
チケットの主な使用例としては、複数の[マルチ署名](multi-signing.html)を並行して集めることができます。チケットを使用することで、複数署名されたトランザクションが完全に署名されて準備が整った時点で、どれが先に準備されるかを気にすることなく送信することができます。
|
||||
|
||||
このシナリオでは、[step8,「チケット付きトランザクションの準備」](#8-prepare-ticketed-transaction)が若干異なります。準備と署名を一度に行うのではなく、[任意のマルチ署名トランザクションの送信](send-a-multi-signed-transaction.html)の手順に従うことになります。まずトランザクションを準備し、次に信頼できる署名者の間でトランザクションを循環させて署名を集め、最後に署名を組み合わせて最終的なマルチ署名トランザクションを作成します。
|
||||
このシナリオでは、[step8,「チケット付きトランザクションの準備」](#8-チケット付きトランザクションの準備)が若干異なります。準備と署名を一度に行うのではなく、[任意のマルチ署名トランザクションの送信](send-a-multi-signed-transaction.html)の手順に従うことになります。まずトランザクションを準備し、次に信頼できる署名者の間でトランザクションを循環させて署名を集め、最後に署名を組み合わせて最終的なマルチ署名トランザクションを作成します。
|
||||
|
||||
複数の異なるトランザクションを処理する場合、それぞれが異なるチケットを使用する限り、この作業を並行して行うことができます。
|
||||
|
||||
|
||||
@@ -171,6 +171,16 @@ targets:
|
||||
# the updates to ledger_entry aren't translated either
|
||||
"ledger_entry.html#get-paychannel-object": "ledger_entry.html"
|
||||
"reliable-transaction-submission.html#ledger-gaps": "reliable-transaction-submission.html#レジャーのギャップ"
|
||||
# Fix links from untranslated NFT transaction references:
|
||||
"transaction-common-fields.html#flags-field": "transaction-common-fields.html#flagsフィールド"
|
||||
"transaction-common-fields.html#memos-field": "transaction-common-fields.html#memosフィールド"
|
||||
# Fix links from untranslated Python wallet tutorial:
|
||||
"subscribe.html#transaction-streams": "subscribe.html#トランザクションストリーム"
|
||||
# cryptographic-keys.html hasn't been updated in Japanese, so this is the
|
||||
# next-nearest equivalent of the #seed anchor:
|
||||
"cryptographic-keys.html#seed": "cryptographic-keys.html#キーの生成"
|
||||
"cryptographic-keys.html#regular-key-pair": "cryptographic-keys.html#レギュラーキーペア"
|
||||
|
||||
|
||||
pages:
|
||||
|
||||
@@ -4145,9 +4155,17 @@ known_broken_links:
|
||||
- http://web.archive.org/web/20171211225452/https://forum.ripple.com/viewtopic.php?f=2&t=3613
|
||||
- https://bitcoinexchangeguide.com/cryptographic-puzzle-creator-xrpuzzler-offers-137-xrp-reward-to-anyone-who-can-solve-it/
|
||||
- https://www.coinbase.com/
|
||||
- https://help.coinbase.com/
|
||||
- https://support.uphold.com/hc/en-us/requests/new
|
||||
- https://www.forte.io/
|
||||
- https://www.kraken.com/
|
||||
- https://xrpscan.com/amendments
|
||||
- https://trezor.io/
|
||||
- https://www.lmax.com/
|
||||
- https://www.etoro.com/crypto/exchange/
|
||||
# This site often times out, but it does work and is the original.
|
||||
- https://theworld.com/~reinhold/diceware.html
|
||||
|
||||
|
||||
# Style Checker Config ------------------------------------------------------ #
|
||||
|
||||
|
||||
Binary file not shown.
@@ -20,7 +20,7 @@ msgstr ""
|
||||
|
||||
#: template/component-footer.html.jinja:23
|
||||
msgid "Open Source."
|
||||
msgstr ""
|
||||
msgstr "オープンソース。"
|
||||
|
||||
#: template/component-footer.html.jinja:31
|
||||
msgid "Jump to top of page"
|
||||
@@ -1508,16 +1508,15 @@ msgstr ""
|
||||
|
||||
#: template/page-xrp-overview.html.jinja:38
|
||||
msgid "About XRP"
|
||||
msgstr ""
|
||||
msgstr "XRPについて"
|
||||
|
||||
#: template/page-xrp-overview.html.jinja:39
|
||||
#, fuzzy
|
||||
msgid "#xrp-trading"
|
||||
msgstr "取引"
|
||||
msgstr "#xrp-trading"
|
||||
|
||||
#: template/page-xrp-overview.html.jinja:40
|
||||
msgid "XRP in Trading"
|
||||
msgstr ""
|
||||
msgstr "XRPの取引"
|
||||
|
||||
#: template/page-xrp-overview.html.jinja:41
|
||||
msgid "#ripple"
|
||||
@@ -1528,18 +1527,16 @@ msgid "Ripple vs. XRP"
|
||||
msgstr "RippleとXRPの違い"
|
||||
|
||||
#: template/page-xrp-overview.html.jinja:43
|
||||
#, fuzzy
|
||||
msgid "#wallets"
|
||||
msgstr "ウォレット"
|
||||
msgstr "#wallets"
|
||||
|
||||
#: template/page-xrp-overview.html.jinja:44
|
||||
msgid "XRP Wallets"
|
||||
msgstr "XRPウォレット"
|
||||
|
||||
#: template/page-xrp-overview.html.jinja:45
|
||||
#, fuzzy
|
||||
msgid "#exchanges"
|
||||
msgstr "取引所"
|
||||
msgstr "#exchanges"
|
||||
|
||||
#: template/page-xrp-overview.html.jinja:46
|
||||
msgid "XRP Exchanges"
|
||||
|
||||
@@ -21,7 +21,7 @@
|
||||
|
||||
{% block main %}
|
||||
<div class="overflow-hidden">
|
||||
|
||||
|
||||
<div id="video-overlay"></div>
|
||||
<div id="video">
|
||||
<div id="videoWrapper">
|
||||
@@ -56,17 +56,17 @@
|
||||
<h5 class="longform mb-10">{% trans %}The XRP Ledger is a decentralized public blockchain. {% endtrans %}</h5>
|
||||
<p class="mb-4">{% trans %}Anyone can connect their computer to the peer-to-peer network that manages the ledger. The global XRP Ledger community—a diverse set of software engineers, server operators, users, and businesses—maintains the ledger.{% endtrans %}</p>
|
||||
<div class="d-none d-lg-block">
|
||||
<a class="btn btn-primary btn-arrow" href="docs.html">{% trans %}Read Technical Docs{% endtrans %}</a> <a class="ml-4 video-external-link" target="_blank" href="https://www.youtube.com/playlist?list=PLJQ55Tj1hIVZtJ_JdTvSum2qMTsedWkNi">{% trans %}Watch Explainer Videos {% endtrans %}</a>
|
||||
<a class="btn btn-primary btn-arrow" href="docs.html">{% trans %}Read Technical Docs{% endtrans %}</a> <a class="ml-4 video-external-link" target="_blank" href="https://www.youtube.com/playlist?list=PLJQ55Tj1hIVZtJ_JdTvSum2qMTsedWkNi">{% trans %}Watch Explainer Videos {% endtrans %}</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="col">
|
||||
<iframe id="video1" style="display:none;" width="560" height="315" src="https://www.youtube.com/embed/sVTybJ3cNyo" title="Intro to the XRP Ledger" frameborder="0" allow="accelerometer; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
|
||||
<a href="#/" id="playvideo">
|
||||
<a href="#" id="playvideo">
|
||||
<img src="./assets/img/overview/video_explainer_intro@2x.png" id="xrpl-overview-video-intro" class="w-100 video-image">
|
||||
</a>
|
||||
|
||||
<div class="text-center d-lg-none">
|
||||
<a class="btn btn-primary btn-arrow mt-5 mb-4" href="docs.html">{% trans %}Read Technical Docs{% endtrans %}</a> <a class="ml-4 video-external-link" target="_blank" href="https://www.youtube.com/playlist?list=PLJQ55Tj1hIVZtJ_JdTvSum2qMTsedWkNi">{% trans %}Watch Explainer Videos {% endtrans %}</a>
|
||||
<a class="btn btn-primary btn-arrow mt-5 mb-4" href="docs.html">{% trans %}Read Technical Docs{% endtrans %}</a> <a class="ml-4 video-external-link" target="_blank" href="https://www.youtube.com/playlist?list=PLJQ55Tj1hIVZtJ_JdTvSum2qMTsedWkNi">{% trans %}Watch Explainer Videos {% endtrans %}</a>
|
||||
</div>
|
||||
|
||||
</div>
|
||||
@@ -131,27 +131,27 @@
|
||||
|
||||
<div class="row row-cols-1 row-cols-lg-3 d-flex justify-content-between w-100 mx-0 mx-md-n3 mt-md-5">
|
||||
<div class="px-md-3 pt-5 pt-md-0">
|
||||
<a href="#/" class="btn1" data-url="https://www.youtube.com/embed/k6VqEkqRTmk?rel=0&showinfo=0&autoplay=1">
|
||||
<a href="#" class="btn1" data-url="https://www.youtube.com/embed/k6VqEkqRTmk?rel=0&showinfo=0&autoplay=1">
|
||||
<img src="./assets/img/overview/video_explainer_consensus@2x.png" id="xrpl-overview-video-consensus" class="w-100 video-image">
|
||||
</a>
|
||||
<div class="mt-2">
|
||||
<h4 class="video-title mt-3 mb-0">{% trans %}The Consensus Mechanism{% endtrans %}</h4>
|
||||
<h4 class="video-title mt-3 mb-0">{% trans %}The Consensus Mechanism{% endtrans %}</h4>
|
||||
</div>
|
||||
</div>
|
||||
<div class="px-md-3 pt-5 pt-md-0">
|
||||
<a href="#/" class="btn1" data-url="https://www.youtube.com/embed/JjaVDXPqnbA?rel=0&showinfo=0&autoplay=1">
|
||||
<a href="#" class="btn1" data-url="https://www.youtube.com/embed/JjaVDXPqnbA?rel=0&showinfo=0&autoplay=1">
|
||||
<img src="./assets/img/overview/video_explainer_nodes@2x.png" id="xrpl-overview-video-nodes" class="w-100 video-image">
|
||||
</a>
|
||||
<div class="mt-2">
|
||||
<h4 class="video-title mt-3 mb-0">{% trans %}Nodes and Validators{% endtrans %}</h4>
|
||||
<h4 class="video-title mt-3 mb-0">{% trans %}Nodes and Validators{% endtrans %}</h4>
|
||||
</div>
|
||||
</div>
|
||||
<div class="px-md-3 pt-5 pt-md-0">
|
||||
<a href="#/" class="btn1" data-url="https://www.youtube.com/embed/WsmldDNGQ9s?rel=0&showinfo=0&autoplay=1">
|
||||
<a href="#" class="btn1" data-url="https://www.youtube.com/embed/WsmldDNGQ9s?rel=0&showinfo=0&autoplay=1">
|
||||
<img src="./assets/img/overview/video_explainer_sustainability@2x.png" id="xrpl-overview-video-sustainability" class="w-100 video-image">
|
||||
</a>
|
||||
<div class="mt-2">
|
||||
<h4 class="video-title mt-3 mb-0">{% trans %}Sustainability of the XRP Ledger{% endtrans %}</h4>
|
||||
<h4 class="video-title mt-3 mb-0">{% trans %}Sustainability of the XRP Ledger{% endtrans %}</h4>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
Reference in New Issue
Block a user