# Deposits

#### L1 → L2 Deposits (Priority Operations)

For **L1 to L2 deposits**, also known as **priority operations**, users cannot directly send transactions to the **Sequencer’s mempool**. Instead, the deposit process requires one of the following methods:

1. **Bitcoin Inscription:**\
   The user **inscribes a message** on the **Bitcoin blockchain** containing the intended **L2 recipient address**, while simultaneously sending the desired amount of **BTC** to the **designated** [**bridge address**](https://docs.onvia.org/~/revisions/rEGNlPbCZsxx1YQ32Gtp/technical-specs/via-bitcoin-wallet-security).
2. **OP\_RETURN Output:**\
   The user utilizes an **OP\_RETURN output** to **encode the L2 recipient address**, again sending the desired amount of **BTC** to the [**bridge address**](https://docs.onvia.org/~/revisions/rEGNlPbCZsxx1YQ32Gtp/technical-specs/via-bitcoin-wallet-security).

Once the **deposit transaction** is confirmed (6 blocks) on Bitcoin, the sequencer detects the deposit, constructs a **priority transaction**, and adds it to the **Sequencer’s mempool**.

The **execution and validation** of these priority transactions follow the same process as standard transactions, with two key differences:

* The corresponding amount of **BTC is minted on L2** and credited to the **L2 recipient address**.
* The **Verifier Network** must validate the **legitimacy of these priority transactions** during the **L1 batch validation** process.

### Bridge Address

| Network           | Address                                                        |
| ----------------- | -------------------------------------------------------------- |
| Bitcoin mainnet   | -                                                              |
| BItcoin Testnet 4 | tb1ppsy8j80jtns42rkpdsfcv25qfschqejxmk6datkvu236eekr4fms06wnz0 |