Skip to content

chore: fix some typos in markdown file #159

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
billcarsoon wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore: fix some typos in markdown file #159

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion nodes/running_testnet_rollup_node.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ Please refer to the [Install Docker Engine](https://docs.docker.com/engine/insta
Please refer to the [Install Docker Compose](https://docs.docker.com/compose/install/standalone/)

## Download configuration files
Below is the releated files
Below is the related files
| Snapshot Data | Size | Download Link | sha256sum
| ----------- | ----------- | ----------- | ----------- |
| 2024-08-23 | 4.0K | [rollup.json](https://download.bsquared.network/testnet/rollup.json) | be7a590a5b4eb177c9953132f65be8cb0417ec47ccb2728c143da66a12c9eb2d
Expand Down
2 changes: 1 addition & 1 deletion tech_architecture/architecture.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
# Architecutre
# Architecture

The technical architecture of B² Network is shown in Figure [B² Network Architecture](https://ipfs.io/ipfs/QmNavFvPfkxeW5nti9WbGw2eCpZksfhzwgomuc7DK9eQjy). Comprising two fundamental layers, Rollup Layer and Data Availability Layer, B² Network seeks to redefine the way we perceive Bitcoin Layer-2 solutions.

Expand Down
4 changes: 2 additions & 2 deletions tech_architecture/b2_nodes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,9 +24,9 @@ The Bitcoin Indexer monitors blocks and transactions on the Bitcoin network. Upo

The Bitcoin Committer sends two types of transactions to Bitcoin: one that writes rollup data into Bitcoin, and another that writes the zk proof verification commitment into Bitcoin.

- The Bitcoin Committer constructs a data structure to record B² rollup data and generates a Tapscript, known as a "B² Inscription." Then, the Bitcoin Committer sends a UTXO of one satoshi unit to a Taproot address containing the $B^{2}$ inscription. The rollup data is permanently written into Bitcoin. (See in Figure [Data availablity in B² Network](https://ipfs.io/ipfs/Qma2tcFRFA78cDNLDTZJzpa4fDWHR4TKGptc5Q6qpsS4yT))
- The Bitcoin Committer constructs a data structure to record B² rollup data and generates a Tapscript, known as a "B² Inscription." Then, the Bitcoin Committer sends a UTXO of one satoshi unit to a Taproot address containing the $B^{2}$ inscription. The rollup data is permanently written into Bitcoin. (See in Figure [Data availability in B² Network](https://ipfs.io/ipfs/Qma2tcFRFA78cDNLDTZJzpa4fDWHR4TKGptc5Q6qpsS4yT))

![Data availablity in B² Network](https://ipfs.io/ipfs/Qma2tcFRFA78cDNLDTZJzpa4fDWHR4TKGptc5Q6qpsS4yT)
![Data availability in B² Network](https://ipfs.io/ipfs/Qma2tcFRFA78cDNLDTZJzpa4fDWHR4TKGptc5Q6qpsS4yT)

- The Bitcoin Committer breaks down large computational units from the ZK Proof Verifier of Rollup Module into smaller computational units. Each small computational unit is then turned into a bit value commitment and placed in a tapleaf script. The zk proof of rollup serves as the input for the first bit value commitment, with the output being the input for the next commitment, eventually forming a taproot. The Bitcoin Committer sends a UTXO of one satoshi unit to a Taproot address containing the commitment. The commitment based on zk proof verification is permanently written into Bitcoin. Additionally, the Bitcoin Committer sets a time-locked challenge, allowing challengers to contest the zk proof verification commitment. If there are no challengers or the challenge fails within the time lock, the rollup is finally confirmed on Bitcoin; if the challenge succeeds, the rollup is rolled back. (See in Figure [Commitment in B² Network](https://ipfs.io/ipfs/QmUSxP47LiQ1PaddAiCHw1SuKHwNVXe9KPi3Ta7JLXurEc))

Expand Down