# MVDs When a new MVD wishes to join the system there should be a network wide vote by VOW token holders, where anyone can put forward a proposed MVD address, the network votes and if successful automatically hooks in the new MVD associated with a particular Vcurrency contract. Any merchant should be able to choose any MVD for initial setup and should have the ability to switch between MVDs Since MVDs are essentially performing oracle services, reporting on fiat transactions and allowing merchant signup (and therefore VSC issuance) they should have a VOW stake to register with the network and be challengeable. Deregistration should be enactable by the MVD themselves as long as they are not under challenge. --- # 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://vow-2.gitbook.io/white-paper/decentralisation-and-governance/other-considerations/mvds.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.