diff --git a/@i18n/es-ES/docs/introduction/crypto-wallets.md b/@i18n/es-ES/docs/introduction/crypto-wallets.md
index 0a0706f434..3c5948295f 100644
--- a/@i18n/es-ES/docs/introduction/crypto-wallets.md
+++ b/@i18n/es-ES/docs/introduction/crypto-wallets.md
@@ -21,7 +21,7 @@ Para los pagos del día a día, esto puede ser preferible, ya que este tipo de c

-Una cartera sin custodia, como [XUMM](https://xumm.app/), es aquella donde tienes las claves secretas (secret keys) de tu cuenta. Esto significa que eres el último reponsable de la administración de la seguridad de tu cuenta.
+Una cartera sin custodia, como [Xaman](https://Xaman.app/), es aquella donde tienes las claves secretas (secret keys) de tu cuenta. Esto significa que eres el último reponsable de la administración de la seguridad de tu cuenta.
**Atención:** Si pierdes tus claves, perderás el acceso a tu cuenta del XRP Ledger y no hay opciones de recupereación.
diff --git a/@i18n/es-ES/translations.yaml b/@i18n/es-ES/translations.yaml
index 82473c34d2..e7002f13a3 100644
--- a/@i18n/es-ES/translations.yaml
+++ b/@i18n/es-ES/translations.yaml
@@ -293,7 +293,7 @@ Ripple's On-Demand Liquidity: On-Demand Liquidity de Ripple
Exchanges: Exchanges
XRPL Rosetta explores fiat data on XRPL through visualization.: XRPL Rosetta explora datos de dinero fiat en el XRPL a través de la visualización
XRPL.org's Ledger Explorer is a block explorer of the XRP Ledger.: El explorador de ledgers de XRPL.org es el explorador de bloques para el XRP Ledger
-Xumm Wallet is a non custodial wallet with superpower for the XRP Ledger.: Xumm Wallet es una cartera sin custodia con superpoderes para el XRP Ledger
+Xaman is a non custodial wallet with superpower for the XRP Ledger.: Xaman es una cartera sin custodia con superpoderes para el XRP Ledger
Web Monetization: Monetización web
Sustainability: Sostenibilidad
CBDCs: CBDC
diff --git a/@i18n/ja/docs/concepts/xrpl-sidechains/index.md b/@i18n/ja/docs/concepts/xrpl-sidechains/index.md
index 3f5f0ef240..322993ad62 100644
--- a/@i18n/ja/docs/concepts/xrpl-sidechains/index.md
+++ b/@i18n/ja/docs/concepts/xrpl-sidechains/index.md
@@ -26,46 +26,4 @@ _([XChainBridge Amendment][] {% not-enabled /%} が必要です)_
- サイドチェーンは独自のバリデータを使い、メインチェーンの `rippled` UNL とは別のUNLを必要とします。
- メインチェーンとサイドチェーンのノードはお互いを認識していません。
-
-## よくある質問
-
-### サイドチェーンとは?
-
-サイドチェーンとは、XRPLメインネットチェーン(以下「メインチェーン」)とサイドチェーン(それぞれ「サイドチェーン」)をつなぐ別のブロックチェーンで、資産や 情報のクロスチェーン交換を可能にします。
-
-
-### Witnessサーバとは?
-
-「Witnessサーバ」(証人サーバ)は、メインチェーンと各サイドチェーンをつなぐ「ドアアカウント」間の送金を検証します。 一連の非中央集権的な組織や個人がWitnessサーバを運営します。
-
-
-### Witnessサーバの運用に伴うリスクはありますか?
-
-サイドチェーンのWitnessサーバの運用には、次のようなリスクがあります。
-
-_規制上の考慮事項_ : Witnessサーバの運用には規制上のリスクが伴います。以下にいくつかのリスクを示しますが、そのうちのいくつかは、米国に所在する人々にサービスを提供するプロジェクトにのみ適用される規制制度に関するものです。
-
-米国では、マネーサービスビジネス(「MSB」)としての連邦政府の登録と州のマネートランスミッタライセンス(「MTL」)を必要とする「マネートランスミッタビジネス」の運営に関する規制体制が、Witnessサーバの運営に適用されるかどうか不明確です。Witnessサーバは、一連の分散化された事業体および個人によって運営されることを意図しています。このような意図にもかかわらず、規制当局が、特定の事業体または調整グループによるWitnessサーバの「中央集権的な」コントロールがあると判断した場合、そのような活動を資金移動とみなす可能性があります。米国財務省は最近、特定のプロジェクトが"分散型"かどうかを判断する際に考慮する一連の要素を特定する報告書を発表しました。[2023 DeFi Illicit Finance Risk Assessment](https://home.treasury.gov/news/press-releases/jy1391)をご覧ください。この最新の規制ガイダンスは、米国財務省が特定のプロジェクトが"分散型"である可能性があり、Witnessサーバの運用が"分散型"である場合、"資金移動業”とみなされない可能性があることを認識していることを示すものであり、重要です。
-
-米国の暗号規制は一貫して最も厳しく、積極的に運用されていますが、他の法域でも「資金」やその他の価値の移転に関する規制や法律が存在します。例えば、英国の規制当局は2022年3月、暗号と分散型金融に関する一連の文書ガイダンスを発表しました。[Financial Stability in Focus: Cryptoassets and Decentralized Finance](https://www.bankofengland.co.uk/financial-stability-in-focus/2022/march-2022)をご覧ください。さらに最近では、2023年6月、E.U.は、分散型暗号プラットフォームに関連する成文化された規則や規制を一部課す規制枠組みを正式に採択しました。[Markets in Crypto-Assets Regulation](https://www.esma.europa.eu/esmas-activities/digital-finance-and-innovation/markets-crypto-assets-regulation-mica)をご覧ください。Witnessサーバの運用を検討されている方は、関連するリスクへ適切に対処するため、関係する各法域の具体的な要件について常に情報を入手し、遵守することが重要です。
-
-_テクノロジーおよびネットワークセキュリティ_:Witnessサーバを運用しようとする者は、その技術的およびセキュリティ的な側面を熟知している必要があります。Witnessサーバの運用に参加する前に、その機能、潜在的な脆弱性、必要な技術的およびセキュリティ対策について十分に理解しておく必要があります。
-
-_民事責任_ : 米国やその他の管轄区域では原告による訴訟が急増しており、特定の原告側弁護士が民事訴訟でどのような理論を実行するかを評価することは困難です。現実の民事責任リスクと認識されている民事責任リスクの如何にかかわらず、軽薄な訴訟であっても対応に時間と費用がかかる可能性があることに留意する必要があります。
-
-
-### Witnessサーバの運営に参加する前に、第三者の助言を求めるべきでしょうか?
-
-はい。Witnessサーバの運営を検討している当事者は、経験豊富な専門家から独立した法律上および税務上のアドバイスを受ける必要があります。Witnessサーバは、クロスチェーン送金を確認するために相互に検証する必要があるため、米国の規制当局によって定義されている共通企業として運営されていると理解される可能性があることにご注意ください。共通企業では、連帯責任が適用される場合があります。つまり、各Witnessサーバは、発生したすべての責任または損害に対して個別に責任を負う可能性があります。今後ますます変化する規制の状況を考慮すると、Witnessサーバを運営する上での期待や義務に関連する複雑で変化する世界的な規制の状況をナビゲートできる法律の専門家に相談することが非常に重要です。他のブロックチェーンプロジェクトと同様、ご自身で調査を行ってください。これらのFAQは一般的なガイダンスであり、法律や税務に関するアドバイスではありません。
-
-
-### Witnessサーバを運用すべきでないのはどのような人ですか?
-
-ブロックチェーン、MSBおよびMTLの規制、その他の適用される規制および法律に関する経験がない(または経験豊富なサポートを利用できない)場合は、Witnessサーバを運用しないでください。また、技術およびコンプライアンスに関する専門知識を有する経験豊富な個人または団体でない場合も、Witnessサーバを運用しないでください。個人でWitnessサーバを運用するのに十分な資格と経験を持つ人はほとんどいません。また、独立した法律上および税務上の助言を求め、得ていない場合は、Witnessサーバを運用しないでください。
-
-
-### これらのFAQは包括的で明確なアドバイスですか?
-
-これらのFAQは、一般的なガイダンスを提供することを目的としており、技術的、財務的、または法的なアドバイスを提供するものではありません。これらのFAQは、各自の具体的な状況に合わせた専門的なアドバイスの代わりとして使用すべきではありません。ブロックチェーンとデジタル資産の状況は複雑で常に変化しているため、常に最新の情報を入手し、専門家の助言を求める必要があります。サイドチェーンに関わる者は、政府や規制機関のWebサイトなどの公式リソースを定期的にチェックすることをお勧めします。とはいえ、ブロックチェーンや暗号通貨を専門とする法律専門家に相談することが、正確で個別のアドバイスを得るための最も信頼できる方法です。
-
{% raw-partial file="/docs/_snippets/common-links.md" /%}
diff --git a/@i18n/ja/docs/concepts/xrpl-sidechains/price-oracles.md b/@i18n/ja/docs/concepts/xrpl-sidechains/price-oracles.md
new file mode 100644
index 0000000000..48551a5ca0
--- /dev/null
+++ b/@i18n/ja/docs/concepts/xrpl-sidechains/price-oracles.md
@@ -0,0 +1,41 @@
+# 価格オラクル
+
+_([PriceOracle Amendment][] {% not-enabled /%} が必要です。)_
+
+ブロックチェーンは、本質的にネットワーク外で何が起こっているのかを把握することはできませんが、分散型金融における多くのユースケースでは、この情報が必要となります。
+
+価格オラクルは、この問題を解決します。オラクルとは、市場価格、為替レート、金利などの実世界の情報を収集し、それをブロックチェーンに伝達するサービスまたはテクノロジーです。ブロックチェーンと同様に、ほとんどのオラクルも分散型であり、複数のノードを通じてデータの検証を行います。
+
+{% admonition type="info" name="注記" %}
+
+一般的に、オラクルは金融情報に限らず、あらゆる種類の情報を提供することができます。例えば、どのスポーツチームが試合に勝ったか、あるいは天気などもです。しかし、XRP Ledgerの価格オラクル機能は、特に資産価格の提供を目的として設計されています。
+
+{% /admonition %}
+
+
+## オラクルの仕組み
+
+ほとんどのオラクルブロックチェーンのやり取りは、次のような仕組みになっています。
+
+1. データは分散型オラクルネットワークによってオフチェーンで検証されます。
+2. データはブロックチェーンに送信されます。
+3. ブロックチェーンはその情報を使用して、エスクローからの資金放出などのスマートコントラクトを実行します。
+
+このプロセスは逆方向にも機能し、トランザクション情報を外部システムにプッシュすることも可能です。
+
+
+## XRP Ledgerの価格オラクル
+
+XRPLの価格オラクルはネイティブのオンチェーンオラクルであり、XRP LedgerのネイティブDeFi機能を強化します。オフチェーン価格オラクルは、そのデータをXRPLオラクルに送信し、XRPLオラクルはオンチェーンにその情報を保存します。これにより、分散型アプリケーションは価格データについてXRPLオラクルに問い合わせることが可能になります。複数のXRPLオラクルに問い合わせることで、リスクと不正確性を最小限に抑えることができます。
+
+このように価格フィードを標準化することで、すべての XRPL アプリが信頼できる共有データソースにアクセスできるようになります。
+
+## 関連項目
+
+- **リファレンス:**
+ - [get_aggregate_priceメソッド][]
+ - [Oracleエントリ][]
+ - [OracleDeleteトランザクション][]
+ - [OracleSetトランザクション][]
+
+{% raw-partial file="/docs/_snippets/common-links.md" /%}
diff --git a/@i18n/ja/docs/introduction/crypto-wallets.md b/@i18n/ja/docs/introduction/crypto-wallets.md
index f1fbb12099..b37c206dab 100644
--- a/@i18n/ja/docs/introduction/crypto-wallets.md
+++ b/@i18n/ja/docs/introduction/crypto-wallets.md
@@ -21,7 +21,7 @@ labels:

-[XUMM](https://xumm.app/)のようなノンカストディアルウォレットは、あなたのアカウントの秘密鍵をあなた自身が管理するものです。つまり、アカウントのセキュリティを管理する最終的な責任はあなたにあるのです。
+[Xaman](https://xaman.app/)のようなノンカストディアルウォレットは、あなたのアカウントの秘密鍵をあなた自身が管理するものです。つまり、アカウントのセキュリティを管理する最終的な責任はあなたにあるのです。
**注意:** もしキーを紛失した場合、あなたはXRP Ledgerのアカウントから切り離されてしまい、回復の方法はありません。
diff --git a/@i18n/ja/docs/references/protocol/ledger-data/common-fields.md b/@i18n/ja/docs/references/protocol/ledger-data/common-fields.md
index e77d2738fb..27187841b4 100644
--- a/@i18n/ja/docs/references/protocol/ledger-data/common-fields.md
+++ b/@i18n/ja/docs/references/protocol/ledger-data/common-fields.md
@@ -32,7 +32,7 @@ seo:
## フラグ
-フラグはオン/オフ設定で、ビットOR演算を使用して1つの数値に結合されるバイナリ値として表されます。レジャーエントリのフラグのビット値は、トランザクションでそれらのフラグを有効または無効にするために使用される値とは異なります。レジャーの状態フラグには、**lsf`**で始まる名前があります。
+フラグはオン/オフ設定で、ビットOR演算を使用して1つの数値に結合されるバイナリ値として表されます。レジャーエントリのフラグのビット値は、トランザクションでそれらのフラグを有効または無効にするために使用される値とは異なります。レジャーの状態フラグには、**`lsf`**で始まる名前があります。
フラグフィールドに指定できる値は、レジャーエントリのタイプによって異なります。一部のレジャーエントリのタイプでは、フラグが定義されていません。このような場合、`Flags`フィールドは常に値`0`になります。
diff --git a/@i18n/ja/docs/references/protocol/ledger-data/ledger-entry-types/oracle.md b/@i18n/ja/docs/references/protocol/ledger-data/ledger-entry-types/oracle.md
new file mode 100644
index 0000000000..e838d2e05d
--- /dev/null
+++ b/@i18n/ja/docs/references/protocol/ledger-data/ledger-entry-types/oracle.md
@@ -0,0 +1,93 @@
+# Oracle
+
+_([PriceOracle Amendment][] {% not-enabled /%} が必要です。)_
+
+[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/impl/LedgerFormats.cpp#L353-L366 "ソース")
+
+Oracleのレジャーエントリには、単一資産の価格オラクルオブジェクトに関連するデータが格納されています。
+
+{% admonition type="info" name="注記" %}
+
+価格オラクルオブジェクトは、最大10個のトークンペアの情報を格納できます。
+
+{% /admonition %}
+
+
+## OracleのJSONの例
+
+```json
+{
+ "LedgerEntryType": "Oracle",
+ "Owner": "rNZ9m6AP9K7z3EVg6GhPMx36V4QmZKeWds",
+ "Provider": "70726F7669646572",
+ "AssetClass": "63757272656E6379",
+ "PriceDataSeries": [
+ {
+ "PriceData": {
+ "BaseAsset": "XRP",
+ "QuoteAsset": "USD",
+ "AssetPrice": 740,
+ "Scale": 3,
+ }
+ },
+ ],
+ "LastUpdateTime": 1724871860,
+ "PreviousTxnID": "C53ECF838647FA5A4C780377025FEC7999AB4182590510CA461444B207AB74A9",
+ "PreviousTxnLgrSeq": 3675418
+}
+```
+
+
+## Oracleのフィールド
+
+| フィールド | JSONの型 | 内部の型 | 必須? | 説明 |
+|---------------------|-----------|---------------|-----------|-------------|
+| `Owner` | 文字列 | AccountID | はい | オラクルの更新および削除権限を持つXRPLアカウント。このアカウントで[マルチシグ](../../../../tutorials/how-tos/manage-account-settings/set-up-multi-signing)を設定することをお勧めします。 |
+| `Provider` | 文字列 | Blob | はい | オラクルプロバイダーを識別する任意の値、例えば、Chainlink、Band、またはDIAなど。このフィールドは、最大256文字のASCII 16進エンコード文字(0x20-0x7E)の文字列です。 |
+| `PriceDataSeries` | 配列 | Array | はい | トークンペアの価格情報を表す、最大10個の`PriceData`オブジェクトの配列。`PriceData`オブジェクトが5個を超える場合、2つの所有者準備金が必要です。 |
+| `LastUpdateTime` | 数値 | UInt32 | はい | Unix時間で表現された、データの最終更新時刻。 |
+| `URI` | 文字列 | Blob | いいえ | 任意で指定可能なユニバーサルリソース識別子で、チェーン外の価格データを参照します。このフィールドは256バイトに制限されています。 |
+| `AssetClass` | 文字列 | Blob | はい | 「通貨」、「商品」、「指数」などの資産の種類を説明します。このフィールドは、最大16文字のASCII 16進コード文字(0x20-0x7E)の文字列です。 |
+| `OwnerNode` | 文字列 | UInt64 | はい | ディレクトリが複数のページで構成されている場合、このエントリにリンクしているオラクル所有者のオーナーディレクトリのページを示すヒント。 |
+| `PreviousTxnID` | 文字列 | UInt256 | はい | このエントリを変更した前回のトランザクションのハッシュ値。 |
+| `PreviousTxnLgrSeq` | 文字列 | UInt32 | はい | このエントリが最後に変更または作成されたレジャーのインデックス。 |
+
+
+### PriceDataのフィールド
+
+| フィールド | JSONの型 | 内部の型 | 必須? | 説明 |
+|---------------------|-----------|---------------|-----------|-------------|
+| `BaseAsset` | 文字列 | Currency | はい | 取引ペアにおける基軸となる資産。株式シンボル、債券CUSIP、通貨コードなど、有効な識別子であれば何でも使用できます。 |
+| `QuoteAsset` | 文字列 | Currency | はい | 取引ペアにおける見積資産。見積資産は、基軸資産の1単位の価格を示します。 |
+| `AssetPrice` | 数値 | UInt64 | いいえ | `Scale`の精度レベルを適用した後の資産価格。最後の更新トランザクションに`BaseAsset`/`QuoteAsset`のペアが含まれていなかった場合は、含まれません。|
+| `Scale` | 数値 | UInt8 | いいえ | 資産価格に適用するスケーリング値。例えば、`Scale`が6で元の価格が0.155の場合、スケーリング後の価格は155000となります。有効な範囲は0~10です。最後の更新トランザクションに`BaseAsset`/`QuoteAsset`のペアが含まれていない場合は、含まれません。 |
+
+
+## Oracleの準備金
+
+Oracleオブジェクトは、1~5個のPriceDataオブジェクトを含む場合は1つの[所有者準備金](../../../../concepts/accounts/reserves.md#基本準備金と所有者準備金)としてカウントされ、6~10個のPriceDataオブジェクトを含む場合は2つとしてカウントされます。
+
+## Oracle IDのフォーマット
+
+OracleオブジェクトのIDは、以下の値を順番に連結した[SHA-512Half][]です。
+
+1. `Oracle`スペースキーy (`0x52`)
+2. `Owner`のAccountID.
+3. `OracleDocumentID`.
+
+## Currencyの内部フォーマット
+
+`Currency`フィールドタイプには、通貨または資産コードを表す160ビットの任意データが含まれています。データがXRPLの[通貨コード][]の標準フォーマットに一致する場合、APIはそれを"`USD`"などの文字列として表示します。一致しない場合は、40文字の16進数として表示されます。以下のJSONの例は、`912810RR9/USD`の取引ペアを表しています。`BaseAsset`はCUSIPコードの912810RR9を16進数文字列で表したものであり、`QuoteAsset`は標準の通貨コードであるUSDです。
+
+```json
+{
+ "PriceData" : {
+ "BaseAsset" : "3931323831305252390000000000000000000000",
+ "QuoteAsset" : "USD",
+ "Scale" : 1,
+ "SymbolPrice" : 740
+ }
+}
+```
+
+{% raw-partial file="/docs/_snippets/common-links.md" /%}
diff --git a/@i18n/ja/docs/references/protocol/transactions/common-fields.md b/@i18n/ja/docs/references/protocol/transactions/common-fields.md
index c47a3d94a0..45bc47800d 100644
--- a/@i18n/ja/docs/references/protocol/transactions/common-fields.md
+++ b/@i18n/ja/docs/references/protocol/transactions/common-fields.md
@@ -131,15 +131,15 @@ MemoTypeフィールドとMemoFormatフィールドには、以下の文字の
`NetworkID`フィールドは「クロスチェーン」トランザクションのリプレイ攻撃に対する保護であり、同じトランザクションがコピーされ、意図していない[ネットワーク](../../../concepts/networks-and-servers/parallel-networks.md)で実行されることを防ぎます。既存のチェーンとの互換性のため、ネットワークIDが1024以下のネットワークでは`NetworkID`フィールドを省略する必要がありますが、ネットワークIDが1025以上のネットワークでは`NetworkID`フィールドを含める必要があります。以下の表は、さまざまな既知のネットワークのステータスと値を示しています。
-| ネットワーク | ID | `NetworkID`フィールド |
-|---------------|----|---------------------|
-| Mainnet | 0 | 使用不可 |
-| Testnet | 1 | 使用不可 |
-| Devnet | 2 | 使用不可 |
-| AMM Devnet | 25 | 使用不可 |
-| Sidechains Devnet Locking Chain | 2551 | 使用不可, ただし、アップデート後に必要となる予定です。 |
-| Sidechains Devnet Issuing Chain | 2552 | 使用不可, ただし、アップデート後に必要となる予定です。 |
-| Hooks V3 Testnet | 21338 | 必須 |
+| ネットワーク | ID | `NetworkID`フィールド |
+| ------------------------------- | ----- | ----------------------------------------------------- |
+| Mainnet | 0 | 使用不可 |
+| Testnet | 1 | 使用不可 |
+| Devnet | 2 | 使用不可 |
+| Batch Testnet | 21336 | 必須 |
+| Xahau Mainnet | 21337 | 必須 |
+| Xahau Testnet | 21338 | 必須 |
+| JS Hooks Testnet | 31338 | 必須 |
トランザクションのリプレイ攻撃は理論的には可能ですが、2つ目のネットワークに特定の条件が必要です。次のすべてが真でなければなりません。
diff --git a/@i18n/ja/docs/references/protocol/transactions/types/oracledelete.md b/@i18n/ja/docs/references/protocol/transactions/types/oracledelete.md
new file mode 100644
index 0000000000..1588bfd982
--- /dev/null
+++ b/@i18n/ja/docs/references/protocol/transactions/types/oracledelete.md
@@ -0,0 +1,44 @@
+---
+html: oracledelete.html
+parent: transaction-types.html
+blurb: 既存の価格オラクルを削除します。
+labels:
+ - オラクル
+status: not_enabled
+---
+# OracleDelete
+_([PriceOracle Amendment][] {% not-enabled /%} が必要です。)_
+
+[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/app/tx/impl/DeleteOracle.cpp "ソース")
+
+既存の`Oracle`レジャーエントリを削除します。
+
+
+## OracleDeleteのJSONの例
+
+```json
+{
+ "TransactionType": "OracleDelete",
+ "Account": "rsA2LpzuawewSBQXkiju3YQTMzW13pAAdW",
+ "OracleDocumentID": 34
+}
+```
+
+
+## OracleDeleteのフィールド
+
+| フィールド | JSONの型 | 内部の型 | 必須? | 説明 |
+|--------------------|-----------|---------------|-----------|-------------|
+| `Account` | 文字列 | AccountID | はい | このアカウントは、`Oracle`オブジェクトの`Owner`フィールドのアカウントと一致する必要があります。 |
+| `OracleDocumentID` | 文字列 | UInt32 | はい | `Account`の価格オラクルの一意の識別子。 |
+
+
+## エラーのケース
+
+すべてのトランザクションで発生するエラーに加えて、`OracleDelete`トランザクションでは次のトランザクション結果コードが発生する可能性があります。
+
+| エラーコード | 説明 |
+|---------------|-------------|
+| `tecNO_ENTRY` | `Oracle`オブジェクトが存在しません。 |
+
+{% raw-partial file="/docs/_snippets/common-links.md" /%}
diff --git a/@i18n/ja/docs/references/protocol/transactions/types/oracleset.md b/@i18n/ja/docs/references/protocol/transactions/types/oracleset.md
new file mode 100644
index 0000000000..8a56387528
--- /dev/null
+++ b/@i18n/ja/docs/references/protocol/transactions/types/oracleset.md
@@ -0,0 +1,88 @@
+---
+html: OracleSet.html
+parent: transaction-types.html
+blurb: 価格オラクルを作成または更新します。
+labels:
+ - オラクル
+status: not_enabled
+---
+# OracleSet
+_([PriceOracle Amendment][] {% not-enabled /%} が必要です。)_
+
+[[ソース]](https://github.com/XRPLF/rippled/blob/master/src/ripple/app/tx/impl/SetOracle.cpp "ソース")
+
+Oracle Document ID を使用して、新しい`Oracle`レジャーエントリを作成するか、既存のフィールドを更新します。
+
+
+## OracleSetのJSONの例
+
+```json
+{
+ "TransactionType": "OracleSet",
+ "Account": "rNZ9m6AP9K7z3EVg6GhPMx36V4QmZKeWds",
+ "OracleDocumentID": 34,
+ "Provider": "70726F7669646572",
+ "LastUpdateTime": 1724871860,
+ "AssetClass": "63757272656E6379",
+ "PriceDataSeries": [
+ {
+ "PriceData": {
+ "BaseAsset": "XRP",
+ "QuoteAsset": "USD",
+ "AssetPrice": 740,
+ "Scale": 3
+ }
+ }
+ ]
+}
+```
+
+
+## OracleSetのフィールド
+
+| フィールド | JSONの型 | 内部の型 | 必須? | 説明 |
+|--------------------|-----------|---------------|--------|-------------|
+| `Account` | 文字列 | AccountID | はい | このアカウントは、`Oracle`オブジェクトの`Owner`フィールドのアカウントと一致する必要があります。 |
+| `OracleDocumentID` | Number | UInt32 | はい | `Account`の価格オラクルのユニークな識別子。 |
+| `Provider` | 文字列 | Blob | 可変 | Oracleプロバイダを識別する任意の値、例えばChainlink、Band、またはDIAなど。このフィールドは文字列で、ASCII 16進コード化文字(0x20~0x7E)を最大256文字まで使用できます。このフィールドは、新しい`Oracle`レジャーエントリを作成する際に必須ですが、更新の場合は任意です。 |
+| `URI` | 文字列 | Blob | いいえ | 任意で指定可能なユニバーサルリソース識別子で、チェーン外の価格データを参照します。このフィールドは256バイトに制限されています。 |
+| `LastUpdateTime` | Number | UInt32 | はい | データが最後に更新された時刻を、[リップルエポックからの秒数]で表します。 |
+| `AssetClass` | 文字列 | Blob | 可変 | 「通貨」、「商品」、「指数」などの資産の種類を指定します。このフィールドは、最大16文字のASCII 16進コード文字(0x20~0x7E)の文字列です。このフィールドは、新しい`Oracle`レジャーエントリを新規作成する際に必須ですが、更新の場合は任意です。 |
+| `PriceDataSeries` | Array | Array | はい | トークンペアの価格情報を表す、最大10個の`PriceData`オブジェクトの配列。`PriceData`が5個を超える場合は、2つの所有者準備金が必要です。 |
+
+
+### PriceDataのフィールド
+
+| フィールド | JSONの型 | 内部の型 | 必須? | 説明 |
+|---------------------|-----------|---------------|--------|-------------|
+| `BaseAsset` | 文字列 | Currency | はい | 取引ペアにおける基軸資産。 株式シンボル、債券CUSIP、通貨コードなど、有効な識別子であれば何でも使用できます。 例えば、BTC/USDペアではBTCが基軸資産であり、912810RR9/BTCでは912810RR9が基軸資産です。 |
+| `QuoteAsset` | 文字列 | Currency | はい | 取引ペアにおける見積資産。見積資産は、ベース資産の1単位の価格を示します。例えば、BTC/USDペアでは、USDが見積資産です。912810RR9/BTCでは、BTCが見積資産です。 |
+| `AssetPrice` | 数値 | UInt64 | いいえ | `Scale`レベルを適用した後の資産価格。含まれていない場合、対応するPriceDataは削除されます。 |
+| `Scale` | 数値 | UInt8 | いいえ | 資産価格に適用するスケーリング値。例えば、`Scale`が6で元の価格が 0.155 の場合、スケーリング後の価格は155000となります。有効なスケール範囲は0~10です。デフォルト値は0です。 |
+
+`PriceData`は、以下のルールに従って作成または更新されます。
+
+- トランザクション内の新しいトークンペアがオブジェクトに追加されます。
+- トランザクション内のトークンペアが、オブジェクト内の対応するトークンペアを上書きします。
+- `AssetPrice` フィールドが存在しないトランザクションのトークンペアは、オブジェクト内の対応するトークンペアを削除します。
+- オブジェクトのみに存在するトークンペアは、価格が古くなっていることを示すために、`AssetPrice`と`Scale`が削除されます。
+
+{% admonition type="info" name="注記" %}
+トランザクション内のトークンペアの順序は重要ではありません。なぜなら、各トークンペアは`PriceDataSeries`内の`PriceData`オブジェクトの場所を一意に識別するからです。
+{% /admonition %}
+
+
+## エラーケース
+
+すべてのトランザクションで発生しうるエラーの他に、`OracleSet`トランザクションでは以下のトランザクション結果コードが発生する可能性があります。
+
+| エラーコード | 説明 |
+|---------------------------|-------------|
+| `temARRAY_EMPTY` | `PriceDataSeries`に`PriceData`オブジェクトがありません。 |
+| `tecARRAY_TOO_LARGE` | `PriceDataSeries`が10個の`PriceData`オブジェクトの制限を超えています。 |
+| `tecINVALID_UPDATE_TIME` | `Oracle`オブジェクトに有効な`LastUpdateTime`値がありません。 |
+| `tecTOKEN_PAIR_NOT_FOUND` | 削除しようとしているトークンペアが`Oracle`オブジェクトに存在しません。 |
+| `tecARRAY_EMPTY` | `PriceDataSeries`に`PriceData`オブジェクトがありません。 |
+| `temARRAY_TOO_LARGE` | `PriceDataSeries`が10個の`PriceData`オブジェクトの制限を超えています。 |
+
+{% raw-partial file="/docs/_snippets/common-links.md" /%}
diff --git a/@i18n/ja/docs/use-cases/tokenization/digital-artist.md b/@i18n/ja/docs/use-cases/tokenization/digital-artist.md
index 262cc1009a..6ee83413de 100644
--- a/@i18n/ja/docs/use-cases/tokenization/digital-artist.md
+++ b/@i18n/ja/docs/use-cases/tokenization/digital-artist.md
@@ -16,7 +16,7 @@ NFTokenを作成すると、実際の物理的またはデジタル資産の実
デジタルアーティストとして、あなたはNFTの作成に専念しており、おそらくXRP Ledgerで販売するためでしょう(自分の作品の実績を証明する方法としてNFTを作成する可能性もありますね)。
-[Xumm](https://xumm.app)などのアプリを使用してNFTokenを作成することができます。
+[Xaman](https://xaman.app)などのアプリを使用してNFTokenを作成することができます。
より実践的な体験をしたい方は、[クイックスタート・チュートリアル3 - NFTokenのミントとバーン](../../tutorials/javascript/nfts/mint-and-burn-nfts.md)をご覧ください。
diff --git a/@i18n/ja/docs/use-cases/tokenization/nft-mkt-overview.md b/@i18n/ja/docs/use-cases/tokenization/nft-mkt-overview.md
index b2ed76d2ad..7e304f4bf0 100644
--- a/@i18n/ja/docs/use-cases/tokenization/nft-mkt-overview.md
+++ b/@i18n/ja/docs/use-cases/tokenization/nft-mkt-overview.md
@@ -75,7 +75,7 @@ NFTokenのURLは、NFTのコンテンツが保存されている場所へのリ
### ウォレットのセットアップ
-新しいウォレットをセットアップします。[Xumm](https://xumm.app/)をご覧ください。
+新しいウォレットをセットアップします。[Xaman](https://xaman.app/)をご覧ください。
アカウントを作成する際には、10 XRPの基本準備金が必要であることに注意してください。[準備金](../../concepts/accounts/reserves.md#base-reserve-and-owner-reserve)をご覧ください。
diff --git a/@i18n/ja/docs/use-cases/tokenization/nftoken-marketplace.md b/@i18n/ja/docs/use-cases/tokenization/nftoken-marketplace.md
index 3299c7093f..ab8bd2830e 100644
--- a/@i18n/ja/docs/use-cases/tokenization/nftoken-marketplace.md
+++ b/@i18n/ja/docs/use-cases/tokenization/nftoken-marketplace.md
@@ -26,7 +26,7 @@ NFTokenマーケットプレイスは、NFTokenクリエイターとコレクタ
### ウォレットのセットアップ
-新しいウォレットをセットアップします。[Xumm](https://xumm.app/)をご覧ください。
+新しいウォレットをセットアップします。[Xaman](https://xaman.app/)をご覧ください。
基本準備金については[準備金](../../concepts/accounts/reserves.md#base-reserve-and-owner-reserve)をご覧ください。
diff --git a/@i18n/ja/translations.yaml b/@i18n/ja/translations.yaml
index 4ee024e99f..232557bfa0 100644
--- a/@i18n/ja/translations.yaml
+++ b/@i18n/ja/translations.yaml
@@ -842,7 +842,7 @@ Ripple's CBDC Platform: Ripple社のCBDC Platform\
Ripple's On-Demand Liquidity: Ripple社のOn-Demand Liquidity
XRPL Rosetta explores fiat data on XRPL through visualization.: XRPL Rosettaは、XRPL上のフィアットデータを可視化することで素晴らしさを追求します。
XRPL.org's Ledger Explorer is a block explorer of the XRP Ledger.: XRPL.orgのLedger Explorerは、XRP Ledgerのブロックエクスプローラーです。
-Xumm Wallet is a non custodial wallet with superpower for the XRP Ledger.: Xumm Walletは、XRP Ledgerのための最高能力を備えた非カストディアルウォレットです。
+Xaman is a non custodial wallet with superpower for the XRP Ledger.: Xamanは、XRP Ledgerのための最高能力を備えた非カストディアルウォレットです。
Web Monetization: ウェブ収益化
CBDCs: CBDC
Cancel: キャンセル
diff --git a/@theme/components/Navbar/Navbar.tsx b/@theme/components/Navbar/Navbar.tsx
index 2bc32c3a31..31f8d52c80 100644
--- a/@theme/components/Navbar/Navbar.tsx
+++ b/@theme/components/Navbar/Navbar.tsx
@@ -104,7 +104,11 @@ export function Navbar(props) {
-
+
@@ -140,7 +144,7 @@ export function AlertBanner({ message, button, link, show }) {
return null;
}
-export function TopNavCollapsible({children}) {
+export function TopNavCollapsible({ children }) {
return (
+ {translate(item2.labelTranslationKey, item2.label)}
+
+ );
+ }
return (
{translate(item2.labelTranslationKey, item2.label)}
diff --git a/@theme/plugin.js b/@theme/plugin.js
index 56bffe5ba1..177373fdd9 100644
--- a/@theme/plugin.js
+++ b/@theme/plugin.js
@@ -11,6 +11,7 @@ export default function customPlugin() {
/** @type {import("@redocly/realm/dist/server/plugins/types").PluginInstance } */
const pluginInstance = {
+ id: 'xrpl',
processContent: async (content, actions) => {
await indexPagesInst.processContent?.(content, actions);
await codeSamplesInst.processContent?.(content, actions);
diff --git a/_code-samples/airgapped-wallet/py/requirements.txt b/_code-samples/airgapped-wallet/py/requirements.txt
index ca8f6cb108..d62c9d2d7c 100644
--- a/_code-samples/airgapped-wallet/py/requirements.txt
+++ b/_code-samples/airgapped-wallet/py/requirements.txt
@@ -4,12 +4,12 @@ base58==2.1.0
certifi==2024.7.4
cffi==1.15.0
colorama==0.4.4
-cryptography==41.0.6
+cryptography==43.0.1
Django==3.2.25
ECPy==1.2.5
h11==0.12.0
httpcore==0.13.6
-idna==3.2
+idna==3.8
image==1.5.33
pifacedigitalio==3.0.5
Pillow==10.3.0
@@ -19,7 +19,7 @@ qrcode==7.2
rfc3986==1.5.0
six==1.16.0
sniffio==1.2.0
-sqlparse==0.4.4
+sqlparse==0.5.1
typing-extensions==4.2.0
websockets==10.0
xrpl-py==2.0.0
diff --git a/_code-samples/build-a-browser-wallet/js/package.json b/_code-samples/build-a-browser-wallet/js/package.json
index 850587310c..94022b7364 100644
--- a/_code-samples/build-a-browser-wallet/js/package.json
+++ b/_code-samples/build-a-browser-wallet/js/package.json
@@ -12,7 +12,7 @@
"rollup-plugin-polyfill-node": "^0.12.0",
"stream-browserify": "^3.0.0",
"stream-http": "^3.2.0",
- "vite": "^4.5.3"
+ "vite": "^4.5.5"
},
"dependencies": {
"dotenv": "^16.0.3",
diff --git a/_code-samples/build-a-browser-wallet/js/yarn.lock b/_code-samples/build-a-browser-wallet/js/yarn.lock
index 373469452a..4adbeb75b5 100644
--- a/_code-samples/build-a-browser-wallet/js/yarn.lock
+++ b/_code-samples/build-a-browser-wallet/js/yarn.lock
@@ -376,9 +376,9 @@ dotenv@^16.0.3:
integrity sha512-7GO6HghkA5fYG9TYnNxi14/7K9f5occMlp3zXAuSxn7CKCxt9xbNWG7yF8hTCSUchlfWSe3uLmlPfigevRItzQ==
elliptic@^6.5.3, elliptic@^6.5.4:
- version "6.5.4"
- resolved "https://registry.npmjs.org/elliptic/-/elliptic-6.5.4.tgz"
- integrity sha512-iLhC6ULemrljPZb+QutR5TQGB+pdW6KGD5RSegS+8sorOZT+rdQFbsQFJgvN3eRqNALqJer4oQ16YvJHlU8hzQ==
+ version "6.5.7"
+ resolved "https://registry.yarnpkg.com/elliptic/-/elliptic-6.5.7.tgz#8ec4da2cb2939926a1b9a73619d768207e647c8b"
+ integrity sha512-ESVCtTwiA+XhY3wyh24QqRGBoP3rEdDUl3EDUUo9tft074fi19IrdpH7hLCMMP3CIj7jb3W96rn8lt/BqIlt5Q==
dependencies:
bn.js "^4.11.9"
brorand "^1.1.0"
@@ -645,9 +645,9 @@ rollup-plugin-polyfill-node@^0.12.0:
"@rollup/plugin-inject" "^5.0.1"
rollup@^3.27.1:
- version "3.29.4"
- resolved "https://registry.npmjs.org/rollup/-/rollup-3.29.4.tgz"
- integrity sha512-oWzmBZwvYrU0iJHtDmhsm662rC15FRXmcjCk1xD771dFDx5jJ02ufAQQTn0etB2emNk4J9EZg/yWKpsn9BWGRw==
+ version "3.29.5"
+ resolved "https://registry.yarnpkg.com/rollup/-/rollup-3.29.5.tgz#8a2e477a758b520fb78daf04bca4c522c1da8a54"
+ integrity sha512-GVsDdsbJzzy4S/v3dqWPJ7EfvZJfCHiDqe80IyrF59LYuP+e6U1LJoUqeuqRbwAWoMNoXivMNeNAOf5E22VA1w==
optionalDependencies:
fsevents "~2.3.2"
@@ -709,10 +709,10 @@ util-deprecate@^1.0.1:
resolved "https://registry.npmjs.org/util-deprecate/-/util-deprecate-1.0.2.tgz"
integrity sha512-EPD5q1uXyFxJpCrLnCc1nHnq3gOa6DZBocAIiI2TaSCA7VCJ1UJDMagCzIkXNsUYfD1daK//LTEQ8xiIbrHtcw==
-vite@^4.5.3:
- version "4.5.3"
- resolved "https://registry.yarnpkg.com/vite/-/vite-4.5.3.tgz#d88a4529ea58bae97294c7e2e6f0eab39a50fb1a"
- integrity sha512-kQL23kMeX92v3ph7IauVkXkikdDRsYMGTVl5KY2E9OY4ONLvkHf04MDTbnfo6NKxZiDLWzVpP5oTa8hQD8U3dg==
+vite@^4.5.5:
+ version "4.5.5"
+ resolved "https://registry.yarnpkg.com/vite/-/vite-4.5.5.tgz#639b9feca5c0a3bfe3c60cb630ef28bf219d742e"
+ integrity sha512-ifW3Lb2sMdX+WU91s3R0FyQlAyLxOzCSCP37ujw0+r5POeHPwe6udWVIElKQq8gk3t7b8rkmvqC6IHBpCff4GQ==
dependencies:
esbuild "^0.18.10"
postcss "^8.4.27"
diff --git a/about/uses.page.tsx b/about/uses.page.tsx
index f24c1954c4..37f76d51b0 100644
--- a/about/uses.page.tsx
+++ b/about/uses.page.tsx
@@ -397,12 +397,12 @@ const cardsData = [
},
{
id: "xumm-wallet",
- title: "Xumm Wallet",
+ title: "Xaman",
description:
- "Xumm Wallet is a non custodial wallet with superpower for the XRP Ledger.",
+ "Xaman is a non custodial wallet with superpower for the XRP Ledger.",
category_id: "wallet",
category_name: "Wallet",
- link: "https://xumm.app/#team",
+ link: "https://xaman.app/#team",
},
];
@@ -815,7 +815,7 @@ export default function Uses() {
{translate("Submit Your Project")}
diff --git a/about/xrp.page.tsx b/about/xrp.page.tsx
index 2e0fb52d8d..544f6e10cc 100644
--- a/about/xrp.page.tsx
+++ b/about/xrp.page.tsx
@@ -19,7 +19,7 @@ const links = [
const softwallets = [
{ href: "https://towolabs.com/", id: "wallet-towo", alt: "Towo" },
- { href: "https://xumm.app/", id: "wallet-xumm", alt: "Xumm" },
+ { href: "https://xaman.app/", id: "wallet-xumm", alt: "Xaman" },
{ href: "https://trustwallet.com/", id: "wallet-trust", alt: "Trust Wallet" },
{
href: "https://gatehub.net/",
@@ -27,6 +27,7 @@ const softwallets = [
alt: "Gatehub",
imgclasses: "invertible-img",
},
+ { href: "https://gemwallet.com/", id: "wallet-gem", alt: "Gem Wallet" },
{ href: "https://coin.space/", id: "wallet-coin", alt: "Coin Space" },
];
diff --git a/blog/2020/developer-reflections-xrp-toolkit.md b/blog/2020/developer-reflections-xrp-toolkit.md
index b91855ea37..3861ffd575 100644
--- a/blog/2020/developer-reflections-xrp-toolkit.md
+++ b/blog/2020/developer-reflections-xrp-toolkit.md
@@ -14,7 +14,7 @@ theme:
> 
-XRP Toolkit is used by thousands of Xumm App and Ledger hardware wallet users to access advanced XRP Ledger features, such as limit orders, cross-currency payments, escrows, checks, and account settings.
+XRP Toolkit is used by thousands of Xaman App and Ledger hardware wallet users to access advanced XRP Ledger features, such as limit orders, cross-currency payments, escrows, checks, and account settings.
> 
diff --git a/blog/2021/xrpl-grants-funding-the-next-phase-of-open-decentralized-innovation.md b/blog/2021/xrpl-grants-funding-the-next-phase-of-open-decentralized-innovation.md
index a07f8760b6..9b0a4a99e0 100644
--- a/blog/2021/xrpl-grants-funding-the-next-phase-of-open-decentralized-innovation.md
+++ b/blog/2021/xrpl-grants-funding-the-next-phase-of-open-decentralized-innovation.md
@@ -63,7 +63,7 @@ The focus area for the first round relates to the development of NFTs on the XRP
The XRP Ledger is ideally suited to deliver a superior user experience for NFTs and tokenization more broadly. When combined with a robust suite of tools and resources, the innate performance advantages of the XRPL and its native digital asset [XRP](https://xrpl.org/xrp-overview.html) enable developers a seamless experience for NFTs, without the environmental implications inherent in other blockchains.
-The developer community around the XRP Ledger is already hard at work proposing features and providing tools and documentation to make XRPL the go-to chain for NFTs. XRPL Labs(https://xrpl-labs.com/), for example, proposed a [standard](https://github.com/XRPLF/XRPL-Standards/discussions/30) for using existing functionality to issue NFTs on the XRP Ledger and started working on an embedded xApp in XRP wallet XUMM for minting NFTs on the XRPL.
+The developer community around the XRP Ledger is already hard at work proposing features and providing tools and documentation to make XRPL the go-to chain for NFTs. XRPL Labs(https://xrpl-labs.com/), for example, proposed a [standard](https://github.com/XRPLF/XRPL-Standards/discussions/30) for using existing functionality to issue NFTs on the XRP Ledger and started working on an embedded xApp in XRP wallet Xaman for minting NFTs on the XRPL.
Inspired by XRPL Labs’ standard, the RippleX team also [proposed](https://github.com/XRPLF/XRPL-Standards/discussions/46) additional functionality that would provide enhanced NFT support on the XRP Ledger.
diff --git a/blog/2022/introducing-xrpl-py-2.0.0beta.md b/blog/2022/introducing-xrpl-py-2.0.0beta.md
index 702b3366b4..b179e488a1 100644
--- a/blog/2022/introducing-xrpl-py-2.0.0beta.md
+++ b/blog/2022/introducing-xrpl-py-2.0.0beta.md
@@ -25,7 +25,7 @@ The three main breaking changes made in this update are:
The `Wallet` class previously included a sequence field to make sending transactions easier. In practice, it made things harder. You usually don't know the sequence number when you create a `Wallet` instance, and you needed to manually increment the number after each transaction. It is safer to get the sequence number from the ledger, the real source of truth, when you auto-fill transactions.
-Generating seeds from an entropy string now takes in hex strings instead of UTF-8 strings. This was especially necessary to implement wallet generation from [XLS-12 Secret Numbers](https://github.com/XRPLF/XRPL-Standards/tree/master/XLS-12), commonly used by the XUMM wallet app. xrpl-py used to treat entropy as a UTF-8 value, but that's problematic because not all byte strings are valid UTF-8 strings, preventing us from the full range of random entropies for seed generation.
+Generating seeds from an entropy string now takes in hex strings instead of UTF-8 strings. This was especially necessary to implement wallet generation from [XLS-12 Secret Numbers](https://github.com/XRPLF/XRPL-Standards/tree/master/XLS-12), commonly used by the Xaman app. xrpl-py used to treat entropy as a UTF-8 value, but that's problematic because not all byte strings are valid UTF-8 strings, preventing us from the full range of random entropies for seed generation.
Lastly, when you initialize a `Wallet` from a seed without specifying an algorithm, the library now uses Ed25519 by default since it has better performance and other convenient properties compared to the secp256k1 algorithm. Previously xrpl-py would try to interpret the algorithm from the seed. To use the old encoding, you can specify `algorithm=secp256k1` when initializing a `Wallet` object.
diff --git a/blog/2023/chispend.md b/blog/2023/chispend.md
index 8118562083..425e16909d 100644
--- a/blog/2023/chispend.md
+++ b/blog/2023/chispend.md
@@ -16,7 +16,7 @@ This week on Developer Reflections, we’re proud to highlight [ChiSpend](https:
ChiSpend (also known as Unispend) supports various blockchains and their native tokens, including the XRP Ledger, Polygon, Ethereum, Celo, and BNB Chain. Users can pay directly from their non-custodial wallets to buy real products like gift cards, send money via the Mobile Money integration, and send Airtime (prepaid minutes) to friends and family around the world. ChiSpend also supports the spending of block rewards, DeFi earnings, yield farming gains, and more.
-The development team behind ChiSpend has prioritized ease-of-use for other developers via simple APIs that enhance existing mobile or web apps, games, wallets, or other on/off-chain projects. The project which is now live on Mainnet was built using `rippled`. Since launch, they have processed over $50,000 worth of transactions in XRP and other tokens. The app is also live on XUMM.
+The development team behind ChiSpend has prioritized ease-of-use for other developers via simple APIs that enhance existing mobile or web apps, games, wallets, or other on/off-chain projects. The project which is now live on Mainnet was built using `rippled`. Since launch, they have processed over $50,000 worth of transactions in XRP and other tokens. The app is also live on Xaman.

diff --git a/blog/2023/xrp-toolkit.md b/blog/2023/xrp-toolkit.md
index 31c22a058f..0fea306f89 100644
--- a/blog/2023/xrp-toolkit.md
+++ b/blog/2023/xrp-toolkit.md
@@ -20,7 +20,7 @@ Since our previous coverage on the project, XRP Toolkit has seen more hardware w

-XRP Toolkit is used by thousands of [Bifrost Wallet](https://bifrostwallet.com/), [Xumm](https://xumm.app/), [Keystone](https://keyst.one/), [D’CENT](https://dcentwallet.com/), and [Ledger](https://www.ledger.com/) hardware wallet users to access advanced XRP Ledger features, such as limit orders, cross-currency payments, escrows, trust lines, and account settings.
+XRP Toolkit is used by thousands of [Bifrost Wallet](https://bifrostwallet.com/), [Xaman](https://xaman.app/), [Keystone](https://keyst.one/), [D’CENT](https://dcentwallet.com/), and [Ledger](https://www.ledger.com/) hardware wallet users to access advanced XRP Ledger features, such as limit orders, cross-currency payments, escrows, trust lines, and account settings.

diff --git a/blog/2023/zoetic.md b/blog/2023/zoetic.md
index 9641c3f744..ba2ee1e6b8 100644
--- a/blog/2023/zoetic.md
+++ b/blog/2023/zoetic.md
@@ -10,17 +10,17 @@ theme:
---
# Developer Reflections: Zoetic
-This week on Developer Reflections, we’re proud to highlight [Zoetic](https://zoetic.xurlpay.org/), a complete and working application example for making xApps using ReactJS, Tailwinds CSS, and the Xumm "Universal" SDK.
+This week on Developer Reflections, we’re proud to highlight [Zoetic](https://zoetic.xurlpay.org/), a complete and working application example for making xApps using ReactJS, Tailwinds CSS, and the Xaman "Universal" SDK.
-Zoetic is a proof of concept for a Xumm app demonstrating the concept of "Hybrid xApps", which are xApps that have the following authentication modes:
+Zoetic is a proof of concept for a Xaman app demonstrating the concept of "Hybrid xApps", which are xApps that have the following authentication modes:
-* xApp - Xumm apps are authenticated by using the application inside the Xumm mobile app and the Xumm API via the xAppToken generated by the Xumm app.
+* xApp - Xaman apps are authenticated by using the application inside the Xaman mobile app and the Xaman API via the xAppToken generated by the Xaman app.
* Browser OAuth2 - xApps can also be authenticated by the user via a browser-based OAuth2 flow. This is the most common way to authenticate a web app.
-The project includes all implementations required to run a Xumm app, a browser-based OAuth2 flow, and a server side JWT backend. The project is a simple FastAPI app that can be run locally or deployed to a server. The app is a simple stub that can be used to build any new xApp, as a ReactJS app that can be built and deployed to a server, or as a static site.
+The project includes all implementations required to run a Xaman app, a browser-based OAuth2 flow, and a server side JWT backend. The project is a simple FastAPI app that can be run locally or deployed to a server. The app is a simple stub that can be used to build any new xApp, as a ReactJS app that can be built and deployed to a server, or as a static site.

diff --git a/blog/2024/clio-2.2.2.md b/blog/2024/clio-2.2.2.md
new file mode 100644
index 0000000000..52c5002d9e
--- /dev/null
+++ b/blog/2024/clio-2.2.2.md
@@ -0,0 +1,54 @@
+---
+category: 2024
+date: 2024-07-22
+seo:
+ title: Introducing Clio version 2.2.2
+ description: Version 2.2.2 of Clio, the XRP Ledger API server optimized for HTTP and WebSocket calls, is now available. Learn more about this update and bug fixes.
+labels:
+ - Clio Release Notes
+theme:
+ markdown:
+ editPage:
+ hide: true
+---
+# Introducing Clio version 2.2.2
+
+Version 2.2.2 of Clio, an XRP Ledger API server optimized for HTTP and WebSocket API calls, is now available. This release adds bug fixes.
+
+## Bug fixes
+
+* Relax error when `full` or `accounts` set to `false` by @godexsoft in https://github.com/XRPLF/clio/issues/1537
+* Add more account check by @cindyyan317 in https://github.com/XRPLF/clio/pull/1543
+
+## Database Migration
+
+If you are currently running Clio 1.0.4 or earlier and upgrading, you must perform a database migration to properly support NFT data. See the [`clio_migrator` branch](https://github.com/XRPLF/clio/tree/clio_migrator%402.0.0) and its README for instructions.
+
+## Install / Upgrade
+
+| Package | SHA-256 |
+|:--------|:--------|
+| [Ubuntu Deb (x86_64)](https://github.com/XRPLF/clio/releases/download/2.2.2/clio_2.2.2-1_amd64.deb) | `c18d6c8aefa20dbe74561dc01cd893ec7e9df93f68c0f4a5c7b5e279a37e4272` |
+
+For other platforms, please [build from source](https://github.com/XRPLF/clio/releases/tag/2.2.2). The most recent commit in the git log should be:
+
+```text
+commit 665fab183a967bb886c68734544ec7e80bea4903
+Author: cyan317 <120398799+cindyyan317@users.noreply.github.com>
+Date: Mon Jul 15 16:42:12 2024 +0100
+
+ fix: Add more account check (#1543)
+
+ Make sure all char is alphanumeric for account
+```
+
+## What's Changed
+
+See the [Full Changelog on GitHub](https://github.com/XRPLF/clio/compare/2.2.1...2.2.2)
+
+## Feedback
+
+The Clio open-source project is seeking feedback and engagement from the XRPL community.
+
+- To provide feedback, please [fill out this survey](https://forms.gle/fnGPTUCAdmEzkFy57).
+- To report an issue or propose a new idea, please [open an issue](https://github.com/XRPLF/clio/issues).
diff --git a/blog/2024/deep-dive-into-amm-integration.md b/blog/2024/deep-dive-into-amm-integration.md
new file mode 100644
index 0000000000..457d64cbf0
--- /dev/null
+++ b/blog/2024/deep-dive-into-amm-integration.md
@@ -0,0 +1,114 @@
+---
+category: 2024
+date: 2024-08-05
+seo:
+ title: XLS-30 - XRP Ledger Automated Market Maker
+ description: The XLS-30 AMM amendment unlocks new liquidity and trading options on the XRP Ledger network. Explore how developers can integrate with AMM.
+labels:
+ - Development
+theme:
+ markdown:
+ editPage:
+ hide: true
+---
+# XLS-30 Overview: XRP Ledger Automated Market Maker
+
+XLS-30 is live on Mainnet, bringing with it new avenues for liquidity and trading on the network. Designed as a native protocol, XLS-30 enables developers to integrate with the AMM and establish their own front-end trading and liquidity provision interfaces.
+
+
+
+The XRPL decentralized exchange (DEX) currently provides liquidity exclusively by manual market making and order books. The XLS-30 adds non-custodial automated market maker (AMM) as a native feature to the XRPL DEX, which offers an opportunity to earn returns to those who provide liquidity to the AMM and decreases slippage when trading the long tail of tokens.
+
+## XLS-30 Timeline
+
+The XRP Ledger’s decentralized amendment process plays a crucial role in the adoption of new features like the AMM. This has meant that the journey toward integration has been a long one, as [validators](https://xrpl.org/validators.html) have thoroughly considered all outcomes before making a decisive turn with their relevant vote.
+
+| Phase | Date |
+|:---------------------------|:-----------------|
+| [AMM Proposal](https://dev.to/ripplexdev/a-proposal-for-the-future-of-the-xrp-ledger-dex-4l7e) | Jul. 2022 |
+| [AMM Performance Testing](https://dev.to/ripplexdev/amm-performance-testing-report-3hon) | Oct. 2023 |
+| [XLS-30 Proposal Voting](https://xrpscan.com/amendments) | Jan. - Mar. 2024 |
+| [XLS-30 Amendment Enabled](https://xrpl.org/resources/known-amendments#amm) | Mar. 2024 |
+| [AMM Bug Fix Integration](https://dev.to/ripplexdev/xrp-ledger-amm-bug-fix-now-integrated-a-detailed-analysis-4915) | Apr. 2024 |
+
+This [consensus](https://xrpl.org/consensus.html) process ensures that changes to the ledger continue to be appropriately scrutinized and vetted before rejection or approval by the community, reflecting a collective agreement on the network’s direction. For any amendment to pass, it must secure at least 80% approval from validators over a two-week continuous voting period, a testament to the XRP Ledger’s commitment to decentralized governance.
+
+To lower the barrier to entry for developers and encourage innovation, several key client libraries ([xrpl.js](https://js.xrpl.org/), [xrpl-py](https://xrpl-py.readthedocs.io/en/stable/), and [xrpl4j](https://xrpl.org/blog/2021/introducing-xrpl4j/)) have been updated and maintained. These libraries have been equipped with functionalities specific to AMM operations, such as creating liquidity pools, managing LP tokens, and executing AMM-specific transactions. Moreover, the [XRPL Explorer](https://amm-devnet.xrpl.org/) has been enhanced to support visibility into AMM pools, offering insights into liquidity depth, transaction history, and a great deal more.
+
+## What is an Automated Market Maker?
+
+The AMM model on the XRPL is designed to facilitate automatic trading and liquidity provision without the need for traditional order books. This is achieved through the creation of liquidity pools for pairs of assets, where the price of assets is determined algorithmically based on the ratio of the assets in the pool. This model is crucial for ensuring constant liquidity and more stable prices, particularly for pairs that might not have a large volume of direct market trades.
+
+## Core Features of the AMM Integration on XRPL
+
+**Protocol Native:**
+
+* As a core primitive of the XRPL, developers can use AMM functionality without the need to create their own smart contracts and face associated risks.
+
+**Aggregated Liquidity:**
+
+* Liquidity for all trading pairs is aggregated at the protocol layer, rather than fragmented or siloed across individual smart contracts.
+
+**Continuous Auction Mechanism:**
+
+* The implementation of a continuous auction mechanism allows arbitrageurs to bid to capture price discrepancies at a discount.
+* The AMM continuously auctions trading advantages for 24-hour periods at near zero trading fees. This results in immediate arbitrage trading and maintains stable volatility.
+* Proceeds from each auction are partially refunded to the prior arbitrage slot holder and partially burnt, effectively reducing impermanent loss for liquidity providers.
+
+**Single-sided Liquidity Provision:**
+
+* Only a single asset is required to contribute to a pool, decreasing the required number of steps for users to contribute liquidity.
+
+**No Miner Extractable Value (MEV):**
+
+* The XRPL uses federated consensus, meaning that each ledger (equivalent to a “block”) is determined by a consensus of participants whereby no single party can dictate which transactions or ledgers are valid. There are no miners to prioritize only certain transactions (namely higher gas fee orders) to the XRP Ledger.
+* The AMM’s (and existing DEX) orders inherit the core ledger’s deterministic-random transaction ordering secured by the distributed network of validators. While it does not eliminate the ability to front run transactions, it does become more difficult compared to an open mem pool.
+
+**CLOB DEX Integration:**
+
+* The AMM is integrated with the central limit order book (CLOB)-based DEX and enables price optimization to determine whether swapping within a liquidity pool, through the order book, or both, provides the best rate and executes accordingly. This ensures that transactions can automatically use the most efficient path for trades, whether through offers on the DEX or through AMM pools, optimizing for the best possible exchange rates, thereby enhancing DEX liquidity.
+
+## Core Transactions of XRPL AMM Protocol
+
+* **AMMCreate:** Enables the creation of a new AMM instance, initializing it with funding and defining the asset pair.
+* **AMMDeposit:** Allows users to add liquidity to an existing AMM, receiving Liquidity Provider (LP) tokens in proportion to their contribution.
+* **AMMWithdraw:** Crypto LPs can withdraw their funds from the AMM, surrendering their LP tokens and receiving their share of the assets back.
+* **AMMBid:** Users bid on the AMM’s auction slot, aiming for discounted trading fees.
+* **AMMVote:** Enables LPs to vote on the trading fee percentage, influencing the economics of the AMM pool.
+
+### LP Tokens and Governance
+
+LP tokens play a central role in the AMM ecosystem, representing the liquidity provider's share in the pool. These tokens not only pool ownership shares but also grant holders a say on key parameters of the AMM, such as trading fees. This feature introduces a layer of decentralized governance, allowing for a dynamic and community-driven approach to managing the pools.
+
+## Building with AMM on XRPL: A Step by Step Guide
+
+**Step 1: Setting Up Your Development Environment**
+
+To start building with AMM functionality, developers should first set up their development environment by integrating with the [xrpl.js](https://js.xrpl.org/), [xrpl-py](https://xrpl-py.readthedocs.io/en/stable/), or [xrpl4j](https://xrpl.org/blog/2021/introducing-xrpl4j/) libraries. These libraries have been updated to support AMM transactions and provide a solid foundation for interacting with the XRPL's AMM features.
+
+**Step 2: Creating and Managing AMM Pools**
+
+Developers can create AMM pools for any pair of assets on the XRPL by executing the [AMMCreate](https://xrpl.org/docs/references/protocol/transactions/types/ammcreate) transaction. This involves specifying the asset pair and providing initial liquidity. Once a pool is established, it can be managed through additional transactions like [AMMDeposit](https://xrpl.org/docs/references/protocol/transactions/types/ammdeposit) and [AMMWithdraw](https://xrpl.org/docs/references/protocol/transactions/types/ammwithdraw), allowing for a dynamic and responsive liquidity environment.
+
+**Step 3: Engaging with the Community for Feedback and Improvement**
+
+As the AMM functionality is novel and complex, engaging with the XRPL community for feedback, bug reports, and suggestions is crucial. The [XRPL Developers Discord channel](https://discord.gg/sfX3ERAMjH) and forums are excellent platforms for collaboration, offering a space for developers to share insights, ask questions, and contribute to the ongoing refinement of the AMM feature.
+
+## Use Cases and Applications
+
+The integration of the AMM on XRPL opens up exciting possibilities for financial and non-financial applications.
+
+**Financial Applications**
+
+Developers can create DeFi services like trading platforms, yield farming applications, and more, that leverage the efficiency and liquidity of AMM pools. The ability to easily swap assets and provide liquidity directly on the ledger enhances user experiences and can drive adoption of a variety of services.
+
+**Non-Financial Integrations**
+
+AMM functionality can enhance non-financial XRPL applications by simplifying transactions that involve asset exchanges. For example, platforms offering NFTs or other digital goods can integrate AMM to facilitate seamless asset swaps, improving the user journey and expanding the use cases for their offerings.
+
+
+## Getting Started and Resources
+
+Access the most up-to-date [technical documentation](https://opensource.ripple.com/docs/xls-30d-amm/amm-uc/) to get started, including comprehensive guides, API references, and tutorials on AMM and other XRP Ledger features. Additionally, the [Livenet XRPL Explorer](https://amm-devnet.xrpl.org/) allows developers to view real-time data on AMM pools, transactions, and more, offering valuable insights for development and analysis.
+
+The AMM integration marks a significant moment in the evolution of the XRP Ledger, introducing a robust mechanism for liquidity and trading that aligns with the principles of decentralized finance. As developers explore and innovate within this new framework, the potential for creating impactful and user-friendly DeFi applications on the ledger is immense. The journey ahead is an exciting one, with the AMM feature laying the groundwork for a vibrant ecosystem of financial innovation on XRP Ledger.
diff --git a/blog/2024/evolving-the-xrp-ledger.md b/blog/2024/evolving-the-xrp-ledger.md
new file mode 100644
index 0000000000..e6db40bd83
--- /dev/null
+++ b/blog/2024/evolving-the-xrp-ledger.md
@@ -0,0 +1,100 @@
+---
+category: 2024
+date: 2024-08-10
+seo:
+ title: Upcoming Testnet Reset Notification
+ description: Discover the latest in the XRPL community, including key organizations' plans to establish a more effective, inclusive, and visible XRPL Foundation with democratic governance.
+
+
+labels:
+ - General
+theme:
+ markdown:
+ editPage:
+ hide: true
+---
+# Evolving the XRP Ledger Foundation
+
+_By XRPL Foundation, XRPL Labs, XRPL Commons, and Ripple_
+
+A new chapter of collaboration within the XRP Ledger community is beginning. Organizations including XRPL Labs, XRPL Commons, the current XRPL Foundation, Ripple, and other prominent members of the XRP community came together recently to discuss how a more effective, inclusive, and visible XRP Ledger Foundation could be established, and what the road towards that looks like. Ongoing stewardship, democratic governance, contributions (both technical and non-technical), community and developer engagement and more are all central priorities to what a future foundation could enable, with the expertise and support of those who have long been involved in the XRP Ledger ecosystem.
+
+The overarching goal of this new foundation is to provide long-term security, growth, and effective, decentralized contributions to the XRPL.
+
+One of the most important near-term outcomes of these discussions is the decision to transfer existing XRPL Foundation key assets (listed below) to the new, independent foundation. This new foundation is set to feature a governance structure designed to represent the broader XRP Ledger community -- including developers, users, academia, validators, and infrastructure providers.
+
+There is more to come, such as fully detailing the charter, governance and other specifics for the new era of the XRPL Foundation – but know that the contributors are working diligently to address these opportunities. This update marks just the beginning in our ongoing commitment to ensuring the XRPL Foundation meets the diverse needs of the entire XRP Ledger community.
+
+As part of this process, the existing XRPL Foundation team has established a new [Inclusive Financial Technology Foundation](https://inftf.org/), paving the way for a future foundation entity to be incorporated. As [announced separately](https://twitter.com/bharathchari/status/1820908738296836565), the existing XRPL Foundation team has created, and will focus its efforts on INFTF to serve a broader financial inclusion mandate (not specifically focused on XRPL) after transitioning the responsibilities of the XRP Ledger Foundation to new leadership. Best of luck to the team on their future endeavors and the community thanks you all for your dedication.
+
+
+## Building on a Solid Foundation
+
+A new chapter for a XRPL Foundation is in progress. The organizations are looking to establish an initial board composed of several key members from the community: XRPL Labs, XRPL Commons, community representation (by, for example, a Community DAO), and Ripple - each bringing a wealth of experience from the XRP Ledger ecosystem to the mission, and working in unison to the larger goals. To ensure balanced governance and fresh perspectives, current discussions include adding an independent, democratically elected, rotating chairperson for the new foundation that will provide leadership.
+
+Current discussions target three stages to ensure inclusivity and adequate representation across the community, but we expect this to continue to evolve:
+
+### Stage 1: Secure Asset Transfers & Establishing Operational Transparency
+
+In this initial stage, our primary focus is to ensure the secure and orderly transfer of specific XRPL-related assets from the existing XRPL Foundation to the newly established foundation.
+
+This transfer will only take place once the new foundation is fully prepared and equipped to manage these assets effectively. Until then, the assets will continue to be managed by the current XRPL Foundation.
+
+The chart below outlines the specific assets held by the existing XRPL Foundation and details the planned steps for their transition to the new foundation.
+
+To set a strong base, the new foundation aims to emphasize operational transparency, such as by creating committees dedicated to various topics including Memberships, Audit and Infrastructure, and regularly publicizing its activities with the broader community. This approach lays the groundwork for coordination across the community, helping to future-proof the XRP Ledger network itself.
+
+The objective of the board composition for Stage 1 of the new foundation is to bring together a range of perspectives and expertise. This structure aims to foster collaboration and inclusivity, helping address the inherent complexity in capturing the interests of such a broad and diverse community. To further address this complexity, a community DAO that strives for equitable representation and participation across the community in a transparent, authentic and responsive way, is being evaluated.
+
+{% table %}
+ * **Existing XRPL-Related Assets Owned or Managed by the XRPL Foundation**
+ * **Current Planned Future Actions**
+ ---
+ * xrpl.org and its content
+ *
+ 1. Transfer of domain ownership
+ 2. Hosting and administrative access
+ 3. Update content and ownership
+ ---
+ * XRP trademarks
+ *
+ 1. Legal documentation for transfer
+ 2. Protect brand guidelines and usage rights
+ ---
+ * UNL (vl.xrplf.org)
+ *
+ 1. Transfer operational control to new XRPL Foundation
+ ---
+ * Github repositories
+ *
+ 1. Transfer repository ownership
+ 2. Update licensing & contribution
+ 3. Notify contributors
+ ---
+ * Communication channels (YouTube, X/Twitter, Blog)
+ *
+ 1. Transfer of access/ownership
+ 2. Notify stakeholders via joint comms
+ {% /table %}
+
+
+### Stage 2: Expand Community Representation and Operational Responsibilities
+
+The second stage may see the foundation take on more operational duties, including creating a formal membership structure. By expanding the governance framework, the goal is to ensure that the foundation truly reflects the varied interests and expertise within the vibrant XRPL ecosystem.
+
+This new foundation also aspires to broaden community representation. The longer-term plan aims to include new members from various sectors such as large ecosystem players, exchanges, or universities. Future board members should play an important role, having the authority to finalize the process and decision making of adding new participants. This process should be conducted in a transparent and inclusive manner to ensure that all stakeholders are fairly represented.
+
+
+### Stage 3: Explore New Initiatives and Expand Foundation Scope
+
+As collectively agreed upon now, the third stage will involve exploring additional committees and potentially expanding the foundation's scope to include areas such as Research & Development (R&D) for the XRPL Protocol, a channel for Grant distribution, and Marketing & Communications. The aim of these initiatives would be to empower the foundation to support innovation and promote development on the XRPL network, all while maintaining a decentralized approach to governance and operations.
+
+A key component of this transition is intended to expand grassroots participation and democratized governance. The objective is to continually broaden participation with formal membership, evolving alongside the community’s needs in ways that prioritize equity, expertise and efficiency of decision-making.
+
+## Looking Ahead
+
+The changes that lay ahead offer a great opportunity for collaboration, innovation and shared responsibility. All parties involved are dedicated to creating a transparent and inclusive process that strengthens an expanding and thriving community.
+
+More updates and details will be provided as soon as they solidify over the coming months.
+
+To provide further insights and answer questions, a X/Twitter Spaces is planned with representatives from the aforementioned organizations (XRPL Commons, XRPL Labs, Ripple, etc) in the coming weeks. Stay tuned for more details shortly.
\ No newline at end of file
diff --git a/blog/2024/how-to-mint-nfts.md b/blog/2024/how-to-mint-nfts.md
index 138c95fa5d..66c52b7779 100644
--- a/blog/2024/how-to-mint-nfts.md
+++ b/blog/2024/how-to-mint-nfts.md
@@ -2,8 +2,8 @@
category: 2024
date: 2024-03-08
seo:
- title: How to Mint an NFT on XRP Ledger
- description: Learn the basics of minting an NFT on XRP Ledger and how you can get started quickly and easily today.
+ title: How to Mint an NFT on XRPL
+ description: Learn the basics of minting an NFT on XRP Ledger and how you can get started quickly and easily with this step-by-step guide. Get started today!
labels:
- Development
theme:
diff --git a/blog/2024/rippled-2.2.1.md b/blog/2024/rippled-2.2.1.md
new file mode 100644
index 0000000000..765bcb6b25
--- /dev/null
+++ b/blog/2024/rippled-2.2.1.md
@@ -0,0 +1,75 @@
+---
+category: 2024
+date: 2024-07-30
+seo:
+ title: Introducing XRP Ledger version 2.2.1
+ description: Rippled version 2.2.1 is now available, addressing a critical bug when handling some types of RPC requests. Learn more about this release.
+labels:
+ - rippled Release Notes
+theme:
+ markdown:
+ editPage:
+ hide: true
+---
+# Introducing XRP Ledger version 2.2.1
+
+Version 2.2.1 of `rippled`, the reference server implementation of the XRP Ledger protocol, is now available. This release fixes a critical bug, introduced in 2.2.0, when handling some types of RPC requests. It does not introduce any new amendments.
+
+
+
+## Action Required
+
+Five amendments introduced in version 2.2.0 are open for voting according to the XRP Ledger's [amendment process](https://xrpl.org/amendments.html), which enables protocol changes following two weeks of >80% support from trusted validators.
+
+If you operate an XRP Ledger server version 2.2.0, upgrade to version 2.2.1 as soon as possible to ensure service continuity.
+
+If you operate an XRP Ledger server older than version 2.2.0, upgrade to version 2.2.1 by August 14, 2024 to ensure service continuity. The exact time that protocol changes take effect depends on the voting decisions of the decentralized network.
+
+## Install / Upgrade
+
+On supported platforms, see the [instructions on installing or updating `rippled`](../../docs/infrastructure/installation/index.md).
+
+| Package | SHA-256 |
+|:--------|:--------|
+| [RPM for Red Hat / CentOS (x86-64)](https://repos.ripple.com/repos/rippled-rpm/stable/rippled-2.2.1-1.el7.x86_64.rpm) | `32312c90ac4c685f11b168c5b9ec75aee8f4b2d7bef5dc11b42232679d0cd1f4` |
+| [DEB for Ubuntu / Debian (x86-64)](https://repos.ripple.com/repos/rippled-deb/pool/stable/rippled_2.2.1-1_amd64.deb) | `f696e6898ad64e73d75bb9a1f50fb325b9675b168ffaeeacfce53fbd9e35bbee` |
+| [Portable Builds (Linux x86-64)](https://github.com/XRPLF/rippled-portable-builds) | (Use signature verification) |
+
+For other platforms, please [build from source](https://github.com/ripple/rippled/tree/master/Builds). The most recent commit in the git log should be the change setting the version:
+
+```text
+commit e6ef0fc26cb8d4db25075eaa1fe21fcc7f984751
+Author: Ed Hennis
+Date: Mon Jul 22 18:08:16 2024 -0400
+
+ Set version to 2.2.1
+```
+
+
+## Full Changelog
+
+### Amendments
+
+- None
+
+### Bug fixes
+
+- Improve error handling in some RPC commands. [#5078](https://github.com/XRPLF/rippled/pull/5078)
+- Use error codes throughout fast Base58 implementation. [#5078](https://github.com/XRPLF/rippled/pull/5078)
+
+
+## Contact and More Information
+
+[Sign Up for Future Release Announcements](https://groups.google.com/g/ripple-server)
+
+The public source code repository for `rippled` is hosted on GitHub at .
+
+We welcome all contributions and invite everyone to join the community of XRP Ledger developers to help build the Internet of Value.
+
+#### Bug Bounties and Responsible Disclosures:
+
+We welcome reviews of the `rippled` code and urge researchers to responsibly disclose any issues they may find.
+
+To report a bug, please send a detailed report to:
+
+
diff --git a/blog/2024/rippled-2.2.2.md b/blog/2024/rippled-2.2.2.md
new file mode 100644
index 0000000000..22a306a9ab
--- /dev/null
+++ b/blog/2024/rippled-2.2.2.md
@@ -0,0 +1,62 @@
+---
+category: 2024
+date: 2024-09-03
+seo:
+ title: Introducing XRP Ledger version 2.2.2
+ description: Rippled version 2.2.2 is now available, addressing a Mainnet issue that caused validators to stall during consensus. Learn more about this release.
+labels:
+ - rippled Release Notes
+theme:
+ markdown:
+ editPage:
+ hide: true
+---
+# Introducing XRP Ledger version 2.2.2
+
+Version 2.2.2 of `rippled`, the reference server implementation of the XRP Ledger protocol, is now available. This release fixes an ongoing issue with Mainnet where validators can stall during consensus processing due to lock contention, preventing ledgers from being validated for up to two minutes. There are no new amendments in this release.
+
+
+
+
+## Action Required
+
+If you run an XRP Ledger validator, upgrade to version 2.2.2 as soon as possible to ensure stable and uninterrupted network behavior.
+
+Additionally, five amendments introduced in version 2.2.0 are open for voting according to the XRP Ledger's [amendment process](https://xrpl.org/amendments.html), which enables protocol changes following two weeks of >80% support from trusted validators. If you operate an XRP Ledger server older than version 2.2.0, upgrade by September 17, 2024 to ensure service continuity. The exact time that protocol changes take effect depends on the voting decisions of the decentralized network. Version 2.2.2 is recommended because of known bugs affecting stability of versions 2.2.0 and 2.2.1.
+
+
+## Install / Upgrade
+
+On supported platforms, see the [instructions on installing or updating `rippled`](../../docs/infrastructure/installation/index.md).
+
+| Package | SHA-256 |
+|:--------|:--------|
+| [RPM for Red Hat / CentOS (x86-64)](https://repos.ripple.com/repos/rippled-rpm/stable/rippled-2.2.2-1.el7.x86_64.rpm) | `d17d2dfc52a776015ba71a93bdd70cca5d57e51ba2c27ab0bb01afe6b645d3f0` |
+| [DEB for Ubuntu / Debian (x86-64)](https://repos.ripple.com/repos/rippled-deb/pool/stable/rippled_2.2.2-1_amd64.deb) | `9e0734966089d9cfde40d1a3551ae1e219faaadfe9fdc69eb900c6cb5024d658` |
+| [Portable Builds (Linux x86-64)](https://github.com/XRPLF/rippled-portable-builds) | (Use signature verification) |
+
+For other platforms, please [build from source](https://github.com/ripple/rippled/tree/master/Builds). The most recent commit in the git log should be the change setting the version:
+
+```text
+commit 85214bdf811e1ff11a02977211fe59b07619b856
+Author: Ed Hennis
+Date: Fri Aug 23 17:19:52 2024 -0400
+
+ Set version to 2.2.2
+```
+
+
+## Full Changelog
+
+### Amendments
+
+- None
+
+### Bug fixes
+
+- Allow only 1 job queue slot for acquiring inbound ledger ([7741483](https://github.com/XRPLF/rippled/commit/774148389467781aca7c01bac90af2fba870570c))
+- Allow only 1 job queue slot for each validation ledger check ([fbbea9e](https://github.com/XRPLF/rippled/commit/fbbea9e6e25795a8a6bd1bf64b780771933a9579))
+
+### Other Improvements
+
+- Track latencies of certain code blocks, and log if they take too long ([00ed7c9](https://github.com/XRPLF/rippled/commit/00ed7c942436f02644a13169002b5123f4e2a116))
diff --git a/blog/2024/rippled-2.2.3.md b/blog/2024/rippled-2.2.3.md
new file mode 100644
index 0000000000..f99ef9e620
--- /dev/null
+++ b/blog/2024/rippled-2.2.3.md
@@ -0,0 +1,111 @@
+---
+category: 2024
+date: 2024-09-14
+seo:
+ title: Introducing XRP Ledger version 2.2.3
+ description: Rippled version 2.2.3 is now available, addressing an issue that could cause full-history servers to run out of space in their SQLite databases. Learn more about this release.
+labels:
+ - rippled Release Notes
+theme:
+ markdown:
+ editPage:
+ hide: true
+---
+# Introducing XRP Ledger version 2.2.3
+
+Version 2.2.3 of `rippled`, the reference server implementation of the XRP Ledger protocol, is now available. This release fixes a problem that can cause full-history servers to run out of space in their SQLite databases, depending on configuration. There are no new amendments in this release.
+
+
+
+[Sign Up for Future Release Announcements](https://groups.google.com/g/ripple-server)
+
+## Background
+
+The `rippled` server uses a SQLite database for tracking transactions, in addition to the main data store (usually NuDB) for ledger data. In servers keeping a large amount of history, this database can run out of space based on the configured number and size of database pages, even if the machine has disk space available. Based on the size of full history on Mainnet, servers with the default SQLite page size of 4096 may now run out of space if they store full history. In this case, your server may shut down with an error such as the following:
+
+```text
+Free SQLite space for transaction db is less than 512MB. To fix this, rippled
+ must be executed with the vacuum parameter before restarting.
+ Note that this activity can take multiple days, depending on database size.
+```
+
+The exact timing of when a server runs out of space can vary based on a few factors. Server operators who encountered a similar problem in 2018 and followed steps to [increase the SQLite transaction database page size issue](../../../docs/infrastructure/troubleshooting/fix-sqlite-tx-db-page-size-issue) may not encounter this problem at all. The `--vacuum` commandline option to `rippled` from that time may work to free up space in the database, but requires extended downtime.
+
+Version 2.2.3 of `rippled` reconfigures the maximum number of SQLite pages so that the database capacity is doubled. With the default page size or 4096, the database capacity is roughly 17.5 TB.
+
+Clio servers providing full history are not affected by this issue.
+
+
+## Action Required
+
+If you run a full-history XRP Ledger Mainnet server, upgrade to version 2.2.3 as soon as possible to ensure service continuity. Other servers may not need to update immediately, but the update is safe regardless.
+
+Additionally, three amendments from version 2.2.0 currently have support from a supermajority of trusted validators and are expected to become enabled in less than two weeks. The following table shows when the amendments are expected to become enabled if they maintain support continuously:
+
+| Amendment | Expected on | Amendment Summary |
+|---|---|---|
+| `fixAMMv1_1` | 2024-09-24 | Fixes AMM offer rounding and low quality order book offers from blocking the AMM. |
+| `fixEmptyDID` | 2024-09-27 | Fixes a bug in the (not yet enabled) [DID Amendment](https://xrpl.org/resources/known-amendments#did). |
+| `fixPreviousTxnID` | 2024-09-27 | Adds history-tracking fields to several types of ledger entry that didn't previously have them. |
+
+If you are running a server older than 2.2.0 when any of these amendments becomes enabled, your server will become amendment blocked, which means it:
+
+* Cannot determine the validity of a ledger
+* Cannot submit or process transactions
+* Does not participate in the consensus process
+* Does not vote on future amendments
+* Could rely on potentially invalid data
+
+If you are not sure if you need to upgrade, the following table shows the minimum recommended server version by configuration.
+
+| Version | Notes |
+|---|---|
+| Older than 2.2.0 | May become amendment blocked on 2024-09-24. |
+| 2.2.0 | Has a known issue with handling certain RPC commands. **Not recommended** for any servers. |
+| 2.2.1 | Not recommended for validators or full-history servers due to known issues. Acceptable for tracking servers. |
+| 2.2.2 | Not recommended for full-history servers unless you've reconfigured the page size from the default (as recommended in 2018). Acceptable for stock servers or validators. |
+| 2.2.3 | Recommended for all servers. |
+
+## Install / Upgrade
+
+On supported platforms, see the [instructions on installing or updating `rippled`](../../docs/infrastructure/installation/index.md).
+
+| Package | SHA-256 |
+|:--------|:--------|
+| [RPM for Red Hat / CentOS (x86-64)](https://repos.ripple.com/repos/rippled-rpm/stable/rippled-2.2.3-1.el7.x86_64.rpm) | `fb90f8f78799c24dd1f6286e96aa31afd0586bf21d32bc711ccc3dc868977da5` |
+| [DEB for Ubuntu / Debian (x86-64)](https://repos.ripple.com/repos/rippled-deb/pool/stable/rippled_2.2.3-1_amd64.deb) | `e6a77cbe32228f9d68a8545c3b4e9a25d098ab30ea01852658ee5efe3371b9f1` |
+| [Portable Builds (Linux x86-64)](https://github.com/XRPLF/rippled-portable-builds) | (Use signature verification) |
+
+For other platforms, please [build from source](https://github.com/ripple/rippled/tree/master/Builds). The most recent commit in the git log should be the change setting the version:
+
+```text
+commit 68e1be3cf544bc8f50283b0bfecba60f8370dbf2
+Author: Elliot Lee
+Date: Sat Sep 14 13:08:18 2024 -0700
+
+ Set version to 2.2.3
+```
+
+## Full Changelog
+
+### Amendments
+
+- None
+
+### Bug fixes
+
+- Update SQLite3 max_page_count to match current defaults ([#5114](https://github.com/XRPLF/rippled/pull/5114))
+
+
+## Credits
+
+The following people contributed directly to this release:
+
+J. Scott Branson
+
+
+## Bug Bounties and Responsible Disclosures
+
+We welcome reviews of the `rippled` code and urge researchers to responsibly disclose any issues they may find.
+
+To report a bug, please send a detailed report to:
diff --git a/blog/2024/testnet-reset-notification.md b/blog/2024/testnet-reset-notification.md
new file mode 100644
index 0000000000..e4a11e078f
--- /dev/null
+++ b/blog/2024/testnet-reset-notification.md
@@ -0,0 +1,58 @@
+---
+category: 2024
+date: 2024-08-14
+seo:
+ title: Upcoming Testnet Reset Notification
+ description: The Testnet reset was completed successfully on Monday, August 19, 2024 to improve stability and reduce the cost of running a Testnet node. Learn more.
+labels:
+ - Advisories
+theme:
+ markdown:
+ editPage:
+ hide: true
+---
+# Upcoming Testnet Reset
+
+Testnet is scheduled for a reset on **Monday, August 19, 2024** to improve stability and reduce the cost of running a Testnet node.
+
+{% admonition type="success" name="Update" %}
+The reset has completed successfully. Testnet network and faucet are online and fully operational.
+{% /admonition %}
+
+## Background
+
+Ripple operates Testnet and Devnet to help the community test new features and integrations without risking real money. Testnet is meant to closely mirror the amendment status of Mainnet while Devnet acts as a preview of proposed and upcoming features based on the develop branch of the source code. Both networks have their own fixed, finite supply of test XRP, most of which is given out for free from a "faucet" service. The networks are occasionally reset so that the faucet can continue to give out test XRP, and to ensure that balances in the test networks have no real-world value.
+
+However, the current structure of Testnet, where test XRP is available for free, allows users to exploit the network by engaging in resource-intensive activities, such as minting millions of NFTs, that would otherwise be prohibitively expensive on XRPL Mainnet. This reset is necessary to reduce infrastructure demands and maintain the efficiency of Testnet.
+
+## Impact
+
+This reset affects Testnet only. Other networks will continue to operate as usual, including XRPL Mainnet, XRPL Devnet, Xahau, and the Hooks Testnet.
+
+The reset will delete all ledger data in Testnet, including all accounts, transactions, balances, settings, offers, AMMs, escrows, and other data. This means all balances will be reset to zero and the block number will start at one again. No changes are anticipated to services such as Tesnet APIs, faucets, Explorers, access rights, and wallet integrations; these services usually manage resets without issues.
+
+Testnet will have its amendment statuses restored to match XRPL Mainnet. Any existing accounts or other data in either network will need new test XRP from the faucet and will need to be re-created.
+
+If code relies on specific addresses, a request to the faucet can fund the same address again. However, any AMMs that are re-created after the reset will generally have different account addresses. As a reminder, it's best not to use the same addresses or key pairs on Mainnet and any test networks.
+
+The important URLs, Network ID, and validator settings for both networks will remain the same.
+
+## Action Recommended
+
+If you run a `rippled` server that is connected to Testnet, after the reset you should delete your database data and restart the server. Database files and folders are defined in the config file in the `[database_path]` and `[node_db]` stanzas. If you use the default config, you can run the following commands:
+
+```sh
+rm -r /var/lib/rippled/db/*
+
+systemctl restart rippled.service
+```
+
+## Learn, Ask Questions, and Discuss
+
+We’re exploring long-term solutions to enhance network resilience and ensure you’re well-prepared, including:
+
+* Optimizing resource allocation to manage testnet resources to prevent overuse.
+* Implementing additional safeguards and resource management strategies.
+* Establishing a regular reset schedule to provide consistency and predictability for developers by setting a clear timeline for testnet maintenance.
+
+We’d like to hear from you! Join the [XRPL Dev Discord](https://discord.gg/sfX3ERAMjH) to share your feedback. Your input and feedback on what changes would be beneficial is invaluable to improve testnet management and better support the community's needs.
\ No newline at end of file
diff --git a/blog/sidebars.yaml b/blog/sidebars.yaml
index d10175d3b1..79245a54c1 100644
--- a/blog/sidebars.yaml
+++ b/blog/sidebars.yaml
@@ -1,11 +1,18 @@
- group: Blog
groupTranslationKey: sidebar.blog
- page: blog/index.page.tsx
+ page: index.page.tsx
expanded: true
items:
- group: '2024'
expanded: false
items:
+ - page: 2024/rippled-2.2.3.md
+ - page: 2024/rippled-2.2.2.md
+ - page: 2024/testnet-reset-notification.md
+ - page: 2024/evolving-the-xrp-ledger.md
+ - page: 2024/deep-dive-into-amm-integration.md
+ - page: 2024/clio-2.2.2.md
+ - page: 2024/rippled-2.2.1.md
- page: 2024/filedgr.md
- page: 2024/clio-2.2.1.md
- page: 2024/clio-2.2.0.md
diff --git a/community/events.page.tsx b/community/events.page.tsx
index 235e4e95ec..ce1010e56e 100644
--- a/community/events.page.tsx
+++ b/community/events.page.tsx
@@ -11,6 +11,10 @@ const calls = require("../static/img/events/CommunityCalls.png");
const brazil = require("../static/img/events/event-meetup-brazil.png");
const korea = require("../static/img/events/SouthKoreaMeetup.png");
const infoSession = require("../static/img/events/InfoSessions.png");
+const infoSession2 = require("../static/img/events/xrpl-builder-office-hours-02.png");
+const infoSession3 = require("../static/img/events/xrpl-builder-office-hours-03.png");
+const infoSession4 = require("../static/img/events/xrpl-builder-office-hours-04.png");
+const decarb = require('../static/img/events/xrpl-decarb.png')
export const frontmatter = {
seo: {
title: "Events",
@@ -52,7 +56,7 @@ const events = [
type: "hackathon",
link: "https://xrpl-hackathon-2021.devpost.com/project-gallery",
location: "Virtual",
- date: "September 13-October 6, 2021",
+ date: "September 13 - October 6, 2021",
image: hackathon,
end_date: "October 6, 2021",
},
@@ -63,7 +67,7 @@ const events = [
type: "meetup",
link: "https://www.meetup.com/xrpl-community/events/281806645/",
location: "San Diego, CA",
- date: "Saturday, November 20, 2021",
+ date: "November 20, 2021",
image: sanDiego,
end_date: "November 20, 2021",
},
@@ -75,7 +79,7 @@ const events = [
type: "meetup",
link: "https://www.meetup.com/xrpl-community/events/281980446/",
location: "Atlanta, GA",
- date: "Saturday, November 27, 2021",
+ date: "November 27, 2021",
image: require("../static/img/events/event-meetup-alanta@2x.jpg"),
end_date: "November 27, 2021",
},
@@ -86,7 +90,7 @@ const events = [
type: "meetup",
link: "https://www.meetup.com/xrpl-community/events/281806676/",
location: "San Francisco, CA",
- date: "Monday, November 29, 2021",
+ date: "November 29, 2021",
image: require("../static/img/events/event-meetup-san-francisco@2x.jpg"),
end_date: "November 29, 2021",
},
@@ -98,7 +102,7 @@ const events = [
type: "meetup",
link: "https://www.meetup.com/xrpl-community/events/281829463/",
location: "Miami, FL ",
- date: "Thursday, December 9, 2021",
+ date: "December 9, 2021",
image: miami,
end_date: "December 8, 2022",
},
@@ -145,7 +149,7 @@ const events = [
name: "XRPL Community Meetup: Toronto",
id: "upcoming-xrpl-toronto",
description:
- "Join us for our first Toronto meetup with an evening of programming and networking with other members of the XRP Ledger Community with special guests from the XUMM Wallet and ARK PLATES teams!",
+ "Join us for our first Toronto meetup with an evening of programming and networking with other members of the XRP Ledger Community with special guests from the Xaman Wallet and ARK PLATES teams!",
type: "meetup",
link: "https://www.meetup.com/xrpl-toronto-community-meetup/events/284177188/",
location: "Toronto",
@@ -736,18 +740,18 @@ const events = [
link: "https://ripple.swoogo.com/xrpl-zone-seoul",
location: "Seongdong-su, Seoul",
date: "September 4, 2024",
- image: zone,
+ image: require('../static/img/events/event-meetup-zone-day.png'),
end_date: "September 4, 2024",
},
{
- name: "XRP Community After Hours",
+ name: "XRPL Zone Seoul After Hours",
description:
"Celebrate with the XRP Community during Korea Blockchain Week! Don't miss this opportunity to mingle with the vibrant XRP community, visionary XRPL developers, trailblazing innovators, and influential investors.",
type: "meetup",
link: "https://lu.ma/mbg067j3",
location: "Seongdong-su, Seoul",
date: "September 4, 2024",
- image: korea,
+ image: require('../static/img/events/event-meetup-zone-night.png'),
end_date: "September 4, 2024",
},
{
@@ -772,8 +776,174 @@ const events = [
image: conference,
end_date: "June 13, 2024",
},
+ {
+ name: "XRP Ledger Hackathon Seoul 2024",
+ description:
+ "Calling all developers in Korea or attending Korea Blockchain Week! Join us for an exclusive pre-KBW meetup in Gangnam, Seoul! Be part of an exciting opportunity to collaborate with fellow builders leveraging the XRP Ledger. Don’t miss this chance to connect with industry peers, explore local funding initiatives, and fuel your projects with new insights just before the main KBW event!",
+ type: "hackathon",
+ link: "https://lu.ma/1viq6evg",
+ location: "Seoul, South Korea",
+ date: "August 31 - September 1, 2024",
+ image: hackathon,
+ end_date: "September 1, 2024",
+ },
+ {
+ name: "XRP Community Day Tokyo",
+ description:
+ "Join senior execs from Ripple, prominent Japanese institutions, and the XRP community for a day of inspiration, networking and insights.",
+ type: "meetup",
+ link: "https://events.xrplresources.org/toyko-community-2024",
+ location: "Shinagawa, Tokyo",
+ date: "September 6, 2024",
+ image: require('../static/img/events/event-meetup-tokyo-day.png'),
+ end_date: "September 6, 2024",
+ },
+ {
+ name: "XRP Community Night Tokyo",
+ description:
+ "Celebrate with the XRP Community in Tokyo! Don't miss this opportunity to mingle with the vibrant XRP community, visionary developers, trailblazing innovators, and influential VCs.",
+ type: "meetup",
+ link: "https://lu.ma/84do37p7",
+ location: "Shinagawa, Tokyo",
+ date: "September 6, 2024",
+ image: require('../static/img/events/event-meetup-tokyo-night.png'),
+ end_date: "September 6, 2024",
+ },
+ {
+ name: "Chicago XRP Ledger Meet Up",
+ description:
+ "Hey Chicago XRP Ledger community! We're hosting a meetup soon—come hang out, share ideas, and talk all things XRPL. Would love to see you there!",
+ type: "meetup",
+ link: "https://lu.ma/74dulzff",
+ location: "Chicago, IL",
+ date: "September 12, 2024",
+ image: require('../static/img/events/chicago-meetup.png'),
+ end_date: "September 12, 2024",
+ },
+ {
+ name: "XRPL Builder Office Hours",
+ description:
+ "XRPL Builder Office Hours is an open forum hosted monthly by Developer Advocates to answer technical and business questions from community members.",
+ type: "info",
+ link: "https://ripple.zoom.us/meeting/register/tJMscOCsrDoiHNUN6hZLpFVR69OcfG9rXtIA",
+ location: "Virtual - Zoom",
+ date: "September 27, 2024",
+ image: infoSession2,
+ end_date: "September 27, 2024",
+ },
+ {
+ name: "XRPL Builder Office Hours",
+ description:
+ "XRPL Builder Office Hours is an open forum hosted monthly by Developer Advocates to answer technical and business questions from community members.",
+ type: "info",
+ link: "https://ripple.zoom.us/meeting/register/tJMscOCsrDoiHNUN6hZLpFVR69OcfG9rXtIA",
+ location: "Virtual - Zoom",
+ date: "October 25, 2024",
+ image: infoSession3,
+ end_date: "October 25, 2024",
+ },
+ {
+ name: "XRPL Builder Office Hours",
+ description:
+ "XRPL Builder Office Hours is an open forum hosted monthly by Developer Advocates to answer technical and business questions from community members.",
+ type: "info",
+ link: "https://ripple.zoom.us/meeting/register/tJMscOCsrDoiHNUN6hZLpFVR69OcfG9rXtIA",
+ location: "Virtual - Zoom",
+ date: "November 22, 2024",
+ image: infoSession4,
+ end_date: "November 22, 2024",
+ },
+ {
+ name: "XRPL Meetup in Munich",
+ description:
+ "Calling all blockchain and XRP Ledger enthusiasts in Munich! Join XRPL Meetups to share knowledge, build real-life connections, and foster communities centered around blockchain and XRP Ledger. We're establishing local “XRPL Hubs” across Europe, and we want you to be a part of it!",
+ type: "meetup",
+ link: "https://www.eventbrite.fr/e/xrpl-meetup-in-munich-tickets-957654278727",
+ location: "Munich, Germany",
+ date: "September 12, 2024",
+ image: require('../static/img/events/germany-meetup.png'),
+ end_date: "September 12, 2024",
+ },
+ {
+ name: "XRPL Town Hall Meeting",
+ description:
+ "Our first virtual Town Hall Meeting is on September 16 at 5 PM CEST. These recurring meetings are designed to bring our community together, provide updates, and offer a platform to address your most pressing questions.",
+ type: "info",
+ link: "https://www.eventbrite.fr/e/xrpl-town-hall-meeting-tickets-959615815737",
+ location: "Virtual",
+ date: "September 16, 2024",
+ image: require('../static/img/events/town-hall-meetup.png'),
+ end_date: "September 16, 2024",
+ },
+ {
+ name: "Building on the XRP Ledger",
+ description:
+ "This 2-day intensive hands-on training is designed for developers who are curious to learn about XRP Ledger. Meet your peers, share insights, and join a community of builders.",
+ type: "meetup",
+ link: "https://www.eventbrite.fr/e/building-on-the-xrp-ledger-tickets-945486885727",
+ location: "Paris, France",
+ date: "September 25 - 26, 2024",
+ image: require('../static/img/events/building-meetup.png'),
+ end_date: "September 26, 2024",
+ },
+ {
+ name: "XRPL Community Magazine #3 Launch Party",
+ description:
+ "Join us on the 9th of October for a night of celebration and discussion! Connect with experts, mingle with fellow blockchain enthusiasts, and hear more about opportunities in the XRP Ledger ecosystem.",
+ type: "meetup",
+ link: "https://www.eventbrite.fr/e/xrpl-community-magazine-3-launch-party-tickets-967649013247",
+ location: "Paris, France",
+ date: "October 9, 2024",
+ image: require('../static/img/events/mag-meetup.png'),
+ end_date: "October 9, 2024",
+ },
+ {
+ name: "San Francisco XRP Ledger Meet Up",
+ description:
+ "Hello San Francisco XRP Ledger community! We're hosting a meetup soon with a focus on ZK research. Excited to see you soon!",
+ type: "meetup",
+ link: "https://lu.ma/evdklm4r",
+ location: "San Francisco, California",
+ date: "September 26, 2024",
+ image: require('../static/img/events/sf-meetup.jpg'),
+ end_date: "September 26, 2024",
+ },
+ {
+ name: "AI Fund - XRPL Grants Info Session",
+ description:
+ "Join our info session to learn about our new XRPL Grants' AI Fund, designed to support innovative projects that leverage artificial intelligence in the XRPL ecosystem.",
+ type: "info",
+ link: "https://ripple.zoom.us/webinar/register/WN__SNDW7LTSM29h5NIpvXFvg#/registration",
+ location: "Virtual - Zoom",
+ date: "October 2, 2024",
+ image: infoSession,
+ end_date: "October 2, 2024",
+ },
+ {
+ name: "XRPL Decarbonization Strategy",
+ description:
+ "Join us for the 3rd webinar in our Sustainability series. This time, Mélanie Damour and CCRI will dive into how Sustainability Disclosure under MiCA for CASPs and Token Issuers.",
+ type: "info",
+ link: "https://decarb3.eventbrite.fr",
+ location: "Virtual",
+ date: "October 7, 2024",
+ image: decarb,
+ end_date: "October 7, 2024",
+ },
+ {
+ name: "The Future with Blockchain",
+ description:
+ "Join us for an exciting side event held by Axiology, SUPER HOW?, XPMarket, and XRPL Commons during the biggest startup festival in Lithuania, StartupFair.",
+ type: "meetup",
+ link: "https://www.eventbrite.fr/e/the-future-with-blockchain-tickets-1013765398597",
+ location: "Vilnius, Lithuania",
+ date: "October 3, 2024",
+ image: require('../static/img/events/xrpl-future.png'),
+ end_date: "October 3, 2024",
+ },
];
+
export default function Events() {
const { useTranslate } = useThemeHooks();
const { translate } = useTranslate();
diff --git a/community/index.page.tsx b/community/index.page.tsx
index a4cb3f5307..9e4ee251dd 100644
--- a/community/index.page.tsx
+++ b/community/index.page.tsx
@@ -17,12 +17,15 @@ const hackathon = require("../static/img/events/Hackathons.png");
const conference = require("../static/img/events/Conference.png");
const zone = require("../static/img/events/XRPLZone.png");
const brazil = require("../static/img/events/event-meetup-brazil.png");
-const korea = require("../static/img/events/SouthKoreaMeetup.png")
+const korea = require("../static/img/events/SouthKoreaMeetup.png");
+const infoSession2 = require("../static/img/events/xrpl-builder-office-hours-02.png");
+const infoSession3 = require("../static/img/events/xrpl-builder-office-hours-03.png");
+const infoSession4 = require("../static/img/events/xrpl-builder-office-hours-04.png");
const findNearestUpcomingEvent = (events) => {
let nearestEvent = null;
let nearestDateDiff = Infinity;
-
- events.forEach((event) => {
+ let index;
+ events.forEach((event, i) => {
const eventStartDate = moment(event.start_date, "MMMM DD, YYYY");
const currentDate = moment();
const diff = eventStartDate.diff(currentDate, "days");
@@ -30,10 +33,11 @@ const findNearestUpcomingEvent = (events) => {
if (diff >= 0 && diff < nearestDateDiff) {
nearestEvent = event;
nearestDateDiff = diff;
+ index = i
}
});
- return { nearestEvent, nearestDateDiff };
+ return { nearestEvent, nearestDateDiff, index };
};
const events = [
@@ -181,30 +185,6 @@ const events = [
start_date: "July 23, 2024",
end_date: "July 23, 2024",
},
- {
- name: "XRPL Zone Seoul",
- description:
- "Join us at XRPL Zone Seoul where developers, corporates, fintechs, banks, VCs, academia, and the XRP community come together under one roof for the biggest XRPL event in South Korea!",
- type: "zone",
- link: "https://ripple.swoogo.com/xrpl-zone-seoul",
- location: "Seongdong-su, Seoul",
- date: "September 4, 2024",
- image: zone,
- start_date: "September 4, 2024",
- end_date: "September 4, 2024",
- },
- {
- name: "XRP Community After Hours",
- description:
- "Celebrate with the XRP Community during Korea Blockchain Week! Don't miss this opportunity to mingle with the vibrant XRP community, visionary XRPL developers, trailblazing innovators, and influential investors.",
- type: "meetup",
- link: "https://lu.ma/mbg067j3",
- location: "Seongdong-su, Seoul",
- date: "September 4, 2024",
- image: korea,
- start_date: "September 4, 2024",
- end_date: "September 4, 2024",
- },
{
name: "XRPL Builder Office Hours",
description:
@@ -217,13 +197,144 @@ const events = [
start_date: "August 23, 2024",
end_date: "August 23, 2024",
},
+ {
+ name: "XRP Ledger Hackathon Seoul 2024",
+ description:
+ "Calling all developers in Korea or attending Korea Blockchain Week! Join us for an exclusive pre-KBW meetup in Gangnam, Seoul! Be part of an exciting opportunity to collaborate with fellow builders leveraging the XRP Ledger. Don’t miss this chance to connect with industry peers, explore local funding initiatives, and fuel your projects with new insights just before the main KBW event!",
+ type: "hackathon",
+ link: "https://lu.ma/1viq6evg",
+ location: "Seoul, South Korea",
+ date: "August 31 - September 1, 2024",
+ image: hackathon,
+ start_date: "August 31, 2024",
+ end_date: "September 1, 2024",
+ },
+ {
+ name: "XRPL Zone Seoul",
+ description:
+ "Join us at XRPL Zone Seoul where developers, corporates, fintechs, banks, VCs, academia, and the XRP community come together under one roof for the biggest XRPL event in South Korea!",
+ type: "zone",
+ link: "https://ripple.swoogo.com/xrpl-zone-seoul",
+ location: "Seongdong-su, Seoul",
+ date: "September 4, 2024",
+ image: require('../static/img/events/event-meetup-zone-day.png'),
+ start_date: "September 4, 2024",
+ end_date: "September 4, 2024",
+ },
+ {
+ name: "XRPL Zone Seoul After Hours",
+ description:
+ "Celebrate with the XRP Community during Korea Blockchain Week! Don't miss this opportunity to mingle with the vibrant XRP community, visionary XRPL developers, trailblazing innovators, and influential investors.",
+ type: "meetup",
+ link: "https://lu.ma/mbg067j3",
+ location: "Seongdong-su, Seoul",
+ date: "September 4, 2024",
+ image: require('../static/img/events/event-meetup-zone-night.png'),
+ start_date: "September 4, 2024",
+ end_date: "September 4, 2024",
+ },
+ {
+ name: "XRP Community Day Tokyo",
+ description:
+ "Join senior execs from Ripple, prominent Japanese institutions, and the XRP community for a day of inspiration, networking and insights.",
+ type: "meetup",
+ link: "https://events.xrplresources.org/toyko-community-2024",
+ location: "Shinagawa, Tokyo",
+ date: "September 6, 2024",
+ image: require('../static/img/events/event-meetup-tokyo-day.png'),
+ start_date: "September 6, 2024",
+ end_date: "September 6, 2024",
+ },
+ {
+ name: "XRP Community Night Tokyo",
+ description:
+ "Celebrate with the XRP Community in Tokyo! Don't miss this opportunity to mingle with the vibrant XRP community, visionary developers, trailblazing innovators, and influential VCs.",
+ type: "meetup",
+ link: "https://lu.ma/84do37p7",
+ location: "Shinagawa, Tokyo",
+ date: "September 6, 2024",
+ image: require('../static/img/events/event-meetup-tokyo-night.png'),
+ start_date: "September 6, 2024",
+ end_date: "September 6, 2024",
+ },
+ {
+ name: "Chicago XRP Ledger Meet Up",
+ description:
+ "Hey Chicago XRP Ledger community! We’re hosting a meetup soon—come hang out, share ideas, and talk all things XRPL. Would love to see you there!",
+ type: "meetup",
+ link: "https://lu.ma/74dulzff",
+ location: "Chicago, IL",
+ date: "September 12, 2024",
+ image: require('../static/img/events/chicago-meetup.png'),
+ start_date: "September 12, 2024",
+ end_date: "September 12, 2024",
+ },
+ {
+ name: "San Francisco XRP Ledger Meet Up",
+ description:
+ "Hello San Francisco XRP Ledger community! We're hosting a meetup soon with a focus on ZK research. Excited to see you soon!",
+ type: "meetup",
+ link: "https://lu.ma/evdklm4r",
+ location: "San Francisco, California",
+ date: "September 26, 2024",
+ image: require('../static/img/events/sf-meetup.jpg'),
+ start_date: "September 26, 2024",
+ end_date: "September 26, 2024",
+ },
+ {
+ name: "XRPL Builder Office Hours",
+ description:
+ "XRPL Builder Office Hours is an open forum hosted monthly by Developer Advocates to answer technical and business questions from community members.",
+ type: "info",
+ link: "https://ripple.zoom.us/meeting/register/tJMscOCsrDoiHNUN6hZLpFVR69OcfG9rXtIA",
+ location: "Virtual - Zoom",
+ date: "September 27, 2024",
+ image: infoSession2,
+ start_date: "September 27, 2024",
+ end_date: "September 27, 2024",
+ },
+ {
+ name: "AI Fund - XRPL Grants Info Session",
+ description:
+ "Join our info session to learn about our new XRPL Grants' AI Fund, designed to support innovative projects that leverage artificial intelligence in the XRPL ecosystem.",
+ type: "info",
+ link: "https://ripple.zoom.us/webinar/register/WN__SNDW7LTSM29h5NIpvXFvg#/registration",
+ location: "Virtual - Zoom",
+ date: "October 2, 2024",
+ image: infoSession,
+ start_date: "October 2, 2024",
+ end_date: "October 2, 2024",
+ },
+ {
+ name: "XRPL Builder Office Hours",
+ description:
+ "XRPL Builder Office Hours is an open forum hosted monthly by Developer Advocates to answer technical and business questions from community members.",
+ type: "info",
+ link: "https://ripple.zoom.us/meeting/register/tJMscOCsrDoiHNUN6hZLpFVR69OcfG9rXtIA",
+ location: "Virtual - Zoom",
+ date: "October 25, 2024",
+ image: infoSession3,
+ start_date: "October 25, 2024",
+ end_date: "October 25, 2024",
+ },
+ {
+ name: "XRPL Builder Office Hours",
+ description:
+ "XRPL Builder Office Hours is an open forum hosted monthly by Developer Advocates to answer technical and business questions from community members.",
+ type: "info",
+ link: "https://ripple.zoom.us/meeting/register/tJMscOCsrDoiHNUN6hZLpFVR69OcfG9rXtIA",
+ location: "Virtual - Zoom",
+ date: "November 22, 2024",
+ image: infoSession4,
+ start_date: "November 22, 2024",
+ end_date: "November 22, 2024",
+ }
];
-const { nearestDateDiff, nearestEvent } = findNearestUpcomingEvent(events);
+const { nearestDateDiff, nearestEvent, index } = findNearestUpcomingEvent(events);
const XrplEventsAndCarouselSection = ({ events }) => {
const { useTranslate } = useThemeHooks();
const { translate } = useTranslate();
- const [currentIndex, setCurrentIndex] = useState(11);
-
+ const [currentIndex, setCurrentIndex] = useState(index); // use nearest event's index as init state
const updateCarousel = () => {
const prevEvent = events[currentIndex - 1] || null;
const currentEvent = events[currentIndex];
@@ -655,6 +766,73 @@ const CommunityPage: React.FC = () => {
+ {/* Bottom Cards Section 2 cards */}
+
+
+
+
+
+ {translate("RippleX Bug Bounty Program")}
+
+
+ {translate(
+ "Contribute to the XRP Ledger's"
+ )}
+
+ Security
+
+
+ {translate(
+ "RippleX’s Bug Bounty, part of Ripple's 1 Billion XRP pledge, strengthens XRP Ledger security and supports its ecosystem."
+ )}
+
+ {
+ translate("Use this program to report bugs in RippleX/rippled. Send a detailed report of a qualifying bug to ")
+ }
+ bugs@ripple.com
+ {
+ translate(" and use the ")
+ }
+ Public Key.
+
+ {translate(
+ "In an evolving industry where trust and security are critical, scams continue to impede progress in crypto and blockchain. Help mitigate scammers by reporting scams."
+ )}
+