> For the complete documentation index, see [llms.txt](https://docs.frequencychain.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.frequencychain.org/14.-cross-chain-interoperability-using-fswap/14.6-security-considerations.md). # 14.6 Security Considerations The bridge mechanism is designed with strict controls to ensure asset safety. These include: * locking contracts that securely hold FreCx tokens * controlled minting of WFreCx only upon verified lock events * mandatory burn operations before token release * transaction verification across both chains These safeguards ensure that assets cannot be duplicated or manipulated during cross-chain transfers. The FreCx bridging mechanism enables seamless asset movement across blockchain ecosystems while maintaining strict supply consistency and security guarantees. By leveraging the lock-and-mint / burn-and-release model and introducing WFreCx as a wrapped asset, FreCx extends its usability beyond its native network and into broader multi-chain environments. --- # 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://docs.frequencychain.org/14.-cross-chain-interoperability-using-fswap/14.6-security-considerations.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.