> For the complete documentation index, see [llms.txt](https://fogcomputingchain.gitbook.io/fog-computing-chain/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://fogcomputingchain.gitbook.io/fog-computing-chain/key-technology/cross-chain/arbitrator.md). # Arbitrator The above transfer process has the participation of the arbitrators. In the transfer of the backbone to the side chain, the role of the arbitrator is to generate and transfer transactions to the side chain, and does not participate in the signature; in the side chain and transfer of the main chain, but also signs the transaction, so that the "extract Token transaction" on the main chain from the account representing the side chain to the general account can be verified by each backbone node. The arbitrator is elected by voting on the main chain, and is regularly rotated.Each arbitrator needs to provide sufficient computational and network resources to run at least one backbone node and N nodes corresponding to the N side chain.The arbitrator's proceeds came from the transaction fee obtained by packing the block for the side chain. **First first to be considered in technical design;** SVM is the execution environment of FOGR, which has fully compatible execution environment SVM (FOGR, VirtualMachine) with EVM (Ethereum Virtual Machine). Developing migration costs are very low, and so FOGR has unique advantages over other schemes. It is exaggeration to say that SVM is an important core technology of FOGR. SVM supports all existing Ethereum development tools and libraries, including Solidity,Vyper,Truffle,Open Zeppelin,Web3.js.The compiler was tested only in the Waffle (Translator Note: A lightweight test runner for Ethereum smart contracts).We are doing other integrations like Truffle and looking forward to understanding the needs of the community to decide what to prioritize integration next. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://fogcomputingchain.gitbook.io/fog-computing-chain/key-technology/cross-chain/arbitrator.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.