# Roadmap

**Presale and Launch Phase 🎯**

1. Designing website and socials.
2. Designing and auditing the contract.
3. Conducting presale.
4. Establishing strategic partnerships with KOLs and influencers.
5. Issuing press releases and collaborating with various marketing teams.
6. Forming partnerships with top DeFi development experts.

**Launch and Growth Strategy🔐**

1. Uniswap launch.
2. Listing on Coinmarketcap and Coingecko.
3. Releasing staking and farming pools.
4. Securing coverage on trending sites.
5. Launching OBTC SWAP and Launchpad.
6. Listing on Tier 1 and Tier 2 Exchanges.
7. Releasing OBTC wallet for cross-chain asset bridging.

**Enhanced Visibility, Usage, and Reach 🔑**

1. Forming cross-community partnerships to promote utility and Launchpads.
2. Partnering with multiple token and utility developers to encourage Launchpad usage.
3. Conducting Certik audit and regular security audits.
4. Releasing Testnet to ensure security before blockchain launch.
5. Inviting various communities to test our blockchain.
6. Launching $OBTC blockchain.

**Exponential growth 📈 strategy of blockchain and Launchpads📣**

1. Enabling the opportunity for launch of multiple launchpads on our blockchain.
2. Listing in Top Exchanges like Binance Okx Crypto.com etc
3. Integrating our L1 Blockchain and ecosystem with multiple exchanges with rich source of volumes and technical support.
4. Introducing multiple burn mechanisms within the blockchain for burning tokens in $OBTC ecosystem.
5. Regular security checks community feedbacks and hardfork the blockchain with enhanced transparency and growth mechanisms.

\
\
\
\ <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://ordinal-btc.gitbook.io/ordinal-btc-whitepaper/fundamentals/roadmap.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.