This is a referendum to authorize runtime upgrade 11: expand capabilities by integrating ERC20 and oracle chain extensions into Pendulum, setting fees for incoming assets.

## Release Overview

For comprehensive details and insights into the new features accompanying this release, we invite you to visit [the Github release page](<https://github.com/pendulum-chain/pendulum/releases/tag/pendulum-release-11>). Key implementations:

- Expand capabilities by integrating ERC20 and oracle chain extensions into Pendulum, leveraging the proven code from Foucoco.

- Setting up XCM fees the incoming assets




This referendum is a significant step forward in the development and growth of our network.

Authorize an upgrade to a given `code_hash` for the runtime. The runtime can be supplied
later.

The `check_version` parameter sets a boolean flag for whether or not the runtime's spec
version and name should be verified on upgrade. Since the authorization only has a hash,
it cannot actually perform the verification.

This call requires Root origin.

Problem Statement & Audience:
- Problem Statement: The Polkassembly council is proposing a referendum to authorize a runtime upgrade to expand capabilities by integrating ERC20 and oracle chain extensions into Pendulum and setting fees for incoming assets.
- Audience: Polkassembly council members and stakeholders.

Significance:
- This referendum is a significant step forward in the development and growth of the Polkassembly network.

Proposed Solution:
- The proposed solution is to integrate ERC20 and oracle chain extensions into Pendulum and set up XCM fees for incoming assets.

Expected Outcomes:
- The expected outcomes of this referendum include expanded capabilities, improved functionality, and increased network efficiency for the Polkassembly network.

#14 Authorize runtime upgrade to Pendulum release 11

No Active Proposals