> For the complete documentation index, see [llms.txt](https://docs.summer.fi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.summer.fi/lazy-summer-protocol/governance/cross-chain-governance.md).

# Cross-Chain Governance

## Overview

The Summer Protocol employs a cross-chain governance system, with the **Base** network serving as the central authority (the "Hub Chain"). All other supported networks operate as execute-only **Satellite Chains** (also referred to as "spoke chains").

Supported networks currently include the **Base** hub plus **Ethereum, Arbitrum, Optimism, Unichain, Sonic and HyperEVM** spoke chains.

## Hub Chain: BASE

Base acts as the central hub for all governance activity and is the source of truth for decision-making. Key responsibilities:

* **TimelockController:** governance actions are subject to a timelock.
* **Token supply & distribution:** Base manages minting and allocation of $SUMR across chains.
* **Proposal creation & voting:** all proposals are created and voted on exclusively on Base.

## Satellite Chains

Satellite chains are execute-only: they cannot create proposals or host votes. They:

* Begin with zero $SUMR (no native governance capability).
* Receive tokens only via the secure "teleportation" mechanism from Base.
* Execute governance decisions relayed from the hub.

## Cross-Chain Communication

Governance messaging between Base and satellite chains uses **LayerZero** for secure, tamper-proof cross-chain messages. (The SummerToken itself is a LayerZero OFT, enabling teleportation across supported chains.)

## Governance Workflow

The flow of a governance proposal within the Summer Protocol is outlined below:

<figure><img src="/files/laBGcCmdbmLU94Fr8bBx" alt=""><figcaption></figcaption></figure>

**Process Explanation**

1. Proposal Creation: A governance proposal is initiated on the Hub (BASE).
2. Voting Delay: A specified delay period passes before voting begins, allowing participants to review the proposal.
3. Voting Begins: $SUMR holders vote on the proposal within the designated period.
4. Voting Period Expires: After the voting period ends, the results are evaluated to determine if the proposal passed.
5. Proposal Queued: Approved proposals are queued in the Timelock Controller for a predefined period.
6. Execution on Hub: The proposal is executed on BASE, finalizing the decision at the hub level.
7. Message Transmission: LayerZero securely transmits the execution message to the relevant Satellite Chain(s).
8. Reception by Satellite: The SummerGovernor on the Satellite Chain receives the message and processes the decision.
9. Execution on Satellite: The Satellite Chain executes the proposal, completing the cross-chain governance cycle.