[Referendum 34](https://centrifuge.subsquare.io/democracy/referendum/34) passed but the pre-image was not stored on-chain which caused the scheduler not to be able to find the preimage and as a result, the proposal didn't get enacted.

So this proposal has been resubmitted and will be **fast-tracked** with a voting time of **900 blocks** (approximately 3 hours).


The proposal seeks funding for the 2023 Summer Polkadot Hackathon in Shanghai, China, organized by OneBlock. It aims to promote Substrate and Polkadot ecosystem growth by attracting developers and converting course learners into builders. Previous hackathons in 2021 and 2022 have been successful, and this event is scheduled for July 2023. Specific metrics include developer participation and project diversity. The execution plan includes registration, coding, workshops, and a demo day. Costs encompass venue, materials, travel, staff compensation, and an afterparty. The proposal emphasizes community building, technical education, and ecosystem expansion, aligning with Parity Asia's Substrate initiatives.

Develop the KILT Decentralized Identity Provider (DIP) protocol.

Deploy provider and relying party components on testnets and production chains.

Test, integrate, and fix any issues that arise during deployment.

Explore and implement future improvements, such as support for verifiable credentials and trustless parachain-to-parachain messaging solutions.

Maintain and update the protocol to ensure compatibility with the latest Polkadot versions.

Send a batch of dispatch calls.

May be called from any origin.

- `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 call are dispatch 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 a proposal called Referendum 34.
- The problem was that the pre-image was not stored on-chain.
- Because of this problem, the proposal couldn't be enacted.
- The proposal has been resubmitted and will be fast-tracked.
- The voting time for the proposal will be 900 blocks, which is about 3 hours.

#36 CP51(RU): Onboarding the 2nd batch of collators (resubmission)

No Active Proposals