> For the complete documentation index, see [llms.txt](https://privacyoncoil.gitbook.io/coil-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://privacyoncoil.gitbook.io/coil-docs/using-coil/broadcasters.md). # Broadcasters How private transactions get submitted and paid for onchain. A private transaction still needs to be submitted to a public blockchain and have its gas paid. Coil supports broadcasters: external wallets that submit transactions on behalf of users. They pay the blockchain transaction cost and receive compensation for their service. This separates the wallet authorizing the private activity from the public address submitting the blockchain transaction. Broadcasters are transaction-submission infrastructure. Users should never give them spending keys or recovery phrases. ### For users Broadcaster selection is part of the transaction experience. A wallet may request a quote, display the expected deduction and submit through an available broadcaster. If submission fails, the first step should be to establish whether the transaction reached the blockchain. A failed interface request is not sufficient evidence that no transaction was submitted. ### For integrators Broadcaster availability, quote expiry, transaction status and retry handling deserve explicit interface states. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://privacyoncoil.gitbook.io/coil-docs/using-coil/broadcasters.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.