# Rollups from appchains to L2s
In this example, we'll use Supersonic, a Bitcoin L2, as the base layer. However, you can use any Bitcoin L2 as a base layer.
An application (Bitcoin L3) first rolls up to Supersonic. Then Supersonic itself rolls up to Bitcoin.
Let's zoom in on the architecture below and examine rollup flows step by step.
The steps to do a ZK rollup from a Bitcoin L3 to Supersonic (a Bitcoin L2) are as follows:
1. A user submits a transaction to the Bitcoin L3 Sequencer
2. The Bitcoin L3 Sequencer executes the transaction and provides a soft confirmation
3. If the user chooses, they can force the Bitcoin L3 Sequencer to include their transaction
4. The Bitcoin L3 Sequencer executes the block of transactions and sends it over to the Bitcoin L3 Prover
5. The Bitcoin L3 Prover creates a cryptographic proof of the block’s execution and sends it to the smart contract on Supersonic.
6. The smart contract verifies that the proof is valid and all the data has been submitted and then updates the rollup’s state in the contract.
7. The Bitcoin L3 Sequencer sends the block’s data to one of the Data Availability layers supported by BVM, such as Celestia, Near DA, Polygon, Avail DA, Filecoin, or Eigen DA.
---
# 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.bvm.network/bvm/l3-scaling-solutions/rollups-from-appchains-to-l2s.md?ask=
```
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.