# Roadmap ### **HDS 1.0：Indra** 1.Honingdas Network overall architecture design 2.NFTs design & website design & token design 3\. Seek more Fil storage nodes to support cooperation and establish HDS-DAO 4\. Get the FIL ecological support fund based on the proportion of creation and collision ### **HDS 2.0： Brahma** 1.HDS contract release test network, collision test, publish website and white paper 2.HDS officially launched the Genesis collision, and the first 100 positions of BNB & FIL positions became the first verified addresses 3.HDS completes token generation and builds built on the PancakeSwap liquidity pool 4\. Improve the organizational structure of the HDS-DAO Treasury ### **HDS 3.0： Shiva** 1\. The FUSD is issued and circulated, and the HDS-DAO State Treasury and its collision address are the first minders of the F U S D 2\. Launch the FUSD revenue aggregator 3\. The UBill NFT issues and circulates, and the FUSD mortgaged in the earnings aggregator obtains tradable / tradable NFT deposit notes 4\. Launch a web3.0 application based on UBill to realize incentive distribution ### **HDS 4.0： Vishnu** 1\. FUSD protocol based on HDS network supporting FVM 2\. Realize the fully decentralized casting, exchange and destruction of FUSD, and the casting rights and destruction rights are all transferred to the IPFS network 3\. Expand the UBill use case, and the UBill will trust the network for access to 100 web3.0 applications 4\. Launch a new poly AMM decentralized trading market based on FVM ### **HDS 5.0： Surier** A brand new SDK that will standardize Honingdas Network development, making it easy to build new web3 applications and allow the Honingdas Network to communicate with each other. Bring more than 1000 projects developed using API into the Honey Badger network. **2023: As a lightweight, low-cost, trust-free bridge based on Honey Badger network computing technology, FVMBridge aims to expand this open source technology to any blockchain to provide a lot of market capitalization liquidity to an ecosystem of smart contracts, DeFi, DEXes and other use cases.** **$HDS addresses 300,000 +** Development: The Honingdas Network asset class agreement enters the development stage Product: The FUSD stablecoin currency market is fully tested and open for use Eco: Work with multiple top Web3 projects to build an interoperable DeFi protocol network **$HDS holds 500,000 + currency addresses** Development: The ALL BLUE enters the development stage Product: Publish the first web3 application built based on Honingdas Network Eco: Become the first metauniverse community of the cryptographic world **$HDS holds 800,000 + currency addresses** Development: The Honingdas Network lending agreement has entered the development stage Product: Launch a fully decentralized Honingdas Lend financial derivatives aggregator market Eco: Support 100 web3.0 dApp to boost the development of metacverse technology **$HDS holds 1 million + currency addresses** A brand new SDK that will standardize Honingdas Network development, making it easy to build new web3 applications and allow the Honingdas Network to communicate with each other. Led by the Honingdas Network Network Foundation, it aims to give developers access to confidential smart contracts, as well as powerful new tools, such as the bridge with the FVM. Bring all more than 100 projects developed using the API into the Honingdas network. **2024: Launch more than five Honingdas Network web3 applications on GooglePlay. Develop your own virtual reality device. Work with Amazon to do the retail business. Set up offline virtual world pavilions around the world. Progressive participation of global citizens in the Honingdas Network Metaverse ecosystem** --- # 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://honingdas.gitbook.io/honingdas.net/roadmap.md?ask= ``` 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.