[Forum Post](https://forum.moonbeam.network/t/proposal-88-proposed-enable-core-autorenewal-for-moonriver/2287)

**Abstract**

This proposal executes two XCM messages, one to open an XCM channel with the Coretime chain, and the other to enable the core autorenewal. This ensures we don’t have to renew the core manually every time.

**Details**

This proposal is based on the following document. The tasks that need to be done are setting up the HRMP channel with the Coretime chain, which is the first item of the batch call.

The second item is the enablement of the autorenewal feature.  XCM channels need one Kusama session actually to be set, so the core autorenewal call was wrapped with a scheduler. The scheduler will execute the call 1800 blocks after the proposal is executed, which provides 3 hours if we account for 6-second block times.

`0x1e02086700030100031400040000000003fa1f7847130000000003fa1f784700060003a03e44dc04183c0aed030000140d01000001009d1f3c04080700000000670003010100b50f03140004000100000712bce7c80513000100000712bce7c8050006010320ca157d043432151b00e70700000108e60500140d01000001009d1f`

Preimage tested in Chopsticks (including the scheduler): `0xb98329ae06fe41e880f47ed403feda278c9e88a6af85a9b6f4c5b101ed42533e`

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

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

#88 [Proposal: 88] Enable Core Autorenewal for Moonriver

No Active Proposals