A recent runtime upgrade deleted our schedule for daily founder allocations.

A description of the problem as well as the remedy can be found here:
[https://github.com/integritee-network/parachain/issues/195](https://github.com/integritee-network/parachain/issues/195)


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

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

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

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.

- There was a problem with the schedule for daily founder allocations.
- The problem was caused by a recent runtime upgrade.
- The issue has been identified and a remedy has been found.
- You can find more information about the problem and the remedy at the provided link.
- The problem has been fixed.

#15 Fix founder allocation schedule

No Active Proposals