Migrate content syntax via script

The changes in this commit were auto-generated by running

tool/migrate.sh

Following this commit, the Dactyl build no longer works but the Redocly
build (mostly) should.
This commit is contained in:
mDuo13
2024-01-31 16:09:41 -08:00
parent 96121303b2
commit 554a3732d4
898 changed files with 19879 additions and 18631 deletions

View File

@@ -1,8 +1,12 @@
---
html: use-xrpl-sidechains.html
parent: tasks.html
template: pagetype-category.html.jinja
metadata:
indexPage: true
---
# Use XRPL Sidechains
Bridge XRP and tokens from _Mainnet_ to XRPL sidechains.
Bridge XRP and tokens from _Mainnet_ to XRPL sidechains.
{% child-pages /%}

View File

@@ -7,17 +7,17 @@ labels:
---
# Set Up an IOU-IOU Bridge
_(Requires the [XChainBridge amendment][] :not_enabled:)_
_(Requires the [XChainBridge amendment][] {% not-enabled /%})_
Setting up an IOU-IOU bridge enables you to move tokens between chains.
**Note**: The code samples on this page illustrate how to bridge a hypotethical "TST" token from *Devnet* to *Sidechain-Devnet*, using a supported [client library](client-libraries.html) to query and submit transactions.
**Note**: The code samples on this page illustrate how to bridge a hypotethical "TST" token from *Devnet* to *Sidechain-Devnet*, using a supported [client library](../../../references/client-libraries.md) to query and submit transactions.
## Prerequisites
- An XRP-XRP bridge must be set up between the locking and issuing chain.
- Ensure the witnesses' transaction submission accounts are funded on the locking and issuing chains.
- Set up an issuer on the issuing chain to mint and burn a wrapped version of the token you want to bridge. See: [Issue a Fungible Token](issue-a-fungible-token.html)
- Set up an issuer on the issuing chain to mint and burn a wrapped version of the token you want to bridge. See: [Issue a Fungible Token](../../use-tokens/issue-a-fungible-token.md)
## Steps
@@ -161,8 +161,4 @@ const disablekey_issuingchain = await client_issuingchain.submitAndWait({
}, {autofill: true, wallet: wallet_issuingchain})
```
<!--{# common link defs #}-->
{% include '_snippets/rippled-api-links.md' %}
{% include '_snippets/tx-type-links.md' %}
{% include '_snippets/rippled_versions.md' %}
{% raw-partial file="/_snippets/common-links.md" /%}

View File

@@ -7,11 +7,11 @@ labels:
---
# Set Up an XRP-XRP Bridge
_(Requires the [XChainBridge amendment][] :not_enabled:)_
_(Requires the [XChainBridge amendment][] {% not-enabled /%})_
Setting up an XRP-XRP bridge enables you to move XRP between chains. The set up requires using the genesis account on the issuing chain as a door account to submit attestations and create transaction submission accounts for witnesses.
**Note**: The code samples on this page illustrate how a bridge was set up between *Devnet* and *Sidechain-Devnet*, using a supported [client library](client-libraries.html) to query and submit transactions. This bridge is already created, so the process can't be reproduced on these networks.
**Note**: The code samples on this page illustrate how a bridge was set up between *Devnet* and *Sidechain-Devnet*, using a supported [client library](../../../references/client-libraries.md) to query and submit transactions. This bridge is already created, so the process can't be reproduced on these networks.
## Prerequisites
@@ -228,7 +228,4 @@ const disablekey_issuingchain = await client_issuingchain.submitAndWait({
}, {autofill: true, wallet: wallet_issuingchain})
```
<!--{# common link defs #}-->
{% include '_snippets/rippled-api-links.md' %}
{% include '_snippets/tx-type-links.md' %}
{% include '_snippets/rippled_versions.md' %}
{% raw-partial file="/_snippets/common-links.md" /%}

View File

@@ -7,9 +7,9 @@ labels:
---
# Submit Cross-chain Transactions
_(Requires the [XChainBridge amendment][] :not_enabled:)_
_(Requires the [XChainBridge amendment][] {% not-enabled /%})_
This tutorial explains how to create a test account on a locking chain (_Devent_), and transfer XRP to an issuing chain (_Sidechain-Devnet_), using a supported [client library](client-libraries.html) to query and submit transactions. Witness servers are already set up to monitor the XRP-XRP bridge and submit attestations.
This tutorial explains how to create a test account on a locking chain (_Devent_), and transfer XRP to an issuing chain (_Sidechain-Devnet_), using a supported [client library](../../../references/client-libraries.md) to query and submit transactions. Witness servers are already set up to monitor the XRP-XRP bridge and submit attestations.
## Prerequisites
@@ -129,8 +129,4 @@ If you don't specify an "OtherChainDestination", the account that submitted the
**Note:** When enough `XChainAddClaimAttestation` signatures are submitted by the witness servers to reach quorum, the funds are released on the issuing chain to the `OtherChainDestination`.
<!--{# common link defs #}-->
{% include '_snippets/rippled-api-links.md' %}
{% include '_snippets/tx-type-links.md' %}
{% include '_snippets/rippled_versions.md' %}
{% raw-partial file="/_snippets/common-links.md" /%}