Merge pull request #141 from bitlayer-org/feature/v2-doc

move YBTC introduction

Author: Nanyan

docs/BitVMBridge/BBN/001-understanding-bbn.md

@@ -40,11 +40,11 @@ A key example is the **BitVM Coordinator**, a protocol contract that plays a cru
 
 A primary function of the BitVM Coordinator is to manage the **attesting committee** for each new BitVM smart contract. This committee is a group of nodes that pre-signs the transaction graph. The Coordinator streamlines this process by:
 
-1. **Electing the Pre-Signing Committee:** For each new contract, the Coordinator selects committee members from a pool of trusted and eligible candidates.
+1. **Electing the Attesting Committee:** For each new contract, the Coordinator selects committee members from a pool of trusted and eligible candidates.
 2. **Implementing Incentives:** To ensure liveness and discourage malicious behavior, the Coordinator manages an incentive structure. Honest committee members are rewarded for their participation, while malicious actors are penalized through slashing.
 3. **Coordinating Signatures:** Once the committee is formed, the Coordinator orchestrates the signing process to ensure all members contribute their signatures in a timely and coordinated manner.
 
-To leverage this functionality, applications must run an **attester node**. For example, a BitVM bridge requires its attester node to verify the format of each transaction in the graph, sign it, and submit the signature to the Coordinator.
+To leverage this functionality, applications must run their own **attester node**. For example, a BitVM bridge requires its attester node to verify the format of each transaction in the graph, sign it, and submit the signature to the Coordinator.
 
 ### Watcher Coordination
 

docs/BitVMBridge/BBN/002-joining-bbn.md

@@ -17,9 +17,9 @@ If you’re interested in getting involved, feel free to contact us via email at
 The BitVM Bridge Broker role can appeal to various entities for different purposes. Below are some examples of how participants might engage as Brokers:
 
 - Type 1: Providing Liquidity Services to End Users
-     You might operate as a Broker to generate revenue by servicing the peg-out requests of end-users and charging transaction fees.
+    You might operate as a Broker to generate revenue by servicing the peg-out requests of end-users and charging transaction fees.
 - Type 2: Supporting Your Business Operations
-     You might operate as a Broker if you run a business (such as DeFi protocols or other services) that integrates YBTC (a highly secure bridged BTC asset) and you require the BitVM Bridge to balance your BTC/YBTC positions. The flexible peg-out feature of the Bitlayer BitVM Bridge allows participants with such needs to achieve this cost-effectively.
+    You might operate as a Broker if you run a business (such as DeFi protocols or other services) that integrates YBTC and you require the BitVM Bridge to balance your BTC/YBTC positions. The flexible peg-out feature of the Bitlayer BitVM Bridge allows participants with such needs to achieve this cost-effectively.
 
 Regardless of the specific motivation, all prospective Brokers must meet the following requirements:
 
@@ -31,13 +31,13 @@ Regardless of the specific motivation, all prospective Brokers must meet the fol
 
 2. Long-Term Collateral:
 
-     All brokers are required to provide long-term liquidity as collateral. A minimum of 0.5 BTC is necessary to participate in a single bridge instance.
+     All brokers are required to provide long-term liquidity as collateral. A certain amount (denoted as `minimum_collateral_per_reclaim`) of BTC is necessary to participate in a single bridge instance.
 
      Note: This collateral will be refunded once the corresponding bridge funds are reclaimed. The duration for this refund depends on the timing of user requests and the reclaim process.
 
 3. Short-Term Liquidity (Especially for User-Facing Services):
 
-     Brokers, particularly those aiming to provide liquidity services to end-users (as in Example 1), will need readily available short-term liquidity to front peg-out requests. A minimum of 2 BTC is recommended for this purpose.
+     Brokers, particularly those aiming to provide liquidity services to end-users (as in Type 1), will need readily available short-term liquidity to front peg-out requests. A minimum of 2 BTC is recommended for this purpose.
 
      Note: This liquidity will be reclaimed from the BitVM smart contract after the broker has fronted the peg-out request. The typical duration for this reclaim is the challenge window, which is generally one week.
 

docs/BitVMBridge/BBN/003-bbn-governance.md

@@ -12,7 +12,7 @@ The governance of the BitVM Bridge Network will be centered around the **Bitlaye
 
 **Key Features:**
 
-- **Governance Platform:** The core governance smart contracts will be deployed on the **Bitlayer Network** (the L2 scaling solution for Bitcoin). You can find more information about Bitlayer Network at [https://www.bitlayer.org/](https://www.bitlayer.org/).
+- **Governance Platform:** The core governance smart contracts will be deployed on the **Bitlayer Network**. You can find more information about Bitlayer Network at [https://www.bitlayer.org/](https://www.bitlayer.org/).
 - **Membership:** Any individual or entity holding a specified minimum amount of BTR tokens will be eligible to participate as a governance member. The exact threshold will be defined in the forthcoming governance framework.
 - **Proposal Submission:** Any eligible governance member can create new proposals and initiate the voting process.
 - **Discussion Forum:** A dedicated governance forum (currently under construction) will serve as the primary platform for discussing proposals, debating ideas, and fostering community consensus before formal voting.

docs/BitVMBridge/Concepts/098-roadmap.md

@@ -5,7 +5,7 @@ slug: roadmap
 
 # Roadmap
 
-![Roadmap](/img/BitvmBridge/introduction/roadmap1.png)
+![Roadmap](/img/BitvmBridge/introduction/roadmap.png)
 
 ## **DEC.2024**
 
@@ -19,8 +19,9 @@ slug: roadmap
 
 ## **July 2025**
 
-- Mainnet Beta Launch
+- Mainnet Beta Launch (Ethereum)
 
 ## **H2. 2025**
 
-- Support for Additional Chains
+- Mainnet Launch (SUI)
+- Support more Blockchains

docs/BitVMBridge/DevGuides/001-introduction-ybtc.md

@@ -8,7 +8,7 @@ slug: integrating-target-chain
 
 ## Introduction to Bitlayer's BitVM Bridge
 
-Bitlayer's BitVM Bridge is a cutting-edge solution designed to facilitate the movement of Bitcoin assets to a diverse array of blockchain ecosystems. This interoperability unlocks a multitude of decentralized finance (DeFi) and yielding opportunities for Bitcoin holders. The bridge supports a multi-chain architecture, encompassing both Layer 1 (L1) blockchains such as Ethereum, Cardano, Sui, Plume, Sonic SVM, and Solana, as well as Layer 2 (L2) solutions including Bitlayer Network, Base, Arbitrum, and Starknet, among others.
+Bitlayer's BitVM Bridge is a cutting-edge solution designed to facilitate the movement of Bitcoin assets to a diverse array of blockchain ecosystems. This interoperability unlocks a multitude of decentralized finance (DeFi) and yielding opportunities for Bitcoin holders. The bridge supports a multi-chain architecture, encompassing both Layer 1 (L1) blockchains such as Ethereum, Cardano, Sui, Plume, Sonic, and Solana, as well as Layer 2 (L2) solutions including Bitlayer Network, Base, Arbitrum, and Starknet, among others.
 
 The core strength of the BitVM Bridge lies in its extensible design, which simplifies the process of integrating new target chains. This document provides a comprehensive guide for developers from the Bitlayer community who wish to extend the bridge's capabilities by adding support for a new target blockchain.
 

docs/BitVMBridge/DevGuides/002-build-with-ybtc.md

@@ -1,7 +1,6 @@
 {
-    "label": "YBTC.B",
-    "position": 10,
-    "link": null,
-    "collapsed": false
-
-  }
+  "label": "YBTC.B",
+  "position": 10,
+  "link": null,
+  "collapsed": false
+}

docs/BitVMBridge/DevGuides/_category_.json

@@ -0,0 +1,6 @@
+{
+  "label": "YBTC",
+  "position": 11,
+  "link": null,
+  "collapsed": false
+}