<p>In order to alow TEER to be transferred to Asset Hub Kusama by anyone, we need KSM as an asset on our chain because XCM fees for Asset Hub need to be paid in KSM<br /><br />Noteworthy is the asset controller: it is a non-account. A simple string with no private key. This equals having no asset controller at all, which is desired. Only root origin can make changes to this asset</p>

In order to alow TEER to be transferred to Asset Hub Kusama by anyone, we need KSM as an asset on our chain because XCM fees for Asset Hub need to be paid in KSM  
  
Noteworthy is the asset controller: it is a non-account. A simple string with no private key. This equals having no asset controller at all, which is desired. Only root origin can make changes to this asset

Schedule a majority-carries referendum to be tabled next once it is legal to schedule
an external referendum.

The dispatch of this call must be `ExternalMajorityOrigin`.

- `proposal_hash`: The preimage hash of the proposal.

Unlike `external_propose`, blacklisting has no effect on this and it may replace a
pre-scheduled `external_propose` call.

Weight: `O(1)`

0x4b7573616d61204b534d

Send a batch of dispatch calls.

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`).

## Complexity
- O(C) where C is the number of calls to be batched.

This will return `Ok` in all circumstances. To determine the success of the batch, an
event is deposited. If a call failed and the batch was interrupted, then the
`BatchInterrupted` event is deposited, along with the number of successful calls made
and the error of the failed call. If all were successful, then the `BatchCompleted`
event is deposited.

- Problem Statement: TEER transfer to Asset Hub Kusama requires KSM on the chain for XCM fees, with the asset controller being a non-account.
- Significance: Ensuring seamless TEER transfers to Asset Hub Kusama and simplifying asset controller management.
- Proposed Solution: Incorporating KSM as an asset on the chain with a non-account asset controller.
- Expected Outcomes: Streamlined TEER transfers, improved asset controller management, and enhanced functionality for users.

#47 Register KSM asset on Integritee Network

No Active Proposals