# Broadcaster Components Diagram

<figure><img src="/files/2sejyxkZ7WzPHJfM3HAD" alt=""><figcaption></figcaption></figure>

This component diagram focuses on the **broadcaster** role and its interactions within the system. Here's a breakdown of the diagram:

1. Main Components:
   * RolesManager: Manages roles, including the MESSAGES\_BROADCASTER role.
   * Registry: Provides access to other components and configurations.
   * InterNetworkExecutor: Handles cross-network message execution.
   * Gateway: Processes cross-chain messages.
   * OneLayerGateway: An alternative gateway implementation.
   * Broadcaster: Represents the external entity with the broadcaster role.
2. Relationships:
   * Dashed lines with open arrows (..>) represent dependencies or usage.
3. Entry Points:
   * InterNetworkExecutor: The `execute(ExecutionMessage)` method is an entry point for the broadcaster.
   * OneLayerGateway: The `receiveMessage(CrossChainMessage)` method is another entry point for the broadcaster.
4. Key Interactions:
   * The Broadcaster interacts directly with InterNetworkExecutor and OneLayerGateway.
   * All components depend on the Registry for accessing other parts of the system.
   * The Registry uses the RolesManager to check roles.

<details>

<summary>Diagram Code</summary>

```mermaid
classDiagram
    class RolesManager {
        +MESSAGES_BROADCASTER
        +hasRole()
    }

    class Registry {
        +getRolesManager()
        +getInterNetworkExecutor()
        +getCentralGateway()
    }

    class InterNetworkExecutor {
        +execute(ExecutionMessage)
    }

    class OneLayerGateway {
        +receiveMessage(CrossChainMessage)
    }

    class Broadcaster["Broadcaster (External)"]

    Registry --> RolesManager : uses
    InterNetworkExecutor --> Registry : uses
    OneLayerGateway --> Registry : uses

    Broadcaster --> InterNetworkExecutor : calls
    Broadcaster --> OneLayerGateway : calls

    class InterNetworkExecutor {
        <<entrypoint>>
    }
    class OneLayerGateway {
        <<entrypoint>>
    }


```

</details>


---

# 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://docs.1layer.io/readme/architechture/smart-contracts/broadcaster-components-diagram.md?ask=<question>
```

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.