<h1 id="">&nbsp;</h1>
<ul>
<li><strong>Description:</strong> This referernda contains following changes:
<ul>
<li>Whitelisting State Machines</li>
</ul>
</li>
<li><strong>Desired outcome:</strong>
<ul>
<li>Hyperbridge pallet requires state machines to be whitelisted before any consensus proofs can be accepted, Hyperbridge included. This ensures that solochains are not spammed with consensus proofs of unwanted chains.</li>
</ul>
</li>
<li><strong>Benefit for the stakeholders:</strong>
<ul>
<li>This adds new state machines which produce GRANDPA consensus proofs to the pallet whitelist, enabling trustless cross-chain communication with the state machines in question.</li>
</ul>
</li>
</ul>

*   **Description:** This referernda contains following changes:
    *   Whitelisting State Machines
*   **Desired outcome:**
    *   Hyperbridge pallet requires state machines to be whitelisted before any consensus proofs can be accepted, Hyperbridge included. This ensures that solochains are not spammed with consensus proofs of unwanted chains.
*   **Benefit for the stakeholders:**
    *   This adds new state machines which produce GRANDPA consensus proofs to the pallet whitelist, enabling trustless cross-chain communication with the state machines in question.

Fixing a problem with xcvDOT, xcvGLMR, xcFIL, and xcvFIL tokens on Moonbeam network and enable trading on Dexs

Add some a state machine to the list of supported state machines

- **Problem Statement:** Implementing whitelisting for state machines to prevent spamming of solochains with unwanted consensus proofs.
- **Significance:** Enhances security by ensuring only approved state machines can participate in cross-chain communication.
- **Proposed Solution:** Whitelisting state machines in the Hyperbridge pallet before accepting consensus proofs.
- **Expected Outcomes:** Improved security and trustless cross-chain communication by adding approved state machines to the pallet whitelist.

#23 Whitelisting State Machines

No Active Proposals