> For the complete documentation index, see [llms.txt](https://circular-protocol.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://circular-protocol.gitbook.io/whitepaper/circular-vs-interoperability.md). # Circular vs Interoperability Circular’s architecture is intended to support interoperability across multiple Circular blockchains, including cross-chain transactions where permitted (for example, subject to access controls on private chains). Smart contract execution is designed to be able to reference state and transactions across authorized chains, subject to defined protocol rules and security constraints. Our near-term focus is implementing and hardening the protocol features required to support this interoperability within the Circular ecosystem. Longer-term, we plan to evaluate integrations with external networks and standards as they mature. Any external interoperability would be introduced through governed upgrades and explicit integration modules, with security, permissions, and operational boundaries defined per integration. By taking an incremental approach, we aim to expand connectivity without compromising the safety, auditability, or reliability of the network. --- # 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://circular-protocol.gitbook.io/whitepaper/circular-vs-interoperability.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.