# Roadmap Per [HIP-14](https://forum.hop.exchange/t/rfc-protocol-fees-and-a-commitment-to-public-goods-funding/566), the DAO has decided to make the development of a V2 Core Messenger its priority for 2023. The V1 Asset Bridge has proven Hop's multichain infrastructure. This next phase opens it up for a whole ecosystem of applications ecosystem to be built on top. ### What is the Core Messenger? The Hop Core Messenger is a simple, trustless messaging protocol that can be used to build powerful cross-chain applications. How it works * The Core Messenger uses a hub-and-spoke model * Messages are aggregated into bundles * The bundle is hashed and sent to the destination * Native bridges with Ethereum are used to pass the bundle hash * At the destination, messages in the bundle can be unpacked and executed Because the native bridges can sometimes be slow, the Hop Core Messenger is best used for messages that require trustlessness and high-security but are not time sensitive (e.g. value settlement, dispute resolution, DAO governance, etc.). Faster messaging models such as collateralized messaging and optimistic messaging (as seen in Hop V1) can be easily implemented on top of the Core Messenger for application-specific or generalized use cases. ### What can be built on top of the V2? The Hop Roadmap foresees a myriad of modules to be built on top of this simple & trustless Messenger. Modules will enable cross-chain functionality such as: * Messaging * Token transfers * NFT transfers * Omnichain tokens * And many more custom use cases ✨ Among other things, the V2 will introduce much larger economies of scale as the amount of messages that can be added into Bundles increases the more applications develop on top of it. This will decrease costs and improve the capital efficiency of the asset bridge which is still the bread and butter vertical for Hop. --- # 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.hop.exchange/governance/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.