# 3. Biop L2 Blockchain

Biop L2 Blockchain = Bitcoin + Optimistic Rollup Protocol + PoS + BVM

Biop is a Bitcoin L2 Blockchain based on Optimistic rollup protocol, which moves the computing of new Bitcoin protocols such as BRC-20 to L2, and is Bitcoin's decentralized computing chain. At the same time, as a Bitcoin L2, Biop will be a blockchain, use PoS (Proof of Stake) as consensus algorithm, use the blocks of Bitcoin network as input, use Ledger Syncer to transfer and parse Bitcoin ledger, inscription ledger, BRC ledger, etc. into Biop block, and use Computing Engine to complete the computing of various Bitcoin protocols. Then the computing results are stored as Merkle Trees and smart contracts, and finally the block state is written into Bitcoin block as witness to complete the block generation. The validator is responsible for challenging the correctness of the block, submitting fault proof for problematic blocks, and obtaining challenge rewards.

Biop will completely change the centralized dependence of new protocols such as BRC-20, will become the decentralized computing chain for Bitcoin, and will become the decentralized infrastructure for all ecosystem decentralized applications such as NFT marketplace, DeFi, GameFi, and SocialFi on Bitcoin.

<figure><img src="/files/NuKBwOuwLKnHC9DeyRBe" alt=""><figcaption></figcaption></figure>

This chapter has two parts, one part introduces the protocols of Biop, and the other part introduces the technical components of Biop.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.biop.io/biop_v1_whitepaper/biop_l2_blockchain.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.