Remove in-development docs for sidechains and EVM sidechains (#1863)

* Remove in-development docs for EVM sidechain and now obsolete content for federated sidechains dev preview

* Remove disclaimer note about EVM sidechain

* Remove references to sidechains which are in development

* Add redirects to deleted pages

* Incorporate feedback to comment out Issue Fields

* Fix broken links

content/_snippets/evmsc-disclaimer.ja.md

@@ -1 +0,0 @@
-_EVM互換サイドチェーンの実装 :not_enabled: は、XRP Ledgerプロトコルの概念実証のための拡張であり、開発目的でのみ使用できます。現在、公式なAmendmentはなく、本番のメインネットでは利用できません。EVM互換サイドチェーンブリッジは、XRP Ledger Devnetに接続されています。Mainnetでトランザクションを送信しないでください。_ 

content/_snippets/evmsc-disclaimer.md

@@ -1 +0,0 @@
-_The EVM compatible sidechains implementation :not_enabled: is a proof of concept extension to the XRP Ledger protocol and is for development purposes only. There is no official amendment currently and it is not available on the production Mainnet. The EVM compatible sidechain bridge is connected to the XRP Ledger Devnet. Do not send transactions in Mainnet._ 

content/concepts/consensus-network/federated-sidechains.ja.md

@@ -1,88 +0,0 @@
----
-html: federated-sidechains.html
-parent: consensus-network.html
-blurb: サイドチェーンとXRP Ledgerの間で、XRPやその他のトークン（IOU）の形で価値を効率的に移動させることができる、フェデレーションサイドチェーンについてご紹介します。
-labels:
-  - ブロックチェーン
----
-# フェデレーションサイドチェーン
-
-_フェデレーションサイドチェーンは開発者プレビューとして提供されており、`rippled` 1.8.0を使った開発やテストに使用することができます。_
-
-サイドチェーンとは、独自のコンセンサスアルゴリズムと取引の種類やルールを持つ独立した台帳のことです。独自のブロックチェーンとして機能します。フェデレーションは、XRPや他のトークンの形で、サイドチェーンとXRP Ledger _メインチェーン_（通常はMainnetですが、テスト用に[Testnet or Devnet](parallel-networks.html)にすることもできます）の間で、価値を効率的に移動させることができます。フェデレーションサイドチェーンは、公開メインネットのスピード、効率、スループットを損なうことなく動作します。
-
-フェデレーションサイドチェーンにより、開発者はXRP Ledger技術の基盤を使って新機能や革新的なアプリケーションを立ち上げることができます。サイドチェーンは、特定のユースケースやプロジェクトのニーズに合わせてXRP Ledgerのプロトコルをカスタマイズし、独自のブロックチェーンとして運用することができます。いくつかの例をご紹介します。
-
-* Ethereum Virtual Machine (EVM)、Web Assembly、またはMove VMと互換性のあるエンジンを搭載した、スマートコントラクトレイヤーの構築。例えば、[smart sidechain with Hooks](https://hooks-testnet.xrpl-labs.com/)を有効にする等。
-* 台帳の種類や取引ルールをカスタマイズした独自のアルゴリズムでのステーブルコインの構築。
-* Mainnetの[分散型取引所](decentralized-exchange.html)で取引することが可能な資産を持つ、許可制またはほぼ無許可、中央集権型または大部分が分散型の台帳の構築。
-
-## フェデレーションサイドチェーンのしくみ
-
-サイドチェーンは、独自のコンセンサス・アルゴリズムや取引の種類・ルールを持つ独立した台帳です。各サイドチェーンは独自のサーバーセット(バリデータを含む)によって運営されており、サイドチェーン上の取引についてはMainnet上のバリデータに依存しません。
-
-各サイドチェーンには、サイドチェーン上とメインチェーン上の2つのドアアカウントがあり、サイドチェーン上のフェデレータが管理しています。フェデレータは、この両方のドアアカウントとの間のトランザクションを監視します。
-
-サイドチェーンには、両ネットワークのドア・アカウントを共同で管理する _フェデレータ_ がおり、[マルチサイン](multi-signing.html)を用いて、フェデレータの80%が取引を承認しなければなりません。多くの場合、フェデレータはサイドチェーンの信頼できる検証者でもあるべきです。
-
-ドアアカウントがサイドチェーンまたはメインチェーンのいずれかでトランザクションを受け取ると、フェデレータは他のチェーンでミラートランザクションを作成します。(例えば、メインチェーンの _ドアアカウントにXRPを送信_ した場合、フェデレータはサイドチェーンのドアアカウントからXRPを _目的の受信者に送信_ するために、サイドチェーンでトランザクションを作成します) フェデレータはそのトランザクションに署名し、お互いにブロードキャストします。同時に、フェデレータは他のフェデレータからの署名付きトランザクションをリッスンし、それを収集します。
-
-フェデレータの80％がトランザクションに署名したら、それを適宜サイドチェーンまたはメインチェーンに提出します。こうすることで、メインチェーンのドアアカウントが持つ資産をサイドチェーンの他の人に割り当てたり、サイドチェーンのドアアカウントが受け取る資産をメインチェーンの他の人に送ったりすることができます。
-
-サイドチェーン内の取引は、サイドチェーン上のサーバーからは見えません。
-
-
-## 用語解説
-
-_サイドチェーン_: XRP Ledgerのサイドチェーンとは、XRP Ledgerの技術をベースにした別のブロックチェーンのことです。_フェデレーター_ サイドチェーンは、メインチェーンからサイドチェーンへの資産移転の手段を提供します。サイドチェーンは、XRP Ledgerのプロトコルの完全なコピーを使用することもできますし、[コンセンサス・アルゴリズム](consensus.html)、[トランザクション・タイプ](transaction-types.html)、その他のルールを含む変更を加えることもできます。
- 
-_フェデレーター_: サイドチェーン上のサーバーで、メインチェーンとサイドチェーンの両方のトランザクションのトリガーをリッスンします。各フェデレーターは、トランザクションの署名に使用される署名鍵を持っています。トランザクションを送信するには、フェデレータの定足数による署名が必要です。フェデレータは、有効なレスポンス・トランザクションの作成と署名、他のフェデレータからの署名の収集、メイン・チェーンとサイド・チェーンへのトランザクションの送信に責任を負います。
-
-_メインチェーン_: 資産が生まれるブロックチェーンで、サイドチェーンで使用されている間、資産が保持される場所。ほとんどのサイドチェーンでは、メインチェーンはXRP Ledger Mainnet、Testnet、またはDevnetとなっています。
-
-_サイドチェーン_: 一部の資産がメインチェーンに裏付けられているカスタムブロックチェーンです。代理資産はサイドチェーンで発行され、同等の資産はメインチェーンのドアアカウントで保有されます。サイドチェーンはメインチェーンとは別の履歴、ルール、バリデーターを持ちます。サイドチェーン上の代理資産は、メインチェーンに送り返され、フェデレータの管理下からロックを解除することができます。
-
-_ドアアカウント_: フェデレータが管理するアカウントです。ドアアカウントは、メインチェーン上とサイドチェーン上の2つがあります。クロスチェーンの取引は、ユーザーがドアアカウントにアセットを送ることで始まります。メインチェーンからサイドチェーンへの取引では、メインチェーンのドアアカウントの残高が増加し、サイドチェーンのドアアカウントの残高が減少します。ドアと呼ばれるのは、あるチェーンから別のチェーンへと資産を移動させるための仕組みだからです。
-
-_トリガー トランザクション_: フェデレータが新たな応答トランザクションに署名して提出するプロセスを開始するきっかけとなるトランザクションのこと。例えば、メインチェーンのドアアカウントにXRPを送ることは、サイドチェーン上でフェデレータに新しいトランザクションを提出させるトリガーとなるトランザクションです。
-
-_レスポンス トランザクション_: トリガーとなるトランザクションに反応してフェデレータが提出するトランザクション。ほとんどの場合、レスポンス・トランザクションはトリガー・トランザクションと反対側のチェーンで発生する。ただし、失敗したトランザクションを処理するためのいくつかの例外があります。
-
-
-## フェデレーションサイドチェーンのセットアップ方法
-
-フェデレーションサイドチェーンは現在開発者プレビューとして提供されているため、サイドチェーンの可能性を実験的に探ることができます。メインチェーンネットワーク内の[サーバー](xrpl-servers.html)のバージョンが1.8.0以上であれば、サイドチェーンをXRP Ledger Testnet、Devnet、Mainnetに接続することができます。
-
-**注意:** サイドチェーンをXRP Ledger Mainnetに接続することで、少量の開発やテストを行うことができますが、フェデレーションサイドチェーンがリリースされるまでは、本番環境での使用はお勧めできません。
-
-サイドチェーンの設定には、次のような大まかなステップがあります。
-
-1. rippled`のソースコードをクローンして、`sidechain`ブランチをチェックアウトします。https://github.com/ripple/rippled/tree/sidechain。
-2. サイドチェーンのソースコードをカスタマイズします。例えば、カスタムの[トランザクションタイプ](transaction-types.html)を書きたいと思うかもしれません。 これは重要で簡単ではない作業であることに注意してください。
-3. 各サイドチェーン・フェデレーターにはそれぞれ設定ファイルがあり、以下の情報を含むように更新する必要があります。
-    - `[sidechain]` 節 - 署名鍵、メインチェーンアカウント、リッスンするメインチェーンアドレス（IPとポート）などの詳細を追加します。
-    `[sidechain_assets]` 節 - クロスチェーン取引に使用できる資産（XRPまたは[発行されたトークン](issued-currencies.html)）、資産の交換レート、デフォルトになる可能性のある取引を阻止するためのオプションの返金ペナルティを定義します。
-    - [sidechain_federators] 節 - 署名に使用されるフェデレータ公開鍵のリスト。このリストは、サイドチェーン上のすべてのフェデレータに共通です。
-4. クロスチェーン取引を可能にするため、ドアアカウントを設定する。これには（両方のチェーンで）以下の手順が必要です。
-    - ドアアカウントの作成と資金調達
-    - ドアアカウントの[署名者リストの設定](set-up-multi-signing.html)
-    - エラー処理のためにの3つの[チケット](tickets.html)の作成
-    - そして最後に、フェデレータがドアアカウントを共同で管理するようにするためのドアアカウントの[マスターキーペアの無効化](disable-master-key-pair.html)
-
-        なお、この最後のステップは、これまでのステップが正常に完了した後に実行することが重要です。
-
-
-_サイドチェーン ローンチキット_ は、フェデレーションサイドチェーンの設定を簡素化するコマンドラインツールで、ローカルマシン上でサイドチェーンを素早く立ち上げるのに使用できます。また、ローンチキットは、サイドチェーンとの対話を可能にするインタラクティブなサイドチェーンシェルをインストールします。
-
-[サイドチェーン ローンチキット >](https://github.com/xpring-eng/sidechain-launch-kit/blob/main/README.md)
-
-
-## 関連項目
-
-- **概念:**
-    - [フェデーレーションサイドチェーン ビデオ](https://www.youtube.com/embed/NhH4LM8NxgY)
-
-
-
-
-

content/concepts/consensus-network/federated-sidechains.md

@@ -1,88 +0,0 @@
----
-html: federated-sidechains.html
-parent: consensus-network.html
-blurb: Learn about federated sidechains, which enable value in the form of XRP and other tokens (IOUs) to move efficiently between a sidechain and the XRP Ledger.
-labels:
-  - Blockchain
----
-# Federated Sidechains
-
-_Federated Sidechains are available as an Engineering Preview and can be used to develop and test using `rippled` 1.8.0._
-
-A sidechain is an independent ledger with its own consensus algorithm and transaction types and rules. It acts as its own blockchain. Federation enables value in the form of XRP and other tokens to move efficiently between a sidechain and an XRP Ledger _mainchain_ (usually Mainnet, but could be [Testnet or Devnet](parallel-networks.html) for testing). Federated sidechains run without compromising the speed, efficiency, and throughput of the public Mainnet.
-
-Federated sidechains enable developers to launch new features and innovative applications using the foundation of XRP Ledger technology. Sidechains can customize the XRP Ledger protocol to the needs of a specific use case or project and run it as its own blockchain. Here are a few examples:
-
-* Build a smart contract layer, powered by an engine compatible with the Ethereum Virtual Machine (EVM), web assembly, or a Move VM. For example, a [smart sidechain with Hooks](https://hooks-testnet.xrpl-labs.com/) enabled.
-* Build your own algorithmic stable coin with customised ledger types and transaction rules.
-* Build permissioned or nearly permissionless, centralized or largely decentralized ledgers whose assets can be traded on the Mainnet [decentralized exchange](decentralized-exchange.html).
-
-## How Federated Sidechains Work
-
-
-A sidechain is an independent ledger with its own consensus algorithm and transaction types and rules. Each sidechain is run by its own set of servers (including validators) and does not rely on the validators on the Mainnet for transactions on the sidechain.
-
-Each sidechain has two door accounts, one on the sidechain and one on the mainchain, that are controlled by the federators on the sidechain. The federators listen for transactions to and from both of these door accounts.
-
-The sidechain has _federators_ who jointly control the door accounts on both networks using [multi-signing](multi-signing.html) so that 80% of federators must approve a transaction. In many cases, the federators should also be the trusted validators of the sidechain.
-
-When a door account receives a transaction on either the sidechain or the mainchain, the federators create a mirror transaction on the other chain. (For example, if you send XRP _to_ the mainchain door account, the federators create a transaction on the sidechain to send XRP _from_ the sidechain door account to the intended recipient.) The federators sign the transaction and broadcast it to each other. Simultaneously, federators also listen for signed transactions from other federators and collect them.
-
-When 80% of the federators have signed the transaction, they submit it to the sidechain or mainchain as appropriate. This way, assets that the mainchain door account holds can be allocated to others on the sidechain, and assets that sidechain door account receives can be sent to others on the mainchain.
-
-Transactions within the sidechain are not visible to the servers on the mainchain. 
-
-
-## Terminology
-
-Below is an alphabetical list of terms and their definitions.
-
-_Door account_: An account controlled by the federators. There are two door accounts: one on the mainchain and one on the sidechain. Cross chain transactions are started by users sending assets to a door account. Mainchain to sidechain transactions cause the balance to increase on the mainchain door account and the balance to decrease on the sidechain door account. It is called a "door" because it is the mechanism to move assets from one chain to another—much like going between rooms in a house requires stepping through a door.
-
-_Federator_: A server on the sidechain that listens for triggering transactions on both the mainchain and the sidechain. Each federator has a signing key associated with it that is used to sign transactions. A transaction must be signed by a quorum of federators before it can be submitted. Federators are responsible for creating and signing valid response transactions, collecting signatures from other federators, and submitting transactions to the mainchain and sidechain.
-
-_Mainchain_: The blockchain where assets originate and where assets are held while being used on the sidechain. For most sidechains, the mainchain is the XRP Ledger Mainnet, Testnet, or Devnet.
-
-_Response transaction_: A transaction submitted by the federators in reaction to a triggering transaction. In most cases, the response transaction occurs on the opposite chain as the triggering transaction. However, there are some exceptions for handling failed transactions.
-
-_Sidechain_: An XRP Ledger sidechain is another blockchain based on XRP Ledger technology. A _federated_ sidechain provides a way to transfer assets from a mainchain to the sidechain and back. A sidechain can use an exact copy of the XRP Ledger's protocol or it can make changes, including to the [consensus algorithm](consensus.html), [transaction types](transaction-types.html), and other rules. Sidechains have separate history, rules, and validators than the mainchain. Proxy assets are issued in the sidechain, with the equivalent assets held by a door account on the mainchain. Proxy assets on the sidechain can be sent back to the mainchain and unlocked from the control of the federators.
- 
-_Triggering transaction_: A transaction that causes the federators to start the process of signing and submitting a new response transaction. For example, sending XRP to the mainchain's door account is a triggering transaction that causes the federators to submit a new transaction on the sidechain.
-
-## How to Set Up a Federated Sidechain
-
-Federated Sidechains are currently available as an Engineering Preview so you can experiment and explore the potential of sidechains. You can connect sidechains to the XRP Ledger Testnet, Devnet, or Mainnet as long as [the servers](xrpl-servers.html) in the mainchain network are running version 1.8.0 or higher.
-
-**Caution:** You can connect sidechains to the XRP Ledger Mainnet to develop and test with small amounts; it is not recommended for production use cases until federated sidechains are available in a release. 
-
-Setting up a sidechain involves the following high-level steps:
-
-1. Clone the `rippled` source code and check out the `sidechain` branch: https://github.com/ripple/rippled/tree/sidechain.
-2. Customize the source code for your sidechain. For example, you may want to write custom [transaction types](transaction-types.html). Note that this is an important and non-trivial task.
-3. Each sidechain federator has its own configuration file that must be updated to include the following information:  
-    - `[sidechain]` stanza - add details such as signing key, mainchain account, and the mainchain address (IP and port) to listen to. 
-    - `[sidechain_assets]` stanza - define assets that can be used for cross-chain transactions (XRP or [issued tokens](issued-currencies.html)), exchange rate for the assets, and optional refund penalty to discourage transactions that may default.
-    - [sidechain_federators] stanza - list of federators public keys to be used for signing. This list is common for all federators on the sidechain.
-4. Set up door accounts to enable cross chain transactions. This involves the following steps (on _both_ chains):
-    - Create and fund the door accounts. 
-    - [Set up the SignerList](set-up-multi-signing.html) for the door account.
-    - Create three [tickets](tickets.html) for error handling.
-    - And finally, [disable the master key pair](disable-master-key-pair.html) to the door account to ensure that the federators jointly control the door account. 
-
-        Note that it is important to perform this final step only after successful completion of the previous steps.
-
-
-The _Sidechain Launch Kit_ is a commandline tool that simplifies setting up federated sidechains and can be used to quickly spin up a sidechain on your local machine. The launch kit also installs an interactive Sidechain Shell that enables you to interact with the sidechain.
-
-[Sidechain Launch Kit >](https://github.com/xpring-eng/sidechain-launch-kit)
-
-
-## See Also
-
-- **Concepts:**
-    - [Federated Sidechains Video](https://www.youtube.com/embed/NhH4LM8NxgY)
-
-
-
-
-

content/concepts/interoperability/intro-to-evm-sidechain.ja.md

@@ -1,44 +0,0 @@
----
-html: intro-to-evm-sidechain.html
-parent: xrpl-interoperability.html
-blurb: EVM互換 XRP Ledger サイドチェーンの紹介
-labels:
-  - 相互運用性
-status: not_enabled
----
-# EVM互換 XRP Ledger サイドチェーンの紹介
-
-{% include '_snippets/evmsc-disclaimer.ja.md' %}
-
-Ethereum Virtual Machine（EVM）互換のXRP Ledgerサイドチェーンは、安全で高速なパブリックブロックチェーンで、あらゆる種類のWeb3アプリケーションをXRP Ledgerコミュニティにもたらします。
-
-- エクスプローラ: [https://evm-sidechain.xrpl.org](https://evm-sidechain.xrpl.org/)
-- 公開RPC: [https://rpc-evm-sidechain.xrpl.org](https://rpc-evm-sidechain.xrpl.org/)
-
-
-EVMサイドチェーンは、以下の特徴を持つ強力な最新世代のブロックチェーンです。
-
-- 1秒間に最大1000件のトランザクションをサポートし、大量のデータとスループットを処理する。
-- 5秒ごとにブロックが生成され、平均してトランザクションの承認までの時間が短い。
-- ブロックがチェーンに追加され、確認されると、そのブロックは確定される（確定時間1ブロック）。
-- Ethereum Virtual Machine (EVM)との完全な互換性があり、ウォレットを接続し、Solidityで書かれたスマートコントラクトと相互にやり取りしたり、デプロイしたりすることが可能。
-
-## コンセンサス
-
-EVMサイドチェーンはプルーフオブステーク（PoS）コンセンサスアルゴリズムで動作しています。ステーキングとは、トランザクションの検証に使用するコインを担保にすることです。プルーフ・オブ・ステークモデルでは、暗号通貨（「コイン」とも呼ばれる）をステークし、独自のバリデーターノードを作成することが可能です。 コインはステーキングしている間はロックされますが、コインをトレードしたい場合は、ステーキングを解除することができます。
-
-プルーフ・オブ・ステーク型ブロックチェーンでは、マイニングパワーはバリデーターがステークしているコインの量に依存します。より多くのコインをステークしている参加者は、新しいブロックの生成者として選ばれる可能性が高くなります。
-
-暗号通貨のステーキングや独自のバリデータの運用に興味がある方は、[EVMサイドチェーン Devnetに参加する](join-evm-sidechain-devnet.html)で詳細を確認してください。
-
-XRP Ledger EVMサイドチェーンのコンセンサスの基盤技術は、ブロックチェーン構築のためのByzantine-Fault Tolerantエンジンである[Tendermint](https://tendermint.com/)です。
-
-ブロックチェーンはTendermintの上にある`cosmos-sdk`ライブラリを使用し、その組み込みモジュールを使ってブロックチェーンを作成・カスタマイズします。EVMサイドチェーンは、[Ethermint](https://github.com/evmos/ethermint)の`cosmos-sdk`モジュールを使用し、EVMとの互換性を提供します。
-
-## EVMサイドチェーンを利用した相互運用性
-
-EVMサイドチェーンは、XRP Ledgerブリッジ[https://bridge.devnet.xrpl](https://bridge.devnet.xrpl.org/)を介してXRP Ledgerに直接接続されています。このブリッジを通じて、EVMサイドチェーンに接続し、その機能を利用することができます。
-
-## 関連項目
-
-[EVMサイドチェーンを始めよう](get-started-evm-sidechain.html)

content/concepts/interoperability/intro-to-evm-sidechain.md

@@ -1,44 +0,0 @@
----
-html: intro-to-evm-sidechain.html
-parent: xrpl-interoperability.html
-blurb: Introduction to the EVM compatible XRP Ledger Sidechain
-labels:
-  - Interoperability
-status: not_enabled
----
-# Introduction to EVM Compatible XRP Ledger Sidechain
-
-{% include '_snippets/evmsc-disclaimer.md' %}
-
-The Ethereum Virtual Machine (EVM) compatible XRP Ledger sidechain is a secure and fast public blockchain that brings all kinds of web3 applications to the XRP Ledger community. 
-
-- Explorer: [https://evm-sidechain.xrpl.org](https://evm-sidechain.xrpl.org/)
-- Public RPC: [https://rpc-evm-sidechain.xrpl.org](https://rpc-evm-sidechain.xrpl.org/)
-
-
-The EVM Sidechain is a powerful latest generation blockchain with the following features:
-
-- Supports up to 1000 transactions per second, thus handling large loads and throughput.
-- Has a low transaction confirmation time, on average, as a block is produced every 5 seconds. 
-- Once a block is added to the chain and confirmed, it is considered final (1 block finalization time).
-- Provides full Ethereum Virtual Machine (EVM) compatibility, enabling you to connect your wallet and interact or deploy smart contracts written in Solidity. <!-- STYLE_OVERRIDE: wallet -->
-
-## Consensus
-
-The EVM Sidechain runs on a proof-of-stake (PoS) consensus algorithm. Staking is when you pledge your coins to be used for verifying transactions. The proof-of-stake model allows you to stake cryptocurrency (also referred to as "coins") and create your own validator nodes. Your coins are locked up while you stake them, but you can unstake them if you want to trade your coins.
-
-In a proof-of-stake blockchain, mining power depends on the amount of coins a validator is staking. Participants who stake more coins are more likely to be chosen to add new blocks.
-
-If you are interested in staking cryptocurrency and running your own validator, see [Join EVM Sidechain Devnet](join-evm-sidechain-devnet.html) for more information.
-
-The underlying technology for the XRP Ledger EVM Sidechain consensus is [Tendermint](https://tendermint.com/), a Byzantine-Fault Tolerant engine for building blockchains.
-
-The blockchain uses the `cosmos-sdk` library on top of Tendermint to create and customize the blockchain using its built-in modules. The EVM sidechain uses the [Ethermint](https://github.com/evmos/ethermint) `cosmos-sdk` module, which provides EVM compatibility.
-
-## Interoperability Using the EVM Sidechain
-
-The EVM sidechain is directly connected to XRP Ledger through the XRP Ledger bridge [https://bridge.devnet.xrpl](https://bridge.devnet.xrpl.org/). Through this bridge, you can connect to the EVM Sidechain and use its features.
-
-## See Also
-
-[Get Started with EVM Sidechain](get-started-evm-sidechain.html)

content/concepts/interoperability/xrpl-interoperability.ja.md

@@ -1,13 +0,0 @@
----
-html: xrpl-interoperability.html
-parent: concepts.html
-blurb: XRP Ledgerにプログラマビリティと他のチェーンとの相互作用能力をもたらす機能を学ぶ.
-template: pagetype-category.html.jinja
-labels:
-  - 相互運用性
-status: not_enabled
----
-# 相互運用性
-
-XRP Ledgerは、トランザクションの処理能力、スピード、低手数料で知られています。プログラマビリティと相互運用性の追加により、開発者はスマートコントラクトなどの機能にアクセスでき、クロスチェーンの相互運用性を備えたアプリを構築することができます。
-

content/concepts/interoperability/xrpl-interoperability.md

@@ -1,13 +0,0 @@
----
-html: xrpl-interoperability.html
-parent: concepts.html
-blurb: Learn about capabilities that bring programmability and ability to interact with other chains to the XRP Ledger.
-template: pagetype-category.html.jinja
-labels:
-  - Interoperability
-status: not_enabled
----
-# Interoperability
-
-The XRP Ledger is known for its transaction throughput, speed, and low fees. With the addition of programmability and interoperability, developers can access features such as smart contracts and can build apps with cross-chain interoperability. 
-

content/faq.md

@@ -35,7 +35,7 @@ Yes, the XRP Ledger was built specifically to be able to tokenize arbitrary asse
 
 #### Isn’t XRPL only for payments?
 
-Although XRPL was initially developed for payment use cases, both the ledger and its native digital asset XRP are increasingly popular for a range of innovative blockchain use cases such as NFTs. New standards proposals for an automated market maker (AMM), XRPL Labs’ hooks amendment for smart contract functionality, and federated sidechains are all currently works in progress.
+Although XRPL was initially developed for payment use cases, both the ledger and its native digital asset XRP are increasingly popular for a range of innovative blockchain use cases such as NFTs. New standards proposals for an automated market maker (AMM), hooks amendment for smart contract functionality, and cross-chain bridges are all currently works in progress.
 
 ## Validators and Unique Node Lists
 

content/references/protocol-reference/serialization.ja.md

@@ -184,7 +184,8 @@ curated_anchors:
 | [Hash256][] | 5 | 256 | いいえ | 256ビットの任意のバイナリ値。これは通常、トランザクション、レジャーバージョン、またはレジャーデータオブジェクトの「SHA-512ハーフ」ハッシュを表します。 |
 | [PathSet][] | 18 | 可変 | いいえ | [複数通貨間ペイメント](cross-currency-payments.html)の有効な[ペイメントパス](paths.html)のセット。 |
 | [STArray][] | 15 | 可変 | いいえ | 可変数のメンバーからなる配列。フィールドによってタイプが異なる場合があります。この例として、[memos](transaction-common-fields.html#memosフィールド)や[マルチ署名](multi-signing.html)で使用される署名者のリストがあります。 |
-| [STIssue][]   | 24        | 320        | いいえ                   | :not_enabled: An asset definition, XRP or a token, with no quantity.<!-- TODO: translate --> |
+<!-- TODO: translate -->
+<!-- | [STIssue][]   | 24        | 320        | いいえ                   | :not_enabled: An asset definition, XRP or a token, with no quantity. |--> 
 | [STObject][] | 14 | 可変 | いいえ | 1つ以上のネストされたフィールドを含むオブジェクト。 |
 | [UInt8][] | 16 | 8 | いいえ | 8ビットの符号なし整数。 |
 | [UInt16][] | 1 | 16 | いいえ | 16ビットの符号なし整数。`TransactionType`は、このタイプの特殊なフィールドで、特定の文字列から整数値へのマッピングを含みます。 |
@@ -268,16 +269,20 @@ XRP LedgerのハッシュタイプにはHash128、Hash160、Hash256がありま
 
 これらのフィールドは、長さインディケーターを使用せずに、ビッグエンディアンバイトオーダーで特定数のビットとしてシリアル化されます。
 
+<!--
 ### Issueフィールド
-[STIssue]: #issueフィールド
+[STIssue]: #issueフィールド -->
 <!-- TODO: translate this section -->
 
+<!-- 
 _(The "Issue" or "STIssue" type is part of multiple proposed extensions to the XRP Ledger protocol, including [XLS-30d: Automated Market Maker](https://github.com/XRPLF/XRPL-Standards/discussions/78) :not_enabled: and [Federated Sidechains](federated-sidechains.html) :not_enabled:)_
+-->
 
+<!--
 Some fields specify a _type_ of asset, which could be XRP or a fungible [token](tokens.html), without an amount. These fields have consist of two 160-bit segments in order:
 
 1. The first 160 bits are the [currency code](currency-formats.html#通貨コード) of the asset. For XRP, this is all 0's.
-2. The next 160 bits are the [AccountID of the token issuer](#accountidフィールド). For XRP, this is all 0's.
+2. The next 160 bits are the [AccountID of the token issuer](#accountidフィールド). For XRP, this is all 0's. -->
 
 ### オブジェクトフィールド
 [STObject]: #オブジェクトフィールド

content/references/protocol-reference/serialization.md

@@ -184,7 +184,7 @@ Transaction instructions may contain fields of any of the following types:
 | [Hash256][]   | 5         | 256        | No                   | A 256-bit arbitrary binary value. This usually represents the "SHA-512Half" hash of a transaction, ledger version, or ledger data object. |
 | [PathSet][]   | 18        | Variable   | No                   | A set of possible [payment paths](paths.html) for a [cross-currency payment](cross-currency-payments.html). |
 | [STArray][]   | 15        | Variable   | No                   | An array containing a variable number of members, which can be different types depending on the field. Two cases of this include [memos](transaction-common-fields.html#memos-field) and lists of signers used in [multi-signing](multi-signing.html). |
-| [STIssue][]   | 24        | 160 or 320 | No                   | :not_enabled: An asset definition, XRP or a token, with no quantity. |
+<!-- | [STIssue][]   | 24        | 160 or 320 | No                   | :not_enabled: An asset definition, XRP or a token, with no quantity. | -->
 | [STObject][]  | 14        | Variable   | No                   | An object containing one or more nested fields. |
 | [UInt8][]     | 16        | 8          | No                   | An 8-bit unsigned integer. |
 | [UInt16][]    | 1         | 16         | No                   | A 16-bit unsigned integer. The `TransactionType` is a special case of this type, with specific strings mapping to integer values. |
@@ -300,15 +300,21 @@ The XRP Ledger has several "hash" types: Hash128, Hash160, and Hash256. These fi
 
 All such fields are serialized as the specific number of bits, with no length indicator, in big-endian byte order.
 
+
+<!-- Issue Fields is still under development -->
+<!--
 ### Issue Fields
 [STIssue]: #issue-fields
 
-_(The "Issue" or "STIssue" type is part of multiple proposed extensions to the XRP Ledger protocol, including [XLS-30d: Automated Market Maker](https://github.com/XRPLF/XRPL-Standards/discussions/78) :not_enabled: and [Federated Sidechains](federated-sidechains.html) :not_enabled:)_ <!-- SPELLING_IGNORE: 30d -->
+_(The "Issue" or "STIssue" type is part of multiple proposed extensions to the XRP Ledger protocol, including [XLS-30d: Automated Market Maker](https://github.com/XRPLF/XRPL-Standards/discussions/78) :not_enabled: and [Federated Sidechains](federated-sidechains.html) :not_enabled:)_ -->
 
+<!-- SPELLING_IGNORE: 30d -->
+
+<!--
 Some fields specify a _type_ of asset, which could be XRP or a fungible [token](tokens.html), without an amount. These fields have consist of one or two 160-bit segments in order:
 
 1. The first 160 bits are the [currency code](#currency-codes) of the asset. For XRP, this is all 0's.
-2. If the first 160 bits are all 0's (the asset is XRP), the field ends there. Otherwise, the asset is a token and the next 160 bits are the [AccountID of the token issuer](#accountid-fields).
+2. If the first 160 bits are all 0's (the asset is XRP), the field ends there. Otherwise, the asset is a token and the next 160 bits are the [AccountID of the token issuer](#accountid-fields). -->
 
 
 ### Object Fields

content/tutorials/interoperability/connect-metamask-to-xrpl-evm-sidechain.md

@@ -1,50 +0,0 @@
----
-html: connect-metamask-to-xrpl-evm-sidechain.html
-parent: get-started-evm-sidechain.html
-blurb: Learn how to connect MetaMask wallet to the EVM Sidechain for the XRP Ledger.
-labels:
-  - Development, Interoperability
-status: not_enabled
----
-# Connect MetaMask to XRP Ledger Sidechain
-
-{% include '_snippets/evmsc-disclaimer.md' %}
-
-MetaMask is an extension for accessing Harmony-enabled distributed applications (_dapps_) from your browser. The extension injects the XRP Ledger EVM sidechain Web3 API into every website's Javascript context, so that Web3 applications can read from the blockchain. <!-- SPELLING_IGNORE: dapps -->
-
-This tutorial walks through the process of installing MetaMask, configuring it on the XRP Ledger EVM sidechain network, and importing an existing account using a previously generated private key.
-
-## 1. Installing MetaMask
-
-Install the MetaMask extension on your browser from **[https://metamask.io/download/](https://metamask.io/download/)**. The extension supports most desktop browsers. 
-
-## 2. Create an Account on MetaMask
-
-To create a new account on MetaMask:
-
-1. Click the MetaMask icon.
-
-    ![Create an account on MetaMask](img/evm-sidechain-create-metamask-account.png "Create an account on MetaMask")
-
-2. Choose **Create Account**.
-
-3. Enter the Account Name.
-
-4. Click **Create**.
-
-### 3. Adding XRP Ledger EVM Sidechain to MetaMask
-
-To add XRP Ledger EVM Sidechain to MetaMask:
-
-1. Open the MetaMask extension.
-
-2. Use the drop-down menu to choose **Add Network**.
-    ![Add the EVM Sidechain network to MetaMask](img/evm-sidechain-add-metamask-network.png "Add the EVM Sidechain network to MetaMask")
-
-3. Enter the XRP Ledger Devnet endpoint information.
-
-    * **Network Name**: XRP Ledger EVM Sidechain
-    * **New RPC URL**: https://rpc-evm-sidechain.xrpl.org
-    * **Chain ID**: 1440001
-    * **Currency Symbol**: XRP
-    * **Block Explorer**: https://evm-sidechain.xrpl.org

content/tutorials/interoperability/evm-sidechain-run-a-validator-node.md

@@ -1,110 +0,0 @@
----
-html: evm-sidechain-run-a-validator-node.html
-parent: evm-sidechains.html
-blurb: Learn how to run a validator node on the EVM Sidechain Devnet.
-labels:
-  - Development, Interoperability
-status: not_enabled
----
-# Run a Validator Node on an EVM Sidechain
-
-{% include '_snippets/evmsc-disclaimer.md' %}
-
-## Create Your Validator
-
-Use your node consensus public key (`exrpvalconspub...`) to create a new validator by staking XRP tokens. You can find your validator public key by running:
-
-```bash
-exrpd tendermint show-validator
-```
-
-To create your validator on Devnet, use the following command:
-
-```bash
-exrpd tx staking create-validator \
-  --amount=1000000000000000000000axrp \
-  --pubkey=$(exrpd tendermint show-validator) \
-  --moniker="<your_custom_moniker>" \
-  --chain-id=<chain_id> \
-  --commission-rate="0.05" \
-  --commission-max-rate="0.10" \
-  --commission-max-change-rate="0.01" \
-  --min-self-delegation="1000000" \
-  --gas="auto" \
-  --gas-prices="0.025aphoton" \
-  --from=<key_name>
-```
-
-**Note** When specifying commission parameters, the `commission-max-change-rate` is used to measure % *point* change over the `commission-rate`. For example, 1% to 2% is a 100% rate increase, but only 1 percentage point.
-
-
-**Note** `Min-self-delegation` is a strictly positive integer that represents the minimum amount of self-delegated voting power your validator must always have. A `min-self-delegation` of `1000000` means your validator will never have a self-delegation lower than `1 axrp`. <!-- STYLE_OVERRIDE: will -->
-
-You can confirm that you are in the validator set by using a third-party explorer.
-
-## Edit Validator Description
-
-You can edit your validator's public description. This info identifies your validator, and _delegators_ use it when they decide to stake XRP tokens to a particular validator. Make sure to provide input for every flag below. If a flag is not included in the command, the field defaults to empty (`--moniker` defaults to the machine name), if the field has never been set, or remains the same, if it has been set in the past. <!-- SPELLING_IGNORE: delegators --><!-- STYLE_OVERRIDE: defaults to -->
-
-The <key_name> specifies which validator you are editing. If you choose to not include certain flags, remember that the --from flag must be included to identify the validator to update.
-
-The `--identity` can be used as to verify identity with systems like Keybase or UPort. When using with Keybase `--identity` must be populated with a 16-digit string that is generated with a [keybase.io](https://keybase.io/) account. It is a cryptographically secure method of verifying your identity across multiple online networks. The Keybase API allows us to retrieve your Keybase avatar. This is how you can add a logo to your validator profile. <!-- SPELLING_IGNORE: uport -->
-
-```bash
-exrpd tx staking edit-validator
-  --moniker="<your_custom_moniker>" \
-  --website="https://xrpl.org" \
-  --identity=6A0D65E29A4CBC8E \
-  --details="<your_validator_description>" \
-  --chain-id=<chain_id> \
-  --gas="auto" \
-  --gas-prices="0.025axrp" \
-  --from=<key_name> \
-  --commission-rate="0.10"
-```
-
-Note that the `commission-rate` value must adhere to the following invariants:
-
-  * Must be between 0 and the validator's `commission-max-rate`
-  * Must not exceed the validator's `commission-max-change-rate` which is the maximum % point change rate **per day**. In other words, a validator can only change its commission once per day and within `commission-max-change-rate` bounds.
-
-## View Validator Description
-
-View the validator's information with this command:
-
-```bash
-exrpd query staking validator <account>
-```
-
-## Track Validator Signing Information
-
-To track a validator's signatures from past transactions use the `signing-info` command. 
-
-```bash
-exrpd query slashing signing-info <validator-pubkey> --chain-id=<chain_id>
-```
-
-## Unjail Validator
-<!-- SPELLING_IGNORE: unjail -->
-
-When a validator is "jailed" for downtime, you must submit an `Unjail` transaction from the operator account to restore block proposer awards (depending on the zone fee distribution).
-
-```bash
-exrpd tx slashing unjail --from=<key_name> --chain-id=<chain_id>
-```
-
-## Confirm Your Validator is Running
-
-Your validator is active if the following command returns anything:
-
-```bash
-exrpd query tendermint-validator-set | grep "$(exrpd tendermint show-address)"
-```
-
-You should now see your validator in one of the Exrp explorers. You are looking for the `bech32` encoded `address` in the `~/.exprd/config/priv_validator.json` file. <!-- SPELLING_IGNORE: exrp -->
-
-**Note** To be in the validator set, you must have more total voting power than the 100th validator.
-
-## Halting Your Validator
-
-When attempting to perform routine maintenance or planning for an upcoming coordinated upgrade, it can be useful to have your validator systematically and gracefully halt. Set the `halt-height` to the height at which you want your node to shut down, or pass the `--halt-height` flag to `exrpd`. The node shuts down with a 0 exit code at that given height after committing the block.

content/tutorials/interoperability/evm-sidechain-validator-security.md

@@ -1,67 +0,0 @@
----
-html: evm-sidechain-validator-security.html
-parent: join-evm-sidechain-devnet.html
-blurb: Learn how to join the XRP Ledger EVM Sidechain Devnet.
-labels:
-  - Development, Interoperability
-status: not_enabled
----
-# EVM Sidechain Validator Security
-
-{% include '_snippets/evmsc-disclaimer.md' %}
-
-Each validator candidate is encouraged to run its operations independently, as diverse setups increase the resilience of the network. Validator candidates should begin their setup phase now, to be on time for launch.
-
-## Horcrux
-
-Horcrux is a [multi-party-computation (MPC)](https://en.wikipedia.org/wiki/Secure_multi-party_computation) signing service for Tendermint nodes.
- 
-- Composed of a cluster of signer nodes in place of the [remote signer](https://docs.tendermint.com/master/nodes/remote-signer.html), thereby enabling High Availability (HA) for block signing through fault tolerance.
-- Secures your validator private key by splitting it across multiple private signer nodes using threshold Ed25519 signatures.
-- Adds security and availability without sacrificing block sign performance.
-
-For information on how to upgrade your validator infrastructure with Horcrux, refer to the [documentation](https://github.com/strangelove-ventures/horcrux/blob/main/docs/migrating.md). 
-
-## Tendermint KMS
-
-Tendermint KMS is a signature service with support for Hardware Security Modules (HSMs), such as YubiHSM 2 and Ledger Nano. It is intended to be run alongside XRP Ledger EVM Sidechain validators, ideally on separate physical hosts, providing defense-in-depth for online validator signing keys, double signing protection, and a central signing service that can be used when running multiple validators in several zones. <!-- SPELLING_IGNORE: kms, hsms, yubihsm, yubikey -->
-
-## Hardware Security Modules (HSM)
-
-You must ensure that an attacker cannot steal a validator's key. Otherwise, the entire stake delegated to the compromised validator at risk. Hardware security modules (HSM) help mitigate this risk.
-
-HSMs must support **`ed25519` signatures for Evmos**. The [YubiHSM 2](https://www.yubico.com/products/hardware-security-module/) supports `ed25519` and can be used with this YubiKey [library](https://github.com/iqlusioninc/yubihsm.rs). <!-- SPELLING_IGNORE: evmos -->
-
-**IMPORTANT**: The YubiHSM can protect a private key but **cannot ensure** in a secure setting that it will not sign the same block twice. <!-- STYLE_OVERRIDE: will -->
-
-## Sentry Nodes (DDOS Protection)
-
-Validators are responsible for ensuring that the network can sustain denial of service attacks.
-
-One recommended way to mitigate these risks is for validators to carefully structure their network topology in a sentry node architecture.
-
-Validator nodes should only connect to full-nodes they trust; either they run these nodes themselves, or the nodes are run by other validator administrators they know personally. A validator node typically runs in a data center. Most data centers provide direct links to the networks of major cloud providers. The validator can use those links to connect to sentry nodes in the cloud. This shifts the burden of denial-of-service from the validator's node directly to its sentry nodes, and might require new sentry nodes be spun up or activated to mitigate attacks on existing ones.
-
-Sentry nodes can be quickly spun up or change their IP addresses. Because the links to the sentry nodes are in private IP space, an internet-based attacked cannot disturb them directly. This ensures that the validator's block proposals and votes always make it to the rest of the network.
-
-To set up your sentry node architecture:
-
-1. Edit your validator node's `config.toml` file:
-
-```sql
-#Comma separated list of nodes to keep persistent connections to
-#Do not add private peers to this list if you don't want them advertised
-persistent_peers =[list of sentry nodes]
-
-# Set true to enable the peer-exchange reactor
-pex = false
-```
-
-2. Edit your sentry node's `config.toml` file:
-
-```sql
-#Comma separated list of peer IDs to keep private (will not be gossiped to other peers)
-#Example ID: 3e16af0cead27979e1fc3dac57d03df3c7a77acc@3.87.179.235:26656
-
-private_peer_ids = "node_ids_of_private_peers"
-```

content/tutorials/interoperability/get-started-evm-sidechain.md

@@ -1,120 +0,0 @@
----
-html: get-started-evm-sidechain.html
-parent: evm-sidechains.html
-blurb: Get started with the EVM compatible sidechain for the XRP Ledger.
-labels:
-  - Development, Interoperability
-status: not_enabled
----
-# Get Started with the EVM Sidechain
-
-{% include '_snippets/evmsc-disclaimer.md' %}
-
-This getting started tutorial walks you through the steps to set up your account and submit a transaction using the EVM sidechain bridge. 
-
-## 1. Create an Account Using an EVM Compatible Wallet
-<!-- STYLE_OVERRIDE: wallet -->
-
-In order to interact with the network, you need to create an account in the EVM sidechain. To create and manage this account you can use any EVM compatible wallet such as MetaMask.
-
-For instructions on how to install and create an account using MetaMask, see [Connect MetaMask to XRP Ledger EVM Sidechain](connect-metamask-to-xrpl-evm-sidechain.html).
-
-
-## 2. Assign your XRP Ledger Devnet Tokens to the EVM Sidechain
-
-Before you can start interacting with the EVM blockchain, you need to assign some of your XRP Ledger Devnet Tokens to the EVM Sidechain. 
-
-To generate tokens in the XRP Ledger Devnet, go to the [XRP Faucets](xrp-testnet-faucet.html) page and click *Generate Devnet credentials* to generate a new Devnet account with some test XRP in it.
-
-![Generate XRP Ledger Devnet credentials](img/evm-sidechain-xrpl-devnet-faucet.png "Generate XRP Ledger Devnet credentials")
-
-Note the address and secret associated with your Devnet address. You need this information to set up your preferred XRP Ledger wallet. 
-
-## 3. Submit a Transaction Using the EVM Sidechain Bridge
-
-Once you have your accounts set up and test fund allocated, submit a transaction to assign some of your test tokens from the XRP Ledger Devnet to the EVM Sidechain using the EVM Sidechain bridge.
-
-The EVM Sidechain bridge is a tool that enables transactions between chains in a fast and secure way.
-
-To start using the bridge, go to [https://bridge.devnet.xrpl.org](https://bridge.devnet.xrpl.org/)
-
-### 1. Connect Both Wallets
-
-**Connect Xumm Wallet**
-
-Use your Xumm wallet to interact with the XRP Ledger Devnet chain. 
-Ensure that you have created an account on the public XRP Ledger Devnet as described in Step 1. 
-
-To connect a Xumm wallet to the bridge, go to the [EVM Sidechain bridge](https://bridge.devnet.xrpl.org) and click “Connect with Xumm Wallet”. 
-
-![Connect XUMM Wallet](img/evm-sidechain-connect-xumm-wallet.png "Connect XUMM wallet")
-
-
-**Note:** Ensure that you are connected to XRP Ledger Devnet and that the application that you are connecting with is the correct one.
-
-Follow the instructions on screen to scan the QR code using the Xumm app. The Xumm wallet app displays a confirmation page.
-
-![Connect to XRP Ledger Devnet](img/evm-sidechain-bridge-sign-in.jpg "Connect to XRP Ledger Devnet")
-
-**Connect MetaMask Wallet**
-
-Use your MetaMask wallet to interact with the XRP Ledger EVM Sidechain. 
-Ensure that you have created a MetaMask account and connected to the public XRP Ledger Devnet as described in [Connect MetaMask to XRP Ledger EVM Sidechain](connect-metamask-to-xrpl-evm-sidechain.html).
-
-To connect a MetaMask wallet to the bridge, go to the [EVM Sidechain bridge](https://bridge.devnet.xrpl.org) and click “Connect with Metamask Wallet”.
-
-![Connect MetaMask Wallet](img/evm-sidechain-connect-metamask.png "Connect MetaMask wallet")
-
-### 2. Start the Transaction 
-
-Now that both Xumm and MetaMask wallets are connected to the bridge, you can select the direction of the bridge, the amount, and the address to fund.
-
-- **Direction of the bridge**: The direction can be either EVM sidechain → XRP Ledger Devnet or XRP Ledger Devnet → EVM sidechain. Use the “Switch Network” button to switch the direction.
-- **From Amount**: This is the transaction amount. Note that there is a fee to use the bridge.
-    - Network fees: The fees required by the network for your transactions.
-    - Commission: The bridge applies a commission for every transaction completed. This is to prevent spam and distributed denial of service attacks (DDOS).
-- **To Address**: The address on the chain where you want the funds.
-
-    ![Start the transaction](img/evm-sidechain-initiate-transfer.png "Start the transaction")
-
-Enter the details for your transaction and click **Transfer**. Review the details of the transaction carefully before accepting the transaction in the corresponding wallet. 
-
-![Approve the transaction](img/evm-sidechain-approve-transaction.png "Approve the transaction")
-
-Depending on the direction of the transaction, you need to approve the transaction in the Xumm Wallet or in the Metamask.
-
-**XRP Ledger Devnet → EVM sidechain**
-
-For this direction you must approve the transaction in your Xumm Wallet. Before doing so, please check that the details are correct:
-
-- Destination address has to be: `radjmEZTb4zsyNUJGV4gcVPXrFTJAuskKa`
-- Memo has to be the same address that you entered in the destination field
-
-    ![Review the transaction](img/evm-sidechain-review-transaction.jpg)
-
-**EVM sidechain → XRP Ledger Devnet**
-
-If this is the case, then you must approve the transaction in your Metamask. Before doing so, please check the details are correct:
-
-- Destination address has to be: `0x8cDE56336E289c028C8f7CF5c20283fF02272182`
-
-    ![Review the transaction in MetaMask](img/evm-sidechain-metamask-confirmation.png "Review the transaction in MetaMask")
-
-
-Once you approve the transaction either in Xumm wallet or in Metamask, a loading screen displays. This process can take up to a few minutes.
-
-![Transaction in progress](img/evm-sidechain-transfer-in-progress.png "Transaction in progress")
-
-### 3. Receive the Funds
-
-Following a few minutes of transaction processing time, you are redirected to the **Transaction Confirmation** screen where you can verify the details of the bridge transaction.
-
-- **Origin transaction hash**: Hash of the transaction in the origin chain.
-- **Destination transaction hash**: Hash of the transaction in the destination chain.
-- **From address**: Address on the origin chain.
-- **To address**: Address on the destination chain.
-- **Receive**: The amount received in the destination address.
-
-![Transaction confirmation](img/evm-sidechain-transaction-confirmation.png "Transaction confirmation")
-
-Your transaction has completed successfully and the test XRP tokens are now available in the other chain.

content/tutorials/interoperability/join-evm-sidechain-devnet.md

@@ -1,121 +0,0 @@
----
-html: join-evm-sidechain-devnet.html
-parent: evm-sidechains.html
-blurb: Learn how to join the XRP Ledger EVM Sidechain Devnet.
-labels:
-  - Development, Interoperability
-status: not_enabled
----
-# Join the XRP Ledger EVM Sidechain Devnet
-
-{% include '_snippets/evmsc-disclaimer.md' %}
-
-This tutorial walks you through the steps to join the existing **XRP Ledger EVM Sidechain Devnet**. 
-
-For ease of use, create an alias, `exprd`, to run all commands inside your Docker container. 
-
-## Pre-requisites
-
-Before proceeding to initialize the node, ensure that the following pre-requisites are installed and running:
-
-* Docker 19+
-* Create an alias to run all commands in this tutorial inside a Docker container: 
-
-    ```bash
-    alias exrpd="docker run -it --rm -v ~/.exrpd:/root/.exrpd peersyst/xrp-evm-client:latest exrpd"
-    ```
-
-## Initialize Node
-
-The first task is to initialize the node, which creates the necessary validator and node configuration files. 
-
-1. Initialize the chain parameters using the following command:
-
-    ```bash
-    exrpd config chain-id exrp_1440001-1
-    ```
-
-2. Create or add a key to your node. For this tutorial, we use the `test` keyring:
-
-    ```bash
-    exrpd keys add <key_name> --keyring-backend test
-    ```
-
-    Note the `key_name` you enter as you need to reference it in subsequent steps.
-
-    **Note** For more information on a more secure setup for your validator, refer to [cosmos-sdk keys and keyrings](https://docs.cosmos.network/v0.46/run-node/keyring.html) and [validator security](evm-sidechain-validator-security.html).
-
-
-3. Initialize the node using the following command:
-
-    ```bash
-    exrpd init <your_custom_moniker> --chain-id exrp_1440001-1
-    ```
-
-    Monikers can contain only ASCII characters. Using Unicode characters renders your node unreachable.
-
-All these commands create your `~/.exrpd` (i.e `$HOME`) directory with subfolders `config/` and `data/`. In the `config` directory, the most important files for configuration are `app.toml` and `config.toml`.
-
-## Genesis & Seeds
-
-1. Copy the Genesis File.
-
-    Download the `genesis.json` file from here and copy it to the `config` directory: `~/.exrpd/config/genesis.json`. This is a genesis file with the chain-id and genesis accounts balances.
-
-        ```bash
-        wget [https://raw.githubusercontent.com/Peersyst/xrp-evm-archive/main/devnet/genesis.json](https://raw.githubusercontent.com/Peersyst/xrp-evm-archive/main/devnet/genesis.json) ~/.exrpd/config/
-        ```
-
-    Verify the genesis configuration file:
-
-        ```bash
-        exrpd validate-genesis
-        ```
-
-2. Add Persistent Peer Nodes
-
-    Set the [`persistent_peer`](https://docs.tendermint.com/master/tendermint-core/using-tendermint.html#persistent-peer)s field in `~/.exrpd/config/config.toml` to specify peers with which your node maintains persistent connections. You can retrieve them from the list of available peers on the archive repo ([https://raw.githubusercontent.com/Peersyst/xrp-evm-archive/main/devnet/peers.txt](https://raw.githubusercontent.com/Peersyst/xrp-evm-archive/main/devnet/peers.txt)).
-
-    To get a list of entries from the `peers.txt` file in the `PEERS` variable, run the following command:
-
-        ```bash
-        PEERS=`curl -sL https://raw.githubusercontent.com/Peersyst/xrp-evm-archive/main/devnet/peers.txt | sort -R | head -n 10 | awk '{print $1}' | paste -s -d, -`
-        ```
-
-    Use `sed` to include them in the configuration. You can also add them manually:
-
-        ```bash
-        sed -i.bak -e "s/^persistent_peers *=.*/persistent_peers = \"$PEERS\"/" ~/.exrpd/config/config.toml
-        ```
-
-## Run a Devnet Validator Node
-
-Run the Devnet validator node using following command:
-
-```bash
-exrpd tx staking create-validator \
-  --amount=1000000000000axrp \
-  --pubkey=$(exrpd tendermint show-validator) \
-  --moniker="<your_custom_moniker>" \
-  --chain-id=<chain_id> \
-  --commission-rate="0.05" \
-  --commission-max-rate="0.20" \
-  --commission-max-change-rate="0.01" \
-  --min-self-delegation="1000000" \
-  --gas="auto" \
-  --gas-prices="0.025axrp" \
-  --from=<key_name>
-```
-
-**Note** For more information on running a validator note, see [Run a validator](evm-sidechain-run-a-validator-node.html)
-
-
-## Start the Node
-
-Start the node. 
-
-```bash
-exrpd start
-```
-
-Once enough voting power (+2/3) from the genesis validators is up-and-running, the node starts producing blocks.

content/tutorials/manage-the-rippled-server/configuration/connect-your-rippled-to-the-xrp-test-net.md

@@ -82,7 +82,7 @@ Edit your `rippled.cfg` file.
 
     <!-- MULTICODE_BLOCK_END -->
 
-    For sidechains and custom networks, everyone who connects to the network should use a value unique to that network. When creating a new network, choose a network ID at random from the integers 11 to 4,294,967,295.
+    For custom networks, everyone who connects to the network should use a value unique to that network. When creating a new network, choose a network ID at random from the integers 11 to 4,294,967,295.
 
     **Note:** This setting helps your server find peers who are on the same network, but it is not a hard control on what network your server follows. The UNL / trusted validator settings (in the next step) are what actually define what network the server follows.
 

dactyl-config.yml

@@ -1071,12 +1071,14 @@ pages:
         targets:
             - ja
 
-    -   md: concepts/consensus-network/federated-sidechains.md
+    # Redirect for now obsolete "Federated Sidechains" page
+    -   name: Federated Sidechains
+        html: federated-sidechains.html
+        template: pagetype-redirect.html.jinja
+        redirect_url: https://opensource.ripple.com/docs/xls-38d-cross-chain-bridge/cross-chain-bridges/
+        nav_omit: true
         targets:
             - en
-
-    -   md: concepts/consensus-network/federated-sidechains.ja.md
-        targets:
             - ja
 
     -   md: concepts/xrpl-servers/xrpl-servers.md
@@ -1155,34 +1157,24 @@ pages:
             - en
             - ja
 
-    -   md: concepts/interoperability/xrpl-interoperability.md
+    # Redirect for "Interoperability" landing page
+    -   name: Interoperability
+        html: xrpl-interoperability.html
+        template: pagetype-redirect.html.jinja
+        redirect_url: https://opensource.ripple.com/docs/xls-38d-cross-chain-bridge/cross-chain-bridges/
+        nav_omit: true
         targets:
             - en
-
-    -   md: concepts/interoperability/xrpl-interoperability.ja.md
-        targets:
             - ja
 
-    -   md: concepts/interoperability/intro-to-evm-sidechain.md
+    # Redirect for "Introduction to EVM Compatible XRP Ledger Sidechain" page
+    -   name: Introduction to EVM Compatible XRP Ledger Sidechain
+        html: intro-to-evm-sidechain.html
+        template: pagetype-redirect.html.jinja
+        redirect_url: https://opensource.ripple.com/docs/evm-sidechain/intro-to-evm-sidechain/
+        nav_omit: true
         targets:
             - en
-
-    -   md: concepts/interoperability/intro-to-evm-sidechain.ja.md
-        targets:
-            - ja
-
-    -   name: Hooks
-        html: https://xrpl-hooks.readme.io/
-        parent: xrpl-interoperability.html
-        blurb: Smart contract proposal for the XRP Ledger.
-        targets:
-            - en
-
-    -   name: Hooks
-        html: https://xrpl-hooks.readme.io/
-        parent: xrpl-interoperability.html
-        blurb: XRP Ledger向けスマートコントラクトの提案。
-        targets:
             - ja
 
     # Redirect old "the-rippled-server.html"
@@ -2240,48 +2232,62 @@ pages:
             - en
             - ja
 
+    # Redirect for "Interoperability - EVM Sidechain" tutorial landing page
     -   name: Interoperability - EVM Sidechain
         html: evm-sidechains.html
-        parent: tutorials.html
+        template: pagetype-redirect.html.jinja
-        blurb: Learn how to interact with the EVM Sidechain Devnet.
+        redirect_url: https://opensource.ripple.com/docs/evm-sidechain/intro-to-evm-sidechain/
-        template: pagetype-category.html.jinja
+        nav_omit: true
-        targets:
-            - en
-
-    -   name: 相互運用性 - EVMサイドチェーン
-        html: evm-sidechains.html
-        parent: tutorials.html
-        blurb: EVM Sidechain Devnetとの接続方法について説明します。
-        template: pagetype-category.html.jinja
-        targets:
-            - ja
-
-        # TODO: translate
-    -   md: tutorials/interoperability/get-started-evm-sidechain.md
         targets:
             - en
             - ja
 
-        # TODO: translate
+    # Redirect for "Get Started with the EVM Sidechain" tutorial page
-    -   md: tutorials/interoperability/connect-metamask-to-xrpl-evm-sidechain.md
+    -   name: Get Started with the EVM Sidechain
+        html: get-started-evm-sidechain.html
+        template: pagetype-redirect.html.jinja
+        redirect_url: https://opensource.ripple.com/docs/evm-sidechain/get-started-evm-sidechain/
+        nav_omit: true
         targets:
             - en
             - ja
 
-        # TODO: translate
+    # Redirect for "Connect MetaMask to XRP Ledger Sidechain" tutorial page
-    -   md: tutorials/interoperability/join-evm-sidechain-devnet.md
+    -   name: Connect MetaMask to XRP Ledger Sidechain
+        html: connect-metamask-to-xrpl-evm-sidechain.html
+        template: pagetype-redirect.html.jinja
+        redirect_url: https://opensource.ripple.com/docs/evm-sidechain/connect-metamask-to-xrpl-evm-sidechain/
+        nav_omit: true
         targets:
             - en
             - ja
 
-        # TODO: translate
+    # Redirect for "Join the XRP Ledger EVM Sidechain Devnet" tutorial page
-    -   md: tutorials/interoperability/evm-sidechain-validator-security.md
+    -   name: Join the XRP Ledger EVM Sidechain Devnet
+        html: join-evm-sidechain-devnet.html
+        template: pagetype-redirect.html.jinja
+        redirect_url: https://opensource.ripple.com/docs/evm-sidechain/join-evm-sidechain-devnet/
+        nav_omit: true
         targets:
             - en
             - ja
 
-        # TODO: translate
+    # Redirect for "EVM Sidechain Validator Security" tutorial page
-    -   md: tutorials/interoperability/evm-sidechain-run-a-validator-node.md
+    -   name: EVM Sidechain Validator Security
+        html: evm-sidechain-validator-security.html
+        template: pagetype-redirect.html.jinja
+        redirect_url: https://opensource.ripple.com/docs/evm-sidechain/evm-sidechain-validator-security/
+        nav_omit: true
+        targets:
+            - en
+            - ja
+
+    # Redirect for "Run a Validator Node on an EVM Sidechain" tutorial page
+    -   name: Run a Validator Node on an EVM Sidechain
+        html: evm-sidechain-run-a-validator-node.html
+        template: pagetype-redirect.html.jinja
+        redirect_url: https://opensource.ripple.com/docs/evm-sidechain/evm-sidechain-run-a-validator-node/
+        nav_omit: true
         targets:
             - en
             - ja

locale/hi/LC_MESSAGES/messages.po

@@ -837,18 +837,6 @@ msgid ""
 "href='docs.html#docs-hot-topic'>proposed standards</a> for issuing NFTs."
 msgstr ""
 
-#: template/page-home.html.jinja:182
-msgid "Sidechains"
-msgstr ""
-
-#: template/page-home.html.jinja:183
-msgid ""
-"Extend, experiment, and specialize a custom sidechain based on the XRPL's"
-" proven blockchain technology. Learn more about <a "
-"href='https://dev.to/ripplexdev/a-vision-for-federated-sidechains-on-the-"
-"xrp-ledger-2o7o' target='_blank'>the vision of sidechains</a>."
-msgstr ""
-
 #: template/page-home.html.jinja:201
 #, fuzzy
 msgid "XRPL.org: by the community, for the community"

locale/ja/LC_MESSAGES/messages.po

@@ -1248,21 +1248,6 @@ msgstr ""
 "手数料の低減、取引の高速化、カスタムトークンの機能性により、XRPLはNFTのエコシステム構築に理想的なものとなっています。NFT発行のための<a"
 " href='docs.html#docs-hot-topic'>提案されている標準規格</a>を参照してください。"
 
-#: template/page-home.html.jinja:182
-msgid "Sidechains"
-msgstr "サイドチェーン"
-
-#: template/page-home.html.jinja:183
-msgid ""
-"Extend, experiment, and specialize a custom sidechain based on the XRPL's"
-" proven blockchain technology. Learn more about <a "
-"href='https://dev.to/ripplexdev/a-vision-for-federated-sidechains-on-the-"
-"xrp-ledger-2o7o' target='_blank'>the vision of sidechains</a>."
-msgstr ""
-"XRPLの実績あるブロックチェーン技術をベースに、カスタムサイドチェーンを拡張、実験、特化させます。詳しくは<a "
-"href='https://dev.to/ripplexdev/a-vision-for-federated-sidechains-on-the-"
-"xrp-ledger-2o7o' target='_blank'>サイドチェーンのビジョン</a>。"
-
 #: template/page-home.html.jinja:201
 #, fuzzy
 msgid "XRPL.org: by the community, for the community"

locale/messages.pot

@@ -1168,18 +1168,6 @@ msgid ""
 "href='docs.html#docs-hot-topic'>proposed standards</a> for issuing NFTs."
 msgstr ""
 
-#: template/page-home.html.jinja:182
-msgid "Sidechains"
-msgstr ""
-
-#: template/page-home.html.jinja:183
-msgid ""
-"Extend, experiment, and specialize a custom sidechain based on the XRPL's"
-" proven blockchain technology. Learn more about <a "
-"href='https://dev.to/ripplexdev/a-vision-for-federated-sidechains-on-the-"
-"xrp-ledger-2o7o' target='_blank'>the vision of sidechains</a>."
-msgstr ""
-
 #: template/page-home.html.jinja:201
 msgid "XRPL.org: by the community, for the community"
 msgstr ""

template/page-home.html.jinja

@@ -174,14 +174,10 @@
           "title":  _("Smart Contracts"),
           "description":  _("Hooks are small, efficient WebAssembly modules designed specifically for the XRPL. Check out the <a href='https://hooks-testnet.xrpl-labs.com/' target='_blank'>hooks amendment and public testnet</a> that enable smart contract functionality."),
           "href": "https://hooks-testnet.xrpl-labs.com/" },
-        { "chip": _("In Development"),
+        { "chip": _("Enabled"),
           "title":  _("Non-Fungible Tokens"),
           "description":  _("Lower fees, faster transactions, and custom token functionality make the XRPL ideally suited for building an ecosystem for NFTs. Explore <a href='docs.html#docs-hot-topic'>proposed standards</a> for issuing NFTs."),
           "href": "docs.html#docs-hot-topic"},
-        { "chip": _("In Development"),
-          "title":  _("Sidechains"),
-          "description":  _("Extend, experiment, and specialize a custom sidechain based on the XRPL's proven blockchain technology. Learn more about <a href='https://dev.to/ripplexdev/a-vision-for-federated-sidechains-on-the-xrp-ledger-2o7o' target='_blank'>the vision of sidechains</a>."),
-          "href": "https://dev.to/ripplexdev/a-vision-for-federated-sidechains-on-the-xrp-ledger-2o7o"},
       ] %}
       {% for feat in features %}
       <li class="col ls-none pt-2">

template/page-uses.html.jinja

@@ -370,10 +370,6 @@
             "title": _("Developer Tooling"),
             "description": _("Developers can leverage open-source libraries, SDKs and more to help build their project and access essential XRP Ledger functionality.")},
 
-          {"id": "interoperability",
-            "title": _("Interoperability"),
-            "description": _("Developers and node operators can build and run custom sidechains while leveraging the XRPL’s lean and efficient feature set.")},
-
           {"id": "wallet",
             "title": _("Wallet"),
             "description": _("Build digital wallets to store passwords and interact with various blockchains to send and receive digital assets, including XRP.")},