mirror of
https://github.com/XRPLF/xrpl-dev-portal.git
synced 2025-11-28 07:35:50 +00:00
Move more amendment disclaimers to end of section
This commit is contained in:
@@ -1,17 +1,13 @@
|
||||
---
|
||||
html: cross-chain-bridges.html
|
||||
parent: xrpl-sidechains.html
|
||||
seo:
|
||||
description: Cross-chain bridges for the XRP Ledger enable value in the form of XRP and other tokens (IOUs) to move efficiently between blockchains.
|
||||
status: not_enabled
|
||||
labels:
|
||||
- Blockchain
|
||||
- Interoperability
|
||||
- Blockchain
|
||||
- Interoperability
|
||||
---
|
||||
# Cross-Chain Bridges
|
||||
|
||||
{% amendment-disclaimer name="XChainBridge" /%}
|
||||
|
||||
Cross-chain bridges enable you to move XRP and tokens between the XRP Ledger and other blockchains. When referring to the blockchains connected by a bridge, one is the locking chain and the other the issuing chain.
|
||||
|
||||
A locking chain is where the digital asset originates from. These assets are locked in a trust when sent across a bridge to an issuing chain.
|
||||
@@ -22,6 +18,8 @@ An issuing chain is an independent ledger with its own consensus algorithm and t
|
||||
|
||||
Both the locking and issuing chains operate as parallel networks with independent nodes and validators. They rely on independent [witness servers](witness-servers.md) to watch transactions between the two chains and attest that assets have moved into specifically designated accounts.
|
||||
|
||||
{% amendment-disclaimer name="XChainBridge" /%}
|
||||
|
||||
|
||||
## How Do Bridges Work?
|
||||
|
||||
|
||||
@@ -1,16 +1,12 @@
|
||||
---
|
||||
html: xrpl-sidechains.html
|
||||
parent: concepts.html
|
||||
seo:
|
||||
description: An XRPL sidechain is an independent ledger with its own consensus algorithm, transaction types, and rules.
|
||||
labels:
|
||||
- Blockchain
|
||||
- Interoperability
|
||||
- Blockchain
|
||||
- Interoperability
|
||||
---
|
||||
# XRPL Sidechains
|
||||
|
||||
{% amendment-disclaimer name="XChainBridge" /%}
|
||||
|
||||
A sidechain is an independent ledger with its own consensus algorithm, transaction types, rules, and nodes. It acts as its own blockchain, running parallel to the mainchain (XRP Ledger), enabling value to move between the two without compromising the speed, efficiency, and throughput of the mainchain.
|
||||
|
||||
Sidechains can customize the XRP Ledger protocol to the needs of a specific use case or project and run it as its own blockchain. Some examples include:
|
||||
@@ -20,6 +16,8 @@ Sidechains can customize the XRP Ledger protocol to the needs of a specific use
|
||||
* Building your own algorithmic stable coin with customised ledger types and transaction rules.
|
||||
* Building permissioned or nearly permissionless, centralized or largely decentralized ledgers whose assets can be traded on the Mainnet [decentralized exchange](../tokens/decentralized-exchange/index.md).
|
||||
|
||||
{% amendment-disclaimer name="XChainBridge" /%}
|
||||
|
||||
|
||||
**Notes:**
|
||||
|
||||
|
||||
@@ -1,18 +1,14 @@
|
||||
---
|
||||
html: witness-servers.html
|
||||
parent: xrpl-sidechains.html
|
||||
seo:
|
||||
description: A witness server is a light-weight server that witnesses and signs transactions between the XRP Ledger and another chain.
|
||||
status: not_enabled
|
||||
labels:
|
||||
- Blockchain
|
||||
- Interoperability
|
||||
- Blockchain
|
||||
- Interoperability
|
||||
---
|
||||
# Witness Servers
|
||||
[[Source]](https://github.com/seelabs/xbridge_witness "Source")
|
||||
|
||||
{% amendment-disclaimer name="XChainBridge" /%}
|
||||
|
||||
A _witness server_ acts as a neutral witness for transactions between a locking chain and an issuing chain. It listens to the door accounts on both sides of a bridge and signs attestations that confirm a transaction occurred. They are essentially acting as an oracle to “prove” that value was locked or burned on a source account, which allows the recipient to then claim (via minting or unlocking) the equivalent funds on the destination account.
|
||||
|
||||
The bridge between the locking chain and the issuing chain includes the following information in its configuration:
|
||||
@@ -24,6 +20,8 @@ Anyone can run a witness server. However, the burden is on the participants of t
|
||||
|
||||
{% admonition type="info" name="Note" %}Issuing chains may choose to configure a bridge with only one witness server initially and run the witness server itself. This strategy is helpful in the initial period, when the issuing chain hasn't established itself yet in the marketplace.{% /admonition %}
|
||||
|
||||
{% amendment-disclaimer name="XChainBridge" /%}
|
||||
|
||||
|
||||
## Witness Server Configuration
|
||||
|
||||
|
||||
Reference in New Issue
Block a user