mirror of
https://github.com/XRPLF/xrpl-dev-portal.git
synced 2025-11-20 19:55:54 +00:00
Use frontmatter for Consensus Network category
This commit is contained in:
mDuo13
@@ -1,3 +1,8 @@
|
||||
---
|
||||
html: about-canceling-a-transaction.html
|
||||
parent: consensus-network.html
|
||||
blurb: 送信済みのトランザクションのキャンセルがいつどのように可能か説明します。
|
||||
---
|
||||
# トランザクションの取消しについて
|
||||
|
||||
XRP Ledgerの重要かつ意図的な機能の1つに、トランザクションが検証済みレジャーに組み込まれると、即時に最終的なトランザクションになるという機能があります。
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
---
|
||||
html: about-canceling-a-transaction.html
|
||||
parent: consensus-network.html
|
||||
blurb: Understand when and how it's possible to cancel a transaction that has already been sent.
|
||||
---
|
||||
# About Canceling a Transaction
|
||||
|
||||
An important and intentional feature of the XRP Ledger is that a [transaction](transaction-basics.html)'s outcome is [final](finality-of-results.html) as soon as it has been incorporated in a [ledger version](ledgers.html) that is validated by the [consensus process](consensus.html).
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
---
|
||||
html: amendments.html
|
||||
parent: consensus-network.html
|
||||
blurb: Amendmentはトランザクション処理の新しい機能やその他の変更を指します。バリデータはコンセンサスを通して連携し、XRP Ledgerにこれらのアップグレードを順序正しく適用します。
|
||||
---
|
||||
# Amendment
|
||||
|
||||
[導入: rippled 0.31.0][]
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
---
|
||||
html: amendments.html
|
||||
parent: consensus-network.html
|
||||
blurb: Amendments represent new features or other changes to transaction processing. Validators coordinate through consensus to apply these upgrades to the XRP Ledger in an orderly fashion.
|
||||
---
|
||||
# Amendments
|
||||
|
||||
[Introduced in: rippled 0.31.0][]
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
---
|
||||
html: known-amendments.html
|
||||
parent: amendments.html
|
||||
blurb: 本番環境のXRP Ledgerに関する既知のAmendmentのすべてとそのステータスをまとめた総合リストです。
|
||||
---
|
||||
# 既知のAmendment
|
||||
[[ソース]](https://github.com/ripple/rippled/blob/master/src/ripple/protocol/impl/Feature.cpp "Source")
|
||||
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
---
|
||||
html: known-amendments.html
|
||||
parent: amendments.html
|
||||
blurb: List of all known amendments to the XRP Ledger protocol and their status.
|
||||
---
|
||||
# Known Amendments
|
||||
[[Source]](https://github.com/ripple/rippled/blob/master/src/ripple/protocol/impl/Feature.cpp "Source")
|
||||
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
---
|
||||
html: consensus-principles-and-rules.html
|
||||
parent: consensus-network.html
|
||||
blurb: XRP Ledgerは世界規模の決済システムで、ユーザーはメールを送るときのようにスムーズに国境を越えて送金することができます。
|
||||
---
|
||||
# コンセンサスの原理とルール
|
||||
|
||||
XRP Ledgerは世界規模の決済システムで、ユーザーはメールを送るときのようにスムーズに国境を越えて送金することができます。Bitcoinなどの他のピアツーピア決済ネットワークと同様に、XRP Ledgerでは分散型コンピューターネットワークを介したピアツーピア取引の決済が可能です。他のデジタル通貨プロトコルとは異なり、XRP LedgerではXRP（XRP Ledgerのネイティブ資産）の他にユーザーが選択した通貨（法定通貨、デジタル通貨、その他の価値形態など）建てでトランザクションを実行できます。
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
---
|
||||
html: consensus-principles-and-rules.html
|
||||
parent: consensus-network.html
|
||||
blurb: The rules and principles of the consensus algorithm that allow users to transfer funds (including fiat currencies, digital currencies and other forms of value) across national boundaries as seamlessly as sending an email.
|
||||
---
|
||||
# Consensus Principles and Rules
|
||||
|
||||
The XRP Ledger is a universal payment system enabling users to transfer funds across national boundaries as seamlessly as sending an email. Like other peer-to-peer payment networks such as Bitcoin, the XRP Ledger enables peer-to-peer transaction settlement across a decentralized network of computers. Unlike other digital currency protocols, the XRP Ledger allows users to denominate their transactions with any currency they prefer, including fiat currencies, digital currencies and other forms of value, in addition to XRP (the native asset of the XRP Ledger).
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
---
|
||||
html: consensus-protections.html
|
||||
parent: consensus-network.html
|
||||
blurb: Learn how the XRP Ledger Consensus Protocol is protected against various problems and attacks that may occur in a decentralized financial system. #TODO: translate
|
||||
---
|
||||
# 攻撃および障害モードに対するコンセンサスの保護
|
||||
|
||||
XRP Ledgerコンセンサスプロトコルは、 _ビザンチンフォールトトレラント性_ のあるコンセンサスメカニズムです。つまり、あらゆる不適切な状況（参加者が信頼できないオープンネットワークを利用して通信している場合や、不正使用者が常にシステムを乗っ取ろうとしているかまたは中断しようとしている場合など）が発生しても動作するように設計されています。さらに、XRP Ledgerコンセンサスプロトコルの参加者が事前に判明していない場合や、時間の経過とともに変わる場合があります。
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
---
|
||||
html: consensus-protections.html
|
||||
parent: consensus-network.html
|
||||
blurb: Learn how the XRP Ledger Consensus Protocol is protected against various problems and attacks that may occur in a decentralized financial system.
|
||||
---
|
||||
# Consensus Protections Against Attacks and Failure Modes
|
||||
|
||||
The XRP Ledger Consensus Protocol is a _byzantine fault tolerant_ consensus mechanism, which means it's designed to work even if all kinds of things can go wrong: participants depend on an unreliable open network to communicate, and malicious actors may be attempting to control or interrupt the system at any given time. On top of that, the set of participants in the XRP Ledger Consensus Protocol isn't known in advance and can change over time.
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
---
|
||||
html: consensus-research.html
|
||||
parent: consensus-network.html
|
||||
blurb: コンセンサスアルゴリズムに関する学術論文と関連研究。
|
||||
---
|
||||
# コンセンサスの研究
|
||||
|
||||
Rippleでは、XRP Ledgerのコンセンサスプロトコルの理論上の制限と実際の制限の両方についての研究を進め、この分野にてさまざまなアイデアを探究しています。以下の表に、Rippleが発表した学術論文の一覧を示します。
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
---
|
||||
html: consensus-research.html
|
||||
parent: consensus-network.html
|
||||
blurb: Scholarly articles on consensus algorithms and related research.
|
||||
---
|
||||
# Consensus Research
|
||||
|
||||
Ripple researches both the theoretical and the practical limits of the XRP Ledger's consensus protocols, and explores other ideas in the same space. The following table lists scholarly articles published by Ripple:
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
---
|
||||
html: consensus.html
|
||||
parent: consensus-network.html
|
||||
blurb: XRP Ledgerにおけるコンセンサスの役割について理解を深めましょう。
|
||||
---
|
||||
# コンセンサス
|
||||
|
||||
_著者: Dave Cohen、David Schwartz、Arthur Britto_
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
---
|
||||
html: consensus.html
|
||||
parent: consensus-network.html
|
||||
blurb: Understand the role of consensus in the XRP Ledger.
|
||||
---
|
||||
# Consensus
|
||||
|
||||
_Written by Dave Cohen, David Schwartz, and Arthur Britto._
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
---
|
||||
html: fee-voting.html
|
||||
parent: consensus-network.html
|
||||
blurb: トランザクションコストと必要準備金の変更投票について。
|
||||
---
|
||||
# 手数料投票
|
||||
|
||||
バリデータは、基本の[トランザクションコスト](transaction-cost.html)と[必要準備金](reserves.html)の変更について投票できます。バリデータの構成の設定がネットワークの現在の設定と異なる場合、バリデータはその設定をネットワークに定期的に公開します。定数のバリデータが変更に合意すると、変更を適用できるようになり、以後この変更が有効になります。バリデータはさまざまな理由から（特にXRPの価値の長期的な変化に適応するために）、この処理を行います。
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
---
|
||||
html: fee-voting.html
|
||||
parent: consensus-network.html
|
||||
blurb: How validators vote on fees (transaction cost and reserve requirements).
|
||||
---
|
||||
# Fee Voting
|
||||
|
||||
Validators can vote for changes to basic [transaction cost](transaction-cost.html) as well as [reserve requirements](reserves.html). If the preferences in a validator's configuration are different than the network's current settings, the validator expresses its preferences to the network periodically. If a quorum of validators agrees on a change, they can apply a change that takes effect thereafter. Validators may do this for various reasons, especially to adjust to long-term changes in the value of XRP.
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
---
|
||||
html: invariant-checking.html
|
||||
parent: consensus-network.html
|
||||
blurb: Understand what Invariant Checking is, why it exists, how it works, and what invariant checks are active.
|
||||
---
|
||||
# Invariant Checking
|
||||
|
||||
Invariant checking is a safety feature of the XRP Ledger. It consists of a set of checks, separate from normal transaction processing, that guarantee that certain _invariants_ hold true across all transactions.
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
---
|
||||
html: parallel-networks.html
|
||||
parent: consensus-network.html
|
||||
blurb: テストネットワークおよび代替レジャーチェーンと本番環境のXRP Ledgerとの関係について説明します。
|
||||
---
|
||||
# 並列ネットワーク
|
||||
|
||||
XRP Ledgerにはピアツーピアの本番環境のネットワークが1つ存在し、XRP Ledger上で行われるすべての取引はその本番環境のネットワーク、すなわちMainnet内で発生します。
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
---
|
||||
html: parallel-networks.html
|
||||
parent: consensus-network.html
|
||||
blurb: Understand how test networks and alternate ledger chains relate to the production XRP Ledger.
|
||||
---
|
||||
# Parallel Networks
|
||||
|
||||
There is one production XRP Ledger peer-to-peer network, and all business that takes place on the XRP Ledger occurs within the production network—the Mainnet.
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
---
|
||||
html: transaction-malleability.html
|
||||
parent: consensus-network.html
|
||||
blurb: トランザクションが想定とは異なるハッシュを持つようにどのように変更される可能性があるか注意してください。
|
||||
---
|
||||
# トランザクション展性
|
||||
|
||||
署名後のトランザクションを、署名に使用されたキーを使用せずに変更できる場合、そのトランザクションには「展性がある」ことになります。XRP Ledgerでは、署名付きトランザクションの**機能性**は変更できませんが、場合によっては第三者がトランザクションの署名と識別用ハッシュを変更できる _可能性があります_ 。
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
---
|
||||
html: transaction-malleability.html
|
||||
parent: consensus-network.html
|
||||
blurb: Be aware of ways transactions could be changed to have a different hash than expected.
|
||||
---
|
||||
# Transaction Malleability
|
||||
|
||||
A transaction is "malleable" if it can be changed in any way after being signed, without the keys to sign it. In the XRP Ledger, the **functionality** of a signed transaction cannot change, but in some circumstances a third party _could_ change the signature and identifying hash of a transaction.
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
---
|
||||
html: transaction-queue.html
|
||||
parent: consensus-network.html
|
||||
blurb: コンセンサスに至る前にトランザクションをどのようにキューに入れることができるか説明します。
|
||||
---
|
||||
# トランザクションキュー
|
||||
|
||||
`rippled`サーバーは、トランザクションキューを使用して[オープンレジャーコスト](transaction-cost.html#オープンレジャーコスト)を適用します。オープンレジャーコストにより、特定のレジャーの目標トランザクション数が設定され、オープンレジャーがこのサイズを超えると、必要なトランザクションコストが迅速に引き上げられます。`rippled`は引き上げられたトランザクションコストを支払うことができないトランザクションを無効にする代わりに、次のレジャーの構築に使用するトランザクションキューにそれらのトランザクションを入れようとします。
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
---
|
||||
html: transaction-queue.html
|
||||
parent: consensus-network.html
|
||||
blurb: Understand how transactions can be queued before reaching consensus.
|
||||
---
|
||||
# Transaction Queue
|
||||
|
||||
The `rippled` server uses a transaction queue to help enforce the [open ledger cost](transaction-cost.html#open-ledger-cost). The open ledger cost sets a target number of transactions in a given ledger, and escalates the required transaction cost very quickly when the open ledger surpasses this size. Rather than discarding transactions that cannot pay the escalated transaction cost, `rippled` tries to put them in a transaction queue, which it uses to build the next ledger.
|
||||
|
||||
@@ -994,52 +994,31 @@ pages:
|
||||
- ja
|
||||
|
||||
- md: concepts/consensus-network/consensus.md
|
||||
html: consensus.html
|
||||
parent: consensus-network.html
|
||||
blurb: Understand the role of consensus in the XRP Ledger.
|
||||
targets:
|
||||
- en
|
||||
|
||||
- md: concepts/consensus-network/consensus.ja.md
|
||||
html: consensus.html
|
||||
parent: consensus-network.html
|
||||
blurb: XRP Ledgerにおけるコンセンサスの役割について理解を深めましょう。
|
||||
targets:
|
||||
- ja
|
||||
|
||||
- md: concepts/consensus-network/consensus-principles-and-rules.md
|
||||
html: consensus-principles-and-rules.html
|
||||
parent: consensus-network.html
|
||||
blurb: The rules and principles of the consensus algorithm that allow users to transfer funds (including fiat currencies, digital currencies and other forms of value) across national boundaries as seamlessly as sending an email.
|
||||
targets:
|
||||
- en
|
||||
|
||||
- md: concepts/consensus-network/consensus-principles-and-rules.ja.md
|
||||
html: consensus-principles-and-rules.html
|
||||
parent: consensus-network.html
|
||||
blurb: The rules and principles of the consensus algorithm that allow users to transfer funds (including fiat currencies, digital currencies and other forms of value) across national boundaries as seamlessly as sending an email. #TODO: translate
|
||||
targets:
|
||||
- ja
|
||||
|
||||
- md: concepts/consensus-network/consensus-protections.md
|
||||
html: consensus-protections.html
|
||||
parent: consensus-network.html
|
||||
blurb: Learn how the XRP Ledger Consensus Protocol is protected against various problems and attacks that may occur in a decentralized financial system.
|
||||
targets:
|
||||
- en
|
||||
|
||||
- md: concepts/consensus-network/consensus-protections.ja.md
|
||||
html: consensus-protections.html
|
||||
parent: consensus-network.html
|
||||
blurb: Learn how the XRP Ledger Consensus Protocol is protected against various problems and attacks that may occur in a decentralized financial system. #TODO: translate
|
||||
targets:
|
||||
- ja
|
||||
|
||||
# TODO: translate this page and blurb
|
||||
- md: concepts/consensus-network/invariant-checking.md
|
||||
html: invariant-checking.html
|
||||
parent: consensus-network.html
|
||||
blurb: Understand what Invariant Checking is, why it exists, how it works, and what invariant checks are active.
|
||||
targets:
|
||||
- en
|
||||
- ja
|
||||
@@ -1051,116 +1030,68 @@ pages:
|
||||
- ja
|
||||
|
||||
- md: concepts/consensus-network/transaction-queue.md
|
||||
html: transaction-queue.html
|
||||
parent: consensus-network.html
|
||||
blurb: Understand how transactions can be queued before reaching consensus.
|
||||
targets:
|
||||
- en
|
||||
|
||||
- md: concepts/consensus-network/transaction-queue.ja.md
|
||||
html: transaction-queue.html
|
||||
parent: consensus-network.html
|
||||
blurb: コンセンサスに至る前にトランザクションをどのようにキューに入れることができるか説明します。
|
||||
targets:
|
||||
- ja
|
||||
|
||||
- md: concepts/consensus-network/about-canceling-a-transaction.md
|
||||
html: about-canceling-a-transaction.html
|
||||
parent: consensus-network.html
|
||||
blurb: Understand when and how it's possible to cancel a transaction that has already been sent.
|
||||
targets:
|
||||
- en
|
||||
|
||||
- md: concepts/consensus-network/about-canceling-a-transaction.ja.md
|
||||
html: about-canceling-a-transaction.html
|
||||
parent: consensus-network.html
|
||||
blurb: 送信済みのトランザクションのキャンセルがいつどのように可能か説明します。
|
||||
targets:
|
||||
- ja
|
||||
|
||||
- md: concepts/consensus-network/transaction-malleability.md
|
||||
html: transaction-malleability.html
|
||||
parent: consensus-network.html
|
||||
blurb: Be aware of ways transactions could be changed to have a different hash than expected.
|
||||
targets:
|
||||
- en
|
||||
|
||||
- md: concepts/consensus-network/transaction-malleability.ja.md
|
||||
html: transaction-malleability.html
|
||||
parent: consensus-network.html
|
||||
blurb: トランザクションが想定とは異なるハッシュを持つようにどのように変更される可能性があるか注意してください。
|
||||
targets:
|
||||
- ja
|
||||
|
||||
- md: concepts/consensus-network/amendments/amendments.md
|
||||
html: amendments.html
|
||||
parent: consensus-network.html
|
||||
blurb: Amendments represent new features or other changes to transaction processing. Validators coordinate through consensus to apply these upgrades to the XRP Ledger in an orderly fashion.
|
||||
targets:
|
||||
- en
|
||||
|
||||
- md: concepts/consensus-network/amendments/amendments.ja.md
|
||||
html: amendments.html
|
||||
parent: consensus-network.html
|
||||
blurb: Amendmentはトランザクション処理の新しい機能やその他の変更を指します。バリデータはコンセンサスを通して連携し、XRP Ledgerにこれらのアップグレードを順序正しく適用します。
|
||||
targets:
|
||||
- ja
|
||||
|
||||
- md: concepts/consensus-network/amendments/known-amendments.md
|
||||
html: known-amendments.html
|
||||
parent: amendments.html
|
||||
blurb: List of all known amendments to the XRP Ledger protocol and their status.
|
||||
targets:
|
||||
- en
|
||||
|
||||
- md: concepts/consensus-network/amendments/known-amendments.ja.md
|
||||
html: known-amendments.html
|
||||
parent: amendments.html
|
||||
blurb: List of all known amendments to the XRP Ledger protocol and their status. #TODO:translate
|
||||
targets:
|
||||
- ja
|
||||
|
||||
- md: concepts/consensus-network/fee-voting.md
|
||||
html: fee-voting.html
|
||||
parent: consensus-network.html
|
||||
blurb: How validators vote on fees (transaction cost and reserve requirements).
|
||||
targets:
|
||||
- en
|
||||
|
||||
- md: concepts/consensus-network/fee-voting.ja.md
|
||||
html: fee-voting.html
|
||||
parent: consensus-network.html
|
||||
blurb: How validators vote on fees (transaction cost and reserve requirements). #TODO: translate
|
||||
targets:
|
||||
- ja
|
||||
|
||||
- md: concepts/consensus-network/consensus-research.md
|
||||
html: consensus-research.html
|
||||
parent: consensus-network.html
|
||||
blurb: Scholarly articles on consensus algorithms and related research.
|
||||
targets:
|
||||
- en
|
||||
|
||||
- md: concepts/consensus-network/consensus-research.ja.md
|
||||
html: consensus-research.html
|
||||
parent: consensus-network.html
|
||||
blurb: コンセンサスアルゴリズムに関する学術論文と関連研究。
|
||||
targets:
|
||||
- ja
|
||||
|
||||
# TODO: add pseudo-transactions concept page
|
||||
|
||||
- md: concepts/consensus-network/parallel-networks.md
|
||||
html: parallel-networks.html
|
||||
parent: consensus-network.html
|
||||
blurb: Understand how test networks and alternate ledger chains relate to the production XRP Ledger.
|
||||
targets:
|
||||
- en
|
||||
|
||||
- md: concepts/consensus-network/parallel-networks.ja.md
|
||||
html: parallel-networks.html
|
||||
parent: consensus-network.html
|
||||
blurb: テストネットワークおよび代替レジャーチェーンと本番環境のXRP Ledgerとの関係について説明します。
|
||||
targets:
|
||||
- ja
|
||||
|
||||
@@ -4397,6 +4328,7 @@ pages:
|
||||
md: https://raw.githubusercontent.com/xpring-eng/xrp-api/master/README.md
|
||||
html: xrp-api.html
|
||||
parent: references.html
|
||||
blurb: An API server that provides a REST-like interface to the XRP Ledger.
|
||||
skip_spell_checker: true
|
||||
filters:
|
||||
- xrpapi_readme
|
||||
@@ -4409,6 +4341,7 @@ pages:
|
||||
- openapi_specification: https://raw.githubusercontent.com/xpring-eng/xrp-api/master/api-doc.yml
|
||||
openapi_md_template_path: tool/openapi_templates_alpha/
|
||||
parent: xrp-api.html
|
||||
blurb: An API server that provides a REST-like interface to the XRP Ledger. #TODO: translate blurb
|
||||
api_slug: xrp-api
|
||||
skip_spell_checker: true
|
||||
targets:
|
||||
|
||||
Reference in New Issue
Block a user