# BlockBolt's Visionary Roadmap

Our roadmap lays out our strategic vision and the significant milestones we strive to achieve as we pioneer innovation and revolutionize how people conduct transactions. Although we may encounter some setbacks while building the BlockBolt ecosystem, our team remains determined to keep going!

**Quarter 1 - 2023**

\-          Website launch

\-          Preparing documents

\-          Smart contract development on the Sui network

**Quarter 2 – 2023**

\-          Merchant payment interface for demo

\-          Private demo release

\-          Boltpay SDK development

**Quarter 3 – 2023**

\-          Code audit payment protocol

\-          Link payment feature

\-          Ecommerce payment

\-          POS payment

\-          DeFi payment

\-          Boltpay SDK / dev docs release Testnet on Sui (Private)

\-          Payment wallet - Android

**Quarter 4 - 2023**

\-          Payment wallet - iOS

\-          Offline retail payment - SoundBox

\-          Merchant Portal

\-          Merchant products, POS, and orders

\-          APIS for merchant apps

\-          Merchant eCommerce

\-          Release: WooCommerce plugin

\-          Marketing campaign

\-          Bug bounty

**Quarter 1 – 2024**

\-          Release: the Blockbolt ecosystem on the Sui network (Mainnet)

\-          Dev docs release for mainnet

\-          Order notification Soundbox hardware integration for offline and online merchants

\-          Boltpay SDK release on Typescript/ Flutter

\-          Stablecoin support (USDC & USDT)

\-          Multichain support (Aptos, Venom, EVM)

&#x20;           o   eCommerce payment\
&#x20;           o   POS payment\
&#x20;           o   Link payment\
&#x20;           o   DeFi payment\
&#x20;           o   Offline retail payment – SoundBox

\-          Release: Shopify application

\-          Marketing campaign

**Quarter 2 – 2024**

\-          Multichain support (Aptos, Venom, EVM)\
\
&#x20;           o   Merchant products, POS, orders and invoices\
&#x20;           o   Merchant APIs to interact with different apps\
&#x20;           o   Merchant eCommerce

\-          Payment wallet supports for multichain

\-          Feature enhancements and multichain support (client and user)

\-          NFT support

\-          Utility token introduction\*

\-          Loyalty module introduction

\-          Magento plugin/extension release

\-          Marketing campaign

**Quarter 3 – 2024**

\-          Release: the Blockbolt ecosystem on the multichain (Mainnet)

\-          Dev docs release for multichain mainnet

\-          Bug bounty  and code audit

\-          Feature enhancements and multichain support (client and user)

\-          Strategic public sale/listing\*

\-          POS enhancements for hardware devices

\-          Development – Scheduled Payments

\-          Marketing campaign

\-          Bug bounty

**Quarter 4 – 2024**

\-          Release: Scheduled Payments on multichain

\-          Feature enhancements and multichain support (client and user)

\-          Marketing campaign

\-          Continuous contract audit and bug bounty

**Quarter 1 – 2025**

\-          Feature enhancements and multichain support (client and user)

\-          Continued marketing and merchant integration

The plan presented above gives a broad summary of BlockBolt's growth path, highlighting important targets and achievements. Nonetheless, it's important to keep in mind that specific schedules and priorities may be subject to alteration based on market trends, technological advancements, and feedback from users.


---

# 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.blockbolt.io/roadmap/blockbolts-visionary-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.
