# 5.1 Road Map and Future Enhancements

### **Phase 1: The Foundation**

* **ERC-6551:** Handles will turn into token-bound accounts, each with its own Rootstock address to receive ERC assets. (Q4 2024)
* **HNDL Market Place:** Buy and sell your handles from fameguild.io and other marketplaces (Q1 2025)
* **SIWH:** 'Sign in With Handle' is a protocol for signing in to apps using handles. (Q2 2025)
* **HNDL in Layer 1:** Own your handles on Bitcoin Layer 1 with ordinal inscriptions. (Q3 2025)
* **ZK-ERC-6551:** A modified version with zero-knowledge proofs. (Q4 2025)

### **Phase 2: Integration with Web 2 & 3 Ecosystem**

* **Study Bitcoin:** Use SIWH on our Study Bitcoin platform, a learn-to-earn system utilizing handles. (Q1 to Q4 2026)​
* **Mass Adoption of SIWH:** Promote SIWH as the login standard and collaborate with creators to integrate it into their apps (fitness, dating, video streaming, social media, etc.) (2026-2027)

###  **Phase 3: Ownership Renounce and Decentralization**

* Renounce the HNDL smart contract ownership once all testing meets the established criteria to achieve 100% decentralization. (Q1 2027)

### [<br>](https://studybitcoin.gitbook.io/hndl-bitcoin-handle-naming-system/5.2-phase-2-integration-with-web-2-and-3-ecosystem)**Phase 4: HNDL Wallet and Explorer**

* A user friendly crypto wallet tailored for HNDL (Q1 2028)
* Integrate HNDL into Rootstock's main explorer (Q4 2028)


---

# 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/5.1-road-map-and-future-enhancements.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.