# Deploy on hVM {% hint style="info" %} ## 📜 **TL;DR:** * To use hVM directly, you will have to call the appropriate precompile address with the appropriate serialized bytes to pass parameters to the function. * Most dApp developers will use the Hemi Bitcoin Kit (hBK) **rather** than hVM directly. {% endhint %} *** ## 🌐 Overview * To use hVM directly, you will have to call the appropriate precompile address with the appropriate serialized bytes to pass parameters to the function. * Each successful precompile call will return serialized bytes according to the precompile’s return data specification. *** ## 🟨 Developer Tip > **Most dApp developers will use the Hemi Bitcoin Kit (hBK) rather than hVM directly.** * If you’re looking for an easy way to get started developing Bitcoin-aware dApps on Hemi, check out the “Hemi Bitcoin Kit (hBK)” section. Understanding how Bitcoin Kit uses hVM under-the-hood may be helpful, and dApp developers looking to maximize gas efficiency may benefit from using hVM directly to avoid paying overhead for unmarshalling data they don’t need for a specific use case. ### --- # 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.hemi.xyz/building-bitcoin-apps/hemi-virtual-machine-hvm/deploy-on-hvm.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.