# 1.1 Background

We chose to develop on the **Rootstock Sidechain** due to its pioneering implementation of the **Ethereum Virtual Machine (EVM)** on Bitcoin since **2018**, without any reported security breaches. That's **6 years+** of no exploitation! Rootstock is backed up by **more than 50% bitcoin miners** using **blind merge mining** and **proof of work**! It also boasts the **largest Bitcoin DeFi** project in the world, [Sovryn](https://sovryn.app/).

Rootstock was one of the first Bitcoin sidechains to enable smart contracts. While still under development, it continues to improve. We anticipate that [**Drivechain** ](https://www.drivechain.info/)and/or [**BitVMX** ](https://bitvmx.org/)could significantly enhance Rootstock's capabilities. Both projects aim to address Bitcoin's L1 limitations in scalability, privacy, and two-way pegs. Notably, Drivechain requires a Bitcoin soft fork for implementation, while BitVMX does not.\
\
With the growing demand for developers building on Rootstock, we want to take this opportunity to be pioneers in shaping the Rootstock ecosystem. This allows us to leverage the security of Bitcoin while utilizing Ethereum-style smart contracts written in Solidity.\
\
Furthermore, given the widespread adoption of the EVM by various chains, we can technically bridge to other Bitcoin EVM Layer 2 chains as needed or create a multi-chain smart contract that communicates with each other under the same contract. This method can build a larger audience and foster interoperability between different blockchain ecosystems, thereby enhancing the utility and reach of HNDL. \ <br>


---

# 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://studybitcoin.gitbook.io/hndl-bitcoin-handle-naming-system/1.1-background.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.