This is a proposal to add a Bridge Hub (BH) parachain to Polkadot. All technical details can be found in the [Bridge Hub Genesis release](https://github.com/paritytech/cumulus/releases/tag/parachains-bridge-hub-polkadot-v9382). The runtime is taken from the v9382 parachains release.

The BH will be the gateway between Polkadot and other networks, like Kusama and Ethereum. For now, the BH only contains some basic logic, and none of the bridge-specific pallets. Those will get added in future runtime upgrades; the goal of this proposal is to get approval from Polkadot stakeholders and launch a "shell" such that bridge teams can focus on releasing their bridge logic, not launching a parachain.

The BH will primarily act as a message routing system within the network and between others. For example, parachains can configure their XCMP routing to interpret `parents: 2` (indicating, "go to another consensus system") as something to send to the BH to handle. Likewise, the BH can handle incoming messages and route them to the correct parachain within Polkadot.

Once operational, a Polkadot<>Kusama bridge will allow more interaction between the networks. For example, from the Polkadot Collectives parachains, the Technical Fellowship can serve both Polkadot and Kusama; or the Kusama network (as a unit body) could join the Polkadot Alliance.

Send a batch of dispatch calls and atomically execute them.
The whole transaction will rollback and fail if any of the calls failed.

May be called from any origin except `None`.

- `calls`: The calls to be dispatched from the same origin. The number of call must not
  exceed the constant: `batched_calls_limit` (available in constant metadata).

If origin is root then the calls are dispatched without checking origin filter. (This
includes bypassing `frame_system::Config::BaseCallFilter`).

# <weight>
- Complexity: O(C) where C is the number of calls to be batched.
# </weight>

 Summary of the Polkassembly Referendum post 

1. Proposal to add a Bridge Hub parachain to Polkadot 
2. The BH will be gateway between Polkadot, Kusama, and Ethereum networks 
3. Not yet containing bridge-specific pallets; will be added in future runtime upgrades 
4. Primary functions include message routing and handling 
5. Polkadot<>Kusama bridge will enable more interaction between the networks 
6. Examples: Polkadot Collectives parachains serving both networks, and Kusama network joining Polkadot Alliance 
7. Runtime taken from the v9382 parachains release

#114 Polkadot Bridge Hub Genesis

No Active Proposals